sap-abap

## 1. Environment Detection Ask before writing any code: ``` □ ABAP release? (7.02 ECC / 7.40 / 7.50 / 7.57 S/4HANA 2023) □ Clean Core required? (on-premise CBO allowed vs BTP side-by-side only?) □ Package / naming convention? (Z* / Y* prefix, package structure) □ Transport landscape? (DEV → QAS → PRD, how many systems?) □ S/4HANA deployment? (on-premise / RISE / Cloud PE — affects what's allowed) ``` --- ## 2. Enhancement Framework — Decision Table | Scenario | Recommended Approach | Notes | |----------|---------------------|-------| | Classic user exit exists | SMOD / CMOD | ECC only — avoid in new S/4HANA dev | | BAdI definition exists | New BAdI (SE19 / GET BADI) | All releases — preferred approach | | No exit/BAdI, on-premise | Enhancement Spot (SE18/SE19) | CBO allowed on-premise | | S/4HANA Clean Core / Cloud PE | BTP side-by-side extension (RAP + Events) | No on-stack modifications | --- ## 3. Code Patterns with Full Examples ### New BAdI (All Releases — Preferred) ```abap " Step 1: Find BAdI via SE19 or BADI Explorer (SPRO) " Step 2: Create enhancement implementation " Step 3: Implement interface method DATA lo_badi TYPE REF TO badi_name. GET BADI lo_badi. CALL BADI lo_badi->method_name EXPORTING iv_input = lv_value IMPORTING ev_output = lv_result. ``` ### ALV — OO Approach (Recommended Over REUSE_ALV_GRID_DISPLAY) ```abap DATA: lo_alv TYPE REF TO cl_salv_table, lt_result TYPE TABLE OF your_structure. " ... populate lt_result ... TRY. ...