Chap 23 PSM

PSM Public Sector Management
SAP R/3 Enterprise

Release 470x200
Release Notes
Copyright 2003 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of
Microsoft Corporation.
IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390, AS/400, OS/390, and
OS/400 are registered trademarks of IBM Corporation.
ORACLE is a registered trademark of ORACLE Corporation.
INFORMIX-OnLine for SAP and Informix Dynamic Server
Incorporated.
TM
are registered trademarks of Informix Software
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other
Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.
JAVA is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI,
SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG
in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered
trademarks of their respective companies.
Design: SAP Communications Media
SAP
System
Table of Contents
SAP AG
______________________________________________________________
23
23.1
23.2
23.2.1
23.2.2
23.2.3
23.2.4
23.2.5
23.2.5.1
23.2.5.2
23.2.5.3
23.2.5.4
23.2.5.5
23.2.5.6
23.2.6
23.2.6.1
23.2.6.2
23.2.6.3
23.2.6.3.1
23.2.6.3.2
23.2.6.3.3
23.2.6.4
23.2.6.4.1
23.2.6.5
23.2.6.5.1
23.2.7
23.2.7.1
23.2.7.2
23.2.7.3
23.2.7.3.1
23.2.7.3.2
23.2.7.3.3
23.2.7.3.4
23.2.7.3.5
23.2.7.3.6
23.2.7.3.7
23.2.7.3.8
23.2.7.3.9
23.2.7.3.10
23.2.7.3.11
PSM Public Sector Management

Assigning Controlling Areas to FM Areas (deleted)
PSM-FM Funds Management
Multi-Year Budget (new)
Federal Government: Classification of Cust
(New)
General budgetary ledger (new)
Changes to IMG Structures in Funds Managements
PSM-FM-MD Master Data
New BAdIs for FM Master Data
Automatic Generation of Cover Pools (enhanced)
Additional Checks when Saving the Budget Structure (new)
Revenue Account Assignments as Posting Objects (new)
Subdivision Enhancement (changed)
Reorganization of Funds Centers and Commitment Items (new)
PSM-FM-BU Budgeting and Availability Control
Additional Checks when Saving the Budget Structure (new)
Revenue Account Assignments as Posting Objects (new)
PSM-FM-BU-BF Basic Functions of Budgeting
Budget entry and distribution (enhanced)
Reassignment when Copying Budget Versions (new)
Reconstruct Budget According to Budget Type (new)
PSM-FM-BU-RB Revenues Increasing the Budget
Text Variables in Long Texts of Budget Memos (new)
PSM-FM-BU-CE Unilateral and Rec
Eligibility
Text Variables in Long Texts of Budget Memos (new)
PSM-FM-BCS Budget Control System
Budget Control System
Key figures for BCS (changed)
PSM-FM-BCS-BU Budgeting
Define budget types for consumption in BCS (new)
Budgeting functionality in BCS (new)
Delete budget data (new)
Editing options for BCS data (new)
BCS field status functionality (new)
Grouping key for FM account assignments (new)
Migration functionality in BCS (new)
Enhance account reassignment rules in BCS (new)
Budget release functionality in BCS (new)
Revenues Increasing the Budget (new)
Budget text functionality in BCS (new)
1
1
1
1
2
2
3
5
5
6
7
7
7
8
9
9
9
9
10
10
10
11
11
11
11
11
11
13
15
15
16
18
19
19
20
20
21
22
22
23
______________________________________________________________
SAP AG
iii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
23.2.7.4
23.2.7.4.1
23.2.8
23.2.8.1
23.2.8.2
23.2.8.2.1
23.2.8.2.2
23.2.9
23.2.9.1
23.2.9.2
23.2.9.3
23.2.9.4
23.2.9.5
23.2.9.6
23.2.9.7
23.2.9.8
23.2.9.9
23.2.9.10
23.2.10
23.2.10.1
23.2.10.2
23.2.10.3
23.2.10.4
23.2.10.5
23.2.11
23.2.11.1
23.2.11.2
23.2.12
23.2.12.1
23.2.12.2
23.2.12.3
23.2.12.4
23.2.12.5
23.2.12.6
23.2.12.7
23.2.12.8
23.2.12.9
PSM-FM-BCS-AC Availability Control

Availability control functionality in BCS (changed)
PSM-FM-PO Funds Management-Specific Postings
Payment Directives for FM Payment Requests
PSM-FM-PO-RE Request
Business Add-Ins (BAdIs) for Requests (new)
Request Functions (changed)
PSM-FM-UP Actual Update and Commitment Update
Business Add-In for Defining Expiry Month (new)
New Budgetary Ledger for USA Federal Government (New)
Consignment Process in Funds Management (New)
Changes to the Funds Management (FM) Deriv
(changed)
Future-Dated Purchase Requisition/Purchase Order (NEW)
Changes to Update for Parked Invoices (Changed)
Validity Dates for Application of Funds an
in FM
Update Purchase Requisitions Generated fro
Accounting (New)
Reassignment (new)
Different Local Currency for Company Code and FM Area (new)
PSM-FM-CL Closing Operations
Commitment Carryforward (enhanced)
Commitment Carryforward for Expiry Period (new)
Balance Carryforward (enhanced)
Close-Out of Unfilled Customer Orders (New)
Reassignment in Year-End Operations (changed)
PSM-FM-IS Information system
Line Item Reports Using the Document Journal (changed)
PSM-FM-DE Special Function P
Germany
Functions for Public-Owned Commercial Operations (Enhanced)
Copying Year-Dependent PCO Account Assignments (enhanced)
Assigning Commitment Items to Revenue Types (New)

Grouping and Structural Changes (changed)
Comparison of Key Figures (new)
24
24
25
26
26
26
27
28
28
28
29
29
30
31
31
32
32
34
34
34
35
35
36
36
37
37
38
38
38
39
39
39
39
39
40
40
40
______________________________________________________________
SAP AG
iv
SAP
System
Table of Contents
SAP AG
______________________________________________________________
23.2.12.10
23.2.12.11
23.2.12.12
23.2.12.13
23.2.12.14
23.2.12.15
23.2.12.16
23.3
23.3.1
23.3.2
23.3.2.1
23.3.2.2
23.3.2.3
23.3.2.4
23.3.2.5
23.3.2.6
23.3.3
23.3.3.1
23.3.3.2
23.3.3.3
23.3.3.4
23.3.3.5
23.3.3.6
23.4
23.4.1
23.4.2
23.4.3
23.4.4
23.4.5
23.4.6
23.4.7
23.4.8
23.4.9
23.4.10
41
41
Cross-Company Code Evaluation for Public-O
Operations
Reorganization of Funds Centers and Commitment Items (new)
Summary Carrryforward of down payments and
clearings (new
PSM-GM Grants Management
Changes to Grants Management Implementation Guide (changed)
PSM-GM-MD Master Data
Changes to the Grants Management (GM) Deri
(Changed)
Master Data Relationships in Grants Management (New)
Report Tracking and Monitoring Function in
(New)
Changes to Sponsored Programs and Sponsore
(changed)
Position Control Adjustments in Time Slices (Changed)
Grants Management Workflow (New)
PSM-GM-BU Budgeting and Availability Control
Flexible Layout of GM Budgeting Dimensions (New)
Budgeting GM-FM Integration (New)
BAPIs for Budgeting in Grants Management (New)
BAPIs for Grant Master Data in Grants Management (New)
New AVC and Checking Functionality in Gran
(New)
Grants Management Workflow (New)
PSM-FG Functions for US Federal Government
US Federal Agencies' Centralized Trial Bal
(Changed)
US Federal Agencies' Centralized Trial Bal
(Changed)
Automatic Budget Postings (New)
Changes to the Federal Government IMG (Changed)
Intragovernmental Payments and Collections (New)
Changes to Federal Government Menu (new and changed)
Federal Government Reconciliation Tool (New)
SF-224 Statement of Transactions (Changed)
Federal Government: Treasury Offset (New)
US Federal Government: Financial Statements (New)
41
42
42
42
42
42
42
44
44
44
45
45
46
46
48
48
49
50
50
51
52
53
53
54
56
57
59
59
61
61
62
62
______________________________________________________________
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
23.4.11
23.4.11.1
23.4.11.2
23.4.11.3
23.4.11.4
23.4.11.5
23.4.11.6
23.5
23.5.1
PSM-FG-PP US Prompt Payment Act

US Federal Government: Automatic Invoice R
Receipt (New
Federal Government: Accounts Receivable Classification (New)
Federal Government: Economic Justification (New)
Federal Government: Exclude Invoice (New)
Federal Government: Improper Invoices (Changed)
Federal Government: Interest Penalty Reason Code (New)
PSM-FA Fund Accounting
Fund Accounting: Fund Message Derivation Tool (New)
63
63
64
64
66
66
67
67
67
______________________________________________________________
SAP AG
vi
SAP System
______________________________________________________________
23 PSM
Public Sector Management
23.1 Assigning Controlling Areas to FM Areas (deleted)

Use
From SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), it is no longer necessary to directly
assign controlling areas to FM areas. The IMG activity Controlling Area - Assign FM Area was
therefore deleted from the IMG of the enterprise structure.
The FM area is now determined using the company codes assigned to the controlling area - which is
assigned to the FM area. The company code is determined from the CO objects.
Using this procedure, a company code relevant to controlling can be excluded from integration in Funds
Management.
The prerequisite for this procedure if that the account assignment elements fund, functional area or grant
are not activated in the IMG activity "Activate Account Assignment Elements".
The following are examples of the possible combinations:
o
A controlling area that is integrated in Funds Management by the assignment of FM area to

company code can be assigned to another company code that is not assigned to a FM area.
Three company codes are assigned to the controlling area. Two of the company codes are assigned
to different FM areas and one company code is not assigned to a FM area.
In this combination, only the plan data for CO objects that belong to the company code assigned to
this FM area are copied during plan data transfer in an assigned FM area.
If one of the account assignment elements is not activated, the assignment of controlling area to FM area
must be unique, as before. All company codes assigned to the controlling area must either be assigned to
the same FM area or this company code is not assigned to a FM area.
The assignment of controlling area to FM area must be unique even if you use the component Position
Budgeting and Control (PA-PM-PB).
See also
You can find more information on integration with Position Budgeting and Control in SAP note
638183.
23.2 PSM-FM
Funds Management
23.2.1 Multi-Year Budget (new)

Use
Starting from SAP R/3 Enterprise Public Services 2.00 (EA-PS 200) you can use a year-dependent
budget for Funds Management. This enables you to manage one of the budgets independent of a fiscal
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
year.
The activities of the fiscal year change (budget carryforward, actual/commitment carryforward and so on)
are no longer required by a multi-year budget. The budget once entered can be managed as a multi-year
budget.
The FM account assignment element 'fund' is obligatory for the multi- year budget. The FM account
assignments valid for a budget can be defined using a Budget ID in the key.
Effects on Existing Data
To be able to use this function, you must be using year-independent master data.
For more information on migration and steps that are prerequisite for the activation of this scenario, see
note 640452.
Effects on Customizing
You activate this function in the Customizing of Funds Management, under Activate Multi-Year Budget.
See also
For more information, see the implementation guide under Activate Multi-Year Budget.
23.2.2 Federal Government: Classification of Customer Invoices (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, the Federal Government solution includes a new function
that enables government agencies to classify customer invoices.
In addition to the standard Prompt Payment Act (PPA) customizing, you must also Maintain Improper
Invoice Reason Codes.
See also
The PPA feature must be installed, configured, and active before you can use the improper invoices
function. For details of the configuration work, see the PPA IMG documentation.
23.2.3 General budgetary ledger (new)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can use the budgetary ledger to post
budget-relevant processes to SAP Finanacial Accounting (FI) by generating separate FI-GL document
lines. Normally the process starts with budgeting and ends with payments. You can post budget data from
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
any budget and commitment/actual posting process to SAP Financial Accounting. This data is recorded in
the General budgetary ledger (BL).
Since for budgeting processes the general budgetary ledger only works together with the Budget Control
System (BCS), you must have installed it in order to create and display budget lines generated by BCS
budget postings in Financial Accounting. In the Budgeting Workbench, for example, the menu path
Environment -> Related Documents enables you to directly access the FI documents generated
through the budgetary ledger.
Using the Derivation Tool, you can set up your own rules to derive the budgetary ledger accounts from
the respective account assignment information.
There are two new nodes in Customizing, with implementation activities grouped into basic settings and
settings for the general budgetary ledger. The basic settings are as follows:
o
Initially, you have to select a budgetary ledger variant in the Customizing activity Activate Variant
for Budgetary Ledger. The following Customizing settings that you make are then based on this
selection.
Next you need to reserve a range of GL accounts for budgetary ledger postings and to assign it to
the postings resulting from budgeted amounts, commitments/actuals or both, in the Customizing
activity Classify BL Accounts.
You then specify the posting keys to be used with the budgetary ledger in the Customizing activity
Define Posting Keys for Budgetary Ledger.
The settings for the general budgetary ledger comprise the following Customizing activities:
o
In order to have BL postings for selected budget categories and value types, you need to Select
Budget Categories and Value Types for BL Update. Here, you also specify whether the GL Offset
Account is required for budgeting.
You select the source fields to be used in the Derivation Tool in the Customizing activity Select
Source Fields for Account Derivation.
Furthermore, you have to set up derivation rules and values for the GL account derivation using the
Derivation Tool in the Customizing activity Define Derivation Strategy for BL Accounts.
If you need to include additional fields for updating the FI Special Ledger (FI-SL), you can select
them in the Customizing activity Select Fields for FI-SL Update.
23.2.4 Changes to IMG Structures in Funds Managements

Use
The structure of the implementation guide (IMG) of Funds Management was changed for SAP R/3
Enterprise Public Services 2.00 (EA-PS 200).
Deleted IMG Activities
o
Define Carryforward Parameters
Assign Carryforward Parameter for Commitment Carryforward
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
Copy Account Assignment Assignment (PCO: Function now in the menu)
New IMG Activities Added

Master Data
Under the node Budget Structure (Former Budgeting)
o
BAdI: Define Checks for Budget Structure Plan
Under the node Subdivision of Master Data

o
BAdI: Check Subdivision ID
BAdI: Check Substrings
Under the new structure node Account Assignment Strategy for Reassignment
o
Define Derivation Strategy for Reassignment
BAdI: Enhanced Functions for Derivation Strategy
Budget Control System (BCS)

You can find more information on the changes to the IMG structures of BCS in the release information
New Functions in the Budget Control System (new).
Budgeting and Availability Control (Former Budgeting)
o
Define Revenue Commitment Items as Posting Objects
BAdI: Edit Text Variables in Budget Memos
Requests
o
Change GUI Status of Requests
BAdI: Enhance Derivation of G/L Account
Cash Desk
Under the new structure node Clarification Worklist
o
Define Processing Status
Public-Owned Commercial Operations

o
BAdI: Derive CO Account Assignment for Correction Documents
Integration
o
BAdI: Definition of Expiry Month
BAdI: Update Debits/Actual
Closing Operations
o
Define Basic Settings for Commitment Carryforward
BAdI: Control of Reassignment
Information System
o
BAdI: Enhance Document Journal
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
BAdI: Activate Authorizations for FI Accounts
Under the new structure node Definition of Reports (Info System German Government)
o
Compare Key Figures
Unnamed IMG Activities

o
Assign FM Area Strategy for the Reassignment of Commitment Items in Assign

Reassignment Strategy to FM Area
Restructured IMG Activities

o
The IMG activities Define Subdivision ID and Define Substrings for each FM Account
Assignment were grouped together in the IMG activity Create and Define Subdivision ID.
You can now find the unnamed IMG Assign Reassignment Strategy to FM Area under Master
Data -> Account Assignment Derivation for Reassignment -> Assign Reassignment
Strategy to FM Area.
23.2.5 PSM-FM-MD
Master Data
23.2.5.1 New BAdIs for FM Master Data

1) FM_MD_SUBID_TYPE
Check Subdivision ID entered in table FMMDSTRID
This BAdI contains one method:

o
CHECK_SUBID_TYPE
By means of this BAdI and your implementation, you can run your own checks on parameters used
during the creation of the subdivision ID. The parameters you can check in BAdIs are the following:
o
Account assignment element
Master data subdivision ID
There is one example of the implementation of this BAdI. During the creation of the subdivision ID, the
system checks whether the subdivision ID, which can be used only for the commitment item, has the
letter #G#, or #E# or #I# at the 7th position.
2) FM_MD_SUB_VALUES
BAdI for initial substring value checking
This BAdI contains thirteen methods:

