Reviewing the details of a partner ID setup

Select Transformation > Configuration > Partner IDs.

Click the Drill down button of a partner ID setup to display the detail view of the Partner IDs page.

Review the header information of the partner ID setup:

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.
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.
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 the FeatureActivation code list. On this code list, add the Code value UseShipmentCanceledMessageType. Activating this code results in process shipments with the status of Canceled to be created as messages with the message type Shipment Canceled BOD instead of Shipment.
Communication Provider: The field specifies the communication provider type. You can select On-premises Provider. This is an on-premises communication provider managed by the customer. With this communication provider, an On-Premises Communication Agent interfaces with the Communication Service in the Infor cloud. The actual communication with trading partners is managed by the customer.; Note: The Communication Provider drop-down list is only displayed, if the field Message Direction is set to Outbound. When you select On-premises Provider as communication provider, the On-premises Communication IDs field set is shown. The field set requires the configuration of additional data for the communication with an external trading partner: Data Set Name, External Partner ID and Character Set.
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.

Review the Note field set. The field set shows comments that are specified for the partner ID setup.

Review the EDI Parameters field set:

Publishing Frequency

The field defines the frequency in which a message is published. The standard publishing frequency is Immediately.

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 and not shown on the Manage Messages page.

Transmission Reference No.

The field provides a transmission reference number for outgoing messages. In , the transmission reference number is automatically incremented by one with each message transfer.

Message Merge

This check box is used to enable 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 you want to set up a day of the month or day of the week for processing merged messages, configure the code list MessageTransformerConfiguration. See Configuring the MessageTransformerConfiguration code list

Message Merge Criteria

If you select the Message Merge check box, you must indicate the criteria by which you want the merged messages to be grouped. The options are:

Bill To
Customer
Pay From

Review 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.

Additional Routing ID

The additional routing ID is the specified identification number of the sender that is contained in the message.

Note: This field is visible in the instance of a Sender ID for which the code CustomAdditionalRoutings has been defined. See Configuring the CustomAdditionalRoutings code list.

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.

Review the On-premises Communication IDs field set:

Data Set Name: The data set name that is assigned to the pair of partner IDs is used for the connection of the On-Premises Communication Agent with Exchange Services. The data set name in Exchange Services refers to a set of AS/2, OFTP/2, or FTP parameters that are used to create a sending order. The set of AS/2, OFTP/2, or 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 external partner, for example, for each plant of a customer.
External Partner ID: The field specifies the external partner ID of an on-premises communication system that is mapped to the partner ID of the trading partner in the application.
Character Set: The character set is used for outgoing messages. You can select the character sets UNOA, UNOB, UNOC, or UNOD. For example, outgoing VDA messages require the use of the character set UNOA. In instances where the UNOD character set is selected, messages with this partner ID are saved to the configured file directory local to the On-Premises Communication Agent. This allows Exchange Services to retrieve these files from the directory with the proper encoding. Files saved this way are named in this format: <ExternalPartnerID>.<DataSetName>.<MessageCorrelationID>.txt with the period (.) being used as the separator between these fields. For example: DEMO_TEST.DEFAULT_OUT.AEDEVTENANT_DEV_OnPrem119789_1704486593473.txt

Review 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.

Review 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.

Review the Internal/External Partner Mapping lines at the bottom of the page. A partner ID setup can contain several partner mapping lines for incoming and outgoing messages. External customer IDs, and ship to IDs, and supplier IDs are mapped with the internal customer IDs, and ship to IDs, and supplier IDs. The mapping enables the area and the connected ERP system to use the internal customer ID and ship to ID. The appropriate contract information and the internal item ID that is associated with a contract line can be evaluated.

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.