on 01-18-2011 10:55 AM
Dear All,
We have implemented the Costing based COPAand while posting the PGI we are getting the follwing error.
" Account determination for entry GBB ,VAY 3000 is not possible"
How to resolve this problem w/o creating cost element for COGS
Whether we should update GBB and VAY through OBYC or any steps
Please help us.
Regards,
Vishwanath
Hi,
Have you done any technical upgrade or support pack upgrade?
Regards,
Akhil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please read note 77764
regards
Waman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Account determination for entry GBB ,VAY 3000 is not possible
Please search the forum before posting. Many times this topic was discussed and had you searched in google, you will find many threads.
Coming to your issue, go to OBYC, select Transaction GBB and maintain for the above combination.
thanks
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
this seems to be configuration error for the valuation class,which is 3000(this is aassigned in mmr screen of that material for which you are trying to do p.g.i.)
so in order to resolve this you have to make the relevant configuration in MM ACCOUNT DETEMINATION which can bve done through tcodeobyc.
-go to obyc
-search for gbb key
-double click and assign the values which are missing there
also,
if you can see the error screen in detail you can also find the +proceed+ option to correct this error.
revert if helpful
Mohit Singh
hi
GBB-VAY Account must be a cost element. So creat cost element.
kkumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
It seems you are in MTO scenario... i.e. your sales order is a Cost Object... thats why you need COGS as Cost element in GBB-VAY
To determine your sales order is a CO object or not.....
1. Go to sale order, procurement tab
2. Check whats the req type
3. Go to OVZH and check whats the req class assigned to this req type
4. Go to OVZG and check whats the acount assignment cateory in req class
5. The account assignment catg shud have consumption posting field as E or V
BR, Ajay M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ajay,
Sorrry for late. I have gone thorugh and checked what u said to check. But still problem remain unsolved. Please clarfiy the followings.
1) Whether we need to create the cost element for COGS to resolve the above problem.
2) If we create the cost element, is it possible to get the cost breakup (as per cost comp structure) in COPA
3) Is there any impact in costing / Accounts, if we create cost element for COGS.
4)Any other steps to be taken to flow the Cost breap up in COPA.
Thnaks in advance.
Regards,
Vishwanath
Hi
If you are in MTS, you should not create COGS as cost eleemnt
In the 5 steps that I mentioned, Your account assignment category (AAC) should be blank... Is it blank?? If yes, then you can not get this error...
If it is blank and still you getting this error, then create an OSS message.. But, am sure beyond doubt that you cant get this error message if AAC is blank
BR,Ajay M
Hi Viswanath/Ajay Maheswari,
I gone through your entire discussion, The same error i am getting.
Account determination for entry 1000 GBB 0001 VAY 9302 not possible:
Scenario:
1)MTS Scenario,
2)I dont want to create GL as Cost element, Routed thorugh COPA.
3) Below five steps also i checked with my SD Consultant, Ok no issues.
1. Go to sale order, procurement tab
2. Check whats the req type
3. Go to OVZH and check whats the req class assigned to this req type
4. Go to OVZG and check whats the acount assignment cateory in req class
5. The account assignment catg shud have consumption posting field as E or V
Help me in this regard
Manoj Kumar Pedada
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.