SNDPRN getting populated with wrong value

[Former Member]

Hi,

We are working on File to IDOC scenario. In the IDOC communication channel, we are not mapping the control record node (EDIDC40) since we have disabled the same. Now the default value that is getting populated in SNDPRN at the run time is the logical system name of XI Development box instead of that of XI Production box. Hence failing in R3 side with the error "Partner profile not matched" in WE02. But since the control record gets the values in the XI, there should be some issues in XI itself.

The XI Prd box has been set up recently and this is the first scenario being executed here. The same was working properly in development environment.

Now I need your help identifying the source from where SNDPRN fetches the value. What could be the probable sources where the wrong logical system could be maintained.

Please help.

Thanks in advance.

[former_member181962]

Hi Rumi Singh,

The design should be The communication component ( Your file system) should be assigned with a logical system name in the adapter specific parameters. This is because, the logical sender for the data is not XI, but the file system.

Then you have to create the partner profile from this system in your SAP system. This should not be environment specific.

Steps: Create a logical system using SALE transaction

Create a logical system entry in partner profile WE20.

Best Regards,

Ravikanth Talagana

[Former Member]

chk the header mapping used in Receiver agreement...

[Former Member]

Hi Amit,

Header Mapping was not checked in dev XI. But still it was working fine.

Do you mean to say I should check it in Production?

[Former Member]

Hi Rumi,

In SLD, Check your logical system name assigned with your prod. BS. Might be the Dev logic system name is associated with your prod. BS.

Check this out:

[http://forums.sdn.sap.com/thread.jspa?threadID=1355184]

Regards

Raghav

[former_member184681]

Hi,

Check the assignment of the Logical System Name to the Client for your Technical System in System Landscape Directory.

Hope this helps,

Greg

[Former Member]

Thanks for your reply.

The logical system name in the SLD configuration in XI is the SAP R/3 system name. But my concern is the value in SNDPRN is the logical name of XI development system. So where is this value coming from.

[Former Member]

chk the "Adapter Specific Identifiers" of the sender (File) service...and see whether something is maintained over there or not??

anywayz u can try this also:

go to receiver agreement-> Header Mapping -> Sender service -> select the SAP R3 business system name

in R3 system create one partner profile with the logical system name of SAP R3 BS (and add message type under Inbound parameters)....