1. Implementing Receivables Credit to Cash
  2. Set Up Oracle B2B to Send Receivables XML Transactions

Set Up Oracle B2B to Send Receivables XML Transactions

Oracle B2B Server is an Oracle SOA Suite component that manages interactions between deploying companies and trading partners. Oracle Receivables supports an outbound Oracle B2B flow using Oracle B2B Server to send transactions to customer trading partners in XML format.

The setup of the Oracle B2B flow for Receivables makes use of these existing elements:

  • XML Schema document guideline

  • OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF document definition

  • Host trading partner MyCompany

To set up Oracle B2B to send Receivables transactions in XML:

  • Configure the host and remote trading partners

  • Configure agreements between the host and remote trading partners

Configure Trading Partners

Configure your enterprise as the host trading partner, and all of your customers that receive XML documents as remote trading partners.

To configure trading partners:

  1. Log in to the Oracle B2B Server.

  2. Navigate to the Administration page.

  3. Click the Document tab.

  4. Load the OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF document definition file.

  5. Click the Types tab.

  6. Add a new Internal Identifier with the name B2B Trading Partner Code.

    This name matches the field name on the customer account profile.

  7. Navigate to the Partners page.

  8. In the Partner section, select the default host partner MyCompany.

  9. If necessary, update the default host partner name to reflect your enterprise.

  10. Click the Documents tab.

  11. Verify that the OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF document definition is assigned to the host trading partner.

  12. Ensure that the Sender option is enabled.

  13. In the Partner section, click the Add icon.

  14. Enter the name of a remote trading partner.

  15. Select the Internal Identifier Type B2B Trading Partner Code that you previously created and enter the Value for the identifier.

    This is the value that you will enter in the B2B Trading Partner Code field on the customer account profile of this remote trading partner.

  16. Click the Documents tab.

  17. Click the Add icon to associate the OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF document definition with the remote trading partner.

  18. Enable the Receiver option.

  19. Click the Channel tab.

  20. Define a channel for the remote trading partner.

    The channel determines how the XML transaction is delivered to the remote trading partner from B2B: directly; using the Oracle Supplier Network (OSN), or using a third party service.

    If you're communicating using Oracle Supplier Network (OSN), select the Generic Identifier and enter the IP Address for OSN.

  21. Repeat steps 13 to 20 for each remote trading partner.

Configure Agreements

A trading partner agreement defines the terms that enable two trading partners, the sender and the receiver, to exchange business documents. The agreement identifies the trading partners, trading partner identifiers, document definitions and channels.

An agreement consists of two trading partners, the host trading partner and one remote trading partner, and represents one type of business transaction between these partners. For example, if the host trading partner MyCompany and the remote trading partner ABC Solutions regularly exchange both purchase orders and invoices, then two separate agreements are needed for each document definition.

To configure agreements between the host and remote trading partners:

  1. Log in to the Oracle B2B Server.

  2. Navigate to the Partners page.

  3. In the Agreement section, click the Add icon to open a new agreement for the host trading partner MyCompany.

  4. Enter the agreement ID and Name.

  5. Enter the agreement parameters.

  6. Select the Document Definition OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF for this agreement.

  7. Select the remote trading partner to include in this agreement.

  8. Select the channel for the remote trading partner.

  9. Add identifiers for the remote trading partner.

  10. Click Save to save the agreement.

  11. Click Validate to validate the agreement.

  12. Click Deploy to deploy the agreement.

    Deployment is the process of activating an agreement from the design-time repository to the run-time repository.

  13. Repeat steps 3 to 12 for each agreement between the host trading partner and this remote trading partner.