Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
IS-REA-COR (Application Component) Recycling Administration Core Functions⤷
J7LR (Package) REA Core Functionality
IMG Activity
| ID | J_7L_REA_LDE_FPM_EXI | BAdI: Customer Enhancements Floor Plan Manager (FPM Event Loop) |
| Transaction Code | (empty) | |
| Created on | 20091020 | |
| Customizing Attributes | J_7L_REA_LDE_FPM_EXI | BAdI: Customer Enhancements Floor Plan Manager (FPM Event Loop) |
| Customizing Activity | J_7L_REA_LDE_FPM_EXI | BAdI: Customer Enhancements Floor Plan Manager (FPM Event Loop) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /J7L/BADI_REA_LDE_FPM_EXIT |
Use
This Business Add-In is used in the Recycling Administration (IS-REA) component.
This BAdI allows you to intervene in the event chain of the Floorplan Manager in the lean master data entry process. The names of the BAdI methods and their signature follow the methods in the event chain of the Floorplan Manager. In addition, a reference to the Web Dynpro component is also passed from which the call is executed. Only one BAdI instance exists within an internal mode so the BAdI implementation can also retain a state across several calls. Two additional methods are used for initialization or finalization.
Requirements
Standard settings
- The Business Add-In is not active in the standard system.
- The BAdI is not designed for multiple use.
- The BAdI is filter-dependent.
Implement a class with the interface /J7L/I_BADI_LDE_FPM_EXIT. Based on the filter criteria, you can link a specific implementation to a Web Dynpro application, Web Dynpro application configuration, or the floorplan.
Activities
You must only implement the methods whose call you want to influence within the event chain of the Floorplan Manager. The events INITIALIZE and FINALIZE are the only events that are not called as part of the Floorplan Manager event chain; they serve to initialize and finalize the BAdI implementation once only. The events PROCESS_BEFORE_OUTPUT and PROCESS_EVENT, and FLUSH and AFTER_FAILED_EVENT are called on entering and exiting each UIBB. The events OVERRIDE_EVENT_OIF/GAF are called at the beginning of the event chain. The events CHECK_BEFORE_SAVE, SAVE, AFTER_COMMIT, and AFTER_REJECTED_SAVE are called when a save is executed in the Web Dynpro application.
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
See also:
This BAdI uses the interface/J7L/I_BADI_LDE_FPM_EXIT. For more information, display the interface in the Class Builder.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| 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 | 20091020 |
| SAP Release Created in | 605 |
