This document explains how you create a partner and a partner alias repository. This is used in Customer Delivery Scheduling (CDS), among others.
You have created a partner ID and connected it with a partner alias ID.
Partner is a M3-defined identity of an internal or external trading partner on different hierarchical levels, such as customer ID, supplier ID, customer address ID and warehouse ID. The partner identity is used to translate itself into a partner alias identity. This is performed when an outgoing EDI message is created by using the API CRS886MI.
A partner alias is an externally defined identity of a trading partner on different hierarchical levels, such as plant code, gate code, EAN location code or supplier number. The partner alias identity is used to translate itself into a partner identity. This is performed when an incoming EDI message is received by using the API CRS886MI.
Partner and a partner alias details are stored in the following M3 tables:
The settings in these documents must be defined:
Create a partner type in 'Partner Type. Open' (CRS883).
Create a partner alias type in 'Partner Alias Type. Open' (CRS884). If required, connect a partner alias type to a partner type.
Create a partner ID in 'Partner Repository. Open' (CRS885).
If the partner type is category 11, 12, or 13, then you can connect the partner ID to a partner ID on a higher level. See Enter Business Chain.
In 'Partner Alias Repository. Connect' (CRS886), select a partner alias type (allowed or available alias types, depending on the settings) to be connected to the partner ID.
Create an alias ID. Depending on the settings you can have 1, 2, or 3 partner alias fields for the partner alias ID.
If you have a partner alias that is a popular number, you can connect several partner alias IDs (records) to one partner ID.