Live Rates Fund Determination
You use the report Live Rates Fund Determination
(RCRM_FM_LRTP_FUND_DETERMINE
) to identify the funds to post the calculated budget amounts
to and to create the combinations of account hierarchy node and product category used for the detailed planning selection.
When the system determines the funds for live rates planning elements, the system uses the funds plans and funds created in funds management.
You have activated the business function Claims and Funds Management (CRM_CF_1
).
You have defined the fund types that are used for live rates planning in Customizing for Define Fund Types
under .
You have completed the activities in Customizing under .
You have created the funds you are going to use for live rates planning in CRM WebClient under . The funds are in the appropriate status.
Your live rates plan has the status In Planning
or Approved
and the live rates planning elements have the status In High-Level Planning
, In Detailed Planning
, or Completed
Planning
.
To determine the funds, the system searches for applicable funds plans, fund types, and funds.
If you specify a funds plan, the system uses this funds plan, and verifies that its validity period is within the live rates plan validity period.
If you do not specify a funds plan, the system searches for a single funds plan that is applicable for the live rates plan.
To find an applicable funds plan, fund determination does the following:
Ensures the validity period of the live rates plan is within the validity period of the associated funds plan
Ensures no overlapping of validity dates between funds plans
A live rates plan only considers a single funds plan at a time. If more than one funds plan is found, the system produces an error.
Considers only those fund plans that are in status Released
or Locked
An applicable fund type for live rates must have one of the following fund attribute combinations:
Account hierarchy node and product category
Account hierarchy node and product
Account hierarchy node
Product category
Product
Territory
Note
If the territory attribute is used with any of the other fund attributes listed above, the system excludes the territory attribute, and only uses the other attributes to determine the fund.
Applicable funds must be in status Released
, Preliminary
, or Locked
.
If the fund attributes are any of the above combinations (except territory), the following applies:
The system searches for funds with attributes that coincide with the attributes in the live rates territory of a live rates planning element.
The fund attributes Account Hierarchy Node
, Product Category
and Product
must be between the Mid
and To
planning levels.
If the fund attribute is Territory
, the following applies:
The rule attributes for the territory must be set between the Mid Level
and To Level
planning levels of the rule attributes of the live rates territory of a live rates planning element.
The validity dates of the live rates territory must fall within the validity dates of the live rates plan.
If the only fund attribute is Product
, the system discards the fund if you are not performing live rates planning at product level.
The system determines funds with overlapping fund attributes in the following way:
If there is more than one fund with the same fund attributes and each fund has a different fund type, the system displays all of these funds.
If there is more than one fund with the same fund attributes and each fund has the same fund type, the system discards these funds.
If there is more than one fund with fund attributes that are related to each other because they have a parent-child relationship, the system discards these funds.
To determine the combinations of account hierarchy node and product category available for the detailed planning selection, fund determination verifies the following:
The account hierarchy node and product category assigned to the live rates territory
The Mid Level
defined in Customizing for the account hierarchy and product hierarchy used for live rates planning
The system displays each combination of account hierarchy node and product category in the Planning
assignment block.
You define the selection criteria and schedule the report Live Rates Fund Determination
(RCRM_FM_LRTP_FUND_DETERMINE
) to run as a background job from or from the Job Scheduler
(SM36
). For more information about the selection criteria, see the report documentation in the Job Scheduler
(SM36
). For more information
about scheduling background jobs, see Background Processing.
The following example illustrates how fund determination for live rates searches for applicable funds.
Only the accounts at the lowest level are shown here. The following table shows an account hierarchy that has three levels:
Level 0 |
Level 1 |
Level 2 |
Level 3 |
Account |
|---|---|---|---|---|
AHIERARCHY |
Head Office |
|||
North |
||||
North West |
||||
Store B |
||||
South |
||||
South West |
||||
Store A |
||||
South East |
||||
Store C |
Only the products assigned to categories at the lowest level are shown here. The following table shows a product hierarchy that has three levels:
Level 0 |
Level 1 |
Level 2 |
Level 3 |
Product |
|---|---|---|---|---|
PHIERARCHY |
Stationery |
|||
Pens |
||||
Ball Point Pens |
||||
Blue |
||||
Highlighters |
||||
Yellow |
||||
Paper |
||||
Letter |
||||
With Watermark |
The following table identifies the planning level values defined in Customizing for the account hierarchy and product hierarchy:
Planning Levels |
From Level |
Mid Level |
To Level |
Additional Information |
|---|---|---|---|---|
Account Hierarchy |
1 |
2 |
3 |
Planning at the account level is not supported. |
Product Hierarchy |
1 |
2 |
3 |
Planning at the product level is not performed. |
The following table identifies territories and their rule attributes:
Territory |
Rule Attribute: |
Rule Attribute: |
|---|---|---|
Live Rates Territory 1 |
Head Office |
Stationary |
Territory for Fund 1 |
North |
|
Territory for Fund 2 |
North |
Paper |
Territory for Fund 3 |
Head Office |
The followings table identifies funds and their fund attributes:
Fund |
Territory |
Account Hierarchy Node |
Account |
Product Category |
Product |
|---|---|---|---|---|---|
Fund 1 |
Territory for Fund 1 |
||||
Fund 2 |
Territory for Fund 2 |
||||
Fund 3 |
Territory for Fund 3 |
||||
Fund 4 |
Store A |
||||
Fund 5 |
Yellow |
||||
Fund 6 |
South |
Pens |
|||
Fund 7 |
Head Office |
Stationary |
|||
Fund 8 |
Paper |
||||
Fund 9 |
Letter |
The following table illustrates the results of fund determination for the live rates planning element for Live Rates Territory 1:
Fund |
Applicable for Live Rates Planning Element for Live Rates Territory 1 |
Explanation |
|---|---|---|
Fund 1 |
Yes |
The account hierarchy node in the territory used in the fund is between the |
Fund 2 |
Yes |
The account hierarchy node and product category of the territory used in the fund are between the |
Fund 3 |
No |
The account hierarchy node in the territory used in the fund is not between the |
Fund 4 |
No |
Planning at the account level is not supported. |
Fund 5 |
No |
Planning is not done at the product level. |
Fund 6 |
Yes |
The account hierarchy node and product category used in the fund are between the |
Fund 7 |
No |
The account hierarchy node and product category used in the fund are not between the |
Fund 8 |
No |
The product category used in Fund 8 is the parent of the product category used in Fund 9. Funds 8 and 9 have overlapping fund attributes. |
Fund 9 |
No |
The product category used in Fund 9 is a child of the product category used in Fund 8. Funds 8 and 9 have overlapping fund attributes. |