Table of Contents

Search

  1. Preface
  2. Introducing B2B Gateway
  3. B2B Gateway administration
  4. Project and asset management
  5. EDI X12 and EDIFACT Messages
  6. Custom files with custom mappings
  7. Inbound Custom Files with Intelligent Structure Discovery
  8. File transfer tasks
  9. Partners
  10. Tracking and Monitoring Events
  11. B2B Gateway REST APIs
  12. Glossary

B2B Gateway

B2B Gateway

Rules and guidelines for outbound flows

Rules and guidelines for outbound flows

The following rules and guidelines apply to custom mappings that you use in outbound flows:
  • To convert relational data to the
    B2B Gateway
    XML interface file in the outbound flow,
    define custom backend processing mappings to extract and process the data to send to the partner from the backend system to an interface file on the
    B2B Gateway
    document store. You can define a single process-from-backend mapping to process all the messages to the interface file, a mapping for each type of file that you want to process, or both mapping types. When an outbound process runs,
    B2B Gateway
    first runs the process-from-backend mappings that are defined for specific message types, and then it runs the process-from-backend mapping that is defined for the outbound flow of the partner.
    You add Hierarchy Builder transformations to the mappings.
  • Do not parameterize the source connection.
    Parameterizing the source connection might result in errors at run time.
  • The targets of the mapping must be the B2B EDI Gateway connection. You must parameterize the target connections.
  • If you assign process-from-backend mappings to specific message types you must also create a message discovery mapping and assign it to the outbound flow of the partner.
  • If you define multiple interchange IDs of the same type for a partner, you must pass the interchange ID to use in outbound flows as a parameter in the process-from-backend mapping that you assign to the partner, so that
    B2B Gateway
    can determine which partner interchange ID to use in outbound flows. You add the ID to the source that contains the message details and map it to the appropriate field in the mapping target.
    For more information, see Partner interchange IDs
  • If you add parameters to the process-from-backend mapping, you can configure the parameter values when you create the partner flow, after you select the mapping. You can also pass the parameter values with the Run Partner REST API. When you run the partner with the API, the values that you define in the API override those that you define in the partner flow. For more information, see Run Partner REST API.

0 COMMENTS

We’d like to hear from you!