Ansicht
Dokumentation

SIMG_CFMENUOFTFOF06 - Define Commitment Item for Unassigned Expenditures/Revenues

SIMG_CFMENUOFTFOF06 - Define Commitment Item for Unassigned Expenditures/Revenues

BAL_S_LOG - Application Log: Log header data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

In this step, you define a commitment item for unassigned revenues and expenditures per FM area. You must do this if existing open items can no longer be assigned to a commitment item, because the reference to earlier postings no longer exists.

This might be the case, for example, if you are already using Financial Accounting and now want to install Cash Budget Management. Posting data from business transactions posted before you installed Cash Budget Management (such as invoices received) are not passed on to Cash Budget Management, because no commitment items were stored in the G/L accounts at the time the posting was made.

To ensure that the cash flow statement is nevertheless consistent, define a commitment item for unassigned revenues, and another for unassigned expenditures. The postings made before Cash Budget Management was activated are collected here, transferred to Cash Budget Management, and displayed in the information system as revenue or expenditure items.

  1. In Cash Budget Management, enter a commitment item for unassigned revenues, and another for unassigned expenditures. You create them as account assignment items (with financial transaction 30, and item category 2 for the revenue item and item category 3 for the expenditure item). You should not connect these commitment items to the rest of the commitment item hierarchy, or to the other subhierarchies.
  2. In the FM area, store a commitment item for unassigned revenues, and another for unassigned expenditures.





BAL_S_LOG - Application Log: Log header data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 1968 Date: 20240524 Time: 013129     sap01-206 ( 68 ms )