Translating OBYC, VKOA, and GGB0 into posting profiles

How SAP's inline account determination engine — OBYC for materials management, VKOA for sales, GGB0 substitution rules — is mapped onto D365 inventory posting setup, customer and vendor posting profiles, and dimension defaulting, with a fully traced goods-receipt example.

What you will be able to do

• Identify the inputs SAP's MM account determination engine uses to resolve a G/L account
• Map each major OBYC transaction key to its D365 inventory posting type equivalent
• Explain how customer and vendor reconciliation accounts migrate from master data to posting profiles
• Translate GGB0 substitution rules into D365 default dimensions and Account Structure rules
• Trace a complete goods receipt through both systems at the voucher level

Introduction

SAP's defining accounting achievement is its inline account determination engine. When a goods receipt is posted, the system consults configuration tables at the moment of posting and resolves the correct G/L accounts automatically. No user enters an account number.

SAP's inline account determination: OBYC

Transaction OBYC is the heart of SAP Materials Management account determination. It resolves three inputs to a G/L account.

VKOA and the SD revenue chain

Sales and Distribution account determination uses transaction VKOA. Where OBYC is item-centric, VKOA is customer-and-item-centric: it determines revenue accounts, discount accounts, and freight accounts from the combination of:

Substitution and validation rules

Beyond OBYC and VKOA, SAP's account determination estate includes two rule systems that are frequently overlooked until opening balances fail to reconcile.

D365's posting-profile framework

Where SAP has one account determination mechanism per module, D365 has a set of purpose-specific surfaces. The core pattern is consistent: a named profile plus a posting type resolves to a main account plus default financial dimensions.

Worked example: one goods receipt end to end

This example traces a goods receipt for 100 units of a stock material at standard cost 15.00 per unit through both systems.

Worked example: sales invoice and account-key decomposition

A sales invoice is the second account-determination path every SAP finance lead asks about, because it proves the migration is not only an inventory exercise. In SAP the user posts billing with VF01.

Reconciliation invariants and special G/L indicators

The invariant to preserve is simple and non-negotiable: subledger balances must explain the G/L control account balance. SAP enforces this with reconciliation accounts. KNB1-AKONT for customers and LFB1-AKONT for vendors point customer and vendor postings to G/L accounts flagged in SKB1 as reconciliation accounts;

Knowledge check

Summary

SAP's account determination is centralised and implicit — the system resolves accounts from configuration tables at the moment of posting with no user involvement. D365's posting profiles are distributed and explicit — each module has its own profile surface, each configured independently, each resolving to a main account and default…