on 04-10-2013 11:50 AM
Hi Experts,
Amount in LC is not showing in MB51 T-Code for some newly created raw materials for which 103 & 105 movement is done first time. Though this amount is coming in PO history and GR documents. Material Ledger is also activated with price control "v" that is "Moving Average Price".
What can be the probable reasons for the amount not coming in MB51? Please throw some light on it.
Thanks in advance.
Regards,
Prerna Garg
Hi
Pls check Fi document for good receipt & verify the transaction event key BSX is hit or not.
As per my observation, if whole amount is hit to PRD it will not reflect in MB51
Or It may Good receipt for subcontracting also.
Pls verify & confirm.
Regards
Gadgil D.R.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gadgil D.R.,
I checked all FI docs. BSX, WRX & PRD are hit at the time of 105. Below are the FI entries generated at the time of 105-
ML Doc type FI Entry - RM Domestic A/C (BSX) 100000
To Loss Ext. Proc PRD A/C (PRD) 100000
WE Doc Type FI Entry- Loss Ext. Proc PRD A/C (PRD) 100000
To GR/IR A/C (WRX) 100000
As per my observation, if whole amount is hit to PRD it will not reflect in MB51
yes, the whole amount is hit to PRD and I want to know the reason for that.
Hi,
The problem is that ML is activated.
Please read note 689189 for your reference to understand this system
logic:
---------------------------------------------------
The material document does not contain the inventory value that was
posted. The inventory value specified in the material document (MSEG-DMBTR
field) does not contain the value that was posted to the inventory
account, because it does not contain the value of the transaction-based
settlement.
A reporting system that is based on these values (for example,
transaction MB51) delivers incorrect results, and should be converted to
material ledger documents.
Solution
You can use the method MODIFY_FI_CLOSING_TABLES of the BAdI CKML_UPDATE
to modify the rows of the transaction-based closing document, if
required. See also Note 639601.
As of Enhancement Package 3 for ECC 6.0 , the MM transactions post
according to the actual moving average price posting logic, even if the
material ledger is activated. This means the transaction-based
settlement is omitted and the related restrictions do not apply either.
For more information, see Note 1253944.
---------------------------------------------------
Thanks and regards,
Polly
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
I created a new raw material and maintained MM Info Record and QA Info Record for it.Tested a whole scenario in DEV system by creating PR/PO/MIGO and found the following results-
1) When first time 105 movement was run then the whole amount went to PRD (Price Difference) account and the entries were -
RM Domestic A/C (BSX) 100
To Loss Ext. Proc PRD A/C (PRD) 100
Loss Ext. Proc PRD A/C (PRD) 100
To GR/IR A/C (WRX) 100
Reason because MAP in Material Master is 0 and system is taking price in PO from Info record. Hence when MIGO happened, system is comparing MM's previous price (which is zero initially) and current price and the difference is posted to PRD account. Here, qty is 10 and Price is Rs.10 so total amount becomes 10X10=100
And the amount posted to PRD is not getting reflected in Amount in LC column in MB51.
2) When the second transaction is being run with different price then system posted the difference in two prices into PRD a/c and inventory a/c is posted with MM price.
RM Domestic A/C (BSX) 0.34
To Loss Ext. Proc PRD A/C (PRD) 0.34
RM Domestic A/C (BSX) 100
Loss Ext. Proc PRD A/C (PRD) 0.34
To GR/IR A/C (WRX) 100.34
Now amount in LC in MB51 is getting reflected by the amount which has gone to Inventory A/C i.e. Rs.100.
This is what I have concluded by running a whole scenario in DEV system. If anybody has more to say into this then please share your views.
Regards,
Prerna Garg
User | Count |
---|---|
98 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.