Hierarchy
EA-PS (Software Component) SAP Enterprise Extension Public Services⤷
PSM-FM (Application Component) Funds Management⤷
FMFG_BLCORE_E (Package) Core of the Budgetary Ledger
Basic Data
| Data Element | NO_SUCCESSOR |
| Short Description | Correct Entries Without Successors |
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 | NO_SUCCESSOR | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | No Succsrs |
| Medium | 20 | Correct w/o Succsrs |
| Long | 40 | Correct Entries Without Successors |
| Heading | 25 | Correct w/o Successors |
Documentation
Definition
To correct Funds Management (FM) entries without a successor document
Use
Only use this feature for exceptional cases and with great care. If this option is selected, the Budgetary Ledger (BL) correction program will process those documents for which no FM successor entries are found. This could happen if the successor entries were not generated in FM or the transaction numbers (field TRANR) in table FMIOI and FMIFIIT do not match, say, as a result of FM re-posting.
In theory, for every posting in Funds Management, the FM original entry (successor) and and FM reduction (predecessor) entry should have identical values stored in TRANR. However, it could happen that this does not hold true.
The default behavior of the BL correction program is to issue an error message in the Application Log and to not process documents with such FM data problem. However, if selected, this option will cause the BL correction program to issue only a warning and continue to process these documents.
Keep in mind that correcting these documents without FM successor entries may not be the complete equation since those FM successor entries have not been considered. As a result, you may have to correct those successor documents without matching FM predecessor entries. To do this, you can use the other complementary option "Correct Entries Without Predecessors".
See below for an example of a case where this option "Correct Entries Without Successors" may be used.
Dependencies
Example
You have a purchase order (PO) document PO1 for $100. Then you create a goods receipt (GR) for GR1. Here is what table FMIOI and FMIFIIT may be updated with:
For the posting of the PO1:
Table FMIOI:
REFBN REFBT BTART STUNR TRANR FKBTR
PO1 020 0100 3000000000000004 3000000000000004 -100
For the posting of the GR1:
Table FMIOI:
REFBN REFBT BTART STUNR TRANR FKBTR
PO1 020 0200 3000000000000006 3000000000000006 +100
Table FMIFIIT: Assume GR1 is the FI document number for the goods receipt.
KNBELNR WRTTP BTART STUNR TRANR FKBTR
GR1 54 0100 3000000000000005 3000000000000005 -100
Notice that the two entries generated by the GR1 posting have different TRANR. Normally, they should have the same TRANR. So if you do not select the option to correct entries without successors, the PO1 reduction entry may never be processed. You can process the GR1 original entry by selecting the option to correct entries without predecessors (being PO1), in which case the following entry is processed:
KNBELNR WRTTP BTART STUNR TRANR FKBTR
GR1 54 0100 3000000000000005 3000000000000005 -100
Now, to correct the PO1 reduction entry, you can select the option to correct entries without successors (being the GR1). In this case, the following entry is processed.
REFBN REFBT BTART STUNR TRANR FKBTR
PO1 020 0200 3000000000000006 3000000000000006 +100
History
| Last changed by/on | SAP | 20040322 |
| SAP Release Created in | 500 |
