Ansicht
Dokumentation

Enhancements to the Budget Control System (Changed / New) ( RELNPSM_60_FM_BCS_COLLEC )

Enhancements to the Budget Control System (Changed / New) ( RELNPSM_60_FM_BCS_COLLEC )

General Material Data   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Enhancements to the Budget Control System (Changed / New)

Use

As of SAP ECC 6.0, Public Services (EA_PS 600), there are several enhancements and new developments in the area of the Budget Control System. With the exception of the subject of migration activities, these new developments are summarized in this release note. For migration activities, please see the release note for the corresponding IMG node.

1) Balanced Budget Entry

A new budgeting process, called "Balanced Entry", has been defined to enable a balanced budget increase in BCS. Using this process, you can enter source data only for revenue commitment items, and target data only for expenditure commitment items. The amounts for the source and the target must be identical. The system check is then carried out per fiscal year (and per year of cash effectivity if applicable). The logic is similar to the one implemented for Revenues Increasing the Budget (RIB), except that no specific rule is required.

2) Enhancement of Budgetary Ledger (BL) Integration

If the budgetary ledger is active, some preliminary checks are performed by BCS upon posting:

  • Only transactions which create entry documents are permitted.
  • The posting date is mandatory.
  • The budget period within a document must correspond to the posting date. For this reason, transfer between periods and carryover were previously not supported, since they deal with more than one period.

Previously, BCS applied these checks to all budget data as soon as the BL was activated for an FM area. To avoid running this check on a very high level - since BL has its own filter (for example, per budget category, per budgeting process.) - only the data which updates BL is now checked by BL itself. For BCS, the impact of the BL activation is as follows:

  • The posting date can be entered when entry documents are processed, but it is no longer mandatory.
  • If the posting date has been entered, the budget period in the document should correspond to the posting date.
  • For transfer between periods, for other sending/receiving processes (such as carryover), or for budget entry in multiple periods, the posting date should not be entered.

  • For sending/receiving budget carryforwards, you should leave the posting date field empty. Otherwise, this field should correspond to either the sender budget period or the receiver budget period. No check is carried out for the budget period on the other side, which can be for the receiver or the sender.

  • Special periods can be used for budgeting.
Comment
Whenever an entry document is involved, the Budgetary Ledger is called and all necessary checks are carried out by the BL. Nevertheless, if data is entered without entry documents (for example, budget prep data entered via the planning transaction FMPLCPD, the generation of plan data, totals migration, etc.), BL will not be called and no check is performed.

3) SAP List Viewer Layout in BCS Transactions

You can use the SAP List Viewer in BCS transactions for which a detailed output list can be displayed. The output list contains the layout defined for the specified variant on the entry screen.

4) Revenue-based Expenditure Control

Using a customer AVC ledger, you can perform a further availability control check, in which FM commitment/actual documents consuming expenditure budget are checked against FM commitment/actual documents consuming revenue budget. This ensures that FM posting documents consuming expenditure budget can be posted only if FM posting documents consuming revenue budget were previously posted with a sufficient amount.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information






Vendor Master (General Section)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 4650 Date: 20240523 Time: 052616     sap01-206 ( 90 ms )