Preface – This post is part of the ABAP Beginner series.

Interactive Report in SAP ABAP is a report where user can interact with the output page of report. They can click on an item of a list to get its details. For example, On first page you have been provided basic details of employees and on click of  a line item i.e. Employee ID, you are navigated to another page where you can see the employee Annual Salary. If you still want to know further, you again clicked on Employee ID here and now you are navigated to third page where you see employee’s salary structure. These all things are possible using Interactive Report in SAP ABAP.

Introduction

An Interactive Report uses a basic list [list number 0] to show basic information and uses secondary list [1 to 20] to show detailed information. Thus, there are total 21 lists. We use SY-LSIND [System Variable] to get the index number of the list.

Events in ABAP

Before, we learn about events of Interactive report, it is advisable to learn all the ABAP events, because it is common across all the programs. ABAP is an event driven Programming language. ABAP Report Events are used to handle different kinds of events during runtime. It starts with the event name, followed by the programming codes belonging to that event.

It is advisable to use Comment line to declare the end of an event, since Events do not have a closing Keyword and it ends as soon any other Event starts.

There are different kinds of events in ABAP, SAP has categorized these events together.

Categories of Events in ABAP:

There are four categories of Events in ABAP. Among them List Events are the one that helps us to make Interactive Reports:

Events in Classical Report [Used in Interactive Reports too]:

Classical Reports have following events, these events are common for Interactive Reports:

