13Collaboration Messaging

This chapter contains the following:

Use Oracle Fusion Collaboration Messaging Framework to enable Oracle Applications Cloud establish business-to-business (B2B) messaging capabilities with trading partners.

Using this framework, you can send and receive real-time transactional messages without building new SOA components. You can use the existing B2B functionality to exchange messages with collaborators such as suppliers either directly or using an intermediary agency such as a B2B Service Provider.

The framework supports transformation of a B2B document, such as a purchase order, between the Oracle Applications Cloud format and an external message format supported by the trading partner. When you send messages to partners or receive messages from them, the framework performs the required transformation.

The following figure illustrates how Collaboration Messaging Framework delivers a message to the intended recipient.

A representation of the Collaboration Messaging
Framework functionality.

Using collaboration messaging involves performing the following high-level tasks:

  • Setting up external (B2B) trading partners and their messaging capabilities.

  • Cross-referencing the Oracle Applications Cloud definition of a trading partner (such as a supplier) with the external trading partner definition setup earlier. Also, selecting the messages that must be enabled with the partner.

  • Configuring the message delivery method for the partner.

To open the Collaboration Messaging Framework Overview page, click the Navigator menu and select Collaboration Messaging.

Use the Collaboration Messaging Framework Overview page to:

  • Manage undelivered collaboration messages

  • Reprocess failed collaboration messages

  • Manage collaboration messaging history

  • Validate inbound and outbound collaboration messaging setup

Collaboration Messaging Configuration

Set Up Outbound Message Processing and Delivery Methods

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 in the Suppliers or Customers functional areas.

  2. In the General Setup tab's Outbound Message Processing section, specify values for:

    Field Description

    Global Sender ID

    Identifies the sender of all outbound messages

    Global Sender ID Type

    The type of identifier of the sender in a message

    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 does not send attachments because they exceed the maximum size, the buyer associated with the purchase order is notified that all attachments were not sent.

  3. 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 does not process messages that exceed the maximum size for a delivery method. It logs the status as Error/Failed.

  4. 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 cannot 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 does not send or receive outbound and inbound messages

Any inbound or outbound message that isn't processed because of some error, remains undelivered. You can view the undelivered messages on the Collaboration Messaging Framework Overview page. For each undelivered message, you can diagnose the errors, take corrective action, and resubmit a request to deliver it again.

To reprocess an undelivered messages:

  1. On the Collaboration Messaging Framework Overview page, click the tasks icon to view the tasks, and select the Manage Undelivered Collaboration Messages task.

  2. On the Manage Undelivered Collaboration Messages page, search for the undelivered message. The message is listed in a table.

  3. Click the message row to view the reason for delivery failure. The details appear in Processing History.

    Tip: Click the message ID link to view the setup details of the message.
  4. Take the required corrective action and return to the Collaboration Messaging Framework Overview page.

  5. Select the specific message and click Reprocess. If there are no further problems, the message is submitted for delivery.

Inbound Collaboration Messages

After you set up an application partner, such as a supplier site, you can send a test inbound message to verify if the setup is appropriate for messaging. Use the Validate Inbound Collaboration Messaging Setup task on the Collaboration Messaging Overview page to validate an inbound message.

