Not Allocated Variances in ML Closing - CKM3N

[zainm_bashir]

Hello Experts,

After executing ML Closing Run successfully, We witnessed that there are some materials which has NOT ALLOCATED Price Differences.

Scenario is that We produce materials in Production Plant then perform stock transfer from Production Plant to Selling Plants.

We witnessed that this issue is happening on all Stock Transfers made between Plants. When we checked  materials on receiving plants, we witnessed that these materials are having messages "Multilevel Price Determ. not Required"

Please advice how to fix this issue and allocate these variances to respective materials?

Regards,

Zain Bashir

[bhaskar_basam · Accepted solution]

Hi Zain

Do below settings

1) Define movement type group for ML update - select reval consumption as "2"

2) Assign movement type groups for ML update - Here map above defined movement type group to movement type 641.

Regards

Bhaskar

[zainm_bashir · Accepted solution]

Hello Bhaskar,

May be you have hit the right nail.

I checked Value Flow Monitor and found that they are making Material Transfer Postings from Movement Type 641 instead of 301 therefore system is not able to absorb these variances to next level.

Please confirm if this will be resolved once i will configure the needful and what about the mess created this month already? How to absorb that?

Regards,

Zain Bashir

[bhaskar_basam · Accepted solution]

Hi Zain,

Yes above config will resolve the unabsorbed variances generated during 641.

You need to reverse the ML closing and re-run all the steps to eliminate the above differences

Regards

Bhaskar

[former_member493884 · Accepted solution]

Also as per Note 2123418

After the setting for Material Update (mention above),

1) Define movement type group for ML update - select reval consumption as "2"

2) Assign movement type groups for ML update - Here map above defined movement type group to movement type 641.

Now If you put the two plants in two different costing runs, system can't allocate the price difference.

[former_member493884]

Also as per Note 2123418

After the setting for Material Update (mention above),

1) Define movement type group for ML update - select reval consumption as "2"

2) Assign movement type groups for ML update - Here map above defined movement type group to movement type 641.

Now If you put the two plants in two different costing runs, system can't allocate the price difference.

[OwenLiu]

Hi Zain,

Seems the movement type is recognized as single level consumption.

You need to set movement type group for the relevant movement type

IMG - Controlling - Product Cost Controlling - Actual Costing/Material Ledger - Material Update

Define Movement Type Groups of Material Ledger

Assign Movement Type Groups of Material Ledger

Then you have to run Revaluation of Consumption step in CKMLCP.

KBA 2123418 & Note 908776 are relevant for this issue.

Best Regards,

Owen

[raymond_moynihan]

Hello Zain,

Firstly, I would check the results of the Multilevel step and verify if

the Multilevel price determination was executed. You can use the Value Flow Monitor. You

can analyse the "Not included/Not allocated" price differences.

Please also review the note 855387:  Application of this note will create an additional

selection parameter for step 'Single Level Price Determination' to

switch on/off price limiter logic.

Also check whether the System applied a fallback strategy during price determination (see

note 579216) to avoid a negative periodic unit price (PUP).

Please check the attached  note 579216: If the regularly calculated PUP

(based on  'Cumulative Inventory' line) would become negative, the

system uses a different strategy to calculate the PUP:

The PUP is calculated with these priorities:

1.'Cumulative Inventory' line (no fallback)

2.Receipts ('ZU') line (Info message C+ 135 in the log)

3.Beginning inventory ('AB') line  (Info message C+ 138 in the log)

4.PUP-price of previous period (Info message C+ 136 in the log)

5.S-price (Info message C+ 137 in the log).

The fallback strategy is active by default for Single-Level price

determination.

For multilevel price determination it must be activated with parameter

'Negative price: automatic error management'

Thanks and regards

Ray

[Former Member]

Hi Zain,

For several reasons, price differences are not allocated 100%.

First thing check material price indicator is S/3 is set in receiving plant or not?

May be small differences or material price indicator issues or consumptions are recorded in one period and GR in other period etc

Check these oss notes for reference.

2134733

673709

744090

Thanks,

Rau

[kamalkumar_biswas2]

Hi Zain

I think your Receiving Plant Mat is not defined as S&3 and thats why it is not taking Multilevel price diff ...  so make it corrected..

Kamal

[zainm_bashir]

Dear Kamal,

We have defined all plants as ML Relevant.

Thanks

[zainm_bashir]

Any advise please?