OBA7 — Document Type Configuration
OBA7 is used to configure FI document types, number-range assignment and permitted account types. It is most useful when implementing a new accounting document flow or analyzing why a document type behaves differently. Start with the exact organizational keys and business date, then prove the result from SAP documents, balances or logs before changing configuration or reposting data.
This page explains OBA7 — Document Type Configuration — from a consultant's point of view: what it changes or displays, when it belongs in the process, which keys matter, how to prove the result, and the mistakes that create avoidable reconciliation work.
Published 19 Sept 2026· 605 words
Esta página ainda não está disponível em português.
Purpose
configure FI document types, number-range assignment and permitted account types. The transaction should be read in the context of the full accounting or logistics flow: source document, organizational assignment, posting date, configuration and resulting document all matter. A technically successful save is not enough; the output must reconcile to the intended business event.
When it is used
OBA7 is typically used when implementing a new accounting document flow or analyzing why a document type behaves differently. In project testing it is equally useful for proving configuration and master data with a controlled example. In production, narrow the scope first and capture the before-state so any posting, clearing, settlement or master-data change can be reconciled afterward.
How to use it in practice
- Start from the business posting scenario and existing standard document type.
- Review number range and permitted account types.
- Check reversal/negative-posting controls only where policy requires them.
- Transport changes through the landscape.
- Regression-test postings and document display.
Key data objects
These are the fields and business objects that usually explain the result in OBA7. Capture them in test evidence and incident handovers, because a mismatch in company code, plant, fiscal period, account or reference document is often more important than the screen message itself.
- document type — verify the exact value, validity/date context and source of derivation.
- number range — verify the exact value, validity/date context and source of derivation.
- account types allowed — verify the exact value, validity/date context and source of derivation.
- negative posting/reversal controls — verify the exact value, validity/date context and source of derivation.
- batch input restrictions — verify the exact value, validity/date context and source of derivation.
How to prove it in the data
Prove the result end to end: identify the source document/master record, inspect the transaction's proposal or status, then open the resulting accounting or logistics document and reconcile amounts, quantities and account assignments. Use document flow, line-item displays and master-data history with the same fiscal period and organizational scope. That distinguishes a true configuration defect from a selection, timing or historical-data difference.
ECC vs S/4HANA
FI document types remain core configuration in S/4HANA, though posting apps and APIs may hide the document type from end users. On S/4HANA, Universal Journal, Business Partner, Material Ledger or Fiori may change the preferred analysis surface, but the business control behind the transaction still has to be understood and tested.
Common pitfalls and how to diagnose them
- Creating a new document type when an existing standard type already fits. Reconcile the exact document and period before making a configuration change.
- Reusing a number range without accounting governance. Reconcile the exact document and period before making a configuration change.
- Changing productive controls to bypass an interface error. Reconcile the exact document and period before making a configuration change.
Whose problem this is
Primary ownership is Finance/Controlling, with Basis or ABAP involved only when runtime, authorization or custom-code evidence points there. A useful escalation includes the business document, organizational keys, posting/valuation date, expected accounting result and the exact mismatch already proven.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/oba7ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.