Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
PS-COS-PER-SE (Application Component) Settlement⤷
KAPG (Package) Automatic Generation of Settlement Rules
IMG Activity
| ID | WBS_SETTLEMENT_RULE | Business Add-In: Generation of WBS Element Settlement Rule (CJB1/CJB2) |
| Transaction Code | S_AL0_96000750 | (empty) |
| Created on | 20020121 | |
| Customizing Attributes | WBS_SETTLEMENT_RULE | Business Add-In: Generation of WBS Element Settlement Rule (CJB1/CJB2) |
| Customizing Activity | WBS_SETTLEMENT_RULE | Business Add-In: Generation of WBS Element Settlement Rule (CJB1/CJB2) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | WBS_SETTLEMENT_RULE |
Use
With this Business Add-In you can influence the generation of settlement rules for WBS elements (transactions CJB1 and CJB2). Use the following methods:
DETERMINE_STRATEGY: With this method you can adapt the strategy determination to your individual needs. To do this you can use the importing parameter I_PROJ (project definition) and I_PRPS (WBS element). Return the determined strategy to the caller using the parameter E_STRAT. While doing this you must differentiate between the following two cases:
- In the method DETERMINE_STRATEGY you could determine a strategy: Fill E_STRAT and in addition set E_STRAT_BY_EXIT to 'X'. If you do not set this parameter the system will ignore the strategy you determined.
- Determining a strategy failed: Leave E_STRAT empty. Using E_STRAT_BY_EXIT you control whether the system tries to determine a strategy afterwards using the standard logic. If you do not fill the parameter E_STRAT_BY_EXIT the system will run the standard strategy determination. You receive only one error message indicating that the system could not determine a strategy if the standard strategy determination is not successfully completed. If you set the paramater instead the system will not look any further for a strategy. You receive in any case an error message.
ADD_ADDITIONAL_PARTNERS: In the standard, the system takes the following partner roles into account when generating a settlement rule: Ship-to party, bill-to party, payer, freight forwarder, and sales executive. Using the method ADD_ADDITIONAL_PARTNERS you can provide for other partner roles you included in KOMK and KOMP. The partners are available to you through the importing parameter I_VPBA. Enter the partner role in CS_KOMK or CS_KOMP.
Be aware that the system does not check the changes you make in the method ADD_ADDITIONAL_PARTNERS for the structures KOMK/KOMP. You are repsonsible for the consistency of this data.
FILTER_SD_ORDERS: If you do not want to take sales documents and sales document items into account when you generate a settlement rule, you can restrict the sales documents and sales document items determined by the system. In the standard, the system takes quotations, orders, contracts and orders free of charge.
Caution: You can only limit the sales documents and sales document items. You cannot expand them. You cannot change characteristics of the sales documents and sales document items in the method. FILTER_SD_ORDERS.
Requirements
You generate settlement rules for WBS elements.
Standard settings
The Business Add-In is not active in the standard system.
Activities
In order to activate the Business Add-In you must create an active implementation.
Example
Be aware that you are not allowed to send any system messages in the methods of these Business Add-Ins. You are also not allowed to carry out a 'COMMIT WORK'.
Furthermore you should take into consideration that the methods carried out above can only be called in the transactions CJB1 and CJB2. If you manually maintain the settlement rule or automatically generate settlement rules for networks and network activities, you cannot run the Business Add-In.
In the past you could influence strategy determination and the determination of partners using modification. Be aware that the function modules described in their corresponding notes are no longer called if an active implementation for the Business Add-In WBS_SETTLEMENT_RULE exists. Therefore is is not important whether the methods of the Business Add-In are used or not.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-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 | WBS_SETTLEMENT_RULE | 0 | HLA0006688 | Automatic and Periodic Allocations |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20020121 |
| SAP Release Created in | 470 |