• LOAD-OF-PROGRAM : First event fired, loads program in memory
• INITIALIZATION: Initialize variable
• START-OF-SELECTION : Actual Business Logic (After START-OF-SELECTION)
• END-OF-SELECTION : To end above
• AT SELECTION-SCREEN : To validate Multiple Input fields (After Initialization and before START-OF-SELECTION) (After
• AT SELECTION-SCREEN OUTPUT: To manipulate Dynamic screen
• AT SELECTION-SCREEN ON
• AT SELECTION-SCREEN ON END OF
• AT SELECTION-SCREEN ON BLOCK
• AT SELECTION-SCREEN ON RADIOBUTTON GROUP
• AT SELECTION-SCREEN ON VALUE REQUEST
• TOP-OF-PAGE : To print heading
• END-OF-PAGE: To print footer

Events of Interactive Report in SAP ABAP:

• TOP-OF-PAGE
• END-OF-PAGE
• AT-LINE-SELECTION
• AT USER-COMMAND
• AT PFnn
• SET USER-COMMAND

Note: To know more about these events, click here.

Example of Interactive Report in SAP ABAP:

TABLES zBarry_emp.
TABLES zBarry_sal.

PARAMETERS: ip type char20.

DATA : it_emp1 TYPE TABLE OF zBarry_emp,
       it_emp2 TYPE TABLE OF zBarry_sal,
       wa_emp  TYPE zBarry_emp,
       wa_emp2 TYPE zBarry_sal,
       it_emp3 TYPE TABLE OF zBarry_add,
       wa_emp3 TYPE zBarry_add,
       fnam    TYPE char20,
       fval    TYPE char8,
       fnam1   TYPE char20,
       fval1   TYPE char8..
set PF-STATUS 'PFSTATUS'.
SELECT-OPTIONS : p_empid FOR zBarry_emp-empid.
AT USER-COMMAND.

CASE SY-UCOMM.

    WHEN 'MAIN'.

     sy-lsind = 1.
     PERFORM display_data.
  ENDCASE.

AT SELECTION-SCREEN.
  PERFORM validate_input.

START-OF-SELECTION.
  PERFORM get_data.
  PERFORM display_data.

TOP-OF-PAGE.
  FORMAT COLOR COL_HEADING INVERSE.
  WRITE 'BASIC EMPLOYEE DETAILS'.

TOP-OF-PAGE DURING LINE-SELECTION.
  IF sy-lsind = 1.
    FORMAT COLOR COL_HEADING INVERSE.
    WRITE 'EMPLOYEE SALARY DETAILS'.
  ELSEIF sy-lsind = 2.

    FORMAT COLOR COL_HEADING INVERSE.
    WRITE 'EMPLOYEE ADDRESS DETAILS'.
  ENDIF.

AT LINE-SELECTION.
  PERFORM primary_list.
  PERFORM secondary_list.





*&---------------------------------------------------------------------*
*&      Form  VALIDATE_INPUT
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*  -->  p1        text
*  <--  p2        text
*----------------------------------------------------------------------*
FORM validate_input . "validating input
  IF p_empid  IS INITIAL.
    MESSAGE 'Please Enter Employee Number' TYPE 'E'. "if the employee id field is left blank

  ELSE.
    SELECT empid FROM zBarry_emp INTO TABLE it_emp1 WHERE empid IN p_empid.
    IF sy-subrc <> 0.
      MESSAGE 'Please Enter Correct Employee Number' TYPE 'E'. "if wrong employee id is entered
    ENDIF.
  ENDIF.
ENDFORM.
*&---------------------------------------------------------------------*
*&      Form  GET_DATA
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*  -->  p1        text
*  <--  p2        text
*----------------------------------------------------------------------*
FORM get_data . "fetching basic employee details from table
  SELECT * FROM zBarry_emp INTO TABLE it_emp1 WHERE empid IN p_empid.
ENDFORM.
*&---------------------------------------------------------------------*
*&      Form  DISPLAY_DATA
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*  -->  p1        text
*  <--  p2        text
*----------------------------------------------------------------------*
FORM display_data . "displaying data
  FORMAT COLOR COL_NEGATIVE INVERSE.
  WRITE:/,3 'Employee ID',
      20 'First NAME',
      35 'Last NAME'.
  SKIP.
  LOOP AT it_emp1 INTO wa_emp.
    FORMAT COLOR COL_POSITIVE INVERSE.
    WRITE : /3 wa_emp-empid,20 wa_emp-emp_fname,35 wa_emp-emp_lname.
  ENDLOOP.
ENDFORM.
*&---------------------------------------------------------------------*
*&      Form  PRIMARY_LIST
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*  -->  p1        text
*  <--  p2        text
*----------------------------------------------------------------------*
FORM primary_list . "fetching employee salary details on list 1
  IF sy-lsind = 1.
    GET CURSOR FIELD fnam VALUE fval.

    IF fnam =  'WA_EMP-EMPID'. "if employee id is selected
      SELECT * FROM zBarry_sal INTO TABLE it_emp2 WHERE empid = fval .
      FORMAT COLOR COL_NEGATIVE INVERSE.
      WRITE:/,3 'Employee ID',
               20 'Transaction ID',
               35 'Month',
               55 'Date Of Salary'.
      SKIP.
      LOOP AT it_emp2 INTO wa_emp2.
        FORMAT COLOR COL_POSITIVE INVERSE.

        WRITE : /3 wa_emp2-empid,20 wa_emp2-tid,35 wa_emp2-mon,55 wa_emp2-dos.

      ENDLOOP.

    ENDIF.

    IF  fnam = 'WA_EMP-EMP_FNAME'. "if employee name is selected

      WRITE: / 'name'.
    ENDIF.
  ENDIF.
ENDFORM.
*&---------------------------------------------------------------------*
*&      Form  SECONDARY_LIST
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*  -->  p1        text
*  <--  p2        text
*----------------------------------------------------------------------*
FORM secondary_list . "fetching employee address details on list 2
  IF sy-lsind = 2.
    GET CURSOR FIELD fnam1 VALUE fval1.
    IF fnam =  'WA_EMP-EMPID'. "if employee id is selected
      SELECT * FROM zBarry_add INTO TABLE it_emp3 WHERE empid = fval1 .
      FORMAT COLOR COL_NEGATIVE INVERSE.
      WRITE:/,3 'Employee ID',
               20 'Flat No.',
               35 'Street Name',
               55 'City Name'.
      SKIP.
      LOOP AT it_emp3 INTO wa_emp3.
        FORMAT COLOR COL_POSITIVE INVERSE.
        WRITE : /3 wa_emp3-empid,20 wa_emp3-flat_no,35 wa_emp3-street_name,55 wa_emp3-city_name.
      ENDLOOP.

    ENDIF.

  ENDIF.
ENDFORM.

Note: To learn more about how this program is functioning, click here.

Programming Guidelines:

1. Never use Selection Screen Events in Function Module
2. Use LOAD-OF-SCREEN to load default values  for the type of Reports executed via SUBMIT or using a transaction code
3. Use INITIALIZATION to load default values  for the executable type of Reports
4. It is advised not to specify an event more than once [Except AT-SELECTION-SCREEN & GET event, all other can be specified multiple times.]
5. If you are not specifying any event name, still specify START-OF-SELECTION to improve readability
6. After every execution of events NEW-LINE event is executed automatically.

Preface – This post is part of the ABAP Beginner series.

ABAP is an event driven Programming language. ABAP Report Events are used to handle different kinds of events during runtime. It starts with the event name, followed by the programming codes belonging to that event. Classical reports in SAP ABAP are the reports which contain both selection screens and output screens.

It is advisable to use Comment line to declare the end of an event, since Events do not have a closing Keyword and it ends as soon any other Event starts.

There are different kinds of events in ABAP; SAP has categorized these events together.

Categories of Classical Report Events in SAP ABAP:

There are four categories of Events in ABAP:

Events of Classical Reports in SAP ABAP:

Classical Reports have following events:

• LOAD-OF-PROGRAM : First event fired, loads program in memory
• INITIALIZATION: Initialize variable
• START-OF-SELECTION : Actual Business Logic (After START-OF-SELECTION)
• END-OF-SELECTION : To end above
• AT SELECTION-SCREEN : To validate Multiple Input fields (After Initialization and before START-OF-SELECTION) (After
• AT SELECTION-SCREEN OUTPUT: To manipulate Dynamic screen
• AT SELECTION-SCREEN ON
• AT SELECTION-SCREEN ON END OF
• AT SELECTION-SCREEN ON BLOCK
• AT SELECTION-SCREEN ON RADIOBUTTON GROUP
• AT SELECTION-SCREEN ON VALUE REQUEST
• TOP-OF-PAGE : To print heading
• END-OF-PAGE: To print footer

Programming Guidelines:

1. Never use Selection Screen Events in Function Module
2. Use LOAD-OF-SCREEN to load default values  for the type of Reports executed via SUBMIT or using a transaction code
3. Use INITIALIZATION to load default values  for the executable type of Reports
4. It is advised not to specify an event more than once [Except AT-SELECTION-SCREEN & GET event, all other can be specified multiple times.]
5. If you are not specifying any event name, still specify START-OF-SELECTION to improve readability
6. After every execution of events NEW-LINE event is executed automatically.

Preface – This post is part of the ABAP Beginner series.

ABAP report is an old term for executable program in ABAP and it is a program that can be executed using the SUBMIT statement. This SUBMIT statement is always executed internally as we execute it using F8 user command or via a Transaction code.

Types of ABAP Report

A report in ABAP is of two types:

1. Classical Reports
2. Interactive Reports

Both these Reports are event driven. The only thing that divides them is the use of different events.

Classical Report

A classical report is a report which contains both selection screens and output screens.

Events in Classical Report

Classical Reports have following events:

• LOAD-OF-PROGRAM : First event fired, loads program in memory
• INITIALIZATION: Initialize variable
• START-OF-SELECTION : Actual Business Logic (After START-OF-SELECTION)
• END-OF-SELECTION : To end above
• AT SELECTION-SCREEN : To validate Multiple Input fields (After Initialization and before START-OF-SELECTION) (After
• AT SELECTION-SCREEN OUTPUT: To manipulate Dynamic screen
• AT SELECTION-SCREEN ON
• AT SELECTION-SCREEN ON END OF
• AT SELECTION-SCREEN ON BLOCK
• AT SELECTION-SCREEN ON RADIOBUTTON GROUP
• AT SELECTION-SCREEN ON VALUE REQUEST
• TOP-OF-PAGE : To print heading
• END-OF-PAGE: To print footer

Interactive Report

An interactive report is a report in which the information are shown using basic and secondary lists. An interactive report has total 21 lists including the basic list. The first list is numbered as 0 and other are from 1 to 20.

To get the current page number, we can use system variable SY-LSIND.

Events in Interactive Report

*** Will be updated soon

Preface – This post is part of the ABAP Beginner series.

ABAP Report Events: Reporting Events

In ABAP Report Events after Program Constructor Event of ABAP, we have ABAP Reporting Events which occur in a predefined manner. These events are called in a predefined sequence (as mentioned later in this post). These events are only called in Executable reports.

Following are the types of Reporting Events:

INITIALIZATION

As discussed above, this event is called just after LOAD-OF-PROGRAM and before any selection screen events; and it is used to fix default values and initialize fields.

Example

PARAMETERS:  p_lan TYPE string.

INITIALIZATION.

p_lan = sy-langu.

***Note: In case a standard selection screen is there, multiple calls are made to the same program based upon user input and interaction. INITIALIZATION is ignored after the first call to the program and in this case to initialize the selection screen explicitly for each call we will have to use the event AT SELECTION-SCREEN OUTPUT.

START-OF-SELECTION

As discussed above, this event is called after the Standard Screens are once processed and it is used to write all the functional statements. By functional statements we mean the actual code/ business logic.

Example

REPORT ztest_report.

DATA:  text TYPE string.

START-OF-SELECTION.

text = ‘Hello World!’.

Write: text.

*** Note: If I will not write START-OF-SELECTION in above program, still the program will construct a block of START-OF-SELECTION implicitly just before the actual code. Thus we can skip writing START-OF-SELECTION, but it is a good practise to use it as it makes the code readable.

Preface – This post is part of the ABAP Beginner series.

Program Constructor Event

A Program Constructor event in SAP ABAP is used to load global constant value or data of a program. It consist only one Event: LOAD-OF-PROGRAM

LOAD-OF-PROGRAM

Load of Program is Just like a Class Constructor or Static Constructor of a Class.

Now if you don’t know class constructor, then simply understand this thing, A Load of Program loads default values for a session e.g. Language.

Now you may say, we can load default values using INITIALIZATION, yes you can but it will be executed for every run, while Load of Program is executed once for a session.

LOAD OF PROGRAM is useful only in case of a report called using SUBMIT or the one that run using a transaction code else it will perform same as INITIALIZATION.

Example of LOAD-OF-PROGRAM:

LOAD-OF-PROGRAM.

DATA global_langu TYPE sy-langu.
global_langu = COND #( WHEN sy-langu = 'D' THEN 'German' ELSE 'English' ).

Explanation:

The above program have two statements.

• The first statement is declaring a variable g_langu (A global variable for language) of type sy-langu (it fetches system language that is based on the system location).
• The second statement is checking a condition, if the system language is D (i.e. German) then assign g_langu as ‘German’ and assign ‘English’ for any other system language.

Notes:

• It is the first even executed by SAP ABAP

• It is used to initialize global default values
• If in a program, LOAD-OF-PROGRAM is only used for initialization and there is no executable lines after that, then LOAD-OF-PROGRAM event is not raised

Flow of an Executable Program

The statement SUBMIT is used to load the program in a separate internal session and based upon the following sequence calls different events as mention below:

1. LOAD-OF-PROGRAM
2. INITIALIZATION
3. AT SELECTION-SCREEN OUTPUT
4. START-OF-SELECTION
5. END-OF-SELECTION

Preface – This post is part of the ABAP Beginner series.

SAP FICO (Financial Accounting and Controlling)

SAP FICO is used to store and control the financial information of the organization. FICO is one of the most important modules as it is used to analyze the financial condition of the company in the market. It can integrate with other SAP modules such as SAP MM, SAP SD, SAP PP, SAP SCM, etc.

The sub components of SAP FICO are as follows:

1. Financial accounting General Ledger: It is a set of accounts a business uses to keep track of its financial transactions and create reports.
2. Financial accounting Accounts receivable and payable: Accounts payable is the amounts the company owes for buying goods or services from a vendor and accounts receivable is the amount the company has to receive for supplying goods and services to a customer.
3. Financial accounting asset: It is managing and supervising the fixed assets the company owns.
4. Financial accounting bank accounting: This component is used to handle transactions that you process with your bank.
5. Financial accounting Travel management: This has a complete integrated management of all processes involved in a business trip.
6. Financial accounting Fund Management: It interacts with various modules of SAP to get fund details.
7. Financial accounting Legal Consolidation: for a company with multiple units, legal consolidation helps to view all details in a single financial statement.

Below are some transaction codes for SAP FICO module:

F110 -> Parameters for automatic payment

FB60 -> Enter incoming invoices

PR00 -> Travel expenses

FB01 -> Post document

FTXP -> Maintain tax code

Below are some basic tables SAP FICO module:

SKA1 -> General Ledger accounts (Chart of Accounts)

SKAT -> General Ledger accounts (Chart of accounts: Description)

SKB1 -> General Ledger accounts (Company codes)

KNBK -> Bank details

KNVP -> Customer partners

KNVK -> Contact persons

Preface – This post is part of the ABAP Beginner series.

SAP Production Planning (PP)

SAP Production planning as the name suggests deals with planning processes such as material planning, capacity planning, production order, and bill of material and goods movement. It is the process of fulfilling demands with the manufacturing capacity. It tracks and makes a note of the manufacturing process flows, for example the target and actual costs. It is integrated with other SAP modules such as MM, SD, FI, QM and PM.

There are two types of production processes in SAP PP:

1. Discrete Production: In this kind of production, the product and costs keep changing according to the orders and lots.
2. Repetitive Production or Production industries: In this kind of production, the product does not change for a long period of time. It is not dependent on orders as production takes place in total quantity.

The process of production execution is as follows:

1. Convert planned order to production order: This is the first step. When a production order is created, its SAP is defined in the system
2. Issue the production order: Unless the issuing of the production order is done, it cannot be executed.
3. Issue goods for production order: after the order is issued, the goods need to be issued for execution of the order. Once it is done, the document number is updated in the system.
4. Production order confirmation: All the remaining sub processes are executed according to the required operations to finish the production as per the order
5. Goods receipt with respect to Production order: Once the production order is complete, the produced goods are placed the storage area.

Some important tables in SAP Production Planning are:

MDKP -> Document header Data

MDTB -> Table structure

S094 -> Stock analysis

PLAF -> Planned order details

S026 -> Material Usage

Some basic Transaction codes in SAP Production Planning module are:

 MD25 -> Create planning calendar

MD26 -> Change planning calendar

MD27 -> Display planning calendar

MEQ1 -> Maintain quota file

Preface – This post is part of the ABAP Beginner series.

SAP CRM (Customer Relationship Management)

SAP CRM is nothing but the way businesses interact with their customers. Traditionally, this is done by automating and integrating your customer related activities such as sales and marketing, and customer service. But in today’s time, the CRM activities go beyond that and provide functionalities like personalization, e-commerce, social media, collaboration and more. New CRM softwares store all customer information from their contacts to social media activities. This information can be used to dramatically improve the business. CRM benefits are huge from increasing sales revenue, customer loyalty to lower costs and better customer related activities.

The SAP CRM application is a software which targets small and large sized businesses in all the sectors.

SAP CRM Architecture:

The following are the key components in the SAP CRM architecture:

• SAP ERM Server (CRM Enterprise, CRM Middleware and Adapter)
• SAP ECC – used for backend
• SAP BI – is used for reporting
• SAP SCM – used to better the capabilities of CRM
• Mobile and handheld devices
• Internet
• Enterprise portal

The Adapter is mainly used for handheld devices and the internet. The CRM Enterprise is used for telephone and email services.

The SAP ECC and CRM are closely related to each other and need to synchronise in some areas like sales, customer master records, organisational model, etc.

Some of the important Transaction codes of the CRM module are:

CRMD_ORDER -> Transaction processing

R3As -> Start initial load

CRM_DNO_MONITOR -> Transaction monitor

SMOEAC -> Administration console

PPOMA_CRM -> Change organizational model

R3AM1 -> Monitor Objects

Some of the important tables of the CRM module are:

BUT000 -> General Data

BUT020 -> Addresses

BUT050 -> BP relationships/role definitions: General data

BNKA -> Bank master data

ADR2 -> Telephone numbers

Preface – This post is part of the ABAP Beginner series.

SAP MM (Material Management)

SAP MM: Material management is a module of SAP which as the name suggests deals with material management and inventory management. It ensures that there is never a shortage of materials in the supply chain process of the organization. It also helps the organization to complete the purchasing of goods in a timely manner and in a cost effective way. It incorporates other modules like Sales and Distribution, Production Planning, Plant Maintenance, Project Systems, Warehouse Management which are based on Materials Management module.

The process of material management is as follows:

1. Determination of requirement: Determines what materials and services are required for the organization.
2. Source Determination: Determines who can fulfil the requirement.
3. Vendor Selection: After gathering the requirements, direct contact is made with the suppliers and a suppliers is chosen who can satisfy the requirements.
4. Purchasing Order (PO): The purchasing department is informed about the products needed. When that request is approved, the purchase order is created and assigned to the supplier.
5. Order Monitoring: Order monitoring is tracking of dates and the goods from the time of ordering to the time the goods are delivered. It is done to ensure that there are no discrepancies and if any, they can be handled beforehand.
6. Goods Receipt: The goods are received and are checked for quality and condition.
7. Invoice Verification: Reconciliation of the invoice and purchase order is done. It means the invoice received is checked for cost, quantity and quality.
8. Payment: The vendor is paid.

Some of the important Transaction Codes for Material Management are as follows:

MM01 -> For creation of material

MM02 -> For change of material

MM03 -> For display purposes

ME51N -> Creation of purchase requisition

ME41 -> creation of RFQ

A few of the basic tables in SAP MM modules are:

MARA -> general data, material type

MLAN -> Sales data, Tax Indicator, Tax

MAKT -> Short texts, descriptions

EBAN -> Purchase Requisition

EKES -> Vendor Confirmations

Preface – This post is part of the ABAP Beginner series.

SAP SD (SALES AND DISTRIBUTION)

Some of the important tables in SAP SD module are:

Some of the important Transaction codes for SAP SD are as follows: