Mastering SAP ABAP: Enhancing Reports with Left Outer Join, Column Labels, and Formatting Techniques

 Welcome back everyone, We have implemented inner join in our last blog, So let’s continue it.

Requirement :- Suppose, there are 7 elements in header table and for only 5 elements of header table, we have elements in item table.





Now, the Customer wants that the matching data between should be displayed, also rest elements of header table should be displayed in the output.

Solution :-

  • In that scenario, we will use left outer join.



Code :-

***********************************************************
*Start of Program
*Declaring the final type structure
TYPES: BEGIN OF ty_final,
         order_number	     TYPE zar_order_number,
         order_date	       TYPE zar_order_date,
         payment_mode	     TYPE zar_payment_mode,
         total_amount	     TYPE zar_total_amount,
         currency	         TYPE zar_curency,
         order_item_number TYPE zar_order_item_number,
         item_cost         TYPE zar_total_amount,
       END OF ty_final.
*********************************************************
*Declaring the internal table and work area
DATA : lt_final TYPE TABLE OF ty_final,
       ls_final TYPE ty_final.
********************************************************
****************************************
*Defining Selection Screen
DATA : lv_order TYPE zar_order_number.
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE TEXT-001.

SELECT-OPTIONS : s_order FOR lv_order OBLIGATORY.

SELECTION-SCREEN : END OF BLOCK b1.
*end of Selection Screen
*************************************************************

*****************************************
*Select queries along with left outer join
SELECT a~order_number a~order_date a~payment_mode a~total_amount a~currency b~order_item_number b~item_cost
  FROM zar_header AS a LEFT OUTER JOIN zar_item AS b ON a~order_number = b~order_number
  INTO TABLE lt_final WHERE a~order_number IN s_order.

IF lt_final IS NOT INITIAL.
*******************************************
*Displaying the data
  LOOP AT lt_final INTO ls_final.
    WRITE :/ ls_final-order_number,
             ls_final-order_date,
             ls_final-payment_mode,
             ls_final-total_amount,
             ls_final-currency,
             ls_final-order_item_number,
             ls_final-item_cost.
  ENDLOOP.

ENDIF.

***********************
*End of Program
*****************************************************************************
  • Execute this program and we will give input from 1 to 7.


  • You can see the output after pressing F8.


  • In the output, we can see that it contains the combined data of both tables and also those records which are not in item table.

Column Labels :-

  • In the above output, we can see that although we are able to display the details of order number but we have not displayed the name for each columns in the output.
  • Now suppose the customer wants to see the columns Labels for each column in the classical report.

Solution :-

  • We will GOTO text elements and we will write Column name for each column.



  • Then, we will use the WRITE statement just above our loop.



Code :-

***********************************************************
*Start of Program
*Declaring the final type structure
TYPES: BEGIN OF ty_final,
         order_number	     TYPE zar_order_number,
         order_date	       TYPE zar_order_date,
         payment_mode	     TYPE zar_payment_mode,
         total_amount	     TYPE zar_total_amount,
         currency	         TYPE zar_curency,
         order_item_number TYPE zar_order_item_number,
         item_cost         TYPE zar_total_amount,
       END OF ty_final.
*********************************************************
*Declaring the internal table and work area
DATA : lt_final TYPE TABLE OF ty_final,
       ls_final TYPE ty_final.
********************************************************
****************************************
*Defining Selection Screen
DATA : lv_order TYPE zar_order_number.
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE TEXT-001.

SELECT-OPTIONS : s_order FOR lv_order OBLIGATORY.

SELECTION-SCREEN : END OF BLOCK b1.
*end of Selection Screen
*************************************************************

*****************************************
*Select queries along with left outer join
SELECT a~order_number a~order_date a~payment_mode a~total_amount a~currency b~order_item_number b~item_cost
  FROM zar_header AS a LEFT OUTER JOIN zar_item AS b ON a~order_number = b~order_number
  INTO TABLE lt_final WHERE a~order_number IN s_order.

IF lt_final IS NOT INITIAL.
*******************************************
*Displaying the data
  WRITE :/ text-001, 15 text-002, 27 text-003, 41 text-004, 51 text-005, 66 text-006,  77 text-007.
  LOOP AT lt_final INTO ls_final.
    WRITE :/ ls_final-order_number,
             15 ls_final-order_date,
             27 ls_final-payment_mode,
             41 ls_final-total_amount,
             51 ls_final-currency,
             66 ls_final-order_item_number,
             77 ls_final-item_cost.
  ENDLOOP.

ENDIF.

***********************
*End of Program
*****************************************************************************

Execute the Program :-



  • Now, We can see the Column Labels for each column in the output.

Note :-

  • We are trying to achieve our requirement through classical reports, later we will see the ALV report as well.

SY-ULINE and SY-VLINE :-

1. SY-ULINE :-

  • It is a system variable for horizontal line.

2. SY-VLINE :-

  • It is a system variable for vertical line.

Requirement :-

  • Till now, we have seen how to display using loop concepts and how to show the column name for each column. Now Suppose, If our Customer wants us to display the data in a box as given below using Classical Report.



Solution:-

  • We will use the concept of SY-ULINE and SY-VLINE to achieve that requirement.



Code :-