All messages that go through the validation process queue up and appear on the Collaboration Messaging History page. There you can examine the details of each processed message to check if it was transformed and processed as intended.

  1. On the Overview page, click the tasks icon to view the tasks, and select the Validate Inbound Collaboration Messaging Setup task.

  2. Select the service provider and the partner ID from whom you expect to receive the collaboration message.

  3. Click Next.

  4. On the Validate Inbound Collaboration Messaging Setup page, enter the required details.

    For Processing Service, if your external message standard is OAGIS, select any processing service from the drop-down list per your requirement. If the standard is not OAGIS, select CollaborationMessageV2.Process or CollaborationMessageV2.ProcessAsync per your requirement.

  5. Click Next.

  6. Click Create Message Payload. The message payload is generated in XML format and appears in the text box.

  7. Update the generated payload or replace it with the XML payload that you want to test.

  8. Examine the elements of the message payload. The following table contains an example of the mapping between the elements and actual data for OAGIS messages.

    XML Element Corresponding Information

    <Sender>

    The ID of the partner who sent the document.

    <Intermediary>

    Contains the ID of the service provider.

    <Receiver>

    Contains the ID of the recipient.

    <BODID>

    An ID that the sender assigns to the message.

  9. Click Process. A confirmation message appears. Click Next.

  10. The Collaboration Message page appears. Click Refresh, if the required.

  11. Click Done.

To view the processed message again, search for it on the Manage Collaboration Messaging History page. In the search results, click the generated message ID to view its details.

Outbound Collaboration Messages

After you set up an application partner, such as a supplier site, you can send a test outbound message to verify if the setup is appropriate for messaging. Use the Validate Outbound Collaboration Messaging Setup task on the Collaboration Messaging Framework Overview page to validate an outbound collaboration message.

All messages that go through the validation process queue up and appear on the Collaboration Messaging History page. There you can examine the details of each processed message to check if it was transformed and processed as intended.

  1. On the Collaboration Messaging Framework Overview page, click the tasks icon to view the tasks, and select the Validate Outbound Collaboration Messaging Setup task.

  2. On the Validate Outbound Collaboration Messaging Setup page, select the relevant document. The related details appear.

  3. Select the supplier. The related details, such as the supplier site and service provider appear.

  4. Click Create Message Payload. The message payload is generated in XML format and appears in the text box.

  5. Update the generated payload or replace it with the XML payload that you want to test.

  6. Click Process. The generated message ID appears on the page.

  7. Click View Collaboration Message to view the processed message.

  8. Click Done.

To view the processed message again, search for it on the Manage Collaboration Messaging History page. In the search results, click the message ID to view its details.

Tip: If the message processing fails, you can view the reason for it on the Manage Failed Collaboration Messages page.

Collaboration Messaging Setup

To configure a message for a predefined service provider, do the following:

  1. Open the Manage Collaboration Messaging Service Providers page and search for a predefined service provider.

  2. Click Actions > Edit.

  3. On the Edit Collaboration Messaging Service Provider page, do one of the following:

    • On the Outbound Collaboration Messages tab, click Duplicate Outbound Collaboration Message.

    • On the Inbound Collaboration Messages tab, click Duplicate Inbound Collaboration Message.

  4. Change the status of the pre-seeded message to Inactive so that you can make active or loopback the duplicate message.

  5. Change the duplicate message's status to Active or Loopback, based on business rule.

  6. Click Save and Close.

  7. Click the Manage B2B Trading Partners task.

  8. Create or edit a trading partner.

  9. Set up the document corresponding to the pre-seeded message that you duplicated.

  10. Click the Manage Customer Collaboration Configuration or the Manage Supplier Collaboration Configuration task.

  11. Search for the relevant customer or supplier and associate the service provider with your trading partner.

  12. Associate the document with your customer or supplier.

  13. Validate the configuration.

After validating the configuration, go to Manage Collaboration Messaging History > Configuration > Transformation and confirm that User Defined is selected in Collaboration Definition in the Transformation section.

A service provider is an intermediary for exchanging messages between Oracle Applications Cloud and trading partner. Whenever you set up a trading partner, you can link it with a service provider.

