SAP Program RFFMTOBL - Transfer Commitments to Budgetary Ledger

Title
Transfer Funds Management Commitments to FI Budgetary Ledger

Purpose
The previously used program RFFMTOBL is for the transfer FundsManagement (FM) commitments to the FI Budgetary Ledger, which forms partof FI-GL. This program has been replaced by the enhanced versionavailable as program RFFMTTTOBL. You can make thisenhancement available by deactivating all implementations forBAdI_FM_FM2AC.
It is possible to request specific FM information (encumbrances)available in FI-GL for FI balance and FI reporting purposes. Datatransfer programs copying encumbrances into FI-GL are offered for thispurpose.
The following procedures are known:

  • Budgetary Ledger

    • Real time postings of budget information from FM into FI. A specialledger is defined to hold the budget information in FM.
    • Collective data transfer on monthly basis

      • Summarized mirroring function for FM encumbrances into FI. This year todate report will synchronize FM commitment information with FI-GL.
      This documentation covers the second of the above procedures.

      Prerequisites
      Besides encumbrance postings in FM, a prerequisite for the report is thecompletion of several Customizing steps. This enables you to define thelevel of detail for information transferred from FM to FI-GL. ForCustomizing, BAdI exits are offered for you to define your own businessspecifics.

      Brief Introduction to the BAdI Providing the Exits for this Process
      Several methods are set up in the BAdI_FM_FM2AC
      . At original delivery, the SAP implementation methods for this BAdIare active. The BAdI specifies methods for additional fields to betransferred, derivation routines for them and settings for creating theFI document. You can change the predefined methods by applying your ownimplementation of the BAdI. The BAdI definitions can be found undertransaction code SE18 and the implementations undertransaction code SE19. The debit and credit G/Laccounts should be derived from an FM G/L account and the value typesettings. This function is available in a Customizing table.
      The program also uses Business Transaction Events (BTEs). These eventsare the predecessors of BAdIs and another way of configuring theinterface. The BTEs have interface numbers associated with them and canbe found in transaction FIBF.
      The following are the steps involved:
      Use transaction OFMTOAC2 to specify debit andcredit G/L accounts in Customizing table FMAC2. (Note: This table wasintroduced in a newer program version and needs to be activated duringfirst execution. Therefore, first access the configuration table usingthe application button in the program selection screen. The Customizingtable should show the G/L account settings pulled from BTE 00108010.)
      Decide on the transfer details. The program supports transfer of thefollowing account assignment objects:
      Company code
      FM Area
      Funds center (Enable/Disable)
      Fund
      Functional area (Enable/Disable)
      Business area (Enable/Disable)
      Profit center (Enable/Disable
      You can enter your own enable/disable settings in BAdI implementationmethod FM_FMAC_GET_CTRL_PARAMETER. To this end, you need to disable themethod supplied by SAP and enable your implementation method for thisfunction activated. This implementation should specify your preferenceon dimensions to be transferred (enable = 'X'= transfer; disable = space= skipped). The business area and profit center are not always availableon the summary level table FMIT. With the flag E_FLAG_SELECT_ON_ITEM theprogram can be switched to access the information from the item leveltable FMIOI. All account assignment objects are available, but theperformance for an annual process may be slow.
      Alternatively, you can configure the system to keep more detail on thesummary level (FMIT table) and derive the necessary account assignmentobjects for your transfer preference using the BAdIFM_FMAC_DERIVE_SPECIFIC BAdI. The procedures important to updating FMITin greater detail are as follows:
      Carry the CO object into summary table FMIT.
      Support CO objects in FMIT by populating the customer exit 001 in theSAP enhancement SAPLFMOI. Extend by moving the CO object from the inputto the output. With this Customizing setting, the CO object is availableon the summary level and can be used to derive specific dimensions (suchas profit center) in the BAdI exit. SAP Enhancements can be found undertransaction code SMOD.
      Availability of USERDIM field. Generally, this field is available torecord customer-specific dimensions on the line item and summary level.If this field is not used for other purposes, it can contain thebusiness area or profit center and make these objects availableautomatically on the summary level. The user field is passed to theFMIOI structure and is available in the FM_FMAC_DERIVE_SPECIFIC BAdImethod.
      Verify the assignment of the document type for the FI document in BAdImethod FM_FMAC_FI_DOCUMENT_TYPE.

      Description
      It is only necessary to post totals resulting from encumbrances forbalance sheet purposes and report on a monthly basis (only periodicpostings). The status indicator makes it possible to identify thedocuments originating from FM, Purchasing, Travel Management, and FI,which need to be posted in FI. Then identify the posting document by thedocument type.
      The program parameters are as follows

      • Company code

        • The company code used to get totals from FM and transfer them into FIGeneral Ledger
        • Fund

          • The funds to which the encumbrances are assigned. With no input, all thefunds are selected
          • To period

            • The period to which the totals are calculated from period 1
            • To year

              • The fiscal year in which the totals are calculated in the specifiedperiods
              • Posting date

                • The date on which the FM totals are transferred to FI General Ledger
                • Fiscal year

                  • The year in which the encumbrances are posted to FM
                  • Posting period in FI-GL

                    • The period in FI General Ledger to which the FM totals are transferred
                    Processing options
                    • Test run

                      • The documents are not changed in the database
                      • Detailed list

                        • With this option, the lists of Transferred to FI-GL, CurrentFM items and Old data in FI-GL are displayed only if theiritems are available.

                        Output
                        Depending on the parameters you have chosen, the program generates thefollowing lists. The default output is as follows:
                        Local date, local time, program title, and page number
                        General information on FI documents: FM area, company code, FM currency,fiscal year, posting period, and posting date
                        Messages output during processing
                        Statistics block showing total information about FM items read, priorFI/GL accounting document items read and new FI/GL accounting documentitems
                        If further details were requested, the output shows line item details inthe SAP List Viewer. A two-dimensional layout contains the blocks of FMitems read, the prior FI/GL accounting document items read, and newFI/GL accounting documents.

                        Example
                        Create a purchase order and transfer the totals to FI General Ledger.When the amount is changed in the purchase order, only the difference inthe totals will be transferred from FM to FI General Ledger. Thetransferred detail information should contain the functional area andfunds center. The document type for the FI document should be SA.Purchase order transfers should end up on account 950400 for debit and959998 for credit postings.
                        Here are the configuration entries for this example:

                        • GL account derive table FMAC2:

                          • ,,FM GL account,,| Value type,,| GL debit account,,| GL credit account
                          ,,,,| 50,,| 950200,,| 959998
                          ,,,,| 51,,| 950400,,| 959998
                          • BAdI implementation for method FM_FMAC_GET_CTRL_PARAMETER:

                            • E_FLAG_SELECT_ON_ITEM = space
                            E_FLAG_COMMITMENT_LEDGER = X
                            E_FLAG_PAYMENT_LEDGER = X
                            E_FLAG_FUNCTIONAL_AREA = X
                            E_FLAG_FUNDS_CENTER = X
                            E_FLAG_BUSINESS_AREA = space
                            E_FLAG_PROFIT_CENTER = space
                            • BAdI implementation for method FM_FMAC_DERIVE_SPECIFIC:

                              • E_FM_DATA_OUT = I_FM_DATA_IN.
                              • BAdI implementation for method FM_FMAC_FI_DOCUMENT_TYPE:

                                • E_FI_BLART = SA
                                The following scenario is used to show this process:
                                Scenario: Records in FI General Ledger
                                Encumbrances,,|Reserved fund balance
                                ,,(FM side),,,,|(FI-GL side)
                                ,,|Debit,, |Credit,,|Debit,,|Credit
                                Create a PO with $100,,| 100,,,,|,,-100
                                Change the PO to $120,,| 20,,,,|,,- 20
                                Change the PO to $80 ,,|,, -40,,| 40