Accrual in account determination

Hi,
In pricing, there is an Accrual account key. And below is the defination in SAP help:
Account key - accruals / provisions
Key which identifies various types of G/L accounts for accruals or provisions.
Use
With the aid of the account key, the system can post amounts to certain types of accruals accounts. For example, rebate accruals which are calculated from pricing conditions can be posted to the corresponding account for rebate accruals.
For my understanding, we should assign it to accrual account, but in my case, it is just assigned to a revenue account, not accrual account.
Will it be a problem?
Thanks,
DL

Hi,
All the rebate conditions specifically will be assigned the accrual account key in the pricing. Base price condition types, discount condition types, tax conditions don't have this accrual key assigned.
Rebate is a special kind of discount which is paid to customer retroactively usually at the end the agreement period. This means based on the volume of the goods sold or the amount of invoice, customer will be given certain rebate which is not paid at the point of invoice but usually at the end of agreement period. This amount will get accrued and will be posted to the GL account corresponding to the accrual account key mentioned in the pricing. Except for rebate conditions you will not have accrual key assigned to other conditions in pricing. When the rebate amount is settled to customer in final settlement or with partial settlement reversal of postings happen to the accrual related GL account.
Hope this explains

Similar Messages

Accruals in account determination

Hi everybody,
My requirement is to have a Price Condition Type (CT) hit an accruals account.
I checked the Accruals box in the CT config. Then I defined a new key and tried different combinations in account determination, pricing procedure (PP) and assiging account keys. But it either hits the Accruals account twice or does not hit it at all.
For eg.
In PP, I assigned that key to my CT as Accruals Key and left Account Key blank. Then in "Assign Account Keys" I again assigned the key as accruals key to my CT. And finally in "Assign GL accounts" I assigned the accruals account # as G/L Account to the right combination of Condition Type/Chart of accounts/Sales actt and act. key and left the provsional account field blank.
But when I save the billing document (g2), it says account determination error and in analysis I read "The 2nd GL account is missing"
So in another case I gave the same account in both GL and Provisional account in "Assign GL accounts". Though this time, it creates the accounting document, but it hits the accruals account twice.
So my problem is, it is either hitting the accruals account either twice or not at all. I want it to hit it only once.
Any help is appreciated.
Regards,

Hi Michael,
I think the catch is in the 3rd step you mentioned
VKOA: input GL account and provision act to your actkey
Also frm your prevoius reply "In some cases you want to assign a GL account to the accrual act key also, then when you do billing, the money flows from the GL account to the provision account."
this has me conclude that there will be a separate GL actt and a separate Provision actt assigned to the same Actkey in VKOA. And money will flow from GL to provision.
Anyways, I think its enough head scratching for me on this issue...I need to talk to my FI guy. I really appreciate your reply.
Regards,
Vik

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

Revenue Recignition Error message - Accrual period not determined fot item

I a creating a credit memo with refrence to billing document. Revenue Recognition type is D. I am getting error message while releasing invoice to accounting "Accrual Period not determined for invoice" Message no. VFRR007
Any help would be appreciated

Dear Pankaj,
I am facing the same problem.
Scenario is similar to yours. There is no contract but a sales order.
Could you please inform how this error got resolved?
Thanks in advance.
Piyush

MIGO - Account Determination Subcontracting

I have a problem....
When the material is being posted using MIGO an error in account determination is determinated and cannot post the document.
It said:
Account determination for entry SSM FRN not possible.
I check my schedule agreement and review the ZOA1 Customs %. And its Account determination said:
Account key     FRE
Accruals           FR3
From where is taking the FRN!!!!!
I also check in customizing the following:
Material Management>Purchasing>Conditions>Define Price determination process>Define Transaction/Event keys...
From where could it get the error!!!

Hi,
   This is due to OBYC setting issue as FRN key is used for Incidental costs of external activities
For subcontracting following should be OBYC settings:
1. Stock Account (finished Account) BSX - Debits
2. GR/IR clearing Account WRX - Credits
3. Change in Stock Account BSV - Credits
4. Processing Charges/Sub Contract Charges FRL - Debits
5. Stock Account (Raw Material) BSX - Credits
6. Consumption from stock of material provided to vendor GBB (VBO) - Debits
In Case of Sub contract while doing Transfer Posting (Providing material to vendor) in MB1B or ME2O only Material document will be generated. No Accounting Document will be generated.
While Receiving the Finished / Semi finished material both Material and Accounting documents will get generated and the accounting entries will be as under
Check along with your FI consultant OBYC.
Regards
Rajesh

