IDOC acknowledge (ALEAUD) - Structure EDI_DC40

Former Member — Wed, 14 Oct 2009 17:25:14 GMT

Hello,

I would like to know please if there is a way to use the field ARCKEY/REFMES within the Structure EDI_DC40 for the IDOC ALEAUD.

The scenario is: we are getting a GUID via the field REFMES message type MATMAS and after then we need to send the relevant GUID back via the acknowledgment IDOC.(THERE IS NO XI/PI)

The most import point that we don't want to insert a code (user-exit, FM and etc.) only configuration.

Can we configure the above Structure with the relevant fields?

Thank you,

Boaz

Re: IDOC acknowledge (ALEAUD) - Structure EDI_DC40

Former Member — Sun, 18 Oct 2009 17:43:14 GMT

You need to understand the purpose of these fields. These fields were designed hold data from the EDI system about the IDoc.

REFMES is meant to hold the Transaction or Message ID for the EDI interchange that the IDoc is bundled into while ARCKEY was designed to hold the path and name of the EDI interchange file archive.

These fields are not processed by the standard system, although they are read in some circumstances. There is no configuration that I know of that will allow you to automatically populate them with anything. Typically they are populated by the EDI system (or middleware) using the STATUS IDoc or through customer exits.

There is one exit called during inbound and outbound processing that can be used to update the control segment of an IDoc. You'll find it in Enhancement SIDOC001. It's called just before the IDoc is written to the database and provides the last chance to change or create control segment values. You need to be careful because it's called for all IDocs, both inbound and outbound. You need to specify which IDoc you want it to process. Good luck.

topic Re: IDOC acknowledge (ALEAUD) - Structure EDI_DC40 in Application Development and Automation Discussions

IDOC acknowledge (ALEAUD) - Structure EDI_DC40

Re: IDOC acknowledge (ALEAUD) - Structure EDI_DC40