Ansicht
Dokumentation
/CPD/PFP_BADI_DATE_R - BAdI: Handling Date Rescheduling
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up Addresses (Business Address Services)This documentation is copyright by SAP AG.
This Business Add-In (BAdI) is used in the Project Cost and Revenue Planning (CA-CPD-FP) component. You can use this BAdI to define your own logic to determine how the system moves planned data when there is a change in the start and end dates of a structure element.
For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
/CPD/CL_PFP_IP_DATE_RESCHEDULE
In the default implementation, the system moves planned quantities to a new period in the same way as it was originally planned. If the new period is shorter than the original plan period, planned quantities are aggregated only at the end of the new period. Consider the following example:
| January | February | March | April | May | June | July | August | September | October |
|---|---|---|---|---|---|---|---|---|---|
| Original Plan Period | |||||||||
| (February - April) | 2 | 3 | 4 | ||||||
| New Period 1 | |||||||||
| (January - March) | 2 | 3 | 4 | ||||||
| New Period 2 | |||||||||
| (April - June) | 2 | 3 | 4 | ||||||
| New Period 3 | |||||||||
| (January - April) | 2 | 3 | 4 | 0 | |||||
| New Period 4 | |||||||||
| (May - June) | 2 | 7 | |||||||
| New Period 5 | |||||||||
| (January - July) | 2 | 3 | 4 | 0 | 0 | 0 | 0 | ||
- For a structure element, if there is a difference in characteristic for a resource type and resource combination, the system initially shifts quantities or amounts by calculating the shift in period. Thereafter, if the quantities or amounts lie outside the new period, they are aggregated either at the beginning or the end of the new period depending on the shift in the new period.
- Consider the following example with reference to a WBS in which you plan for a human resource type Consultant in USD and EUR. In the following example, the numbers in the first line have shifted by three months. Consequently, the quantity for the planning in USD is aggregated at the beginning of the new period because 10 hours have shifted to a period outside the new plan period.
| January | February | March | April | May | June | July | August | September | October | November | December |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Original Plan Period | |||||||||||
| (April - June) | |||||||||||
| Consultant (EUR) | 10 | 20 | |||||||||
| Consultant (USD) | 10 | 30 | |||||||||
| New Period 1 | |||||||||||
| (February - April) | |||||||||||
| Consultant (EUR) | 10 | 20 | |||||||||
| Consultant (USD) | 40 (10 + 30) | ||||||||||
/CPD/CL_IM_PFP_DATE_RESCHEDULE
In the sample implementation, the system moves planned quantities to a new period using the following rule:
- The same quantity is copied wherever the periods overlap.
- If the original planned quantities or amounts are earlier to or later than the new period, the figures are aggregated at the start or end of the new period respectively.
- The quantity is aggregated at the closest period (start or end) if the new period is outside the original plan period
Consider the following example:
| January | February | March | April | May | June | July | August | September | October |
|---|---|---|---|---|---|---|---|---|---|
| Original Plan Period | |||||||||
| (February - April) | 2 | 3 | 4 | ||||||
| New Period 1 | |||||||||
| (January - March) | 0 | 2 | 7 | ||||||
| New Period 2 | |||||||||
| (April - June) | 9 | 0 | 0 | ||||||
| New Period 3 | |||||||||
| (January - April) | 0 | 2 | 3 | 4 | |||||
| New Period 4 | |||||||||
| (May - June) | 9 | 0 | |||||||
| New Period 5 | |||||||||
| (January - July) | 0 | 2 | 3 | 4 | 0 | 0 | 0 | ||
| New Period 6 | |||||||||
| (January - February) | 0 | 9 | |||||||
BAdI method documentation:
RFUMSV00 - Advance Return for Tax on Sales/Purchases PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 9467 Date: 20240423 Time: 161215 sap01-206 ( 64 ms )