o
CHECK_VALUES_CISUB1, 2, 3, 4, 5
CHECK_VALUES_FCSUB1, 2, 3
CHECK_VALUES_FDSUB1, 2
CHECK_VALUES_FNSUB1, 2, 3
during the creation of substrings. The parameters you can check in BAdIs are the following:
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
Master data subdivision ID
Master data substring value
Master data substring length
There are two examples of implementation of this BAdI:

1.
During the creation of each substring, the first one checks whether the values entered contain only
characters (except the last one, this must be a numerical entry).
2.
The second example, in contrast, checks that the number is at the first position.
If the check results in an error, an error message is displayed.

This BAdI is also called when you enter substrings during master data creation.
Authorization Checks
The authorization check controls the user authorizations necessary to maintain the views.
Authorization checks are performed every time there is an updating operation on the IMG tables for the
substring value maintenance. Authorization checks are also performed every time you copy or add entries
to the tables in the standard menu during master data creation.
3) FM_MD_SUBSTRINGS
BAdI for subdivision parameters used at master data creation
This BAdI contains four methods:

o
FIPOS_CHECK_SUBSTRINGS
FISTL_CHECK_SUBSTRINGS
FUND_CHECK_SUBSTRINGS
FUNCTION_CHECK_SUBSTRINGS
during the creation of master data using substrings. Depending on the methods involved, there will be
different parameters to check. Please click on the following links:
o
Documentation on BAdI method for commitment item
Documentation on BAdI method for funds center
Documentation on BAdI method for fund
Documentation on BAdI method for functional area
23.2.5.2 Automatic Generation of Cover Pools (enhanced)

Use
From SAP R/3 Enterprise Public Services 2.00 (EA-PS 200) you can define that individual FM
Account Assignments are not taken into account in the generation of cover pools and are therefore not
reciprocally eligible for Cover. You define this in the rule maintenance for the automatic generation of
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
Cover Pools.
See also
You can find more information on the generation of cover pools in the SAP Library under Accounting ->
Public Sector Management -> Funds Management -> Master Data -> Automatic Generation of
Cover Pools.
23.2.5.3 Additional Checks when Saving the Budget Structure (new)

Use
Starting from Release SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can use Business
Add-In (BAdI) FMBS_CHECK_STRUCTURE to carry out extra checks when processing the budget
structure. These additional, customer-defined checks are part of the consistency checks for the budget
structure.
This function is only relevant if you are using former budgeting.
You can implement the BAdI in IMG activity Define Checks for Budget Structure .
See also
For more information, see the BAdI documentation.
23.2.5.4 Revenue Account Assignments as Posting Objects (new)

Use
If you are working in former budgeting with a budget structure, actual and commitment postings are
allowed on all revenue account assignments by default.
If you want to change this posting logic, you can define revenue account assignments explicitly as
posting objects in the budget structure as of Release SAP R/3 Enterprise Public Services 2.00 (EA-PS
200). This enables you to exclude certain revenue account assignments from being posted.
If you do not use this function, all revenue account assignments can be posted.
You can use program BPCARRM01 to transfer the affected settings of the revenue account assignments
in old budget structure definitions.
You define the setting in IMG activity Define Revenue Account Assignment as Posting Object.
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
23.2.5.5 Subdivision Enhancement (changed)

Use
In SAP R/3 Enterprise Public Services Rel. 2.00 the functionality for the subdivision of master data has
been enhanced. Using master data substrings, you can save detailed and user-defined master data
information in your system for the subdivision of master data defined in Customizing. This provides a
simpler way of customizing the subdivision of Funds Management master data than previously.
The transactions for entering values in the substrings defined in Customizing are in the Funds
Management menu under Master Data -> Tools -> Subdivision, then the master data you choose.
Add Substrings to Maintenance Tables during Master Data Creation
Once you have activated the subdivision functionality, you can create master data by concatenating the
substrings you create. This means that you can enter new substrings in the corresponding tables when you
create master data.
The program automatically checks whether the substring entered into the dialog box for the creation of
the concatenated master data exists in the corresponding table. If not, a popup displays, asking if you
want to store it in the table. If you agree, another dialog box displays in which you can add a description
for the substring value to be stored in the corresponding table.
Copy Substring Values
If you want to copy substring values belonging to a certain subdivision ID to a different subdivision ID,
you can use the copy program. This program and its documentation are available in the Funds
Management menu under Master Data -> Tools -> Subdivision and from here to the master data you
choose.
You use the Business Add-In in the IMG activity Check Subdivision Parameters at Master Data Creation
to activate and implement your own substring check when creating master data.
Create and Define Subdivision ID
The new view cluster Create and Define Subdivision ID provides a simpler way of customizing the
subdivision of Funds Management master data than previously. There are standard checks which provide
controls on the subdivision ID name and on the substring lengths and positions. Furthermore, you can
customize your specific checks on the subdivision ID and substring values implementing your own code
in the BAdIs Check Subdivision ID and Check Substring Values.
23.2.5.6 Reorganization of Funds Centers and Commitment Items (new)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can reorganize master data within
a current fiscal year. Up until now, this was not possible once a budget allocation or budget entry had
taken place.
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
Now it is possible to reorganize commitment items/funds centers under certain conditions.

You can find an exact description of the reorganization of master data in the note 553664.
If you belong to the client group German Government, read the separate release information
Reorganization of Funds Centers and Commitment Items (new).
23.2.6 PSM-FM-BU
Budgeting and Availability Control
23.2.6.1 Additional Checks when Saving the Budget Structure (new)

Use
Starting from Release SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can use Business
Add-In (BAdI) FMBS_CHECK_STRUCTURE to carry out extra checks when processing the budget
structure. These additional, customer-defined checks are part of the consistency checks for the budget
structure.
This function is only relevant if you are using former budgeting.
You can implement the BAdI in IMG activity Define Checks for Budget Structure .
See also
For more information, see the BAdI documentation.
23.2.6.2 Revenue Account Assignments as Posting Objects (new)

Use
If you are working in former budgeting with a budget structure, actual and commitment postings are
allowed on all revenue account assignments by default.
If you want to change this posting logic, you can define revenue account assignments explicitly as
posting objects in the budget structure as of Release SAP R/3 Enterprise Public Services 2.00 (EA-PS
200). This enables you to exclude certain revenue account assignments from being posted.
If you do not use this function, all revenue account assignments can be posted.
You can use program BPCARRM01 to transfer the affected settings of the revenue account assignments
in old budget structure definitions.
You define the setting in IMG activity Define Revenue Account Assignment as Posting Object.
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
23.2.6.3 PSM-FM-BU-BF
Basic Functions of Budgeting
23.2.6.3.1 Budget entry and distribution (enhanced)

Use
Starting from SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can use enhancement
Budget Entry and Distribution (SAPLKBPB) to check that parked documents meet your requirements.
Function module Validating Entry Document Lines (EXIT_SAPLKBPB_001) is now also called when
parked documents are created and undone.
23.2.6.3.2 Reassignment when Copying Budget Versions (new)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can take assignment changes into
account that are necessary due to changes in the areas of responsibility (for example) or the functional
assignment when copying budget versions by using program Copy Budget Version (BPCAOPY00)
In order to make reassignments when copying budget versions, you must create a derivation strategy for
the reassignment that contains the assignments from the old to the new account assignments. To do this,
execute IMG activity Define Derivation Strategy for Reassignment in the IMG ofFunds Management
Government.
You must also assign this derivation strategy to your FM area and fiscal year. To do this, execute IMG
activity Assign Derivation Strategy for Reassignment to FM Area in the IMG of Funds Management
Government.
See also
Release information Reassignments with Year-End Operations.
23.2.6.3.3 Reconstruct Budget According to Budget Type (new)

Use
Starting from Release SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can use program
Reconstruct Budget According to Budget Type (BPDIST07) to reconstruct budget in accordance with
budget types and budget subtypes. This program can be used instead of program Reconstruct Budget
(BPDIST05).
You use this program if FM account assignments already budgeted (funds centers or commitment items)
were changed in the hierarchy. After such hierarchy changes the hierarchical budget data is no longer
correct. Start this program in order to make the data consistent again. It reconstructs the data. The
differences calculated by this program are not totaled across all budget types and subtypes and written in
______________________________________________________________
SAP AG
10
SAP System
______________________________________________________________
the original budget (as is the case with BPDIST05) but are determined and updated individually for each
budget type and budget subtype.
See also
For more information on the functions of the program, see the Program documentation.
23.2.6.4 PSM-FM-BU-RB
Revenues Increasing the Budget
23.2.6.4.1 Text Variables in Long Texts of Budget Memos (new)

Use
From SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can include text variables in the
long texts of budget memos. These text variables are evaluated in the budget plan print.
If you want to adapt the handling of text variables to your own requirements, you can use the Business
Add-In Edit Text Variables in Budge Memos (FMTX_HVM).
To activate and deactivate the BAdI, carry out the IMG activity
Edit Text Variables in Budget Memos in the implementation guide of Funds Management
Government.
23.2.6.5 PSM-FM-BU-CE
Unilateral and Reciprocal Cover Eligibility
23.2.6.5.1 Text Variables in Long Texts of Budget Memos (new)

Use
From SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can include text variables in the
long texts of budget memos. These text variables are evaluated in the budget plan print.
If you want to adapt the handling of text variables to your own requirements, you can use the Business
Add-In Edit Text Variables in Budge Memos (FMTX_HVM).
To activate and deactivate the BAdI, carry out the IMG activity
Edit Text Variables in Budget Memos in the implementation guide of Funds Management
Government.
______________________________________________________________
SAP AG
11
SAP System
______________________________________________________________
23.2.7 PSM-FM-BCS
Budget Control System
23.2.7.1 Budget Control System

Use
As of SAP R/3 Enterprise Public Services 1.10 (EA-PS 1.10), the new Budget Control System (BCS) is
available. For a better distinction, the existing budget execution application of FI-FM/IS-PS has been
renamed '"former budgeting'"
BCS is the new strategic system for budget execution, which SAP will enhance with later releases. Due to
the implemented architecture, BCS does not have any influence on the existing budget execution
application. For performance reasons and in order to avoid problems caused by handling errors, SAP does
not recommend using both budgeting systems in parallel.
BCS offers a large array of new features that provide you with a flexible, well-performing and highly
user-friendly budget execution system. The most important features you should consider are:
o
All master data account assignment elements of Funds Management

With the Enterprise release, the FM account assignment elements Grant and Funded Program
have been introduced into Funds Management. These account assignment elements are only
supported in BCS, not in the former budgeting. In addition, the master data Funds Center,
Commitment Item, Fund and Functional Area that already exist are still available.
In order to minimize data maintenance effort and restrict the budget structure to suit your needs, you
can choose the FM account assignment elements you want to use actively in BCS via Customizing.
Non-hierarchical data structure

BCS is based on a non-hierarchical data model. Contrary to the former budgeting tool, data for
distributed budgets are not stored. This ensures a very flexible handling of data entry.
Customizable budget types

The concept of user-defined budget types, already introduced in the former budgeting environment
with Release IS-PS 4.61 via subtypes, has been enhanced. BCS now requires the definition of
budget types and enables you to use them either as a subdivision of budget processes predefined by
SAP or to join and structure budget in a completely self-defined way across processes.
Customizable consistency checks

While SAP defines a basic level of budget consistency, you can add your own rules for budget
consistency. The system offers both document-based checks and checks which take data already
stored on the database into account.
Document principle
BCS applies the document principle to budgeting. You use document types to distinguish different
kinds of budget documents and control the numbering of them. In order to enter new budget
documents or view existing ones, you use the new budgeting workbench. It allows you to define
flexible layouts to suit the needs of different budgeting situations.
Status management
You can define the individual phases which make up your budget execution cycle and control the
allowed activities for each phase. Using an authorization concept, you can also define specific user
roles to have more powerful authorizations than other user groups.
Customizable Active Availability Control
______________________________________________________________
SAP AG
12
SAP System
______________________________________________________________
You use a derivation strategy to define where availability control should check the budget for each
posting you make. The system supports the definition of easy and complex rules and allows multiple
and parallel checks.
o
Integration with Budget Preparation

BCS provides you with a retractor function from the budget preparation environment in SAP
Strategic Enterprise Management to fully support all budget-related activities. You can also use an
integrated planning tool for basic planning requirements in BCS.
Reporting using Business Warehouse

BCS uses Business Warehouse as its primary reporting tool. Some basic reports are available in the
transactional system in order to quickly verify a situation and check the availability of budget.

Existing budget/availability data established with the former budgeting tool (irrespective of the release in
which it was created) is not affected in any way by BCS. Completely new tables are used to store all BCS
information. SAP is planning to provide migration tools for budget data from the existing budgeting tool
(not in EA-PS 1.10).
Effects on Data Transfer
As all data structures and many concepts are different, you need to completely redesign any data transfer
programs that you might use. With this release, programs are available for BCS that support the
generation of budget entry documents and thereby the transfer of data into BCS.
Effects on System Administration
BCS uses new authorization objects. In order to grant controlled access to the functions of BCS, you need
to maintain these authorization objects.
Availability control provides the option to use customer-defined ledgers for additional checking
requirements. These ledgers reside in the standard SAP tables, therefore no special attention is required.
Customizing for budgeting offers two separate structures for the existing former budgeting and BCS.
Using the two different kind of application components of BCS or former budgeting you can generate
individual customizing projects including the relevant customizing settings for each component. In order
to use BCS, no Customizing setting of the existing budgeting is needed or used.
For more information, see IMG documentation on BCS under Public Sector Management -> Funds
Management Government:
o
Basic Settings -> Activate Global Functions for Budget Control System (BCS)
Master Data -> Budget Structure for Budget Control System (BCS)
Budget Control System (BCS)
Closing Operations -> Closing Operations Budget Control System (BCS)
See also
For more information, see SAP library for Funds Management under Budget Control System (BCS).
______________________________________________________________
SAP AG
13
SAP System
______________________________________________________________
23.2.7.2 Key figures for BCS (changed)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), when you select attributes that you define
for a data field for key figures in BCS, the new meta-value "&" is supported in conjunction with the fields
"Budget Type" and "Fiscal Year".
BCS offers the maintenance of key figures, which are used to check the consistency of budgets or to carry
forward residual budgets at the end of the year. Key figures are linked to the budgeting workbench
(BWB).
Depending on the fund in question, some budget types are considered as "consumable" and others as not
"available for consumption". This means that when you choose the meta-value "&", the key figure will
only evaluate the amount of all consumable budget types for the fund currently being processed. Other
budget values which are assigned with non-consumable budget types are not totaled up.
As an example, SAP delivers two new key figures for consumable budget and for budget which is not
available for consumption, YE_RESIDU_CONS (residual consumable budget for fiscal year change) and
YE_RESIDU_NCONS (residual non-consumable budget for fiscal year change).
For data source "Budgeting Data" and "Posting Data" :
Depending on the fund in question, some budgets are based on annual values and others on overall
values. This is defined in the Customizing activity Activate Multi-Year Budget, as well as in the
Customizing activity for defining fund types.
o
If the fund you are processing is defined as annual, the input value for the fiscal year is adopted as a
value. In this case, the meta-value "&" is dynamically replaced by "#" .
If the fund you are processing is defined as overall, all existing values for the fiscal year are totaled
up. In this case, the meta-value "&" is dynamically replaced by "*".
As an example, SAP delivers three new key figures for the multi-year budget scenario:
o
MY_RESIDUAL (multi-year budget residual )
MY_RESIDU_CONS (residual multi-year consumable budget)
MY_RESIDU_NCONS (residual multi-year non-consumable budget)
For data source "AVC Data" :

Depending on the Checking Horizon for Availability Control, the meta-value "&" for the fiscal year will
be replaced as follows :
o
If the checking horizon is defined as " ", the same rule applies as for the data sources "Budgeting
Data" or "Posting Data", see details above.
If the checking horizon is defined as "A", the input value for the fiscal year is adopted as a value.
The meta-value "&" is dynamically replaced by "#" .
If the checking horizon is defined as "O", all existing values for the fiscal year are totaled up. In
this case, the meta-value "&" is dynamically replaced by "*".
As an example, SAP delivers two new key figures for the multi-year budget scenario:
______________________________________________________________
SAP AG
14
SAP System
______________________________________________________________
MY_AVAILABLE (Multi-year available budget amount)
MY_CONSUMABLE (Multi-year consumable budget, payment budget)
Maintain the IMG activity Define Key Figures.
See also
Please find further information under the IMG activities Define Budget Type for Consumed Amount for
Each Fund Type and Define Budget Type for Consumed Amount for Each Fund, and Activate
Multi-Year Budget.
23.2.7.3 PSM-FM-BCS-BU
Budgeting
23.2.7.3.1 Define budget types for consumption in BCS (new)

