Excise Tx.type CEIV - G/L Account determination

Dear all,
I am cancelling an Excise invoice through TX.code J1IH. At the time of cancellation, G/L Account are determined. However the GL Code related to PLA are picked, actually it should pick GL code of RG23A.
Also note, while I create an excise invoice (DLFC) the GL code pertaining to RG23A are picked.
Therefore when I cancel excise invoce ie CEIV accounting entry should be exactly reverse of DLFC.
my question is ; on what basis the GL codes of PLA or RG23 A are picked?
Thanking you
Dilip

>
Dilip Ghansham wrote:
> Hi,
> Thanks for your reply.
>
> Do you have any idea on what basis GL for RG23 A and PLA are picked.
>
> Regards
>
> Dilip
Hi,
The system first checks for Balance in RG23A Register, if Balance is not available, it checks for Balance in RG23C Registers, if balance is not there then it picks the PLA register.
Cheers,
Santosh

Similar Messages

SAP CIN SD Condition Type Classification link to Account Determination

Hi,
one last Question according to Account Determination. I am facing the problem not to see the link between Condition Type Classification and the Excise Account Assignment Table in Customizing (Logistics u2013 General -> Tax on Goods Movements -> India -> Account Determination -> Specify G/L Accounts per Excise Transaction).
In Pricing Procedure i use the Account Key EXD, but i do not link that one to any Accounts. But i Calculate for example JEXP + JEXQ to JEXT.
I classify JEXP as A/R BED Percentage
I classify JEXQ as A/R BED Quantity Basedt
I classify JEXT as A/R BED Total
In Pricing Procedure i do not assign JEXT to any Accounting Key and thus even not to any account. But it is linked somehow to 'G/L account RG23A BED account' inside the Excise Account Assignment Table in Customizing. Is anybody able to describe how? Is it in another table where just defined: Classification A/R BED Total -> G/L account RG23A BED account. If yes, wich transaction code or which Customizing Path do i need to go to.
Please, need help for my understanding.
Best Regards,
Conrad

Hi
In Pricing Procedure i do not assign JEXT to any Accounting Key and thus even not to any account. But it is linked somehow to 'G/L account RG23A BED account' inside the Excise Account Assignment Table in Customizing. Is anybody able to describe how? Is it in another table where just defined:
These entries are entered manually by FI consultants.System picks these accounts whenever a relevant transaction is executed.
Regards,
Phani Prasad

SD tax G/L account determination

First, I am not a Finance person nor do I know a lot about tax configuration. My background (relevant for this issue) is in S/D pricing and associated account determination. This is an S/D tax calculation and account determination issue for the United States.
I am attempting to generate a use tax in an internal service order and then to populate the correct G/L account(s) with these tax values. The service order, which is really just a sales order, generates a statistical value for the basis and then I have pricing condition types (condition class = D (taxes), condition category = D (Tax)) specified in the pricing procedure. These tax condition types are correctly calculating the tax amount.
Normally, to point to the correct G/L account for a pricing condition type, you would configure Account Determination within S/D. The simplest form would be the usage of the account key. The account key would be specified in the AccKey column and account determination configuration would point this key to the correct G/L account.
I understand (both from my own very recent experience and also from some of the information I have read on the internet) that things might be a little bit different when determining a G/L account for tax. Originally I specified two different account keys in the pricing procedure for the tax condition types (normally I would have specified just one). I specified MW1 through MW4 in the account key column for all 4 tax condition types and MWS in the accrual column. My intent was to update the tax expense account from MW1 4 and the tax accrual account from MWS (I realize I might have this backward).
When I created a billing document, SAP would not create the accounting document. It indicated (from my recollection) that it was missing a tax code for the G/L account for the first tax condition type (YTX1). Cutting through the history, it appears that SAP needs this code to point to the correct G/L account for S/D. I also learned that there is a tax code field in the tax condition record (VK11) where you specify this code.
I am actually familiar with the configuration and setup for use tax for A/P vendor invoices. I had to perform this setup very recently. In short, I know that the tax code determines what the tax rates will be and also determines the G/L accounts. I know how to setup a situation for tax accrual (this is setup found in tax code U1).
My questions are the following:
1) Is it true that I have to use the tax code to determine the G/L accounts for taxes generated in an S/D pricing procedure? Is it possible I am doing something wrong in the S/D account determination (at the moment, not quite sure what this would have been)?
2) Is it possible that I am adversely affecting account determination by specifying an account key in the accrual column of the pricing procedure for the tax pricing condition types?
3) If we do have to specify a tax code in the tax pricing condition records in order to use the FI tax procedure to point to the correct G/L account, do we also specify the tax rates in this FI tax code or do we still specify them in the S/D tax pricing condition records? It does not make sense to have to specify these rates twice. In short, what does SAP actually use for tax calculation?
Thanks a lot Ed Seigler