How to create new account determination in OBYC

Dear SAP Guru,
I'm getting error 'Maintain account determination (table T030B) for posting ST3' upon GR (posting) against PO. I noticed name of the procedure or group of procedures for which automatic postings can be generated is NOT maintain for ST3 in OBYC (Maintain FI Configuration : Automatic Posting - Procedure). Appreciate if you could show me the path or t/code how to create new procedure for ST3 & maintain in OBYC. Thank you.
rgds,
nantha

Hello Nantha,
Transaction key can be created in
SPRO - MM - Purchasing - Conditions - Define Proce determination Process - Define transaction/event key
Here go for new entries and maintain the transaction key with a description.
Then go to M/08 and maintain the transaction key in the 'acct key' field for your pricing procedure and the condition type.
Also make sure to tick the 'Accruals' tickbox in M/06 for the condition type you want to post in the account key.
Now go to OBYC and maintain the G/L accounts along with the posting keys and the posting rules as explained in my previous reply.
Regards
Gregory Mathews

Transaction key for account determination

Hi guru,
i would like to add a new transaction key for account determination to fullfil a business process .
Could you help me to find out the Transaction code in customizing?
A prompt reply is appreciated.
Thanks in advance
Vir

Dear Vir,
The G/L account determination process in G/L Accounting mostly uses the
transaction key technique to obtain the required G/L accounts for business transactions.
For Foreign currency transactions:
SPRO -> Financial Accounting -> General Ledger Accounting -> Periodic Processing -> Valuate -> Foreign Currency Valuation
Other General Ledger Transactions
SPRO -> Financial Accounting -> General Ledger Accounting -> Business Transactions -> Closing -> Carried Forward -> Define Retained Earning Account
OBA1 G/L account determination for foreign currency valuation
OBYA Maintain inter-company clearing G/L accounts
OB53 Maintain retained earnings accounts
OBBV Assign AR/AP adjustment accounts
OBXD Maintain bad debt reserve accounts
ACACAD Accrual account determination ( simple or extended )
ACACADMETASGL Accrual account determination strategy
ACACTREE01 Create accrual objects
Pricing:
        V/09    Condition Types: Account Determin.
        V/10    Account Determination: Access Seqnc
        V/11    Conditions: Account Determin.Proced.
        V/12    Account Determination: Create Table
        V/13    Account Determination: Change Table
        V/14    Account Determination: Display Table
G/L Accounts in MM Account Determination:
The program RM07C030 check all the G/L account define in your Material Master valuation class.
Search is via Company code and Valuation area.
Visit the following link for more information:
http://www.sapscene.com/sapscene/accassg.html#SD-FI%20Account%20Determination
Reward points if this is helpful.
Regards,
Naveen.

Error: Account Determination.

Hi Experts,
I have configured rebate settings. And till incoiving everything is going smooth. But at the time of saving invoice in VF01, after saving it I am getting this error of account determination. After I go to Environment->Account determination analysis->revenue accounts, and click on the rebate condition type, I found this message - "Accruals condition: The second G/L account is missing". Tell me how to take care of this thing.
Thanks in advance.

Hi,
In Tcode VKOA ,you can maintain missing G/L Account.
Take help of FI guy if feel so.
Regards,
Vikas

Why do we need account determination?

Hello,
why do we need account determinations and how can i create them for the COA?
Thanks,
-S

Hi
To create accruals and post payables, the system must first of all determine the correct G/L accounts for posting in FI.
Before the system can determine the G/L accounts, certain settings must be made in Customizing. In the IMG, select: Logistics Execution -> Transportation-> Shipment costs -> Settlement -> Automatic G/L account determination. The settings required are described in detail here.
G/L account determination is carried out automatically. The following parameters are used for determination:
Chart of accounts
Valuation grouping code
Transaction key
Account grouping
Valuation class
G/L account determination can be carried out at shipment cost item level or you can have the system carry out posting at delivery or delivery item level for a more detailed process.
Nagesh

Account determination for entry C002 ZF2 X001 not possible while doing GR

