If Material ledger is Active CR is not going to Activate.

[former_member193063]

Hello,

While during Material Creation/Change we want to Create/Update  respectively both case for Valuation Accounting/Costing data .But We are unable to Activate Change Request . Error Message come like this .

Cannot update valuation data for TEST-ALL-DATA/XXXX; plant set up for material ledger....

Case-1 In our case Material Ledger is Active at Plant Level .

Comment : We don't want to deactivate this is our requirement.

Case -2: We Don't want to go MM01/MM02 to Create/Change Valuation Accounting/Costing Data.

Comment : We want to do this activity with in MDG-M

Case-3 We already know Snote: 1806108 there Point No : 21.

Our requirement is that we have to create/change Valuation accounting/costing data with in MDG.

So plz help us how to achieve this if Material ledger is Active at plant level.

I appreciate any help.

Thanks

Nikhilesh Agarwal

[former_member188878 · Accepted solution]

close this thread we have resolved this right.

[dharamveer_gaur2 · Accepted solution]

Hi Shankar,

I am getting this same error and not able to create CR with Valuation data.

Valuation Area is same as Plant.

We found that MDG method BWKEY_CHECK_MATERIAL_LEDGER checking T001k table for field MLBWA (Material ledger activated in valuation area) and throwing this error.

Kindly let me know solution for this.

Thanks,

Dharamveer

[former_member188878 · Accepted solution]

Dharam

please comment the code in that class,which checks the material ledger active will resolve the issue.

[d024348 · Accepted solution]

If you modify your system like this, please bear in mind that any data inconsistencies (e.g. missing MBEW-MLAST and others) will not be covered by the complimentary SAP support and might lead to inconsistencies in transactional data (e.g. purchase orders). These checks were introduced with a reason, removing them is at your own risk.
Regards, Ingo Bruß

[former_member188878 · Accepted solution]

Ingo,

yes,you are right modifying the SAP in not a solution but let us know

1.what are all the data inconsistencies your are taking about.?

2. you mean to say that the method BWKEY_CHECK_MATERIAL_LEDGER is used some where else while creating the Transation data?.

3. If this change is effecting the transational data,then why it is allowed with MM02 tcode?

tell us the specific reason why the user has to go back to MM02 to make the changes ?.

and what is the thought behind this code,it was not there in MDG 6.0 so you mean to say there was inconsistencies and SAP come up with this code to address that in MDG 7.0.

[d024348 · Accepted solution]

Support for Material Ledger was implemented in MM01/MM02, so there will be no inconsistencies when you use MM0x to update the accounting/costing data for a material ledger plant (as recommended).

For legal reasons, we can't make any roadmap statements on SCN concerning MDG-M.

[dharamveer_gaur2 · Accepted solution]

Hi Shankar,

I have already tried code comment but and creating Accounting/Costing view but we have face issue when creating CR with multiple Plant.

MDG API are removing data while sending to active are. Below are the messages

  I140(MG): “The field & is not ready for input and was therefore not transferred”

  I141(MG): “The field & is not ready for input and was therefore not initialized”

Thanks,

Dharamveer

[former_member188878 · Accepted solution]

comment only this three lines only not other lines....

MESSAGE e020(mdg_bs_mat_api) WITH ls_bwkey-matnr ls_bwkey-bwkey INTO lv_dummy.
MOVE-CORRESPONDING syst TO ls_message.
INSERT ls_message INTO TABLE et_message.