Fun with ABAP

Problem with Custom table activation

2011-09-24T00:07:00.000-07:00

Joyjit Ghosh, Kolkata.

Background:
Recently we have seen a peculiar problem during activation of an existing custom table after a field addition.
During activation it was throwing following message:

From the above screen shots we were clueless about the problem
That's why thought to check the system log (SM21):

It gives the required hint that problem is with database physical storage

Solution:
After searching through SAP market place we have found an OSS note that gives a clue to resolve this issue. It states about a data dictionary table called DDSTORAGE that stores the parameters related to database storage for any data dictionary table. Further investigation reveals that to resolve this problem we have to increase the value for MAXEXTENTS parameter.

Changed the value of MAXEXTENTS parameter in debug mode.

After maintaining the value for parameter MAXEXTENTS when we had activated the table it was activated without any error.

Few SAP tips

2010-08-01T01:34:00.000-07:00

Joyjit Ghosh, Kolkata

1. Maintain single table entry at a time without coding or debugging

Steps:

Go to SE16 transaction
Give any table name and press Enter , Ex: MARA
Now execute (F8) this screen
Choose the record you want to manipulate and display (F7)
Go to Debug mode (/H) and press ‘Enter’ 2 times
Change the value of the variable ‘CODE’. By default, it is 'SHOW'
Change the code value as 'EDIT' for modifications, 'INSR' for insert and 'DELE' for delete.

2. Maintain multiple table entries at a time without coding or debugging

Steps:

Goto transaction SE16N
Give the table name
In command box write ‘&sap_edit’ then press ‘Enter’
Press execute button

3. Debugging background job

Steps:

Goto transaction SM37
Select any job that you want to debug
Enter 'jdbg' as okcode in command box
Press ‘Enter’

Note: You can do the same from transaction SM50 as well

4. Environmental analysis of a program

Steps:

Goto Transaction SE38 and key in the program name for which you want to Environmental analysis
Press ‘SHIFT+F4’. 'Environment Analysis' pop-up-window opens.
Check the required information and press ‘Enter’

Aslo check the programs RSINCL00, RSDEPEND.

5. Start debugging from a popup window

Alernative 1:

Steps:

Create a short cut for any transaction from the SAPGUI.
Change transaction type to ‘system command’.
Enter command as ‘/h’
Save this on the desktop.
On any screen just drag and drop this shortcut
You are all set to debug now

Alternative 2 :

Steps:

Create a text file with following commands

*********************

[FUNCTION]

Command=/H

Title=Debugger

Type=SystemCommand

*********************

On any screen just drag and drop this shortcut
You are all set to debug now

6. Retrieving the deleted program

Steps:

Create a program with the same name as earlier (which is deleted)
Click on "Utilities" --> "Versions" --> "Version Management"
Select the version of your earlier program and click on display.
Your earlier program is displayed here.

7. Sending message to other user from SAP

Steps:

Go to transaction SE37
Execute the FM ‘TH_POPUP’ by mentioning the client , user name and the message text

8. Display icon in selection screen

Steps:

Find the hex code of the icon. Hex codes of all the icons are available in type-pool ‘ICON’ or available through the program ‘’ .
Now you have to create text-elements using that hex codes.

Ex: @6A@ Click

Triggering workflow event from WE19 (Inbound)

2009-11-19T01:47:00.000-08:00

Joyjit Ghosh, Kolkata.

We were trying to test a custom inbound function module where for error it triggers the workflow so that user can be send notification mails with details of the problem.

We were using transaction WE19 to test the FM, for that we had chosen Inbound function module option.

But in SWEL we had found that no event was raised by the FM.

But in our code we had populated workflow variables correctly

Also we had checked the config. and found that this FM is properly configured to raise the event INPUTERROROCCURRED.

After spending few minutes we were able to figure out the problem. We had observed that if we choose Standard Inbound option with ALE Service Check box checked then it triggers the event.

Note: Our custom inbound FM Z_IDOC_INPUT_GOODS_RECEIPT was attached with custom process code ZMIM_POGR.

SWEL:

Then what was the reason for not triggering the workflow? Reason is very simple; workflow is triggered by the ALE layer itself, without ALE layer we cannot trigger the workflow. So if you want to trigger workflow for inbound IDOC from WE19, choose Standard Inbound option with ALE Service Check box checked.

Error handling in LSMW

2009-10-23T13:21:00.000-07:00

Joyjit Ghosh, Kolkata.

To do error handling in LSMW object we can write validation logic in step “5 Maintain Field Mapping and Conversion Rule”. All custom codes written in this section will be part of the conversion program once we generate it.

Following steps are required for error handling:

Define an internal table to store all error messages
Write logic to validate the data and populate the error table when validation fails
Display error messages as part of conversion program output

All these steps should be performed under step “5 Maintain Field Mapping and Conversion Rule” from transaction LSMW.

Step 1: Define an internal table to store all error messages

In __GLOBAL_DATA__ section define the internal table that will store the error messages.

Step 2: Write logic to validate the data and populate the error table when validation fails

Now write validation logic for the fields those we want to validate. If validation fails then populate the error table and after that call the macro “SKIP_TRANSACTION” so that this error record can be skipped and control will go to next record in the file.

Step 3: Display error messages as part of conversion program output

Now at __END_OF_PROCESSING__ section write logic to display the error table.

After writing the above steps, check the syntax of the custom code by clicking the appropriate button () on application toolbar. It will display a pop-up screen where we need to press ‘Yes’ button.

If everything is OK then it will display message that conversion program is regenerated successfully.

After this follow the LSMW steps like “7 Specify Files”, “8 Assign Files”, “9 Read Data”, “10 Display Read Data”. And lastly perform the step “11 Convert Data” where SAP actually executes the validation logic (written in step “5 Maintain Field Mapping and Conversion Rule”) as part of conversion program. And display the error messages those are generated due to error handling.

Output:

Guidelines to write a good Technical Specification

2009-08-10T03:10:00.000-07:00

Joyjit Ghosh, Kolkata

Following points need to be remembered at the time of TS preparation.

If Technical Specification template contains any instruction then we need to replace them with actual content. If nothing is required to fill against that section then put N/A (Not applicable) instead.
Use consistent Font (Family and Size) throughout the document (e.g. Arial 10 or Times New Roman 10)
The Technical Specification title should follow the naming convention that is agreed with the client like :"( Type of Development) : (Description of the Development)".
Ex: Report: BOM explosion level by level.
The Technical Specification file name should have an agreed naming convention like "TS_(Short Description)". E.g. TS_BOM_Explosion.doc
Maintain Date and Version on the first page of TS
Maintain Amendment History
Maintain QA’s and Signoffs Section.
Do not add anything in “Table of contents”, only you can update the page number.
Don’t delete any section of the TS template; if no information is available for any section then put N/A instead.
Maintain contact details of the developer and functional owner
Provide all CTS numbers including dependent objects stored in other CTS.
Mention all assumptions & issues; provide closure date with issue resolution for the closed issues
Mention all technical details like Program name, Transaction name, Package name, Message class, and other repository objects correctly, they should follow the agreed naming convention
If required Table access diagram should be created where all tables along with keys fields and their relationships are drawn correctly
The flow diagram should describe the high level program flow. It should have a START node and an END node. Use the Flow Chart symbols to depict various steps.
The pseudo code should be organized in paragraphs indented properly as per the flow logic.
In the pseudo code each sentence should start with words like “Retrieve”, “Perform” etc.
Example: Retrieve the following fields from table MARA
Perform the following steps for each record of T_MARA
In the pseudo code a SELECT statement can be written as:
Retrieve the fields (Field List) from into an internal table (Say T_ITAB) using the following criteria.
In the pseudo code a LOOP statement can be written as:
Perform the following steps for each record of internal table T_ITAB.
In the pseudo code an IF statement can be written as:
Perform the following steps if is true or false.
In the pseudo code data declarations can be written as:
Declare the following variables. X1 type CHAR1
In the pseudo code calls to function module can be written as: Call the function module and pass the following parameters to the function module. The parameters can be specified in a Table format or attached as an excel document.
In the pseudo code for custom table, list of fields should be included along with the data elements, foreign key checks etc. Also Technical settings need to be specified along with Delivery and Maintenance details.
In the pseudo code mention Selection Screen Criteria along with its data type, default value, mandatory, selection screen type and validations.
Perform spelling check after the preparation of the document.
Go to document Properties and fill the Summary tab with appropriate values.
In Unit test plan (UTP) document all the test conditions appropriately
In Unit test plan (UTP) expected results should be documented clearly
In Unit test plan (UTP) test data should be given if available

Display background (water mark) image using SAPscript

2009-07-30T02:54:00.000-07:00

Joyjit Ghosh, Kolkata

Detail Steps:

Step 1: Create a standard text (transaction SO10) and insert the background image in it

Step 2: Now open the layout set (transaction SE71) in which background image needs to be displayed and do the required changes as mentioned below.

Note: Here I am using an existing custom sapscript layout where all windows, pages and page windows are already created except the background image. And for this demo I am showing the changes required for inserting the background image in the 1st page.

Goto “Page window” of the 1^st page and create another page window of type ‘MAIN’. And its attributes must be same as the existing “MAIN” window.

Now open the Text Elements of the main window in edit mode and in the 1^st line of the Sapscript editor insert the standard text (created above) that contains the background image.

Now in the 2^nd line insert the special command NEW-WINDOW

Definition of NEW-WINDOW command:

Each page can consist of up to 99 main windows. Each main window is assigned a consecutive identifying number (0..98), and the windows are filled in this order. This feature enables SAPscript to print labels and to output multi-column text. When one main window fills up, the next main window on that page is taken, if there is a next one. A page break is inserted after the last main window.

You can use the NEW-WINDOW command to call the next main window explicitly, even if the current main window is not yet full. If you are in the last main window of the page, the command has the same effect as the NEW-PAGE command

Now activate the form

Step 3: Maintain required configuration for triggering the form

Step 4: Now trigger the form and see the print preview

Result:

Form is displayed with background image in print preview.

ALE Audit

2009-07-28T23:34:00.000-07:00

Joyjit Ghosh, Kolkata.

You can configure the receiving system to generate ALE Audit messages for all incoming ALE IDocs for certain message types, and to send these messages to the sending system, where the ALE Audit toolset can use them to maintain a complete audit trail.

To enable ALE Audit:

§ Set up the ALEAUD message type in the Customer Distribution Model and Partner Profiles.

§ Define a filter object in the distribution model to specify the message type that you want to audit.

The data contained within the ALEAUD messages (IDOC type ALEAUD01) provides detailed status information on the IDocs in the receiving system, as well as the links between the IDocs and the resulting SAP application objects on the receiving system.

Audit IDoc Structure

These are the segments in an ALEAUD01 IDoc, with the fields they contain:

§ Segment E1ADHDR

o Message type

§ Segment E1STATE

o Sender’s IDoc number

o Current status

o Message fields

§ Segment E1PRTOB

o Receiver’s IDoc number

o Application object information

Two programs enable cross-system reporting.

§ RBDSTATE. This program is scheduled to run periodically on the destination system. It reports the status of incoming IDocs to the sending system, using the ALEAUD message and ALEAUD01 IDoc. This status information is recorded separately from IDoc status information in the audit logs.

§ RBDAUD01. This program is executed on the sending system. It analyzes the audit log and displays the output as a report.

Program RBDSTATE

Transaction: BDM8

Program: RBDSTATE

Use the program RBDSTATE on the receiving system to send the audit messages to the sending system, using ALE (I.e. asynchronously). You typically run this program as a scheduled batch job. The parameters of RBDSTATE are:

§ The sending system (of the original IDoc)

§ The message type

§ The date range the IDoc’s status was changed. Any IDoc having a status record in this date range will be confirmed.

The audit messages contain:

§ The current status of the inbound IDoc

§ The id of the resulting SAP application object (if the IDoc was
successfully posted)

The system will confirm up to 500 IDocs in one ALEAUD message. If
there are more than 500 IDocs to be audited, then it will create multiple
audit IDocs.

