Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FREP (Package) RF reporting
Basic Data
| Data Element | UMSVFB01 |
| Short Description | Replace Transaction FB05 with FB01 |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 0 | |
| Medium | 0 | |
| Long | 0 | |
| Heading | 0 |
Documentation
Definition
This has the effect that the clearing of open G/L account items is done in 2 phases.
Transaction FB01 (Post Document) is called up instead of transaction FB05 (Post with Clearing).
Firstly, the program notes the number of the document posted with FB01. It then creates a clearing document for the document posted in the first step, and for additional documents determined by the program.
If an error occurs in the first phase, the data is saved in a batch input session.
In this case it is no longer possible to clear the postings automatically, and you have to carry out the clearing manually.
Use
This procedure is used in Italy to display the deferred documents correctly in report RFUMSV20.
Procedure
Examples
Dependencies
To use this function, you have to select the field 'Call transaction'.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