Note: You must be signed in as a supplier and must have access to the Supplier task.
  1. In the Procurement work area, go to Suppliers.

  2. On the Supplier Overview page, navigate to the Supplier Business Classifications section and click the supplier.

  3. On the Edit Supplier page, switch to the Sites tab and click the required site.

  4. On the Edit Site page, select Collaboration Messaging Framework as the channel for B2B Communication.

  5. In Associated Collaboration Documents, click Manage Trading Partners.

  6. On the Manage Trading Partners dialog box, click Create > Create Trading Partner with Service Provider.

  7. On the Create Trading Partner dialog box, fill the required details.

  8. Click Actions > Add Row and fill the details to associate collaboration documents with the trading partner. You may add multiple documents.

    Note: To enable exchange of messages, you must set the collaboration document status to Active.
  9. Click Save and Close.

  10. On the Manage Trading Partners dialog box, click OK.

  11. On the Edit Site page, click Save and Close.

  12. On the Edit Supplier page, click Save and Close.

To update the details for a trading partner, use the edit option on the Manage Trading Partners dialog box.

You can exchange messages with a trading partner directly, without using a service provider.

Note: You must be signed in as a supplier and must have access to the Supplier task.
  1. On the Supplier Overview page, navigate to the Supplier Business Classifications section and click the supplier.

  2. On the Edit Supplier page, switch to the Sites tab and click the required site.

  3. On the Edit Site page, select Collaboration Messaging Framework as the channel for B2B Communication.

  4. In Associated Collaboration Documents, click Manage Trading Partners.

  5. On the Manage Trading Partners dialog box, click Create > Create Trading Partner without Service Provider.

  6. On the Create Trading Partner dialog box, fill the required details.

    Note: By default, the Service Provider is set to None because this setup doesn't involve a service provider.
  7. Click Actions > Add Row and fill the delivery method, outbound collaboration message, and inbound collaboration message details on the respective tabs.

    Note: The following table contains some tips on filling the important information on each tab.
    Tab Details

    Delivery Methods

    • Provide the endpoint URL and the associated authentication credentials to initiate the collaboration messaging web service. It must be in the format http://<server>:<port>/<context>, where <context> contains the name of the web service as defined in the application.

    Outbound Collaboration Messages

    • Specify a unique name and select the collaboration message. The associated details automatically appear in the row.

    • Select a delivery method.

    • Set the outbound collaboration document status to Active or Loopback.

    Inbound Collaboration Messages

    • Specify a unique name and select the collaboration message. The associated details automatically appear in the row.

    • Specify an XPath that identifies the application partner in the inbound collaboration document.

    • Set the inbound collaboration document status to Active or Loopback.

  8. Click Save and Close.

  9. On the Manage Trading Partners dialog box, click OK.

  10. On the Edit Site page, click Save and Close.

  11. On the Edit Supplier page, click Save and Close.

To update the details for a trading partner, use the edit option on the Manage Trading Partners dialog box.

To set up collaboration messaging, you must associate the supplier site with a trading partner, and select the documents you want to exchange with that partner. The documents that you set up here are associated with trading partners or the service providers of those trading partners.

Note: You must be signed in as a supplier and must have access to the Supplier task.
  1. On the Supplier Overview page, navigate to the Supplier Business Classifications section and click the supplier link.

  2. On the Edit Supplier page, switch to the Sites tab and click the required site.

  3. On the Edit Site page, select Collaboration Messaging Framework as the channel for B2B Communication.

  4. In Associated Collaboration Documents, click Edit.

  5. On the Edit Associated Collaboration Documents dialog box, click Add Row and fill the details required to set up the document. The read-only particulars appear based on the selected details.

  6. Click Save and repeat the steps to add more documents or click Save and Close to return to the previous page.

  7. On the Edit Site page, click Save and Close.

  8. On the Edit Supplier page, click Save and Close.

Overview of Importing Collaboration Messaging Setup Data

You can migrate your Oracle B2B setup data and update Oracle Fusion application setup in these scenarios:

  • Data of Oracle Supplier Network Trading Partners

  • Data of non-Oracle Supplier Network Trading Partners (a single trading partner, set up with many B2B Supplier site codes)

  • Data of non-Oracle Supplier Network Trading Partners (many trading partners, each with a single B2B Supplier site code)

