Centrally in the Partner Administration

You can centrally create additional IDs in the Partner Administration (if you have the user right Admin). These additional IDs are valid system-wide.

(1) Each central additional ID must have an ID in the range of 100000 to 199999.

(2) In addition, a name must be assigned.

In Partner Channels

Within the partner channels, it is possible to store values for these system-wide additional IDs, which then only apply specifically to this channel.

(3) If this option is selected, the value in the database is not in plain text, but is encrypted with AES-256.

(4) The name from (2). Important note: Uppercase and lowercase must be considered.

(5) The value for this partner channel. Note: In other partner channels, a different value can be assigned to the same additional ID.

Caution When Importing and Exporting Partners (with Its Channels)

If a central additional ID is not defined in the target system, a corresponding additional ID cannot be created successfully in the channel (when manually exporting/importing a partner and its channels). You will then find an additional ID in the channel, but without a name. If you manually create a central additional ID with the same ID on the target system (not the same name!), the name in the additional ID of the channel will be updated respectively. Alternatively, to work around this problem, you can use the Transport Manager.

Application Examples

You can, for example, use additional IDs in

• File Inspectors of Content Inspectors (dynamic filter values, see EDIFACT Inspector and X12 Inspector),

• in the functions find channel reference-value(a,b), find channel reference-value(a,b,c,[d],[e]) and find channel(a,b,[c,d]) (see the examples there, e.g. dynamic exchange of channels in Input Agents and Response Routes or the retrieval of specific customers parameters using other customers parameters)

• and to dynamically define an alternative DMZ server for a partner channel.

The idea is that dynamic values can be used depending on the partner channel (i.e. communication partner). You could, for example, read out the specific values from the additional IDs for the respective partner and use these in the mapping (e.g. address data). Using these values, you could also control which Response Routes are executed in phase 6. That way you could have Response Routes in a profile that are only executed for specific partners. This allows an abstract creation of profiles, which can then be used for several partners. On the one hand, that saves work and/or profiles and on the other hand, a less error-prone and clearer maintenance of contact and communication data is made possible.