Hierarchy
⤷ PSM-FM-MD (Application Component) Master Data
⤷ FMCC (Package) FIFM: Cash budget management customizing
IMG Activity
ID | _ISPSFM_N_FMAVCDERIA | Define Derivation Strategy for Control Objects |
Transaction Code | S_KI4_38000329 | (empty) |
Created on | 20001114 | |
Customizing Attributes | _ISPSFM_N_FMAVCDERIA | Define Account Assignment Derivation of Availability Control Objects |
Customizing Activity | _ISPSFM_N_FMAVCDERIA | Define Account Assignment Derivation of Availability Control Objects |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | _ISPSFM_N_FMAVCDERIA |
Note:
The settings affected here are exclusively reserved for the use of the Budget Control System (BCS).
Use
In this IMG activity, you can define your own strategies for deriving Funds Management account assignments (FM account assignments) for availability control.
Each FM account assignment in which you create budget or to which you post budget consumption is assigned an account assignment in the availability control ledger. In this IMG activity, you define the logic on how the account assignments of the availability control ledger (availability control object) should derive the budget addresses and posting addresses.
One and two-step derivation of control object
The derivation strategy that you define in this IMG activity controls the assignment of the control object to one or more budget addresses. For a budget posting, the corresponding control object is determined on the basis of this derivation strategy. Budget postings are updated in the AVC in a single step. In comparison, actual/commitment postings are updated in two steps in the AVC, using two consecutive derivation strategies. First the corresponding budget address is determined from the posting address - this occurs with the derivation strategy of the budget structure (IMG activity Define Derivation Strategy for Budget Addresses). The control object is then derived from the respective budget address in the same way as the budget posting.
The derivation strategy for availability control objects consists of a sequence of steps that uses one of the following derivation step types:
- Clear
In the "clear" derivation step type, you can define whether you want to exclude individual FM account assignment elements from the availability control ledger. - Move
In the "move" derivation step type, you can determine whether the values for the individual FM account assignment elements of your postings should be carried forward partially or in full to the account assignment elements of the ledger. - Derivation rule
In the "derivation rule" step, you can directly enter the assignment of the FM account assignments of your postings to the ledger account assignments. - Table Lookup
In the step "table access", you can access individual records from database tables. - Function Module
In the step "function module", you can call function modules that allow you to search for account assignment elements in master data hierarchies or to determine master data attributes, for example.
All derivation steps defined here can be linked to requirements which must be met before the derivation step can be executed.
Example
You want to aggregate the budget for consumed amounts in the AVC ledger in the following way when entering budget values:
Posting to account assignments Acct assgmts in AVC ledger
Fund/Funds center/Commitment item Fund/Funds center/Commitment item
Move
FND1/FC1/CI1 -> FND1/FC1/CI
FND1/FC1/CI2 -> FND1/FC1/CI
FND1/FC1/CI3 -> FND1/FC1/CI
A possible derivation strategy in this case consists of three derivation steps which carry forward the values of the account assignment elements one after the other to the relevant account assignment elements in the ledger, the fund and funds center being carried forward in full, whereas only the first five characters of the commitment item are carried forward.
Requirements
The example makes clear that a suitable technical name is required for the FM account assignments when you use "move" steps for this type of summarization.
If you use descriptive names for your FM account assignments, there are function module steps available that carry out an evaluation during the derivation of master data hierarchies.
Standard settings
SAP provides standard strategy 9HSAP000, which contains examples of how to use different step types.
Note
If you do not need a summarization of budget values in one of your availability control ledgers, that is, if all control objects in this ledger match the Funds Management budget objects, then it is not necessary to to define your own strategy. In this case, leave the field Strategy for Derivation of Control Objects blank in the IMG activity Assign Tolerance Profiles and Strategy for Control Objects.
Recommendation
- Create your own strategy by copying the strategy 9HSAP000 delivered by SAP.
- Edit your strategy by adding more derivation steps.
- Save your strategy.
Further notes
If you change a strategy that is used by already active AVC ledgers, you must execute Re-Initialize Availability Control Ledgers (FM) for all these ledgers.
You start the reconstruction of availability control from the Funds Management menu under Budgeting -> Budget Control System (BCS) -> Tools -> Availability Control -> Reconstruction.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | _ISPSFM_N_FMAVCDERIA | 0 | ALN0000196 | Availability Control |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
VV_FMTABADRH_FMAVCDERIAO | V - View | SM30 | . |
History
Last changed by/on | SAP | 20030620 |
SAP Release Created in | 462 |