ITPub博客

首页 > Linux操作系统 > Linux操作系统 > OBYC中的Transaction key详细解释以及用法-Group(RMK)

OBYC中的Transaction key详细解释以及用法-Group(RMK)

原创 Linux操作系统 作者:Immortalwill 时间:2008-01-03 14:54:20 0 删除 编辑

The following list shows the individual transactions with examples of how they are used:

  • 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.

  • 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 t

  • 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.

  • 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)
  • VB 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.

  • 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 and semi-finished products used in the manufacture of a semi-finished or finished product are debited or credited to that semi-finished 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 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 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 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 and semi-finished products used in a semi-finished or finished product are debited or credited to that semi-finished 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 key, which posts inflation postings to a different account within the handling of inflation 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.

  • 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.

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/8628891/viewspace-85986/,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论

注册时间:2007-12-29

  • 博文量
    66
  • 访问量
    108637