Importing View Object to Physical and Logical Layers

This issue applies to Fusion Direct (Non SAAS) run.

The full or incremental load after upgrade runs into an error as the FscmTopModelAM.DooTopAM.ReturnReason view object is missing in the 11.1.1.10.1 RPD.

Workaround

Use these instructions to import the FscmTopModelAM.DooTopAM.ReturnReason view object in to the physical and logical layers.

1. Stop BI Services and open RPD.
2. In the Physical Layer of the RPD, right click Connection Pool under oracle.apps.fscm.model.analytics.applicationModule.FscmTopModelAM_FscmTopModelAMLocal.
   
   Description of the illustration GUID-45FA291B-D877-4690-B639-739B577BCF40-default.gif
3. Click Import Metadata.
4. In the Import Metadata — Select Metadata Objects dialog, enter ReturnReason in the Find field and click Search icon.
   
   Description of the illustration GUID-91F9A11E-D1BA-4D39-83CB-49807EA32046-default.gif
5. Select FscmTopModelAM.DooTopAM.ReturnReason in the Data Source View pane, select oracle.apps.fscm.model.analytics.applicationModule.FscmTopModelAM_FscmTopModelAMLocal in the Repository View pane, and click the Import Selected icon.
   
   Description of the illustration GUID-3E80E582-FA1C-4F10-8DD6-261AFDA087BB-default.gif
   The Importing popup displays the import.

   
   Description of the illustration GUID-34A49DEA-22B4-4C11-BB1F-6DDD55E68710-default.gif
6. Click Finish when import is complete.
7. The previous steps were for the Physical Layer. Now add RefreshNumber attribute from the VO to the Z - VO OBIA ETL Logical Table in BMM Layer. Select the attribute, drag and drop it in to the Z - VO OBIA ETL logical table.
   
   Description of the illustration GUID-8C21C1BE-7B32-45DB-9B3F-D71671D5DAD4-default.gif
8. Save and close the RPD.
9. Restart the BI Services.