In our custom report we need to use some flexfields from FA retirements data FA_RETIREMENTS_GUI DFF. Of cause, we have to use segment names instead of “attributeN” fields. But, unfortunately, view FA_RETIREMENTS_V_DFV is not created at pressing “Compile” button time. As we can see, program FDFVGN “Flexfield View Generator” even is not ran. Lets set the programs “Use in SRS” flag, add three text parameters, add it to responsibility and run using parameters: 3, 140, FA_RETIREMENTS_GUI.

After that we can find the reason in the log:

The view was not created since the DFF is based on table FA_RETIREMENTS_V which is a psuedo table (TABLE_TYPE = F) Really, the FA_RETIREMENTS_GUI flexfield is based on FA_RETIREMENTS_V view.

So, FA_RETIREMENTS_V_DFV could not be created, because FA_RETIREMENTS_V view have not ROWID pseudocolumn. Lets make some research on FA_RETIREMENT% flexfields:

There are two DFFs about retirements: FA_RETIREMENTS_GUI & FA_RETIREMENTS. FA_RETIREMENTS_GUI uses RET_ATTRIBUTEn fields, while FA_RETIREMENTS uses ATTRIBUTEn fields. Lets check source of RET_ATTRIBUTEn fields:

So, RET_ATTRIBUTEn = ATTRIBUTEn !

Conclusion.

FA_RETIREMENTS_GUI & FA_RETIREMENTS descriptive flexfields should be configured identically. Assets form uses FA_RETIREMENTS_GUI DFF, but in custom extensions FA_RETIREMENTS_DFV view should be used.