Understanding OSA

You can use OSA interfaces to output to third-party software programs. OSA interfaces enable the third-party program to process and format JD Edwards EnterpriseOne data concurrently with the processing of a UBE. OSA interfaces must be predefined, typically by a representative of the third-party product that you are using. Several interfaces may exist for one program, depending on the section types included in the report and the desired output.

OSA uses its own set of commands from a third-party library.

Benefits of using OSA are:

• Employs the formatting options of the target software program.

• Employs the processing power of the target software program.

The system processes the components of batch applications in a specific order. At different points during this processing, you can trigger an event through the OSA interface.

This diagram illustrates the OSA execution points:

At each of these execution points, with the exception of PRT_InitializeLib and PRT_TerminateLib, you can call an OSA function. You can create functions or you can use existing XML libraries and their functions.