Hello Edward,
The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.
SAP supplies a tax calculation procedure for each country. The procedure comprises a list of all common tax types with rules for tax calculation.
You have to define a separate tax on sales/purchases code for each country in which one of your company codes is located. Each code contains one or more tax rates for the different tax types.
Tax codes are actually configured in FI, but they play a significant role while creating tax condition records for a particular condition type.
Account keys in the account determination procedure connect the condition types to the relevant GL accounts. It doesnt have any impact on tax calculation. Its a procedure that is purely used to map GL accounts to the condition types.
Finally, i would suggest you to check at the condition record level, whether you have assigned the correct tax code to the appropriate condition type to rectify the error.
<b>REWARD POINTS IF HELPFUL.</b>
Regards
Sai

Run Time Error in Account Determination

Dear Friends
In my system using std one for account det then it posting to FI.
Now I created my own Table, Access Seq, Condition Type and Procedures after all assignment when I assign my procedures to F2 .
Then I done sales cycle upto billing, but when I am trying to save it it shows Run time Error. if assigning the Std Procedure KOFI00 to F2 then it is ok.
give me solution
Thanking You
Arun

Dear Arun,
Can you provide in detail !!
What is the error you are getting when you save the invoice
Check the settings at all these steps with compare to the standard setings.
SPRO>IMG>Sales and Distribution>Basic Functions>Account Assignment/Costing-->Revenue Account Determination.
-->Check Master Data Relevant For Account Assignment
-->Define Dependencies Of Revenue Account Determination
-->Define Access Sequences And Account Determination Types
-->Define And Assign Account Determination Procedures
-->Define And Assign Account Keys
-->Assign G/L Accounts.
I hope this will help you,
Regards,
Murali.

Account determination-urgent

hi
how the account will post in GL account during intercompany billing transaction, third party order, and STO. very urgent.
please give me the answer
regards
murali

Hi,
Apart from the above information,i would like to add one more point i.e.condition types KOFI/KOFK are controlled with the reqirement type given in the Account determination procedure.
I hope this info will add up to your query.
kiran,

MM Account Determination Exits

Greetings to all Experts -
We're trying to fix an issue here with inter-company processing and want account assignment for cost of sales for inter-company orders to flow to a separate cost of sales account than trade sales. The problem is that we do not use separate order types for inter-company nor do we use separate movement types so using standard account determination configuration, we're not able to separate this out.
Does anyone know of a standard enhancement or other method by which to accomplis this (i.e. BTE)?

These are two different postings:
BSX: stock posting
GBB: Offsetting entry for stock posting
Stock posting (BSX)
This transaction is used for all postings to stock accounts. Such
postings are effected, for example:
-   In inventory management in the case of goods receipts to own
    stock and goods issues from own stock
-   In invoice verification, if price differences occur in
    connection with incoming invoices for materials valuated at
    moving average price and there is adequate stock coverage
-   In order settlement, if the order is assigned to a material with
    moving average price and the actual costs at the time of
    settlement vary from the actual costs at the time of goods
    receipt
Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory
Management. They are dependent on the account grouping to which each
movement type is assigned. The following account groupings are
defined in the standard system:
-   VKA:     for sales order account assignment
         (for example, for individual purchase order)

New G/L account assigment MATD Excise Transaction Type

Hi expert
I need to assign a new G/L while performing TCode J1is,i am using Red Doc Type MATD
Regard
Nabil

Hi
I need to assign new G/l account for Excise Transaction Type MATD, and when i take Excise Transaction Type OTHR BED amount disappears in J1IS after clicking Enter button.
Have you maintain assessable value in J1ID for your material ? check J1ID setting for your material and plant ,vendor,material chapter ID and cenvate determination
check it
Regards
Kailas ugale