Hi,
I am facing problem while GR (MIGO) and error: Account determination for entry C002 ZF2 X001 not possible
Scenario: Client wants to capture for transport cost while doing the GR by using material group (without material).
Steps:
1. Purchase order (ME21N):
By using account assignment category K u2013 Cost centre, material group (without material) and fright condition
(Account determination: Account key FRE and Accruals ZF2)
2. GR (MIGO): error: Account determination for entry C002 ZF2 X001 not possible
Configuration made:
1. Assing material group to valuation class (OMQW)
Material group - 600000020 Office BOOKS to Valuation class Y170 BOOKS
2. Account determination for valuation class (OMWD):
Valuation area X001 - VGCd X001
3. Automatic account determination (OBYC):
FRE u2013 X001(VGCd) - Y170 (VC) u2013 606400000 (GL)
ZF2 - X001(VGCd) - Y170 (VC) u2013 408300000 (GL) (This is Z transaction key to capture transport cost).
For ZF2 transaction key above configuration was attached and still I am getting error.
Did I miss any other configuration?
Thanks in advance for suggestion.

Based on the Error message, i think account determination is not looking for valuation class Y170. This is normally included in the error message, so i think you should maintain FRE and ZF2 with valuation class as 'blank'.
Regards,
Ganesh

Error: Accrual Period not determined in invoice.

Hi Group,
I've created an invoice, but it is not releasing to accounting and giving an error as "Accrual period not determined for invoice, no revenue dist. possible." Message no. VFRR007
Can anyone please let me know where this problem is coming from....
Your input is really really appreciated
Thanks in advance.
Raa

Hi Sankar,
This invoice is not rebate related, it is a credit note.There is no any accrual key assigned to condition types in pricing procedure.
Any idea, if there is another reason causing this problem!!!
Thank u very much..
Cheerz
RAA
That invoice seems to be rebate related invoice. I think for this you have not maintained any rebate aggrement in VBO1 t.code. Please mainatain the rebate aggrement records and then retry..
More over pleae check accrual keys assigned to condition types in pricing procedure..
regards
sankar

How will i configure revenue account determination

how will i configure revenue account determination....

IMG MENUu2014Sales & Distributionu2014Basic Functions-Account assignment/ Costing-Revenue account determination
Check master data relevant for account assignment
Materials: account assignment groups
New entries
Account assignment group          Description
K1                                   Finished Products
K2                                   Service
K3                                   Trading products
Save
Customers: account assignment groups
New entries
Account assignment group     Description
KA                                   Domestic
KB                                   Export
KC                                   Internal
Save
We use condition technique to set up Account determination
Standard Condition Type     KOFI
Access sequence               KOFI
Account determination Procedure      KOFi00
Standard Tables
001          Customer/material account assign
002          Customer account assignment
003          Material account assignment
004          general
005          Account key
Use the above tables for search that is access sequence
Select define access sequence and account determination type
Maintain access sequences for account determination
Select new entries
Acc seq               Description
ZK00               Access seq for account det
Continue
Select ZK00 and select accesses
New entries
Acc          table          Description
10          1               cust/mat/account key
20          5               account key
Select 10 & 1 Combination. Select fields and activate the fields
Select 20 & 5 combination and select fields and activate fields
Save the access sequence
Fields in tables
Table          Fields
1     Sales Org, Cust account assignment grp.mat account assignment grp, account key
5     Sales org, account key
Same menu path
Define account determination type (Condition type)
New entries
Ctyp          Name               Access sequence
ZK00          Accnt det type     Zk00
Save
Define and assignment account determination Procedures
Define account determination Procedure
New entries
Proce               Description
ZK0000          Account det Procedure
Continue
Select Zk0000 and select control data
New entries
Step     Cntr     Condition Type
10          0          ZK00
Save
Assignment account determination Procedure
(Assign the procedure to all the Billing document types)
Position ZKF2
ZKF2                    ZK0000
Save
Define and assign account keys
Define account Key
Account key          Description
ERL                    Sales Revenues
ERS                    Sales deductions
ERF                    Freight revenue
MWS                    Taxes on sls/purchase
ERB                    Rebate sales deductions
ERU                    Rebate accruals
EVV                    Cash clearing
Account keys are assigned in the pricing procedure against various condition types
PR00                    ERL
K004                    ERS
K005                    ERS
KF00                    ERF
MWST                    MWS
B001 to B005          ERB               ERU
B001 to B005 are Rebate discount condition types
Assign GL accounts
(Here we maintain information in tables, which will be searched by system for selecting GL accounts)
Select table 1
Select details button
App= application, select V for sales
Condition type= Account determination type (ZK00)
Ch= Chart of accounts= INT
(Chart of account is assigned to company code and has the complete list of GL accounts used for business)
SORG= sales org which is involved in revenue generation/ sales unit
Au2026= Customer account assignment Group
AAG. = Material account assignment group
Actky= Account key like ERL etc
GL account No=the GL accountu2013NO maintained in Chart of accounts
Select new entries and maintain the following
Select Table number 5 to maintain GL accounts for tax, Rebates and cash clearing
MWSu2014175000
ERBu2014884000
ERU     884010          89000
EVV     10000
Create Order; Delivery, PGI and then billing document, when the Billing document is saved account determination should happen
hope this will help u
Regards
nitin