NOTE: The RBDSTATE program looks at IDoc status records to determine which IDocs to audit. If any status record was added to an IDoc during the specified date range, the program will audit the IDoc.

The RBDSTATE program returns the following statuses, from the receiving to the sending system.

Status of IDoc in receiving system	Status reported to sending system via ALEAUD
53 (Application document posted.)	41 (Application document created in receiving system.)
51 (Error: Application document not posted.)	Status 39 (IDoc is in the receiving system.) This status is repeated each time RBDSTATE is run, as long as the IDoc remains in status 51.
68 (Error: No further processing.)	40 (Application document not created in receiving system.)

Program RBDAUD01

Transaction: BDM7

Program: RBDAUD01

Use the program RBDAUD01 on the sending system to look at the ALE Audit IDoc statistics.

§ “IDocs total” is the total number of IDocs audited

§ “Queue Outbound” is the number of IDocs that have not yet been sent to the other system

§ “Queue Inbound” is the number of IDocs that are still being processed by the receiving system

§ ALE Audit records may be selected by message type, date range, etc. You can drill down into the report to see information on daily statistics, detailed information on IDocs, and cross-system links for successfully processed IDocs:

How to execute SOLMAN_DOCU_VERSION_DEL

2009-07-27T13:49:00.000-07:00

Joyjit Ghosh, Kolkata.

Program SOLMAN_DOCU_VERSION_DEL is part of Solution Manager and purpose of it is to delete versions of stored documents. To run this program successfully we need to do following things:

In tran. SOLAR02 for a project when we upload a document it is stored in folder SOLAR00 by default (see the screen shot below), we need to change it to our project folder, ex: for project SARA_TEST9 all documents should be in the folder SARA_TEST9.

It can be done by clicking button beside folder field.

Now click on change button and then SAVE the document so that SAP generates separate version for every change

Here we have changed a web link (TEST) with status NOT_STARTED (Z001).

Now run the program with value shown in the screen shot:

As result we will get the status log:

How to add new fields in dynamic selection screen

2009-05-21T01:37:00.000-07:00

Joyjit Ghosh, Kolkata.

Most of us observe that whenever a logical database is attached with a report, it automatically adds dynamic selection screen button on the report selection screen.

Ex: Transaction FBL1N

If we click on this button, it will open up a separate selection screen that can be dynamically adjusted based on the fields you choose from the left hand side folders (Function groups).

Now our requirement is to add new field in the left hand side folder (as well as in the selection screen) that is not present currently.

1^st we need to know the name of the logical database that is attached with the program.

In case of FBL1N, program name is RFITEMAP.

Go to the program’s attribute screen to know the logical database name. In our case it is KDF.

Now go to transaction SE36 and choose the menu Extras → Selection Views.

In the next screen, select Origin of view: SAP and Name of view: STANDARD, and click Display button.

This is the view that SAP uses to generate the dynamic selection screen.

Here three functional groups of fields those are available in the dynamic selections.

01 Vendor Master

02 Company code

03 Document

Each functional group contains fields from the tables that are listed on the right side (LFA1, ADDR1_VAL, etc). The field which is assigned to a functional group will be available in left hand side of the dynamic selection screen under the folder with name of the function group. Notice that for every field assigned to a functional group, there is a “Preselect” checkbox on the right. This checkbox indicates whether the relevant field should be directly available for selection.

As we want to extend the SAP-delivered dynamic selections with new fields, so we must create our own selection view. This view will have CUS as the Origin, and must be named STANDARD. To create such a view, simply use the Copy button on the top of the screen, and copy the SAP delivered view to a CUS view.

Once the customer-defined view is created then go to change mode and add new fields in the functional group.

In this case we have added the field NAME1 in functional group Vendor master (01).

Now save the view , go back to the transaction and open the dynamic selection screen. You can see the new field NAME1 is added in it.

How it works?

When a selection view with origin CUS (customer) and name STANDARD exists, and is assigned to a logical database, then this view takes precedence over the SAP-defined view. When such a view does not exist for a particular logical database, then the selection view SAP – STANDARD is used to

Display table field as checkbox in transaction SM30

2009-05-18T11:35:00.000-07:00

By Joyjit Ghosh

Scenario: To maintain a field as a checkbox in the transaction SM30 (as shown below)

Procedure:

Create a domain for the field that you want to display as checkbox in SM30, with values “X” and “ “ (blank). Or you can use an existing domain as well with the same values.

Now create a data element with this domain.

Use this data element to define the field in the actual table.

Now create table maintenance generator for this table.

Now maintain table entries from transaction SM30. In this case field ‘STATUS’ will be displayed as check box.

SE16-Table content (Before data change):

Now set the check box for any record to test that data (“X”) is updating in the underlying database table correctly.

SE16-Table content (After data change):

As shown in the above screen shot, data (“X”) is updated in the database successfully.

Debugging Active Jobs

2009-05-18T11:31:00.000-07:00

By Joyjit Ghosh

Go to the transaction SM37 and select the background job (with job status ‘Active’) that you want to debug.

Now select ‘Capture: active job’ from menu ‘Job’,

This will open the selected active job (program) in the debugger.

Also you can do the same from transaction SM50.

Select the work process where this job is running and then choose the menu path Program/ModeàProgramàDebugging.

It will display a pop up window for confirmation, click on the ‘Yes’ button.

Then you can see the job (program) in the debugger.

ALV interface check

2009-05-18T11:26:00.000-07:00

By Joyjit Ghosh

In ALV we have an option to check the interface parameters, which we are passing from our program. This check will identify any problem(s) that may occur during calling the ALV FM or ALV class method. It is advisable to perform this check before formal submission of the code to avoid any inconsistency that can lead to problem(s), even program termination in worst case. To enable this check interface parameter I_INTERFACE_CHECK of ALV FM(s) must contain ‘X’.

Example:

*&-------------------------------------------------------------*
*& Report  Z_ALV_INTERFACE_CHECK                               *
*&                                                             *
*&--------------------------------------------------------------

REPORT  z_alv_interface_check                   .

***************************************************************
* Type pool declaration for ALV
***************************************************************
TYPE-POOLS: slis.

***************************************************************
* Table
***************************************************************
TABLES: sbook.

***************************************************************
* Type declaration for SBOOK table
***************************************************************
TYPES: BEGIN OF ty_sbook,
       carrid TYPE s_carr_id, " Airline Code
       connid TYPE s_conn_id, " Flight Connection Number
       fldate TYPE s_date,    " Flight date
       bookid TYPE s_book_id, " Booking number
       customid TYPE s_customer," Customer Number
      END OF ty_sbook.

*****************************************************************
* Table declaration for SBOOK table
*****************************************************************
DATA:  i_sbook TYPE STANDARD TABLE OF ty_sbook INITIAL SIZE 0,

****************************************************************
* Table declaration for field catalog
****************************************************************
      i_fcata TYPE slis_t_fieldcat_alv.

****************************************************************
* Workarea declaration for field catalog table
****************************************************************
DATA:  w_fcata TYPE slis_fieldcat_alv.

****************************************************************
* Selection screen
**************************************************************
SELECT-OPTIONS: s_carrid FOR sbook-carrid.

***************************************************************
* Start-of-selection event
****************************************************************

* Fetch data from sbook table
PERFORM fetch_data.

* Populate field catalog
PERFORM populate_catalog.

* Display data in ALV
PERFORM display_alv.

*&--------------------------------------------------------------
*&      Form  fetch_data
*&-------------------------------------------------------------
FORM fetch_data .

  SELECT  carrid       " Airline Code
         connid       " Flight Connection Number
         fldate       " Flight date
         bookid       " Booking number
         customid " Customer Number
 FROM sbook
 INTO TABLE i_sbook
 WHERE carrid IN s_carrid.

  IF sy-subrc = 0.

    SORT i_sbook BY carrid.

  ENDIF.

ENDFORM.                    " fetch_data

*&-------------------------------------------------------------*
*&      Form  populate_catalog
*&--------------------------------------------------------------
FORM populate_catalog .

  w_fcata-fieldname = 'CARRID'.
 w_fcata-tabname  = 'I_SBOOK'.
 w_fcata-seltext_m = 'Airline Code'(001).
 w_fcata-ddictxt = 'M'.
 APPEND w_fcata to i_fcata.

  w_fcata-fieldname = 'CONNID'.
 w_fcata-tabname  = 'I_SBOOK'.
 w_fcata-seltext_m = 'Flight Connection Number'(002).
 w_fcata-ddictxt = 'M'.
 APPEND w_fcata to i_fcata.

* Wrong field name FIDATE

  w_fcata-fieldname = 'FIDATE'.
 w_fcata-tabname  = 'I_SBOOK'.
 w_fcata-seltext_m = 'Flight date'(003).
 w_fcata-ddictxt = 'M'.
 APPEND w_fcata to i_fcata.

* Wrong field name BOOKLD

  w_fcata-fieldname = 'BOOKLD'.
 w_fcata-tabname  = 'I_SBOOK'.
 w_fcata-seltext_m = 'Booking number'(004).
 w_fcata-ddictxt = 'M'.
 APPEND w_fcata to i_fcata.

  w_fcata-fieldname = 'CUSTOMID'.
 w_fcata-tabname  = 'I_SBOOK'.
 w_fcata-seltext_m = 'Customer Number'(005).
 w_fcata-ddictxt = 'M'.
 APPEND w_fcata to i_fcata.

ENDFORM.                    " populate_catalog

*&----------------------------------------------------------
*&      Form  display_alv
*&-----------------------------------------------------------
form display_alv .

data: l_repid type sy-repid.

l_repid = sy-repid.

* Interface check parameter, we have to pass ‘X’ as value in this parameter

CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
  I_INTERFACE_CHECK              = 'X'
  I_CALLBACK_PROGRAM             = l_repid
  IT_FIELDCAT                    = i_fcata
 TABLES
   t_outtab                       = i_sbook
EXCEPTIONS
  PROGRAM_ERROR                  = 1
  OTHERS                         = 2
         .
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

endform.                    " display_alv

Selection screen:

Output:

Additional screen (before showing the final output) to show the error or warning or success message(s)

Also various buttons are present on the application tool bar to check contents of Fieldcatalog, Layout, Sort, Filter, Events, Variant, and Special Fieldgroup.

Fieldcatalog:

Layout:

Sort:

Filter:

Event:

Variant:

Field group:

From the initial screen if we press back button then it will display the final output.

Final output:

Note:

Always remember to switch off this check before formal code delivery otherwise these extra screen(s) can confuse the end user.
In ECC 5.0, I have seen that this check does not work with FM REUSE_ALV_GRID_DISPLAY, in that case we need to convert grid to list temporarily to implement this check.

Scheduling background jobs by triggering events

2009-05-18T11:18:00.000-07:00

By Joyjit Ghosh

Step1: Create event from transaction SM62.

Give event name and description and press save button

Step2: Create a program that triggers this event by calling the FM ‘BP_EVENT_RAISE’.

*&---------------------------------------------------------------------*
*& Report  Z_TRIGGER_EVENT                                             *
*&                                                                     *
*&---------------------------------------------------------------------*
*&                                                                     *
*&                                                                     *
*&---------------------------------------------------------------------*

REPORT  Z_TRIGGER_EVENT                         .

CALL FUNCTION 'BP_EVENT_RAISE'
EXPORTING
  eventid                      = 'Z_TRIGGER_JOB'
EXCEPTIONS
 BAD_EVENTID                  = 1
 EVENTID_DOES_NOT_EXIST       = 2
 EVENTID_MISSING              = 3
 RAISE_FAILED                 = 4
 OTHERS                       = 5
        .
IF sy-subrc <> 0.
Write: 'Event failed to trigger'.
else.
Write: 'Event triggered'.
ENDIF.

Step3: Configure the background job from transaction SM36.

In the initial screen give job name and job class and press “Start condition” button.

In the popup screen press “After event” button and give the event name and then press save button.

Now go back to the initial screen and press “Step” button

Provide program and variant name and after providing all the values press save button.

In the initial screen press save button.

