Hierarchy

⤷

⤷

IMG Activity
ID | /MRSS/NW_RAC_BADI_CH | BAdI: Determination of Planning Status for PM/CS Orders |
Transaction Code | /MRSS/92000357 | (empty) |
Created on | 20130328 | |
Customizing Attributes | /MRSS/NW_RAC_BADI_CH | BAdI: Determination of Planning Status for PM/CS Orders |
Customizing Activity | /MRSS/NW_RAC_BADI_CH | BAdI: Determination of Planning Status for PM/CS Orders |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /MRSS/NW_RAC_BADI_CHECK_DURA |
Use
This Business Add-In (BAdI) is used to determine the planning status of PM/CS orders.
You can use this BAdI to determine whether the duration of an assignment exceeds the planned time, falls short of it, or covers it exactly when compared with the duration of a demand. You can also use this BAdI to incorporate individual tolerances.
Depending on the result of the comparison, the system sets one of the following abstract statuses: PLAN_EMPTY, PLAN_UNDR, PLAN_OVER or PLAN_FULL. In addition, you can override the icon that indicates the planning status at worklist level in the planning board.
This BAdI provides the following methods:
- CHECK_DURATION
This method is used to determine the abstract planning status by comparing the assignment duration with the demand duration. The result of the comparison is determined as follows:
- Assignment duration equals demand duration: '='
- In this case, the system sets the abstract status as PLAN_FULL.
- Assignment duration exceeds demand duration: '+'
- In this case, the system sets the abstract status as PLAN_OVER.
- Assignment duration falls short of demand duration: '-'
- In this case, the system sets the abstract status as PLAN_UNDR.
- CHANGE_PLAN_STATUS
You can use this method to override the planning status icon that is displayed at worklist level in the planning board. This method is not implemented by default.
Possible planning statuses that are indicated by an icon in the planning board are the following:
- NP - Not Planned
- PP - Partially Planned
- TP - Planned
Requirements
You have defined abstract statuses as described in Customizing activityDefine Abstract Status.
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transactionSE18).
Activities
Example
You can find example implementations in the BAdI Builder on the Enhancement Spot Element Definitions tab in the Implementation Example Classes section.
The following example implementations are available:
- /MRSS/CL_RAC_BADI_CHECK_DURATN
This class is implemented by default. It is used to determine the abstract planning status based on the comparison between the assignment duration and the demand duration. The system does not take the number of resources into account.
- /MRSS/CL_RAC_BADI_CHECK_DEM_TW
You can use this implementation to determine the abstract planning status. In this case, the total demand work (that is, the number of resources multiplied by the demand duration) is taken as a basis for the comparison.
See also
For more information about implementing BAdIs as part of the Enhancement Framework, see SAP Library for SAP NetWeaver Platform on SAPHelp Portal at http://help.sap.com/nw_platform. Choose a release and the Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development -> Enhancement Framework.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20130403 |
SAP Release Created in | 800 |