cancel
Showing results for 
Search instead for 
Did you mean: 

Dynamic Configuration for IDOC

Former Member
0 Kudos

Hi,

Whenever an IDOC is send from SAP R3 system to PI (SAP R3 -> SAP PI -> Target), we get an additional node of Dynamic Configuration under the SOAP Header in SXMB_MONI.

Why is this happening? Does this happen for all the versions of SAP XI (PI)?

This issue does not occur when the IDOC is send by SAP PI to SAP R3 system (Source --> SAP PI --> SAP R3)

I am using SAP PI 7.1.1

Thank you,

Pankaj.

Accepted Solutions (1)

Accepted Solutions (1)

stefan_grube
Active Contributor
0 Kudos

> This issue does not occur when the IDOC is send by SAP PI to SAP R3 system (Source --> SAP PI --> SAP R3)

Why this is an issue for you?

It works as designed.

Former Member
0 Kudos

Hi,

Why this is an issue for you?

I am trying to send IDOC from SAP System to PI system.

Ideally there should be no DynamicConfiguration step under SOAP Header folder in SXMB_MONI (I tested a SOAP -> PI -> FILE and the Dynamic Configuration does not come); unless and until we make use of the ASMA properties (UDF/ Module). Is this understanding correct?

For example, if I send an IDOC i get the below details in SXMB_MONI:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Response --> 
<SAP:DynamicConfiguration SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPOR">SAPPI</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRT">LS</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRN">SAPPISYSTEM</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPOR">SAPECC</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/Message/30" name="CALLER_CODEPAGE">4102</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRN">SAPECCSYSTEM</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="CIMTYP"/>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="IDOCTYP">Z_VALIDATION_ACK01</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="MESTYP">Z1VALIDATIONACK</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRT">LS</SAP:Record>
</SAP:DynamicConfiguration>

Is this behavior as expected?

Thank you,

Pankaj.

Former Member
0 Kudos

Hi Pankaj,

this is expected behaviour, as the ECC already sets these values to the DynConf.. default for an IDoc sender, and very useful for party substitution. Like Stefan says, this should not hinder you.

kr,

Peter Glas

Former Member
0 Kudos

Hi,

this is expected behaviour, as the ECC already sets these values to the DynConf.. default for an IDoc sender, and very useful for party substitution.

Ok. so is this is a normal behavior when IDOC is sender?

Thank you,

Pankaj.

stefan_grube
Active Contributor
0 Kudos

>

this is expected behaviour, as the ECC already sets these values to the DynConf.. default for an IDoc sender, and very useful for party substitution.

> Ok. so is this is a normal behavior when IDOC is sender?

Yes.

And it should not cause any issues.

Former Member
0 Kudos

Hi,

Thank you very much for a quick resolution. Actually working for the first time on IDOC and hence considered it as an error/ issue.

Thank you,

Pankaj.

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Pankaj,

An additional node Dynamic configuration comes under SOAP Header due to using of ASMA properties.

This should only appear if you are doing any dynamic configuration(Using an UDF).

Thanks,

Former Member
0 Kudos

Hi,

This should only appear if you are doing any dynamic configuration(Using an UDF).

Agreed. But why is it coming for IDOC (if I have read properly IDOC does not support Dynamic Configuration).

Moreover, I do nothing other than importing IDOCs into ESR (not even mapping/ no ID part). Even then I get the above details for an IDOC -> PI flow.

Thank you,

Pankaj.

Former Member
0 Kudos

Hi Pankaj,

this is because of the use of Adapter Specific Message Attributes, check this: http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce299c3a8e5430e10000000a42189b/frameset.htm

Can you share the content of the Dynamic Configuration XML ?

kr,

Peter Glas