To migrate the data you have to first export your B2B configuration data using the B2B export feature, which creates a compressed file that contains all the B2B set up data, and upload the file into the scm$/B2BConfigurationImport$/import$ account.

Then you need to use two scheduled processes to create a collaboration messaging setup data import file and then import the collaboration messaging setup data. And then you need to review the imported data using the Manage Collaboration Messaging Setup Data Import task.

Create a Collaboration Messaging Setup Data File

After you export your B2B set up data from B2B and upload it to the scm$/B2BConfigurationImport$/import$ account, run the Create Collaboration Messaging Setup Data File process.

  1. Go to Tools > Scheduled Processes.

  2. Click Actions > Schedule New Process.

  3. Search for Create Collaboration Messaging Setup Data File and click OK.

  4. Specify these parameters:

    • B2B Configuration ZIP file: The file that you uploaded to the scm$/B2BConfigurationImport$/import$ account

    • Import Type: Oracle Supplier Network B2B Setup or Other B2B Setup

    Import Type Import Data Extracted

    Oracle Supplier Network B2B Setup

    • Trading partners that have the Oracle Supplier Network Test or Production URL set up with an HTTP Delivery Channel.

    • Trading partners with a single ID, with ID Type of B2B Supplier Site Code.

    • Trading Partner Agreements for trading partners that use one of the pre-seeded (V1 implementation) OAG 7.2.1 document definitions.

    Other B2B Setup

    • Trading partners that have an HTTP Delivery Channel with a non-Oracle Supplier Network Test or Production URL.

    • Trading partner with a single ID or multiple IDs with ID Type of B2B Supplier Site Code.

    • Trading Partner Agreements for trading partners that use one of the pre-seeded (V1 implementation) OAG 7.2.1 document definitions.

  5. Click Submit.

The scheduled process extracts the setup data and creates two CSV files into the scm$/B2BConfigurationImport$/import$ account (which is the same account to which you uploaded the B2B export file). The CmkConfigImportPartners.csv file contains all the trading partner information that is extracted from the B2B export file and the CmkConfigImportDocs.csv file contains all the documents that are set up for that trading partner.

The records of the CmkConfigImportPartners.csv file are described in this table:

Column Title Description Required During Import

ImportPartnerId

Not used during import.

N

ImportBatchId

A unique batch ID.

Y

ImportPartnerLineNum

A unique line number.

Y

ImportType

Not used during import.

N

PartnerId

Trading Partner ID. For B2B export, this is the trading partner name set up in B2B.

Y

IdType

ID Type. For B2B export, the ID Type is Name.

Y

OsnPartnerId

This is the RECEIVER_ID set up in the HTTP channel for Oracle Supplier Network trading partners. If a value is found, it is used as the Trading Partner ID (this value overrides the Trading Partner ID value). Required only for Oracle Supplier Network migration, that is, if partnerkeytype is B2B Supplier Site Code.

Optional

OsnPartnerIdType

This is the RECEIVER_ID_TYPE set up in the HTTP channel for Oracle Supplier Network trading partners. If a value is found, it is used as the Trading Partner ID Type (this value overrides the Trading Partner ID Type value).

Optional

ServiceProviderName

The service provider name to be associated with the trading partner. This service provider must exist in Collaboration Messaging Framework.

Y

processedStatus

Not used during import.

N

ExtPartnerStatus

Not used during import.

N

ExtPartnerFailReason

Not used during import.

N

PartnerKeyType

For importing trading partners to be associated to supplier sites, and for the B2B Migration import, this is to be set as B2B Supplier Site Code.

For manual import this may be set to Supplier Site and, in that case, PartnerKey1, PartnerKey2, and PartnerKey3 are all required and need to be populated as outlined.

Y

PartnerKey1

For importing trading partners to be associated to supplier sites, and for the B2B migration import, this is to be set as the value of the B2B Supplier Site Code as specified in the B2B trading partner setup and the Oracle Fusion supplier site record.

