idoc_Guiaburros_SUPERCOMPLETO

< html> < body> When posting an IDOC to XI, the receiver system configured in XI can be a Business System, a Business Service or an Integration Process. Let us consider a simple scenario where in an SAP system sends an IDOC to XI and a mapping program within XI runtime converts the IDOC structure to a simple XML structure and stores it in a file system using the file adapter. The Sender IDOC adapter requests an acknowledgement when sending the IDOC to XI. The system acknowledgement sent by the file adapter is converted into an ALE audit message and sent back to the sender SAP system by an IDOC ACK channel configured in XI(an IDOC receiver adapter).

A quick checklist for the configuration steps is below.

View weblogs by: Most Recent | Topics | Top Blog Posts | SDN Bloggers

&RQILJXUDWLRQ7LSVIRUD%XVLQHVV6HUYLFH,QWHJUDWLRQ3URFHVVWRVHQGEDFN$/(DXGLW,'2&Saravana Kumar Kuppusamy Business Card &RPSDQ\Wipro Technologies Jan. 20, 2005 07:39 PM3HUPDOLQN

Print

Create an RFC destination to XI in the sender SAP system using SM59 Create a transactional port to XI using the RFC destination created in the above step Create a Partner agreement usign transaction we20 in the sender SAP system Create a logical system using transaction bd54 for the parner agreement created in the above step Select an IDOC using transaction we19 and change the EDIDC header recepient port & LS name Create an RFC destination to the Sender SAP system using SM59 Create port to sender system using idx1 in the XI system for the RFC destination created in the above step Create SLD entries(technical and business system) for the sender SAP system

%XVLQHVV6HUYLFHDVWKHUHFHLYHUV\VWHPHowever, when the file adapter communication channel is configured under a Business Service, the sending of ALE audit message may fail with the message "Unable to convert the sender service < Business Service Name> to an ALE logical system". To avoid this error, we need to specify a Logical System for the IDOC adapter.To specify the logical system, open Integration directory and select the Business Service that is configured as receiver for the IDOC.Switch to Edit Mode and choose the "Service" menu and then the menu option "Adapter-specific identifiers". In the popup specify a Logical System for the IDOC adapter.Save and activate the Business Service. Now the ALE audit message is sent back to the SAP system without any errors.

Pgina 1 de 4SAP Developer Network Blog: Configuration Tips for a Business Service/Integration Process to send...

12/10/2005https://weblogs.sdn.sap.com/pub/wlg/1180

,QWJHUDWLRQ3URFHVVDVWKHUHFHLYHUV\VWHPThere could be scenarios where in an integration process is configured as the receiver system for IDOC.This could be the case when we intend to collect IDOCs in an integration process and then post it in bulk to another SAP system.Here too, we have to specify the Logical System for the IDOC adapter. To acheive this, open integration directory and select the integration process that is configured as receiver for the IDOC.Switch to Edit mode and choose the "Service" menu and then the menu option "Adapter-specific identifiers". In the popup specify a Logical System for the IDOC adapter.Save and activate the integration process. Now the ALE audit message is sent back to the SAP system without any errors.

6ZLWFKLQJ2II$/(DXGLWPHVVDJHVAt times, there could be a scenario where in we do not need the ALEAUD IDOCs to be got back.To acheive this add the PORT,CLIENT and MESSAGETYPE to the table IDXNOALE.Use transaction SE16 -> specify the table name "IDXNOALE" and then choose create new entries.Specify the values for PORT, CLIENT and MESTYPE fields, save the entry.This procedure helps switch off ALEAUD IDOCs from being sent back to the sender SAP system.

! " $#&%'()$ +*!,,-."/0 1 2!#&3454+)0*61!&70888908:;

< /body> < /html>

Saravana Kumar Kuppusamy is an SAP Netweaver consultant in Wipro Technologies.

(? .1 0-

ALEAUD.ALEAUD01

Showing messages 1 through 5 of 5.

Titles Only

Main Topics

Oldest First



2005-01-27 14:04:34ChristopheDUMONT Business Card [Reply]

Hi,

I find this on help.sap.com :

"For the inbound IDoc adapter to be able to send an acknowledgment IDoc to the sender, a Structure link communication channel with the interface ALEAUD.ALEAUD01 must be maintained for the sender."

I have a question :

How could I change the ApplicationAckRequested and ApplicationErrorAckRequested to false without change SystemAckRequested and SystemErrorAckRequested (at true) ?

I want do this, because when I send an Idoc that it is correctly post with the file adapter, I get an error : "AckRequestNotSupported". I think it's because file adapter is not considerate as an application ?!

Thanks for your help. Best regards, Chris

Sending ACk back 2005-01-21 06:47:00RichardCurtis Business Card [Reply]

Hey,

Good weblog, I am trying to do a senario as we speak.

Question1: My receiver is a business process under a party. I specified a logical system name PO_DELL for the process in the adapter specific idenifiers, however I still get the "unable to convert error". Does the LS name have to match anything on the XI or R/3 side? The partner profile in R/3 is the vendor number(ex 1111222200), type LI . Does the LS in XI have to be this number?

Question2: What has to be done for the acknowledgment part? Do I have to create a partner profile in the R/3 side for DELL_PO(see above) and assign ALEAUD as a message type?

thanks for the log,

Chris IDX2

2005-01-21 00:45:07ChristopheDUMONT Business Card [Reply]

Hello,

Good job !

I am not sure, but I think you must create metada for the idoc in IDX2 !?



Thanks, Regards @ IDX2

2005-01-21 11:17:35ChristineGeier Business Card [Reply]

Hi Christophe,

if you do not import Metadata to IDX2, then XI will do that the first time a message of this type is sent.

Best regards Christine

@ IDX2 2005-01-21 01:13:17Saravana KumarKuppusamy Business Card [Reply]

Hi Christophe, idx2 definitely is useful to view the IDOC metadata/ remove the IDOC type/ reassign the IDOC type. One more thing to be taken care is to set the "ACK_SYSTEM_FAILURE" parameter in the XI engine to enable using acknowledgements. In XI ABAP stack, execute SXMB_ADM -> Integration Engine Configuration , add the "ACK_SYSTEM_FAILURE" parameter in the category RUNTIME as well.

Thanks Saravana

Showing messages 1 through 5 of 5.



Documents

idoc_Guiaburros_SUPERCOMPLETO