Account determination for entry GIL ___ GIL ___ 6120 not possible

Hi Friends,
During GR using MIGO t-code I am getting the followin message.
"Account determination for entry GIL ___ GIL ___ 6120 not possible"
Here Transaction key and Account grouping code is not provided in error message.
Actually, we have checked Purchase account Processing in t-code OBY6 after opening purchase order offset entries, you are getting this message, also this message is not occuring for all purchase orders and if we remove offset account entries check in OBY6, system allowing to make GR.
Please suggest the solution for raised issue.
KRaheja.

Hi
You marked delivery costs tab in IMG - MM - valuation and account assignment - Account Determination - Account Determination Without Wizard - Purchase Account Management - Calculation of Value for Purchase Account which will post delivery costs to price difference account?
And also check the calculation schema - all the delivery conditions have account key as FRE and accruals as different transaction keys.
Thanks

Business transaction key in account determination..?

Hi all
Can anybody explain me in simple form form, what is business transaction key in account determination , for eg, GBB,BSA,BSX,PRD,VBR,.WRX....etc (Approximately 60 transaction keys in std SAP)
If i want to do configuration the for new client, what are all the business transaction key,,, How the configuration wil happen..?
Pls giv me expaination,
Reply will be rewardable..
Thanks
sap-mm

Hi MM,
Please Search in SDN threads solution is given already in lot of threads.
Go to SAP Library
SPRO> Help> SAP Library
Or go to SPRO> IMG> MM>Valuation and Account Assignment>Account determination> Account det without wizard> configure Automatic postings
Click on IMG ACTIVITY DOCUMENTATION
These transactions are important for Accounts.
Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting.
Example:
Posting lines are created in the following accounts in the case of a goods issue for a cost center:
Stock account
Consumption account
Agency business: income (AG1)
This transaction can be used in agency business for income deriving from commission (e.g. del credere commission). The account key is used in the calculation schemas for agency business to determine the associated revenue accounts.
Agency business: turnover (AG2)
This transaction can be used in agency business if turnover (business volume) postings are activated in Customizing for the payment types. The account key is specified in Customizing for the billing type.
Agency business: expense (AG3)
This transaction can be used in agency business for commission expenses. The account key is used in the calculation schemas for agency business to determine the associated expense accounts.
Expense/revenue from consumption of consignment material (AKO)
This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
Expenditure/income from transfer posting (AUM)
This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
Provisions for subsequent (end-of-period rebate) settlement (BO1)
If you use the "subsequent settlement" function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.
Income from subsequent settlement (BO2)
The rebate income generated in the course of "subsequent settlement" (end-of-period rebate settlement) is posted via this transaction.
Income from subsequent settlement after actual settlement (BO3)
If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the "subsequent settlement" facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.
Supplementary entry for stock (BSD)
This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.
Change in stock (BSV)
Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
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
Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.
Revaluation of other consumption (COC)
This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.
Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger application. This revaluation can either take place in the account where the original postings were made, or in a header account.
The header account is determined using the transaction/event key COC.
Del credere (DEL)
Transaction/event key for the payment/invoice list documents in Purchasing. The account key is needed in the calculation schema for payment/settlement processing to determine the associated revenue accounts.
Small differences, Materials Management (DIF)
This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
These transactions are used only if Purchase Account Management is active in the company code.
Note
Due to special legal requirements, this function was developed specially for certain countries (Belgium, Spain, Portugal, France, Italy, and Finland).
Before you use this function, check whether you need to use it in your country.
Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)
These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.
You can also enter your own transactions for delivery costs in condition types.
External service (FRL)
The transaction is used for goods and invoice receipts in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
External service, delivery costs (FRN)
This transaction is used for delivery costs (incidental costs of procurement) in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
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:
Purchase order with account assignment (KBS)
You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.
Exchange Rate Differences Materials Management(AVR) (KDG)
When you carry out a revaluation of single-level consumption in the material ledger for an alternative valuation run, the exchange rate difference accounts of the materials are credited with the exchange rate differences that are to be assigned to the consumption.
Exchange rate differences in the case of open items (KDM)
Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
Differences due to exchange rate rounding, Materials Management (KDR)
An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.
Exchange Rate Differences from Lower Levels (KDV)
In multi-level periodic settlement in the material ledger, some of the exchange rate differences that have been posted during the period in respect of the raw materials, semifinished products and cost centers performing the activity used in the manufacture of a semifinished or finished product are debited or credited to that semifinished or finished product.
Consignment liabilities (KON)
Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.
Depending on the settings for the posting rules for the transaction/event key KON, it is possible to work with or without account modification. If you work with account modification, the following modifications are available in the standard system:
None for consignment liabilities
PIP for pipeline liabilities
Offsetting entry for price differences in cost object hierarchies (KTR)
The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.
Accruals and deferrals account (material ledger) (LKW)
If the process of material price determination in the material ledger is not accompanied by revaluation of closing stock, the price and exchange rate differences that should actually be applied to the stock value are contra-posted to accounts with the transaction/event key LKW.
If, on the other hand, price determination in the material ledger is accompanied by revaluation of the closing stock, the price and exchange rate differences are posted to the stock account (i.e. the stock is revalued).
Price Difference from Exploded WIP (Lar.) (PRA)
If you use the WIP revaluation of the material ledger, the price variances of the exploded WIP stock of an activity type or a business process are posted to the price differences account with transaction/event key PRA.
Differences (AVR Price) (PRC)
In the alternative valuation run in the material ledger, some of the variances that accrue interest in the cost centers, are transfer posted to the semifinished or finished product.
Price differences (PRD)
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
None for goods and invoice receipts against purchase orders
PRF for goods receipts against production orders and
order settlement
PRA for goods issues and other movements
PRU for transfer postings (price differences in the case
of external amounts)
Price Differences (Material Ledger, AVR) (PRG)
When you carry out a revaluation of single-level consumption in the material ledger during the alternative valuation run, the price difference accounts of the materials are credited with the price differences that are to be assigned to the consumption.
Price differences in cost object hierarchies (PRK)
In cost object hierarchies, price differences occur both for the assigned materials with standard price and for the accounts of the cost object hierarchy. In the course of settlement for cost object hierarchies after settlement via material account determination, the price differences are posted via the transaction PRK.
Price Difference from Exploded WIP (Mat.) (PRM)
If you use the WIP revaluation of the material ledger, the price and exchange rate differences of the exploded WIP stock of a material are posted to the price difference account with transaction/event key PRM.
Price differences, product cost collector (PRP)
During settlement accounting with regard to a product cost collector in repetitive manufacturing, price differences are posted with the transaction PRP in the case of the valuated sales order stock.
This transaction is currently used in the following instances only:
Production cost collector in Release 4.0
Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
Offsetting entry: price differences, product cost collector (PRQ)
The offsetting (contra) entry to price difference postings (transaction PRP) in the course of settlement accounting with respect to a product cost collector in repetitive manufacturing in the case of the valuated sales order stock is carried out via transaction PRQ.
This transaction is currently used in the following instances only:
Production cost collector in Release 4.0
Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
Price Differences from Lower Levels (PRV)
In multi-level periodic settlement in the material ledger, some of the price differences posted during the period in respect of the raw materials, semifinished products, and cost centers performing the activity used in a semifinished or finished product, are transfer posted to that semifinished or finished product.
Price differences for material ledger (PRY)
In the course of settlement in the material ledger, price differences from the material ledger are posted with the transaction PRY.
Expense and revenue from revaluation (retroactive pricing, RAP)
This transaction/event key is used in Invoice Verification within the framework of the revaluation of goods and services supplied for which settlement has already taken place. Any difference amounts determined are posted to the accounts assigned to the transaction/event key RAP (retroactive pricing) as expense or revenue.
At the time of the revaluation, the amounts determined or portions thereof) are posted neither to material stock accounts nor to price difference accounts. The full amount is always posted to the "Expense from Revaluation" or "Revenue from Revaluation" account. The offsetting (contra) entry is made to the relevant vendor account.
Invoice reductions in Logistics Invoice Verification (RKA)
This transaction/event key is used in Logistics Invoice Verification for the interim posting of price differences in the case of invoice reductions.
If a vendor invoice is reduced, two accounting documents are automatically created for the invoice document. With the first accounting document, the amount invoiced is posted in the vendor line. An additional line is generated on the invoice reduction account to partially offset this amount. With the second accounting document, the invoice reduction is posted in the form of a credit memo from the vendor. The offsetting entry to the vendor line is the invoice reduction account. Hence the invoice reduction account is always balanced off by two accounting documents within one transaction.
Provision for delivery costs (RUE)
Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.
Taxes in case of transfer posting GI/GR (TXO)
This transaction/event key is only relevant to Brazil (nota fiscal).
Revenue/expense from revaluation (UMB)
This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
Expenditure/income from revaluation (UMD)
This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.
Unplanned delivery costs (UPF)
Unplanned delivery costs are delivery costs (incidental procurement costs) that were not planned in a purchase order (e.g. freight, customs duty). In the SAP posting transaction in Logistics Invoice Verification, instead of distributing these unplanned delivery costs among all invoice items as hitherto, you have the option of posting them to a special account. A separate tax code can be used for this account.
Input tax, Purchasing (VST)
Transaction/event key for tax account determination within the "subsequent settlement" facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.
Inflation posting (WGB)
Transaction/event key that posts inflation postings to a different account, within the handling of inflation process for the period-end closing.
Goods issue, revaluation (inflation) (WGI)
This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.
Goods receipt, revaluation (inflation) (WGR)
This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.
WIP from Price Differences (Internal Activity) (WPA)
When you use the WIP revaluation of the material ledger, the price variances from the actual price calculation that are to be assigned to the WIP stock, an activity type or a business process are posted to the WIP account for activities.
WIP from Price Differences (Material) (WPM)
When you use the WIP revaluation of the material ledger, the price and exchange rate differences that are to be assigned to the WIP stock of a material are posted to the WIP account for material.
GR/IR clearing (WRX)
Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders. For more on the GR/IR clearing account, refer to the SAP Library (documentation MM Material Valuation).
Caution
You must set the Balances in local currency only indicator for the GR/IR clearing account to enable the open items to be cleared. For more on this topic, see the field documentation.
GR/IR clearing for material ledger (WRY)
This transaction/event key is not used from Release 4.0 onwards.
Prior to 4.0, it was used for postings to the GR/IR clearing account if the material ledger was active. As of Release 4.0, the transaction is no longer necessary, since postings to the GR/IR account in parallel currencies are possible.
Reg,
Ashok
assign points if useful.

