2Collaboration Messaging Framework Setup

This chapter contains the following:

Define Message Processing and Delivery Method Parameters

By default, Collaboration Messaging Framework stores all source and transformed outbound and inbound documents. This facilitates auditing the documents and reprocessing or resending them when required. So you need to configure how to process outbound messages and types of delivery methods:

  1. In the Setup and Maintenance work area, go to the Manage Collaboration Messaging Configuration task.

  2. In the General Setup tab's Trading Partner Search Configuration section, select a Default Service Provider.

    The drop-down list displays a list of pre-defined service providers available in Collaboration Messaging.

    The pre-seeded service provider you select here defaults to the service provider on the Search and Select: Trading Partner ID dialog box, when you use the Manage Supplier B2B Configuration task from the Collaboration Messaging work area to Edit Supplier B2B Configuration.

  3. In the Outbound Message Processing section, specify values for:

    Field Description

    Global Sender ID

    Identifies the sender of all outbound messages.

    Global Sender ID Type

    Type of identifier of the Global Sender ID, for example D-U-N-S.

    Maximum attachment size

    Determines the maximum size of embedded attachments that can be included in a message.

    Note: You can set up only invoice and purchase orders to send attachments. Collaboration Messaging Framework takes into account only the size of the attachments, not the size of the message.

    When Collaboration Messaging Framework doesn't send attachments because they exceed the maximum size, the buyer associated with the purchase order is notified that all attachments weren't sent.

  4. In the Delivery Method Types section, specify a value for Maximum Message Size MB for your Delivery Method Type.

    Here, the maximum value specified refers to the size of the message plus the size of the attachment. Collaboration Messaging Framework doesn't process messages that exceed the maximum size for a delivery method. It logs the status as Error/Failed.

  5. Click Save and Close.

    If you need to stop storing the source and transformed outbound and inbound documents according to your business requirements, disable the options that you do not need in the Message Storage section in the General Setup tab.

    Note that if you disable the Store outbound source document check box, you can't reprocess existing messages.

Set Up a Business Process

You can enable Oracle Fusion Collaboration Messaging Framework for these business processes:

  • Procure to Pay

  • Supply Chain Operations

  • Order to Cash

  • Brazil Electronic Invoicing

    The collaboration business processes are enabled by default and have collaboration documents associated with them. For the collaboration documents, you can configure additional details. For example, you can enable embedding attachments in an XML message for a purchase order outbound message.

    1. In the Setup and Maintenance work area, go to the Manage Collaboration Messaging Configuration task in the Suppliers or Customers functional area, and then to the Business Process Setup tab.

    2. Select a collaboration business process and an associated collaboration document and, in the Configure Collaboration Documents section, click Configure Additional Details.

      Note: If you disable a business process then the application doesn't send or receive outbound and inbound messages

Procure to Pay Documents

Collaboration Messaging Framework supports these documents for the procure to pay process:

Document Type Description Document Configuration Parameters

Process Purchase Order

Process PO outbound

PROCESS_PO_OUT

Embed attachments in the XML message

This parameter determines if the attachments will be embedded in the XML message. If this option isn't selected, the application ignores attachments.

Acknowledge Receipt Advice

Process receipt acknowledgment inbound

ACK_RCV_ADV_IN

N/A

Process Invoice

Process invoice inbound

PROCESS_INVOICE_IN

Retrieve Supplier site from PO

If this parameter is selected, and if the application partner code isn't provided in the payload, the application gets the PO# from the payload and finds the supplier site information from that.

Process Shipment

Process Shipment Inbound

PROCESS_SHIPMENT_IN

Retrieve Supplier site from PO

If this parameter is selected, and if the application partner code isn't provided in the payload, the application gets the PO# from the payload and finds the supplier site information from that.

Change Purchase Order

Change Purchase Order Outbound

CHANGE_PO_OUT

Embed attachments in the XML message

This parameter determines if the attachments will be embedded in the XML message. If this option isn't selected, the application ignores attachments.

Cancel Purchase Order

Cancel Purchase Order Outbound

CANCEL_PO_OUT

