Account determination at plant level
Hi All,
There is a requirement: we have 1 cocode and 10 plants are assigned to it. Valuation is to be at plant level.
There are around 15 valuation classes. While doing config for account determination, do i need to assign each combn of valuation modifier and valuation class to a different GL account for stock postings i.e. BSX ?
Thanks
Ritu
Edited by: ritu on Dec 24, 2007 8:12 AM
Hi Ritu
G/L accounts will differenciate the accounts which u procure the matls. If u maintain the same G/L account for all valuation class, for all types of materials system wil show same gl account .This will confuse the accounts person. u should differentiate the matls.
Mainthing is gl accounts to be defined by accounts people based on business process.
For ex: If u maintain same gl accounts for raw matl and finished goods, accounts guy wants to check the price that how much raw matl consumed on this month. what he wil do he will check based on gl account.
if u use "transxn event key" or "general modifier" you r more specifying the gl accounts for ur business transactions.
Finally if u want to differentiate accounts u have to maintain different gl account.
In ur case maintain one valuation grouping code for all plants and assign to ur company code and ur chart of account.
Maintain different gl account for ur valuation class and ur valuation grouping code.
For any clarification plse rewert back.
reward if useful.
Regards
Viru
Similar Messages
-
Partner determination at plant level
at present we are having partner determination at p.org level and plant level.
In our business we have a one vendor with 2 ordering addresses for 2 of our plants.
we had maintained these ordering address at vendor master --plant level.
when we are creating manual PO system is picking up the order address where as when we are creating automatic PO using ME59N transaction system is picking partner function maintained at p.org level rather than maintained at plant level.
plz suggest the solution.Hi,
Check the intial requriment are there r not like source list before craeting the PO.
Check whether the Partner function are maintained at plant level in XK03 in partner fuctions selection field and also check whether you had ticked the data revel at plant level allowed.
Hope this will hep you.
BR,
Patil -
Inter plant STO with intermediate G/L Account & profit at Plant level
Hello Experts,
I have a situation at a client in California. The client does Make-to-Order sales. This client has plants in several cities.
The scenario goes like this. The plant 0020 wants to sell materials to external customer. If this 0020 plant does not have enough stock in inventory, a purchase order needs to be placed with another plant 0010 of same company code.
I know this can be mapped with standard STO Process but client's concerns are:
1) At the time of PGI, both stock accounts will update once.
But he wants an intermediate G/L account as it takes 1 month to recieve goods.
2) Inter plant profit has to be captured.
Example: 0020sells materials @ 120$, procures from 0010@ 100$. Actual cost of that in 0010 is 80$.
Meaning total profit for company is 40$, 20$ each to plant 0010 & plant 0020
Would someone please be so kind as to helpme with a Best process flow for this scenario
I am open to your suggestions.
Thanks,
NageshHi Nagesh,
Generally it sounds wrong; I think that businesswise it is not good practice (and in some countries even forbidden) to record a profit in a company just by moving stock around. This way we could all make millions!
Stock price can vary from one plant to another, but then it is recorded as price difference when it moves, not profit.
Regards,
Mario -
G\L Account determination per itemgroup
Hello,
I do have a question about the G\L Account determination in SAP B1. It is my task to find out which G\L Account(s) is/are being used by the program for all different kind of (trans)actions.
I checked out help.sap.com to check out the different GL accounts that can be determined but this wasn't very useful. There is only a description for GL account determination at company level (Administration > Setup > Financial > G\L account determination).
But after a hard (and long) time of searching I found out most of them myself. But I still need to know 6 of them. I can't find out where they are used and the description @ help is not good as well.
It is about these G\L accounts:
Sales credit account
Purchase credit account
Sales credit account foreign
Purchase credit account foreign
Sales credit account EU
Purchase credit account EU
I need to know when these accounts are being used in journal entries.
Thanks in advance,
Kind regards,
HendriDo you have access to the SAP Business One Document Resource Center? If you do, there is a 19 page PDF there that you should have. It is called 'How to Determine G/L Accounts for Automatic Creation of Journal Entries'.
You have to dig for it. There is no 2007 release, but the 2005 document is still good. In the Document Resource Center, look under
SAP Business One 2005 A SP01
then
How-To Guides 2005 A & 2005 A SP01
then
How to Determine G/L Accounts 2005 SP01 - US
This link may or may not work to get you to the How To Guide page where you will find the PDF:
https://websmp110.sap-ag.de/~form/sapnet?_FRAME=OBJECT&_HIER_KEY=701100035871000437965&_SCENARIO=01100035870000000183& -
Account determination error at billing level
Hi,
for Account determination error at billing level
i checked the line item level for the material by highlighting the item, then GO TO > ITEM > ITEM DETAILS. here 5 line items are there , 4 line items have same "Acct asgnmt grp" and 1 line item is different at order level. i gess this is the problem if am wrong please correct me.
thanks
Edited by: pandu123 on May 26, 2011 2:24 AM
Edited by: pandu123 on May 26, 2011 2:32 AMHi Pandu
A/c deterimation error. 1st you check in customer master sales area data billing tab page with account assingment and go to material master u select particular material see in sales organization 2 tab with account assignment. and go to T.Code VKOA check the combination which is assiged A/c assingmnet group of customer and matrial account assingment group. If it is not come goto VFX3 and specify the customer execute and click on RELEASE FLAG. If it is error go to log see the digonsis.
Kind Regards
Chandra Mouli A -
Account Determination at Company code level for an interface
Hi All,
We need an account determination table at company code level that will be used by an interface to find the GL accounts for a particular company code.
This is required for interfacing certain GL documents onto SAP and the account determination need not be hardcoded in the program.
Kindly revert with your ideas.....
Regards,
Gangs.Hi Gangesh,
All the account determinations will be done only at the Chart of Accounts level only. You cant show me even one account determination which will be done at the company code level. (without giving chart of accounts before assigning a GL)
So only table T030 will be the right table for you. Hope you understood,
Regards,
Sreekanth.... -
Account determination error while using 412 Q in MB1B
Hi All,
While doing transfer posting for a material using Movement Type, 412 Q, we are getting the error "Account determination for entry 1000 AUM 1000 ___ 2002 not possible". The transfer posting was done already for the same material for other batch and it had accepted. This was the last batch to be transferred.
I know in OBYC, we have to enter the G/L Account. But I would like to know why the error has come only for one particular batch for the same material
Please help.
Regards,
RoshHi,
AUM 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.
Please check whether GL code assigned for valuation class in Transaction AUM or not.
Regards,
Manish Jain -
GL account determination for vendor invoice in cross company sale sales
Hi
we are planning to implement cross company sales scenario.
High level design-
1) Sales Order is in co code X and the delivery is from group company lets say co code Y
2) The delivery from co code Y generates two invoices- one in Sales area of co code X for the final customer and 2nd in sales area of co code Y for the inter company
3) The intercompany invoice has EDI output type (Sap standard delivered object is RD04). The output generates a IDOC which has ability to post automatic vendor invoice in co code X crediting the inter company vendor Y.
4) The automatic vendor invoice GL account determination is via customisation OBCB and OBCE
I have some questions around this , particularly if in the vendor invoice we have to account for material and returnable packaging
In my current project there would FG packed in returnable packaging in co code Y
For Export there would be a dedicated co code(X).
Co code X gets orders from customers; and creates sales orders in its sales area with delivery plant of co code Y.
Along with FG returnable packaging is also charged as deposit by - co code X to customer and Co code Y to Co code X.
so in the vendor invoice how to generate the following entry
Inter company vendor 150 Cr
Cost of Goods sold 100 Dr
Returnable Packages deposit 50 Dr.
Similarly when the end customer returns the packaging generate the following entry via the cross company return order and intercompany invoice
intercompany vendor 50 Dr
Returnable packages 50 Cr
if you have worked on this kind of scenario and share how to customise to post for FG and Returnable packaging separately in the automatic vendor invoice it would be great.
Edited by: pravin_shah1403 on Nov 25, 2011 3:00 PMHi Pravin.
Did you figure this out?
I'm seeing that via OBCB we can hit only one G/L account.
We also need to hit multiple accounts.
We've figured out how to hit this via user-exit, however I'm hoping that I've missed something in configuration and that a resolution via configuration is possible?
Any ideas? -
Dear Forum members:
I have an account determination for Posting Inventory differencies (mi07 and movement type 702) that from all indications is all of a sudden going to a different GL Account.
It is apparent that something has been changed in the configuration and as yet I am unable to determine what.
Here is what I know:
(a) Valuation grouping is activated (Plant Level) and from what I can tell, nothing has been changed here.
(b) The valuation Class of the material is determined from the material type and Account Category classifications
(c) The movement type, 702, is same as has always been.
(d) Split valuation is not activated for this material.
(e) I have checked for changes in the materials and nothing has been changed e.g. material type
This is a Production Client and it seems really strange that something could have been altered but I cant determine what. This problem has arisen because the system is now saying the materia is posting to an account requiring a CO object. Now I know I can go and configure the account to have a default CO object. But that will not determine the problem's root.
Forum members please help, is there something else I can check. I have researched for days now and found nothing.Hi
In Physical Inventory-----> if you find the Physical Count is lesser that the Book Stock....then during MI07...automatically 702- movement type will be triggered....and the Inventory Difference will be posted in Inventory Diff. Account...The Transaction Event key for that is GBB and Account Modifier in INV....
So in OBYC -
> For the TEK, GBB--> for your Chart of Accounts - Valuation Grouping Code -- Account modifier INV-Valuation Class combination assign Proper GL Account...If you have assigned Proper GL Account...then you can view that in OMWB ---> GL Accounts ---> there for your Valuation Area...you can view for the Transaction Event Key-Account Modifier Combination which GL account has been assigned..
Reward if useful
Regards
S.Baskaran -
Account determination without wizard
Materials management>valuation and account assignment>account determination>account determination without wizard>group together valuation area.
i am not able to find 2 plants (valuation area is activated at plant level) with assignments
can any one pls let me know wht the reason and how can i do that
there is no option for entring a new item.have you executed before: Materials management>valuation and account assignment>account determination>account determination without wizard>Define Valuation Control
This is the customizing that allows you to group.
The plants will automatically show up there, just without a grouping in the field on the right.
But the precondition for this is that your valuation level is set to plant level in Enterprise Structure >
Definition > Definition > Define valuation level -
Account determination w/o material master
how the automatic account determination is done without using the material master ( material type) ? I mean we are not using material master but wants to user the auto matic account determination ?
Wheather it possible or not?Dear,
Account determination without material master happens when you perform transactions for the following:
1) Goods receipt
2) Goods Issue
3) Transfer posting
4) Account maintenence
5) Prive changes
6) Invoice verifications.
So, for the aforesaid account determination without material master happens at:
1) Organization Level: When doing Goods receipt, you have to select purchasing orgaization, plant which is linked to company code, which in turn linked to respective chart of account (INT). So based on the respective G/L account defined or configured in FICO respective G/L a/cfor debit and G/L A/c for credit will be identified by the system.
2) Business Transactions: When you perform the above said transactions, you have to mention the movement type which is configured in inventory management module. Each transactions or movement type has been asigned a 3 digit number called 101 for GR w.r.t PO. based on this movement type system will select respective tranaction key through Value string i.e: WE01. which is the combination of transactions keys for that particular transactions. Ex: BSX for inventory posting, GR/IR for clearing account which are the key defined for GR w.r.t PO. So system identifies the particular G/lAccount for debit and credit based on define or configured value string which in turn linked to account groping code w.r.t Valuation grouping code. So to summarizise Mvt type - > value string -> transaction key -> G/l A.c for debit or G/l A.c for credit.
3) Material: When you are posting the respective tranaction you need to select the material which is linked to valuation class in material master account view no 1. based on this valuation class system will identified the particular valuation level i.e: Company code or Plant. but as defined or recommended by SAP standard you need to define valuation level at plant level. Based on the valuation level linked at plant which in turn is linked to the valuation gruoping code( which is defined as grouping of similar palnt to identifiy the particluar g/l account is known as VGO). So when the system identifies the particular VGO through G/l acount for debit and credit will be identified by the system through transaction key configured in the SAP system.
Also, there are some cases where you don't know the material code, but you need to mention material type. At that point of time system identifies the account detemination based on material type through valuation class linked by Account Catergory Refernce. You may link many material types to single ACR which in trun you may link many valuation class to single ACR.
This is how, automatic account determination has been configured in SAP system.
The other facrors which influences Automatic account determination are:
a) Valuation Level: Different plant but same material
b) Matarial: Different material but same plant
c) Bussines transctions and
d) Movement types.
Hope this Gyan from my end should clarify you thoughts on account determination.
Note: Appropriate points allocated, if convined would be highly appericated.
Regards,
Prashanth Pai
Awrad, If helpful -
Account determination for entry 1000 AUM
Hello Everybody,
While doing the stock transfer (MB1B) from unrestricted stock to sales order stock system is giving the below error.
"Account determination for entry 1000 AUM 1000 ___ 3100 not possible
Message no. M8147
Diagnosis
The system did not find an account for this transaction. This means that
the account determination for key 1000 AUM 1000 ___ 3100 is not
maintained in MM Customizing (Valuation). The key is made up of:
o Chart of account
o Transaction key (= Posting transaction)
o Valuation grouping code
o Account grouping code
o Valuation class
System Response
The system cannot update a G/L account for this transaction. You cannot
post the transaction."
*The total quantity of the Material is 600.but if i transfer up to 599 qty system is not giving any error.for 1 qty only its asking AUM assignment.*
**why system is behaving like this..? where its finding the price difference...?
Please help me..
Regards,
Srinivas Putty
Edited by: srinu putty on Apr 21, 2010 7:44 AMhi
goto OBYC here dbl click on AUM and then here give the accounts for the valuation class 3100
SAP help for understanding AUM
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.
regards
kunal -
MM subcontracting Account determination
Hi All,
Any one knows MM subcontracting Account determination in OBYC?
any help is appreciated..
Thanks,
RauHi,
Hi,
For Account Determination 5 major characteru2019s are as follow:
1.Chart of Account,
2.Valuation Class,
3.Transaction Event Key,
4.Valuation Grouping Code,
5.Account Grouping Code/Account Modifier.
Configuration of Automatic Account Determination with T.Code are as follow:
1.OMSK: valuation Class with Account category reference,
2.OMWM: Active Valuation Grouping Code,
3.OMWN: Active Movement type with G/L account,
4.OMWD: Active Valuation Area,
5.OMWB: Active Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
In OMWB or OBYC
Click TE key and enter Chart of account and then save the Roles 1st for
1.Debit/Credit
2.General modification
3.Valuation Modif
4.Vakuation class
And then enter respective critetia for that TE key and save.
If assignment(Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
are correct and u would not face any problems in G/GI/IV.
The TE keys are:
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.
u2022 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.
u2022 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.
u2022 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.
u2022 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.
u2022 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.
Caution :
Take care to ensure that:
A stock account is not used for any transaction other than BSX
Postings are not made to the account manually
The account is not changed in the productive system before all
stock has been booked out of it
Otherwise differences would arise between the total stock value of
the material master records and the balance on the stock account.
Revaluation of "other" consumptions (COC)
This transaction/event key is only relevant to Brazil. It is used if
a revaluation report is used for company codes in Brazil.
The revaluation report uses the actual prices determined by the
material ledger/actual costing to:
Revaluate costs on the basis of actual prices
Post the price differences arising from "other" consumptions
(e.g. consumption to cost center) to a collective account
This transaction/event key is needed to post the price differences.
The account specified here is posted with the price differences for
"other" consumptions.
o documentation currently available.
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.
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
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:
AUA: for order settlement
AUF: for goods receipts for orders (without account
assignment)
and for order settlement if AUA is not maintained
AUI: Subsequent adjustment of actual price from cost center
directly
to material (with account assignment)
BSA: for initial entry of stock balances
INV: for expenditure/income from inventory differences
VAX: for goods issues for sales orders without
account assignment object (the account is not a cost
element)
VAY: for goods issues for sales orders with
account assignment object (account is a cost element)
VBO: for consumption from stock of material provided to
vendor
VBR: for internal goods issues (for example, for cost
center)
VKA: for sales order account assignment
(for example, for individual purchase order)
VKP: for project account assignment (for example, for
individual PO)
VNG: for scrapping/destruction
VQP: for sample withdrawals without account assignment
VQY: for sample withdrawals with account assignment
ZOB: for goods receipts without purchase orders (mvt type
501)
ZOF: for goods receipts without production orders
(mvt types 521 and 531)
You can also define your own account groupings. If you intend to
post goods issues for cost centers (mvt type 201) and goods issues
for orders (mvt type 261) to separate consumption accounts, you can
assign the account grouping ZZZ to movement type 201 and account
grouping YYY to movement type 261.
Caution
If you use goods receipts without a purchase order in your system
(movement type 501), you have to check to which accounts the account
groupings are assigned ZOB
If you expect invoices for the goods receipts, and these invoices
can only be posted in Accounting, you can enter a clearing account
(similar to a GR/IR clearing account though without open item
management), which is cleared in Accounting when you post the vendor
invoice.
Note that the goods movement is valuated with the valuation price of
the material if no external amount has been entered.
As no account assignment has been entered in the standard system,
the assigned account is not defined as a cost element. If you assign
a cost element, you have to enter an account assignment via the
field selection or maintain an automatic account assignment for the
cost element.
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 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.
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.
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)
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).
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.
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.
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.
Thanks,
Raja -
Hi,
Can anybody explain total how many G/l Accounts, we will generally assign and please give the list including TE Key.. The reply will be highly appreciated...Hi,
For Account Determination 5 major characteru2019s are as follow:
1.Chart of Account,
2.Valuation Class,
3.Transaction Event Key,
4.Valuation Grouping Code,
5.Account Grouping Code/Account Modifier.
Configuration of Automatic Account Determination with T.Code are as follow:
1.OMSK: valuation Class with Account category reference,
2.OMWM: Active Valuation Grouping Code,
3.OMWN: Active Movement type with G/L account,
4.OMWD: Active Valuation Area,
5.OMWB: Active Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
In OMWB or OBYC
Click TE key and enter Chart of account and then save the Roles 1st for
1.Debit/Credit
2.General modification
3.Valuation Modif
4.Vakuation class
And then enter respective critetia for that TE key and save.
If assignment(Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
are correct and u would not face any problems in G/GI/IV.
The TE keys are:
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.
u2022 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.
u2022 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.
u2022 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.
u2022 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.
u2022 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.
Caution :
Take care to ensure that:
- A stock account is not used for any transaction other than BSX
- Postings are not made to the account manually
- The account is not changed in the productive system before all
stock has been booked out of it
Otherwise differences would arise between the total stock value of
the material master records and the balance on the stock account.
Revaluation of "other" consumptions (COC)
This transaction/event key is only relevant to Brazil. It is used if
a revaluation report is used for company codes in Brazil.
The revaluation report uses the actual prices determined by the
material ledger/actual costing to:
- Revaluate costs on the basis of actual prices
- Post the price differences arising from "other" consumptions
(e.g. consumption to cost center) to a collective account
This transaction/event key is needed to post the price differences.
The account specified here is posted with the price differences for
"other" consumptions.
o documentation currently available.
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.
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
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:
- AUA: for order settlement
- AUF: for goods receipts for orders (without account
assignment)
and for order settlement if AUA is not maintained
- AUI: Subsequent adjustment of actual price from cost center
directly
to material (with account assignment)
- BSA: for initial entry of stock balances
- INV: for expenditure/income from inventory differences
- VAX: for goods issues for sales orders without
account assignment object (the account is not a cost
element)
- VAY: for goods issues for sales orders with
account assignment object (account is a cost element)
- VBO: for consumption from stock of material provided to
vendor
- VBR: for internal goods issues (for example, for cost
center)
- VKA: for sales order account assignment
(for example, for individual purchase order)
- VKP: for project account assignment (for example, for
individual PO)
- VNG: for scrapping/destruction
- VQP: for sample withdrawals without account assignment
- VQY: for sample withdrawals with account assignment
- ZOB: for goods receipts without purchase orders (mvt type
501)
- ZOF: for goods receipts without production orders
(mvt types 521 and 531)
You can also define your own account groupings. If you intend to
post goods issues for cost centers (mvt type 201) and goods issues
for orders (mvt type 261) to separate consumption accounts, you can
assign the account grouping ZZZ to movement type 201 and account
grouping YYY to movement type 261.
Caution
If you use goods receipts without a purchase order in your system
(movement type 501), you have to check to which accounts the account
groupings are assigned ZOB
If you expect invoices for the goods receipts, and these invoices
can only be posted in Accounting, you can enter a clearing account
(similar to a GR/IR clearing account though without open item
management), which is cleared in Accounting when you post the vendor
invoice.
Note that the goods movement is valuated with the valuation price of
the material if no external amount has been entered.
As no account assignment has been entered in the standard system,
the assigned account is not defined as a cost element. If you assign
a cost element, you have to enter an account assignment via the
field selection or maintain an automatic account assignment for the
cost element.
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 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.
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.
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)
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).
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.
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.
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.
Regards,
Biju K -
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-mmHi 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.
Maybe you are looking for
-
I can't not open up my firefox a dialog box pops up and say Mozilla crash report
I tried everyting... I could not check if it is a safemode issue because when I click on fire fox it won't let me in just a dialog box that say that mozilla has crashed. This is the lastest crash report. Crash ID: bp-80765d76-e647-44e9-8f45-473b82130
-
Oracle RAC 2 node architecture-- Node -2 always gets evicted
Hi, I have Oracle RAC DB with simple 2 node architecture( Host RHEL5.5 X 86_64) . The problem we are facing is, whenever there is network failure on either of nodes, always node-2 gets evicted (rebooted). We do not see any abnormal errors on alert.lo
-
Zen touch - software for finding duplicates in libr
After buying my player and putting 800 tracks on there so far I have found that I have a lot of duplicates of songs. Some are ones I want (album version v li've version of songs) but sometimes I have exactly the same recording a few times. I mean who
-
Printing Multiple Photos per Page in Mac PSE4
I have PSE 4 for the mac. I would like to print 4 3.5 X 5 photos on an 8.5 X 11 sheet -- but I want them to be DIFFERENT photos, not 4 copies of the same photo. I can't figure out how to do this. The picture package will print multiple copies of a ph
-
Help Ipod 4GB - cannot locate radio stations
I recently deleted the radio stations i had in my itunes and on my ipod. I now cannot dial into my car radio (I have an iTrip connector which works fine). I have just lost all the stations and want to restore 87.5 or there abouts which will allow me