Set Up a Business Process
You enable Oracle Fusion Collaboration Messaging Framework for business processes.
The business processes are:
-
Procure to Pay
-
Supplier Collaboration
-
Customer Collaboration
-
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.
-
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.
-
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 |
Supports Attachment |
Document Type |
Configuration Parameters |
|---|---|---|---|
|
Purchase Order - Outbound |
Yes |
Process Purchase Order |
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. Sender Email Enter the sender's email address for all outbound B2B messages for the
selected document.
Note: If you don’t make an entry, the application-generated email address
is used by default. |
|
Receipt Confirmation - Inbound |
No |
Acknowledge Receipt Advice |
N/A |
|
Invoice - Inbound |
Yes |
Process Invoice |
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. |
|
Advance Ship Notice - Inbound |
No |
Process Shipment |
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. |
|
Purchase Order Change - Outbound |
Yes |
Change Purchase Order |
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. Sender Email Enter the sender's email address for all outbound B2B messages for the
selected document.
Note: If you don’t make an entry, the application-generated email address
is used by default. |
|
Purchase Order Cancellation - Outbound |
Yes |
Cancel Purchase Order |
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. Sender Email Enter the sender's email address for all outbound B2B messages for the
selected document.
Note: If you don’t make an entry, the application-generated email address
is used by default. |
|
Purchase Order Acknowledgment Change - Inbound |
No |
Acknowledge Change Purchase Order |
N/A |
|
Purchase Order Acknowledgment - Inbound |
No |
Acknowledge Purchase Order |
N/A |
|
Invoice Acknowledgment - Outbound |
No |
Acknowledge Invoice |
N/A |
|
Receipt Advice - Outbound |
No |
Process Receipt Advice |
Sender Email Enter the sender's email address for all outbound B2B messages for the
selected document.
Note: If you don’t make an entry, the application-generated email address
is used by default. |
|
Credit Note - Inbound |
Yes |
Credit Note |
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. |
Supplier Collaboration Documents
Collaboration Messaging Framework supports these documents for supplier collaboration:
|
Document |
Supports Attachments |
Document Type |
Configuration Parameters |
|---|---|---|---|
|
Order Forecast - Outbound |
No |
Process Forecast |
Sender Email Enter the sender's email address for all outbound B2B messages for the
selected document.
Note: If you don’t make an entry, the application-generated email address
is used by default. |
|
Order Forecast Commit - Inbound |
No |
Acknowledge Forecast |
N/A |
|
Supply Planning Data - Inbound |
No |
Supply Planning Data |
N/A |
Customer Collaboration Documents
Collaboration Messaging Framework supports these documents for customer collaboration:
|
Document |
Supports Attachments |
Document Type |
Configuration Parameters |
|---|---|---|---|
|
Order Forecast - Inbound |
No |
Process Forecast |
N/A |
Order to Cash Documents
Collaboration Messaging Framework supports these documents for the order to cash process:
|
Document |
Supports Attachments |
Document Type |
Configuration Parameters |
|---|---|---|---|
|
Purchase Order - Inbound |
No |
Process Purchase Order |
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. Initiate Load Interface File for Import process on receipt of orders If you select this parameter, the scheduled process is submitted on receipt of purchase orders. |
|
Purchase Order Change - Inbound |
No |
Change Purchase Order |
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. Initiate Load Interface File for Import process on receipt of orders If you select this parameter, the scheduled process is submitted on receipt of purchase orders. |
|
Purchase Order Cancellation - Inbound |
No |
Cancel Purchase |
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. Initiate Load Interface File for Import process on receipt of orders If you select this parameter, the scheduled process is submitted on receipt of purchase orders. |
|
Purchase Order Acknowledgment - Outbound |
No |
Acknowledge Purchase Order |
Sender Email Enter the sender's email address for all outbound B2B messages for the
selected document.
Note: If you don’t make an entry, the application-generated email address
is used by default. |
|
Purchase Order Change Acknowledgment - Outbound |
No |
Acknowledge Change Purchase Order |
Sender Email Enter the sender's email address for all outbound B2B messages for the
selected document.
Note: If you don’t make an entry, the application-generated email address
is used by default. |
|
Advance Ship Notice - Outbound |
Process Shipment |
Sender Email Enter the sender's email address for all outbound B2B messages for the
selected document.
Note: If you don’t make an entry, the application-generated email address
is used by default. |
|
|
Invoice - Outbound |
Yes |
Process Invoice |
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. Sender Email Enter the sender's email address for all outbound B2B messages for the
selected document.
Note: If you don’t make an entry, the application-generated email address
is used by default. |
|
Invoice Acknowledgment - Inbound |
No |
Acknowledge Invoice |