Hierarchy
⤷ TR-CB (Application Component) Cash Budget Management
⤷ FFCBI (Package) Cash Budget Management - Integration
Basic Data
Data Element | CBM_SLEEP_FI |
Short Description | Cash Budget Mgt: Online Update from FI Not Active |
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 | 10 | FI Off |
Medium | 20 | FI Update Off |
Long | 25 | FI Update Off |
Heading | 25 | FI Update Off |
Documentation
Definition
Verification of the source and appliycation of payment flows is the central task of Cash Budget Management. To this end, it is essential to record transaction data from documents posted in FI.
You can use this switch to deactivate the corresponding update. This is a good idea as a temporary measure if you want to reconstruct the Cash Budget Management transaction data from FI in full. Normally, no further FI documents may be posted in the system while this reconstruction is in progress. However, if the quantity of data to be reconstructed is very large, the time available may not be sufficient.
If you find yourself in this situation, activate Cash Budget Management and this switch, and reconstruct the data from the old, closed periods (using program RFFMRP52). Postings are still possible during this process. Cash Budget Management ensures, for example, that commitment items are entered in newly posted purchase orders and their follow-up documents.
For the reconstruction of FI transaction data from posting periods currently open, you need only a time window with no FI postings. Once the full reconstruction is complete, you must reactivate this switch immediately, thereby reactivating the transaction data update from FI.
History
Last changed by/on | SAP | 19991110 |
SAP Release Created in |