SAP CIN SD Conditon Type linked to Account Determination

Hi,
is anybody able to explain, how Condition Types like JEXP/JEXQ/JEXT, ... are linked to the account determination. In
Logitics General --> Tax on Goods Movements --> India --> Account Determination --> Specify G/L Accounts per Excise Transaction
I specify different account numbers to the Accounts. But where is it specified, which Condition Type is determining what account, for example 'G/L account RG23A BED account' or... SED, ...
Where is the link to the account key EXD and where can i influence what it is doing?
I appreciate a detailed answer.
Best Regards,
Conrad

In SD Pricing Procedure, you assign the Account Key EXD which you can see in OB40. If you double click this, you can see G/L accounts assigned to various tax codes. Also in FV11, for those condition types, you assign this tax code.
thanks
G. Lakshmipathi

No G/L account found in Account determination type ZOFK

Hi Forum,
I have several inoices for which the acct. doc is not generated thru VFX3.
In the header the Posting status shows "Posting document not created (pricing Error)"
If I look in to the inovice's account determination analysis I find for two pricing condition types follwoing message is displayed *"No G/L account found in Account determination type ZOFK"*.
Also in VKOA transaction there is no mention of ZOFK acct. det. condition type. It has all the G/L a/cs are assigned to ZOFI.
Could some body help me how to know why in invoice the system is taking the ZOFK value and not posting it to account.
Thanks.

ZOFK is the copy of KOFK account determination type.................therefore whenever you are doing any costing related accounting entry system will required G/L account and Account Key combination for ZOFK account determination type...
go to VKOA and maintain the G/L account with combination of Account key and Account determination type ZOFK...
Regards,
Ratish
u2003

No G/L account found in Account determination type KOFI

Hello everyone,
I have an issue with a billing document, it will not release to accounting. I think I know what the issue is, however I have no idea how to fix it.
When I go into the billing document, and I run an "Account Determination Analysis" for Revenue Accounts, I am getting the following error...
"Access Message Description
70 121 No G/L account found in Account determination type KOFI"
And I am seeing the following details...
Access (complete) Description
Field in condition table Field in document Value in doc.
Chart of accounts Chart of accounts KHAA
Sales organization Sales organization 0001
AcctAssgGr AcctAssgGr 01
Acct assignment grp Acct assignment grp 01
Valuation type Valuation type 1110170001
Account key Account key ERL
The account assignment group matches in the customer master as well as the material master.
The Valuation Type above is set to "1110170001". This is NOT a valid valuation type, it is not setup in OMWC or anywhere else that I can find. This valuation type should be "EPAS". if it were, then the information is setup in VKOA, and we would not get this error.
I was wondering if anyone has had this issue before? What can I do to get rid of this invalid valuation type?
Thanks in advance for all your help.
Rhonda

Hi Rhonda
Check what is the Valuation type of the Material Master Record. Also check in OMWC for the plant what is the Account category reference. Also check in OMWD wheather for the Valuation area ,properly Valuation grouping code has been assigned or not. Finally check in VKOA wheather all G/L accounts are assigned or not and what is the G/L accounts that have been assigned
Regards
Srinath
Edited by: sri nath on Oct 27, 2011 5:50 PM

Message VE121 - No G/L account found in account determination type KOFI

Currently, if an invoice has an account determination error we have to go to path VF03 -> Environment -> Acct Determination Analysis -> Revenue Account to get all the item condition record. Then we have to click each condition record in each item in order to figure out which one has account determination error (Message type VE 121).
If an invoice has 500 line items, this manual process is very time-consuming. Is there a FM or R3 Report to retrieve the information and let us know which item have account determination error? Thanks

I don't think there is one, but you can probably look at the logic of SD_ACCOUNT_DETERMINATION_SHOW and see if you can get it in some sort of internal table programatically instead of showing it.

Transaction type for Account Determination

