System RD2CLNT400 of pur. org. DOI differs from doc reference SD2CLNT400

[Former Member]

Hi all:

We are on SRM 5.0 and getting the above error during SC creation.

We have 1 pur org. which is pointing to the backend pur org (from system RD2CLNT400).

Where is the SRM system (SD2CLNT400) being picked up in the SC document ?

Thanks

-Bakulesh

[Former Member]

Hi Atul:

We are not using the direct material scenario.

The R/3 version is ECC 6.0

The pur org in the org model points to R/3 and same is the case in the definiton of backend system in IMG where the R/e system has been defined as the BE system.

The strange part is that this error is not happening in our sandbox client, only in the unit testing client.

-Bakulesh

[Former Member]

Hi Claudia:

In another client (sandbox), I do not have the local POrg and PGrps and the system is working fine. However, in my unit testing client, I'm having this issue.

Thanks

-BAkulesh

[Former Member]

Hi

Please provide R/3 System version details.

When this error is happening ? What are the steps to replicate the same ?

<u> Are you using the Direct Material scenario. ? / Have you maintained the attribute DP_PROC_TY</u>

<u>Please check your setting for the Porg under the FUNCTIONS tab in the Org structure.The logical system should correspond to R/3.</u>

Also ensure that the purchasing org in the purchasing org node in SRM System is in the form of system RD2CLNT400. Check the backend system in SPRO. I guess it is pointing to SD2CLNT400. Either you can change the backend system to RD2CLNT400 or you can specify the purchasing org / grp from SD2CLNT400.

Do let me know.

Regards

- Atul

[Former Member]

Hi Bakulesh,

compare once again the settings with Sandbox. I am still thinking, your OrgModel

is differing. The SC pointer is set to SRM, but the Org Model is pointing to ECC.

When you do not use pure local POrg/PGroup and use the Backend Org Units

in extended classic, there still the setting is different than in classic:

Check the setting in PPOMA_BBP for POrg / Pgroup: just only set the tick box

and <i>fill the field "corresponds to";</i> <u>leave the source system field blank</u>.

Thanks,

Claudia

[Former Member]

Hi Claudia:

Can u explain "The SC pointer is set to SRM" ? Where does one set the SC pointer ?

Also, I have the confirmed from my sandbox client that I dont have any local POrg and PGrp and that system is functioning quite well. There must be a setting in my unit test client which I am missing or overlooking which is causing the error. I cannot pinpoint it.

-Bakulesh

[Former Member]

Hi Bakulesh,

in the moment, the extended classic scenario is active, SRM becomes the leading

system for the PO and a copy is send to backend. for this, SRM sets the system

information in SC to the SRM system. In your case to "SD2CLNT400" as the SRM

system. When in PPOMA_BBP, the Org Units pointing to the Backend

"RD2CLNT400", then the error message comes up, when you try to create a PO.

In SRPO the extended classic is activated via "Activate extended classic

scenario". On that screen there are two tick boxes, one for activating the ECC and

the second for using the Backend PGroups. Is that ticked as well in DEV?

When you use the Backend Org Units in extended classic, you need to ensure the

correct setting in PPOMA_BBP. Just only set the tick box for POrg / PGroup and

fill the field "corresponds to" with the Information from Backend, but leave the

source system field blank. With this the backend units can be used, but pointing

correctly to SRM. I assume, one of this settings are different between SBX and

DEV.

Cheers,

Claudia

[Former Member]

Hi Claudia:

My error is happening during SC creation not during PO creation.

[Former Member]

Hi Claudia:

I did what u suggested.

I get 2 errors now:

Enter company code

Plant for follow-on document missing

Any suggestions why ?

[Former Member]

Hi Bakulesh,

have a look into PPOMA_BBP and check the Company Code (attribute BUK)

settings for the user creating the SC as well for the PGroups. Seems there are missing the related entries; when these settings are fine, the issue should be solved. Let me know.

Cheers,

Claudia

[Former Member]

Hi Claudia:

The attribute BUK has been maintained for the user as well as the Pur Grp. But the error is still there.

Another qs. - Do we have to maintain a local pur org and pur grp ?

-Bakulesh

[Former Member]

And the plant settings? Are these ok as well? Check also if the responsiblities are

maintained at the Pgroup. The mentioned error is almost 100% related to missing

setting in attributes in PPOMA_BPP. You mentioned, it works in SBX, compare

again, if you are missing something. At the moment the system does not find a

valid information.

Cheers,

Claudia