Embed attachments in the XML message

This parameter determines if the attachments will be embedded in the XML message. If this option isn't selected, the application ignores attachments.

Acknowledge Change Purchase Order

Acknowledge Change Purchase Order Inbound

ACKNOWLEDGE_CHANGE_PO_IN

N/A

Acknowledge Purchase Order

Acknowledge Purchase Order inbound

ACKNOWLEDGE_PO_IN

N/A

Acknowledge Invoice

Acknowledge Rejected Invoice Outbound

ACK_REJECTED_INVOICE_OUT

N/A

Process Receipt Advice

Process Receipt Advice Outbound

PROCESS_RCV_ADV_OUT

N/A

Supply Chain Operations Documents

Collaboration Messaging Framework supports these documents for supply chain operations:

Document Type Description Document Configuration Parameters

Process Forecast

Process Forecast Outbound

PROCESS_FORECAST_OUT

N/A

Acknowledge Forecast

Acknowledge Forecast Inbound

ACKNOWLEDGE_FORECAST_IN

N/A

Order to Cash Documents

Collaboration Messaging Framework supports these documents for the order to cash process:

Document Type Description Document Configuration Parameters

Process Purchase Order

Process Purchase Order Inbound

PROCESS_PO_IN

Electronic order source system

This parameter identifies where the purchase order originated from.

Document security group

Purchase orders delivered to Oracle Fusion Order Management are delivered as a ZIP file that contains a number of CSV files. The document security group identifies the folder in which the ZIP file gets placed.

Change Purchase Order

Change Purchase Order Inbound

CHANGE_PO_IN

Electronic order source system

This parameter identifies where the purchase order originated from.

Document security group

Purchase orders delivered to Oracle Fusion Order Management are delivered as a ZIP file that contains a number of CSV files. The document security group identifies the folder in which the ZIP file gets placed.

Cancel Purchase

Cancel Purchase Order Inbound

CANCEL_PO_IN

Embed attachments in the XML message

This parameter determines if the attachments will be embedded in the XML message. If this option isn't selected, the application ignores attachments.

Acknowledge Purchase Order

Acknowledge Purchase Order Outbound

ACKNOWLEDGE_PO_OUT

N/A

Acknowledge Change Purchase Order

Acknowledge Change Purchase Outbound

ACKNOWLEDGE_CHANGE_PO_OUT

N/A

Process Shipment

Process Shipment Outbound

PROCESS_SHIPMENT_OUT

N/A

Process Invoice

Process Invoice Outbound

PROCESS_INVOICE_OUT

Number of invoices processed concurrently

This parameter determines how many invoices are processed at the same time to be sent out.

Embed attachments in the XML message

This parameter determines if the attachments will be embedded in the XML message. If this option isn't selected, the application ignores attachments.

Sometimes some outbound messages aren't processed successfully because of resource issues or temporary system unavailability. You can reprocess the messages with such outbound errors automatically. You can define the window of time during which the errors occurred to include in the automatic reprocessing and determine how often the application must attempt to reprocess the outbound messages.

You can automatically reprocess messages with the status of B2B Error or with these error subtypes:

Error Subtype Reason for Error

Application Service Invocation Failure

Collaboration Messaging Framework is unable to call the application service used to retrieve the outbound message payload.

External Service Invocation Failure

Collaboration Messaging Framework is unable to call the trading partner or service provider's service.

Internal Service Issue

Collaboration Messaging Framework is unable to call an internal processing service.

Here's how you enable automatic reprocessing of outbound error messages:

  1. In the Setup and Maintenance work area, use the Manage Collaboration Messaging Configuration task in the Manufacturing and Supply Chain Materials Management offering.

  2. In the General Setup tab, Automatic Message Reprocessing section, select the Enable Reprocessing check box.

  3. Enter a value in the Reprocessing Window in hours to specify the past window of time to include messages that encountered errors.

    The default value is 48 hours.

  4. Enter a value in the Reprocessing Interval in minutes to define the interval at which the messages must be reprocessed.

    The default value is 120 minutes.

  5. Click Save and Close.