Transaction Key

DEFINTION

The transaction keys, also known as event keys, are used to determine GL accounts based on business transactions.

  • BSX: Inventory Posting Debit

  • WRX: GR/IR Clearing Account

  • GBB: Goods Issue/Scrapping/Delivery of Goods

  • BSV: Stock Change Account

  • FRL: External Activity

  • PRD: Price Difference Account

  • KON: Consignment Liability

  • UMB: Revaluation of Material Account

BSX - Inventory Posting Debit

• When you utilize BSX, the expense or asset account will be credited and the inventory account will be debited.
Debit: Account for inventory, such as finished goods, raw materials, etc.
Credit: An asset account (such as a purchase account) or an expense account (such as a cost of goods sold, etc.)
• Common transactions using BSX include:
- Goods Receipt - Inventory transfer
- Adjustment (increase) of inventory
• As an illustration, let's say you create purchase order for 100 units of material, and the purchase order price is ₹10 per unit.
• A ₹1000 debit is made to the inventory account.

WRX - GR/IR Clearing Account

• Received goods and an invoice for material.
Debit: Invoice Receipt and Asset accounts for invoice clearance.
Credit: Goods Receipt, Invoice clearing, Expenses/Asset account for reversal and cancellation.
• Example: Create a purchase order for 100 pieces of material. The buy order price is ₹10 per unit. You receive an invoice from the seller for the materials. The invoice price is ₹11 per unit.
•The GR/IR clearing account is funded with ₹100.

GBB - Goods Issue/Scrapping/Delivery of Goods

• GBB debits the inventory account and credits the appropriate account.
Debit: Inventory, COGS, and Scrap Goods.
Credit: Assets, Expenses, and Revenue
• The key records the decrease in inventory value of the material.
• For example: You generate a purchase order for 100 units of material. The buy order price is ₹ 10 per unit. You issue100 units of material for production.
• The Inventory account is debited by ₹1,000.

BSV - Stock Change Account

• BSV refers to the difference in inventory value between a material's standard price and the price received from the vendor.
• The purchase order unit is 100, and the purchase order price is ₹10 per unit. However, the actual material cost is ₹9 per unit.
• The inventory value decreased by ₹100 compared to the purchase order and standard material prices.

FRL - External Activity

• The key is record the cost of external activities, such as: 
- Services provided to outside parties (such as consulting or training)
- External labor costs, such as fees for contractors
- External costs (such as entertainment during travel)
• Inventory values decrease the FRL transaction key is used in conjunction with the GBB transaction key.
Debit: Account for external expenses (such as external labor and services delivered).
Credit: Revenue account (service done) or asset account (prepaid expenses)
• As an illustration, you subcontract to a vendor the production of 100 units of material at a cost of ₹10 per unit. The subcontract has a ₹1,000 price tag.
• FRL - A ₹1000 debit is made to the inventory account.
• GBB – Consumption account is debited by ₹1000.


PRD - Price Difference Account

• When the price of the material's differs from the standard price, like:
- Variations in the purchase price
- Modifications to sales prices
- Revaluations of inventories
Debit: PRD for value additions or price increases.
Credit: PRD for reduction in value or price decreases.
• As an illustration, let's say you purchase ₹10 for 100 units of material from a vendor. The material is standard priced at ₹11 per unit.
• There is a ₹100 debit to the inventory account.
• There is a ₹100 credit to the Price difference account.

KON - Consignment Liability

• The responsibility for goods that a vendor has on consignment.
• As an illustration, let's say you receive a consignment of 100 units of materials for ₹1,000 from a vendor.
Debit: Receive material consignment (e.g., Receive)
Credit: Issue the material from consignment (e.g., Reversed).
• Consignment of material received; ₹1000 is debit on the liability account.
• The liability account is credited with ₹1,000 when the material from the consignment is issued, and the KON transaction event key is reversed.

UMB - Revaluation of Material Account

• During the transportation of goods, materials are revalued using the UMB transaction key. When there is a difference between the standard price and the moving average price, the system must post the difference to a particular general ledger (G/L) account. In this case, the transaction key is specifically used.
• These pricing differences are recorded in a particular G/L account that is mapped to the transaction key UMB.
• The materials are provided to you at a price that deviates from the standard price.
• A company manages a material whose standard price is ₹100 per unit; however, because of recent acquisitions, the moving average price has changed to ₹90 per unit.
Debit (Dr): Inventory Account (increase inventory value to ₹100)
Credit (Cr): Price Difference Account (recognize the ₹10 difference)


TRANSACTION FLOW


ASSOCIATION

Transaction event keys associated with Movement Types:


CONFIGURATION

Step 1: Access the Configuration for Transaction Keys

  • Enter Transaction Code: Use transaction OBYC in the SAP GUI or search for "Automatic Account Determination" in the Fiori Launchpad.

Step 2: Select the Area for Configuration

  1. In the "Automatic Determination" configuration screen (transaction OBYC):

    You will see various transaction keys related to different business processes, such as BSX (Inventory Posting), WRX (GR/IR Clearing), GBB (Offsetting Entry for Inventory Posting), etc.

    These keys are grouped under different processes like Inventory Management, Invoice Verification, Materials Management, etc.

  2. Select the Transaction Key:

    Choose the transaction key you want to configure (e.g., BSX, WRX, GBB).

    Double-click on the transaction key to open its configuration.

Step 3: Configure the Transaction Key

  1. Account Determination:

    In the configuration screen, you will see various fields like Chart of Accounts, Valuation Class, and Account Modifier.

    The combination of these fields determines which G/L account will be used for the transaction.

  2. Assign G/L Accounts:

    Chart of Accounts: Select the relevant chart of accounts.

    Valuation Class: Specify the valuation class, which corresponds to the material type. For instance, raw materials, finished goods, and semi-finished goods might have different valuation classes.

    Account Modifier (if applicable): Some transaction keys, like GBB, use account modifiers (e.g., VAX, AUF) to further differentiate postings based on business transactions.

    G/L Account: Assign the G/L account that will be debited or credited for this combination of chart of accounts, valuation class, and account modifier.

  3. Save the Configuration:

    After assigning the appropriate G/L accounts, save your changes.

Step 4: Test the Configuration

  1. Perform a Test Transaction:

    After configuring the transaction key, perform a test transaction, such as a goods receipt or invoice posting, to ensure that the correct G/L accounts are being posted.

  2. Check the Accounting Entries:

    Verify the accounting documents created by the test transaction to ensure that the expected G/L accounts are debited or credited correctly.

  3. Adjust if Necessary:

    If the postings are not as expected, return to the OBYC configuration and adjust the account assignments as needed.

Step 5: Transport the Configuration (If applicable)

  • If you're working in a development or quality assurance system, remember to create a transport request to move your configuration to the production system.

Key Considerations:

  • Valuation Class: The valuation class is crucial because it links the material type to the relevant G/L accounts. Ensure that your valuation classes are correctly assigned in the material master data.

  • Account Modifiers: These are used for more detailed account determination, especially in cases like goods issues for different purposes (e.g., sales orders vs. production orders).

  • Testing: Always test your configuration in a non-production environment before implementing it in production to avoid incorrect financial postings.


Previous
Previous

Movement Types

Next
Next

Automatic Account Determination