This doubt in STO scenario:
STO - between 2 plants - different company codes under same client
Created STO from Receiving Plant in ME21N with document type NB
Based on that STO, Created Delivery in VL10B from supplying Plant
Tried PGI in VL02N from supplying Plant.
Received the Error Message as below:
Posting keys for account determination for transaction BUV do not exist
Message no. F5598
Diagnosis
The posting keys necessary for account determination for transaction BUV have not been set.
System Response
Because the posting key is missing, the system cannot generate any automatic postings.
Procedure
Maintain the posting keys necessary for transaction BUV.
After working thru OBYC found that the transaction type BUV is missing.
How to create the transaction type?
Thanks in advance
Vaidee
Edited by: Vaidee on Mar 11, 2009 10:08 AM

Thanks for the effort.
Executed TCode OBYA.
Entered the company codes.
For Company Code 1 u2013 Receivable u2013 Debit posting Key u2013 86
For Company Code 1 u2013 Payable u2013 Credit posting key u2013 96
For Company Code 1 u2013 Receivable u2013 Debit posting Key u2013 86
For Company Code 1 u2013 Payable u2013 Credit posting key u2013 96
Tried to change the posting key to 89 and 99.
Error message is :
Enter posting key with account type D, K or S
Message no. F4809
Diagnosis
You have specified a posting key which is defined for neither customer, nor vendor, nor G/L account postings
Thanks
Vaidee

PR00 120 G/L account 0000785101 determined from Account determination type

Hi all,
I am getting the following error while saving sales order.
PR00 120 G/L account 0000785101 determined from Account determination type
I dont know why this error is occuring while creating sales order. Because of this issue, i am not able to save the sales order.
How to solve this issue? Can anyone give me solution for this issue?
Thanks in advance,
Babu

Hiii
I hope you people are using COPA or Controlling in your process.
This error is basically comes if you are not maintained the KOFK setting, same where u have done your KOFI setting, you have to do same with KOFK in Transaction VKOA.
see what setting you have done for KOFI, copy that line and change KOFI to KOFK and save it.
Hope it will solve your problem
Regards
Shambhu Sarkar

Cost of Goods Sold account determination by customer type (inter-company)

We have a business need to separate the the cost of goods sold be customer type. Specifically separating the inter-company cost of goods sold from the 3rd party cost of goods sold.
The standard COGS account determination in GBB/VAX only allows for differentiating between material valuation class.
Has anyone attempted this before and what method worked?

For those who may need an answer to this, our solution was the following:
1)       Created new types for SO, SO Item, Sched. Line, Delivery, Delivery Item, Billing type
2)       Created new Pricing procedure
3)       Created new movement type Y61/Y62 modeled after 601/602
4)       Mapped Y61/Y62 to account modifier ZAX.
5)       Mapped GBB/ZAX to the new account.
Benefits, they now have better view of the orders going inter-company. It is flexible enough to adjusting prices for intercompany separate from standard orders, even though for now it is a straight copy of cost. They are able to remove the sales/use tax, from the calculations. They are able to plan with these orders separated out. Plus, this will standardize their process for inter-company.
Hope this helps someone.
Cheers!
Rick

Account determination for project stock delivery (for movement type 281Q)

Hello
We are trying to carry out delivery for project stock (CNS0) using movement type 281Q.
We notice that there is no account modifier availalbe for this scenario resulting in error during PGI. However, we can do PGI after changing the config of account determination without account modifier.
Since working without an account modifier is not acceptable for various business reasons, we must have an account modifier defined. We are wondering why SAP has not provided a standard solution for dealing with project stock delivery.
Can any one please suggest how to deal this situation.
Thanks and warm regards,
Jagadeeesh

We have business requirement as stated below:
We need to procure materials for specific Projects but also want to track the stock for the Project by value in the invnetory. In other words, the encumbrance of the procurement needs to take place against the Project but we want to be able to take it into inventory as a valuated stock and issue to the WBS whenever it is required.
Is this possible? What we know is that as soon as we give reference of the WBS for the Procurement, it gets expensed to the Project and we cannot value manage in inventory.
The reason for this requirement is there is a long time between when the item is procured and when it is used for the project. Till such time we have to track the Project items in the inventory as any other stock but its still tagged for the project and encumbrance would need to have happened
Any ideas on how to deal with this will be appreciated
Thanks
Noornie

Excise Tx.type CEIV - G/L Account determination

Similar Messages

Maybe you are looking for