***********************************************************
*Start of Program
*Declaring the final type structure
TYPES: BEGIN OF ty_final,
         order_number	     TYPE zar_order_number,
         order_date	       TYPE zar_order_date,
         payment_mode	     TYPE zar_payment_mode,
         total_amount	     TYPE zar_total_amount,
         currency	         TYPE zar_curency,
         order_item_number TYPE zar_order_item_number,
         item_cost         TYPE zar_total_amount,
       END OF ty_final.
*********************************************************
*Declaring the internal table and work area
DATA : lt_final TYPE TABLE OF ty_final,
       ls_final TYPE ty_final.
********************************************************
****************************************
*Defining Selection Screen
DATA : lv_order TYPE zar_order_number.
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE TEXT-001.

SELECT-OPTIONS : s_order FOR lv_order OBLIGATORY.

SELECTION-SCREEN : END OF BLOCK b1.
*end of Selection Screen
*************************************************************

*****************************************
*Select queries along with left outer join
SELECT a~order_number a~order_date a~payment_mode a~total_amount a~currency b~order_item_number b~item_cost
  FROM zar_header AS a LEFT OUTER JOIN zar_item AS b ON a~order_number = b~order_number
  INTO TABLE lt_final WHERE a~order_number IN s_order.

IF lt_final IS NOT INITIAL.
*******************************************
*Displaying the data
  WRITE : sy-uline(102).
   WRITE :/ sy-vline, text-001,
         15 sy-vline, text-002,
         27 sy-vline, text-003,
         42 sy-vline, text-004,
         58 sy-vline, text-005,
         70 sy-vline, text-006,
         90 sy-vline, text-007,
         102 sy-vline.
  LOOP AT lt_final INTO ls_final.
    WRITE :/ sy-uline(102).
    WRITE :/ sy-vline, ls_final-order_number,
             15 sy-vline, ls_final-order_date,
             27 sy-vline, ls_final-payment_mode,
             42 sy-vline, ls_final-total_amount,
             58 sy-vline, ls_final-currency,
             70 sy-vline, ls_final-order_item_number,
             90 sy-vline, ls_final-item_cost,
             102 sy-vline.
  ENDLOOP.
  WRITE :/ sy-uline(102).

ENDIF.

***********************
*End of Program
*****************************************************************************

Output :-



Note :- So, this is how we can use the concept of SY-ULINE and SY-VLINE to show our output in a table format.

Message Class :-

  • Messages always plays an important role for end user.
  • The various types of messages are - A(abort), E(error), I(information), S(success/status), W(warning), X(exit).
  • The transaction code for message class is SE91.


So, that’s enough for today.

We will see how to implement, messages in our code in the next blog.

Thanx alot for being a part of this wonderful journey.

Location: India

Comments

Post a Comment

Popular posts from this blog

Understanding Different Types of SAP Function Modules: Normal, RFC, and Update

Image
  1. Normal/Regular Function Module :- It can be called inside the system. Here Pass by value + Pass by reference both is fine. 2. RFC Function Modules :- You can call from same system or from another possible. In RFC function module you can only have pass by value. In the same system if you are going to add the DESTINATION NONE’ while calling the RFC then it’ll be called in separate session. 3. UPDATE Function Modules :- This is generally used to update the database record. Update Function Module can be called from the same system. ( Background RFC / trfc / grfc ) This is used to achieve generally the SAP LUW. Some time we use from performance perspective also. When COMMIT WORK gets executed then Update starts getting executed. Important Questions on Update Function Modules :- When Update function Module gets Triggered ? ON COMMIT WORK IF a update function module gets failed, under which transaction we can see that ? OR What is the T-Code for ...
Read more

Mastering ABAP: A Step-by-Step Guide to Function Modules and Groups for Modularized Programming

Image
  Function Modules :- It is a modularization technique. The transaction code to create a function module is SE37. To create a function module, we need to create a function group. Function Group :- Function group is a container for the function modules. The transaction code to create a function group is SE80. A function group can store up to 99 function modules. Requirement :- let’s create a function module for sum of two numbers. 1. Creation of function group :- Step 1 :- Go to SE80 transaction code → Object Navigator. Step 2 :- From the drop down select function group. Step 3 :- Give a name of function group. Step 4 :- press enter. Step 5 :- Click on yes a popup screen will appear. Step 6 :- Give short description → press enter → Assign package and transaction request and press enter. Step 7 :- Right click on function group and click on activate to activate the function group. Step 8 :- You will see two includes, will be added afte...
Read more

Introduction to SAP

Image
  1. ERP :- Enterprise Resource Planning The purpose of ERP software is to manage the entire organization. 2. SAP :- System Application and Products in real time data processing 3. History of SAP :- SAP was introduced by SAP AG in 1972 at Walldorf. ( Germany ). SAP is a German based product. 4. Features of SAP :- It is an integration of all functions in to one common software. It is available in more than 40 language across the world. It is a user-based license agreement. ( requires user name and password ). 5. SAP R/3 Architecture :- ( 3 - 3 tier architecture , R - Real ) - SAP is a real time architecture. Layers in SAP Architecture :- Presentation Layer ( User Interaction Layer ) Application Layer ( Writing the programs and applications ) Database Layer ( To store and retrieve the data ). 6. SAP NetWeaver :- SAP NetWeaver (NW) is an integrated technology platform which can support various SAP applications. Examples :- SAP ERP ( Enterpr...
Read more