Settlement Rule 彭睿给的
1 General Introduction to Settlement
1.1 The General Purpose of Settlement
Settlement is always used for cost accounting on jobs. Typical jobs include marketing events such as trade fairs or the completion of a product for a special customer. In these situations, the costs and any revenues are saved temporarily on a CO object such as an order or a WBS element before being finally allocated. Settlement is used for this allocation.
1.2 Transactions and Reports
The following transactions are used in settlement
1.2.1 Actual Settlement
KO88: Individual order settlement (you can process any order category)
KO8G: Collective settlement of internal orders
CO88: Settlement of production orders, process orders, and production cost collectors
CJ88: Individual project settlement
CJ8G: Collective project settlement
KK88: Individual settlement of cost objects
KK89: Collective settlement of cost objects
KK87: Individual settlement of production cost collectors
VA88: Collective settlement of sales orders
FO8C: Individual settlement of real estate (from 4.0)
FO3C: Collective settlement of real estate (from 4.0)
1.2.2 Retirement Investment
KO8A: (Not contained in the menu, see note no. 23814): Investment order - retirement
CJ8A: (Not contained in the menu, see note no. 23814): WBS investments - retirement
1.2.3 Planned Settlement and Plan Data Transfer
KO9E: Plan individual settlement of internal orders
KO9G: Plan collective settlement of internal orders
CJ9E: Plan individual settlement of projects
CJ9G: Plan collective settlement of projects
CJ7E: Plan data transfer of projects (individual processing)
CJ7G: Plan data transfer of projects (collective processing
1.2.4 Reports for Settlement
You can also call up each collective processing in the background, while in the transaction. This triggers off a background report, which you start with the SE38 transaction.
In 3.0 this report is called RKOO7400. If you want to use it see note no. 68279. SAP does not provide complete support for the use of this report.
From 4.0 there is a background report for each collective settlement: RKO7 (...= transaction name), e.g. RKO7KO8G for settlement of internal orders. SAP provides complete support for the use of these reports. They provide the same user interface as the online transactions.
1.3 Settlement Rule
In the settlement rule, you specify the receivers to which the costs are to be distributed.
The settlement contains the settlement parameters as well as the distribution rules.
Distribution rules contain the settlement receivers, settlement shares and settlement type. They can contain a source assignment. You always create a distribution rule for a view.
1.3.1 Settlement Receivers
More or less all CO objects are allowed as receivers of a distribution rule, and the external G/L account and fixed asset receivers. In addition, production orders have Material as an external receiver. External means that the settlement not only occurs in CO, but also triggers postings in Financial Accounting.
You specify whether a receiver category can be entered in a distribution rule or not in the settlement profile (see: Settlement Customizing).
During planned settlement, only the following receivers are possible: in 3.0 - cost centers, in 4.0 - cost centers and business processes, from 4.5 cost centers, business processes, plan-integrated orders, WBS elements and profitability segments (see also: note no. 113629).
1.3.2 Distribution Rules Using Percentages, Equivalence Numbers, and Amounts
Settlement is made depending on the settlement rule created. You can create distribution rules with either percentages, equivalence numbers, or amounts.
In planned settlement, you cannot use amounts for settling (see also note no. 113629).
In the settlement profile, you need to specify whether fields (such as for the amount in the rule) are ready for input (see Settlement Customizing).
Note no. 330001 describes how amount settlement works, providing detailed examples. The main theory of amount settlement is that the amount to be settled (from the distribution rule) is proportionately deducted from incurred costs. The rest is distributed to the receivers of the percentage rules.
The amount settlement does not take place if there are no costs that need to be settled. The customer may find the tip in note no. 50249 useful at this stage.
1.3.3 PER/FUL/PRE Rules
You need to assign a settlement type (PER for periodic settlement, and FUL for full settlement) to each distribution rule.
When you manually create a settlement rule, the system defaults the settlement types depending on the receiver category: FUL for G/L accounts and fixed assets and PER for all other receivers. The default value cannot be entered without making modifications.
You can only create FUL and PRE rules for an investment measure (see Investment Measures).
You can create PER and FUL rules at the same time. For the effects of these rules, and the access sequence, see note 27911, and the F1 help for the "Processing type" field, in the initial screen for settlement. The following is important:
The PER rules only include the costs from the settlement period during settlement, whereas the FUL rules also include the values from the previous period that have not yet been settled.
The PER rules mean that during activity inputs, the information is transferred via the activity provider to the settlement receiver, whereas the FUL settlement does not do this.
Therefore it is often useful for an order to have two rules. One with 100% PER to the receiver cost center, and one with 100% FUL to the receiver cost center. This means that all costs from the settlement period are settled using the PER rule, and the activity information for these costs are transferred thus to the receiver cost center. On the other hand, the FUL rule ensures that any subsequent costs that were settled to the past are also settled.
Planned settlement only allows PER rules (see also: note no. 113629)
1.3.4 Settlement View
The settlement rule is always created with reference to a special view. The different views enable you to have different settlement rules for each business transaction. The "actual" view is available for all senders. In addition there is the "plan" view for plan-integrated senders, the "variance" view for production orders, the "incoming order data" view for billing elements that have a results analysis key, and the "plan data transfer" view for billing elements that are not plan-integrated.
1.3.5 Settlement Parameters
These are used to control sender settlement. Listed in the settlement parameters
Description (not used)
Settlement profile
The default value for the settlement profile is taken from the order type for orders and networks, from the project profile for WBS elements, from the requirements class for sales orders and from the cost object type for general objects. You create the settlement profile in Customizing (see Settlement Customizing).
Allocation structure/PA transfer structure/Source structure
The default values for these structures are taken from the settlement profile. You create the structures in Customizing. (see Settlement Customizing).
Hierarchy number
Hierarchical settlement is automatically supported during collective settlement. This means that a sender (that is also a receiver during this settlement) is processed according to the object settled to it. This is controlled by the hierarchy number in the settlement parameters. The higher this number, the sooner the sender is processed. The hierarchy number is automatically issued or adapted by the system, and does not need to be entered manually by the user. If however, there should be any inconsistencies with the hierarchy numbers, then you can repair them using the RKSRULE4 report from note no. 71492
1.3.6 Source Assignments
If a sender has a source structure in the settlement parameters (see Settlement Customizing), then you can create settlement rules for each source assignment. This enables costs and revenues to be settled to various receivers separately, for example.
1.3.7 Simple Settlement
In internal orders, you can store a simple settlement rule in the master data for a cost center or general ledger account, with a settlement cost element. You therefore do not need to customize settlement.
1.3.8 Generated Settlement Rules
There are a lot of object types (including production orders and sales orders) where it is not feasible for the user to create a settlement rule manually. For this reason, the system generates the settlement rules automatically at certain times.
The settlement rule for production orders mainly determines the business behavior of the production order. Therefore, the automatically generated rules for production orders cannot be deleted, you can often only change the percentage. If you enter 0%, you can, however, force a different settlement. The following are examples of automatically created distribution rules:
Production order: Settlement rule to material or sales order. The rule is created at the same time as the order.
Production order: Settlement rule for the variances to the profitability segment. The rule is generated during the first variance settlement.
Sales order: Settlement rule to profitability segment. The rule is created at the same time as the sales order.
WBS elements: PS contains "strategies for determination of settlement rules". This means that you can transfer the settlement rule from higher-level WBS elements for example, for network activities or WBS elements. These settlement rules can be changed as required.
WBS elements: Since Release 4.5, PS has its own transaction for generating settlement rules.
...
