Scribd
Upload
1K views

Output Determination For Delivery

I created a new Output type called ZBL1 to send delivery documents from SAP to an XI system whenever a delivery is created. However, when trying to maintain the Output type, errors occurred regardless of whether EDI or ALE was selected as the medium. The errors indicated issues with the partner profile or connection for the XI system partner XIDCLNT100.

Uploaded by

phenomenon1483
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
1K views

Output Determination For Delivery

I created a new Output type called ZBL1 to send delivery documents from SAP to an XI system whenever a delivery is created. However, when trying to maintain the Output type, errors occurred regardless of whether EDI or ALE was selected as the medium. The errors indicated issues with the partner profile or connection for the XI system partner XIDCLNT100.

Uploaded by

phenomenon1483
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 8

1. I created a new Output type called ZBL1 for sending DESADV.

DELVRY03 IDOCS
from the SAP system to the XI system whenever a delivery is created.

TCODE: NACE
2. Then I created a partner profile in WE20 for the XI system.
3. Created a port in WE21 with RFC destination pointing to the XI system.
4. When I try to maintain the Output type ZBL1 I get the following error.

If I give EDI as the Medium I get a error saying Maintain outgoing EDI-connection data
for the partner XIDCLNT100.
If I give ALE as the Medium I get a warning saying partner XIDCLNT100 does not exist
for partner function LS.

You might also like