cancel
Showing results for 
Search instead for 
Did you mean: 

No location and purchasing group assignement in SC for a MDM material

Former Member
0 Kudos

Hello,

I try to create a SC for a MDM1.0 catalogue material but I can not assign the location and the purchasing group in the SC, the match-code are empty.

For a replicated material from ECC6 is okay.

The user is assigned/inherited in PPOMA to the attributes location, purchasing group and product category.

We use SRM5.5 and MDM1.0. I try to find the solution in a OSS note without success.

Some one can help?

Cheers,

Marta

PURCH_GRP O 50000762 140

PURCH_GRPX D01CLNT190140 140

PURCH_ORG O 50000760 4000

PURCH_ORGX D01CLNT1904000 4000

WRK D01CLNT190000000014340004000 4000

Accepted Solutions (0)

Answers (2)

Answers (2)

masa_139
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Marta,

Please test adding materials from internal goods not from MDM. Do you get same error ? I think the MDM is not relevant for your problem.

Regards,

Masa

Former Member
0 Kudos

Hello,

Thank you very much for your comments.

I have only the missing location and purchasing group assignement in SC for a MDM material. For replicated materials SRM55 indenties de location and purchasing group, even I can change the default data.

In the customizing transacion "Activate Extended Classic Scenario"

BBPBEEKGRP: "back-end purchasing group responsible" is activated.

BBPEXPO: "Extended Local Purchase Order" is not activaded.

The user has the location and purchasing group as default data in PPOMA_BBP - Process Organization Model.

We are in

SRM_PLUS 550 0007 SAPKIBK007

SRM_SERVER 550 0007 SAPKIBKT07

So the note 944918 was implemented.

Cheers,

Marta

Former Member
0 Kudos

Hi

What happened with the earlier OSS notes I told you earlier in my reply.

Have you raised any OSS message with SAP yet ?

Do let me know.

Regards

- Atul

Former Member
0 Kudos

Hi,

As Atul said, I think <b>Note 944918 - ECS: Find back end purchasing group as a responsible group</b> will do it for you.

We had similar problem earlier today but after we flagged "background purchasing group as responsible", everything worked nicely.

//Henrik