Skip Headers

Oracle® Application Server Integration Adapter for J.D. Edwards OneWorld XE User's Guide
10g (9.0.4)

Part Number B10302-01
Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

3
Defining an Interaction

This chapter describes how to configure Oracle Application Server ProcessConnect to access Business Functions in a J.D. Edwards OneWorld XE system.

When using J.D. Edwards OneWorld XE PurchaseOrder or SalesOrder, you must create three Oracle Application Server ProcessConnect interactions to accomplish one business function completion in J.D. Edwards OneWorld XE.

See Also:

"Creating a PurchaseOrder or SalesOrder Interaction" for information on using J.D. Edwards OneWorld XE and Oracle Application Server ProcessConnect interactions

This chapter discusses the following topic:

Adding an Interaction

After defining a delivery channel for a J.D. Edwards OneWorld XE system you can add interactions. Follow these instructions to add a J.D. Edwards OneWorld XE business function as an interaction in Oracle Application Server ProcessConnect.

See Also:

Oracle Application Server ProcessConnect User's Guide for details about interactions in Oracle Application Server ProcessConnect

  1. Select Modeling > Interactions.

    Text description of modeling.gif follows.

    Text description of the illustration modeling.gif

  2. Click Add to add an interaction.

  3. Expand Oracle.

    Text description of int_select.gif follows.

    Text description of the illustration int_select.gif

  4. Select JDE Adapter.

  5. Select a delivery channel.

    Text description of sel_app.gif follows.

    Text description of the illustration sel_app.gif

  6. Expand Outbound.

    The Add Interaction: Select Interaction page displays the J.D. Edwards OneWorld XE adapter exchange protocols that you can access.

    Text description of sel_out.gif follows.

    Text description of the illustration sel_out.gif

    J.D. Edwards OneWorld XE has too many modules to show in one long list. The modules are group together according to the first three characters of their name. The first level of the hierarchy is the list of all 3-character prefix for the module names. The second level lists all the modules that share the same 3-character prefix. The last level lists the business functions belonging to a module.

    Text description of sel_in.gif follows.

    Text description of the illustration sel_in.gif

    Visibility of Business Functions - If you create a new (or change a) J.D. Edwards OneWorld XE Business Object it should not be necessary to re-deploy the object in J.D. Edwards OneWorld XE in order to view it in Oracle Application Server ProcessConnect. However, it is possible that, in some scenarios with high security, this step is required. For example:

    • Create business function in the J.D. Edwards OneWorld XE system with no data structure - The business function is visible from Oracle Application Server ProcessConnect

    • Add a data structure to the business function - The business function is visible, although data structure is not

    • Check-in business function to the J.D. Edwards OneWorld XE system - The business function is visible, although data structure is not

    In most cases, stopping and restarting Oracle Application Server ProcessConnect process forces a refresh of the definitions being used. This causes the new definitions to re-load the next time you view the system in the Select Interaction screen.

    There may be cases where you must deploy the business object in J.D. Edwards OneWorld XE in order to see the changes to the data structure through Oracle Application Server ProcessConnect.

  7. Select a group and choose an interaction. For this discussion, expand B00 > B0000002 and select the ValidateLedgerTypeOptions interaction.

    Text description of int_review.gif follows.

    Text description of the illustration int_review.gif

    The Add Interaction: Review page displays the details. For an Outbound selection there is an InRecord Type and an OutRecord Type.

  8. Click Apply.

    The Confirmation screen appears, allowing you to specify the Native Format of the request.

    Text description of native.gif follows.

    Text description of the illustration native.gif

  9. Verify that the selection for the Native Format and the Extractor for the request is XSD and click Apply.

    The Confirmation screen appears, allowing you to specify the Native Format of the reply.

    Text description of reply.gif follows.

    Text description of the illustration reply.gif

  10. Verify that the selection for the Native Format and the Extractor for the reply is XSD and click Apply.

  11. The interaction continues into the Create Native Event Type wizard. You can continue using the instructions in the Oracle Application Server ProcessConnect User's Guide for this wizard.

On completion, the new interaction appears in the Interactions list.

Text description of end_int.gif follows.

Text description of the illustration end_int.gif

You can click the interaction link for a complete view of the interaction details.

Text description of end_select.gif follows.

Text description of the illustration end_select.gif


Go to previous page Go to next page
Oracle
Copyright © 2003 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index