Extend the Outbound Purchase Order Message for Electronic Communication

You can extend the information contained in purchase order outbound messages used in collaboration messaging. For example, you may require additional information to be sent in the messages to suppliers.

To extend the information in the purchase order outbound message perform these main tasks:

  1. Enable the Extensible Data Model Used for Electronic Messaging profile option.

  2. Extend the Purchase Order Data Model by adding new attributes.

  3. Update the predefined XSL file associated with the message definition that you're modifying to update the message transformation with the new attributes.

  4. Create a new message definition using the updated XSL file. If you're using a predefined message definition you can duplicate it.

  5. Update your trading partner or service provider setup to use the new message definition.

Enable the Profile Option

If the profile option is already enabled, proceed to the section of this topic titled Extend the Data Model. If it is not enabled, you must be assigned the Procurement Application Administrator related privileges or a similarly configured privileges to perform these steps. Here's what you need to do:

  1. In the Setup and Maintenance work area, access the Manage Administrator Profile Values task in the Procurement Foundation functional area.

  2. On the Manage Administrator Profile Values page, search for the Extensible Data Model Used for Electronic Messaging (PO_ELECTRONIC_COMM_DATA_MODEL) profile option.

  3. Set the profile option value to Yes.

Extend the Data Model

Use Oracle Analytics Publisher to extend the Purchase Order Data Model by adding more attributes to the model.

  1. Sign in to Oracle Analytics Publisher as a user with the BI Administrator Role.

  2. From the Catalog, navigate to the delivered Purchase Order Data Model.

    1. In the Folders pane, expand Shared Folders > Procurement > Purchasing > Data Models.

  3. Make a copy of the delivered data model and place it in the Custom folder.

  4. Modify the copy of the data model to include the new attributes.

  5. When you complete the changes to the modified copy of the data model, ensure the Purchase Order PDF Report points to the modified copy for the changes to take effect.

For more information about working with data models and editing data sets, refer to these guides available on the Oracle Help Center:

  • Oracle Fusion Cloud Procurement: Creating and Administering Analytics and Reports for Procurement

  • Oracle Fusion Middleware Data Modeling Guide for Oracle Analytics Publisher

Update the XSL File

Use the Collaboration Messaging work area in Oracle Applications Cloud to modify the XSL file associated with the message definition of the message that you're updating. The XSL file is used for message transformation and the new attributes need to be included.

Refer to the Export The Message Transformation Package section in the Oracle Fusion Cloud SCM: Configuring and Managing B2B Messaging guide for information on how to download the XSL file associated with the message definition for the message that you're modifying.

New Message Definition

Use the Collaboration Messaging work area in Oracle Applications Cloud to duplicate the predefined message to create a new one. Associate the updated XSL file with the new message definition.

Refer to the Collaboration Messages Definition chapter in the Oracle Fusion Cloud SCM: Configuring and Managing B2B Messaging guide for information on how to create or duplicate a message definition.

Update the Service Provider or Trading Partner Setup

In the Collaboration Messaging work area, associate the new message definition with any service providers or trading partners. You can change the status of the existing message that you no longer want to use to Inactive.

Refer to the sections Collaboration Messaging Service Providers and Collaboration Messaging for B2B Trading Partners in the Oracle Fusion Cloud SCM: Configuring and Managing B2B Messaging guide for more information on message setup.