Transaction Key PRD or BSX

Hello SAP Guru
I did MIRO and there is a price vairance of $10, But insted of posting happen to PRD account its happening to BSX , I checked all IMJJ OBYC but not be able to fingure out. Can anybody please help.

Base Unit of Measure LB    US pound     Valuation Category
Currency             USD                Current period       07 2014
Division                                Price determ.
Valuation Class      SSM1
VC: Sales order stk                     Proj. stk val. class
Price Control        V                  Price Unit           1
Moving price         0.24               Standard price       0.00
Total Stock          450                Total Value          108.00
Future price         0.00               Valid from
Previous price       0.00               Last price change
NOt be able to insert pic, so sharing details.

Similar Messages

Posting transaction key PRD

Good morning,
I should do a little analysis about our G/L accounts definition for transaction key PRD. What I would like to understand is how SAP configures the automatic posting procedure or, in a better way, how SAP determines which transaction keys must be used in a particular situation.
I think that these tables should be involved in the procedure:
T156SC
T156SY
T156X
T156W
Does someone have more information?
Thank you in advance.
Francesco Alborghetti

Dear Francesco,
Go to T.code - OBYC.
Select the posting key - PRD.
Give the concern chart of Account and go inside.
You will see Valuation modification and Valuation class assigned to GL accounts.
If you want to include the movement types into this, you need the Account modifier. If so, click rules,
select the check box of Account modifier also and save the screen first.
Then go into the trasnaction, where you will find the Account modifier will also be included. You can select the correct account modifier which is in turn assigned with the movement type.
Hope this helps.
Reward points if satisfied.
Thanks.
Augustine Ponraj.

Transaction key PRD

Hi!
Is it possible to attach a cost center in the GL account in transaction key PRD?
We put the Miscellaneous GL in the transaction key PRD. The cost center is required in the Misc GL. Is there a way that we can set an automatic Cost Center in transaction key PRD?
Thanks so much.
Regards,
Paula
Edited by: Angela Paula Oquendo on Feb 4, 2010 4:26 AM

hi
firstly u have to assign the GL account to the key PRD in transaction code OBYC
now this gl u have to make it cost element in FS00 (in fs00 chnge mode select gl acct and cick on cost element)
now goto OKB9 here give the assignment of Gl acct to the cost center
regards
kunal

Account grouping/Transaction keys PRD/DIF

Hello Gurus
I have a situation that some MIRO posting are using PRD and some are using DIF transaction keys. For some reason The postings with DIF are not picking up the material thus resulting in putting dummy profit center.
Please advise the difference between PRD and DIF and how these are triggered during MIRO transactions.
Many thanks
MSJ

HI Jayaram/Surabhi
The see what you are saying and it make sense after I read your reply.
The reason that I say that few MIRO postings are using DIF is because the posting key 83 debit and 93 credit are defined in the OBYC for DIF.
So when I looked at the document in the Vendor acct (after I post MIRO), I see the profict center and material missing for posting keys 83 and 93 for some postings.
Wheras I can see the profict center and material for posting keys 86 and 96 for some othe MIRo postings which use these posting keys.
Of course all these postings are generated automatically
So my question is where do I make a setting to have the material and profict center generated for posting keys 83 and 93.
I appreciate your help on this critical issue for me.
Please advise.

PRD - PRA transaction Key

Dear All,
I hav one doubt regarding transaction key PRD - PRA.
When actually it hits . I think it is used while using goods issue and other movements.
But tell me the functionaly of it.
Also I found in OMJJ for movement type 201,221 posting like
PRD PRA and check box is unticked (a/c assignment)
Why is it so?
Pls clear my doubt.
Thanks in advance.
Regards,
Gitesh

Hi,
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 price),
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, then you can use this modification.
"PRA for goods issues and other movements "
thanks,
Prashant Rathore.

How to know debit and credit transaction key for movement type

Hi,
With T. code OMWB account assignment simulation we can see all the accounts which are involve for debit and credit enties but I want to know is there any T. code or method with which we can know which transaction key will be debit and which will be credited like for movement type 101 the transaction keys are GBB, BSX WRX etc. i want o know whethere GBB a

Hi,
Thanks for your reply, but with this we can see the for GBB which is the credit account and which account is use for debit entry, like this for all transaction event key like WRX, BSX etc. we can see the G/L account use for Debit and credit, but i want to know for particular selction of Plant, material , movement type, my GBB account will have entry in debit account or credit account How we can know this.
regards,
zafar

Transaction Key PRD_PRA

HI All,
In which scenario OBYC Settings Transaction key PRD--PRA will be used. we did nt activated ML. Still the system is throwing a message at that time of cancellation of production order confirmation "Account determination for entry PRD_PRA valuation class XXXX not possible.
1.For PRD_PRA-- ML Need to activated or not??
2. how PRD-PRA is differ from the PRD
3. in which scenario PRD_PRA will be assigned with GL
Thanks

