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

Sources and targets in inbound flows

Sources and targets in inbound flows

Mapping sources and targets in inbound flows depend on the processing method, two-step processing or single-step processing.
Two-step processing
In two-step processing you use both an inbound mapping and a process-to-backend mapping.
The following table describes the sources and targets of the inbound mapping in two-step processing:
Mapping component
Requirements
Source Connection
B2B EDI Gateway Endpoint
Source Object
get
Target Connection
B2B EDI Gateway
Target Object
CUSTOM_TARGET
The following table describes the sources and targets of the process-to-backend mapping in two-step processing:
Mapping component
Requirements
Source Connection
You can add multiple source connections to the mapping. You can use the following connections in the mapping:
  • B2B EDI Gateway. You must parameterize the connection.
  • Optional connections to other connectors.
    You can use any Informatica connection that isn't a
    B2B Gateway
    connection. Do not parameterize the connections.
    Connecting additional sources to a
    B2B Gateway
    connection or parameterizing them might result in errors at run time.
Source Object
CUSTOM_SOURCE
Target Connection
Any
Target Object
Any
Single-step processing
In single-step processing you use an inbound mapping. The following table describes the sources and targets of the inbound mapping in single-step processing:
Mapping component
Requirements
Source Connection
B2B EDI Gateway Endpoint
Source Object
get
Target Connection
Any
Target Object
Any

0 COMMENTS

We’d like to hear from you!