Step4: Now execute the program to trigger the event and as well check the background job.

Run transaction SM37

Check the status of job defined above

Now check the spool to see the generated list

Test User-exit without creating a project

2009-05-18T11:13:00.000-07:00

by Joyjit Ghosh

This tip will show us how to test user-exit from SMOD without creating any project.

Go to SMOD and check the enhancement.

For example, here we are checking the enhancement SEUED001. Now press Test button.

Now put the cursor on an exit FM and press select component button.

Now create the include program.

Insert a break point in it.

Now go back to the test screen and press activate button.

It will activate the enhancement without creating any project.

Now press the execute button and enter the transaction for which this user exit may trigger.

As shown below user exit is triggered from SE38.

After the testing you should de-activate the exit and delete the include program created above.

Go back to the test screen. And press the Undo activation button.

You will get the following message

Now delete the include program created earlier. Press the Delete Test Objects button

In the next popup select the include program and press ok button.

Now press Yes button

It will display the following message

Now to crosscheck whether the include program is really deleted or not, select the exit and again press button. And in the next screen double click on the include name and then press enter.

It will display the pop up which confirms that include program does not exist.

Printing ALV along with Page numbers

2009-05-18T11:07:00.000-07:00

By Joyjit Ghosh

Expected Layout of the ALV report (when printing):

Step 1: Display each new document in a new page

To achieve this below routine is written to populate the IT_SORT table parameter of ALV function module REUSE_ALV_GRID_DISPLAY. And ALV will automatically insert page break whenever a new document is encountered.

CONSTANTS:    
c_spos        TYPE SLIS_SPOS   VALUE '01',     " Column position
c_up          TYPE SLIS_SOUP   VALUE 'X',      " Sorting order
c_table       TYPE tabname     VALUE 'I_FINAL'," Name of o/p table
c_group       TYPE SLIS_CTRLS  VALUE '*',      " Sorting group
c_fld2        TYPE fieldname   VALUE 'IDCNGA04-IDCN037'." Field name(Document no)

* Prepare sort table
 PERFORM prepare_sort_table CHANGING i_sort[].

FORM prepare_sort_table CHANGING pi_sort TYPE slis_t_sortinfo_alv.

  CLEAR st_sort.
 st_sort-spos      = c_spos.     " Sort sequence
 st_sort-fieldname = c_fld2.     " Document no
 st_sort-tabname   = c_table.    " Table name
 st_sort-up        = c_up.       " Ascending
 st_sort-group     = c_group.    " Group

* Populate sort table
 APPEND st_sort TO pi_sort.

ENDFORM.                    "prepare_sort_table

Step 2: Reset page number to 1 for each new document

From ALV function module we cannot control the page numbers as it will automatically increment the page counter whenever a new page is printed. So to achieve this we have written our custom code within the TOP_OF_PAGE routine.

Register TOP_OF_PAGE routine with the TOP_OF_PAGE event in IT_EVENTS table parameter of the ALV function module.

* Prepare event table
 PERFORM prepare_event_table.

FORM prepare_event_table .

* Populate top-of-page event
 st_event-name = slis_ev_top_of_page.
 st_event-form = slis_ev_top_of_page.
 APPEND st_event TO i_event.

  CLEAR st_event.

ENDFORM.                    " prepare_event_table

Custom code to control the page number in TOP_OF_PAGE routine

Code block marked in bold are used to control the page number. As in our case we are using ALV grid to display the report so during report display page number is not visible. It is only visible in print preview or at the time of printing.

FORM top_of_page.

* Local variable declaration
 STATICS: l_comm  TYPE syucomm.  " Store user command

* Declaration of local variables
 DATA: l_line_size  TYPE sylinsz,           " Line size
       l_line       TYPE slis_listheader,   " Hold list header
       l_currdoc    TYPE idcn037,           " Current doc.
       l_currtabix  TYPE sytabix.           " Current index

* Check for print or print preview
 IF ( sy-ucomm = c_prin OR
 sy-ucomm = c_rnt_prev OR
 sy-ucomm = c_rnt ).

    IF l_comm <> sy-ucomm.
     CLEAR : g_page_cnt.

    ENDIF. " l_comm <> sy-ucomm

*   Store current table index
   l_currtabix  = sy-tabix.
   CLEAR st_final.

*   If current index is 1 then start page numbering from 1
   IF l_currtabix = 1.

*     Read 1st record and store the document no
     READ TABLE i_final INDEX l_currtabix INTO st_final.
     g_prevdoc = st_final-idcnga04-idcn037.

*     Start page numbering from 1
     g_page_cnt =  1.
     g_prevtabix = 1.

    ELSE.

*     Read the table line
     READ TABLE i_final INDEX l_currtabix INTO st_final.

*     Store the current document
     l_currdoc = st_final-idcnga04-idcn037.

*     If the current doc. is same as previou doc.
*     increament the page no, otherwise start it from 1
     IF l_currdoc = g_prevdoc.

*       Increament the page no
       g_page_cnt = g_page_cnt + 1.
     ELSE.

*       Start page from 1
       g_page_cnt =  1.

*       Store current doc. as previous doc.
       g_prevdoc = l_currdoc.

      ENDIF. " l_currdoc = g_prevdoc

    ENDIF. " l_currtabix = 1

  ENDIF. " sy-ucomm = c_prin OR

  IF g_page_cnt = 1.

*   Store the user command
   l_comm = sy-ucomm.

  ENDIF. " g_page_cnt = 1

* Display page no
 IF g_page_cnt > 0 .

*  Store the report width
   l_line_size = sy-linsz.

*  Calculate position
   l_line_size = l_line_size - 10.

*  Display page no
   WRITE AT l_line_size 'Page no:'(021).

*  Calculate position
   l_line_size = l_line_size + 5.

    WRITE AT l_line_size g_page_cnt.

  ENDIF. " g_page_cnt > 0

  REFRESH st_list_top_of_page.

* Populate company name
 CLEAR l_line.
 l_line-typ  = c_typ.
 l_line-info = g_comp_name.
 APPEND l_line TO st_list_top_of_page.

* Populate heading
 CLEAR l_line.
 l_line-typ  = c_typ.
 l_line-info = text-020.
 APPEND l_line TO st_list_top_of_page.

* At the time of printing or print preview display additional info
* on 1st page
 IF g_page_cnt = 1 AND
   ( sy-ucomm = c_prin OR
     sy-ucomm = c_rnt_prev OR
     sy-ucomm = c_rnt ).

    CLEAR l_line.
   l_line-typ  = 'A'.

*   Populate Staff name
   CONCATENATE text-017
               st_final-idcnga04-idcn053
               INTO l_line-info
               SEPARATED BY ':'.
   APPEND l_line TO st_list_top_of_page.

    CLEAR l_line.
   l_line-typ  = 'A'.

*   Populate Accountant
   CONCATENATE text-018
               '______________________'
               INTO l_line-info
               SEPARATED BY ':'.

    APPEND l_line TO st_list_top_of_page.

    CLEAR l_line.
   l_line-typ  = 'A'.

*   Populate Book keeper
   CONCATENATE text-019
               '______________________'
               INTO l_line-info
               SEPARATED BY ':'.

    APPEND l_line TO st_list_top_of_page.

    l_line-typ  = 'A'.
   l_line-info = space.
   APPEND l_line TO st_list_top_of_page.

  ENDIF.

* Display list header
 CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
   EXPORTING
     i_logo             = space
     it_list_commentary = st_list_top_of_page.

* No sy-subrc check is required

ENDFORM.                    " top_of_page

Step 3: Display report

Display the ALV report using 'REUSE_ALV_GRID_DISPLAY' function module.

  CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
     i_callback_program      = l_prog         " Call back progrm
     it_fieldcat             = i_fieldcat_msg " Field catalog
     is_layout               = st_layout      " Layout
     it_sort                 = i_sort[]       " Sort table
     i_save                  = c_save         " 'A'
     is_variant              = l_variant      " ALV variant
     it_events               = i_event        " ALV events
     is_print                = st_print       " Print parameters
   TABLES
     t_outtab                = i_final        " Output table
   EXCEPTIONS
     program_error           = 1
     OTHERS                  = 2.

Result:

Report is displayed in ALV grid. Note that no page number is displayed. Now press the print preview button

Report is displayed in print preview with page numbers.

Limitations:

For positioning the page number in the report we have to calculate the position based on the list width. As in this case we are using the formula

Page number position = sy-linsz – 10. But if you want you can change it.

2. In print preview only 1^st page number is visible for every document i.e. if a document spreading multiple pages
only the 1^st page number will be visible. You can see all the page numbers at the time of actual printing.

ALV with EDIT and SAVE functionality

2009-05-18T11:05:00.000-07:00

By Joyjit Ghosh.

Code:

REPORT z_demo_alv_jg.

*******************************************************************
* TYPE-POOLS                                                      *
*******************************************************************
TYPE-POOLS: slis.

*******************************************************************
* INTERNAL TABLES/WORK AREAS/VARIABLES     *
*******************************************************************
DATA: i_fieldcat TYPE slis_t_fieldcat_alv,
     i_index TYPE STANDARD TABLE OF i WITH HEADER LINE,
     w_field TYPE slis_fieldcat_alv,
     p_table LIKE dd02l-tabname,
     dy_table TYPE REF TO data,
     dy_tab TYPE REF TO data,
     dy_line TYPE REF TO data.

*******************************************************************
* FIELD-SYMBOLS                                                   *
*******************************************************************
FIELD-SYMBOLS:  TYPE STANDARD TABLE,
               TYPE ANY,
               TYPE ANY,
               TYPE STANDARD TABLE.

*******************************************************************
* SELECTION SCREEN                                                *
*******************************************************************
PARAMETERS: tabname(30) TYPE c,
           lines(5)  TYPE n.

*******************************************************************
* START-OF-SELECTION                                              *
*******************************************************************
START-OF-SELECTION.

* Storing table name
 p_table = tabname.

* Create internal table dynamically with the stucture of table name
* entered in the selection screen
 CREATE DATA dy_table TYPE STANDARD TABLE OF (p_table).
 ASSIGN dy_table->* TO .
 IF sy-subrc <> 0.
   MESSAGE i000(z_zzz_ca_messages) WITH ' No table found'.

    LEAVE TO LIST-PROCESSING.
 ENDIF.
* Create workarea for the table
 CREATE DATA dy_line LIKE LINE OF .
 ASSIGN dy_line->* TO .

* Create another temp. table
 CREATE DATA dy_tab TYPE STANDARD TABLE OF (p_table).
 ASSIGN dy_tab->* TO .

  SORT i_fieldcat BY col_pos.

* Select data from table
 SELECT * FROM (p_table)
 INTO TABLE 
 UP TO lines ROWS.

  REFRESH .

* Display report
 CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
   EXPORTING
     i_callback_program       = sy-repid
     i_structure_name         = p_table
     i_callback_user_command  = 'USER_COMMAND'
     i_callback_pf_status_set = 'SET_PF_STATUS'
   TABLES
     t_outtab                 = 
   EXCEPTIONS
     program_error            = 1
     OTHERS                   = 2.

  IF sy-subrc <> 0.

  ENDIF.

*&-----------------------------------------------------------------*
*&      Form  SET_PF_STATUS
*&-----------------------------------------------------------------*
*       Setting custom PF-Status
*------------------------------------------------------------------*
*      -->RT_EXTAB   Excluding table
*------------------------------------------------------------------*
FORM set_pf_status USING rt_extab TYPE slis_t_extab.

  SET PF-STATUS 'Z_STANDARD'.

ENDFORM.                    "SET_PF_STATUS

*&----------------------------------------------------------------*
*&      Form  user_command
*&-----------------------------------------------------------------*
*       Handling custom function codes
*------------------------------------------------------------------*
*      -->R_UCOMM      Function code value
*      -->RS_SELFIELD  Info. of cursor position in ALV
*------------------------------------------------------------------*
FORM user_command  USING    r_ucomm LIKE sy-ucomm
              rs_selfield TYPE slis_selfield.

