
There are 5 call-up points which can be used for Substitution or Validation. Substitutions are also activated at the company code level and can be a constant value, a user exit or field-field assignment Call-up Points and Boolean Class

A substitution is enforced if the prerequisite is met. Substitutions are used to substitute a document field value and consist of a prerequisite and substitution. They are used to examine settings, say, postings from company code to business area are made or not. The validation rules are activated at company code level. If the prerequisite is met and the check is not fulfilled, the message is displayed. Validation consists of perquisite, check and message. The situations may or may not apply for substitutions and validations in other application areas Introduction This document explains the situations for FI Substitutions/Validations exclusively.


To overcome the situation it is possible to fill XACCIT-GSBER by using Userexit EXIT_SAPLV60B_002: FBKP) for the field status group assigned to the G/L account, the error message F5808 (Field business area is a required field fo G/L account) appears. If the business area is flagged as required field (tr.

Note 1490708 is automatically implemented into the system with the following Support Packages:īy applying the note following source code is introduced in FORM ACCOUNTING_HEAD_LINE which is responsible for the missing business area: The business area is no longer taken over from the invoice. With note 1490708, the system behavior concerning the transfer of the business area of the invoice item (field VBRP-GSBER) to the accounting document (field BSEG-GSBER) had been changed radically. In most cases this phenomenon occurs when an invoice is being posted to accounting after a system upgrade.
