Hierarchy
EA-DFPS (Software Component) SAP Enterprise Extension Defense Forces & Public Security⤷
IS-DFS-OF (Application Component) Organizational Flexibility⤷
/ISDFPS/ORGM (Package) Organizational Measure
IMG Activity
| ID | /ISDFPS/ORGM_SUBAREA | BAdI: Change Measure Subareas |
| Transaction Code | /ISDFPS/89000046 | (empty) |
| Created on | 20050113 | |
| Customizing Attributes | /ISDFPS/ORGM_SUBAREA | BAdI: Change Measure Subareas |
| Customizing Activity | /ISDFPS/ORGM_SUBAREA | BAdI: Change Measure Subareas |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /ISDFPS/ORGM_SUBAREA |
Use
You use this Business Add-In (BAdI) to change the standard assignment of data to a measure subarea.
Any data that is changed within an organizational measure is assigned initially to predefined subareas. These subareas can be grouped in measure areas in Customizing. Within an organizational measure, checks, status changes, and approvals must always be executed together for the data within a measure area. In certain circumstances, you might decide that data is assigned to an unsuitable subarea and want to assign it to a different subarea independently of the other data assigned to the current subarea. You can implement this change in this BAdI.
Technically, data is assigned to a subarea when the change document for a data record is assigned to a subarea. The assignment of a change document to a subarea is not saved. It is determined again each time a change document is accessed. The implementation of this BAdI therefore also affects data that was created or changed before this implementation was activated.
The CHANGE_DOCUMENT and ORGM_SUB_AREA parameters are available for the implementation. The importing parameter CHANGE_DOCUMENT transfers the change document for which the assignment to a subarea is to be determined. The changing parameter ORGM_SUB_AREA transfers the subarea already determined by the standard system. This can be changed, if necessary.
The system does not support a scenario in which a subarea cannot be determined. If the initial value for ORGM_SUB_AREA is returned, the system regards the result as an implementation error.
Requirements
Standard settings
Activities
Example
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 |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | /ISDFPS/ORGM_SUBAREA | 0 | /ISDFPS/KL10000013 | Structures Workbench |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20050113 |
| SAP Release Created in | 470 |