For manual import if the PartnerKeyType is set to Supplier Site, this is required and will be set to Supplier Name

Y

PartnerKey2

For manual import if the PartnerKeyType is set to Supplier Site, this is required and will be set to Supplier Site Name.

N

PartnerKey3

For manual import if the PartnerKeyType is set to Supplier Site, this is required and will be set to Procurement Business Unit Name.

N

partnerKey4

Not used during import.

N

PartnerKey5

Not used during import.

N

PartnerKey6

Not used during import.

N

AppPartnerStatus

Not used during import.

N

AppPartnerFailReason

Not used during import.

N

ApplPartnerId

Not used during import.

N

ExternalPartnerId

Not used during import.

N

importDateTime

Not used during import.

N

CreatedBy

Not used during import.

N

CreationDate

Not used during import.

N

LastUpdatedBy

Not used during import.

N

LastUpdateDate

Not used during import.

N

LastUpdateLogin

Not used during import.

N

ObjectVersionNumber

Not used during import

N

The records of the CmkConfigImportDocs.csv file are described in this table:

Column Title Description Required During Import

ImportDocId

Not used during import.

N

ImportPartnerId

Not used during import.

N

ImportBatchId

Key reference to an import batch.

Y

ImportPartnerLineNum

Key reference to a trading partner.

Y

PartnerId

Partner ID.

Y

IdType

Partner ID Type

Y

MessagingStandard

Not used during import.

N

Version

Not used during import.

N

MessageType

Not used during import.

N

MessageSubtype

Not used during import.

N

DocumentName

A collaboration document name. There must be a message definition set up for the service provider for this collaboration document. The possible list of values depend on what is set up for the service provider.

Y

Direction

Direction of the message (In/Out).

Y

ChannelEndpoint

This is not used by the import. It is populated by the Create Collaboration Messaging Setup Data scheduled process if there is an HTTP channel associated with the trading partner agreement. This is informational only, intended for the user to verify if the documents and trading partners extracted by the scheduled process from the B2B ZIP file are accurate and valid for import.

N

BusinessProcess

Not used during import.

N

ImportDelMethodId

Not used during import.

N

DeliveryMethodName

Not used during import.

N

ExtPartnerDocStatus

Not used during import.

N

ExtPtnrDocFailReason

Not used during import.

N

AppPartnerDocStatus

Possible values are Enabled, Disabled, Hold. This is used to set the status of the application partner document, that is, whether the B2B document for the supplier site is enabled for processing after import. If no value is specified, or the value is not one of the listed values, it is set to Enabled.

Optional

AppPtnrDocFailReason

Not used during import.

N

ApplPartnerDocId

Not used during import.

N

ExternalPtnrDocId

Not used during import.

N

PartnerMessageId

Not used during import.

N

CreatedBy

Not used during import.

N

CreationDate

Not used during import.

N

LastUpdatedBy

Not used during import.

N

LastUpdateDate

Not used during import.

N

LastUpdateLogin

Not used during import.

N

ObjectVersionNumber

Not used during import.

N

Import Collaboration Messaging Setup Data

After you create the import file you need to import it using the Import Collaboration Messaging Setup Data scheduled process.

  1. Go to Tools > Scheduled Processes.

  2. Click Actions > Schedule New Process.

  3. Search for Import Collaboration Messaging Setup Data and click OK.

  4. Select Import Type as Import to CMK.

    Import Type Action

    Import to CMK

    Uploads the setup data to the staging table, validates the import, and creates the valid records in Collaboration Messaging Framework setup tables.

    Validate Only

    Uploads the setup data to the staging table and validates the import. No further processing is done.

  5. Select the CSV Configuration ZIP File that you created using the Create Collaboration Messaging Setup Data File scheduled process.

  6. For Oracle Supplier Network data import, enter User Name and Password for the Oracle Supplier Network buyer account.

  7. Click Submit.

    The records created by the process have a Batch ID stamped on them.

