cancel
Showing results for 
Search instead for 
Did you mean: 

It is possible to change the ALEAUDIT IDoc

andreas_schfer
Explorer
0 Kudos

Hi,

we use SAP PI 7.1 SP10 and use ALEAUD IDoc create fromn SAP PI for message tracking in the ERP system.

In some scenarios we distribute the messages to more than one system.

We need to add the destination system in the ALEAUD Idoc to identify which system get/not get the message.

Is there any way to enhance the ALEAUD Idoc in SAP PI.


Andy

Accepted Solutions (0)

Answers (2)

Answers (2)

nitinlpatil12
Participant

Hi Andy,

yes, it is possible you need to enhance the standard idoc ALEAUD in ECC and then you can import extension in PI, following are the brief steps for creating extension.

Create Segment --> WE31

Create Extension --> WE30

Link std. and extended idoc --> WE82

Write custome code to populate extension segment --> User Exit or Z Function Module

How to Find User Exit - WE30 (Edit-Object Repository-Package)

SMOD - Ctrl + 5 - Enter Packege and execute - list of exits

Refer following blogs for details,

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80677e5d-dc79-2c10-b7bb-a7e99767c...

https://scn.sap.com/thread/412949

Regards,

Nitin Patil

Please reward points if you find information useful.

andreas_schfer
Explorer
0 Kudos

Hi Nitin,

This refers to the enhancement in ECC but I need enhancement in the SAP PI and for the ALEAUDIT the PI creates by himself and not for a message PI receive from one systen and send to another.

Andy

ambrish_mishra
Active Contributor
0 Kudos

Hi Andreas,

Although I have not used enhanced ALEAUD in any of my projects but it is like any other standard IDoc and can be enhanced in ECC, not PI. You will need to import the metadata of the enhanced IDoc in PI.

Ambrish

andreas_schfer
Explorer
0 Kudos

Hi Ambrish,

the problem is not to add additional field, instead we need additional information in the IDoc.

In PI we splitt the message and send it to two systems.

System One runs on error, System Two process is Ok.

You get two Status Idoc, one with success (first message) and one with error (second message).

There is no identifcation in the Status Idoc which Business system throws the error.

Andy

ambrish_mishra
Active Contributor
0 Kudos

Hi Andreas,

The whole IDoc/IDoc acknowledgment (ALEAUD) functionality is defined in  ECC sending data/acknowledgment to other systems. Don't think it can be changed in PI. It has to be changed in ECC.

You mentioned that you are looking for details as to which system has thrown an error. This is visible in SXMB_MONI in outbound status so you would whether or not the message reached the target ECC box or not. No ?

Or are you looking for application errors in ECC ?

Ambrish

andreas_schfer
Explorer
0 Kudos

Hi Ambrish,

in SAP PI there is the possibility to activate Acknowledgments for the IDoc Adapter in SAP PI, T-Code SE38 --> IDX_NOALE you can switch on/off Acknowledgments for IDoc's created in SAP PI. In case of an error/success an SAP PI Acknowledgment is created which is later convert to an ALEAUD Idoc and send back to the initial sender system.

I need to enhance this ALEAUD Idoc created by SAP PI

Andy

ambrish_mishra
Active Contributor
0 Kudos

Hi Andy,

I do understand ALEAUD functionality and your requirement. Since the IDoc is created in another ECC system, the acknowledgment comes from there and not PI. You cannot change anything in PI for this to enhance ALEAUD IDoc.

Essentially the ALEAUD functionality is for IDoc communication between 2 SAP systems. In your case, when PI sends an IDoc to 2 receiver systems, they generate acknowledgments for PI separately, unaware that the same IDoc data has been received by 2 ECC systems.

Please take a look at the link below:

http://wiki.sdn.sap.com/wiki/display/ABAP/Handling+Idoc+Acknowledgements

If at all enhancing in an option, it has to happen in ECC and PI needs to have the metadata of the enhanced IDoc.

Hope it helps!

Ambrish

andreas_schfer
Explorer
0 Kudos

Hi Ambrish,

we need some information in the IDoc like the receiver System of the message.

So we need no additional fields, add/change the content of existings fields are everything we need.

In the SAP PI there is everything we need in the soap header

We found also the XSLT transformation ST_XMS_MSGHDR30_ERROR_INC which is used to create the acknowledgment error.

Here is this the first location we want to fill other information in the fields like the receiver system