Purchasing Organization for follow-on-document Missing message while creating the Shopping Cart

[Former Member]

Hi Gurus,

We have receently changed our R/3 syste from MD1-400 to MD1-500 and completed the config changes in our SRM client MED-400.

We are trying to create the SC in MED SRM ITS portal and receiving the below error message.

1.Purchasing Organization for follow-on-document missing

2. No Purchasing Organization exists

3.No purchasing Group exists.

Also when we verified the Purchasing group field in Extended details it has been Grayed out in SRM ITS Portal and we are using SRM 5.0.

We have maintained the Co.Code, Purchasing Group and purchasing Orgdetails in the Functional tab of user ID and the EBP.

Could you please suggest us how to fix this issue.

Thanks,

Sada

[Former Member]

Hello Sada,

Whenever you replace/change a R/3 backend, there are a number of changes required in the connected SRM system. It also depends on the scenarios being used. But mostly following are the top checks/changes to be done in SRM and R/3 :

-->Run BDLS in SRM  and R/3 (if required) to replace old logical system name with new ones

--> Check if RFCs work fine in SRM and new R/3 system

-->Check and change SRM specific config tables by going through all the SRM-relevant nodes in

SPRO->Supplier Relationship Management->SRM Server like BBP_BACKEND_DEST, product category configurations etc.

--> Check related number range objects in SRM and R/3

-->Check views V_t160pr, V_T160EX in R/3 in case you are using PR transfer to SRM

-->Check ALE Settings in SRM & ECC (BD64, WE20, WE21 etc). These have to point to the correct system

-->If you use material master download from R/3, you need to redo your material master download by deleting the existing one in SRM

-->Check your Org Structure in SRM (PPOMA_BBP) thoroughly for all attributes like SYS, Account assignment objects, Extended attributes tab, Function tab, Responsibility tab etc for reference to old R/3 logical system name

you must run BDLS on tables like HRP1000, HRP1001... etc.

Let me know if you need more info.

Regards,

Sushil.

[ricardo_cavedini]

Hello,

Check the ECC system alias maintained in PPOMA_BBP.

See if it is pointing to the correct system/client.

Regards,

Ricardo

[Former Member]

Hi Sada,

Did you use BDLS to change the old log system to new one, this t code will replace old one with new one in all places, first try with the test run and see how many places Old log system is used,take help of Basis for executing this t code.

hope this is help full.

regards,

raghu

[Former Member]

Rahu,

Thanks for the update. Per your suggestion I have executed the t-code BDLS and received the below message in the bottom for the test run. Could you please check and suggest me.

------------------------------------------------------------------------------------------------------------------------

* Identifies Cross-Client Tables

@AH@ Field in table already contains the name MD1CLNT500

------------------------------------------------------------------------------------------------------------------------

@0S@ SAPoffice Object references that have to be converted: 6

@0S@ SAPoffice Object references that are to be converted: 0

@0S@ SAPoffice Object references that contain another LogSystem: 6

------------------------------------------------------------------------------------------------------------------------