MARC RP parameters getting copied during a new site listing

[Former Member]

Dear Retail experts,

MARC( - RDPRF rounding profile) parameter is getting copied with a value albeit none is present for that article and Ref Site validity in Log store/DC View of Art Master. This happens when a new site created is added to an assortment in which articles exist. After the listing job completes creating segments , I check the article in MM43 Log store tab with new site as validity and I see the rounding profile populated. Now when I just enter in MM42 Log Store new site validity I do not see it and when I just save and check change documents , I can see that old value had the rnd prof and new value is blank.

To explain more , the supply source is 2 for log store .Also Log Dc do not have the rounding profile populated for Ref DC or for other listed DCs. Rounding profile is only maintained in purchasing view.

These articles are differently maintained in Log View for diff stores , MABW shows differences.

I have checked Field group settings , copy and propose are ticked for MARC-RDPRF, EINE - RDPRF .

Where is the rounding prof copied from in this case?

It causes a lot of discrepancy because we refer the field for other interface functionally when creating POs.

There are 1000's of articles in the client and highly difficulty to remove the Rdprf using mass Txns everytime a new site is created and listed.

Kindly advice in detail and query if required , I will immediately post answers.Please consider this question urgent.

Thanks in advance to all of you.

[Former Member · Accepted solution]

Hi Jae,

We had a similar issue where in the RP Group and the Stock Planner used to get picked and populated in Dc and Store views for other DC and Sites when articles where extended to different sites through LSMW. As they were not defined for other sites, there would be errors after entering MM42 transaction and trying to save after changing certain fields.

Hence the workaround we used was to create the defaulting rogue stock planners and RP groups to all the sites. It worked because we do not use the fields for our planning purposes .(Though Configurations were made) .

We are yet to ascertain the similar behavior !

[Former Member]

HI,

Thanks for the comment , could you please explain the work around in detail please.

[Former Member]

Hi Jae,

As i have mentioned in my earlier post we created the defaulting stock planner for all the sites as we do not use them with a function/purpose .hence the error of stock planner xxx not created for site xxxx was solved.

[Former Member]

HI techie ,

THanks for writing again , I happened to solve the issue using a different approach , will share it in few days for sure once the customer applies it in production .