Data transfer > OFTP > SSID groups > Sending files to one partner using differing settings

What if two files are to be sent to a partner with differing settings, for example with different SFIDs? In this case, two partner accounts can be created for the partner with the corresponding settings. Then two jobs can be created, each containing one of the files and the corresponding partner account. However, this can lead to problems when receiving EERPs/NERPs if they are received or sent asynchronously. To solve this problem the two partner accounts have to be combined into one SSID group.

Different SFIDs via Fixed File Names

Sending different files using different SFID to one partner can also be achieved using the fixed file names feature in the partner settings.

Example 1

•The partner accounts Partner A and Partner B differ in the SFID used.

•File D1 is sent via partner account partner A, the partner does not transmit the EERP for the file in the same session.

•The next connection to the partner is via the partner account partner B. The other side cannot, of course, distinguish between the two partner accounts, so the outstanding EERP for the previously transmitted file D1 is sent during this session.

•If partner A and partner B are in the same SSID group, !MC5 recognizes that the EERP belongs to the file D1 previously sent via partner A. If the partner accounts were not grouped, !MC5 would not be able to associate the EERP.

Example 2

•The partner accounts partner A and partner B differ in the SFID used.

•The file D1 is received via the partner account partner A. The EERP is not returned in the same session.

•A connection is established via partner account partner B. If both partner accounts are in a group, !MC5 recognizes that there is a pending EERP for partner A and sends it during the session via partner B. Otherwise, the EERP would only be sent via the next connection via partner account partner A.