Hi
In PRD we assign accounts for price difference. It is independent of ML activation and has no relevance to ML.
PRD can be used with/without account modifier. If you use account modifier, you can assign separate account for price differences from purchase order or production order etc.
In particular PRD- PRA is for price difference in case of goods issue.
In your case, since you are cancelling Production confirmation, goods issue is happening for the finished good (presumed it is maintained with price control S and backflush is 'ON' for this)
This is the reason error is showing up.
In normal cases PRA will not picked because goods issue is generally done for raw materials which are maintained with price control V.
Generally PRA can be assigned with the same account as that for normal PPV (purchase price variance) account unless business specifically wants to assign something else.
Hope this helps
Regards
Abhinav

BSX / WRX transaction key in OMWN (Account grouping)

Hi There,
I'm trying to understand AAD.
My confusion is, I do not see BSX / WRX transaction key for MVT 101 (considering all permutations and combinations) in OMWN .
As we know, when we perform 101, below accounts come to picture. So where this MVT 101 will be linked to BSX & WRX.
Goods Receipt Against Purchase Order:101
Movement Type: 101
Accounting Entry:
Inventory of Raw Material Debit [BSX]
GR/IR (Goods Receipt/Invoice Receipt) Credit[WRX]
Thanks,
Udaya

Hi,
Account grouping is not available for BSX and WRX. It available for GBB, PRD, and KON only. Refer the help doc: Define Account Grouping for Movement Types - Valuation and Account and
Assignment - SAP LibraryConfigure Automatic Postings - Valuation and Account Assignment - SAP Library
Regards,
AKPT

Transaction Keys Description in MM(BSX, GBB etc)

Hi all,
I was going through many documents for FI/MM Integration but i could not understand what exactly are these transaction keys used for. for ex if thr is a movement type 101, GR agnst PO. then we have two things to do go to BSX- give the debit account and go to GBB-AUM to credit, if i am not wrong. I appreciate if someone please explain the usage in normal terms quoting some examples.
Thanks
Shriya

Hi,
some of the key descriptions -
Expense/revenue from consumption of consignment material (AKO)
     Expenditure/income from transfer posting (AUM)
     Provisions for subsequent (end-of-period rebate) settlement (BO1)
     Income from subsequent settlement (BO2)
     Income from subsequent settlement after actual settlement (BO3)
     Change in stock (BSV)
   Stock posting (BSX)
Revaluation of "other" consumptions (COC)
   Small differences, Materials Management (DIF)
   Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
External service (FRL)
External service, delivery costs (FRN)
Offsetting entry for stock posting (GBB)
-   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)
Regards,
Sridevi
<i><b>* Pls. assign points, if useful</b></i>
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/sridevi+pattabiraman">me!</a>

MIRO TRANSACTION - BSX TRANSACTION KEY TAKE PLACE

Dear Consultants,
While posting MIRO document, the BSX transaction key is taking place & posting key is 89 apart from WRX transaction key, the figure of (MIRO )WRX transaction key ie the automatic G/L a/c assign in OBYC is matching with WRX transaction key in MIGO.
pls note that BSX transaction key i.e automatic G/L posting is taking effect in MIGO.( 120000Rs)
My question is why BSX transaction key ( hardly 200 Rs ) is taking place in MIRO posting, wht was the reason & further there is no invoice condition difference from PO & MIRO.
Anticipating your advices.

Hello
Posting key 89 is for debit and BSX transaction gets debited at the time of MIGO as stock account is getting debited at the time of MIGO.
WRX is GR/IR clearing and it gets credited at the time of GR.
In normal cases the debit and credit entry will be for the same amount unless configured otherwise.
At the time of MIRO WRX gets debited and vendor account gets credited. As you are saying BSX is also coming into play at the time of MIRO, that means some amount is getting into the material accounts in the line item.
It can happen if you have given unplanned delivery costs (should be Rs.200) and is configured to be distributed among the material account.
Hope it is clear.
Regards
Gregory Mathews

Miro posting - BSX transaction key take place

Dear Consultants,
While posting MIRO document, the BSX transaction key is taking place & posting key is 89 apart from WRX transaction key, the figure of (MIRO )WRX transaction key ie the automatic G/L a/c assign in OBYC is matching with WRX transaction key in MIGO.
pls note that BSX transaction key i.e automatic G/L posting is taking effect in MIGO.( 120000Rs)
My question is why BSX transaction key ( hardly 200 Rs ) is taking place in MIRO posting, wht was the reason & further there is no invoice condition difference from PO & MIRO.
Anticipating your advices.
Edited by: vivek tripathi on Sep 26, 2008 6:55 AM