* Local data declaration
 DATA: li_tab TYPE REF TO data,
       l_line TYPE REF TO data.

* Local field-symbols
 FIELD-SYMBOLS: TYPE table,
                 TYPE ANY.

* Create table
 CREATE DATA li_tab TYPE STANDARD TABLE OF (p_table).
 ASSIGN li_tab->* TO .

* Create workarea
 CREATE DATA l_line LIKE LINE OF .
 ASSIGN l_line->* TO .

  CASE r_ucomm.

*   When a record is selected
   WHEN '&IC1'.

*     Read the selected record
     READ TABLE  ASSIGNING  INDEX
     rs_selfield-tabindex.

      IF sy-subrc = 0.

*       Store the record in an internal table
       APPEND  TO .

*       Fetch the field catalog info
       CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
         EXPORTING
           i_program_name         = 'Z_DEMO_PDF_JG'
           i_structure_name       = p_table
         CHANGING
           ct_fieldcat            = i_fieldcat
         EXCEPTIONS
           inconsistent_interface = 1
           program_error          = 2
           OTHERS                 = 3.
       IF sy-subrc = 0.

*         Make all the fields input enabled except key fields
         w_field-input = 'X'.

          MODIFY i_fieldcat FROM w_field TRANSPORTING input
         WHERE key IS INITIAL.

        ENDIF.

*       Display the record for editing purpose
       CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
         EXPORTING
           i_callback_program    = sy-repid
           i_structure_name      = p_table
           it_fieldcat           = i_fieldcat
           i_screen_start_column = 10
           i_screen_start_line   = 15
           i_screen_end_column   = 200
           i_screen_end_line     = 20
         TABLES
           t_outtab              = 
         EXCEPTIONS
           program_error         = 1
           OTHERS                = 2.

        IF sy-subrc = 0.

*         Read the modified data
         READ TABLE  INDEX 1 INTO .

*         If the record is changed then track its index no.
*         and populate it in an internal table for future
*         action
         IF sy-subrc = 0 AND  <> .
            = .
           i_index = rs_selfield-tabindex.
           APPEND i_index.
         ENDIF.
       ENDIF.

      ENDIF.

*   When save button is pressed
   WHEN 'SAVE'.

*     Sort the index table
     SORT i_index.

*     Delete all duplicate records
     DELETE ADJACENT DUPLICATES FROM i_index.

      LOOP AT i_index.

*       Find out the changes in the internal table
*       and populate these changes in another internal table
       READ TABLE  ASSIGNING  INDEX i_index.
       IF sy-subrc = 0.
         APPEND  TO .
       ENDIF.

      ENDLOOP.

*     Lock the table
     CALL FUNCTION 'ENQUEUE_E_TABLE'
       EXPORTING
         mode_rstable   = 'E'
         tabname        = p_table
       EXCEPTIONS
         foreign_lock   = 1
         system_failure = 2
         OTHERS         = 3.

      IF sy-subrc = 0.

*       Modify the database table with these changes
       MODIFY (p_table) FROM TABLE .

        REFRESH .

*       Unlock the table
       CALL FUNCTION 'DEQUEUE_E_TABLE'
         EXPORTING
           mode_rstable = 'E'
           tabname      = p_table.

      ENDIF.
 ENDCASE.

  rs_selfield-refresh = 'X'.

ENDFORM.                    "user_command

Selection screen:

Output:

Passing table data to the layout without changing the driver program

2009-05-18T10:59:00.000-07:00

By Joyjit Ghosh

I have seen a typical requirement from client that SAP script layout need to be changed (additional data need to be displayed) without modifying the driver program (mainly standard SAP program). This tip will show us how to pass table data (multiple records at a time) to layout without changing the driver program.

Step1. Create a standard text from SO10.

Create a blank standard text. This will store the table data

Step2. Create a subroutine pool and a routine in it that can be called from SAP script.

From transaction SE38 create a subroutine pool.

Now create subroutine with proper interface to fetch the data from the table.

Step3. Within this routine write the logic to fetch the table data and populate the standard text.

***************************************************************
* Fetch table data and upload the data in proper format to the
* standard text
***************************************************************
DATA: i_zemployee TYPE STANDARD TABLE OF zemployee INITIAL SIZE 0,
      w_zemployee TYPE zemployee,
      i_text TYPE STANDARD TABLE OF tline INITIAL SIZE 0,
      w_header LIKE  thead,
      w_text TYPE tline.
CONSTANTS: c_par  TYPE char2 VALUE ',,'. " Sign for tabs

* Fetch data for employee
SELECT * FROM zemployee
INTO TABLE i_zemployee.

  IF sy-subrc = 0.

*  Create text table
  LOOP AT i_zemployee INTO w_zemployee.

*     Store default paragraph format
    w_text-tdformat = '*'.

*     Add all the required fields separated by tab
    CONCATENATE w_zemployee-empno  w_zemployee-empname
    INTO w_text-tdline
    SEPARATED BY c_par.

*     Store table data
    APPEND w_text TO i_text.

    ENDLOOP.

    check sy-subrc = 0.

*   Populate header info

*   Text object
  w_header-tdobject = 'TEXT'.

*   Standard text name
  w_header-tdname = 'Z_TABLE_DATA'.

*   Text id
  w_header-tdid = 'ST'.

*   Language
  w_header-tdspras = 'E'.

*  Populate the standard text with table data
  CALL FUNCTION 'SAVE_TEXT'
    EXPORTING
      header                = w_header
      insert                = 'X'
      savemode_direct       = 'X'
    TABLES
      lines                 = i_text
   EXCEPTIONS
     id                    = 1
     language              = 2
     name                  = 3
     object                = 4
     OTHERS                = 5
            .
  IF sy-subrc <> 0.

    ENDIF.

  ENDIF.

Step4. Call the routine and standard text from the SAP script layout.

Note: For the sake of simplicity this tip is shown in a custom layout that is called from a custom report.

