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

Creating a process-to-backend mapping for inbound EDI message flows

Creating a process-to-backend mapping for inbound EDI message flows

Create a process-to-backend mapping that processes incoming EDI messages in
Data Integration
.
A mapping can process a single message type or multiple message types. When you create a partner, you can select a mapping that contains a single message type when you add the message type for the partner. You can select a mapping that includes multiple message types when you define the inbound flow for the partner.
When you create a mapping you define the
B2B Gateway
document store as the source, add a filter for each message type in the mapping, add and configure a Hierarchy Parser transformation for each message type, and, for each message type, add the relevant backend systems as targets.
To define
B2B Gateway
as a source, you select the B2B EDI Gateway connection. You must parameterize the connection.
Optionally, you can add sources that connect to locations other than the document store.
You can use any Informatica connection that isn't a
B2B Gateway
connection. Do not parameterize the connections.
Parameterizing connections other than
B2B Gateway
connections might result in errors at run time.
After you add all the required elements to the mapping save and validate the mapping.

0 COMMENTS

We’d like to hear from you!