on 05-22-2015 11:28 PM
Hi Everyone,
I am trying to determine how to post to the correct GL when I MIGO a PO with no account assignment category
Below is the accounting document generated from MIGO – I’m not sure why some of the amount is going to 261000, it should all go to 112060
However, something changed in the system between this test and the current test that follows, I am trying to determine what changed so I can fix it
When I replicate these steps, I cannot MIGO because a different GL is triggered upon goods receipt and the system needs a CO object to allow this posting
Step 1 – create PO with BLANK acct assn cat
Step 2 – MIGO
ERROR
Does anyone know why this new GL is posted to when I MIGO?
Moderator message
I think your screenshot is now distracting from your real issue and the initial question.
If this discussion continues about this new screenshot then I will lock it because this KI235 error message was discussed already some hundred times.
Just to wrap this up again, you want know why the account 261000 was hit.
You testing failed for a different reason.
This in general tells me already that the customizing got changed between the original posting and today, so you should logon to your development client and see what the change log says.
Now the folks can focus to on the initial issue, the new issue with your testing was already discussed up to exhaustion
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is one question here and two accounts - one account is providing the error. I want to know why the 261000 and 601900 accounts are hit by this posting - the later account is what's providing the error.
I know what this error means and how to fix it, the issue is that the P&L account providing the error should not be part of this transaction, nor should 261000. Only the inventory balance sheet account 112060 should.
I have now changed settings back to the original screenshot, the error is no longer triggering. So yes, now the only issue is why is 261000 being triggered when I MIGO a PO with blank acct assn cat rather than the GL assigned to both the valuation class for material and BSX transaction.
I deleted the GL in PRD from OBYC, but the system requires me to maintain PRD in order to MIGO even when there is no price difference.
According to your initial screenshot, PO has price condition PR00 = 777 USD per 1 EA
Material is has price control = S with standard price = 18 & stock = 0.
Therefore, GR of quantity 10 should have the following posting.
BSX = 18*10 = 180 +
WRX = 777*10 = 7770 -
PRD = 7770-180 = 7590 +
This PRD posting is as expected on account of the price difference between the PO and the Material Master.
Moderator message: I am going to lock this discussion now as this is just basic knowledge. And it is well explained in help.sap.com what a standard price is and how valuation postings are made.
the standard price is the price to which you valuate your stock,
the price in the PO is the price to which you buy your materials.
Ideally it should be close to one other.
But you may have some reasons why you or somebody else entered 18$ as standard price while you have to pay 777 $ to your vendor. Check the change history and talk to the two parties who deal with prices (accounting and purchasing)
Hi,
Go to SE16 Tcode and Enter Table "T030".
Here enter G/L account 261000 then execute. now you can find Transaction Keys for this G/L account.
Now try analysis why this g/l account is triggering.
Regards,
B V
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Material or PRD GL comes during MIGO based on your price indicator in material master.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear,
What are the settings maintained in OKB9.
Hope OKB9 will will help you.
Regards,
Pardhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Joe,
Please go through the following link to have a better understanding of how G/L Accounts are triggered.
Kindly revert if you need have any more questions.
Br,
Raghu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Go to OBYC, and find out whether the GL is assigned to the account key.
Check SPRO-->IMG-->Materialmanagement-->Valuation and account assignmnet-->Account determination-->Account determination with out wizard-->Define accounting grouping for moment types
Here check out whether the account have been defined for the movement type for which you are using in GRN.
Thanks,
Hassan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear,
Check SPRO-->IMG-->Materialmanagement-->Valuation and account assignmnet-->Account determination-->Account determination with out wizard-->Define accounting grouping for moment types.
Here we are having "value strings", this value strings determines the G/L account at the time of GRN posting for all moment types.
Regards,
Pardhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Joe P
point 1. refer transaction event key and go to OBYC transaction refer gl accounts assigned for account key
point 2. refer tax code assigned to PO and go to OB40 transaction refer gl accounts assigned for account key
hope with this you come to know why GL appering
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seems some screen shots are missing. What is the transaction key involve in this accounting entry ?
Check is there any difference with PO price and material price in material master ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Joe,
Could you please check the field status group (Under Create/bank/interest tab) of the account in FS00 by entering the G/L# 601900 and the right Company Code#.
It could be that the Field Status Group that has been assigned to the G/L which has this problem is having the CO assignment mandatory.
Please check with your FI colleagues who might help you in changing this entry to "Optional" or choosing a different Field Status Group for the same G/L.
Refer to the following thread for more info:
Br,
Raghu
User | Count |
---|---|
107 | |
12 | |
11 | |
6 | |
5 | |
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.