Use
As of R/3 Enterprise Release 2.0, you can define multiple budget types for consumption. Previously, only
one budget type was permitted. To each budget type, you can allocate the corresponding budgeting
processes.
Budget Types
You can use the budget type group to bundle multiple budget types for consumption, for example in this
way you can define budget types for consumption per fund for a specific fiscal year. If no settings are
found on the fund level, the settings on the fund type level apply.
The budget types defined for consumption are updated in availability control and can therefore be
consumed by actuals or commitment postings. By default, all budget types are defined as being for
consumption and therefore are considered during availability control.
The definition of budget types for consumption is considered in the calculation of the residual budget. In
BCS, you can do the following:
o
You can transfer residual budget using transaction FMMPTRAN Transfer Budget Data
You can carry over residual budget using transaction FMMPCOVR Carry Over Residual Budget
Key Figures
In the above transactions, the calculation of the residual budget is done according to the key figure you
have defined. In order to include budget types for consumption in the residual budget calculation per
fund, you must enter the meta-value "&" in the budget type term of your key figure definition. You define
key figures based on budget types for consumption (that is, you should enter the meta-value "&"). The
key figure should only be valid for the key figure categories transfer and carryover.
When you define key figures, you can include budget types for consumption. For this, please see the
documentation of the Customizing activity Define Key Figures.
______________________________________________________________
SAP AG
15
SAP System
______________________________________________________________
You can bundle several budget types in a budget type group in the Customizing activity Define Budget
Type Group.
In order to maintain budget types for consumption per fund type or fund, maintain the following settings:
o
Define Budget Type for Consumed Amount for Each Fund Type
Define Budget Type for Consumed Amount for Each Fund
The settings defined in this Customizing activity will only be included in availability control if the budget
types are correctly defined. In the view "Define Budget Values as Consumed Amounts" of the
Customizing activity Define Filter Settings for Budget Values, you must select the value type "Budget or
budget/release according to fund-dependent settings" for this.
See also
Release note Availability control functionality in BCS.
23.2.7.3.2 Budgeting functionality in BCS (new)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), the following new functions are available
in the Budget Control System. Please access the individual release notes for them:
Migration from Former Budgeting to Budget Control System
Budget Release Functionality
Revenues Increasing the Budget
Field Status Functionality
Budget Texts for FM Account Assignment Elements
Grouping Key for FM Account Assignments for multi-year budgeting
Deletion of Budget Data
Individual new functions in BCS also include the following subjects, not described in individual release
notes.
Restructuring of IMG for BCS Budgeting
The area of BCS Budgeting in the Funds Management IMG has been restructured, as many new activities
have been added since the last release and subnodes were inserted to more clearly structure the activities.
FI-SL Report Writer for Budget Control System
The Report Writer has been added to the Public Sector Management information system for reporting on
the Budget Control System (BCS), for which no Customizing is necessary. There is a set of standard
reports (Budget Report, Budget Version Comparison, Budget Consumption), which you must import into
your client using the Report Writer copy program. Furthermore, there is a new Business Add-In that you
can use to get field value texts for the Report Writer, called Enhance Report Writer implementation.
______________________________________________________________
SAP AG
16
SAP System
______________________________________________________________
To define additional reports, use the standard Report Painter functionality for ad-hoc reporting in
Financial Accounting.
Two new transactions have been added which will generate so-called "set hierarchies" from the master
data hierarchies for funds centers and commitment items.
Transfer of CO Planning Data to BCS

With transaction Transfer of CO Planning Data to BCS, you can transfer the planning data you created in
Controlling for the cost objects cost center, internal order, WBS element and CO business process to the
corresponding account assignment objects contained in BCS. The data transfer creates budget documents
in BCS.
All primary and secondary CO planning data is processed. The program determines the receiver in FM
according to FM account assignment derivation rules in the FM Derivation Tool. For further information,
see Transfer of CO Planning Data to BCS and the documentation provided there.
Archiving of BCS Database Tables

The archiving of budget data in BCS enables you to get rid of large sets of data in your database by
copying this data to an archiving system and then deleting the entries in your database.
The following database tables can be archived using Transaction SARA:
o
FMBH and FMBL: database tables used to create budget entry documents in BCS
FMBDP: database table containing changed line items (history of changes made during the budget
entry process)
FMBDT: database table summarizing the total values posted per FM account assignment
To archive Use program
Entry documents RFFMEDWR
Line items RFFMLIWR
Budget totals
RFFMTTWR
with arch. objects

FM_ED
FM_LI
FM_TT
to archive DB tables
FMBH and FMBL
FMBDP
FMBDT
Group Selection
For BCS transactions involving the mass maintenance of budget data, such as carryover, budget transfers,
etc., you can use master data groups for selecting multiple FM account assignment elements. In BCS, a
master data group bundles together several master data records of the same type (fund group, fund center
group, etc.) and simplifies processing if you are working with several funds, for instance.
Grouping options are displayed in a separate selection popup contained in BCS transactions involving
master data.
Business Application Processing Interfaces (BAPIs) in BCS
For Transaction BAPI, BAPI scenarios have been developed in the areas of entry documents and totals
______________________________________________________________
SAP AG
17
SAP System
______________________________________________________________
data as of BCS Rel. 1.1. With these BAPIs, you can create an FM entry document, get detailed
information on an entry document, get a list of entry documents, or reverse an entry document. There is a
BAPI to import the results of the budget preparation phase to R/3 Enterprise, since budget preparation
work is often done in another system. Finally, there is a mass process BAPI for reading budget data,
which you can use, for example, to initialize data for budget preparation with the budget data of the
previous year.
Reassignments Using the Derivation Strategy
In order to handle organizational changes, you may need to reassign your FM account assignments for
specific commitment items. R/3 Enterprise contains a Customizing activity enabling you to carry this out
in Assign Derivation Strategy for Reassignment to FM Area.
Some BCS copy processes are linked to a fiscal year end process.
Please note that the derivation strategy only works when copying from one fiscal year to the next.
The derivation strategy is integrated with the following mass transactions:
o
Generate Planning Data

-
Generate Budget Data

-
This procedure is linked to the fiscal year end process "Copy Budget/ Budget Version".
Transfer Budget Data

-
This procedure is linked to the fiscal year end process "Copy Budget / Budget Version".
This procedure is linked to the fiscal year end process "Budget Transfer".
Carry Over Residual Budget

-
This procedure is linked to the fiscal year end process "Budget Carryover".
You can carry out the reassignment of FM account assigment elements via a derivation strategy in the
Customizing activity Assign Derivation Strategy for Reassignment to FM Area.
You can enhance reassignment rules in the Customizing activity Enhance Reassignment Rules.
See also
Release Notes Enhance Reassignment Rules, Funds Management Derivation Tool and Account
Reassignment for Fiscal Year Change.
23.2.7.3.3 Delete budget data (new)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can delete entries from the following
database tables:
o
FMBH/FMBL: database tables used to create budget entry documents in BCS
FMBDP: database table containing changed line items (history of changes made during the budget
______________________________________________________________
SAP AG
18
SAP System
______________________________________________________________
entry process)
o
FMBDT: database table summarizing the total values posted per FM account assignment
Only use this functionality in an early phase when you are preparing the budget. The deletion program is
not intended to be used as an archiving tool. For the archiving of budget data, use the general SAP
archiving tool (transaction SARA).
One common scenario is the following: after creating the preparatory budget, you copy this budget to the
operative version, and then delete the draft or preparatory data created in the database.
Carry out the Customizing activity Delete Budget Data.
See also
Delete database tables used by BCS.
23.2.7.3.4 Editing options for BCS data (new)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can specify the following editing
options for budgeting data:
o
the sign (+/-) to be used for your budget values, depending on the commitment item category you
are using
the number of decimals for manual budget entry

The sign (+/-) used to display and maintain values in the budgeting workbench is adjusted accordingly.
If you reduce the number of decimals, existing data will be rounded off when displayed.
Please note that these are only display and editing options. The values posted to the database remain the
same, irrespective of the settings made for the sign or number of decimals.
Make the necessary settings in the Customizing activity Define Editing Options for Budget Amounts.
23.2.7.3.5 BCS field status functionality (new)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), the field status function allows you to
control whether the fields your users see when they create budget entry documents are hidden, displayed,
optional or mandatory.
______________________________________________________________
SAP AG
19
SAP System
______________________________________________________________
Carry out the field status management Customizing activities in the following sequence:
Define Field Status Variant
Assign Field Status Variant
Define Field Status Group
Assign Field Status Group
Maintain Field Status Definition
Assign Field Status Definition.
23.2.7.3.6 Grouping key for FM account assignments (new)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), in BCS you can assign any individual FM
account assignment to a group of FM account assignments, which can be identified by a grouping key.
The grouping key can be used, for example, to define a budget ID, which enables a public organization to
manage all account assignment elements belonging to one budget, as approved by government,
independently of the fiscal year involved (multi-year budget execution).
For more information, see the IMG documentation of the Customizing activity Define Grouping Keys.
If you want to define your own checks for the grouping key, you can create an implementation in the
BAdI FMKU_BUDGET_EVNT. SAP delivers a default implementation called
FMKU_BUDGET_EVNT_GK.
Carry out the Customizing activity Define Grouping Keys.
See also
For more information, please see Default Implementation of Checks for Grouping Key and Activate
Multi-Year Budget.
23.2.7.3.7 Migration functionality in BCS (new)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), the migration functionality enables you to
copy the budget data of previous years (before BCS activation) from Former Budgeting to BCS. The
migration is done on a totals basis. There are the following possibilities:
o
You can migrate your annual funds. For this select fiscal years for the annual funds.
______________________________________________________________
SAP AG
20
SAP System
______________________________________________________________
You can also migrate your overall funds:

-
for all fiscal years before BCS starts, if annual values exist
for the overall amount if no annual values exist
The distinction between annual fund and overall fund depends on the level at which availability control is
defined in the budget profile.
Carry out migration activities in Migration of Former Budgeting to BCS.
In order to define derivation rules for assigning Former Budgeting fields to BCS fields, proceed as
follows:
1.
Check the predefined settings delivered by SAP in the Customizing activities:

-
Display Assignment Rules for Budgeting Process
Display Assignment Rules for Value Type
2.
Make the necessary settings in the Customizing activity Define Derivation Strategy for Migration.
3.
Carry out the migration of the data in the Customizing activity Migrate Budgeting Totals.
23.2.7.3.8 Enhance account reassignment rules in BCS (new)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can enhance the reassignment of FM
account assignment elements by defining your own rules using a Business Add-In called Enhance
Account Reassignment Rules.
This enables you to create your own derivation strategy for new FM account assignments, and split
budget amounts among different FM account assignment elements using a percentage or distribution key.
This is useful when you are doing multi-year budgeting and carry out your fiscal year change procedure.
Using this function, you can also change individual budget amounts.
The Business Add-In is integrated with the following mass transactions:
o
Generate Planning Data
Generate Budget Data
Transfer Budget Data
Carry Over Residual Budget
Transfer CO Planning Data to BCS.
Carry out the Customizing activity Enhance Account Reassignment Rules.
See also
______________________________________________________________
SAP AG
21
SAP System
______________________________________________________________
Release Note FM Account Reassignments for Fiscal Year Change.
23.2.7.3.9 Budget release functionality in BCS (new)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), the release function in BCS allows you to
control the availability of your budget for consumption using individual or mass budget releases. If the
release is activated, only released budget will be considered for availability control, at least for the
standard ledgers involved.
If you activate the release function after implementing BCS, you should specifically deactivate the
release for the previous years in which you work with budgets only and not with the release functionality.
Otherwise availability control will not take the correct values into consideration.
You can release your budget individually in the transaction FMBB budgeting workbench (BWB) or via a
mass process using transaction FMMPRELE Release Budget Data.
You can select release data as source data within mass processes (Freeze Budget Version, Generate
Planning Data, Generate Budget Data, Carry Over Residual Budget, Transfer Budget).
For existing data, you must adjust the Customizing entries of a previous R/3 release using the XPRA
report RFFMCU_VALTYPE_XPRA, Value Type Xpra. This report is executed in the background during
the upgrade.
If you are upgrading from a previous release, Customizing settings will be converted in the XPRA report
RFFMCU_VALTYPE_XPRA, after which you should verify in the log that it has run without errors.
In order to activate the release, make the necessary settings in the Customizing activity Define Release
Scenario.
In order to define specific release settings per fiscal year (e.g. deactivate the release, activate an automatic
release...), make the necessary entries for either Define Release Scenario for each Fund or Define Release
Scenario for each Fund Type.
After this, carry out the Customizing activities Define Budget Type for Release and Assign Budget Type
for Release to Processes.
See also
Release note Availability control functionality in BCS (changed).
23.2.7.3.10 Revenues Increasing the Budget (new)

Use
______________________________________________________________
SAP AG
22
SAP System
______________________________________________________________
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), the function of Revenues Increasing the
Budget (RIB) is available for the budget control system (BCS).
With this function, you can define rules for increasing the expenditure budget through revenue postings
such as customer invoices or expected revenues. Revenues increasing the budget are calculated on the
basis of updated total values and can be distributed to receiving expenditure account assignments (budget
addresses) according to specific calculation formulas. You can automatically generate such "RIB rules"
applying a new derivation strategy, or you can manually process the rules.
Rules for the budget increase (RIB rules) make use of the following:
o
RIB objects
A two-level hierarchy is provided to aggregate available revenues posted to a posting address:
posting address -> budget address (assignment defined in BCS budget structure) -> RIB object
(assignment defined in Customizing of BCS revenues increasing the budget).
Furthermore, on the level of the RIB object, you assign a rule for increasing the budget, in order to
specify the following: Which expenditure budget addresses receive budget? Which types of revenue
(invoices or payments, for example) increase the budget? And which calculation formula is applied
for determining the available budget amount for the increase?
Calculation formulas
Using calculation formulas, you define the share of revenues to be available for the increase, and
you can set lower and upper limits for the budget increase. Usually only the amount between the
lower and upper limit will be available for the budget increase, but you can also increase the
expenditure budget of a separate surplus budget address by specifying that revenues may exceed the
upper limit.
Activation status of a rule (or of a RIB object):

You cannot delete an existing rule for revenues increasing the budget, instead you must set it to
"inactive". Already posted budget increases may then be reversed. As an additional option, you can
choose the status frozen: in this case the budget increase posted with this rule will remain as
distributed - further revenue increases will not increase the budget of the receiving expenditure
budget addresses.
Carry out the following Customizing activities for Revenues Increasing the Budget:
Define Derivation Strategy for RIB Objects
Maintain Calculation Formulas for Revenues Increasing the Budget
Maintain Derivation Strategy for Rule Generation
See also
Program documentation Generate Rules for Revenues Increasing the Budget.
23.2.7.3.11 Budget text functionality in BCS (new)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 2.00), you can create, maintain, and display texts
______________________________________________________________
SAP AG
23
SAP System
______________________________________________________________
created for . FM account assignment elements via the Budget Text Organizer transaction FMTEXT. In
Release EA-PS 1.10, in contrast, the maintenance of budget texts was only possible in the budget
planning transaction.
You can access the budget text(s) you have created in the planning transaction FMPLCPD, the
Budgeting Workbench transaction FMBB, the Budget Structure maintenance transaction FMBSBO, and
in the RIB rule transaction FMRBRULE.
You can also copy the budget text(s) from one year to another, from one version to another, or from one
budget type to another using transaction FMCYTEXT Copy Budget Text.
Furthermore, in transaction SMARTFORMS, you can define a form (SAP Smartform) to be used for
budget texts. In this way, you can influence the layout of your budget texts, the individual elements to be
output (text, graphics, addresses, tables, etc.), the form logic that, for example, reads application data
from internal tables, introduces conditions and controls processes, and a form interface to pass the
application data to the form definition.
If you have created budget texts in Release EA-PS 1.10 via the budget planning transaction, these texts
will no longer be accessible in the new release. If you want to reload these texts into the new release, you
must first access Customizing and Define Key Fields for Budget Texts.
Carry out the following Customizing activities:
Define Key Fields for Budget Texts
Assign Forms for Budget Texts
23.2.7.4 PSM-FM-BCS-AC
Availability Control
23.2.7.4.1 Availability control functionality in BCS (changed)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), availability control has been enhanced in
BCS by the following functionality:
o
Control on revenues (incoming amounts)

Availability control usually limits expenditures or outgoing amounts. With the new ceiling type
revenues you can now assign independent tolerance limits for the checking of incoming amounts,
such as revenues from sales orders or from customer invoices.
Absolute variances
Tolerance profiles now enable you to check the limits you have set on availability control by using
absolute variances. In addition, you can specify how and in which order the system should apply
relative and absolute tolerances.
Please note that tolerance profiles supporting absolute variances must be assigned to a currency. The
system verifies whether this currency is the same as the currency of the FM area in which these
tolerance profiles are used.
______________________________________________________________
SAP AG
24
SAP System
______________________________________________________________
Overall checks
You can set up availability control so that it checks "overall values", which are defined as total
values over all fiscal years. You do this by selecting the checking horizon Overall Period.
In the Customizing of availability control, you can choose between two options to select the
appropriate value for the checking horizon:
a)
Derive it from the budget scope of the funds master data (default selection).
b)
Explicitly assign a checking horizon per control ledger.
Availability control on released budget

You can set up availability control to check budget consumption against normal budget or against
released budget. The following options exist:
c)
You can derive the value type for the budget (normal budget or released budget) from
fund-dependent settings (default selection).
d)
You can consider only the normal budget as relevant for availability control.

o
If you want to use availability control on revenues (tolerance profiles with ceiling type revenues)
and if you already used BCS budgeting with preposted budget documents in a previous R/3 release,
you have to reconstruct all availability control ledgers using transaction Availability Control:
Reconstruct (FMAVCREINIT).
You must adjust the Customizing entries of a previous R/3 release using the XPRA report AVC
Table Entry Control.

If you are upgrading from a previous release, Customizing settings will be converted in the XPRA report
RFBUAVC_APPLIC_XPRA ,AVC Table Entry Control . After the upgrade and XPRA run, you should
verify in the log that it has run without errors.
o
You can modify your tolerance profiles in the Customizing activity Edit Tolerance Profiles, if you
decide to activate availability control on revenues in your organization, or if you want to define
tolerance limits with absolute variances.
If you want to use budget control on overall values, you can set up funds with budget scope Overall
Budget in the funds master data. No further actions are necessary if you want availability control to
perform checks according to the selected budget scope. In all other cases, you must explicitly
specify the checking horizon per control ledger in the Customizing activity Select Checking Horizon
for Availability Control.
In the Customizing activity Define Filter Settings for Budget Values, you decide whether the
definition of the consumable budget for availability control should include released budget or not.
See also
Release note Budget release functionality in BCS.
______________________________________________________________
SAP AG
25
SAP System
______________________________________________________________
23.2.8 PSM-FM-PO
Funds Management-Specific Postings
23.2.8.1 Payment Directives for FM Payment Requests

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), a new transaction FMPO is provided in the
standard system to generate so-called payment directives.
In normal document processing, the process flow from a commitment to the final payment uses the
approved and posted invoice document in financial accounting as the basis for the payment process.
However, if a public sector organization (such as those in Spain, Portugal, and Italy) requires the
separation of tasks and the four-eyes principle for outgoing payments, a posted financial accounting
document cannot always be used as the basis for payments.
This means that an additional accounting document may be required to order the treasury or the
financial accounting department to pay an amount (not necessarily the invoice amount) to a third party:
o
The payment directive references other accounting documents, such as invoices and credit memos.
It is an intermediate document that follows the payment request or invoice and comes before the
payment itself. For the current release, only posting for expense (debit) documents is supported.
The document produced by a payment directive contains two line items, which both post to the same
vendor or customer account. In the general ledger, payment data is posted to a normal reconciliation
account and makes an offsetting posting in a special reconciliation account, which is used as the
basis for the payment process.
In this way, payment directives enable the separation of the invoicing process in the financial accounting
department from the actual payment in the treasury department, with the following features:
o
The payment directive allows a user to pay an invoice in several payments at different dates.
The payment directive is paid either by manual payment or by the automatic payment program,
while the original invoices are blocked for payment.
Since partial payment is supported, an invoice can be linked to several payment directives.
However, one payment directive cannot order the payment of several payments.
The payment directives are usual FI documents and also contain tax information. Normal
withholding tax handling is available.
The standard FI display transaction is used to display a payment directive.
It makes no difference whether the invoice has been generated in Funds Management, Financial
Accounting, or by invoice verification in Materials Management.
Make settings in Post FM Payment Directive.
______________________________________________________________
SAP AG
26
SAP System
______________________________________________________________
23.2.8.2 PSM-FM-PO-RE
Request
23.2.8.2.1 Business Add-Ins (BAdIs) for Requests (new)

Use
Starting from SAP R/3 Enterprise Public Services 2.00 (EA-PS 200) , you can use BAdI FM_REQUESTS
to change the GUI Status of requests.
To derive the G/L account, you can use BAdI FM_REQUEST_GL_ACC as well as the existing customer
exit EXIT_SAPLF0PR_001 (enhancement SAPLF0PR). You can use this BAdI to determine the G/L
account of the dependent funds center and fund. G/L account determination is only supported for the
commitment item by default as of SAP R/3 Enterprise Public Services 1.10.
If you want to use BAdI FM_REQUESTS , you must first activate it in IMG activity BAdI: Change GUI
Status of Requests .
IF you want to use BAdI FM_REQUEST_GL_ACC, you must first activate it in IMG activity
BAdI:Enhance Derivation of G/L Account.
See also
For more information, see the BAdI documentation on the above-mentioned IMG activities.
23.2.8.2.2 Request Functions (changed)

Use
The following changes/enhancements are included in Release SAP R/3 Enterprise Public Services 2.00
(EA-PS 200) :
o
Deleting standing requests

You can now delete parked original standing request documents. However, you are not allowed to
create any requests and/or FI documents from them and the parked original standing request
documents must be marked for deletion.
Automatic clearing of deduction, short-term waiver and remission.

The system now clears deductions, short-term waivers and remissions in the original documents
(payment/acceptance request or posted down payment) automatically with postings.
The system also automatically clears requests generated automatically with function Generate
Requests from Down Payments on Earmarked Funds.
Direct input of requests with program RFBIBLK0

Until now a selection screen appeared when you started program RFBIBLK0 which offered you a
choice between internal and external number assignment for the request number. This selection
screen will no longer appear as of this release. If you want to create a request with an external
number assignment, you need to set the corresponding indicator in data structure BBKPF_FM in
field LOTEXNO.
______________________________________________________________
SAP AG
27
SAP System
______________________________________________________________
Reassign Standing Request

You can now change the commitment item, fund, functional area and grant in standing requests
automatically by using program RFFMSRCICHNG. For German Government customers the
program can be used for structural and grouping changes.
Reversing Deferrals
When reversing a deferral, receivables that refer the same original receivable are combined into one
item. Deferral interest that accrues is written off and recalculated if necessary.
Deferral interest calculation

When defining the interest formulas for the deferral interest calculation, you can stipulate that no
deferral interest should be calculated for additional receivables as of this release.
23.2.9 PSM-FM-UP
Actual Update and Commitment Update
23.2.9.1 Business Add-In for Defining Expiry Month (new)

Use
Starting from SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can define an expiry
month for the end of the fiscal year using the Business Add In Define Expiry Month
(FMPA_END_MONTH) . This definition achieves the following:
All payments that are posted at the beginning of a new fiscal year until the date you specified, but that
refer to invoices from the old fiscal year will still be updated in the old fiscal year in Funds Management
(FM).
You can implement and activate the new BAdI by executing the IMG activity BAdI: Define Expiry
Month in the Customizing of Funds Management Government.
23.2.9.2 New Budgetary Ledger for USA Federal Government (New)

Use
Legislation in certain countries, including Federal legislation in the United States, imposes a legal
requirement to record certain data, such as budget creation or updates, and commitments, in a "budgetary
ledger". This is part of the general ledger (G/L), usually distinct from the ordinary FI accounts, which is
designed to record the budget and changes to it so that its status can be traced in the G/L.
The postings concerned can be regarded as a chain, starting with the appropriation of new budget and
ending with the payment made against the budget and until the appropriation cancellation.
Budgetary ledger functionality was first delivered with IS-PS 4.62. As of SAP R/3 Enterprise Public
Services 2.0, we are delivering a new budgetary ledger implementation. The old version continues to be
supported, but new implementations are advised to use the new version.
______________________________________________________________
SAP AG
28
SAP System
______________________________________________________________
See also
For more details, refer to the US Federal Government section of the SAP Library documentation.
23.2.9.3 Consignment Process in Funds Management (New)

Use
Funds Management can now handle the accounting for transfer and settlement of vendor consignment
stock into project stock. This includes the budget consumption during the transfer into project stock and
the settlement done using transaction MRK0.
23.2.9.4 Changes to the Funds Management (FM) Derivation Tool (changed)

Use
As of SAP R/3 Enterprise Public Services 2.0, a new rule type (FUNCTION MODULE) is available in
the FM derivation tool. Most predefined step rules are now obsolete since they can be replaced by the
new rule definition directly in the FM Derivation Tool. The transaction to maintain the predefined rules
has been adjusted to display only the rules still available.
The function KEDR_DERIVE_CHARACTERISTICS is now obsolete and is no longer used to derive the
FM assignments. The function ABADR_DERIVE_CHARACTERISTICS is used instead. The report
RFMXPR49 is used to migrate all step rules defined in the previous release.
The derivation tool now offers a Business Add-In (BAdI) enabling further validation of FM assignments.
The existing rules are still valid. Nevertheless, it is advisable to consider the option to replace old rules
with the new ones.
Use the transaction FMDERIVE to create new rules with type "Function Module" as a substitution for the
existing rules:
o
The list below shows the rules that were in Release IS-PS 4.62. Apart from the rules that appear in
table FMZUOB (the first four in the list), they are obsolete in Enterprise Release 2.0.
-
Sales Distribution assignment (table FMZUOB)
Plant Maintenance assignment (table FMZUOB)
Network header assignment (table FMZUOB)
Network activity assignment (table FMZUOB)
Functional area from G/L account
Commitment item from G/L account
______________________________________________________________
SAP AG
29
SAP System
______________________________________________________________
Funds center from commitment item master data
Fund from funds center master data
Cost center from order master data
Responsible Cost Center from Order Master Data
Requesting Cost Center from Order Master Data
Responsible Cost Center from WBS Master Data
Requesting Cost Center from WBS Master Data
Cost center from asset master data
Responsible cost center from asset master data
Functional area from cost center
Internal order from asset master data
Investment order from asset master data
Functional area from internal order
WBS element from order master data
WBS element from Network Header master data
WBS element from asset master data
Functional area from WBS element
Profit center from order master data
The following rules, which were new in Enterprise Release 1.0, are now obsolete:
-
Financial Transaction from Commitment item
Objects Assigned to Cost Center Master Data
Objects Assigned to Order Master Data
Objects Assigned to WBS element Master Data
Objects Assigned to Asset Master Data
See also
Check Account Assignment
23.2.9.5 Future-Dated Purchase Requisition/Purchase Order (NEW)

Use
You may want to prevent users from posting purchase requisitions (PR) or purchase orders (PO) on future
dates. As of SAP R/3 Enterprise Public Services 2.0, two customizable messages are provided so that you
can restrict such postings by user.
______________________________________________________________
SAP AG
30
SAP System
______________________________________________________________
In addition, two reports are provided to post the documents that are on hold.
The messages can be customized under the IMG activity Change Message Control
If the messages are not configured, they are not issued.
The message numbers are FICUSTOM 174 for posting of a PO and FICUSTOM 173 for posting of a PR.
You can also configure message FICUSTOM 172 to disallow the posting of a PO referencing a PR with a
later date than PO.
See also
Documentation of program RFFMFG_PR_HOLD_TO_POST.
23.2.9.6 Changes to Update for Parked Invoices (Changed)

Use
Before EA-PS 2.0, when an invoice was parked, it would update the relevant accounting receivers. As of
SAP R/3 Enterprise Public Services Release 2.0, you can decide whether a parked invoice should update
accounting receivers or not.
A BAdI BADI_PRKNG_NO_UPDATE has been provided. If you would like to update the accounting
receivers for a parked invoice, you do not have to implement the BAdI, but if you do not want to update
the accounting receivers for a parked invoice, implement the BAdI as in the sample code.
This change has a little impact on existing data.
23.2.9.7 Validity Dates for Application of Funds and Functional Area in FM

Use
You can now enter validity periods for application of funds or a functional area, limiting their validity to
a given span of time.
Existing functional areas and application of funds can be updated by giving an interval of time.
None.
Users cannot make postings outside the validity period defined for the application of funds or functional
area.
______________________________________________________________
SAP AG
31
SAP System
______________________________________________________________
BADI FM_DATES_ENHANCEMENT must be activated and must return an "X" flag in export
parameter E_ACTIVE.
APP_FUNDS_DATES_ACTIVE controls the dates for application of funds.
FUNCT_AREA_DATES_ACTIVE controls the validity periods for functional area.
23.2.9.8 Update Purchase Requisitions Generated from MRP to Accounting

(New)
Use
You can perform budget checks and encumber funds for purchase requisitions generated using
Consumption Based Planning in MRP and for purchase requisitions converted from planned orders. This
allows proper integration within Funds Management (FM) as well as enabling the system to more
accurately track budget and preventing budget overruns.
Limitations include the following:
o
Purchase requisitions cannot be updated or deleted using the MRP transactions (MD02, MD03), as it
is not possible to reverse or update the settlement receivers from the MRP transactions (an error
message appears if you try to do this. You can delete or update these purchase requisitions from
ME52N).
The MRP run does not delete purchase requisitions that have been updated in FM, as these
requisitions have been fixed for the MRP run.
To access the function, choose Public Sector Management -> Funds Management -> Posting -> Tools ->
Purchase Requisition -> Transfer from Requirement Planning.
You can select the existing purchase requisitions, generated by MRP or converted from planned orders, to
be updated to accounting.
o
Customize the derivation tool so that the following are derived:

-
GL accounts
FM account assignments
CO account assignments
Standard MM customizing for MRP is also required. There is no other customizing specific to this
function.
See also
See the documentation for program RFFMRP_MRP_PR,Updating PRs Generated from MRP into FM.
______________________________________________________________
SAP AG
32
SAP System
______________________________________________________________
23.2.9.9 Reassignment (new)

Use
For SAP R/3 Enterprise Public Services 2.00 (EA-PS 200) the program for the reassignment tool
was released:
o
Select documents, overall reassignment (RFFMCHAG)
Select documents, document reassignment (RFFMCHAB)
Work list reporting, reassignment tool (RFFMCHAR)
Delete work list, reassignment tool (RFFMCHAR)
Convert documents, supplementary account assignment and reassignment

(DS:RE.RFFMCHAT>(RFFMCHAT)
Until now, you could only use the reassignment program with the approval of SAP, as a reassignment of
source documents and all follow-on documents could not be guaranteed for all systems .
Starting from this release, it is possible to guarantee the reassignment of parked documents, purchase
requisitions, purchase orders and fund commitments through the official SAP change routines in all
systems. The corresponding Funds Management account assignments are kept consistent in the R/3
system (this means that the FM account assignment of the documents mentioned are identical in
Controlling and in Funds Management).
All documents and objects not mentioned here must still be reassigned manually although this is not
necessary for updated financial accounting documents that are posted.
However, you are still not allowed to use the reassignment tool together with the budgetary ledger.
If you use SAP R/3 Enterprise HR Extension 2.00 (EA-HR 200) as well as SAP R/3 Enterprise
Public Services 2.00 (EA-PS 200) and want to transfer account assignment changes executed
in Funds Management for commitment documents to Human Resources department for
infotype record, use one of the following programs:
o
Transfer Reassignment from Funds Management for Infotypes of Personnel Administration
Transfer Reassignment from Funds Management for Infotypes of Personnel Planning and
Development
In order to enter the overall reassignment, you must create a derivation strategy that contains the
assignments from the old to the new account assignments starting from this release.
To do this, in the IMG of Funds Management Government, execute IMG activity Define Derivation
Strategy for Reassignment.
The derivation strategy enables you to enter rules more easily than before and offers more functions.
See also
For more information on reassignments, see the SAP Library, under SAP R/3 Enterprise Applications
-> Accounting -> Public Sector Management -> Funds Management -> Actual/ Commitment
Update -> Reassignment
______________________________________________________________
SAP AG
33
SAP System
______________________________________________________________
23.2.9.10 Different Local Currency for Company Code and FM Area (new)
Use
Until now, the company codes had to have the same local currency as the assigned FM areas.
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), the first local currency for your
company code (company code currency) no longer needs to match the FM area currency.
If you do not want to use this function, you must create an additional local currency that matches your
FM area currency. This ensures that the data from Financial Accounting is updated in Funds
Management (FM) without any errors occurring. The amounts in the additional local currency are
transferred from FM as the FM area amount.
You can only use this function if you implement Funds Management again. Otherwise, the document
updated in Funds Management must be posted subsequently.
If you want to use this function, you must create an additional local currency (currency type) for the
corresponding company codes in the IMG of Financial Accounting. You can use IMG activity "Define
Additional Local Currencies" to do this.
You must then assign the currency type of the additional local currency to the FM area. To do this,
execute IMG activity "Make Other Settings ". in the IMG of Funds Management.
23.2.10 PSM-FM-CL
Closing Operations
23.2.10.1 Commitment Carryforward (enhanced)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200) the following new functions are
available in Funds Management for carrying forward commitment:
o
Commitment Carryforward with Document Chains

You can use program Closing Operations: Carryforward Open Items (Chains)
(RFFMCCF1_CHAIN) to carry forward commitment with document chains.
With this program, you can carry forward document chains that consist of linked commitment
document items (e.g. earmarked funds and invoice or purchase requisition and purchase order) in
accordance with different processing types. The processing type determines which open and
consumed amounts of the document items in the chain should be carried forward.
Undo Commitment Carryforward with Document Chains

With program Closing Operations: Undo Carryforward of Open Items (Chains)
(RFFMCCFR_CHAIN) you can undo the commitment carryforward with chains again.
______________________________________________________________
SAP AG
34
SAP System
______________________________________________________________
Manual Selection of Receiver Account Assignment for Commitment Carryforward

In the derivation strategy for account assignment determination for the commitment carryforward
you can assign several receiver account assignments to a sender account assignment. The user can
select one of the assigned receiver account assignments.
Approval of Commitment Carryforward

The commitment carryforward can run a one-level or two-level approval procedure.
If the approval procedure is active in Customizing, the commitment carryforward programs
(RFFMCCF1 and RFFMCCF1_CHAIN) do not execute the carryforward directly, they can only
select the documents for the carryforward with these programs. You can use program Approve
Carryforward of Open Items (RFFMCCF_APPROVE) to reject or approve the carryforward for
selected documents.
If you want to use the commitment carryforward with document chains, the manual selection of receiver
account assignment or the approval procedure, you must activate the respective function in Customizing
of Funds Management.
To do this, in the implementation guide (IMG) of Funds Management Government, execute IMG
activity"Define Basic Settings for the Commitment Carryforward".
So as to facilitate a manual selection of the receiver account assignment, you must assign your derivation
strategy for account assignment determination to your FM area with the commitment carryforward.
To do this, you must execute the following activities in the IMG of Funds Management Government:
o
Assign FM Area Strategy for Reassignment
23.2.10.2 Commitment Carryforward for Expiry Period (new)

Use
Starting from SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can use the function
Commitment Carryforward According to Entry Date (program RFFMCCFD) for the commitment
carryforward during the expiry month. You can use this to select and process commitment documents by
their entry date (with the exception of travel documents).
23.2.10.3 Balance Carryforward (enhanced)

Use
With SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), the functions of the balance
carryforward program (SAPFMVTR) for the multi-year budget have been enhanced. As soon as you
have activated the multi-year budget for FM area, the functions of the program have been reconciled to a
new system setting.
______________________________________________________________
SAP AG
35
SAP System
______________________________________________________________
IF you have not activated the multi-year budget, the old program functions remain the same.
Note that you must adjust the reporting for fund balances if necessary when activating multi-year budget
execution as no summarization then occurs via the commitment items through the balance carryforward
of the fund.
See also
Release Information for Multi-Year Budget Execution
23.2.10.4 Close-Out of Unfilled Customer Orders (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, you can reduce and close customer orders.
A customer order is an incoming reimbursable order from a goverment agency, or non-federal customer
that provides funding. Customer orders are commonly provided via federal customers, but can also be
orders from non-federal customers if accompanied by advance funds.
Periodic Closing and Fiscal Year End
The limited availability of Federal funding (annual funds, multi-year funds, and so on) means that closing
actions are associated when funding expires. The closing actions are required when the authority/funds
for the agency providing the goods/services expire and/or when the authority/funds for the agency paying
for the goods/services expire. If the customer funds expire this must be returned to the customer. If the
customer funds do not expire, they can be moved to the new fiscal year.
A BAdI BADI_UNFILLED_ORDERS has been provided. If you would like to update the quantity
amount or the obligation amount of the sales order you can do it implementing the BAdI.
23.2.10.5 Reassignment in Year-End Operations (changed)

Use
The maintenance of carryforward parameters and rules for reassignment in the year-end operations have
been replaced in SAP R/3 Enterprise Public Services 2.00 (EA-PS 200). The rules for reassignment
can now be entered by defining one or more derivation strategies.
Reassignment was only possible for commitment carryforward and budget carryforward up until now.
This new procedure also enables reassignment in all other functions used during year-end operations, for
example, when copying budget versions or rules for cover eligibility.
The definition of carryforward parameters and the definiion, display and copying of carryforward rules
(transactions FMD1, FMD2 and FMDS) are not part of the implementation guide (IMG) anymore (IMG)
or the Funds Management menu. There is a new IMG activity available for editing derivation strategies
and there is a new transaction for editing account assignment derivation (rule maintenance) (FMYCR).
______________________________________________________________
SAP AG
36
SAP System
______________________________________________________________
From this release, external documents are reassigned in the year-end operations using official SAP
change routines. You can find more information in the release information Reassignment (new).
If you use SAP R/3 Enterprise HR Extension 2.00 (EA-HR 200) in addition to SAP R/3 Enterprise
Public Services 2.00 (EA-PS 200) and want to transfer account assignment changes made in
Funds Management within year-end operations for infotype records in Human Resources, use
one of the following programs:
o
Transfer Reassignment from Funds Management for Personnel Administration Infotypes
Transfer Reassignment from Funds Management for Infotypes of Personnel Planning and
Development

Existing carryforward rules can still be edited using the transactions FMD1, FMD2 and FMDS. If you
want to continue to use the rules for the year-end operations, proceed as follows:
o
You can define the carryforward parameters using the view V_FMYC_CFRULE (SM30), view
V_FMYC_CFC1R for the commitment carryforward and the views V_FMYC_CFRULE and
V_FMYC_CFC2_2 for the carryforward of residual budget.
Then create a derivation strategy for the reassignment and define a derivation step of the type
"function module". Enter the function module FM_FYC_RECEIVER_GET (carryforward rules
(FMCFSB) read).
If you want to make changes to account assignments for the fiscal year
change, create a derivation strategy which contains the assignments from the old account assignments to
the new ones. Then assign this strategy to your FM area.
Execute the following activities in the implementation guide of Funds Management Government:
o
Assign Derivation Strategy for Reassignment to FM Area
23.2.11 PSM-FM-IS
Information system
23.2.11.1 Line Item Reports Using the Document Journal (changed)

Use
The report Document Journal is available from SAP R/3 Enterprise Public Services 2.00 (EA-PS 200).
This report selects data according to FM account assignments and issues all movements on the selected
account assignments.
The document journal replaces the following line item reports in the info system of Funds Management in
EA-PS 2.0.
FFMEP1OX
commitment and fund transfers
RFFMEP1FX
FI postings
______________________________________________________________
SAP AG
37
SAP System
______________________________________________________________
RFFMEP1CX
RFFMEP1AX
CO postings
all postings
The report RFFMEP2FX (FI postings with document header information) was removed from the menu
because the functionality and selection screen are identical to RFFMEP1FX.
The original transaction calls of the line item report remain in the menu, but call the new document
journal with the selection screen.
The main difference from the previous line item reports is that much more data can be displayed in the
document journal (document header data, document item data, bank details data, CO data, subledger
account data, FI-CA documents). In addition to the previous reports, it is possible to restrict the number
of data read and specify a layout.
You can find more information on the functions of the document journal in the report documentation.
You cannot use the report variants from the variant catalog of the previous report for the document
journal. SAP delivers a default variant instead.
You can enhance the document journal using the Business Add-In FMRP_RFFMEPGAX_EXIT.
23.2.11.2
23.2.12 PSM-FM-DE
Special Function Public Sector Germany
23.2.12.1 Functions for Public-Owned Commercial Operations (Enhanced)

Use
Release SAP R/3 Enterprise Public Services 2.00 (EA-PS 200) includes the following enhancements for
public-owned commercial operations:
Connection to Schedule Manager
From now on the following PCO program and transactions support the Schedule Manager:
o
Program RFFMBGCPY (Copies PCO account assignments)
Program RFFMVAQ (Determines input tax deduction rate)
Program RFFMVCORM (Determines the monthly input tax adjustment values)
Program RFFMVCORJ (Determines the annual input tax adjustment values)
Transaction FMBGM (Posts input tax adjustments)
Transaction FMBGJ (Posts annual adjustments)
Lifting posting restrictions / Tax split

All postings restrictions that occur in connection with the tax line are lifted. It is now possible to enter an
______________________________________________________________
SAP AG
38
SAP System
______________________________________________________________
invoice with a tax code and several PCOs. With these restrictions gone, it is possible that rounding
differences may occur for individual PCOs with the tax display (sales tax list) that must be accepted.
Transfer Postings with the Same Tax code
Transfer postings, in other words, clearing requests between PCOs for the same tax code are now
allowed. The postings must have a special document type. The possible document types must be defined
in Customizing.
You define the document types for postings in the IMG activity Define Document Type for Transfer
Postings.
23.2.12.2 Copying Year-Dependent PCO Account Assignments (enhanced)

Use
Starting from release SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), Program allows you to copy
PCO assignments from one year to another as well as the reassignment parameters (structural and
grouping changes)
It is now possible to copy entries if the master data does not yet exist in the new year. You can also delete
indicator Only add ex. account assignments .
As of this release, it is possible to execute an authorization check when executing the program run as well
as FM area authorization check; in other words only people who have authorizations for PCO
Customizing can execute the program.
The program was deleted from Customizing with release and is now available for closing operations in
the menu of Funds Management, under Additional Functions -> Additional Functions German
Government -> Closing Operations -> Preliminary Steps -> Copy PCO Assignment.
23.2.12.3
23.2.12.4
23.2.12.5
23.2.12.6 Assigning Commitment Items to Revenue Types (New)
Use
With Release SAP R/3 Enterprise Public Services 2.00 (EA-PS 200) SAP provides a program that
German Government customers can use to copy the assignments of commitment items to revenue types
for a fiscal year variant to another.
______________________________________________________________
SAP AG
39
SAP System
______________________________________________________________
See also
For more information on the functions of this program, see the program documentation.
23.2.12.7 Grouping and Structural Changes (changed)

Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200) a majority of the closing operations
that have to be executed by German Government customers (activities in the menu section Grouping
and Structural Changes ) have been transferred to the standard closing operations of Funds
Management.
The menu section Grouping and Structural Changes has been renamed Preparation. In this menu
section you will still find program Copy Commitment Items to the Following Year and two new functions
(info under: See also). The menu entries for maintaining the derivation strategies for the fiscal year
change were removed. These settings are now executed in the Customizing of Funds Management.
Functions such as generating strategies and carryover rules as well as activating strategies are no longer
required.
For more information, see the release information Reassignment with Year-End Operations.
EA-PS 200 SP1 provides you with the postprocessing program RFFM_UPGRADE_FMREAS_RULES
so you can transfer defined strategies of earlier releases. For more information, see note 640128.
You maintain the derivation strategies for grouping and structural changes in IMG activity Define
Derivation Strategy for Reassignment.
See also
o
Copy Assignments of Commitment Items to Revenue Types
Copy Year-Dependent PCO Account Assignments
23.2.12.8 Comparison of Key Figures (new)

Use
The report RFFMKFCHECK is available from SAP R/3 Enterprise Public Services 2.00 (EA-PS 200). It
is used to compare key figure definitions between different systems and/or clients to determine any
possible differences.
You execute the report in Customizing of Funds Management under Compare Key Figures.
______________________________________________________________
SAP AG
40
SAP System
______________________________________________________________
23.2.12.9
23.2.12.10
23.2.12.11
23.2.12.12 Cross-Company Code Evaluation for Public-Owned Commercial
Operations (changed)
Use
The reports on evaluating public-owned commercial operations (PCO) such as cash discount and
backdated tax calculation program could only be executed for one company code until now.
The reports and program have been enhanced with release SAP R/3 Enterprise Public Services 2.00
(EA-PS 200). It is now possible to process the data of several company codes. This involves the data
being evaluated separately in different company codes and/or processed sequentially. The following are
affected by this enhancement:
o
Sales Tax List (RFFMBGA)
Automatic Calculation of Input Tax Deduction Rate (RFFMVAQ)
Determination of Input Tax Adjustment for Monthly and Annual Values ( RFFMVCORM and
RFFMVCORJ)
Cash Discount and Backdated Tax Calculation (RFFMBGDC).
In spite of this enhancement, it is still not possible to post cross-company code documents on account
assignments in PCOs if the tax posting does not take place in the company code of the PCO (for example,
a posting of PCO 0001 in company code 0001 to a PCO 0002 in company code 0002).
If you have already created input tax deduction rates (ITDR) and want to carry on using them, you must
transfer the existing entries of table FMBGAVAQS to the new table FMBGAVAQF.
You call the existing ITDRs in transaction SM30 with the view V_FMBGAVAQS and can trasnfer this to
the the new table in the manual ITDR maintenance OFMBG2. To do this, replace the company code with
the assigned FM area.
If you want to use a PCO in all company codes, the affected company codes must fulfill the following
consistency checks:
o
All affected company codes must be assigned to the same FM area.

IMG activity Assign Company Code to FM Area.
The same tax codes are assigned to the company codes for non-taxable transactions.
IMG activity Assign Tax Code for Non-Taxable Transactions
The company codes use the same local currency.
______________________________________________________________
SAP AG
41
SAP System
______________________________________________________________
IMG activity Edit, Copy, Delete, Check Company Code.

o
The company codes use the same tax calculation procedure.

IMG activity Assign Country to Calculation Procedure.
23.2.12.13
23.2.12.14 Reorganization of Funds Centers and Commitment Items (new)
Use
As of SAP R/3 Enterprise Public Services 2.00 (EA-PS 200), you can reorganize master data within
a current fiscal year. Up until now, this was not possible once budget allocation or budget entry had taken
place.
Now it is possible to reorganize commitment items/funds centers under the following conditions:
o
All budget values must be set to zero on a budget type basis.
Budget texts can be entered.
If these conditions are met, you can maintain the hierarchy in the Funds Management menu using
Change Standard Hierarchy of Commitment Items and Change Standard Hierarchy of Funds
Centers. Then it is also possible to delete commitment items/funds centers.
23.2.12.15
23.2.12.16 Summary Carrryforward of down payments and down payment
clearings (new
Use
Starting from SAP R/3 Enterprise Public Services 2.00 (EA-PS 200) , you can carry forward the
amounts from down payments and down payment clearings in a summarized form via the FM account
assignment from one fiscal year to the following. You can do this using program Closing Operations:
Carry Forward Down Payments and Down Payment Clearings (RFFMCCF_DP).
23.3 PSM-GM
Grants Management
23.3.1 Changes to Grants Management Implementation Guide (changed)

Use
As of SAP R/3 Enterprise Public Services 2.0, the structure of the Grants Management (GM)
______________________________________________________________
SAP AG
42
SAP System
______________________________________________________________
Implementation Guide (IMG) has changed. In addition, some functions in that structure have been
renamed.
o
A new BAdI has been added to the Global Settings for Override Updating Attributes.
The Grant subnode of the Master Data section has changed as follows:
RENAMED function - Maintain Grant Number Ranges (previously Maintain GM Number

Ranges)
RENAMED function - Maintain Grant Authorization Types (previously Maintain GM

Authorization Types)
RENAMED function - Maintain Grant Authorization Groups (previously Maintain GM

Authorization Groups)
A new Maintain Grant Relationships step has been added to this section.
A new Workflow Settings for Grant Master Data subnode and step have been added.
The Budgeting section has changed, reflecting the change to the Budget Control System (BCS)
functionality, as follows:
-
NEW function: Maintain Number Range Interval for Budget Change Documents
RENAMED function - Assign Budget Phase to Version (previously GM Budget Version)
The Availability Control section is now structured as follows:

-
NEW Step: Prepare Activation of Availability Control

Contains documentation only. No function is attached to this step.
NEW Function: Check Standard Customizing of Availability Control
MOVED Function - Maintain Activation Status for GM Availability Control Ledger

This function now appears at the end of the Availability Control section of the GM IMG.
NEW Node - Settings for Availability Control Ledger

NEW Function - Create User-Defined Ledger for Availability Control
RENAMED Function - Define Filter Settings for Budget Values (previously "Maintain AVC
Filters for GM Budget Values")
RENAMED Function - Define Filter Settings for Actual Values (previously "Maintain AVC
Filters for GM Actual Values")
RENAMED Function - Define Account Assignment Derivation of Availability Control Objects
(previously "Derive GM Control Objects")
RENAMED Function - Maintain Derivation Strategy for Overriding the Standard Tolerance
Profile (previously "Derive GM Tolerance Profile")
RENAMED Function - Assign Attributes for Availability Control Ledger (previously
"Maintain Attributes for GM Availability Control Ledger")
The node "Derive GM Activity Groups" has been deleted.
A new Workflow Settings subnode has been added, containing the Budget Workflow Settings
transaction.
A new Integration node has been added, containing the following:

-
Activate Integration with Position and Budget Control
______________________________________________________________
SAP AG
43
SAP System
______________________________________________________________
BAdI: Integration with Records Management
A new Reporting node has been added, containing the following:

-
Report Tracking/Monitoring
Maintain Report Classes
Maintain Schedule Rules
Maintain Report Rules
BAdI: Define Date for Report Tracking
BAdI: Enhancement functions for GM Reporting
23.3.2 PSM-GM-MD
Master Data
23.3.2.1 Changes to the Grants Management (GM) Derivation Tool (Changed)

Use
As of SAP R/3 Enterprise Public Services 2.0, a new rule type 'FUNCTION MODULE' is available in the
GM Derivation Tool. It permits you to retrieve assignments stored in the master data (examples: G/L
account, cost center, WBS element, asset).
The function KEDR_DERIVE_CHARACTERISTICS is now obsolete and is no longer used to derive the
GM assignments. The function ABADR_DERIVE_CHARACTERISTICS shall be used instead. The
report RFMXPR49 is used to migrate all step rules defined in the previous release.
Predefined rules can be added directly using transaction GMDERIVE.
See also
Changes in the FM Derivation Tool
23.3.2.2 Master Data Relationships in Grants Management (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, grants can be linked to other business partners and other
grants.
Not applicable.
New relationships can be defined in the IMG within the customer name space. Standard relationships for
______________________________________________________________
SAP AG
44
SAP System
______________________________________________________________
primary source of funds, and grant recipient are delivered.
23.3.2.3 Report Tracking and Monitoring Function in Grants Management (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, the Grants Management (GM) solution includes a report
tracking and monitoring feature. This supports the following:
o
Group reports or workflows together as different Report Classes
Record reporting rules representing sponsor reporting requirements

Reporting rules can be one-time or periodic (daily, weekly, monthly, and annually).
Specify default reports and/or workflows, as well as reporting rules in sponsor master data
Specify default reports and/or workflows, as well as reporting rules in grant types
Allow user to schedule the details based on the grant reporting rules
Automatically execute the reports or workflows based on scheduling, and provide job status
Notifying the responsible person can be satisfied by using SAP workflows.
Generate audit trail with time and date stamp for each grant reporting rule
The generic reporting rules, along with the reports and/or workflows, should be created and assigned to
grant types and sponsor master records first. When the grant master is created, the system defaults these
automatically. You can accept or reject the defaults, and add more reports and/or workflows.
For a report or workflow that needs to be scheduled periodically, enter the detailed scheduling parameters
(for example, which day of which month, for a yearly report rule) in the grant master. The report or
workflow is scheduled when you save the grant master.
After the reports and/or workflows are scheduled in the grant master record, the system carries out the
tasks when the time parameters are satisfied.
Each of the above steps is used to support the grantee organization's responsibilities for sponsor
reporting.
23.3.2.4 Changes to Sponsored Programs and Sponsored Classes (changed)

Use
As of SAP R/3 Enterprise Public Services Release 2.0, the following new features apply to sponsored
programs and classes:
o
Master data maintenance for the sponsored program and sponsored class now permits multiple
Funds Management (FM) assignments when Grants Management is integrated with FM.
Two new customizing flags are available in the sponsored program and sponsored class master data:
Validate Budget Transfer
Validate Allowed Budget and Posting Objects
______________________________________________________________
SAP AG
45
SAP System
______________________________________________________________

Existing FM assignments are not transferred to the new assignments. You must maintain them manually.
23.3.2.5 Position Control Adjustments in Time Slices (Changed)

Use
As of SAP R/3 Enterprise Public Services Release 2.0, if position control is active for Grants Management
(GM), then the budget validity periods are adjusted to the start of the first day of the posting period.
There is an IMG node for activation of position control in GM.
23.3.2.6 Grants Management Workflow (New)

Use
As of SAP R/3 Enterprise Public Services Release 2.0, basic workflow is being introduced to Grants
Management (GM) for the following business processes:
o
Grant master data
Budget documents
With this functionality, your organization can electronically route, review, and approve grant master data
and budget documents on the basis of user-defined responsibility types created in GM.
The new functionality involves the following:
o
Electronic notifications for updates of the grant master data lifecycle and user statuses.
Electronic approval for updates of the grant master data Lifecycle and user statuses
Electronic approval of budget documents
Review and approval procedures required to support the basic business processes for grant master
data and budgeting documents.
Electronically capture and document the required approvals from the responsible person(s) before
recording master data updates and budget documents.
Date and time stamp for each step in the review and approval process for evaluate organizational
efficiencies.
GM introduces basic workflow scenarios for grant master data and budgeting transactions. The following
elements are used to support workflow:
o
Grant responsibility type
Business Objects
WF activities
______________________________________________________________
SAP AG
46
SAP System
______________________________________________________________
Grant responsibility types are user defined and represent resources (such as users, persons, positions,
work centers, or organizational units) that participate in the administration of sponsor awards. In turn,
responsibility types are assigned in the grant master record; theycan be selected as participants in GM
workflow activities.
Business Objects represent the SAP data elements and transactions available to take part in workflow
activities. In GM, unique Business Objects for the grant master record and budget documents have been
created for use in workflow.
Finally, WF activities are the actions used to invoke or trigger workflow. The grant lifecycle and user
statuses are the events that initiate workflow processing for the grant master and the 'Preposted' budget
document status is the event used to initiate workflow process for GM budgeting.
Grant Master Data
Workflow can be used for reviews and approval of grant master data. Specifically, workflow can be
initiated for any change in the grant master data status. Note that grant master data status changes include
both the lifecycle statuses, which we deliver as standard (initial draft, proposal, application, award,
closing, and closed) and user statuses, which are user-defined. Both types of status are used to represent
the organization's business processes; this means that workflow be invoked to obtain the required reviews
and approvals before the grant master record is switched to the next status.
For example, before the grant lifecycle status is changed from Proposal to Application or Application to
Award, an authorized official reviews the proposed master data update(s) to determine whether the action
is appropriate. If the update(s) are appropriate, the responsible person approves the master data using GM
workflow.
In addition to reviews and approvals, workflow can also be used as a communication tool. In this
situation, a responsible person receives a workflow message for information purposes only. No action is
required in this scenario, though the responsible person is still provided a workflow message with a
description of the action reviewed or approved.
Budgeting
GM uses the budget document status 'Preposted' to initiate workflow processes for GM Budgeting.
When using workflow, the responsible person is then allowed to review and approve budget documents
prior to posting the budget document. In addition, GM budget documents can be entered for three Grant
Lifecycle statuses: Proposal, Application, and Award. Although entering budget documents at each of
theses stages is optional, based on the Organization's business process requirements, workflow is
supported for each stage utilized by the Organization.
For example, if a budget document is entered for a Grant Proposal and approval is required, then
workflow would be started once the budget document status is set to 'Preposted'. In addition, workflow
for GM budgeting can be implemented for each lifecycle status. Thus approval could be required for
Budget documents involving grants with a Lifecyclestatus Application and Award,but not for the
Proposal. Thus, budget documents involving grants in the Proposal stage would not require approval, but
once the grant master record is updated to Application or Award, budget documents would require
approval by the user's manager.
Technically, workflow for GM budgeting uses budget document status, the grant lifecycle status, and the
responsibility types recorded in the Grant master record as the business objects. Next, workflow is
triggered when the budget document status is set to 'Preposted' (the event). Together, these elements are
______________________________________________________________
SAP AG
47
SAP System
______________________________________________________________
used to support workflow for GM budgeting.
23.3.3 PSM-GM-BU
Budgeting and Availability Control
23.3.3.1 Flexible Layout of GM Budgeting Dimensions (New)

Use
Budgeting in Grants Management (GM) previously consisted of entering values for all GM budgeting
dimensions: grant, fund, sponsored program, sponsored class and timeslice for each phase of the grant
(that is, proposal, application, and award).
As of SAP R/3 Enterprise Public Services 2.0, the solution includes features enabling you to:
o
Deactivate specific GM budgeting dimensions
Redefine the hierarchical order of the GM budgeting dimensions
Enhancements to the layout of the GM budgeting dimensions provide the following business value:
o
You can enter only the budget data required for grant proposals, applications, and awards. This
makes the tool more efficient and reducesthe need for training.
The budget layout supports the organization's pre-award requirements and the sponsor's post-award
requirements.
You can organize budgeting transactions to represent the organization's view of budgeting.
The flexible layout enhancement is intended to enable greater control inentering and displaying
budget information in GM.
First the standard budgeting data entry and layout consist of the following GM dimensions:
-
Grant
Fund
Sponsored Program
Sponsored Class
Timeslice
The above budgeting dimensions appear in the standard GM budgeting transaction. With the new
functionality, it is possible to deactivate any of these budgeting dimensions when entering a GM
budgeting document. This means you can suppress any of the specific budgeting dimensions based on the
business process. For example, consider the impact the enhancement on the business process when
entering budget documents for a grant proposal, application, and award.
o
Grant Proposal: require and enter the Grant dimension only.
Grant Application: require and enter the Grant and Sponsored Class dimensions.
Grant Award: all dimensions are required. No options are available since all dimensions are required
for processing documents and postings in GM.
For the grant proposal and application, only minimum data entry is required, making the budgeting
______________________________________________________________
SAP AG
48
SAP System
______________________________________________________________
process more efficient. In addition, all budgeting dimensions are required in the award phase, which is
why the dimensions cannot be suppressed there.
Budget Document Standard Layout
GM dimensions appear in a standard order: Grant, Fund, Sponsored Program Sponsored Class and
Timeslice. With the enhancement, the standard order can be altered to improve the presentation of the
data in the budget document. Any changes are effected on both the Hierarchical and List View tabs in
the Budget Document data entry screen. The budget document dimension layout can also be maintained
in GM customizing, grant master data, and GM budget documents. Multiple options are thus available for
managing the layout; which you use depends on your organization's business requirements.
The entry points are as follows:
o
Grant type customizing

See Customizing below.
Grant master data

Maintain Grant Master Goto Budgeting Tab, then enter the desired version and layout.
GM Budgeting Document, just for display purposes

GM Budget Modification Goto Edit -> Chng Dimension Order.

A report (to be developed) will fill in the appropriate information.
To customize the layout in the grant type, choose Maintain Grant Types -> Grant Type -> Budget
Layout in the IMG.
23.3.3.2 Budgeting GM-FM Integration (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, this functionality is used to integrate individual Grants
Management (GM) budgeting objects with one or more Funds Management (FM) budgeting objects.
Since GM objects are organized on a time basis, you might have the opportunity to distribute amounts
over several fiscal years.
The new functionality consists of allowing more than one element per fiscal year.
To do that, start at Sponsored Program Master Data and Sponsored Class Master Data, where you can
enter a validation type indicator and the FM objects linked.
Then go to the budgeting transaction Create GM Budgeting or Modify GM Budgeting and, if you are
processing an award-released document, you see an FM fiscal year distribution table where you can
distribute the GM budget line amount over several FM budget lines.
Several features are available to make processing easier:
o
Drag&Drop
______________________________________________________________
SAP AG
49
SAP System
______________________________________________________________
Copy from FM Object lines
Delete lines.
You can also double-click to the master data transactions for the objects in GM and FM:
-
Grant
Fund
Program
Class
Commitment Item
Funds Center
Functional Area
Funded Program
See also
Sponsored Object Release Note Documentation
23.3.3.3 BAPIs for Budgeting in Grants Management (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, the following new Business Application Programming
Interfaces (BAPIs) are available:
Budget Entry Document
To use Grants Management (GM) budgeting processes from an external system, the following new
methods of the Business Object Repository (BOR) object BudgetEntryDocGM are provided:
o
Create: BudgetEntryDocGM.Create
GetDetail: BudgetEntryDocGM.GetDetail
GetList: BudgetEntryDocGM.GetList
Reverse: BudgetEntryDocGM.Reverse
23.3.3.4 BAPIs for Grant Master Data in Grants Management (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, the following new Business Application Programming
Interfaces (BAPIs) are available:
Grant
______________________________________________________________
SAP AG
50
SAP System
______________________________________________________________
To use grants management grant master data from an external system, the following new methods of the
Business Object Repository (BOR) object Grant are provided:
o
Create: Grant.Create
GetDetail: Grant.GetDetail
GetList: Grant.Change
23.3.3.5 New AVC and Checking Functionality in Grants Management (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, availability control (AVC) has been enhanced in Grants
Management (GM) with the following functionality:
o
Control on revenues (incoming amounts)

AVC usually limits expenditures or outgoing amounts. With the new ceiling type revenues, you
now have the option of assigning independent tolerance limits to check incoming amounts, such as
revenues from customer/sponsor invoices.
If you want to use AVC on revenues and if you already used GM AVC in a previous SAP R/3
release, we strongly recommend that you reconstruct all AVC ledgers, in the SAP menu under
Accounting -> Public Sector Management -> Grants Management -> Budgeting -> Tools ->
Availability Control: Reconstruct (transaction GMAVCREINIT).
Overall checks
AVC can be set up to check overall values defined as total values over all fiscal years. You define
this by selecting the checking horizon Overall Period.
In AVC customizing, you can choose between one of the following options for selecting the
appropriate value of the checking horizon:
a)
Derive it from the grant or company code through a strategy.
b)
Explicitly assign a checking horizon per control ledger.
Separate Customizing entries for Funds Management and Grants Management:

As of SAP R/3 Enterprise Public Services 2.0, AVC provides different key ranges for Customizing
entries of Funds Management and GM - for instance, for activity groups and tolerance profiles.
If you are upgrading from a previous R/3 release, the Customizing entries concerned must be
adjusted by an XPRA report (see below).

o
If you want to use AVC on revenues (tolerance profiles with ceiling type revenues) and if you
already used GM budgeting with preposted budget documents in a previous R/3 release, you have to
reconstruct all AVC ledgers using transaction GMAVCREINIT.
o
You can modify your tolerance profiles in the Customizing activity Edit Tolerance Profiles, if you
decide to activate AVC on revenues in your organization, or if you define tolerance limits with
absolute variances.
______________________________________________________________
SAP AG
51
SAP System
______________________________________________________________
23.3.3.6 Grants Management Workflow (New)

Use
As of SAP R/3 Enterprise Public Services Release 2.0, basic workflow is being introduced to Grants
Management (GM) for the following business processes:
o
Grant master data
Budget documents
With this functionality, your organization can electronically route, review, and approve grant master data
and budget documents on the basis of user-defined responsibility types created in GM.
The new functionality involves the following:
o
Electronic notifications for updates of the grant master data lifecycle and user statuses.
Electronic approval for updates of the grant master data Lifecycle and user statuses
Electronic approval of budget documents
Review and approval procedures required to support the basic business processes for grant master
data and budgeting documents.
Electronically capture and document the required approvals from the responsible person(s) before
recording master data updates and budget documents.
Date and time stamp for each step in the review and approval process for evaluate organizational
efficiencies.
GM introduces basic workflow scenarios for grant master data and budgeting transactions. The following
elements are used to support workflow:
o
Grant responsibility type
Business Objects
WF activities
Grant responsibility types are user defined and represent resources (such as users, persons, positions,
work centers, or organizational units) that participate in the administration of sponsor awards. In turn,
responsibility types are assigned in the grant master record; theycan be selected as participants in GM
workflow activities.
Business Objects represent the SAP data elements and transactions available to take part in workflow
activities. In GM, unique Business Objects for the grant master record and budget documents have been
created for use in workflow.
Finally, WF activities are the actions used to invoke or trigger workflow. The grant lifecycle and user
statuses are the events that initiate workflow processing for the grant master and the 'Preposted' budget
document status is the event used to initiate workflow process for GM budgeting.
Grant Master Data
Workflow can be used for reviews and approval of grant master data. Specifically, workflow can be
______________________________________________________________
SAP AG
52
SAP System
______________________________________________________________
initiated for any change in the grant master data status. Note that grant master data status changes include
both the lifecycle statuses, which we deliver as standard (initial draft, proposal, application, award,
closing, and closed) and user statuses, which are user-defined. Both types of status are used to represent
the organization's business processes; this means that workflow be invoked to obtain the required reviews
and approvals before the grant master record is switched to the next status.
For example, before the grant lifecycle status is changed from Proposal to Application or Application to
Award, an authorized official reviews the proposed master data update(s) to determine whether the action
is appropriate. If the update(s) are appropriate, the responsible person approves the master data using GM
workflow.
In addition to reviews and approvals, workflow can also be used as a communication tool. In this
situation, a responsible person receives a workflow message for information purposes only. No action is
required in this scenario, though the responsible person is still provided a workflow message with a
description of the action reviewed or approved.
Budgeting
GM uses the budget document status 'Preposted' to initiate workflow processes for GM Budgeting.
When using workflow, the responsible person is then allowed to review and approve budget documents
prior to posting the budget document. In addition, GM budget documents can be entered for three Grant
Lifecycle statuses: Proposal, Application, and Award. Although entering budget documents at each of
theses stages is optional, based on the Organization's business process requirements, workflow is
supported for each stage utilized by the Organization.
For example, if a budget document is entered for a Grant Proposal and approval is required, then
workflow would be started once the budget document status is set to 'Preposted'. In addition, workflow
for GM budgeting can be implemented for each lifecycle status. Thus approval could be required for
Budget documents involving grants with a Lifecyclestatus Application and Award,but not for the
Proposal. Thus, budget documents involving grants in the Proposal stage would not require approval, but
once the grant master record is updated to Application or Award, budget documents would require
approval by the user's manager.
Technically, workflow for GM budgeting uses budget document status, the grant lifecycle status, and the
responsibility types recorded in the Grant master record as the business objects. Next, workflow is
triggered when the budget document status is set to 'Preposted' (the event). Together, these elements are
used to support workflow for GM budgeting.
23.4 PSM-FG
Functions for US Federal Government
23.4.1 US Federal Agencies' Centralized Trial Balance System I (Changed)

Use
The US Federal Agencies' Centralized Trial Balance System I (FACTS I) feature has been developed for
use by US Federal Government agencies. It is a system maintained by the Financial Management System
Service of the US Treasury.
Agencies must electronically transmit preclosing Adjusted Trial Balances (ATBs) at the Treasury
______________________________________________________________
SAP AG
53
SAP System
______________________________________________________________
appropriation/fund group level using proprietary U.S. Government Standard General Ledger (SGL)
accounts.
FACTS I processing consists of the following programs:
o
FACTS I Transaction Register
FACTS I Trial Balance report
FACTS I Send Bulk File to Treasury
As of SAP R/3 Enterprise Public Services 2.0, all the programs for FACTS I have been redesigned. The
selection and ALV screens have been modified.
o
The FACTS I Transaction Register should be run using transaction FMFG_E_TRANS_REG. This
newly created report (program RFFMFG_TRANS_REG) replaces the old report
(RFMUSFG_FACTS1_TR) run by transaction RFACTS1_TR. This report can display the
transaciton registers of ledgers 95, 96, and 97. You can maintain the different views on the ledgers
by preconfiguring ledger-specific reporting layouts.
FACTS I Trial Balance - The trading partner field has been added to thetarget list of fields for the
FACTS attribute derivation. In addition, fields for funds center and funded program have been
added to the ALV list.
FACTS I Send Bulk File to Treasury - Additional selection criteria in the Federal Department and
Business Line fields.
23.4.2 US Federal Agencies' Centralized Trial Balance System II (Changed)

Use
The US Federal Agencies' Centralized Trial Balance System II (FACTS II) feature has been developed
for use by US Federal Government agencies. It is a system maintained by the Financial Management
System Service of the US Treasury. Agencies are required to report quarterly their U.S. Standard General
Ledger (SGL) budgetary account trial balances and selected proprietary account balances to Treasury
using this system. FACTS II subjects the balances to a series of edits which have been replicated in the
R/3 environment. The edits test for proper account attributes and relationships. SF-133 and TFS-2108
reports have now been replaced by the data reported to the FACTS II system.
FACTS II processing consists of the following steps:
1.
Extract data from the ledger or run the extract.
2.
Upload the Master Accounts File (MAF) from Treasury and maintain it.
3.
Run the edits. If there are any errors, post adjusting transactions. Return to step 1 and continue.
4.
Maintain footnotes.
5.
Send data (consisting of the edited data and footnotes) to Treasury.
6.
Reporting
Note that the order of steps 1 and 2 can be interchanged and so can the order of steps 3 and 4. The rest
must be carried out in the order in which they are listed.
______________________________________________________________
SAP AG
54
SAP System
______________________________________________________________
Functionality exists in IS-PS 4.62 for FACTS II. However, it is designed to meet the FY 2001
requirements and does not handle all of the possible data configurations, such as many funds referring to
a single application of funds. Treasury has issued new requirements for reporting data in FY 2002 .
As of SAP R/3 Enterprise Public Services 2.0, the programs have been redesigned to include FY 2002
requirements.
Changes to attributes:
o
Transfer Agency. Two-digit code. Every valid Department Code is a valid value for this field.
Treasury will validate against edit tables.
Transfer Account. Four-digit code. Every 4-digit main account that is valid for a given Department
is a valid value for this field. Treasury will validate against edit tables.
Advance Flag. One character field. Values are P (Advanced in Prior Year), F (Advanced from
Future Year) and X (Not applicable) and space. This can be derived using a combination of SGL
account and fund.
Defense Indicator. Values: DEF (Defense) or NND (Non-defense) or space. In most agencies, this
can be derived using SGL account.
Year of Budget Authority. NEW (to track outlays from new budget authority) or BAL (to track
outlays from balances brought forward from a previous year) or space. This attribute is associated
with all budgetary accounts that represent outgoing payments for no-year funds.
Authority Type. New values in addition to existing: D for Advance Appropriation; L for Proceeds of
Loan Asset Sales with Recourse, R for Re-appropriaiton.
BEA Category Indicator. New value in addition to existing: E for Emergency.
Borrow Source. New value in addition to existing: F for Federal Financing Bank.
Transaction Partner. New values and definitions replace the old ones:
E for Non-federal exceptions
F for Federal
X for Non-Federal
Changes to Input Fields

-
Legislation (LEGIS) field from the header of FM budget documents. This field is no longer
used as of FY 2002. However, it is still included in the bulk file sent to Treasury, but
blank-filled.
Non-zero values in the field COHORT are used only if the agency manages loan programs.
Cohort should be added by extending the FI coding block using existing techniques . This
would make cohort available on FI, MM, and other such transactions.
Changes made to FACTS II programs:

-
FACTS II Trial Balance - The field LEGIS removed from report and the following fields were
added Transfer Agency, Transfer Account, Year of Budget Authority, Advance Flag, and
Defense Indicator.
FACTS II Extract - The format of the bulk file, which is the ultimate output of the SAP
FACTS II process changed.
______________________________________________________________
SAP AG
55
SAP System
______________________________________________________________
The program no longer hard codes the apportionment category B detail field to be 001 if the
apportionment flag on the record equals #B# and 000 otherwise. The program has been
updated to accommodate multiple category B apportionments (each in a separate fund) within
a single TAFS, which would require the detail field to be 001, 002, and so on. If the funds
apportionment category is B, the first 25 characters of the fund Description field are placed in
the Apportionment Category B Text field of the FACTS II Bulk Extract File for those accounts
that report apportionment category B. In addition, a new BAdI iFMFG_FACTS2_CATB' has
been added to allow users to specify the detail number and text for each fund. (The system
defaults to 001 for this field for accounts that require a value in it.)
Originally, the data extract was written so that the fund code had to be the same as the
application of funds code. This has since been changed so that they can have different values.
Other changes were made to handle having multiple funds associated with a single application
of funds.
-
FACTS II - Upload MAF File - The format of the MAF file, which is an input file that comes
from Treasury and is used in editing, was updated. The program to upload was also updated to
accomodate changes.
FACTS II Edits - An attribute edit and Edit 10 Canceled Authority have been added to the
program. In addition, Preparer ID and Application of Funds were added to the selection screen.
The resultant list has been changed to allow easier analysis of the edits that have passed or
failed.
FACTS II Footnote - Function added to enable you to know on the front screen whether or not
a footnote has been entered for a particular account detail record.
The FACTS II Transaction Register should be run using transaction FMFG_E_TRANS_REG.

This newly created report (program RFFMFG_TRANS_REG) replaces the old report
(RFMUSFG_FACTS2_TB) run by transaction RFACTS2_TR. This report can display the
transaction registers of ledgers 95, 96 and 97. You can maintain the different views on the
ledgers by preconfiguring ledger-specific reporting layouts.
FACTS II Trial Balance - The following fields were added to the ALV list: trading partner,
profit center, BL status, subkey, funds center, funcded program, transfer agency, transfer
account, year of budget authority, advanced flag, and defense indicator.
Additional customizing required as a result of these changes: you must configure Edit 10 and the attribute
edit.
23.4.3 Automatic Budget Postings (New)

Use
The US Government Standard General Ledger (SGL) defines the accounting transactions that federal
agencies must use. Many of the specified transactions must, in turn, automatically generate a budget
transaction. As of SAP R/3 Enterprise Public Services 2.0, the Federal Government solution includes an
Automatic Budget Postings (ABP) feature developed to satisfy this requirement.
ABP automatically posts budget transactions in the Budget Control System (BCS). The generated budget
transactions can be either budget transfers (most commonly used) or budget entry transactions.
______________________________________________________________
SAP AG
56
SAP System
______________________________________________________________
Derivation rules are used to specify which transactions are relevant for ABP (for example, sales orders,
customer invoices, incoming payments) and what the values should be for the sender and receiver lines of
the budget transaction. You can specify default values for fields on the budget document header using a
configuration screen. If default header values do not satisfy your requirements, you can use a Business
Add-In (BAdI) to override the values.
For federal agencies, ABP is expected to replace the old functionality of Revenues Increasing the Budget
(RIB).
Automatic Budget Postings (ABP) requires the following customizing activities:
o
Activate Automatic Budget Postings
Define Budget Entry Document Header Defaults
Maintain Derivation Rules
Additionally, you may wish to override header default values by using the following Business Add-In:
o
Override Default Budget Entry Document Header Values
23.4.4 Changes to the Federal Government IMG (Changed)

Use
As of SAP R/3 Enterprise Public Services 2.0, the Implementation Guide (IMG) for the US Federal
Government solution has been restructured.
o
A General Settings node has been added, containing the following functions:
-
Activate Federal Government Functionality
Maintain SGL Account Master Table
Maintain Derivations for SGL Attributes
An Automatic Budget Postings (ABP) node has been added. It contains the following functions:
-
Activate Automatic Budget Postings
Define Budget Entry Document Header Defaults
Derivation
Here you can either define derivations for ABP across the board or define just the rules to be
used for such derivations.
A Payment Processing node has been added. The following nodes, which existed in the previous
IMG, have been moved and are subnodes to this new node:
-
Prompt Payment Act
Treasury Confirmation
______________________________________________________________
SAP AG
57
SAP System
______________________________________________________________
Payment Statisticial Sampling
A new subnode has also been added, for Intragovernmental Payments and Collections
(IPAC)
An Integration node has been added, with the following subnodes:

-
Asset Management
The Accountable Property functions now appear in this subnode.
Materials Management
The function for document-to-document tolerances now appears here.
Sales and Distribution

-
The new Reimbursable Orders function is customized here.
A new node has been added, called Ledgers. Many of its functions previously appeared under
"Actual and Commitment Update/Integration" in the Funds Management Government IMG. It is
structured as follows:
-
Former Budgetary Ledger

- Define Document Types
- Define Posting Key
- Define Account Determination for US Government
Budgetary Ledger (BCS)

Basic Settings
- Activate Budgetary Ledger Variant
- BL Account Classification
- Define Posting Key
- Maintain Budget Type Attributes
Account Derivation
- Definition of BL Areas
- Federal Extension Derivation Access
A new node has been added, called Reconciliation. It contains the following customizing steps:
-
Define Reconciliation Data Slice
Define Reconciliation Rule
A new node has been added, called Closing Operations, which previously appeared as "US Federal
Govt: Preliminary Closing" under Closing Operations in the Funds Management Government IMG.
It is structured as follows:
-
Preclosing (BCS/New Budgetary Ledger)

Collected Fields Year-End
Year-End Closing Rules
Year-End Account Assignment Derivation
Preclosing (Former Budgetary Ledger)

Define Rules for Closing Commitments
Define Rules for Budget Rollup with Fund
Define Rules for Budget Rollup with Fund Type
Define Rules for Closing Residual Accounts
______________________________________________________________
SAP AG
58
SAP System
______________________________________________________________
A new node has been added, called Reporting, which previously appeared in the Information
System node of the Funds Management Government IMG. It contains the following:
- FACTS II Edits and Pre-Edits
- SF-224 Treasury Subclass Codes Maintenance and Assignments
See also
Changes to Federal Government Menu
23.4.5 Intragovernmental Payments and Collections (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, the Federal Government solution includes functions for
handling intragovernmental payments collections. The function is usually known by its acronym, IPAC.
IPAC requires the customizing steps shown below:
o
Maintain Payment Office
Maintain Agency Location Code
Maintain Fiscal Station Number
Maintain IPAC Document Reference Number
Prepare Automatic Posting for IPAC
Maintain DIT and FBT Accounts
There is also a Business Add-In (BAdIs) you can use to vary the standard code if required:
Override IPAC Standard Code
23.4.6 Changes to Federal Government Menu (new and changed)

Use
As of SAP R/3 Enterprise Public Services 2.0, the structure of the Federal Government Easy Access menu
has changed.
The following nodes and functions have been added to the menu "Functions for US Federal
Government":
o
A new Payment Processing node has been added, with the following subnodes:
-
Treasury Confirmation
Execute Treasury Confirmation
______________________________________________________________
SAP AG
59
SAP System
______________________________________________________________
GOALS Import
Reverse Entire Check Run
Reverse Check
Payment Statistical Sampling

Process in Batch
Certification
Reporting
Treasury Offset
IPAC
Outgoing Payments and Collections
Send Upload to Treasury
IPAC Confirmation
Incoming Payments and Collections
Receive Download File
A new Integration node has been added, containing the following:

-
A new Asset Management subnode with the following functions:

Accountable Properties
A new Materials Management subnode with the following functions:

Post Parked Purchase Requisitions
Post Parked Purchase Orders
Closing Operations and Closing Rules

-
Preclosing
Reconciliation
-
Reconciliation Analysis Report

Use this function to reconcile balances.
Reconciliation Rules Check

Use this function to evaluate rules per specified default breakdown fields and to determine
whether any nodes are out of balance.
Information System
This node contains the reports that previously appeared in "Additional Functions US
Government" under Funds Management -> Information System. It includes the reports for
FACTS I and FACTS II.
A new Environment node has been added, containing the following:

-
Federal Extension Derivation Data
Display US Federal Derivation Data

See also
Changes to the Federal Government Implementation Guide
______________________________________________________________
SAP AG
60
SAP System
______________________________________________________________
23.4.7 Federal Government Reconciliation Tool (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, the Federal Government solution includes a reconciliation
function. This enables you to compare values between two components to ensure that they match.
o
You first define reconciliation rules, as equations with operands.
Regular reconciliations can be scheduled in batch processing.
Drilldown and item matching features are available to help you identify and analyze items that do
not match.
Customizing comprises the following steps, which appear under Reconciliation in the Functions for US
Federal Government Implementation Guide:
Define Reconciliation Data Slice
Define Reconciliation Rule
23.4.8 SF-224 Statement of Transactions (Changed)

Use
As of SAP R/3 Enterprise Public Services 2.0 the Federal Government solution SF-224 feature has been
enhanced.
The SF-224, Statement of Transactions, is a monthly report required by Treasury. It has a format
specified by Treasury. It is prepared by agencies for whom the Treasury Financial Management Service
(FMS) makes payments at any of its regional financial centers. The report shows disbursements,
collections, and receipts, organized in three sections.
It uses data that comes from transactions that impact SGL accounts 1010, Fund Balance with Treasury,
and 1110, Undeposited Collections. These include Treasury payment confirmations, IPAC collections
and payments, and manual collections and payments. There are a few transactions that hit 1010 that are
not included, such as appropriation warrants and a very limited number of payments. The balances as of
the beginning of the month and end of the month for SGL account 1110 are also included in the report.
The original report, written using Report Painter, has been replaced. The new report can:
o
Report activities that come from prior months but were posted in the current month
Handle undeposited collections properly
Handle Treasury Symbol subclasses
Produce an electronic file in the format specified by Treasury (GOALS II FMS 224 Bulk Layouts)
The SF-224 Statement of Transactions report requires the following customizing activities:
______________________________________________________________
SAP AG
61
SAP System
______________________________________________________________
Maintain Treasury Subclasses
Assign FI Document Type, Account and Fund to Treasury Subclass Code
23.4.9 Federal Government: Treasury Offset (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, the Federal Government solution includes a new function,
designed to enable government agencies to mark records with a Treasury Offset Status and create a file
for Treasury with records eligile for offset.
The following statuses are available:
o
Eligible for Offset #

The document meets requirements for offset and should be included in the next transmission to
Treasury.
Eligible for Offset, Under Investigation #

That the document has been flagged, but should not be picked in the next Treasury
transmission (investigation needs to be completed).
Referred to Treasury, Uncollected #

Document was already picked up and transmitted to Treasury. It should be excluded from
further files.
Referred to Treasury, Collected #

Treasury was able to recover the money and send it to the agency (using OPAC).
At the time of customer invoice creation/parking, a new Treasury Offset Field has been provided that
enables you to display the Treasury Offset Status.
See also
The customer BAdI, RFFMFG_TREA_OFFSET, which allows you to define the date used in the ageing
calculation and set up the Treasury Offset File Format.
23.4.10 US Federal Government: Financial Statements (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, the US Federal Government solution includes the
Financial Statements. The Financial Statements for the Federal Government, which are commonly
referred by as Federal Government Form & Content, are described in Bulletins from:
o
Office of Management and Budgeting - OMB
Joint Financial Management Improvement Program -JFMIP
Treasury within the USSGL Section.
Each of them publishes the bulletins on their website. Each financial statements is defined using a
______________________________________________________________
SAP AG
62
SAP System
______________________________________________________________
crosswalk which maps the USSGL accounts to the reporting figures. The following financial statements
are required by US Federal Government agencies and available as R/3 information system reports:
o
Balance Sheet
Statement of Net Cost
Statement of Changes in Net Positions
Statement of Financing
Statement of Custodial Activities
Statement of Budgetary Resources
SF 132 - Apportionment and Reapportionment Schedule*
SF 133 - Report on Budget Execution and Budgetary Resources*
SF 224 - Statement of Transactions*

Note: Items marked * appear in the Other section of the Information System node in the
Federal Government menu.
All US Federal Government reports take information out of the following different available ledgers:
o
95 Ledger with breakdown by R/3 Organizational Financial objects
96 Ledger with breakdown by FACTS I
97 Ledger with breakdown by FACTS II
For the purpose of creating financial reports, these ledgers are available inside the Report Writer R/3
reporting tool or in reports specifically addressing the reporting requirements. Documentation can be
found attached to the report itself.
Note: From SAP R/3 Enterprise Public Services 2.0 onward, Public Services also supports the Business
Information Warehouse (BW) as a reporting system. This reporting systems contains a variety of
reporting-specific tools and is geared towards flexible customer reporting.
23.4.11 PSM-FG-PP
US Prompt Payment Act
23.4.11.1 US Federal Government: Automatic Invoice Release on Goods

Receipt (New
Use
As of SAP R/3 Enterprise Public Services 2.0, the Federal Government solution includes a feature for
automatic invoice release on goods receipt. In a normal procurement cycle, a purchase order is followed
by a goods receipt (and/or acceptance) which in turn is followed by an invoice receipt (in logistics
invoice verification). Sometimes, however, the goods receipt may occur after the invoice receipt or there
may be partial goods receipt before the invoice comes in. In both cases (if you have customized your
tolerances in Materials Management appropriately), the invoice is blocked. It is necessary to run the
invoice release report (transaction MRBR) in order to release invoices when all the goods are received or
the quantity of goods that is required to satisfy the Material Management tolerances is received.
______________________________________________________________
SAP AG
63
SAP System
______________________________________________________________
The new solution reduces the incovenience of having to run this extra step by automating the invoice
release. This is done at goods receipt time and happens in the background. If a certain goods receipt
fulfills the conditions set out in the tolerances and the quantity in the invoice, the automatic invoice
release is process is triggered in the background. When the goods receipt is posted, the corresponding
invoice (which had an invoice verification block) is now automatically released. Since the financial (FI)
invoice document is also released automatically, this invoice is now ready for payment clearing.
Note that this solution does not replace the existing invoice release report. The report is comprehensive in
scope and caters to different kinds of blocks. The automatic release solution handles only the invoice
verification block.
23.4.11.2 Federal Government: Accounts Receivable Classification (New)

Use
that enables government agencies to classify accounts receivable (A/R) invoice. The "Status of Accounts
Receivable" pushbutton is now visible on A/R invoices. This is the default: there is now a BAdI you can
use to change the text. A pop-up panel is displayed when the pushbutton is selected.
Only document types for customer invoices are displayed in the pop-up panel. You can classify invoices
by using one or more reason codes already configured.
The classification information has no impact on invoice processing calculations and is only stored for
view on the invoice screens and later reporting.
For those customers who have already implemented the Improper Invoice function, entries will already
exist in the IMG table.
Transaction FMFG_IMPROP_REASONS invokes the customizing table. Enter document types for
customer invoices, two-character identifier for each reason you want to create and descriptive text up to
50 characters for each new reason.
See also
The Prompt Payment Act (PPA) feature must be installed, configured, and active before you can use the
A/R classification function. For details of the configuration work, see the PPA documentation in the
Implementation Guide.
23.4.11.3 Federal Government: Economic Justification (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, the Prompt Payment Act (PPA) feature in the US Federal
Government solution has been revised to reflect changes in the regulations.
______________________________________________________________
SAP AG
64
SAP System
______________________________________________________________
For discounts offered by the vendor, agencies must decide if it is more economical to pay early (accept
the discount) or pay on the normal PPA payment due date (reject the discount). The same holds true for
rebates offered by purchase card issuers. Agencies must decide if it is more economical to pay early
(accept the rebate) or pay on the normal PPA payment due date (reject the rebate).
Agencies are required to determine purchase card payment dates based on on analysis of total costs and
total benefits to the Federal government. When calculating costs and benefits, agencies are expected to
include the cost to the government of paying early. This cost is the interest the government would have
earned based on the Current Value of Funds Rate (CVFR).
The revised Prompt Payment regulation requires agencies to determine government-wide commercial
purchase card payment dates based on an analysis of the total benefits to the Federal government as a
whole. Specifically, agencies are required to compare daily basis points offered by the card issuer with
the corresponding daily basis points of the CVFR. If the basis points offered by the card issuer are greater
than the daily basis points of the CVFR, the government will maximize savings by paying at the earliest
date. If the basis points offered by the card issuer are less than the daily basis points of the CVFR, the
government minimizes costs by paying on the Prompt Payment due date or the date specified in the
contract.
Agencies use a formula to calculate whether to pay early or on the normal Prompt Payment due date. The
CVFR daily basis points are compared with daily basis points offered by the card issuer to determine
economic justification. The following formula is used to calculate the average daily basis points of the
CVFR:
(CVFR/360)* 100
Agencies must then compare this CVFR daily basis points to the daily basis points offered by the card
issuer. To obtain daily basis points offered by the card issuer, agencies may refer to their contract with
the card issuer.
Example:
Card Issuer daily basis points = 1.5 basis points
CVFR = 6%
CVFR daily basis points = 1.67 based on the following calculation:
(.06/360) * 100 = 1.67

At a CVFR of 6%, the daily basis points of the CVFR are 1.67 basis points. The government earns 1.67
basis points for each day it delays paying the card issuer. Since 1.67 is greater than 1.5 offered by the
card issuer, the agency should pay as close to the payment due date as possible so the Government
continues to earn interest on its funds. However, if the basis points offered by the card issuer are more
than the daily basis points of the current value of funds, the government should pay as early as possible to
maximize savings.
Users can set a value for the daily basis points in the company-code-specific vendor master data
(transaction XK02). When this information is saved, there is an algorithm for economic justification that
runs in the background and determines whether the vendor basis points are more than the converted daily
basis points valid for this time period. The latter is obtained from the configuration for interest rates
(transaction OFIR) where you can enter the CVFR, which is then converted to the daily basis points. If
the vendor basis points are more than the daily basis points, the vendor will have to pay immediately and
therefore the vendor will have a new payment term (purchase card payment term if you have configured
one). On the other hand if the daily basis points are more than the vendor basis points, the old vendor
payment term remains unchanged. If there was no default payment term to begin with, a new default
______________________________________________________________
SAP AG
65
SAP System
______________________________________________________________
payment term (if configured) is entered as the vendor master default.

The functionality is also triggered when you have to make a change to anexisting value of the CVFR
(transaction OFIR). Such changes should be avoided and should be resorted to only when absolutely
necessary. Whenever such a change takes place, the same comparison algorithm is run in the background
for all vendors that would be affected by it and, if required, the current payment term is replaced with the
purchase card payment term or the purchase card payment term is replaced by a default payment term (if
you have configured this).
The US Federal Government pushbutton is visible on all the vendor master screens. Whenever you click
on this pushbutton, a new screen is displayed with two new (tabstrips) subscreens.
Selection of the US Federal Government tabstrip displays a screen allowing entry to fields 'Agency
Location Code' and 'Payment Office'.
Selection of the Purchase Card Information tabstrip displays a screen allowing entries in the basis points
field.
Existing Transaction OFIR allows you o use view V_T023R to assign the interest indicator (whether the
penalty interest or the CVFR), the start validity date of an interest rate and the interest rate. In the case of
interest penalties, the corresponding indicator must be selected and the interest rate is that for penalties.
When the data entered is saved, the respective fields in table T023R are updated.
23.4.11.4 Federal Government: Exclude Invoice (New)

Use
that enables government agencies to have the system skip over an entire invoice in Prompt Payment Act
(PPA) processing.
o
The invoice header includes a new checkbox. Check this to allow the relevant invoice to be
excluded. The indicator is only visible on accounts payable (A/P) invoices.
There is a new report you can use to exclude specific line items from Prompat Payment Act penalty
calculations.
Standard PPA customizing required. No other customizing required.
23.4.11.5 Federal Government: Improper Invoices (Changed)

Use
As of SAP R/3 Enterprise Public Services 2.0, the Federal Government solution includes a BAdI that you
______________________________________________________________
SAP AG
66
SAP System
______________________________________________________________
can use to change the delivered pushbutton text from "Required Information on Invoice" to a text of your
choice, such as "Improper Invoices".
A/P classification function also uses transaction FMFG_IMPROP_REASONS to invoke the customizing
table.
See also
o
Treasury Offset
A/R Invoice Classification
PPA Customer BAdI
23.4.11.6 Federal Government: Interest Penalty Reason Code (New)

Use
designed to enable government agencies to assign the interest penalty reason code online. On the Details
tab at the header level of an invoice, a new field has been provided that enables the user to record the
"Reason for delay".
As in previous releases, you can assign each invoice document with penalties a reason code, identifying
the reason why the document was paid late. Now you can include uncleared or cleared invoices with or
without penalties.
Standard Prompt Payment Act (PPA) customizing required.
In addition, you can maintain reason codes that identify the reason for late payment (with penalties).
See also
23.5 PSM-FA
Fund Accounting
23.5.1 Fund Accounting: Fund Message Derivation Tool (New)

Use
As of SAP R/3 Enterprise Public Services 2.0, the Fund Accounting solution includes a highly flexible
fund message derivation tool that can be customized to meet user needs. You do this using an application
of the derivation tool to set up certain rules. These rules need to be created in response to the following
______________________________________________________________
SAP AG
67
SAP System
______________________________________________________________
conditions/situations/requirements:
o
Minimally, when posting previously unrecorded obligations (funds commitments, purchase orders,
down payments) to current year general ledger (G/L) obligation accounts, the system outputs an
error or warning message as customized. An example of this is the posting of such documents to an
expired fund. In this case, you might want the system to display a warning message.
A similar error message when posting against cancelled funds. The error message should be
customizable by fund status (current, expired, cancelled). An example of this is a hard error when
posting to a cancelled fund.
An error/warning message based on the amount type
Message derivation based on value type. For example, a hard error when creating a PO, but no
message when creating a goods receipt
Message derivation by message type, based on user ID or the authorization group to which the user
is assigned. An example of this is customizing in order for a data entry clerk to receive an error
message while the supervisor receives only a warning.
Message derivation extension to include other objects like the G/L account, commitment item, and
funds center
When this tool is properly customized, every document that satisfies allthe conditions in the fund
message derivation tool is checked both during both the "check" and the "post" phases.
The following are the steps you need to carry out in order to customize this solution:
1.
Create user groups for fund messages (transaction OFGR): In this transaction, you create user
groups (examples: clerk, supervisor)
2.
Set up rules in the fund message derivation tool (transaction FMSGDERIVE): In this transaction,
you set up the rules discussed above.
______________________________________________________________
SAP AG
68

Chap 23 PSM

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chap 23 PSM

Uploaded by

Copyright:

Available Formats

PSM Public Sector Management

SAP R/3 Enterprise

Copyright 2003 SAP AG. All rights reserved.

are registered trademarks of Informix Software

PSM Public Sector Management

PSM-FM-BCS-AC Availability Control

Assigning Commitment Items to Revenue Types (New)

PSM-FG-PP US Prompt Payment Act

Public Sector Management

23.1 Assigning Controlling Areas to FM Areas (deleted)

A controlling area that is integrated in Funds Management by the assignment of FM area to

23.2.1 Multi-Year Budget (new)

23.2.2 Federal Government: Classification of Customer Invoices (New)

23.2.3 General budgetary ledger (new)

23.2.4 Changes to IMG Structures in Funds Managements

Define Carryforward Parameters

Assign Carryforward Parameter for Commitment Carryforward

Copy Account Assignment Assignment (PCO: Function now in the menu)

New IMG Activities Added

BAdI: Define Checks for Budget Structure Plan

Under the node Subdivision of Master Data

BAdI: Check Subdivision ID

BAdI: Check Substrings

Define Derivation Strategy for Reassignment

BAdI: Enhanced Functions for Derivation Strategy

Budget Control System (BCS)

Define Revenue Commitment Items as Posting Objects

BAdI: Edit Text Variables in Budget Memos

Change GUI Status of Requests

BAdI: Enhance Derivation of G/L Account

Define Processing Status

Public-Owned Commercial Operations

BAdI: Derive CO Account Assignment for Correction Documents

BAdI: Definition of Expiry Month

BAdI: Update Debits/Actual

Define Basic Settings for Commitment Carryforward

BAdI: Control of Reassignment

BAdI: Enhance Document Journal

BAdI: Activate Authorizations for FI Accounts

Compare Key Figures

Unnamed IMG Activities

Assign FM Area Strategy for the Reassignment of Commitment Items in Assign

Restructured IMG Activities

23.2.5.1 New BAdIs for FM Master Data

Check Subdivision ID entered in table FMMDSTRID

This BAdI contains one method:

Account assignment element

Master data subdivision ID

BAdI for initial substring value checking

This BAdI contains thirteen methods:

Master data subdivision ID

Master data substring value

Master data substring length

There are two examples of implementation of this BAdI:

If the check results in an error, an error message is displayed.

BAdI for subdivision parameters used at master data creation

This BAdI contains four methods:

Documentation on BAdI method for commitment item

Documentation on BAdI method for funds center

Documentation on BAdI method for fund

Documentation on BAdI method for functional area

23.2.5.2 Automatic Generation of Cover Pools (enhanced)

23.2.5.3 Additional Checks when Saving the Budget Structure (new)