Creating a partner ID setup

To create a partner ID setup:

  1. Select Transformation Services > Configuration > Partner IDs.
  2. Click Create to display the detail view of the Partner IDs page.
  3. Specify this header information:
    Effective from Date
    This field defines the start date of the valid period for the configuration.
    When editing, click the Calendar button to select the start date from a calendar.
    Effective to Date
    This field defines the end date of the valid period for the configuration.
    When editing, click the Calendar button to select the end date from a calendar.
    Partner Hierarchy Name
    The partner hierarchy name is a classification for a group of communication partners. A partner hierarchy must exist for this configuration.
    Partner ID
    The partner ID is the hierarchy node of the configuration that identifies a communication partner or a group of communication partners.
    Message Type
    The message type defines the content of the message. Examples are VDA 4905, VDA 4915, ASC X12 830 Planning Schedule with Release Capability, or ASC X12 862 Shipping Schedule. The message type depends on the message standard.
    Note: For trading partners who require the Shipment Cancellation message to be sent to a different data source name (i.e., final recipient) than the regular shipment, a new code list must be activated in FeatureActivation code list. On this code list, add the Code value UseShipmentCanceledMessageType. Activating this code results in process shipments with the status of Canceledto be created as messages with the message type Shipment Canceled BOD instead of Shipment. See Configuring ASN cancellation and replacement for more details.
    Message Direction
    The message direction is Inbound for incoming messages or Outbound for outgoing messages.
    Remark
    Review or provide a short description that clarifies the purpose of the configuration.
    Location
    A location is a single geographical site of an organization that is associated with data or transaction. This is, for example, a warehouse, a manufacturing location, or an office. Items are being shipped to or from a specific location. Example locations are a warehouse, a ship to, and a ship from.
    Accounting Entity
    The accounting entity is a corporation or a subset of a corporation. The accounting entity is independent in regard to one or more operational functions or accounting functions. An accounting entity produces a P&L and balance sheet from a complete, balanced set of transactions, and is often a legal entity. An accounting entity is defined within a tenant and can contain locations. The field entry is disabled. The accounting entity is automatically set when you save the data. The default is the accounting entity where you are currently working.
  4. Expand the Note field set and specify a comment on the partner ID setup.
  5. Specify this information in the EDI Parameters field set:
    Publishing Frequency
    The field defines the frequency in which a message is published. The standard publishing frequencies are Daily, Publish Immediately, Publish Monthly, and Publish Weekly.
    Publish Message
    This check box is used to publish messages to ION, Exchange Services, or store the messages in the file system. In cloud environments, deactivate the check box for messages that must be printed by InterFormNG and must not be stored in the file system. This setting prevents configured file system output from being processed.
    EDI Flag
    This check box is used to enable EDI processing. If not activated, the EDI data is not loaded in Transformation Services and not shown on the Manage Messages page.
    Transmission Reference No.
    The field provides a transmission reference number for outgoing messages. In Transformation Services, the transmission reference number is automatically incremented by one with each message transfer.
    Message Merge
    This check box is used to activate a message merge for several messages that are processed together. For example, some trading partners expect to receive collective invoices over a weekly or monthly time period. If a message merge is activated, Transformation Services merges the incoming invoices of a period into the first message of the period and removes the remaining single invoices from the Manage Messages page. This setting is related to the Publishing Frequency that defines the period for the message merge.
  6. Specify this information in the EXS Parameters field set:
    EXS Partner ID
    The partner ID is used by Exchange Services to access a defined message exchange configuration.
    Data Set Name
    The data set name is assigned to the partner ID in Exchange Services. The data set name in Exchange Services refers to a set of OFTP/FTP parameters that are used to create a sending order. The set of OFTP/FTP parameters includes parameters such as IP address, ISDN number, record length, user name, and password. You can configure several Data Set Names for one EXS Partner ID, for example, for each plant of a customer.
    Character Set
    The character set is used for outgoing messages. You can select the character sets UNOA, UNOB, or UNOC. For example, outgoing VDA messages require the use of the character set UNOA.
    Partner ID Reference
    Some Original Equipment Manufacturers (OEMs) require that transmission reference numbers of invoices and shipments from their suppliers are in the same number range. This is the case especially in North America. To meet this requirement, you can use a partner ID reference. This field shows the reference to another partner ID that provides a unique number range of transmission reference numbers for several ship to addresses. You can use this functionality for the same message type, for example, Invoice BOD, or for different message types such as Invoice BOD and Shipment BOD.
  7. Specify this information in the Sender/Receiver IDs field set:
    Sender ID
    The sender ID is the identification number of the sender that is contained in the message. For example, the sender ID is the customer ID, the supplier ID, or the logical address of the sender of the message.
    Receiver ID
    The receiver ID is the identification number of the receiver that is contained in the message. For example, the receiver ID can be the customer ID, the supplier ID, or the logical address of the receiver of the message.
    Data Segment Separator
    The data segment separator is used for messages that contain records of variable length. These separators are specified in hexadecimal code, for example, to process ASC X12 messages:
    • Data Segment Separator: 0x3A
    • Data Group Separator: 0x2A
    • Segment Separator: 0x7E

    Whereby 0x indicates a hexadecimal code and 3A, for example, represents a colon :.

    Data Group Separator
    A data group separator is used for messages that contain records of variable length. The data group separator must be specified in hexadecimal code, for example, to process ASC X12 messages.
    Segment Separator
    A segment separator is used for messages that contain records of variable length. The segment separator for ASC X12 messages must be specified in hexadecimal code.
  8. Specify this information in the Additional Sender/Receiver IDs field set:
    Additional Sender ID
    This field provides an additional sender ID. If the message direction is Outbound, you can configure an additional pair of sender and receiver IDs. This information can be used in the UNB segment data of an UN-EDIFACT or ODETTE message to identify the two business partners. Within the protocol header of the message, the information serves as an input for Exchange Services.
    Additional Receiver ID
    This field provides an additional receiver ID.
    Routing for Sender
    This field provides routing information for the sender in the UNB segment of UN-EDIFACT messages. The information is provided in addition to the Sender ID in the UNB segment of UN-EDIFACT messages.
    Routing for Receiver
    This field provides routing information for the receiver in the UNB segment of UN-EDIFACT messages. The information is provided in addition to the Receiver ID in the UNB segment of UN-EDIFACT messages.
    ISA/UNB Qualifier for Sender
    The code qualifier is used to qualify the sender ID of the ISA/UNB segments in the message (ASC X12, UN-EDIFACT, ODETTE). The code qualifier is contained in the message.
    ISA/UNB Qualifier for Receiver
    The code qualifier is used to qualify the receiver ID of the ISA/UNB segments in the message (ASC X12, UN-EDIFACT, ODETTE). The code qualifier is contained in the message.
  9. Specify this information in the Inbound Acknowledgments field set:
    Application Advice Expected
    You can define whether an Application Advice message is expected in response to a previously sent ASN message:
    • Not Expected: An Application Advice message is not expected.
    • Only on Error: An alert message is sent to the user, if an Application Advice message reports an error on a previously sent ASN message.
    • Expected: The status of the published ASN message is set to Pending after the transformation until the Application Advice message is successfully received within the defined waiting time. If you select this option, you must specify the waiting time in minutes in the Application Advice Waiting Time (Minutes) field. If the time limit is exceeded, an alert message is sent to the user.
    Application Advice Waiting Time (Minutes)
    If a defined waiting time in minutes is reached after the creation of an ASN message, an alert message is sent to the user. You can only define a waiting time, if an Application Advice message is expected in response to a previously sent ASN message.
    Functional Acknowledgment Expected
    You can define whether an Functional Acknowledgment message is expected in response to a previously sent message:
    • Not Expected: A Functional Acknowledgment message is not expected.
    • Only on Error: An alert message is sent to the user, if a Functional Acknowledgment message reports an error on a previously sent message.
    • Expected: The status of the published message is set to Pending after the transformation until the Functional Acknowledgment message is successfully received within the defined waiting time. If you select this option, you must specify the waiting time in minutes in the Functional Acknowledgment Waiting Time (Minutes) field. If the time limit is exceeded, an alert message is sent to the user.
    Functional Acknowledgment Waiting Time (Minutes)
    If a defined waiting time in minutes is reached after the creation of an original message, an alert message is sent to the user. You can only define a waiting time, if a Functional Acknowledgment message is expected in response to a previously sent message.
  10. To add a new partner mapping line, click the Create button of the Internal/external Partner Mapping list.
    A partner mapping line is created. A partner mapping line for incoming and outgoing messages maps internal and external values. For example, an external customer ID, ship to ID, or supplier ID is mapped to the internal customer ID, ship to ID, or supplier ID.
  11. Specify this information in the Internal/external Partner Mapping line:
    Source Value
    The source value is required for the ERP system to process a message. The source value must be mapped to the target value. For example, the source value is a customer ID or supplier ID. The type of source value depends on the defined type of assignment.
    Target Value
    The target value is expected to be included in a message. The target value is mapped to the source value. For example, the target value is a customer ID or supplier ID. The type of target value depends on the defined type of assignment.
    Type of Assignment
    The type of assignment determines the type of target value that is mapped to the appropriate source value. This is required to deliver the correct information for the message handling of the ERP system. Types are Business Accounting Entity, Buyer, Carrier, EDI Plant, ESP Code, Internal Ship To, Invoicee, Item, Seller, Ship From, Ship To, Text Qualifier, and Warehouse. For example: If the type is Buyer, an external customer ID is mapped to the internal customer ID that is processed by the ERP system.
    Accounting Entity
    The accounting entity is a corporation or a subset of a corporation. The accounting entity is independent in regard to one or more operational functions or accounting functions. An accounting entity produces a P&L and balance sheet from a complete, balanced set of transactions, and is often a legal entity. An accounting entity is defined within a tenant and can contain locations.
    Location
    A location is a single geographical site of an organization that is associated with data or transaction. This is, for example, a warehouse, a manufacturing location, or an office. Items are being shipped to or from a specific location. Example locations are a warehouse, a ship to, and a ship from.
  12. To save the partner ID setup, click Save.
    A notification displays that the partner ID has been saved successfully.