Manage Collaboration Messaging Setup Data Import

After you import your collaboration messaging setup data, you can review the imported data.

  1. Go to the Collaboration Messaging Framework work area and click Manage Collaboration Messaging Setup Data Import from the Tasks pane.

  2. Search for the imported data. You can:

    • Select a row in the Trading Partners section and click Actions > Export to Excel.

    • Select a row in the Documents section and click View > About This Record.

      The search results include:

      • Reasons for any import failure

      • Status of the import of trading partners: Success, Invalid, or Skipped

      • Reason for any failure of associating the supplier ID with the trading partner

      • Status of association of the supplier with the trading partner: Success, Error, or Invalid

  3. Click Done.

Undo Import

After reviewing the data, you might sometimes need to undo the import of the setup data that you created using the Create Collaboration Messaging Setup Data scheduled process, for example, if duplicate application partner records are created, you can delete them. Here's what you can do:

  1. In the Collaboration Messaging Framework work area, click Manage Collaboration Messaging Setup Data Import in the Tasks panel.

  2. In the Trading Partners section, click Actions > Undo Import.

  3. Select the Batch ID and click OK.

If multiple batches are imported, you can delete the setup data created by each batch. Delete the latest batch that was imported, followed by the previous one, and so on.

Using this task, you can associate a customer account with an existing trading partner and select the collaboration messaging documents to be exchanged with the customer.

To configure collaboration messaging for a customer:

  1. On the Collaboration Messaging Overview page, click the Tasks icon, and select the Manage Customer Collaboration Configuration task.

  2. Search for the customer account, select the row, and click Edit Collaboration Configuration.

  3. In Associated Service Providers, click Actions - Add Row and fill the details of the service provider and the trading partner.

  4. Click Actions - Add Row and select at least one collaboration document.

  5. Set the Association Status to Active to enable messaging with the selected service provider.

  6. Click Save and Close.

You can specify a location code for the address of each of your customer sites. The code is used to identify the address of the ship-to and bill-to location for inbound order processing.

  1. In the Collaboration Messaging Framework work area, click Manage Customer Collaboration Configuration in the Tasks panel.

  2. Search for your customer.

  3. Select the row for the customer and click Manage B2B Location Codes.

    You see a list of sites that are already set up with location codes for your customer.

  4. Click Add Locations for specifying other sites.

    You see a list of sites that are not set up with location codes for your customer.

  5. Select a site and click Add.

  6. In the B2B Location Code field, enter text to uniquely identify your customer site.

  7. Click Save and Close.

If you need to edit a location code for a site, delete the row for the relevant customer site and location code and then add it again with a new value for the location code.

Using this task, you can configure a customer account to setup delivery of XML payload for the outbound messages and receive confirmation for the inbound messages.

To configure collaboration messaging for a customer account:

  1. On the Collaboration Messaging Overview page, click the Tasks icon, and select the Manage Customer Account Collaboration Configuration task.

  2. Search for the business process, select the customer account row, and click Edit Collaboration Configuration.

  3. In Associated Service Providers, click Actions - Add Row and fill the details of the service provider and the trading partner.

  4. In Collaboration Documents for Service Provider, click Actions - Add Row and select at least one collaboration document.

    Note: To select a collaboration document for the service provider, the associated trading partner must have either process invoice outbound document or confirm message receipt inbound document configured.
  5. Set the Association Status to Active to enable messaging with the selected service provider.

  6. Click Save and Close.

Sending an Outbound Message to Multiple Trading Partners: Procedure

