PR not pulling into SRM system

[Former Member]

i made PR in r/3,but it is not pulling into SRM system,even i

checked "SLDCHECK,SPROXY,SXI_MONITOR,SMQ1 &

SMQ2" in R/3 also in PI system,but error occuring in SRM

system while i am checking SXI_MONITOR, there is system

error in perticular PR's created date.

[Former Member]

Hi,

everything is ok but while i m monitor XML message in SRM with sxi_monitor,there is an error for a perticular date which is related to my PR.

[former_member22425]

Hello,

Can you please provide details about the error message shown by system here in sxi monitor. What is the status of the xml message flag. Is it zig-zag or red ?

If it is zig-zag , try to check the error details in the t-code /n/sappo/ppo2.

Best Regards,

Rahul

[Former Member]

Hi,

The Error is zig-zag..

I have checked the t-code /n/sappo/ppo2, ther is some worning message,but checked the system connection is ok....

[Former Member]

HI,

i am still facing same problem,the XML Message stucked in SRM.

Edited by: saurabhsen on Jan 2, 2012 8:07 AM

[former_member22425]

Hello Saurabh,

Sorry for the delay response here.As mentioned by you the xml shows the FEH error(zig-zag sign) , it could be either due to the user attributes inconsistency or due to master data issues with regards to the PR getting transfered from ERP to SRM system.

Please check whether the user used for the xml processing should exists in the SRM org structure with proper roles and attributes.

assgin the following roles to the integration user used here.

/SAPSRM/EMPLOYEE

/SAPSRM/OP_PURCHASER

SAP_XI_APPL_SERV_USER

Also assign the SAP_ALL profile to it.

Also ensure that you have configured Forward Error handling in your system, then only FEH tcode will you the correct error detials. If it is configured then goto the transaction /n/sappo/ppo2 and set the parameters as below:

Order Status as 1 to 2

Order Assignment 1

Mode of Postprocessing Order 0 to 3

then execute it.

Ignore the warning for the RFc error for srm to sus client.

Search for the PR number against which you will get the exact error details.

Hope this will answer your query.

Best Regards,

Rahul

[Former Member]

Hi Rahul,

Thanks for your valuable reply,SRM having SAP_ALL already exist,i have added more given roles also which u have given.

and check t-code /n/sappo/ppo2 also,there is only warning mess "No RFC destination saved for logical system AGPCLNT300" .

after that,there is no PR number against which i will get the exact error details

Thanks,

Saurabh Sen

[former_member22425]

Hello Saurabh,

Have you configured Forward Error handling in your system. Kindly re-check the config with the config guides.

Refer to the links for more details on FEH :

http://help.sap.com/saphelp_nw73/helpdata/en/cd/798aa3c7754c61b2f2d50ea7b66aac/content.htm

Note 1270081 - Trouble shooting SOA Services

Also try to change the inputs for Mode of Postprocessing Order from 0 to 3 , 1 to 3 like this.

Also ensure that time lines to execute the check is correct. It should show you the error details for sure if the XML goes to FEH error.

Best Regards,

Rahul

[Former Member]

questions for you first

1. Which version of ECC and SRM are you using

2. Has the PR been sent for external sourcing(in PR screen)?(are you sending the PR for sourcing purpose)

3. do you know if an XML is triggered out from ECC or not!!

answer these first

[Former Member]

i am using ECC- 6.5 and SRM-7.0

[Former Member]

The reason for XML failing in SRM system can be THE USER though which the XML is being processed(user which PI uses to connect to SRM), is not assigned in the org structure and the attributes/responsibilities not maintained for that user.

maintain that and then it will work fine

[Former Member]

During the making of PR ,i think the plant/company and purchaseing group should be maintain in Organization structure.

it is already maintain in Organization structure.

[Former Member]

Yes those are needed.

ALONG WITH THAT:

you need to maintain that user which PI used to connect to SRM(the user though which SC will be created), in the Org structure with all responsibilities and user attributes. if you dont do that SC wont get created

[former_member22425]

Hello,

Refer to thread for more details.

Best Regards,

Rahul