Hi
There must be some difference in the PO Value and the Actual invoice received from the Vendor. This difference can be due to various reasons, e.g. difference in Basic Value, or difference in Sales Tax, or even difference in amount of excise duty as that as per the PO condition and as captured in J1IEX
regards
Parag Bhargava

Assign GL account in two transaction keys

Hi! In OBYC, is it possible for us to assign the GL account twice? We would like to use a specific GL account in two Transaction Keys.. Is that possible?
Thanks so much!
Regards,
Paula

Hi,
BSX- Account is Balanc sheet account.
PRD is P& L Account-- the same varient G/; account only can assign to twice.
Check in FS00. the G|L account account group.
SAM

Transaction Keys in Materials Management

Also known as u2018process keys,u2019 the u2018Transaction Keysu2019 are pre-defined in the system to enable transaction postings in Inventory Management and Accounting (Invoice Verification). For each of the movement types in MM, there is a value string that stores these possible transactions.
The pre-defined transaction keys are:
BSX (used in Inventory Postings)
WRX (used in GR/IR Clearing Postings)
PRD (used to post Cost/Price differences)
UMB (used to post Revenue/Expenses from revaluation)
GBB (used in offsetting entries in Stock postings)
BSX, WRX, and PRD are examples of transaction keys that are relevant for a GR with reference to a purchase order for a material with standard price control.
The transaction key UMB is used when the standard price has changed and the movement is posted to a previous period.
Likewise,GBB is used to identify the GL account to post to as the offsetting entry to the stock account (when not referencing a purchase order) such as miscellaneous goods receipts, goods issues for sales orders with no account assignment, and scrapping

Also known as u2018process keys,u2019 the u2018Transaction Keysu2019 are pre-defined in the system to enable transaction postings in Inventory Management and Accounting (Invoice Verification). For each of the movement types in MM, there is a value string that stores these possible transactions.
The pre-defined transaction keys are:
BSX (used in Inventory Postings)
WRX (used in GR/IR Clearing Postings)
PRD (used to post Cost/Price differences)
UMB (used to post Revenue/Expenses from revaluation)
GBB (used in offsetting entries in Stock postings)
BSX, WRX, and PRD are examples of transaction keys that are relevant for a GR with reference to a purchase order for a material with standard price control.
The transaction key UMB is used when the standard price has changed and the movement is posted to a previous period.
Likewise,GBB is used to identify the GL account to post to as the offsetting entry to the stock account (when not referencing a purchase order) such as miscellaneous goods receipts, goods issues for sales orders with no account assignment, and scrapping

View Transaction keys by migo.......

Hi All,
In MIGO, in Display Material document, there is a option available "FI Documents" .
We can view the account posting by clicking on that button and selecting the fi document.
But I also want to view here the Transaction Keys(i.e. BSX, WRX, PRD................)
Is there any option for the same.

Hi,
In the accounting document, you can change the layout, and select field "Transaction" to be
"display field", then you will be able to see BSX/KBS/WRX etc., in the material document's
accounting document.
Thanks and regards,
Polly

OBYC- GBB- Transaction keys

hi
Can any one tell me what are these keys meant for
In GBB: AUA,AUF,BSA,INV,VBR,VAX,VAY,ZOF,ZOP are some of the keys I have mentioned.
I want to know to which key I have assign the inventory,scrap,consumption G/L codes ,etc for process industry in repetitive and discrete manufacturing scenario.

Hi,
Check this..
     Transactions
     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.
     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.
     Account determination of valuated sales order stock and project stock
     Note that for valuated sales order stock and project stock (special stock E and Q) and for the transaction/event keys BSX andGBB, you must maintain an account determination to avoid receiving warning messages when entering data (purchase order or transfer posting) for valuated stock.
     During data entry, the system attempts to execute a provisional account determination for GBB for valuated stock. The system will only replace the provisional account determination for GBB with the correct account determination for the stock account (BSX), in the background, if you enter the data for valuated stock at a later point in time.
     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:
     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.
     Account determination of valuated sales order stock and project stock
     Note that for valuated sales order stock and project stock (special stock E and Q) and for the transaction/event keys BSX andGBB, you must maintain an account determination to avoid receiving warning messages when entering data (purchase order or transfer posting) for valuated stock.
     During data entry, the system attempts to execute a provisional account determination for GBB for valuated stock. The system will only replace the provisional account determination for GBB with the correct account determination for the stock account (BSX), in the background, if you enter the data for valuated stock at a later point in time.
     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.
     Customers who used the transaction WRY prior to Release 4.0 must make a transfer posting from the WRY account to the WRX account in order to ensure that the final balance on the WRY account is zero.
Thanks,
Rau

Transaction Key PRD or BSX

Similar Messages

Maybe you are looking for