G/L account determination for shipment cost

Hi Experts,
I am having a problem setting up account determination for shipment cost document.
When saving shipment cost document, SAP generates "service entry sheet" (PO) and GR with accounting document,
but I would like to change the default G/L account by shipping condition type.
So far, I have set up automatic G/L account (OBYC), GBB and WRX, but I could only define the default one.
Could you please advise if it is possible to change G/L account for freight accrual?
and if yes, how to change G/L account determination by shipping condition type?
Thank you
JK

Hi,
1. Menu Path: Logistics Execution > Transport > Shipment Costs > Pricing > Pricing Control > Define And Assign Pricing Procedures
Transaction Code: SPRO
Shipment pricing procedure is same as the standard pricing procedure and uses condition technique to retrieve the data from condition tables.
2. Pricing Procedure Determination for Shipment Costs:
Based on the combination of Item category Determination group, Service Agent Procedure Group, Shipping Type Procedure Group, pricing procedure is determined
Menu Path: Logistics Execution > Transport > Shipment Costs > Pricing > Pricing Control > Define And Assign Pricing Procedures
3. Search Procedure for the PO:
TPPt: Transportation planning point is taken from the shipment document
SCTy: Shipment Cost type is taken from the shipment cost document
POrg: /Pgr/Plant: Purchasing Organization, Purchasing group and Plant is assigned to the combination of TPPt & SCTy.
On these values the purchase order is searched for the Vendor mentioned in the shipment document
Menu Path: Logistics Execution > Transport > Shipment Costs > Settlement > Assign Purchasing Data
4. Automatic G/L account Determination
I hope this information will help to you.
Thanks & Regards
Raju
From the Transaction u201CGBBu201D and combination of General Modification key u201CVBRu201D and valuation class the G/L account is determined for the posting to the freight accounts.
Menu Path: Logistics Execution > Transport > Shipment Costs > Settlement > Automatic G/L Account Determination
From the Transaction u201CWRXu201D and value of valuation class as u201C u201C the G/L account is picked for GR/IR accounts.

Accrual in account determination

Similar Messages

Maybe you are looking for