To send an outbound message to multiple trading partners, that is, suppliers or service providers, you must associate the trading partners with the outbound message and ensure that only one of them is the primary recipient of the message. Do the following:

  1. On the Collaboration Messaging Overview page, click the Tasks icon, and then click one of the following:

    • Manage Customer Collaboration Configuration

    • Manage Supplier Collaboration Configuration

    • Manage Customer Account Collaboration Configuration

  2. Enter the required values and click Search.

  3. From the search results, select a customer or supplier and click Edit Collaboration Configuration.

  4. On the page that opens, using the Edit Associated Collaboration Documents dialog box, set up multiple associated service providers and associate the relevant document with the service providers.

  5. Select the service provider that you want as the primary recipient and then in the Collaboration Documents for Service Provider section, select the Primary Recipient check box.

  6. Click Save and Close.

  7. Validate the configuration.

The OAGIS XML B2B message can be delivered as an email attachment to your trading partners. Using this task, you can configure the subject and body of the email.

To configure email properties for an outbound message:

  1. In the Collaboration Messaging Overview work area, click Manage Collaboration Message Definitions in the Tasks panel.

  2. Search for the outbound messages, select the collaboration message row, and click Actions > Configure Email Properties.

  3. On the Configure Email Properties dialog box, fill the required details. such as the default text for the subject line, the XPath that identifies the email ID of the recipient, and the header and column titles in the email body.

    Note: The email body content can be configured to have only header, only column table, or both header and column table.

    The following figure is a sample email format.

    A sample email format.
  4. Click Save and Close.

Manage Pending Inventory Balances

Pending transactions are the result of transactions not yet executed or transactions that have resulted in an error.

You can update pending cycle count, physical count, and material status transactions by running the Manage Inventory Balances process.

For pending transactions:

  1. In the Scheduled Processes work area, select Schedule New Process.

  2. Search for and select the Manage Inventory Balances process.

  3. Click OK.

  4. In the Process Details dialog box, enter your process details.

  5. Click Submit.

For transactions with errors:

  1. In the Inventory Management work area, click the Manage Inventory Balance Messages in Spreadsheet task.

  2. Edit the errors.

  3. Upload the data.

Note: You need a Microsoft Excel add-in to do this task. From the Navigator, click Download Desktop Integration Installer to install the add-in.

FAQs for Collaboration Messaging

The following table describes the main differences among the various error statuses.

Error B2B Error Hold

Indicates that the messages haven't been delivered because of a validation, configuration, or processing error in Collaboration Messaging Framework.

Indicates that the B2B component of the SOA suite couldn't deliver the message because of a configuration or processing error.

Indicates that messages haven't been processed because an administrator has put them on hold.

The following table describes the main differences among the message error types.

Document Retrieval Error Inbound Processing Error Outbound Processing Error

Occurs when the collaboration messaging framework fails to retrieve the document associated with a collaboration event.

Occurs when the collaboration messaging framework can't process inbound messages because of setup or business rule validation issues.

Occurs when the collaboration messaging framework can't process outbound messages because of setup or business rule validation issues.

If you don't enable a document type for storage, the message processing and delivery details of such documents aren't stored in the log table.

To know the cause of a message failure, search for the failed message on the Manage Failed Collaboration Messages page.

When you click the message row, the cause of the failure appears in Processing History.

To the see the list of setup data, you must first run the scheduled process to import the data into the staging tables.

After Collaboration Messaging Framework delivers an outbound message and sets the status to Success or Sent, the processing may fail further in the business flow. In such cases, you can resubmit the message from Collaboration Messaging Framework.

You can attach a user-defined XSLT file only to user-defined messages. To create a user-defined message, duplicate a predefined message.

The actions you can perform for the selected messages depend on the message status. For example, if you select messages with Success and Error status, you can't perform any action.

Based on the message status, you can:

  • Resubmit messages with Success or Sent status

  • Reprocess messages with Failed status

  • Cancel messages with Error or B2B Error status

  • Delete messages with Success, Sent, Failed, or Canceled status

You can view the logs on the Message History page.

Go to the Manage Collaboration Message Definitions page, search for a user-defined message, and then click Export Transformation Package.