SAP Note

158739 - Validation when parking documents in FI

Component: FI-GL-GL-W (Financial Accounting > General Ledger Accounting > Basic Functions > Preliminary
Posting/Workflow), Version: 19, Released On: 09.06.2010

Symptom

When you park FI documents using the classic parking transactions FBV0, FBV1 and FBV2, the
FI validations are processed at call-up points 1, 2 and 3. Prior to Release 4.0A, these
validations were only processed when posting the parked document.

The substitution is performed only when posting the document, as before. There are no plans
to change this process. See also Note 48121 for information about dialog boxes, warnings,
information messages or "COMMIT WORK", as the parked documents are updated using a batch
input process.

Other Terms

Document parking, FBV1, validation, F-63, F-64, F-65, F-66, F-67, FIPP, FBV0
G_VSR_VALIDATION_CALL, ENJOY, FV50, FV60

Reason and Prerequisites

Due to several customer requests, FI document parking was added to the validation functions.

Validation is now performed when

- parking a document (transactions FBV0, FBV1 and FBV2)

- setting a parked document to complete and
- posting a parked document using transaction FBVB (as before).

Here, we must point out a possible misunderstanding: In transaction

FBV0, it is possible to post the parked document (by calling the posting transaction FBVB or
FB01 internally), but transaction FBV0 is not a posting transaction from a technical point
of view, but purely a parking transaction. No substitution is performed in transaction FBV0
itself. To prevent a validation from producing errors due to a missing substitution within
the parking process in transaction FBV0, for example (if validation checks for
substitution), validation must be turned off completely during the parking process (see the
procedure under "Solution").

Solution

To ensure that the validations are not active for FI document parking, you must add a rule
to the prerequisite. This rule could look as follows:

NOT ( SYST-TCODE = 'FBV0' AND BKPF-GLVOR = 'RFBV' ) AND

NOT ( SYST-TCODE = 'FBV1' AND BKPF-GLVOR = 'RFBV' ) AND
NOT ( SYST-TCODE = 'FBV2' AND BKPF-GLVOR = 'RFBV' ) AND

To ensure that the validations are not active when saving as complete, you must add a rule
to the prerequisite. This rule could look as
follows:

NOT ( SYST-TCODE = 'FBV0' AND BKPF-GLVOR = 'RFBU' )

(the same for FBV1 and FBV2)

If you do not want to validate during parking nor when saving as complete, you must combine
these two rules with AND:

NOT ( SYST-TCODE = 'FBV0' AND BKPF-GLVOR = 'RFBV' ) AND

NOT ( SYST-TCODE = 'FBV1' AND BKPF-GLVOR = 'RFBV' ) AND
NOT ( SYST-TCODE = 'FBV2' AND BKPF-GLVOR = 'RFBV' ) AND
NOT ( SYST-TCODE = 'FBV0' AND BKPF-GLVOR = 'RFBU' )

When posting a parked document, the field BKPF-GLVOR is set to 'RFBU'. To prevent the system
performing a validation when posting a parked document, the condition must read as follows:

NOT ( SYST-TCODE = 'FBV0' AND BKPF-GLVOR = 'RFBU' )

After the validation is performed in the parking process, the program actually posts the
document using batch input. The variable SYST-TCODE = 'FBVB', and the prerequisite for the
validation is then fulfilled: the step is performed. This validation occurs after the
substitution.

Validation and EnjoySAP parking transactions:

--------------------------------------------------
The statements above apply to the classic parking transactions only. If you also work with
all new FI EnjoySAP parking transactions (FV50, FV60 and so on), you must also enhance the
rules listed above as follows:

AND NOT ( SYST-TCODE LIKE 'FV*' AND

( BKPF-GLVOR = 'RFBV' OR BKPF-GLVOR = 'RFBU' ) )

If you only want to refer to one of the parking transactions

(FV50, for example), the enhancement should look as follows:

AND NOT ( SYST-TCODE = 'FV50' AND

( BKPF-GLVOR = 'RFBV' OR BKPF-GLVOR = 'RFBU' ) )

------------------------------------------------------------------------
* Note the following:
------------------------------------------------------------------------

There is a critical difference between the FI EnjoySAP parking transactions and the old
parking transactions:

In the old transactions - FBV1, for example - the validation is performed when parking as
well as when saving as complete.

In the EnjoySAP parking transactions, such as FV50, the handling is different: Generally,
validation is not performed. This allows the end user to at least park the entered document.
The validation is carried out only when saving as complete or when posting.

In the EnjoySAP posting transactions, such as FB50, the validation is generally performed
(for every time "Enter" is chosen). The validation not carried out only when parking, so
that the document can be parked.

In other words: "Complete" + "Post" always validates, "Park" never.

However, if you want to always validate the documents in the FI EnjoySAP parking
transactions, the "Park" button must be deactivated. For further information, see Note
361420.

Attributes
Key Value

Other Components Financial Accounting > Special Purpose Ledger > Validation, Substitution and Rules (FI-SL-VSR)

Transaction codes FBV1

Transaction codes FBV0

Transaction codes FBV2

Transaction codes F-63

Transaction codes F-65

Transaction codes F-64

Transaction codes F-66

Transaction codes F-67

This document refers to

SAP Note/KBA Component Title

896778 FI-GL-GL-W FBV0: No posting possible due to error 00349

863267 FI-AP-AP-A FAQ: Validations in Enjoy transactions

548645 FI-GL-GL-W Validations with display parked documents

48121 FI-SL-VSR User Exits in Validations/Substitutions

1765373 FI-AP-AP-W ENJOY: Posting/completely despite validation error V

This document is referenced by

SAP Note/KBA Component Title

1765373 ENJOY: Posting/completely despite validation error V

863267 FI-AP-AP-A FAQ: Validations in Enjoy transactions

896778 FI-GL-GL-W FBV0: No posting possible due to error 00349

842318 FI-SL-VSR Frequently asked questions about validations and substitutions

48121 FI-SL-VSR User Exits in Validations/Substitutions

548645 FI-GL-GL-W Validations with display parked documents