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

General rules and guidelines

General rules and guidelines

The following rules and guidelines apply to both inbound and outbound flows:
  • You can create the mappings after your organization is set up in
    Data Integration
    and
    B2B Gateway
    connections are available for selection when you create the mapping.
    When you set up the organization in
    B2B Gateway
    ,
    B2B Gateway
    creates the connections
    B2B EDI Gateway
    ,
    B2B EDI Gateway Endpoint
    , and
    B2B Gateway Document Store
    in the
    Informatica Intelligent Cloud Services
    organization. Do not rename or edit these connections. Editing a connection or changing a connection name might result in errors at run time.
  • Define each message type in one mapping only. If you define the same message type in both a message-specific backend processing mapping and in the flow's backend processing mapping,
    B2B Gateway
    might run messages of that message type twice. For example, if you define a process-from-backend mapping for the
    810 Invoice
    message type for a customer, and
    810 Invoice
    is also defined in the process-from-backend mapping that is defined for the outbound flow of the customer,
    B2B Gateway
    might run
    810 Invoice
    messages twice.

0 COMMENTS

We’d like to hear from you!