Kontakt

Ansicht
Dokumentation

RFFMTOBL - Transfer Commitments to Budgetary Ledger

RFFMTOBL - Transfer Commitments to Budgetary Ledger

rdisp/max_wprun_time - Maximum work process run time   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Title

Transfer Funds Management Commitments to FI Budgetary Ledger

Purpose

The previously used program RFFMTOBL is for the transfer Funds Management (FM) commitments to the FI Budgetary Ledger, which forms part of FI-GL. This program has been replaced by the enhanced version available as program RFFMTTTOBL. You can make this enhancement available by deactivating all implementations for BAdI_FM_FM2AC.

It is possible to request specific FM information (encumbrances) available in FI-GL for FI balance and FI reporting purposes. Data transfer programs copying encumbrances into FI-GL are offered for this purpose.

The following procedures are known:

  • Budgetary Ledger
Real time postings of budget information from FM into FI. A special ledger 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 to date 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 the completion of several Customizing steps. This enables you to define the level of detail for information transferred from FM to FI-GL. For Customizing, BAdI exits are offered for you to define your own business specifics.

Several methods are set up in the BAdI_FM_FM2AC. At original delivery, the SAP implementation methods for this BAdI are active. The BAdI specifies methods for additional fields to be transferred, derivation routines for them and settings for creating the FI document. You can change the predefined methods by applying your own implementation of the BAdI. The BAdI definitions can be found under transaction code SE18 and the implementations under transaction code SE19. The debit and credit G/L accounts should be derived from an FM G/L account and the value type settings. This function is available in a Customizing table.

The program also uses Business Transaction Events (BTEs). These events are the predecessors of BAdIs and another way of configuring the interface. The BTEs have interface numbers associated with them and can be found in transaction FIBF.

The following are the steps involved:

  1. Use transaction OFMTOAC2 to specify debit and credit G/L accounts in Customizing table FMAC2. (Note: This table was introduced in a newer program version and needs to be activated during first execution. Therefore, first access the configuration table using the application button in the program selection screen. The Customizing table should show the G/L account settings pulled from BTE 00108010.)
  2. Decide on the transfer details. The program supports transfer of the following 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 implementation method FM_FMAC_GET_CTRL_PARAMETER. To this end, you need to disable the method supplied by SAP and enable your implementation method for this function activated. This implementation should specify your preference on dimensions to be transferred (enable = 'X'= transfer; disable = space = skipped). The business area and profit center are not always available on the summary level table FMIT. With the flag E_FLAG_SELECT_ON_ITEM the program can be switched to access the information from the item level table FMIOI. All account assignment objects are available, but the performance for an annual process may be slow.
    Alternatively, you can configure the system to keep more detail on the summary level (FMIT table) and derive the necessary account assignment objects for your transfer preference using the BAdI FM_FMAC_DERIVE_SPECIFIC BAdI. The procedures important to updating FMIT in 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 the SAP enhancement SAPLFMOI. Extend by moving the CO object from the input to the output. With this Customizing setting, the CO object is available on the summary level and can be used to derive specific dimensions (such as profit center) in the BAdI exit. SAP Enhancements can be found under transaction code SMOD.

  • Availability of USERDIM field. Generally, this field is available to record customer-specific dimensions on the line item and summary level. If this field is not used for other purposes, it can contain the business area or profit center and make these objects available automatically on the summary level. The user field is passed to the FMIOI structure and is available in the FM_FMAC_DERIVE_SPECIFIC BAdI method.

  1. Verify the assignment of the document type for the FI document in BAdI method FM_FMAC_FI_DOCUMENT_TYPE.

Description

It is only necessary to post totals resulting from encumbrances for balance sheet purposes and report on a monthly basis (only periodic postings). The status indicator makes it possible to identify the documents originating from FM, Purchasing, Travel Management, and FI, which need to be posted in FI. Then identify the posting document by the document type.

The program parameters are as follows

  • Company code
    The company code used to get totals from FM and transfer them into FI General Ledger
  • Fund
    The funds to which the encumbrances are assigned. With no input, all the funds 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 specified periods
  • 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, Current FM items and Old data in FI-GL are displayed only if their items are available.

Output

Depending on the parameters you have chosen, the program generates the following lists. The default output is as follows:

  1. Local date, local time, program title, and page number
  2. General information on FI documents: FM area, company code, FM currency, fiscal year, posting period, and posting date
  3. Messages output during processing
  4. Statistics block showing total information about FM items read, prior FI/GL accounting document items read and new FI/GL accounting document items

If further details were requested, the output shows line item details in the SAP List Viewer. A two-dimensional layout contains the blocks of FM items read, the prior FI/GL accounting document items read, and new FI/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 in the totals will be transferred from FM to FI General Ledger. The transferred detail information should contain the functional area and funds center. The document type for the FI document should be SA. Purchase order transfers should end up on account 950400 for debit and 959998 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






CPI1466 during Backup   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 12395 Date: 20240601 Time: 114937     sap01-206 ( 170 ms )