SAP ABAP Central: Calling Fragment Form & Send it as an attachment using ABAP Walk-Through

This Blog is based on the Output Management Form and has all of its configuration completed

Ex for dunning: use maintenance view: V_T047E using code: sm30 to switch between frameworks through drop-down list

Calling Fragment Form & Send it as an attachment using ABAP Walk-Through

First: you can identify Fields for Key & Master Key internal tables for standard fragment form through putting a breaking point

By using framework: sap cloud and using fragment form template and of course maintain brf+ configuration

In class: CL_SOMU_FORM_SERVICES , Method : GET_DOCUMENT

1. Put a break point in the first line and go back to the previous program to see internal tables passed to form calling for keys.

2. Take screenshots for them, as you will be using them for the custom calling of the form as these fields are maintained according to configuration & master form template derivation.

3. If you need the application ID Key, it’s a concatenation between multiple variables, You will find it in the call back class specific to a given object in the SPRO configuration

SPRO -> CROSS APPLICATION COMPONENTS -> OUTPUT CONTROL (here you can find all of OM Configuration) -> DEFINE OUTPUT TYPE THEN SELECT THE ENTRY CORRESPONDING TO YOUR BRF+ ROLE and click details, you will find your call back class, in our class for dunning : CL_FIN_FO_DUNN_OUTPUT , all call back classes Implement same interface, then go into method : IF_APOC_COMMON_API~GET_FDP_PARAMETER

Second step:

Activate the legacy printout system and put a breakpoint inside the printing object whether it’s a program or function module, if you are using PDF, you can put a breakpoint in open job FM and trace back through the stack to the transaction screen printing program

In our case for dunning: It prints using FM : “PRINT_DUNNING_NOTICE_PDF”, put a breakpoint there

1. Start comparing the values of the key & master key internal table with local variables available to locate the objects that contain the data which will be passed to the fragment forms Key internal tables from the standard

1. You will find all the data u need in the objects because whether it is fragment, PDF or whatever technology, the system always collects the same data passed one way or the other

2. After that start creating your custom code to call the fragment form

Consider the condition to identify which master form template to use.

3. Create an enhancement in the standard program to defuse the standard code and prevent its execution, make sure that the standard code doesn’t update standard somewhere along the code as you need to confirm whether it happens through the OData service of fragment or not! ( because if not you will have to use the standard code that does that to make everything consistent )

1. then test the cycle end to end

in our case , here is the example for the PO Form

1. I created a custom program se38 to test using po form

*&---------------------------------------------------------------------*

*& Report ZDUMMY

*&---------------------------------------------------------------------*

REPORT ZDUMMY.

SELECTION-SCREEN BEGIN OF BLOCK b1.

PARAMETERS: p_po_num TYPE ebeln MATCHCODE OBJECT h_ekko OBLIGATORY.

SELECTION-SCREEN END OF BLOCK b1.

INITIALIZATION.

START-OF-SELECTION.

DATA: lo_cl_somu_form_services TYPE REF TO cl_somu_form_services.

DATA: lt_keys TYPE cl_somu_form_services=>ty_gt_key.

DATA: ls_ekko TYPE ekko.

DATA: lt_master_keys TYPE cl_somu_form_services=>ty_gt_key.

DATA: lv_content TYPE xstring.

DATA: lv_xml TYPE xstring.

DATA: lv_pages TYPE fppagecount.

DATA: lv_trace_string TYPE string.

DATA: lv_stop_processing TYPE abap_bool.

DATA: lt_message TYPE cl_somu_form_services=>ty_gt_message.

DATA: lv_output_length TYPE i.

DATA: lt_generated_pdf TYPE STANDARD TABLE OF tbl1024 .

FIELD-SYMBOLS: <ls_key> TYPE cl_somu_form_services=>ty_gs_key.

SELECT SINGLE *

FROM ekko

INTO ls_ekko

WHERE ebeln = p_po_num.

" --------------------------- Values for the purchase order form ---------------------------

APPEND INITIAL LINE TO lt_keys ASSIGNING <ls_key>.

<ls_key>-name = 'PurchaseOrder'.

<ls_key>-value = p_po_num.

APPEND INITIAL LINE TO lt_keys ASSIGNING <ls_key>.

<ls_key>-name = 'SenderCountry'.

<ls_key>-value = 'DE'.

APPEND INITIAL LINE TO lt_keys ASSIGNING <ls_key>.

<ls_key>-name = 'PurchaseOrderChangeFlag'.

<ls_key>-value = space.

APPEND INITIAL LINE TO lt_keys ASSIGNING <ls_key>.

<ls_key>-name = 'Language'.

<ls_key>-value = 'E'.

APPEND INITIAL LINE TO lt_keys ASSIGNING <ls_key>.

<ls_key>-name = 'ReceiverPartnerNumber'.

<ls_key>-value = ls_ekko-lifnr.

" --------------------------- Values for the master form template ---------------------------