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 partner for EDI and EDIFACT messages

Creating a partner for EDI and EDIFACT messages

Create a customer in the
New Customer
wizard, or create a supplier in the
New Supplier
wizard.
  1. Click
    New
    and select
    Partners
    Customer
    or
    Partners
    Supplier
    , as applicable.
    The
    New Customer
    or
    New Supplier
    wizard appears.
  2. In the
    General
    page enter the partner name and number, select
    EDI X12
    or
    EDIFACT
    from the
    File Type
    list, and then enter the message interchange details. Click
    Next
    .
    The
    Messages
    page appears.
  3. Perform the following steps:
    1. Click
      Add Message
      to select a message type to exchange with the partner.
    2. If required, edit the version, mode, or status of the message type.
    3. For each message type, you can assign a custom process to process EDI messages of that type. To assign a custom process to a message type, perform the following tasks:
      1. Customize a Library Data Transformation project in Informatica Developer.
      2. Export or deploy the transformation as a service. For more information, see the
        Data Transformation User Guide
        .
      3. Upload the custom transformation service to
        B2B Gateway
        . For more information, see Creating a custom B2B Gateway transformation service.
      4. In the
        Custom Process
        field, select a transformation service from the list.
    4. For each message type, you can attach a process-from-backend mapping. To attach a process-from-backend mapping to the message type, click the Actions button to the right of the line of the message type, click
      Add Process-from-Backend Mapping
      , select a mapping that is appropriate to the message type that you are adding, and then click
      Select
      .
      For both inbound and outbound flows, 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.
    5. Add as many message types as applicable for the partner.
    6. Click
      Next
      .
    The
    Inbound
    page appears.
  4. To define an inbound flow, perform the following steps:
    1. Select the connection type for the flow and configure connection details.
    2. If you selected the
      Advanced FTP V2
      ,
      Advanced FTPS V2
      , or
      Advanced SFTP V2
      connection type, select the connection where
      B2B Gateway
      creates files for the partner and the action that
      B2B Gateway
      performs on the files after pickup.
    3. If you selected the
      File Servers
      connection type, you can select a file transfer task in the
      Pre-Process
      area and define the task variables. You can select one of the following file transfer tasks:
      Name
      Description
      Decrypt
      Decrypts files that the partner uploads to the file server before the files are sent to
      B2B Gateway
      . For more information, see Decrypt.
      Decompress
      Decompresses files that the partner uploads to the file server before the files are sent to
      B2B Gateway
      . For more information, see Decompress.
    4. If you selected the
      Local Folder/MFT
      ,
      FTP Client
      , or
      SFTP Client
      connection type, select whether or not
      B2B Gateway
      deletes files after pickup.
    5. Select a process-to-backend mapping if applicable and the location where
      B2B Gateway
      saves the mapping.
      This mapping is used for messages where a process-to-backend mapping is not associated with the message type.
    6. If the mapping contains parameters, optionally enter parameter values in the
      Mapping Parameters
      list.
    7. For EDI X12 messages, select
      whether to use element names or element reference numbers in the
      B2B Gateway
      XML interface files.
    8. Define a schedule for the flow.
    9. Click
      Next
      .
    The
    Outbound
    page appears.
    If the outbound flow uses the same connection as the inbound flow, and the connection type is File Servers, Local Folder/MFT, FTP Client, or SFTP Client, click
    Copy Details from Inbound
    to populate the
    Outbound
    page with details that you entered in the
    Inbound
    page and then edit the outbound details, as required.
  5. To define an outbound flow, perform the following steps:
    1. Select the connection type for the flow and configure connection details.
    2. If you selected the
      Advanced FTP V2
      ,
      Advanced FTPS V2
      ,
      Advanced SFTP V2
      , or
      AS2 Client
      connection type, select the connection where
      B2B Gateway
      creates files for the partner.
    3. If you selected the
      File Servers
      connection type, you can select a file transfer task in the
      Post-Process
      area and define the task variables. You can select one of the following file transfer tasks:
      Name
      Description
      Encrypt
      Encrypts files that you send to the partner before they are upload to the file server. For more information, see Encrypt.
      Compress
      Compresses files that you send to the partner before they are upload to the file server. For more information, see Compress.
    4. Select one or both of the following mappings, and the locations where
      B2B Gateway
      saves the mappings:
      • If you assigned process-from-backend mapping to specific messages on the
        Messages
        page, select a message discovery mapping.
      • Select a process-from-backend mapping to use for messages where a process-from-backend mapping is not associated with the message type.
    5. If the mappings contain parameters, optionally enter parameter values on the
      Mapping Parameters
      lists.
    6. Optionally configure message details.
    7. Optionally define a schedule for the flow.
    8. Click
      Save
      .
    The partner shows on the
    Explore
    page.

0 COMMENTS

We’d like to hear from you!