1. Integration Playbooks for SCM
  2. Collaboration Messaging Framework

Collaboration Messaging Framework

Oracle Collaboration Messaging Framework provides native messaging capability for the most widely used B2B messages in Oracle Purchasing, Oracle Fusion Cloud Supply Chain (SCM) & Manufacturing, and Oracle Fusion Cloud Financials.

Applications supporting Collaboration Messaging Framework raise the collaboration event or invoke the Collaboration Messaging Framework send document service to start sending B2B messages to partners.

The framework retrieves the message payload and, depending on the recipient (service provider or trading partner), delivers the payload in the external message format setup for the recipient.

It also receives B2B messages from service providers or partners in external message formats that are translated and delivered to the application by invoking application web services.

B2B messaging is normally handled by third-party service providers or B2B applications. The Collaboration Messaging Framework delivers ready-to-use connectivity with some service providers.

The framework provides the ability to configure what's delivered ready to use, and the ability for customers to create and connect to other B2B service providers, applications, or partners.

Key Features

  • Exchange (send or receive) B2B messages with partners (suppliers or customers).
  • Message sending triggered by application events or scheduled processes.
  • Multiple options for sending messages:
    • Send directly to the partner
    • Send to a B2B service provider (partner or user defined).
    • Deliver to Oracle Universal Content Management (UCM) or an SFTP file location.
    • Trigger an Oracle Integration Cloud (OIC) flow for later enrichment and delivery.
  • Ready-to-use multiple message formats supported. For example, UBL, cXML, OAGIS, and Brazil SEFAZ.
  • Multiple delivery methods for sending messages:
    • SOAP services or REST APIs (REST using Oracle B2B)
    • SFTP
    • UCM
    • AS2 (using Oracle B2B)
    • OIC (B2B Message Business Event)
  • Multiple communication methods for receiving messages:
    • SOAP services
    • REST APIs (using Oracle B2B)
    • UCM folders
    • OIC (B2B Message Business Event)
    • Messages received are delivered to applications through interface tables, file-based data import (FBDI), or directly by calling an application SOAP service or REST API.
  • Configuration supported for handling other data elements; value cross-referencing; and simple validations by changing the provided ready-to-use XSL stylesheets.
  • Support for ready-to-use multiple third-party service providers, with an option for the user to add their own service providers.
  • Support for ready-to-use multiple messaging standards, with an option for users to add their own.
  • Error-handling capabilities, including automatic retry, error notification, and resending messages.
  • Support for a set of ready-to-use documents (for example, Purchase Order Out, Invoice In). For each document, delivers a few external message formats.
  • EDI support using OIC or third-party service providers.

Best Practices

  • All business processes are enabled, ready to use. Disable the ones you're not using.
  • Review the messaging configuration parameters, especially the ones related to message size and attachment handling.
  • If you're using service providers for B2B, don't configure override message definitions for trading partners unless you have specific override requirements for those partners. This isn't common.
  • If you perform a production-to-test, update your delivery method credentials, and verify the external delivery endpoints after the update.

Constraints

Users can implement new message formats for existing documents but can't add new documents.