Adding Oracle EBS WebADI object support to Stat (4368612)

Adding Oracle EBS WebADI object support to Stat

You can use the Generic Loader (FNDLOAD) concurrent program to download integrator definitions from an Oracle E-Business Suite instance to a text file, and to upload integrator definitions from a text file to an Oracle E-Business Suite instance. For example, you can download an integrator definition from a development or test instance and upload it to a production instance. You can also download and store a text file representation of an integrator definition for source control purposes. 

Use the bneintegrator.lct configuration file with the Generic Loader to load integrator definitions. The bneintegrator.lct file is located in the $BNE_TOP/patch/115/import/ directory.  

The entity for this configuration file is BNE_INTEGRATORS . This entity includes the following sub-entities: BNE_QUERIES, BNE_PARAM_LISTS, BNE_COMPONENTS, BNE_SECURED_OBJECTS, and BNE_VIEWERS.

The Developer Guide, in this instance, gives me exactly what I need in order to add the configuration to Stat.  The example I am providing here is for a single integrator (INTEGRATOR_CODE) since I want to manage, version, migrate, and track objects individually.  The option to do all or a group of integrators could potentially cause locking issues in Stat as well as make it more difficult to track the change history of a specific integrator.

New Oracle Setup objects may be added via the Stat Object Type Maintenance screen.  Access to Object Management requires Administrator level access.  It is also recommended that you first configure any new setup objects in your non-production Stat environment.  The navigation to the screen is Maintenance | General | Object Types | Object Class: Oracle App Setup Objects.

1. In the Object Class field, select Oracle Apps Setup Objects.  

2. Click New.

3. Create an entry for BEN Startup Action Types, as illustrated below:
   File type: BNE Integrators     Type code: BNE

4. Mouse click the Apply button to save.

5. Mouse click the Setup button at the top right of the window. This opens the Details window.

6. Select the version of Oracle Applications you are using. Next, you need to map the contents of the .lct file into Stat.

7. In the Lct Filename field, enter bneintegrator.lct.

8. In the Entity Name field, enter BNE_INTEGRATORS.

9. Next, you can optionally pass any appropriate parameters to the FNDLOAD utility in the Parameters field. For new records, it defaults to the value, “CUSTOM_MODE=FORCE.”

10. In the Lov Partial Sql field, enter:

    from BNE_INTEGRATORS_TL bib

    ,fnd_application fa

    where bib.APPLICATION_ID = fa.APPLICATION_ID

    This is the sql statement that retrieves the list of objects.

11. Next, you need to define the parameters that identify a unique row. Our first parameter name is integrator_asn, column name is fa.PRODUCT_CODE, and the display name is ASN.

12. Click the Add button to add the second parameter. The name is integrator_code, column name is bib.INTEGRATOR_CODE and the display name is Integrator code.

13. Click Update to save your changes.

14. Restart the Stat Oracle Agent to test our new configuration. Once the agent is restarted, you can perform a Fetch Object list to verify the new object type.

15. In the Environment field, select an environment.

16. Click Fetch. A list of objects will be retrieved if the object is defined correctly. In our example, the list has 2 columns corresponding to each parameter that you defined. Now you can test the archive for any particular row from the retrieved list.

    

17. Select a row from the list and click Test Archive

18. Once agent is done, examine the content of the archive to make sure a unique row was retrieved.

    

19. If content of the archive textbox does not identify a unique record or it is empty, you will likely get an error on the Oracle Agent log. In this case, you may need to run your Oracle Agent in Debug mode to identify any problems.

This information is provided as an example only of how Stat can be extended to support configurations not delivered with the product. If you decide to use the information in this article to configure support for WebADI, please test it thoroughly before using it in production. These are considered custom objects and would only be supported by Quest to the same extent to which Oracle supports your customizations to EBS. Oracle® E-Business Suite Desktop Integration Framework Developer's Guide | Oracle E-Business Suite Documentation Web Library Release 12.2 / Technology. https://docs.oracle.com/cd/E26401_01/doc.122/e22005/T544562T544566.htm https://docs.oracle.com/cd/E18727_01/doc.121/e15877/T544562T550952.htm Preservation of data | Oracle E-Business Suite Documentation Web Library Release 12.2 https://docs.oracle.com/cd/E26401_01/doc.122/e22953/T174296T575361.htm