By Ashish Sampat
How to Make Trading Partner Mandatory in SAP FI Using Validation Rules
In SAP Financial Accounting (FI), the Trading Partner field (VBUND) identifies the affiliated company involved in an intercompany transaction. Maintaining this field consistently is important for accurate intercompany reporting, reconciliation, and consolidation in SAP ECC and SAP S/4HANA.
A common configuration challenge is determining how to make Trading Partner mandatory during FI document posting. Although field status settings can control whether certain fields are displayed or available for entry, making Trading Partner mandatory may require additional validation logic, depending on the posting scenario and system configuration.
In this second part of our series, we explain how to use SAP FI validation rules, configured through transaction OB28, to check whether Trading Partner has been populated and prevent a document from being posted when the required value is missing.
We cover the validation prerequisites, the use of relevant document and line-item fields, and the configuration considerations that should be evaluated before implementing this control in a production SAP system.
For background on Trading Partner configuration and master data, see Part I: How to Make Trading Partner a Required Entry in SAP.
1) Field Status Group
Field status groups control whether fields are required, optional, displayed, or suppressed during financial document posting.
However, the Trading Partner field (VBUND) is not available as a standard field status group option.
It is technically possible to extend the coding block configuration to influence Trading Partner field status. However, this approach should be evaluated carefully because changes to the coding block can affect Financial Accounting document posting.
Refer to the relevant SAP documentation or SAP Notes for your system release before implementing coding block changes.
- OBC4 – Field Status Variants: G/L account level
- OB41 – Field Status Groups: Posting key level
2) Document Type
Document type configuration can be used to make Trading Partner available for entry during financial document posting.
You can review document type settings using Transaction OBA7. The relevant settings are stored in table T003:
- XMGES – Partner Company Can Be Input
- XGSUB – Cross-Company
These settings can make Trading Partner available for entry at the document level. However, making the field available for input does not by itself make Trading Partner mandatory.
If Trading Partner must be required for specific transactions, an FI validation can be used to check that the field is populated before the financial document is posted.
3) FI Validation
FI validation can be used to check that the Trading Partner field is populated before a financial document is posted. The validation can be limited to specific G/L accounts, users, document types, or other defined conditions.
An FI validation consists of three components: Prerequisite, Check, and Message.
The following SAP transactions are used in this example:
- OB28 – Financial Accounting Validation: Used to activate validations in Financial Accounting.
- GS01 – Create Set: Used to create sets referenced by the validation.
- GS02 – Change Set: Used to maintain existing sets referenced by the validation.
Prerequisite:
The prerequisite defines when the validation applies. In this example, it applies to:
- Selected G/L accounts defined in set ZGL_TRAD_PART_REQD (Figure 2)
- Selected users defined in set ZUSR_TRAD_PART_REQD (Figure 3)
- Selected document types defined in set ZDOC_TYPE_TRAD_PART_REQD (Figure 4)
Check:
The check verifies that the Trading Partner (VBUND) field is populated.
Message:
If the prerequisite conditions are met and Trading Partner is blank, the system issues an error message.
This validation prevents the applicable financial document from being posted until the required Trading Partner value is entered.
Figure 1: FI Validation for Missing Trading Partner
Prerequisite:
BSEG-HKONT IN ZGL_TRAD_PART_REQD AND
BKPF-USNAM IN ZUSR_TRAD_PART_REQD AND
BKPF-BLART IN ZDOC_TYPE_TRAD_PART_REQD
Check:
BSEG-VBUND <> ''
Message:
Error Z1 032 Trading Partner is required for GL
Figure 2: G/L Account Set for Trading Partner Validation
Figure 3: User Set for Trading Partner Validation
Figure 4: Document Type Set for Trading Partner Validation
SAP Trading Partner Validation Summary
Organizations can use several configuration approaches to control Trading Partner entry during financial document posting.
Field status and document type settings can influence whether Trading Partner is available for entry, but they have limitations when the field must be mandatory.
FI validation provides a more flexible approach for checking whether Trading Partner information has been entered for selected transactions. By defining appropriate prerequisites, checks, and error messages, organizations can help prevent incomplete intercompany postings and improve the accuracy of financial reporting, reconciliation, and consolidation.
Reference:
SAP Note 1397715 - FI - Adding VBUND to the coding block
Glossary
Company Code
Company Code is an organizational unit in SAP Financial Accounting (FI) used to maintain financial records and produce financial statements for a legal entity or accounting unit. Company codes can be assigned to companies for intercompany reporting and consolidation.
Cost Center
Cost Center is an organizational unit used to collect and monitor costs for a defined area of responsibility in SAP Controlling.
Document Type
Document Type classifies accounting documents in SAP and controls certain document-level settings. In this article, document type configuration can make Trading Partner available for entry during financial document posting.
F.13 - Automatic Clearing
F.13 is an SAP transaction used to automatically clear open items that meet defined matching criteria. It can help streamline reconciliation and clearing activities in Financial Accounting.
FBL3N - G/L Account Line Item Display
FBL3N is a classic SAP transaction used to display G/L account line items. It allows users to review individual postings for selected G/L accounts and analyze financial transaction details.
Field Status Group
Field Status Group controls whether fields are required, optional, displayed, or suppressed during financial document posting. The Trading Partner field (VBUND) is not available as a standard field status group option.
Financial Consolidation
Financial Consolidation combines financial information from multiple companies into consolidated financial statements. The process includes eliminating intercompany transactions and balances to present the financial position and performance of the corporate group as a single economic entity.
FI Validation
FI Validation checks defined conditions before a financial document is posted. A validation consists of a prerequisite, check, and message and can be used to require Trading Partner information for selected transactions.
FS10N - G/L Account Balance Display
FS10N is a classic SAP transaction used to display G/L account balances by fiscal year and posting period. It provides a summarized view of account balances with the ability to analyze financial activity.
Intercompany Transactions
Intercompany Transactions are business transactions between companies within the same corporate group. Examples include intercompany sales, purchases, loans, and transfers. Trading Partner information helps identify these transactions for reconciliation, reporting, and financial consolidation.
Profitability Analysis
Profitability Analysis in SAP Controlling supports analysis of profitability by market segments such as customers, products, sales organizations, and other characteristics.
Profit Center
Profit Center is an organizational unit used for internal management reporting and responsibility-based analysis. Profit centers can be used to analyze financial results across business areas, divisions, or other organizational units.
SAP Fiori
SAP Fiori provides role-based applications for accessing and managing SAP S/4HANA processes. Depending on system configuration and available apps, users can perform Financial Accounting activities and analyze financial information through the SAP Fiori launchpad.
SAP Universal Journal
SAP Universal Journal provides a single source of financial and management accounting data in SAP S/4HANA. Actual postings are stored in ACDOCA, enabling integrated reporting across Financial Accounting, Controlling, and related processes.
Source Cost Element
Source Cost Element identifies the original cost element from which costs are allocated or settled in SAP Controlling, helping retain information about the nature of the original costs.
Tracing Factor
Tracing Factor defines how costs are distributed among receiver objects during periodic allocations in SAP Controlling. Examples include statistical key figures, percentages, fixed amounts, or other allocation bases.
Trading Partner
Trading Partner identifies the company involved in an intercompany transaction in SAP. The Trading Partner field (VBUND) supports intercompany reporting, reconciliation, and financial consolidation.