[Former Member]

The plant settings are also maintained.

Do we have to create a local POrg and PGrp ?

In my SBX system, I did not maintain any local info and the purchasing data were pointing to the backend (basically in the Function tab, the POrg was specified and the backend system, too).

-Bakulesh

[Former Member]

Hm, getting tricky.

Local Org Units are only needed, when you are using all Org Units local in SRM.

But you mentioned, you want to use Backend Org Units.

Please have a look again: In SRPO the extended classic is activated via "Activate

extended classic scenario". On that screen there are two tick boxes, one for

activating the ECC and the second for using the Backend PGroups. Is that ticked

in your SBX as well DEV?

Cheers,

Claudia

[Former Member]

Yes, both boxes are checked.

[Former Member]

Please have a look into your settings for product category and backend system.

Are they pointing to the right system / settings same like in SBX?

Also have a look into PPOMA_BBP on the extended attributes for the responsility

of the category, that this is set to the ECS PGroup.

Cheers,

Claudia

[Former Member]

Claudia:

In my SBX system, I was not using a local POrg and PGrp. So, we cannot compare the org models since in the unit testing client, I have a local POrg and PGrp.

But my IMG settings are the same in both the systems.

[Former Member]

Hi Bakulesh,

what do you mean with "using a local POrg and PGrp"?

You mentioned, that in SBX the Backend Org Units are used? This is what I am

suggesting. This is not a local Org Unit. A truely local Org Unit in SRM would be

without any linkage to the Backend. I am suggesting / supporting, that you have

the same settings in SBX and DEV.

I am getting to the question, whether the ECS is active in your SBX?

Do you have any BADIs active to control the ECS in SBX you also expect in DEV?

Cheers,

Claudia

Points for all the different guys already replying would

be quite motivating for the whole community .

[Former Member]

ECS is active in SBX and there are no relevant BADI's associated with activation of ECS.

IN my SBX system, my org model has a Pur org which points to the backend (pur org number and the backend R/3 system) (under the Function tab). Same is the case with PGrp.

X Pur org Corresponds to 1400 RD2CLNT500

X Pur grp Corresponds to S02 RD2CLNT500

RD2CLNT500 is the backend system in SBX.

However, in RD2CLNT400 (DEV), you had told me not ot enter the backend system, so the org model entries are different.

[Former Member]

Please maintain the same setting like you have in BSX.

I told you use Backend Org Units at the trigger for ECS. In parallel the settings

in PPOMA_BBP and in SPRO - "Define Backend System for Product Category"

needs to be sync.

So far, I somehow get the feeling, that in SBX, you have a classic process in an ECS environment working. Is ECS active in SBX? For a true ECS process, the settings

should be somehow comparable to what I suggested.

Are you sure, that a true ECS is active in SBX as well DEV? Please confirm.

Cheers,

Claudia

[Former Member]

I have now maintained my system as the SBX system.

Besides the error, System RD2CLNT400 of pur. org. DOI differs from doc reference SD2CLNT400, I'm now getting another error,

System of purchasing organization O 50000XXX and purchasing group O

50000YYY differ

We have maintained the same backend system (RD2CLNT400) for both pur

org and pur grp in the org model.

[Former Member]

True ECS is active in the SBX system since I have local POs and backend POs.

[Former Member]

Thank you all.

I'm maintaining R/3 product categories only. No local ones.

We are on SRM 5.0 SP 7, and with this release you dont have to maintain local Pur org and Pur grp.

There is an option in the config for the system to see backend pur groups for extended classic scenarios.

-Bakulesh

[Former Member]

Hi Bakulesh,

the release is not the driver which POrgs / PGroups to be used.

I assume you are using extended classic with the Backend Groups.

Check the setting in PPOMA_BBP for POrg / Pgroup: just only set the tick box

and fill the field "corresponds to"; leave the source system field blank.

Thanks,

Claudia

[Former Member]

Hi Bakulesh,

besides the option Khan is suggesting, are you using pushed Reqs from ECC

in SRM? Are you using extended classic?

The error mentioned is created, when the system tries to create a PO in the

Backend (because this in the only setting currently in your system), but the SC

points to SRM for PO creation.

In order to check, create a local POrg and local PGroup in SRM to create the PO

in SRM.

Thanks,

Claudia

[khan_voyalpadusman]

Hi,

Which category are you using for the shopping cart creation , let me know.

product category can be of two types.

1.Local product category

2.Backend product category

In your customizing check the way you have maintained the settings for product categories