/*   Call the routine
/:   PERFORM FETCH_TABLE_DATA  IN PROGRAM Z_SUBROUTINE_POOL
/:   USING &INVAR1&
/:   CHANGING &OUTVAR1&
/:   ENDPERFORM

/*   Now call the standard text
/:   INCLUDE Z_TABLE_DATA OBJECT TEXT ID ST LANGUAGE EN

Step5. Test the SAP script form

Activate the SAP script debugger

Run the custom report to test the SAPscript layout.

*&---------------------------------------------------------------*
*& Report  Z_TEST_SAPCSRIPT                                            *
*&---------------------------------------------------------------*

REPORT  Z_TEST_SAPCSRIPT                        .

start-of-selection.

CALL FUNCTION 'OPEN_FORM'
EXPORTING
 DEVICE                            = 'PRINTER'
 DIALOG                            = 'X'
 FORM                              = 'Z_DEMO_LAYOUT'
 LANGUAGE                          = SY-LANGU
EXCEPTIONS
 CANCELED                          = 1
 DEVICE                            = 2
 FORM                              = 3
 OPTIONS                           = 4
 UNCLOSED                          = 5
 MAIL_OPTIONS                      = 6
 ARCHIVE_ERROR                     = 7
 INVALID_FAX_NUMBER                = 8
 MORE_PARAMS_NEEDED_IN_BATCH       = 9
 SPOOL_ERROR                       = 10
 CODEPAGE                          = 11
 OTHERS                            = 12
        .
IF sy-subrc = 0.
CALL FUNCTION 'WRITE_FORM'
EXPORTING
 ELEMENT                        = '001'
 FUNCTION                       = 'SET'
 TYPE                           = 'BODY'
 WINDOW                         = 'MAIN'
* IMPORTING
*   PENDING_LINES                  =
EXCEPTIONS
 ELEMENT                        = 1
 FUNCTION                       = 2
 TYPE                           = 3
 UNOPENED                       = 4
 UNSTARTED                      = 5
 WINDOW                         = 6
 BAD_PAGEFORMAT_FOR_PRINT       = 7
 SPOOL_ERROR                    = 8
 CODEPAGE                       = 9
 OTHERS                         = 10
        .
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

 CALL FUNCTION 'CLOSE_FORM'
EXCEPTIONS
  UNOPENED                       = 1
  BAD_PAGEFORMAT_FOR_PRINT       = 2
  SEND_ERROR                     = 3
  SPOOL_ERROR                    = 4
  CODEPAGE                       = 5
  OTHERS                         = 6
         .
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

ENDIF.

After execution of this report SAPscript debugger is triggered.

As shown below layout is calling the code written in the routine

Standard text is populated with the data fetched from table

Output of SAP script:

Table entries:

Create Dynamic Patterns

2009-05-18T10:52:00.000-07:00

By Joyjit Ghosh

Step1. Create a pattern with only one line that contains *$&$EXIT.

Put this above expression and press save button.

Step2. Now from CMOD create a project and include enhancement SEUED001 in it.

Now select the user exit EXIT_SAPLLOCAL_EDT1_001 and create the include program in it.

Now insert the following code block in the include program and activate it.

*&---------------------------------------------------------------------*
*&  Include           ZXSEUU26                                         *
*&---------------------------------------------------------------------*

DATA: w_buffer TYPE string.

CASE keyword.

  WHEN 'DYNAMIC_PATTERN'.

    w_buffer =
'*********************************************************************'.
APPEND w_buffer TO buffer.
w_buffer = '*& Program           :'.
APPEND w_buffer TO buffer.
w_buffer = '*& Module            :'.
APPEND w_buffer TO buffer.
w_buffer = '*& Sub-Module        :'.
APPEND w_buffer TO buffer.
w_buffer = '*& Functional Contact:'.
APPEND w_buffer TO buffer.
w_buffer = '*& Funct. Spec. Ref. :'.
APPEND w_buffer TO buffer.
w_buffer = '*& Developer(Company):'.
APPEND w_buffer TO buffer.
w_buffer = '*& Create Date       :'.
APPEND w_buffer TO buffer.
w_buffer = '*& Program Type      :'.
APPEND w_buffer TO buffer.
w_buffer = '*& Project Phase     :'.
APPEND w_buffer TO buffer.
w_buffer = '*& Description       :'.
APPEND w_buffer TO buffer.
w_buffer =
'*********************************************************************'.
APPEND w_buffer TO buffer.

  WHEN OTHERS.

* Do nothing
ENDCASE.

Lastly activate the project

Step3. Insert this newly created pattern in a program and test whether it is displaying the dynamic pattern or not.

SAP code to call the user-exit.

User-exit call

Dynamic pattern

Find transaction for table maintenance generator

2009-02-11T06:37:00.000-08:00

By Joyjit Ghosh,
Kolkata,

India

Sometime we only know that a table has a table maintenance generator but does not have any idea whether any transaction is attached with it or not. To find that go to table TSTCP and in the selection screen against PARAM field give the following string:

*SM30 VIEWNAME=@Table in question@*

Here replace

@Table in question@ by actual table name.

For example if we are searching transaction for table T001CM then resultant string would be:

*SM30 VIEWNAME=T001CM*

Now press execute button, if any transaction is available then it will show the transaction name.

In our case it is “OBZK”.

Note: if you donot find the transaction by using above string then use the table name in lower case (t001cm)in the string and try to search again.

Ex: *SM30 VIEWNAME=t001cm*

Store internal table content in local file during debugging in 4.6c

2009-01-26T07:40:00.001-08:00

By Joyjit Ghosh,
Kolkata, India.

In 4.6C there is no direct option provided in the debugger to store internal table content in local file as it is there from release 6.20 onwards (see the screen shot below).

This tip will show us how to achieve the same in release 4.6C.

Step1: When you are in debugging mode press the table push button. And enter the internal table name. Place the cursor on the table field.

Step 2: Go to the “Goto” menu. Choose ”Display data object” sub-menu. And from the Sub-menu Choose “Structure Editor”.

Step 3: When we press the ‘Structure editor’ sub-menu, screen with title “Structure editor: change [table name] from entry 1” is displayed, where all the contents of the internal table is displayed as a list. Here if we want we can add /delete/modify new rows.

Step 4: Here our main objective is to download the contents of the internal table. To accomplish this go to “Object” menu and select “Display entire list” sub-menu.

Step 5: Now go to System -> List -> Save -> Local file sub-menu.

Step 6: A pop-up screen is appeared to ask ’In which format should the list be saved?’ Just press OK button.

Step 7: When OK button is pressed again a pop-up screen is appeared where the file name has to be given. After providing the file name, press ‘Transfer’ button.

Step 8: Now if we open the file then we can see that the content of the internal table is stored in the following format. This facility will save us from tedious work of researching the internal table contents from within the ABAP debugger as we can now use a user-friendly tool (like Microsoft Excel, Notepad etc.) to check the data in the file itself.

Set up business events to update custom tables from a Standard Transaction

2009-01-26T01:41:00.000-08:00

By Joyjit Ghosh,
Kolkata, India.

At times the business requirement demands that if the user changes some data from a standard SAP transaction, the same will be noted down in some form and subsequently a daily batch job will pick up that information and will send to another system. One way to achieve this type of requirement is to have the business events set up for this standard transaction in question (provided that transaction calls the business events in it). There are a number of business events declared in a SAP system that may be of use. The transaction is BF34 where we need to configure the business events.

Step-1

In the BF34 transaction, SAP provides the opportunity to configure the Business events and the corresponding function modules:

There is a F4 drop down help available for these business events as shown below:

One can easily choose the business events from this drop down box.

For every event number one corresponding function module exists.

Step-2

The function module SAMPLE_INTERFACE_00001340 is a function module template that needs to be copied as a Z-function module and then altered so that the desired functionality can be achieved. Please see the following screenshots for details:

The existing template:

Please note that this function module contains all the details about the relevant data as importing parameters. The example above is relevant to the event no. 00001340, which is ‘Customer Master data: Final checks’. All data corresponding to this transaction is available within this function module. The idea is to create a custom function module by copying this template function module and then add additional code in that to get the desired functionality.

A real life scenario:

A typical case can be monitoring the customer hierarchy (tcodeVDH1N) for any create/change/delete in the hierarchy relationship. This is important when the client decides that he/she will use non-SAP software (e.g. I-MANY) to monitor the rebate amount distribution. This is a primary requirement for the I-MANY software that the customer hierarchy relationship is in sync with SAP.

The business events for the customer hierarchy create/change/delete are as below: -

These events are configured in the BF34 transaction as below: -

Using transaction BF24 we can create the “Product” as shown below:

The requirement was to write down the create/change/delete information for the customer hierarchy in three different custom tables with the Higher-level customer number and the validity start, end dates. The Z_CS_LOG_CH_CREATE,Z_CS_LOG_CH_CHANGE, Z_CS_LOG_CH_DELETE function modules accomplishes the same.

How does this work?

In the standard SAP transaction VDH1N, the standard code issues outbound function calls as below: -

For the creationà the outbound call is made for the business event 00504004

For the change à the outbound call is made for the business event 00504005

For the deletionà the outbound call is made for the business event 00504006

These events have been set up in the configuration as shown above. So, whenever there is a change in the customer hierarchy by the standard SAP transaction, the same is being logged by these custom function modules via the business events.

There is a separate program, which is scheduled to run once daily, which picks up the information for the day it is running, from these custom tables and sends Idocs to the non-SAP system.

Create transaction on a class method

2008-11-22T02:15:00.000-08:00

By Joyjit Ghosh,
Kolkata, India.

In this demo I am going to show how to create transaction on a local class method.

Step1: First create a local class in a report from transaction SE38.

REPORT z_demo_oop_jg .

*---------------------------------------------------------------------*
* CLASS create_report DEFINITION
*---------------------------------------------------------------------*
*
*---------------------------------------------------------------------*

CLASS create_report DEFINITION.

PUBLIC SECTION.

METHODS: main.

PRIVATE SECTION.

DATA: i_data TYPE STANDARD TABLE OF sbook INITIAL SIZE 0.

METHODS: fetch_data,

display_data.

ENDCLASS. "create_report DEFINITION

*---------------------------------------------------------------------*
* CLASS create_report IMPLEMENTATION
*---------------------------------------------------------------------*
*
*---------------------------------------------------------------------*

CLASS create_report IMPLEMENTATION.

METHOD fetch_data.

* Select 100 records from SBOOK table

SELECT * FROM sbook

INTO TABLE i_data

UP TO 100 ROWS.

ENDMETHOD. "fetch_data

METHOD display_data.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

i_structure_name = 'SBOOK'

TABLES

t_outtab = i_data

EXCEPTIONS

program_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

ENDMETHOD. "display_data

METHOD main.

fetch_data( ).

display_data( ).

ENDMETHOD. "main

ENDCLASS. "create_report IMPLEMENTATION

Step2. Now from transaction SE93 create a transaction for the method MAIN as shown in the screen shots given below:

Give a transaction name and press create button.

In the next screen give a description and choose the proper radio button

In the next screen provide report name (where the local class is defined), local class name and method name.

Now save the transaction and execute it.
In this case it will display the report.

This technique can be used to call a method (local class) from another program using statement: call transaction.

EX: call transaction 'Z_OOP'.

Note: In the same way you can create a transaction on method of a global class.

Problem with system refresh

2008-11-22T01:37:00.000-08:00

By Joyjit Ghosh,
Kolkata, India.

Problem :

In few cases I have seen that after system refresh custom codes developed in the original system are not editable. This problem mainly happens in a landscape which contains two parallel paths one dedicated to development and another one for maintaining the old code. After a certain point in development cycle it is important to make the 2 paths in sync with each other and that’s why we have to refresh one system by the other. And after this refresh this problem may arise.

Solution:

From the above message you can get a hint and based on it you can check the original system name of this program from the menu path (Goto à Object directory) shown below

In this case original system name is different than the current system (BSP) name. This is happened because of system refresh. As code is refreshed from BT1 to BSP; due to this original system name is also changed to BT1 from BSP. And now SAP is considering BT1 as the original system that’s why it is showing this above message and not permitting to edit the program directly.

So to avoid this problem we need to manually change the original system from BT1 to BSP.

Go to transaction SE03. Set the first check box and give the program name to its corresponding text box and press execute button.

In the next screen select program entry and press the change object directory button.

In the next popup screen change the original system and press save button.

You will get the following message:

Now you can edit the program without any problem

Display footer info in ALV Grid

2008-10-22T07:54:00.000-07:00

By Joyjit Ghosh.

Steps:

Step1: Populate the ALV event table with 'END_OF_LIST' event

Step2: Populate the footer text in to an internal table which is of type

slis_t_listheader.

Step3: Create a subroutine with name 'END_OF_LIST' and with in this form we have to call the function module ‘REUSE_ALV_COMMENTARY_WRITE’.

Step4: Now call the function module REUSE_ALV_GRID_DISPLAY’ to display the ALV report. Whenever ‘END_OF_LIST' event is get fired it executes the subroutine END_OF_LIST and displays the text into the footer of the ALV GRID.

Code:

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

*& Report Z_TEST_ALV

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

REPORT z_test_alv.

TYPE-POOLS: slis.

DATA: i_mara TYPE STANDARD TABLE OF mara INITIAL SIZE 0.

DATA i_events TYPE slis_t_event.

DATA: i_end_of_page TYPE slis_t_listheader.

DATA: w_events TYPE slis_alv_event.

DATA: v_repid LIKE sy-repid.

START-OF-SELECTION.

SELECT * FROM

mara INTO TABLE i_mara

UP TO 100 ROWS.

CHECK sy-subrc = 0.

PERFORM populate_alv_event.

PERFORM comment_build USING i_end_of_page[].

PERFORM display_grid.

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

*& Form POPULATE_ALV_EVENT

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

FORM populate_alv_event .

* Populate event table

w_events-name = 'END_OF_LIST'.

w_events-form = 'END_OF_LIST'.

APPEND w_events TO i_events.

ENDFORM. " POPULATE_ALV_EVENT

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

*& Form COMMENT_BUILD

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

FORM comment_build USING p_i_end_of_page TYPE slis_t_listheader.

DATA: ls_line TYPE slis_listheader.

REFRESH p_i_end_of_page.

CLEAR ls_line.

ls_line-typ = 'H'.

ls_line-info = 'This is end of list'(001).

APPEND ls_line TO p_i_end_of_page.

ENDFORM. " COMMENT_BUILD

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

*& Form end_of_list

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

FORM end_of_list.

CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'

EXPORTING

it_list_commentary = i_end_of_page.

ENDFORM. "end_of_list

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

*& Form DISPLAY_GRID

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

FORM display_grid .

v_repid = sy-repid.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

i_callback_program = v_repid

i_structure_name = 'MARA'

it_events = i_events

TABLES

t_outtab = i_mara

EXCEPTIONS

program_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

ENDIF.

ENDFORM. " DISPLAY_GRID

Output:

Go to any page of a list directly form selection screen

2008-09-25T02:08:00.001-07:00

By Joyjit Ghosh,
Kolkata, India.

Code:

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

*& Report Z_DEMO_JG

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

*& Go to any page of a list directly form selection screen

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

REPORT z_demo_jg LINE-SIZE 80 LINE-COUNT 50

NO STANDARD PAGE HEADING.

TABLES: sflight.

* Type declaration

TYPES : BEGIN OF ty_flight,

carrid(19) TYPE c,

connid(18) TYPE c,

fldate LIKE sflight-fldate,

fldate1(14) TYPE c,

planetype(13) TYPE c,

END OF ty_flight.

* Data declaration

DATA: i_flight TYPE STANDARD TABLE OF ty_flight,

w_flight TYPE ty_flight.

DATA: field(50) TYPE c.

DATA: part1(30) TYPE c,

part2(30) TYPE c.

DATA: l_counter TYPE i.

* Selection screen

SELECT-OPTIONS: s_carrid FOR sflight-carrid.

PARAMETERS: p_page TYPE int3.

START-OF-SELECTION.

* Fetch data from sflight table

SELECT carrid

connid

fldate

planetype

FROM sflight

INTO CORRESPONDING FIELDS OF TABLE i_flight

WHERE carrid IN s_carrid.

CHECK sy-subrc = 0.

* Display final data

PERFORM display_data.

TOP-OF-PAGE.

* Display report header

PERFORM display_column_name.

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

*& Form display_column_name

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

* Display column header

*----------------------------------------------------------------------*

* None

*----------------------------------------------------------------------*

FORM display_column_name .

WRITE: /10 'Program name:', sy-repid.

WRITE: /10 'Page no:', sy-pagno.

* Store report header texts

w_flight-carrid = 'Airline Code'(001).

w_flight-connid = 'Flight Connection'(002).

w_flight-fldate1 = 'Flight date'(003).

w_flight-planetype = 'Aircraft Type'(004).

* Display report header

SKIP.

ULINE.

FORMAT INTENSIFIED ON COLOR 1.

WRITE: 1 sy-vline,

2 w_flight-carrid,

21 sy-vline,

22 w_flight-connid,

40 sy-vline,

41 w_flight-fldate1,

55 sy-vline,

56 w_flight-planetype,

80 sy-vline.

ULINE.

ENDFORM. " display_column_name

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

*& Form display_data

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

* Display flight data

*----------------------------------------------------------------------*

* None

*----------------------------------------------------------------------*

FORM display_data .

CLEAR w_flight.

* Display report final data

LOOP AT i_flight INTO w_flight.

w_flight-fldate1 = w_flight-fldate.

FORMAT INTENSIFIED ON COLOR 2.

WRITE: 1 sy-vline,

2 w_flight-carrid,

21 sy-vline,

22 w_flight-connid,

40 sy-vline,

41 w_flight-fldate1,

55 sy-vline,

56 w_flight-planetype,

80 sy-vline.

ULINE.

ENDLOOP.

IF p_page IS NOT INITIAL.

* Check whether any page exist with the number entered

* in the selection screen

READ LINE 1 OF PAGE p_page.

IF sy-subrc = 0.

* If exist then scroll down to that page

SCROLL LIST TO PAGE p_page LINE 1 .

ELSE.

* Otherwise display information message and continue

* processing

MESSAGE i000(z_zzz_ca_messages)

WITH 'Page number does not exist'(001).

ENDIF.

ENDFORM. " display_data

Screen shots:

Input:

Output:

Input:

Output:

Display Average in ALV report

2008-09-22T04:27:00.000-07:00

By Joyjit Ghosh,
Kolkata, India.

Code:

*&---------------------------------------------------------------------*
*& Report Z_DEMO_JG
*&
*&---------------------------------------------------------------------*
*& Display average in ALV report
*&---------------------------------------------------------------------*

REPORT z_demo_jg LINE-SIZE 80 LINE-COUNT 50

NO STANDARD PAGE HEADING.

TABLES: sflight.

TYPE-POOLS: slis.

* Data declaration

DATA: i_flight TYPE STANDARD TABLE OF sflight,

i_catalog TYPE slis_t_fieldcat_alv,

w_flight TYPE sflight,

w_catalog TYPE slis_fieldcat_alv.

DATA: v_repid TYPE syrepid.

* Selection screen

SELECT-OPTIONS: s_carrid FOR sflight-carrid.

START-OF-SELECTION.

* Fetch data from sflight table

SELECT *

FROM sflight

INTO TABLE i_flight

WHERE carrid IN s_carrid.

CHECK sy-subrc = 0.

v_repid = sy-repid.

* Build field catalog for ALV report

PERFORM build_catalog.

* Display ALV report

PERFORM display_report.

*&---------------------------------------------------------------------*
*& Form build_catalog
*&---------------------------------------------------------------------*
* Build field catalog for ALV report
*----------------------------------------------------------------------*
* None
*----------------------------------------------------------------------*

FORM build_catalog .

CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'

EXPORTING

i_program_name = v_repid

i_structure_name = 'SFLIGHT'

CHANGING

ct_fieldcat = i_catalog

EXCEPTIONS

inconsistent_interface = 1

program_error = 2

OTHERS = 3.

IF sy-subrc = 0.

* For average populate 'C' as value in

* field DO_SUM

w_catalog-do_sum = 'C'. " C = Average

* Modify record with new value

MODIFY i_catalog FROM w_catalog TRANSPORTING

do_sum WHERE fieldname = 'PRICE'.

ENDIF.

ENDFORM. " build_catalog

*&---------------------------------------------------------------------*
*& Form display_report
*&---------------------------------------------------------------------*
* Display ALV report
*----------------------------------------------------------------------*
* None
*----------------------------------------------------------------------*

FORM display_report .

IF i_catalog[] IS NOT INITIAL.

* Call ALV grid

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

i_callback_program = v_repid

it_fieldcat = i_catalog

TABLES

t_outtab = i_flight

EXCEPTIONS

program_error = 1

OTHERS = 2.

IF sy-subrc = 0.

ENDIF.

ENDFORM. " display_report

Selection Screen:

Output:

Display subtotal text in ALV grid

2008-09-21T07:24:00.000-07:00

By Joyjit Ghosh,
Kolkata, India.

Steps:
• Declare the fields twice in the table structure on which subtotal needs to be calculated.
• Populate these fields with same values in the internal table.
• When populating field catalog with these fields, hide one of the field by populating no_out = ‘X’ and tech = ‘X’ in the field catalog.
• Populate alv sort table for the field which is hidden in the field catalog.
• Populate alv event table for subtotal text (slis_ev_subtotal_text) event with routine name.
• Define the routine in the program to display subtotal text.

Code:

*&---------------------------------------------------------------------*
*& Report Z_ALV_SUBTOTAL
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*
REPORT z_alv_subtotal.

*&---------------------------------------------------------------------*
*& Table declaration
*&---------------------------------------------------------------------*

TABLES: ekko.

*&---------------------------------------------------------------------*
*& Type pool declaration
*&---------------------------------------------------------------------*
TYPE-POOLS: slis. " Type pool for ALV

*&---------------------------------------------------------------------*
*& Selection screen
*&---------------------------------------------------------------------*
SELECT-OPTIONS: s_ebeln FOR ekko-ebeln.

*&---------------------------------------------------------------------*
*& Type declaration
*&---------------------------------------------------------------------*

* Type declaration for internal table to store EKPO data
TYPES: BEGIN OF x_data,
ebeln TYPE char30, " Document no.
ebelp TYPE ebelp, " Item no
matnr TYPE matnr, " Material no
matnr1 TYPE matnr, " Material no
werks TYPE werks_d, " Plant
werks1 TYPE werks_d, " Plant
ntgew TYPE entge, " Net weight
gewe TYPE egewe, " Unit of weight
END OF x_data.

*&---------------------------------------------------------------------*
*& Internal table declaration
*&---------------------------------------------------------------------*
DATA:

* Internal table to store EKPO data
i_ekpo TYPE STANDARD TABLE OF x_data INITIAL SIZE 0,
* Internal table for storing field catalog information
i_fieldcat TYPE slis_t_fieldcat_alv,
* Internal table for Top of Page info. in ALV Display
i_alv_top_of_page TYPE slis_t_listheader,
* Internal table for ALV Display events
i_events TYPE slis_t_event,
* Internal table for storing ALV sort information
i_sort TYPE slis_t_sortinfo_alv,
i_event TYPE slis_t_event.

*&---------------------------------------------------------------------*
*& Work area declaration
*&---------------------------------------------------------------------*

DATA:
wa_ekko TYPE x_data,
wa_layout TYPE slis_layout_alv,
wa_events TYPE slis_alv_event,
wa_sort TYPE slis_sortinfo_alv.

*&---------------------------------------------------------------------*
*& Constant declaration
*&---------------------------------------------------------------------*

CONSTANTS:
c_header TYPE char1
VALUE 'H', "Header in ALV
c_item TYPE char1
VALUE 'S'.

*&---------------------------------------------------------------------*
*& Start-of-selection event
*&---------------------------------------------------------------------*

START-OF-SELECTION.

* Select data from ekpo
SELECT ebeln " Doc no
ebelp " Item
matnr " Material
matnr " Material
werks " Plant
werks " Plant
ntgew " Quantity
gewei " Unit
FROM ekpo
INTO TABLE i_ekpo
WHERE ebeln IN s_ebeln
AND ntgew NE '0.00'.

IF sy-subrc = 0.
SORT i_ekpo BY ebeln ebelp matnr .
ENDIF.

* To build the Page header
PERFORM sub_build_header.

* To prepare field catalog
PERFORM sub_field_catalog.

* Perform to populate the layout structure
PERFORM sub_populate_layout.

* Perform to populate the sort table.
PERFORM sub_populate_sort.

* Perform to populate ALV event
PERFORM sub_get_event.

END-OF-SELECTION.

* Perform to display ALV report
PERFORM sub_alv_report_display.

*&---------------------------------------------------------------------*
*& Form sub_build_header
*&---------------------------------------------------------------------*
* To build the header
*----------------------------------------------------------------------*
* No Parameter
*----------------------------------------------------------------------*
FORM sub_build_header .

* Local data declaration
DATA: l_system TYPE char10 , "System id
l_r_line TYPE slis_listheader, "Hold list header
l_date TYPE char10, "Date
l_time TYPE char10, "Time
l_success_records TYPE i, "No of success records
l_title(300) TYPE c. " Title

* Title Display
l_r_line-typ = c_header. " header
l_title = 'Test report'(001).
l_r_line-info = l_title.
APPEND l_r_line TO i_alv_top_of_page.
CLEAR l_r_line.

* Run date Display
CLEAR l_date.
l_r_line-typ = c_item. " Item
WRITE: sy-datum TO l_date MM/DD/YYYY.
l_r_line-key = 'Run Date :'(002).
l_r_line-info = l_date.
APPEND l_r_line TO i_alv_top_of_page.
CLEAR: l_r_line,
l_date.

ENDFORM. " sub_build_header

*&---------------------------------------------------------------------*
*& Form sub_field_catalog
*&---------------------------------------------------------------------*
* Build Field Catalog
*----------------------------------------------------------------------*
* No Parameter
*----------------------------------------------------------------------*
FORM sub_field_catalog .

* Build Field Catalog
PERFORM sub_fill_alv_field_catalog USING:

'01' '01' 'EBELN' 'I_EKPO' 'L'
'Doc No'(003) ' ' ' ' ' ' ' ',

'01' '02' 'EBELP' 'I_EKPO' 'L'
'Item No'(004) 'X' 'X' ' ' ' ',

'01' '03' 'MATNR' 'I_EKPO' 'L'
'Material No'(005) 'X' 'X' ' ' ' ',

'01' '03' 'MATNR1' 'I_EKPO' 'L'
'Material No'(005) ' ' ' ' ' ' ' ',

'01' '04' 'WERKS' 'I_EKPO' 'L'
'Plant'(006) 'X' 'X' ' ' ' ',

'01' '04' 'WERKS1' 'I_EKPO' 'L'
'Plant'(006) ' ' ' ' ' ' ' ',

'01' '05' 'NTGEW' 'I_EKPO' 'R'
'Net Weight'(007) ' ' ' ' 'GEWE' 'I_EKPO'.

ENDFORM. " sub_field_catalog

*&---------------------------------------------------------------------*
*& Form sub_fill_alv_field_catalog
*&---------------------------------------------------------------------*
*& For building Field Catalog
*&---------------------------------------------------------------------*
*& p_rowpos Row position
*& p_colpos Col position
*& p_fldnam Fldname
*& p_tabnam Tabname
*& p_justif Justification
*& p_seltext Seltext
*& p_out no out
*& p_tech Technical field
*& p_qfield Quantity field
*& p_qtab Quantity table
*&---------------------------------------------------------------------*
FORM sub_fill_alv_field_catalog USING p_rowpos TYPE sycurow
p_colpos TYPE sycucol
p_fldnam TYPE fieldname
p_tabnam TYPE tabname
p_justif TYPE char1
p_seltext TYPE dd03p-scrtext_l
p_out TYPE char1
p_tech TYPE char1
p_qfield TYPE slis_fieldname
p_qtab TYPE slis_tabname.

* Local declaration for field catalog
DATA: wa_lfl_fcat TYPE slis_fieldcat_alv.

wa_lfl_fcat-row_pos = p_rowpos. "Row
wa_lfl_fcat-col_pos = p_colpos. "Column
wa_lfl_fcat-fieldname = p_fldnam. "Field Name
wa_lfl_fcat-tabname = p_tabnam. "Internal Table Name
wa_lfl_fcat-just = p_justif. "Screen Justified
wa_lfl_fcat-seltext_l = p_seltext. "Field Text
wa_lfl_fcat-no_out = p_out. "No output
wa_lfl_fcat-tech = p_tech. "Technical field
wa_lfl_fcat-qfieldname = p_qfield. "Quantity unit
wa_lfl_fcat-qtabname = p_qtab . "Quantity table

IF p_fldnam = 'NTGEW'.
wa_lfl_fcat-do_sum = 'X'.
ENDIF.
APPEND wa_lfl_fcat TO i_fieldcat.
CLEAR wa_lfl_fcat.
ENDFORM. " sub_fill_alv_field_catalog

*&---------------------------------------------------------------------*
*& Form sub_populate_layout
*&---------------------------------------------------------------------*
* Populate ALV layout
*----------------------------------------------------------------------*
* No Parameter
*----------------------------------------------------------------------*
FORM sub_populate_layout .

CLEAR wa_layout.
wa_layout-colwidth_optimize = 'X'." Optimization of Col width

ENDFORM. " sub_populate_layout

*&---------------------------------------------------------------------*
*& Form sub_populate_sort
*&---------------------------------------------------------------------*
* Populate ALV sort table
*----------------------------------------------------------------------*
* No Parameter
*----------------------------------------------------------------------*
FORM sub_populate_sort .

* Sort on material
wa_sort-spos = '01' .
wa_sort-fieldname = 'MATNR'.
wa_sort-tabname = 'I_EKPO'.
wa_sort-up = 'X'.
wa_sort-subtot = 'X'.
APPEND wa_sort TO i_sort .
CLEAR wa_sort.

* Sort on plant
wa_sort-spos = '02'.
wa_sort-fieldname = 'WERKS'.
wa_sort-tabname = 'I_EKPO'.
wa_sort-up = 'X'.
wa_sort-subtot = 'X'.
APPEND wa_sort TO i_sort .
CLEAR wa_sort.

ENDFORM. " sub_populate_sort

*&---------------------------------------------------------------------*
*& Form sub_get_event
*&---------------------------------------------------------------------*
* Get ALV grid event and pass the form name to subtotal_text
* event
*----------------------------------------------------------------------*
* No Parameter
*----------------------------------------------------------------------*
FORM sub_get_event .
CONSTANTS : c_formname_subtotal_text TYPE slis_formname VALUE
'SUBTOTAL_TEXT'.

DATA: l_s_event TYPE slis_alv_event.

CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
i_list_type = 4
IMPORTING
et_events = i_event
EXCEPTIONS
list_type_wrong = 0
OTHERS = 0.

* Subtotal
READ TABLE i_event INTO l_s_event
WITH KEY name = slis_ev_subtotal_text.
IF sy-subrc = 0.
MOVE c_formname_subtotal_text TO l_s_event-form.
MODIFY i_event FROM l_s_event INDEX sy-tabix.
ENDIF.

ENDFORM. " sub_get_event

*&---------------------------------------------------------------------*
*& Form sub_alv_report_display
*&---------------------------------------------------------------------*
* For ALV Report Display
*----------------------------------------------------------------------*
* No Parameter
*----------------------------------------------------------------------*
FORM sub_alv_report_display .
DATA: l_repid TYPE syrepid .
l_repid = sy-repid .

* This function module for displaying the ALV report
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = l_repid
i_callback_top_of_page = 'SUB_ALV_TOP_OF_PAGE'
is_layout = wa_layout
it_fieldcat = i_fieldcat
it_sort = i_sort
it_events = i_event
i_default = 'X'
i_save = 'A'
TABLES
t_outtab = i_ekpo
EXCEPTIONS
program_error = 1
OTHERS = 2.
IF sy-subrc <> 0.
* MESSAGE i000 WITH 'Error in ALV report display'(055).
ENDIF.

ENDFORM. " sub_alv_report_display

*&---------------------------------------------------------------------*
* FORM sub_alv_top_of_page
*---------------------------------------------------------------------*
* Call ALV top of page
*---------------------------------------------------------------------*
* No parameter
*---------------------------------------------------------------------*

FORM sub_alv_top_of_page. "#EC CALLED

* To write header for the ALV
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = i_alv_top_of_page.

ENDFORM. "alv_top_of_page

*&---------------------------------------------------------------------*
*& Form subtotal_text
*&---------------------------------------------------------------------*
* Build subtotal text
*----------------------------------------------------------------------*
* P_total Total
* p_subtot_text Subtotal text info
*----------------------------------------------------------------------*
FORM subtotal_text CHANGING
p_total TYPE any
p_subtot_text TYPE slis_subtot_text.

* Material level sub total
IF p_subtot_text-criteria = 'MATNR'.
p_subtot_text-display_text_for_subtotal
= 'Material level total'(009).
ENDIF.

* Plant level sub total
IF p_subtot_text-criteria = 'WERKS'.
p_subtot_text-display_text_for_subtotal = 'Plant level total'(010).
ENDIF.

ENDFORM. "subtotal_text

Change color of a cell in ALV report

2008-09-12T02:26:00.001-07:00

By Joyjit Ghosh,
Kolkata, India.

To change the color of a particular cell at runtime ,we have to perform the following steps:

Step1:

Define an internal table of TYPE slis_specialcol_alv as a field into the output table which has to pass into the ‘REUSE_ALV_GRID_DISPLAY’ Function module.

TYPES: BEGIN OF ty_user_output,

BELNR like RBKP-BELNR, "Doc. Number

BUDAT like RBKP-BUDAT, "Posting Date

BUKRS like RBKP-BUKRS, "Company Code

LIFNR like RBKP-LIFNR, "Invoicing Party

NAME1 like LFA1-NAME1, "Name

USNAM like RBKP-USNAM, "User

BUZEI like RSEG-BUZEI, "Invoice Item

RBWWR like RSEG-RBWWR, "Amount

EBELN like RSEG-EBELN, "Purchase Document

EBELP like RSEG-EBELP, "Purchase Order Item

WERKS like RSEG-WERKS, "Plant

EKGRP like EKKO-EKGRP, "Purchasing Group

TBTKX like RSEG-TBTKZ, "Subsequent Debit/Credit

SPGRG like RSEG-SPGRG, "Order Price Quantity

SPGRM like RSEG-SPGRM, "Blocking Reason:Quantity

SPGRP like RSEG-SPGRP, "Blocking Reason:Price

SPGRC like RSEG-SPGRC, "Blocking Reason:Quality

SPGRS like RSEG-SPGRS, "Blocking Reason:Amount

SPGRT like RSEG-SPGRT, "Blocking Reason:Date

SPGRQ like RSEG-SPGRQ, "Blocking Reason:Manual

parked(1) type c , "Indicates Parked Invoice

Note(1) type c, "Indicates Blocking Notes

GJAHR like RBKP-GJAHR, "Fiscal year

color TYPE slis_specialcol_alv OCCURS 2,

"For cell color

END OF ty_user_output.

Step2:

When building the layout set for ALV ,specify the color field name.

w_layout-coltab_fieldname = 'COLOR'.

Step3:

If we want to give a color to any column when the report is first displayed,

then we have to populate the internal table COLOR.

DATA: w_color TYPE slis_specialcol_alv. " Color

w_color-fieldname = p_field.

w_color-color-col = p_color.

w_color-color-int = p_int.

w_color-color-inv = p_inv.

w_color-nokeycol = p_key.

APPEND w_color TO w_user_output-color.

CLEAR w_color.

Step4:

If the user press any custom button or double click on any particular field,

then we have to track the sy-ucomm value .To do this we have to create a subroutine,

which has two parameters ,one is like sy-ucomm and another is type slis_selfield,

and we have to assign the subroutine name in the ‘i_callback_user_command ‘ parameter of the function module REUSE_ALV_GRID_DISPLAY.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

i_callback_program = c_repid

i_callback_user_command = 'USER_COMMAND'

i_structure_name = 'i_tab'

is_layout = w_layout

it_fieldcat = i_fieldcat[]

I_SAVE = 'A'

is_variant = w_variant

it_events = i_levents

is_print = w_print

TABLES

t_outtab = i_tab

EXCEPTIONS

program_error = 1

OTHERS = 2.

Form USER_COMMAND USING r_ucomm LIKE sy-ucomm

rs_selfield TYPE slis_selfield.

ENDFORM. "USER_COMMAND

Now when ever user generates a particular function code then we have to first check the field name then modify the color table depending upon field name and lastly modify the output table. This logic is written in to the above subroutine.

IF r_ucomm = V_F2CODE.

if rs_selfield-fieldname = c_doc_name.

*Work area for color table.

DATA: w_color TYPE slis_specialcol_alv.

clear w_user_output.

*Read internal table for proper value.

read table i_user_output

index rs_selfield-tabindex(Contains index of the current record selected by the user)

into w_user_output.

if sy-subrc = 0.

read table w_user_output-color into w_color

with key fieldname = rs_selfield-fieldname(Contains current field name selected by the user).

if sy-subrc = 0.

w_color-color-col = '4'.

w_color-color-int = 1.

w_color-color-inv = 0.

* Modify the internal table Color

MODIFY w_user_output-color FROM w_color

INDEX sy-tabix TRANSPORTING color.

CLEAR w_color.

* Modify the internal table i_user_output

MODIFY i_user_output FROM w_user_output

INDEX p_index TRANSPORTING color.

endif.

Endif.

Now to refresh the ALV grid, set the refresh field of the rs_selfield parameter.

rs_selfield-refresh = ‘X’.

Report Output:

First time when the report is displayed:

After successive processing:

Insert separator in a string after specified position

2008-09-11T08:28:00.001-07:00

By Joyjit Ghosh,
Kolkata, India.

Code:

*&---------------------------------------------------------------------*
*& Report Z_DEMO_JG
*&
*&---------------------------------------------------------------------*
*&
*& Insert separator in a string after specified position
*&---------------------------------------------------------------------*

REPORT z_demo_jg.

* Data declaration

DATA: l_char1(3) TYPE c.

DATA: l_char TYPE string.

DATA: l_pos TYPE i.

DATA: l_len TYPE i.

DATA: l_len1 TYPE i.

* Selection screen

PARAMETERS: l_srt(255) TYPE c DEFAULT `12344566` obligatory, " String

l_spch(1) type c DEFAULT `,` obligatory, " Separator

l_no type int3 DEFAULT 1 obligatory. " No of places

* Length of the string

l_len = STRLEN( l_srt ).

* Divide the length by 3

l_len1 = l_len DIV l_no.

l_pos = 0.

DO l_len1 TIMES.

* Storing next l_no chars

l_char1 = l_srt+l_pos(l_no).

* Add separator with it

CONCATENATE l_char l_char1 l_spch INTO l_char.

l_pos = l_pos + l_no.

ENDDO.

* Check remaining length

l_len1 = l_len - l_pos.

IF l_len1 > 0.

* Storing remaining characters

l_char1 = l_srt+l_pos(l_len1).

CONCATENATE l_char l_char1 INTO l_char.

ENDIF.

CONDENSE l_char NO-GAPS.

* Display original string

write /.

WRITE : 'Original String:',

l_srt.

l_srt = l_char.

* Display modified string

write /.

WRITE : 'Modified String :',

l_srt.

Selection screen:

Output:

Creating dynamic variant using table TVARV

2008-09-11T02:45:00.000-07:00

By Joyjit Ghosh,
Kolkata, India.

Let us say for the given selection screen we need to create a dynamic variant.

Step 1. First maintain a variable with values in table TVARV. This can be done from transaction STVARV. Later this variable needs to be assigned to the variant.

Step 2. Next create the dynamic variant by pressing the SAVE button on the selection screen.

In the next screen (ABAP: Save as Variant) enter Variant name, description, set the ‘Selection variable’(L) radio button and press ‘Selection variable’ push button.

In the next screen check that green traffic light is on under column T (T: Table variable from TVARV). Then click on button.

Now from the popup select the variable name created in Step1 and save the variant.

Step 3. Select the variant from Variant catalog.

It will populate ‘Airline’ select-option with the values maintained in TVARV table against variable ZAIRLINE_CODE.

Global Macro

2008-09-11T02:17:00.000-07:00

By Joyjit Ghosh,
Kolkata, India.

Most of the time we define macro in our program by DEFINE … END-OF-DEFINITION statement.

Ex:

DEFINE macro_name

Statement……

Statement …..

………………..

END-OF-DEFINITION.

And this macro can be called in the following way

macro_name par1 par2 …par9. “par1… par9 = Parameters, separated by spaces

This above definition is local to the program where it is defined i.e. we cannot call this macro from another program. But we can create global macro that can be called by any program.

Global macro can be created by maintaining entries in table TRMAC.

Most popular example of standard global (system) macro is BREAK which is defined in table TRMAC as shown in the screen shot below.

From any program we can call this macro as:

BREAK user_id. “ user_id = placeholder for userid

Similarly we can maintain our own global macro in TRMAC as shown below:

Add new entry to TRMAC

Create custom macro

Call this global macro from a report

Output:

Dynamic selection screen with list box

2008-09-11T01:55:00.000-07:00

By Joyjit Ghosh,
Kolkata, India.

Code:

*&---------------------------------------------------------------------*
*& Report Z_DYNAMIC_SCREEN
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*

REPORT z_dynamic_screen.

TYPE-POOLS: vrm.

DATA: name TYPE vrm_id, list TYPE vrm_values, value LIKE LINE OF list.

TABLES: sscrfields.

* Selection screen

* List box
PARAMETERS: ps_parm AS LISTBOX VISIBLE LENGTH 10

USER-COMMAND abc.

* Radio buttons
PARAMETERS: rb1 RADIOBUTTON GROUP ab MODIF ID bl2,

rb2 RADIOBUTTON GROUP ab MODIF ID bl2,

rb3 RADIOBUTTON GROUP ab MODIF ID bl3.

INITIALIZATION.

* Populate list box values

name = 'PS_PARM'.

value-key = '1'. value-text = 'Line 1'. APPEND value TO list.

value-key = '2'. value-text = 'Line 2'. APPEND value TO list.

AT SELECTION-SCREEN OUTPUT.

* Set list box with value

CALL FUNCTION 'VRM_SET_VALUES'

EXPORTING

id = name

values = list.

* Control the display of screen components

LOOP AT SCREEN.

IF ps_parm = 1.

IF screen-name = 'RB1' OR screen-name = 'RB2' .

screen-invisible = 0.

ELSEIF screen-name = 'RB3'.

screen-invisible = 1.

ENDIF.

MODIFY SCREEN.

ELSEIF ps_parm = 2.

IF screen-name = 'RB1' OR screen-name = 'RB2' .

screen-invisible = 1.

ELSEIF screen-name = 'RB3'.

screen-invisible = 0.

ENDIF.

MODIFY SCREEN.

ELSEIF ps_parm = space.

rb1 = 'X'.

clear: rb2,rb3.

IF screen-name = 'RB1' OR screen-name = 'RB2' OR

screen-name = 'RB3'.

screen-invisible = 0.

MODIFY SCREEN.

ENDIF.

ENDLOOP.

AT SELECTION-SCREEN.

IF sscrfields-ucomm = 'ABC'.

ENDIF.

START-OF-SELECTION.

WRITE: / 'Parameter:', ps_parm.

Selection screen:

Simple ALV GRID (Full screen)

2008-07-31T08:15:00.000-07:00

By Joyjit Ghosh,
Kolkata, India.

REPORT z_alv_object_1.

DATA: i_mara TYPE STANDARD TABLE OF mara.
DATA: dref TYPE REF TO cl_salv_table.

*&---------------------------------------------------------------------*
*& Start-of-selection event
*&---------------------------------------------------------------------*
START-OF-SELECTION.

* Fetch data from database
SELECT * FROM mara
INTO TABLE i_mara
UP TO 100 ROWS.

CHECK sy-subrc = 0.

* Get the ALV instance
TRY.
CALL METHOD cl_salv_table=>factory
* EXPORTING
* list_display = IF_SALV_C_BOOL_SAP=>TRUE
* r_container =
* container_name =
IMPORTING
r_salv_table = dref
CHANGING
t_table = i_mara
.
CATCH cx_salv_msg .
MESSAGE i000(z_zzz_ca_messages)
WITH 'Error in ALV processing'(001).

LEAVE LIST-PROCESSING.
ENDTRY.

IF dref IS BOUND.

* Display AlV report
CALL METHOD dref->display( ).

ENDIF.

Execute report from sap mail

2008-07-30T13:10:00.000-07:00

By Joyjit Ghosh,
Kolkata, India.

*&---------------------------------------------------------------------*
*& Report Z_DEMO_MAIL
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*

REPORT z_demo_mail.

*&---------------------------------------------------------------------*
*& Global data declaration
*&---------------------------------------------------------------------*

DATA:
w_document_data LIKE sodocchgi1.

DATA:
i_object_header TYPE STANDARD TABLE OF solisti1,
w_object_header TYPE solisti1,

i_object_content TYPE STANDARD TABLE OF solisti1,
w_object_content TYPE solisti1,

i_contents_hex TYPE STANDARD TABLE OF solix,
w_contents_hex TYPE solix,

i_object_para TYPE STANDARD TABLE OF soparai1,
w_object_para TYPE soparai1,

i_object_parb TYPE STANDARD TABLE OF soparbi1,
w_object_parb TYPE soparbi1,

i_receivers TYPE STANDARD TABLE OF somlreci1,
w_receivers TYPE somlreci1.

*&---------------------------------------------------------------------*
*& Selection screen
*&---------------------------------------------------------------------*
PARAMETER : uname TYPE syuname DEFAULT sy-uname.

*&---------------------------------------------------------------------*
*& Start-of-selection event
*&---------------------------------------------------------------------*
START-OF-SELECTION.

* Populate receiver info
clear: w_receivers.
w_receivers-receiver = uname.
w_receivers-rec_type = 'B'.
append w_receivers to i_receivers.

* Populate header data
w_document_data-obj_name = 'Your action required'.
w_document_data-obj_descr = 'Pl. press execute button'.
w_document_data-sensitivty = 'O'.
w_document_data-proc_type = 'R'.
w_document_data-proc_name = 'RSINCL00'.

* Populate mail content
clear: w_object_content.
concatenate 'Please execute report: '
w_document_data-proc_name
into w_object_content-line separated by space.
append w_object_content to i_object_content.

CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
EXPORTING
document_data = w_document_data
DOCUMENT_TYPE = 'RAW'
* PUT_IN_OUTBOX = ' '
* COMMIT_WORK = ' '
* IMPORTING
* SENT_TO_ALL =
* NEW_OBJECT_ID =
tables
* OBJECT_HEADER =
OBJECT_CONTENT = i_object_content
* CONTENTS_HEX =
OBJECT_PARA = i_object_para
* OBJECT_PARB =
receivers = i_receivers
EXCEPTIONS
TOO_MANY_RECEIVERS = 1
DOCUMENT_NOT_SENT = 2
DOCUMENT_TYPE_NOT_EXIST = 3
OPERATION_NO_AUTHORIZATION = 4
PARAMETER_ERROR = 5
X_ERROR = 6
ENQUEUE_ERROR = 7
OTHERS = 8
.
IF sy-subrc = 0.
message s000(z_zzz_ca_messages)
with 'Mail send successfully'(001).
ENDIF.

Changing font style in ALV

2008-07-27T03:06:00.000-07:00

By Joyjit Ghosh,
Kolkata, India.

By using the Function Module REUSE_ALV_GRID_DISPLAY_LVC we can change the font style in ALV report.

Example:

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

*& Report Z_DEMO_ALV_JG *

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

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

REPORT z_demo_alv_jg .

* Include for all style values

INCLUDE <cl_alv_control>.

* Internal table for final output data

DATA: i_flight TYPE STANDARD TABLE OF sflight.

* Internal table for field catalog info

DATA: i_fields TYPE lvc_t_fcat.

* Field symbol for field catalog

FIELD-SYMBOLS: <wa_fields> TYPE lvc_s_fcat.

* Select data

SELECT * FROM sflight

INTO TABLE i_flight

UP TO 100 ROWS.

IF sy-subrc = 0.

* Get field catalog

CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'

EXPORTING

i_structure_name = 'SFLIGHT'

CHANGING

ct_fieldcat = i_fields

EXCEPTIONS

inconsistent_interface = 1

program_error = 2

OTHERS = 3

.

IF sy-subrc = 0.

* Changing the style of field catalog

LOOP AT i_fields ASSIGNING <wa_fields>.

IF sy-tabix > 4.

<wa_fields>-style = ALV_STYLE_FONT_ITALIC.

ELSE.

<wa_fields>-style = ALV_STYLE_FONT_BOLD.

ENDIF.

ENDLOOP.

ENDIF.

* Calling the FM to display ALV report

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY_LVC'

EXPORTING

i_structure_name = 'SFLIGHT'

i_grid_title = 'Style demo'(001)

it_fieldcat_lvc = i_fields

TABLES

t_outtab = i_flight

EXCEPTIONS

program_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.
ENDIF.

Output:

Add custom sub-menu in ALV context menu

2008-07-26T02:20:00.000-07:00

By Joyjit Ghosh,
Kolkata, India.

Code:

REPORT z_alv_context_menu NO STANDARD PAGE HEADING.

***********************************************************************
* Type pool declaration
***********************************************************************

TYPE-POOLS: slis.

***********************************************************************
* Internal table declaration
***********************************************************************
DATA: BEGIN OF gt_outtab OCCURS 0.

INCLUDE STRUCTURE sflight.

DATA: END OF gt_outtab.

data: gt_events TYPE slis_t_event.

**********************************************************************
* Structure / Variable declaration
**********************************************************************
DATA: g_repid LIKE sy-repid,

event TYPE slis_alv_event.

**********************************************************************
* Event: START-OF-SELECTION
**********************************************************************
START-OF-SELECTION.

* Storing the program name
g_repid = sy-repid.

* Building ALV event table
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'

EXPORTING

i_list_type = 4

IMPORTING

et_events = gt_events

EXCEPTIONS

list_type_wrong = 1

OTHERS = 2.

IF sy-subrc = 0.

REFRESH gt_events.

* Adding records for CONTEXT_MENU event
event-name = 'CONTEXT_MENU'.

event-form = 'CONTEXT_MENU'.

APPEND event TO gt_events.

ENDIF.

* Data Selection
SELECT * FROM sflight INTO CORRESPONDING FIELDS

OF TABLE gt_outtab

UP TO 00030 ROWS.

* Display ALV grid
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

i_callback_html_top_of_page = 'HTML_TOP_OF_PAGE'

i_callback_program = g_repid

i_callback_user_command = 'USER_COMMAND'

i_structure_name = 'SFLIGHT'

it_events = gt_events

TABLES

t_outtab = gt_outtab

EXCEPTIONS

program_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

***********************************************************************
* FORM html_top_of_page
***********************************************************************
FORM html_top_of_page USING top TYPE REF TO cl_dd_document.

CALL METHOD top->add_text

EXPORTING

text = 'Hello world '

sap_style = 'heading'.

CALL METHOD top->add_gap

EXPORTING

width = 200.

CALL METHOD top->add_picture

EXPORTING

picture_id = 'ENJOYSAP_LOGO'.

ENDFORM. "html_top_of_page

***********************************************************************
* Form context_menu
***********************************************************************
FORM context_menu USING e_object TYPE REF TO cl_ctmenu.

DATA: l_smenu TYPE REF TO cl_ctmenu.

IF e_object IS BOUND.

* Create custom Sub-menu to hide column on which right
* mouse button will be clicked
CREATE OBJECT l_smenu.

CALL METHOD l_smenu->add_function

EXPORTING

fcode = 'ZFN1'

text = 'Hide Column'(001).

CALL METHOD e_object->add_submenu

EXPORTING

menu = l_smenu

text = 'Hide'(002).

ENDIF.

ENDFORM. "CONTEXT_MENU

***********************************************************************
* Form user_command
***********************************************************************
FORM user_command USING r_ucomm TYPE sy-ucomm

ls_selfield TYPE slis_selfield.

DATA: g_grid TYPE REF TO cl_gui_alv_grid,

t_catalog TYPE lvc_t_fcat,

w_catalog TYPE lvc_s_fcat,

l_repid TYPE sy-repid.

CASE r_ucomm.

* When 'hide column' sub-menu is clicked from the context menu
* then hide the column from where this is happened
WHEN 'ZFN1'.

* Get the global instance of the ALV grid as well as
* it's field catalog info.
CALL FUNCTION 'GET_GLOBALS_FROM_SLVC_FULLSCR'
IMPORTING

e_callback_program = l_repid

e_grid = g_grid

et_fieldcat_lvc = t_catalog.

CHECK l_repid = g_repid.

IF g_grid IS BOUND AND t_catalog[] IS NOT INITIAL.

* Set the 'NO_OUT' attribute of the catalog to 'X'
w_catalog-no_out = 'X'.

* Modify the field with this above value
* on which right click occured
MODIFY t_catalog FROM w_catalog TRANSPORTING no_out

WHERE fieldname = ls_selfield-fieldname.

IF sy-subrc = 0.

* Set the field catalog with this modified one
CALL METHOD g_grid->set_frontend_fieldcatalog

EXPORTING

it_fieldcatalog = t_catalog.

ENDIF.

WHEN OTHERS.

* Do nothing

ENDCASE.

ls_selfield-refresh = 'X'.

ENDFORM. "USER_COMMAND

Output: