Use

This derivation strategy maps the account assignment determination for Funds Management, taking into account fiscal master data models.

If you use Funds Management integrated with other application components, the main question regarding account assignment determination in Funds Management is: How can you derive FM account assignment elements from CO account assignments?

This question is relevant because FM account assignment elements cannot be assigned to an account manually in all components. This mainly affects commitment items. The commitment item is the central account assignment element in Funds Management for German local authorities as it contains both content and organizational information. You cannot enter the commitment item in the component Human Resources (HR). In this case, they must be derived from CO account assignments.

The account assignment components of the commitment item Unit/Grouping, Title/grouping and sub-account are only included in Funds Management. From an integration point of view, it is necessary to derive this information from CO account assignment elements in order to find the “correct” commitment items for Funds Management.

Prerequisites

You must use the components for Cost Center Accounting and Project Controlling.

Specifications

Funds center and commitment item (grouping, sub-account) must always be derivable from a CO object (cost center and order) and G/L account or cost element. Accordingly, the CO objects cannot be defined separately from Funds Management.

In our example it is assumed that cost centers and orders are assigned to an account. If you also work with projects, you can proceed in the same way as with orders.

Purpose of the funds center

Budget planning with a funds center

In this scenario, the so-called funds center must be derived for the budget for technical reasons, for example “town”.

Budget planning with several funds centers

In this scenario, the funds center is used to map the management of the organization and therefore corresponds with the cost center. In this scenario, three cases need to be distinguished regarding account assignment derivation.

If the same exists for the cost center and the fund centers, the funds center can be derived from the cost center with derivation type “Move” .

If the cost centers have more detail than is required for Funds Management, the commitment items are on a summation level above the cost centers. In this case, only the names in a substring of the cost center are the same. The funds center can then be derived from the cost center using the derivation type “Move” which takes this substring into account.

If the names of the cost centers and fund centers are different, the funds center must be defined in a customer-defined field as an attribute in the cost center so that a derivation can take place.

Alternatively, you can create the corresponding derivation steps as a “derivation rule” if the names are different. Which of the two alternatives you use is at your discretion.

Structure of the commitment item as a budget object

According to §5 section 3 of local authority budget regulation, the commitment item as budget object has the following structure in our example.

In the table, the terms “Operating budget” and “Capital budget” were abbreviated withOBand CB respectively.Characteristic values are in commas.

The unit/grouping must be derivable from the CO objects. As a rule, there are more cost centers than units/groupings.

The unit/grouping must be derivable from the G/L accounts/cost elements. There must be a corresponding G/L account and cost element for each title or grouping.

Specifications: Customer-Defined Fields in CO Master Data

You must define customer-defined fields which should deliver the grouping in the master record of the CO objects and in the cost element. The fields must be flagged as required-entry fields.

You can create customer-defined fields for CO objects and cost elements by using the following enhancements delivered by SAP:

COOMKS01 Cost center: Customer-defined additional fields in the master record

COOPA003 Customer-defined fields in master order

CNEX0007 PS customer-specific fields WBS element

COOMKA01 Cost element: Customer-defined additional fields in the master record

You can find more information in the documentation on the enhancements.

You use enhancement SAPLFMDT which is provided by SAP for derivation. For more information on this enhancement, see Derivation Step Types

Specifications: Source Fields and Target Fields

To determine the account assignments relevant for Funds Management with your derivation strategy with the specifications above from the CO account assignments, you also require customer-defined work fields.

Work fields for distinguishing operating budget/capital budget (cost element)

Work fields for unit/grouping (cost center, order)

Work fields for title/grouping (cost element)

You must enhance the database structure FMDERIVE (in Include CI_FMDERIVE ) in order to enhance these customer-defined fields. The enhancement enables you to copy the required field content from CO master data fields to the corresponding work fields in the derivation strategy. You can then determine the “correct” commitment items and, if necessary, fund centers from the work fields in the next derivation steps, by copying the field content from the work fields to the correct place in the target field Commitment Item ( COMMIT_ITEM ) and, if necessary, fund center (FUND_CENTER).

Whether a posting affects the capital or operational budget depends on the derivation via the order type in our example. The capital budget is affected if an assignment is made on an investment order (order type > or = 1000), the operational budget is affected if an assignment is made on a cost center or internal order (order type < 1000). The definition of values for the order type is voluntary in this example and can be adjusted to suit your own requirements.

In our example, reference is only made to grouping. The specifications also apply to unit and title.

