Receive B2B Messages from Your Trading Partners in Real Time Using a REST API
You can now receive B2B messages directly from your trading partners using the new Generic B2B Message Receiving Service.
- The endpoint for this service is: https://<hostname:port>/fscmRestApi/scm/redwood/11.13.18.05/Genericb2bMessageReceivingService
- This service is secured using basic authentication.
- The username and password that are provided are validated.
- The user must be a valid Oracle Fusion applications user.
- The user must be set up with the privilege required to call the collaboration message service.
The headers that are required for this service are shown below:
Required HTTP Headers
| Header | Description |
|---|---|
|
SenderID |
This is the ID of the party that is sending the B2B message and the trading partner ID, that is, ABC Company. |
|
SenderIDType |
This is the type of ID of the party that is sending the B2B message and the trading partner ID type, that is, Name. |
|
Document |
This is the type of document that is being sent, that is, ProcessPurchaseOrder. |
|
Content-Type |
Specifies the type of content being sent to the server. The valid value is application/xml. |
The optional headers for this service are shown below:
Optional HTTP Headers
| Header | Description |
|---|---|
|
Prefer |
If the Prefer header is specified with the value respond-async, the service will process the request asynchronously, which generally offers better performance compared to synchronous processing. If the Prefer header is not included, the response will be handled synchronously. Using the Prefer request header to set the service to asynchronous mode can lead to improved performance and efficiency. |
|
AgentID |
This is the service provider ID if a service provider is used to send B2B messages, that is, XYZ Service Provider. |
|
AgentIDType |
This is the type of service provider ID if a service provider is used to send B2B messages, that is, Name. |
In addition to the existing SOAP API, the new REST API processes B2B messages directly, thereby offering a simple and alternative way to receive B2B documents via Oracle Collaboration Messaging Framework.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Refer to the Configuring and Managing B2B Messaging for Oracle Fusion Cloud SCM guide on the Oracle Help Center.
Access Requirements
Users who are assigned a configured job role that contains this privilege can access this feature:
- Invoke Collaboration Message Inbound Service (CMK_INVOKE_INBOUND_COLLAB_DOC_SERVICE_PRIV).
This privilege was available prior to this update.