SAP Goods Issue Accounting: How OBYC, GBB and BSX Fit Together

A goods issue is a logistics event with an accounting consequence. In the sell-from-stock example demonstrated in the course, issuing goods reduces inventory and recognizes cost of goods sold. SAP then uses automatic account determination to select the G/L accounts. BSX and GBB are parts of that determination path, not universal account numbers.

A simplified entry for a normal valuated goods issue is:

• Debit cost of goods sold
• Credit inventory

The exact keys, modifiers, accounts and even whether an accounting document is created depend on the movement type, valuation and business process. Do not assume every goods movement uses the same GBB modifier or the same two accounts.

What BSX does in this scenario

BSX is the transaction key used for inventory postings in automatic account determination. It helps the system select the inventory account using inputs such as chart of accounts, valuation grouping and material valuation class. In the lesson's example, a missing BSX entry appears while stock is being introduced for a trading-good valuation class. After the correct inventory account is configured, the stock posting can proceed.

What GBB does in this scenario

GBB covers offsetting entries for inventory postings. It is subdivided by account or general modifiers because different business events need different offset accounts. In the demonstrated sales-order goods issue, the message includes GBB with modifier VAX and the material's valuation class; the selected account is cost of goods sold. Another movement can use a different GBB modifier and therefore a different account.

Illustrative worked example

Assume 20 units of fictional trading material FG-100 leave stock. The standard price is EUR 75 per unit, so the valuated quantity is EUR 1,500. In the demonstrated type of sell-from-stock flow, the expected simplified posting is:

To explain why those accounts were chosen, capture the movement type and process, valuation area or grouping, material type and valuation class, transaction key, GBB modifier, chart of accounts and configured account. The amount comes from valuation; the account comes from determination. Those are related investigations, but not the same one.

A repeatable tracing method

1. Open the material document and its accounting document. Confirm quantity, value and posting date.
2. Identify the movement type and business event.
3. Read the full account-determination error if posting failed; record every key shown rather than only the account name you expected.
4. Check the material's valuation class and the valuation grouping used by the plant or valuation area.
5. Inspect the relevant OBYC transaction key and modifier combination.
6. Verify that the proposed G/L account exists in the chart and company code and has the required account properties.
7. Retest the same logistics event and inspect the resulting debit and credit lines.

In on-premise SAP S/4HANA, OBYC is a common entry point for this configuration. Configuration interfaces differ in cloud editions, and all changes should follow the authorized design and transport route.

Common mistakes

• Treating GBB as one account instead of a transaction key with event-specific modifiers.
• Ignoring valuation class and checking only the plant.
• Creating a new G/L account before proving that the existing account design cannot be used.
• Fixing the missing account but failing to check whether the posted amount is correctly valued.
• Assuming the keys from a sales goods issue apply to a purchase receipt, scrapping or production movement.

Continue learning

Continue the order-to-cash flow with the customer billing and account-determination lesson.

FAQ

Does BSX always post inventory? It is the standard transaction key for inventory postings, but the complete business event and configuration determine the result.

Is GBB always cost of goods sold? No. GBB can select different offsetting accounts through modifiers. The demonstrated VAX sales goods issue points to cost of goods sold.

How do I verify the result? Inspect the actual material and accounting documents, not only OBYC. SAP's production cost-posting example also illustrates that BSX and GBB can work together while a different GBB modifier serves a different event.