Ansicht
Dokumentation
SAPDBFMF - Logical Database FMF : Database Program
PERFORM Short Reference SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
Title
Logical Database for Funds Management
Purpose
Using logical database (LDB) FMF is an easy way to import master data and transaction data and then process them.
The selection of master data is independent of the selection of transaction data. The assignment of transaction data to the respective master data is, in contrast to LDB F1F, not statistical and results in better performance. The corresponding assignment is only performed during the execution of a report that uses the FMF LDB.
In setting the indicators Master data is selective or Transaction data is selective, the users themselves can decide whether the master data is selected first and then the corresponding transaction data; or whether the transaction data is selected first and then the attributes of the corresponding master data.
- Master data is selective
If this indicator is set, all funds, funds centers and commitment items of the current FM area are imported to an FM area. As soon as the FM account assignments have been defined according to the selection criteria, only the transaction data (budget values as well as commitment and actual values) is selected for these.
This indicator should, for example, be used if an evaluation is to be carried out for only a limited number of FM account assignments.
- Transaction data is selective
If this indicator is set, all transaction data is first selected for an FM area. The master data is then only selected for the relevant FM account assignments according to the corresponding selection criteria.
This indicator should, for example, be used if an evaluation is to be performed for only a small number of document numbers, but the FM account assignment is not known.
Whereas the FM account assignments are depicted along with their respective attributes in the master data nodes, the nodes for the transaction data in essence are divided into totals records and line items. The totals records can be used if you want to get an overview of the whole situation. The line items are best suited for a detailed depiction of special business transactions.
If a report is processing the node Year-end closing (FMCFX) in order to display year-end closing data, an additional parameter for the fiscal year to be closed (or already closed) as well as 2 selection buttons will appear on the selection screen. This means on the one hand that year-end closing data can always only be displayed for one fiscal year. On the other hand, you can use the selection buttons to differentiate whether the values already carried forward are to be displayed, or whether the values that have been preselected for carryforward are displayed.
The nodes Funds (FFND), Funds center (FCTR) and Commitment item (FPOS) cannot be processed together with node FM account assignment (FMAA) in the same report. You should use nodes FFND, FCTR and FPOS when only master data (funds, funds center or commitment item) but not tranaction data is to be selected; or when transaction data is to be selected first and the attributes of all attributes (such as short text) of the FM account assignment are not needed for the evaluation, but only the fund (or funds center or commitment item) for example.
The General selection criteria for FMF node (FMF_SEL_SCREEN) is only for the generation of the selection screen. In the GET FMF_SEL_SCREEN, the fields of the nodes are always transferred empty and only once.
The nodes for the transaction data (BPBTX, BPBPX, FMTOX, FMOIX, FMFIX, FMCOX, FMCFX) always contain the key FM account assignment. In doing so, the transaction data is assigned to the master data.
- Parameters for node General selection criteria for FMF (FMF_SEL_SCREEN)
- Parameter for performance optimizing
P_FMBUD = 'X' Master data is selective
First the master data is selected and then all the transaction data for this master data.
P_BUDFM = 'X' Transaction data is selective
First the transaction data is selected and then the master data for this transaction data.
- P_FMAADN 'X' Including subordinate FMAA
All subordinate FM account assignments in accordance with the Budget structure are selected for the selected FM account assignments.
- P_FMAHIE 'X' Hierarchical order
The selected FM account assignments are issued in hierarchical order in accordance with the Budget structure.
- P_STAMM 'X' Only master data posted to
The only FM account assignments that are selected are those for which transaction data is selected. You should only use this parameter in conjunction with parameter Master data is selective.
- Parameters for node Assigned FM account assignments (FMAAREL)
- P_ED 'X' Unilateral CE
The only FM account assignments selected are those relevant for unilateral cover eligibility.
- P_UD 'X' Revenues increasing the budget
The only FM account assignments selected are those relevant for revenues increasing the budget.
- P_GD 'X' Cover pool
The only FM account assignments selected are those relevant for cover pools.
- P_RP 'X' Revenues cover pool
The only FM account assignments selected are those relevant for revenues cover pools.
- P_ONLY_R Only FM account assignments eligible for cover
'X': Only the master data (or transaction data) of FM account assignments with cover eligibility relationships is selected.
SPACE: The master data (or transaction data) of FM account assignments that have no cover eligibility relationships is also selected.
- Parameters for node FM account assignments assigned to collective expenditure (FMSNREL)
- P_CENT = 'X' Central
The node FMSNREL contains the central collective expenditure FM account assignments.
- P_DEC = 'X' Local
The node FMSNREL contains the local collective expenditure FM account assignments.
Integration
Prerequisites
Features
An important aspect when using FMF is performance. You should therefore restrict the selection criteria for FM area, fund, funds center, commitment item, functional area or cover pool as greatly as possible. For this reason, these selection fields appear as standard on the selection screen of all programs that use FMF.
If possible, parameter Master data is selective or Transaction data is selective should be prespecified in the report, so that the user cannot select any settings that have a negative effect on performance.
You can also define the selection criteria for funds, funds centers and commitment items using the classification on the selection screen.
You can define extended selection criteria using the dynamic selection. This allows you to call up many fields of the node being used in the corresponding report (such as document number) for the definition of selection criteria.
You can select the data source for reports with the nodes FMFIX (line items from FI documents) and FMTOX (totals records: commitment actual). You can enhance the selection from the database tables using the selection of the archived data. The archived data can be accessed using the archive information system or by selecting the files manually. In the case of manual selection of archive files, the correct archiving object must be entered. For reports that process the node FMFIX, you enter the archiving object FM_DOC_FI and FM_ACTSUM for reports that process the node FMTOX.
It is not possible to define a maximum number of hits (parameter P_MAXSEL) for reading from the archive; all corresponding data is read.
Selection
Standard Variants
Output
Activities
Example
General Data in Customer Master Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.
Length: 9765 Date: 20240531 Time: 145709 sap01-206 ( 177 ms )