Specification Work Fields: Derivation Strategy

The derivation strategy is created with the following customer-defined work fields.

For an example of the values of the work fields for grouping, see Example Customer-Defined Cost Element Fields

Derivation Strategy

How the funds center is used in your organization is decisive in the determination of the funds center in the first derivation step.. For this reason, the following depicts three different steps which depend on how the funds center is used.

Step 01a – Setting the funds center from a constant (budget planning with a funds center)

Derivation Type Move

In this step, you derive the funds center from a constant. You can use this step if you execute budget planning with a funds center as described above. The constant corresponds to the funds center defined for the budget in Customizing.

Step 01b – Determining funds center from cost center (when names are the same and several fund centers)

Derivation Type Move

In this step, you derive the funds center from a cost center. You can use this step if you execute budget planning with several funds center as described above.

Step 01c Copying the funds center customer-defined field for cost center or for order (when name is the same and several fund centers)

In this case, you do not need a special step, you can use step 07 to determine the funds center

Step 02 Determining the commitment item (special cases) from cost center, cost element and special G/L indicator

Step type derivation rule

In this derivation step, you can derive those commitment items (special cases) that could not be determined through the following derivation steps. Note that the number of these “special cases” should be kept small in order to minimize manual maintenance of rule entries.

The rule entries are saved in a table. You can maintain them with a validity date.

Step 03 – Determining the indicator for operational budget from cost center

Derivation Type Move

This step determines whether the posting affects the operational budget. With a posting on a cost center, the customer-defined field Indicator Operational/Capital Budget is filled with constant “O” (operational budget). This information is used in step 08 to define the first item of the commitment item.

Step 04 – Determining the order type and unit/grouping from the order

Derivation type table access

This step determines the order type and the grouping using a table access to table ORTY and copies these to the customer-defined fields Order Type and Grouping Order . The order type is used to define whether a posting affects the OB or the CB with an account assignment on an order in step 05. The grouping is used to define the grouping (item 2-4) of the commitment item in step 011.

Step 05 – Determining the indicator for operational budget from order type

Derivation Type Move

This step determines whether the posting affects the operational budget. With a posting on an order with order type < 1000, the customer-defined field Indicator Operational/Capital Budget is filled with constant “O” (operational budget). This information is used in step 08 to define the first item of the commitment item.

Step 06 – Determining the indicator for capital budget from order type

Derivation Type Move

This step determines whether the posting affects the capital budget. With a posting on an order with order type < or = 1000, the customer-defined field Indicator Operational/Capital Budget is filled with constant “C” (capital budget). This information is used in step 09 to define the first item of the commitment item.

Step 07 – Copy values of master data fields in customer-defined work fields derivation type enhancement

This step copies the grouping from cost center and cost element to the corresponding customer-defined work fields and, if necessary, the funds center (see step 01C).

Step 08 – Define prefix digit (operating budget) of the commitment item

Derivation Type Move

This step defines the first item of the commitment item – prefix digit = 1 (operating budget).

Step 09 – Define prefix digit (capital budget) of the commitment item

Derivation Type Move

This step defines the first item of the commitment item – prefix digit = “2” (capital budget).

Step 10 - Define grouping of the commitment item from cost center

Derivation Type Move

This step defines item 2-4 (grouping) of the commitment item.

Step 11 - Define grouping of the commitment item from order

Derivation Type Move

This step defines item 2-4 (grouping) of the commitment item.

Step 12 – Define grouping for expenditures operating budget

Derivation Type Move

This step defines item 5-8 (grouping) of the commitment item.

Step 13 – Define grouping for revenues operating budget

Derivation Type Move

Define grouping for revenues operating budget

This step defines item 5-8 (grouping) of the commitment item.

Step 14 – Define grouping for expenditures capital budget

Derivation Type Move

This step defines item 5-8 (grouping) of the commitment item.

Step 15 Determine grouping for revenues capital budget

Derivation Type Move

This step defines item 5-8 (grouping) of the commitment item.

Step 16 – Commitment item from G/L account

Step type Function Module

Name of function module: FMDT_READ_MD_ACCOUNT_COMPANY

This derivation step derives the commitment item defined in the G/L account. Commitment items that have financial transaction other than 30 – for example commitment items with financial transaction 60 (receivables and payables) and 90 (check clearing and bank clearing) cannot be derived with the steps mentioned above. These must be assigned to the G/L accounts.

This function module is in the standard delivery. You can copy this step into your derivation strategy.