Creation of Transparent Table

By Sasidhar Reddy Matli, ROBERT BOSCH

1. Enter the table name and press Create

2. Enter the description, Delivery class and check on table maintenance allowed. Then click on the
tab Fields.
3. Enter the ZCHAR in fields tab and ZCHAR_DE in field type tab.
4. Double click on ZCHAR_DE. Then it will ask for Save. Press ‘YES”.

5. Save it as a local object on pressing Local object button

6. Now it will ask for the creation of the data element. Press Yes.
7. Click on the Field label tab and enter the lengths and descriptions accordingly.
 8. Then press Definition tab and enter the domain.

9. Double click on that zchar_d to create domain, then it will ask for save before going next screen.

Press Yes.
10. Save it as a local object.
11. Now it will ask for domain creation. Press Yes.

12. Give short description for that domain which you are creating. And mention the data type in data
type field and length in no. characters field an press ENTER.
13. Then press Ctrl+F3. It will ask for save before activation. Save it as a local Object.
14. Press Enter.

15. Then the following screen appears. Press on back button.

16. Press Ctrl+F3. You will get the following screen. Press Back button.

17. You will get the following screen.

18. Create one more field ZNUM and give data element name as ZNUM_DE. And double click on
‘ZNUM_DE’
19. Save it by pressing Yes.

20. Now it will ask for the data element creation. Press Yes.
 Give short description of the data element. And give the lengths and field labels accordingly in
Field label tab.

22. Press on Definition tab and give the domain name in Domain field. Double click on ZNUM_D.
23. It will ask for save. Press Yes.

24. Save it as a local Object.

 25. Now it asks for Domain creation. Press Yes.

26. Give short description in short text field. Enter the data type and no. characters, Press Enter.

Then Press on Activate button or Press Ctrl+F3.

27. Save this as a local object.
28. Press enter.
29. Now you will get the following screen. Press Back button.
30. Activate the data element By pressing Activate button or Pressing Ctrl+F3.
31. Press enter.
32. Press Back button.
 33. Now we created two fields. And Data elements and Domain for these two fields.

Now we have to maintain the technical settings. Press on Technical settings button.
 34. Give the data class and size category of the table as per the requirement.

And press the back button.

35. Now activate the table by pressing the activate button or CTRL+F3.
36. Press enter.

37. Now you will get the following screen.

38. Now enter the data into table. Go to Utilitiesà Table contents à Create Entries.
39. Now enter the data in the fields and Save it.
40. You will get the following screen after clicking the Reset Button.
41. Enter the data for the second entry into the table.
42. Save it and press reset.
43. You will get the following screen.
44. Again enter the data for the third entry.

45. Press save, Reset (Optional) and Back button.

46. Now you will get the following screen.
47. To see the table contents go to Utilities à Table contents à Display. Or press Ctrl+Shift+F10.
 You will get the following screen.
49. Press on run button or press F8. Now it will display the table contents.
Creating a Structure in ABAP Dictionaryd
By Vikram Chellappa, Mouri Tech Solutions

Go to transaction SE11 and select the radio button “Data type”. Enter a structure name starting with Y or
Z.

Press create button.

A pop-up screen appears with 3 different options. Select the radio button structure.

The screen will be displayed like this.

Provide the description and also components.

Then press SAVE, CHECK and ACTIVATE.

Structure Created Successfully.

Creating Search Helps (Elementary and Secondary)
By Vikram Chellappa, Mouri Tech Solutions

Go To SE11 T-code.

Select the radio button of search help.

Provide the search help name. Select the create button.

Select ELEMENTARY search help.

Press Enter.

Provide the short description, the selection method.

Provide the fields.

Save it, Check It & Activate it.

Then execute it.

We can see the screen like this, and then press F4 in this page.

Then press F4 View the output like this.

This is the output for elementary search help.

The Collective Search Help is like this.

Goto T-Code Se11.

Provide name. Select collective search help button.

Press enter.
Provide the Values

Select include search help.

Then provide search help name, which is already define by the same fields.

Then save it, activate it & execute it.

Press F4 we can see the output like this.
Diff Between Elementary search helps & Collective search helps

1) Elementary search helps describe a search path. The elementary search help must
define where the data of the hit list should be read from (selection method), how the
exchange of values between the screen template and selection method is implemented
(interface of the search help) and how the online input help should be defined (online
behavior of the search help).

2) Collective search helps combine several elementary search helps. Collective search
help thus can offer several alternative search paths.

3) An elementary search help defines the standard flow of an input help.

4) A collective search help combines several elementary search helps. The user can thus
choose one of several alternative search paths with collective search help.

5) A collective search help comprises several elementary search helps. It combines all
the search paths that are meaningful for a field.

6) Both elementary search helps and other search helps can be included in a collective
search help. If other collective search helps are contained in collective search help, they
are expanded to the level of the elementary search helps when the input help is called.
Creating a secondary index
By Neha Kapoor

There are two types of indexes: Primary index and secondary index. Primary index is
automatically created using the primary keys defined.

 Secondary index could be created as per the user requirement. This article discusses about
creating a secondary index.
 Go to transaction SE11.


 For our demo purpose, we have considered the table ZAUTHOR.
 To know if there are any secondary indexes available, click on Goto à Indexes
 Following popup appears:


 From the above screenshot, it is evident that there are no secondary indexes already created.
 Click on Create à Create Index


 Enter the name of the index.


 Fill in the details – Short description and the fields in the index.

 Save and activate.
 Now you can observe the index created above in the list now:


 Maximum number of secondary indexes we can have are 9.
 How to make SELECT statement to make use of any particular secondary index?
Consider the following example:
SELECT * FROM SPFLI
%_HINTS ORACLE 'INDEX("SPFLI" "SPFLI~001")'
.......
ENDSELECT.

In the above example, 001 is the secondary index of the table SPFLI. It's a well-known fact that
the efficient way of retrieving data from the database tables is by using secondary indexes. Many
database vendors provide the optimizer hints for the same. From SAP® v4.5, optimizer hints can
be provided by the %_HINTS parameter. This is dependent on the database systems that support
optimizer hints. The point to be noted here is these optimizer hints are not standardized by the
SQL standards. Each database vendor is free to provide the optimizer hints.
Now to know which index to use for our table:
1. Go to SE11 and there specify the table name
2. Now from the menu, goto --> indexes
3. select the required index.

Now suppose that the identifier 001 represents a non-unique secondary index comprising of the
columns CITYFROM and CITYTO. The index name should be defined as:

<tablename>~<Index Identifier>
like SPFLI~001 in the above example.

The sequence of fields in the WHERE condition is of no relevance in using this optimizers index.
If you specify hints incorrectly, ABAP ignores them but doesn't return a syntax error or runtime
TM

error.
The code was written in R/3 4.6C.

Code

Consider the following example:

REPORT Suresh_test.

TABLES: spfli.

DATA : t_spfli LIKE spfli OCCURS 0 WITH HEADER LINE.

SELECT * FROM spfli

INTO TABLE t_spfli
%_HINTS ORACLE 'INDEX("SPFLI" "SPFLI~001")'.

LOOP AT t_spfli.
WRITE :/ t_spfli.
ENDLOOP.
Working with Table Maintenance Generator
By Rakhi Bose, Capgemini

Go to SE11 and enter the Z table name for which the table maintenance generator has to be generated.
Click on Change.
Click on Utilities à Table Maintenance Generator
Enter Authorization group (For e.g. &NC&)
Function group (go to SE80 for creating function group)

You can select either one step or two step. Assign Screen numbers (To assign Screen numbers click on
the button 'Find Scr no'. It will propose screen no's)

Then Create. Save

Single step: Only overview screen is created i.e. the Table Maintenance Program will have only one
screen where you can add, delete or edit records.

Two step: Two screens namely the overview screen and Single screen are created. The user can see the
key fields in the first screen and can further go on to edit further details.

You can now create TCode for the table maintenance generator. Enter the TCode to be created and click
on Create.
Select “Transaction with parameters (Parameter transaction)”
Click on save.
Creation of a Logical Database
By Kameswara Rao, IBM India

Go to transaction 'SE36' or 'SLDB'.

Enter the logical database name as shown above .

If we are using Logical Database for HR purpose, we should check the check Box “Info types (HR only).
Press CREATE Button as shown above.

It would prompt for package name and workbench request .

On pressing Save button, following screen appears, prompting for the details of the root node.

Click on create button. Following screen appears:

Now enter the details of all the tables under LFA1 (as shown below).

Click on create Button.

Click on create Button.

Now create a Node with hierarchically under LFB1.

The above screen displays the LDB structure as per our requirements.

We can maintain search help for the fields for the tables defined in structure.
For our demo purposes, let us provide search help for MATNR and WERKS.
Let us use the standard search help available for MATNR and WERKS.
The currency and quantity fields are automatically maintained here.
Go back to the main screen
Here we can design our own selection screen as per the requirements.
Automatically created include with naming convention.

Here by using above marked statement we can create Dynamic selection screen for different tables as
per the requirements.

Database program (with some includes) are automatically created upon the creation of logical database:
Go back to the main screen.

Here we can maintain texts for select-options and parameters.

Navigate to the main screen:
Here we can maintain documentation for our created Z logical database.
Click on Display.
Creation of a View cluster
By T.N.Swapna

View Cluster

A view cluster is the set of objects, such as views, reports or tables, which belong to one business
function. The data can be arranged either hierarchically or non-hierarchically in view cluster. A view-
cluster transaction edits the complex cross-table data in a view cluster. The transaction navigation box
shows the complex business object with its components or sub objects.

Example:

Let us create a View Cluster on Material Details. The view cluster would include three tables namely,
MARA, MARC and MARD. We need to create maintenance views for each of these tables.

Maintenance view for Table MARA

To create maintenance view for the table MARA follow the procedure below. Go to transaction SE11. Give
a view name say ZMM_V_MARA and click on ‘Create’. Give a short description, enter the table name as
MARA and click on the tab View fields.

By default all the key fields would be added. We can add more fields by clicking on the button Table fields.
Now Save and activate the view.

Maintenance view for Table MARC

Follow the same procedure as above. In the Tab View fields, give ‘S’ in the column ‘P’ for the fields
MANDT and MATNR as shown in the screen shot below:

This is because the fields MANDT and MATNR would be filled in the view for MARA and thus they act as
subsets and appear as header data when we create entries in view cluster.

Maintenance view for Table MARD

Follow the same procedure as above. In the Tab View fields, give ‘S’ in the column ‘P’ for the fields
MANDT, MATNR and WERKS as shown in the screen shot below:
This is because the fields MANDT, MATNR and WERKS would be filled in the view for MARC and thus
they act as subsets and appear as header data when we create entries in view cluster.

Now, for each view we need to create a table maintenance generator, which has to be done as follows:

The table maintenance screen appears. Here give the details as in the screen shot below. This table
maintenance is for the view ZMM_V_ MARA.
Before creating a table maintenance generator, create a function group say ZFG_MATERIAL from the
transaction SE80. After the function group is successfully created, enter the function group name as
shown in the screen shot. Also select Maintenance type as ‘One Step’ and give the Maintenance Screen
no. as ‘1’ in the Overview screen and click on the button ‘Create’.

Similarly, create the Table maintenance Generators for the views ZMM_V_MARC and ZMM_V_MARD.
The screen shots for these views would be as follows:

Table Maintenance Generators for ZMM_V_MARC and ZMM_V_MARD

Note that the Overview screen numbers would change for each view. It would be ‘2’ for the view
ZMM_V_MARC and it would be ‘3’ for the view ZMM_V_MARD.

The pre-requisites for creating the View Cluster are now ready. Go to transaction SE54 and select the
button ‘Edit View Cluster’. Enter the view cluster name as say ‘ZMM_VC_MATERIAL’ and click on
‘Create’.
An information message would pop up saying

Continue by pressing ‘Enter’. The following screen appears. Give a short description and click on ‘Object
Structure’ as shown in the screen shot below:

On Clicking the ‘Object Structure’ the following screen appears. Select the ‘New Entries’ button to enter
the maintenance views created to form a cluster.
Enter the values as shown below:

The entries would be entered in a hierarchical manner. The short text is the description of the view. The
‘Predecess’ column specifies the predecessor of that view. So in this case, the predecessor of
ZMM_V_MARA is ZMM_V_MARA itself. The predecessor of ZMM_V_MARC is ZMM_V_MARA and the
predecessor of ZMM_V_MARD is ZMM_V_MARC. The ‘DEP’ column explains whether the entry is a
Header entry or a Dependent entry. It is ‘R’ for the view ZMM_V_MARA, because it is a header entry and
does not depend on any other view. Whereas, it is ‘S’ for ZMM_V_MARC and ZMM_V_MARD, because
ZMM_V_MARC is dependent on ZMM_V_MARA and ZMM_V_MARD is dependent on ZMM_V_MARC.
The column ‘POS’ specifies the sequence of the views. In the column ‘Start’ select the radio button
against the entry for ZMM_V_MARA as it comes first in the hierarchy.

After entering the above entries, press ‘Enter’. Three pop-ups for each view would appear as shown
below. Proceed further by clicking on ‘Enter’ key.
Now select each line and click on ‘Field-dependence’ button. A pop-up appears saying ‘Field
dependencies successfully generated’.

Generate the field dependence for the views ZMM_V_MARC and ZMM_V_MARD in the same way. Now,
save the entries and go back to ‘Header Entry’ folder. Activate the view cluster. A pop-up appears as
shown below. Click on ‘Yes’.
The view cluster is now created successfully.

Note:

1. The view cluster can be created on the tables whose data has to be stored in a hierarchical
manner.

2. One has to check whether proper foreign key relationships are maintained between the tables
appearing in the cluster. Sometimes while generating the Field-dependencies, errors may occur if
the foreign keys are not maintained properly.

Testing the View Cluster

From the initial screen of the transaction ‘SE54’ give the view cluster name and click on ‘Test’.

Since we have created the view cluster on standard tables MARA, MARC and MARD we observe that all
the existing entries would appear. The screen shot below shows all the existing entries of the table
MARA. In order to see the corresponding Plant details for the material, just select an entry and double
click on Plant details as shown below.
The plant details would appear. In the same way for the corresponding storage location details,
select an entry and double click on Storage details as shown below.

In the above screen shot the material selected in the Material details view would appear as a header
entry. The storage location details are as follows:

In the above screen shot the material selected in the Material details view and the plant selected in the
Plant details view would appear as header entry.
Row level locking of database table
By Swetabh Shukla, Infosys Technologies

Normally if a person opens table maintenance generator and tries to maintain the table, no one
else can maintain the same table at the same time. This is because of table level lock by default
in SAP. Only one user can maintain any table at a time through SM30 or any transaction that
calls table maintenance generator. In the tutorial below we will see how to remove table level
lock and apply row level lock. This way any number of users can modify the table at same time.
But any particular row can be modified by only one user at a time. We will create a transaction
for this purpose. The transaction will call our custom report. This custom report will call the
table maintenance generator of the table after deleting table level lock.

In current example let’s create following:

Report: ZREP_SHUKS3

Transaction: ZTEST_SHUKS3

Table: ZTEST_SHUKS3 with table maintenance generator.

Using transaction ZTEST_SHUKS3 we will delete the table level lock and put row level lock so that
multiple users can maintain table at same time. Rows locked by one user will not be editable by other
user.

1. Create table ZTEST_SHUKS3.

2. Create table maintenance generator for the table.

We will make single screen maintenance for this table. Save it. So finally we have table maintenance
code automatically generated in function group ZTEST_SHUKS3.

3. Create lock object EYTSS_E433SH in SE11. Give it name as EZTEST_SHUKS3.

Now save and activate the Lock object. SAP creates two function modules corresponding to lock object
for enqueue and dequeue of the table.

4. Now create a report ZREP_SHUKS3 and transaction code ZTEST_SHUKS3 to call this report. This
tcode will call table maintenance generator of table ZTEST_SHUKS3 .
5. Normally if a person opens table maintenance generator and tries to maintain the table, no one else
can maintain table at the same time. This is because of table level lock by default in SAP. Only one
user can maintain any table at a time. In report ZREP_SHUKS3 we will delete the table level lock and
put row level lock so that multiple users can maintain table at same time. Rows locked by one user
will not be editable by other user. Check the report and comments given below.

*&---------------------------------------------------------------------*
*& Report ZREP_SHUKS3
*&
*&---------------------------------------------------------------------
*& Author : Swetabh Shukla
*& Date : 05/22/2009
*& Description : To delete table level lock from table.
*&---------------------------------------------------------------------*
REPORT zrep_shuks3.

**Selection range for view maintenance

DATA:
BEGIN OF selekttab OCCURS 1. "Selektionsbereich
INCLUDE STRUCTURE vimsellist.
DATA: END OF selekttab,

**Table of inactive CUA functions for view maintenance

BEGIN OF excl_cua_funct OCCURS 1. "inaktive CUA-Fkt bei View-Pflege
INCLUDE STRUCTURE vimexclfun.
DATA: END OF excl_cua_funct.

DATA: lt_enq_del TYPE STANDARD TABLE OF seqg3,

lt_enq_read TYPE STANDARD TABLE OF seqg7,
lw_enq_read TYPE seqg7,
lw_enq_del TYPE seqg3,
lv_subrc TYPE sy-subrc.

*Read all the lock details in system

CALL FUNCTION 'ENQUE_READ2'
EXPORTING
gclient = sy-mandt
gname = ' '
guname = '*'
TABLES
enq = lt_enq_read.

*We will search entry for table level lock for our table
LOOP AT lt_enq_read INTO lw_enq_read
WHERE gname EQ 'RSTABLE'
AND garg CS 'ZTEST_SHUKS3'.
MOVE-CORRESPONDING lw_enq_read TO lw_enq_del.
APPEND lw_enq_del TO lt_enq_del.
ENDLOOP.

*Delete table level lock entry for our table

CALL FUNCTION 'ENQUE_DELETE'
EXPORTING
check_upd_requests = 1
IMPORTING
subrc = lv_subrc
 TABLES
enq = lt_enq_del.

*Now call the table maintenace generator.

CALL FUNCTION 'VIEW_MAINTENANCE_CALL'
EXPORTING
action = 'U'
view_name = 'ZTEST_SHUKS3'
show_selection_popup = 'X'
TABLES
dba_sellist = selekttab
excl_cua_funct = excl_cua_funct.

Just one more change in table maintenance screen. Now open table maintenance function
group(ZTEST_SHUKS3) in SE80.We know for table maintenance SAP automatically creates code in
the function group. Now we will make some modification in that existing code to change the behavior.
Open the screen you created through table maintenance and add one module.

Open the screen 0001 and add one module in PBO of the screen as shown in figure below.
Check the code below to be added in the module m_change_locking.

MODULE m_change_locking OUTPUT.

*Call the function module corresponding to the lock object we created
CALL FUNCTION 'ENQUEUE_EZTEST_SHUKS3'
EXPORTING
matnr = ztest_shuks3-matnr
werks = ztest_shuks3-werks
EXCEPTIONS
foreign_lock = 1
system_failure = 2
OTHERS = 3.
IF sy-subrc NE 0.
* row is locked..hence gray..
LOOP AT SCREEN.
screen-input = 0.
MODIFY SCREEN.
ENDLOOP.
ENDIF.
ENDMODULE. " m_change_locking OUTPUT

7. Now we are ready for testing. Call the transaction once and make some entries in table. In below
screenshot I have entered some random values. Since we have not maintained any check tables etc,
so values may be invalid. That can be taken care in real scenario.
Save data.

Let’s call two sessions of the transaction ZTEST_SHUKS3.

Session 1

In first session we will call the transaction ZTEST_SHUKS3 and try to open some existing values for table
maintenance.

Let’s open an existing value material = MAT1 and Plant = 0678.

So the entry opens in change mode.

Now open a second session of the transaction and see. Now the same material and plant combination
can not be changed by any other user or session.

Session 2

Open transaction ZTEST_SHUKS3

So we can see that our transaction is able to achieve a row level locking and has removed table
Creation of a table pool and pool table
By Kiran Kumar Kandakatla, Intelligroup

In this Tutorial, we create a Table pool first and then create/ (add a table to Table pool) a Pooled Table.

Step 1:

Go to transaction SE11. Go to Utilities à Other Dictionary Objects

Step 2:

Select Radio button Table pool/Cluster Give table Pool Name: ZTBL_POOL.

Then press F5 or choose Create.

Step 3:

Then Select Radio button Table Pool. Press Enter.

Step 4:

Then you go to maintain Poll Screen there give Short Description.

Step 5:

Then go to Technical settings.

Step 6:

In the “Maintain technical Settings” screen Provide Size category.

Save and activate the table Pool. Go back to SE11.

Step 7:

Go to SE11 ABAP Dictionary: Initial Screen.

Create a Z table.
Step 8:

Maintain Delivery and Maintenance attributes for the Z table.

Add fields to the Z table.

Maintain Technical settings and Enhancement Category.

Step 9:

Then Go to Extrasà Change table category

Step 10:

Choose Table type.

In our Example it is Pooled table.

Step 11:

Go back to Delivery and Maintenance tab and provide Pool/Cluster value.

We have successfully created Table pool and Pooled table.

Adding new values in Standard Domain
By Mohan Babu K J, IBM India

Open any domain in which you want to add new values.

In Menu, Goto->Fixed Values Append and click OK for information message.

Give Append Name and ok.

Then add new values in the value append.

Save and Activate it. If you go back to Domain, you can view your values.
Comparison of Transparent, Pool and Cluster tables
By YSP, Defiance technologies

Transparent Pool Cluster

Contain a single table. They are used to hold a They are used to hold
Used to store master large number of very data from a few number
data small tables(stores of large tables.(stores
customizing data or system data)
system data)

It has a one-to-one It has a many-to-one It has a many-to-one

relationship with a table relationship with a table relationship with table in
in the database in the database the database

For each transparent It is stored with other Many cluster tables are
table there is one pooled tables in a single stored in a single table
associated table in the table called table pool in in the database called a
database the database table cluster

The database table has The database table has The database table has
the same name, same different name, different different name, different
number of fields and the number of fields and number of fields and
fields have the same fields have different fields have different
names names names

There is only a single Table pools contain Contains less tables

table more tables than table than table pools
clusters

Single table can have Primary key of each Primary key of each
one or more primary key table does not begin table begins with same
with same fields or fields fields or fields

Secondary indexes can Secondary indexes Secondary indexes

be created cannot be created cannot be created

They can be accessed They can be accessed They can be accessed

using open and native using open SQL only using open SQL only
SQL

USE: They are used to USE: They reduce the USE: They would be
hold master data e.g. amount of database used when the tables
Table vendors or table resources needed when have primary key in
of customers. Example many small tables have common and data in
of transaction data is to be opened at the these tables are all
orders placed by same time accesses
customers simultaneously
Creating a projection view
By Gokul R, Iteanz Technologies

We use projection view to mask unwanted fields and display only relevant fields in a table. Basically View
acts like a database table only, the difference is view will not occupy storage space.

1. Creating Projection View

2. Choose Projection View in the pop up which appears when you click on create
3. Give Description & base Table name(In this example we have taken KNA1)
4. After giving table name click on Table fields button
5. Choose the fields which you want to be displayed in output and click copy
6. Now Save, Activate & execute it, output will be
Summary

In standard SAP tables we will have many fields, of which we will use only few fields. whenever we go
and view the data we have to come across unwanted data, to avoid this and get display of field which
relevant to scenario we use this projection view.
Providing multiple selection options in Search help
By Virendra Soni, Zaffera Softwares

This document specifies how to include multiple select options for the given fields in the search help. For
example below we can see that for material we have single selection possible.

So to convert it in the select option we need to follow certain steps.

We need to create a “Search Help Exit” in search help. Search help exit is a function module with the
same interface like “F4IF_SHLP_EXIT_EXAMPLE”.
Double click in the search help exit name and paste the following code lines:

DATA:type_info LIKE dfies.

callcontrol-no_maxdisp = 'X'.

IF callcontrol-step EQ 'SELECT'.
callcontrol-step = 'DISP'.
ENDIF.

CHECK: callcontrol-step EQ 'DISP'.

CALL FUNCTION 'TABCONTROL_VISIBLE'

EXPORTING
visible = 'F'
tab_id = 1.

SUBMIT zmat_search VIA SELECTION-SCREEN AND RETURN.

IMPORT record_tab TO record_tab FROM MEMORY ID 'REC1'.

READ TABLE shlp-fielddescr INDEX 1 INTO type_info.

type_info-leng = 18.
CLEAR type_info-offset .
MODIFY shlp-fielddescr INDEX 1 FROM type_info
TRANSPORTING leng offset.

callcontrol-step = 'RETURN'.

Create a executable program and paste code lines like this:

REPORT zmat_search.

TABLES: mara,makt.
TYPE-POOLS: slis.
DATA: gs_fcat TYPE slis_fieldcat_alv ,
 gt_fcat TYPE STANDARD TABLE OF slis_fieldcat_alv ,
gs_layout TYPE slis_layout_alv .

DATA: record_tab TYPE STANDARD TABLE OF seahlpres,

gs_record TYPE seahlpres.

DATA:BEGIN OF gs_output,
matnr TYPE matnr,
brand_id TYPE mara-brand_id,
saiso TYPE mara-saiso,
saisj TYPE mara-saisj,
saity TYPE mara-saity,
maktx TYPE makt-maktx,
chk TYPE c,
END OF gs_output,
gt_output LIKE STANDARD TABLE OF gs_output.

SELECT-OPTIONS:matkl FOR mara-matkl matchcode object wwg1,

brand FOR mara-brand_id,
saiso FOR mara-saiso NO INTERVALS NO-EXTENSION,
saisj FOR mara-saisj NO INTERVALS NO-EXTENSION,
saity FOR mara-saity NO INTERVALS NO-EXTENSION.

START-OF-SELECTION.

SELECT mara~matnr
mara~matkl
mara~brand_id
mara~saiso
mara~saisj
mara~saity
makt~maktx
FROM mara INNER JOIN makt ON mara~matnr = makt~matnr AND makt~spras EQ sy-
langu
INTO CORRESPONDING FIELDS OF TABLE gt_output
WHERE mara~matkl IN matkl AND
mara~brand_id IN brand AND
mara~saiso IN saiso AND
mara~saisj IN saisj AND
mara~saity IN saity .

PERFORM build_fcat USING : 'MATNR' 'Article' 'X' ,

'BRAND_ID' 'Brand Id' '' ,
'SAISO' 'Season Category' '' ,
'SAISJ' 'Season Year' '' ,
'SAITY' 'Rollout' '' ,
'MAKTX' 'Description' '' .

gs_layout-box_fieldname = 'CHK'.
gs_layout-colwidth_optimize = 'X'.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING
 i_callback_program = sy-repid
i_callback_pf_status_set = 'PF_STATUS_ALV'
i_callback_user_command = 'USER_COMMAND_ALV'
is_layout = gs_layout
it_fieldcat = gt_fcat
TABLES
t_outtab = gt_output
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 build_fcat
*&-------------------------------------------------------------------FORM build_fcat USING us_fieldname T
YPE c
us_seltext_m TYPE c
us_key TYPE c.

gs_fcat-fieldname = us_fieldname .
gs_fcat-seltext_l = us_seltext_m .
gs_fcat-key = us_key .
APPEND gs_fcat TO gt_fcat .
CLEAR gs_fcat .

ENDFORM. " build_fcat

*&---------------------------------------------------------------------*
*& Form pf_status_alv
*&-------------------------------------------------------------------

FORM pf_status_alv USING rt_extab TYPE slis_t_extab.

SET PF-STATUS 'YSTANDARD' EXCLUDING rt_extab.
ENDFORM. "pf_status_alv

*&---------------------------------------------------------------------*
*& Form user_command_alv
*&-------------------------------------------------------------------
FORM user_command_alv USING r_ucomm LIKE sy-ucomm
rs_selfield TYPE slis_selfield.
CASE r_ucomm.
WHEN 'EXC'.

LOOP AT gt_output INTO gs_output WHERE chk EQ 'X'.

WRITE gs_output-matnr
TO gs_record-string(18).

APPEND gs_record TO record_tab.

 ENDLOOP.

EXPORT record_tab TO MEMORY ID 'REC1'.

LEAVE PROGRAM.

WHEN '&IC1'.

READ TABLE gt_output INTO gs_output INDEX rs_selfield-tabindex.

IF sy-subrc EQ 0.

WRITE gs_output-matnr
TO gs_record-string(18).

APPEND gs_record TO record_tab.

EXPORT record_tab TO MEMORY ID 'REC1'.

LEAVE PROGRAM.

ENDIF.

WHEN '&FB03'.

SET SCREEN 0 .
LEAVE SCREEN.

ENDCASE.

ENDFORM. "user_command_alv

Save and activate both Search help and Search help exit and run the search help.

Screen – 1
Press enter,

Screen – 2
Press Enter.

Screen - 3

Give the selection values and press F8. Output will show in ALV. Select any line and find the values in the
corresponding selection box.
This search help can be attached to the standard search help say MATNR search help in MM01. BASIS
will perform this action.
Automatically populating the search help values into
different fields on the selection screen by using search help
exit
By Krishna Chaitanya Gogineni, Deloitte Consulting

Requirement overview:

I have a selection screen with some fields. For scheduling agreement field I have given the F4 help by
using search help exit.

When user clicks on F4 for scheduling agreement, in the search results along with the scheduling
agreement I’m giving Item, date, and some other fields.

Now, the requirement is when ever user selects a scheduling agreement from F4 help I need to populate
the corresponding item automatically from the search help on to the Item field on the selection screen.

Solution:

In the above screen shot if I select 30000018 and click enter, corresponding item (000020) should get
populated into the Item field on the selection screen.

After displaying the search help values, when CALLCONTROL-STEP = ‘RETURN’ we need to call the
function module ‘DYNP_UPDATE_FIELDS’.

IF callcontrol-step = 'RETURN'.
DATA : i_dynp TYPE STANDARD TABLE OF dynpread.
DATA : w_dynp TYPE dynpread.
 w_dynp-fieldname = 'S_POSNR-LOW'.
w_dynp-fieldvalue = gv_posnr.
APPEND w_dynp TO i_dynp.
CLEAR : w_dynp.
CALL FUNCTION 'DYNP_UPDATE_FIELDS'
EXPORTING
dyname = 'SAPMZKLIM_HUREPORT'
dynumb = '0300'
request = 'A'
TABLES
dynpfields = i_dynp
EXCEPTIONS
invalid_abapworkarea = 1
invalid_dynprofield = 2
invalid_dynproname = 3
invalid_dynpronummer = 4
invalid_request =5
no_fielddescription = 6
undefind_error =7
OTHERS = 8.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
EXIT.
ENDIF.

Result:

When I select the agreement, corresponding item (20) will get populate into item field in the selection
screen.
Creating custom search help for transaction MM03
By Debarun Battabyal, TCS

Step-1 : Go to transaction SE11. Create an elementary search help

Step-2: Enter the selection method as ‘ MARA’. Write the search help parameter as required.
Save and activate.

Step-3: Go back to main screen of SE11 and change The MAT1_A search help (standard search help).

Step-4: Go to tab-‘Included Search Help’ and add the above created Search help (e.g.: zkh_size).
Step-4: Selecting the added search help, go to Parameter Assignment button. Enter the reference
parameter as required.
Demo on Search help exit for the material
By Naveen Kumar Kusuma, OpenText Technologies

Search help exits are used to restrict the standard search help returned values according to users’
requirement.

Example:

Scenario: When User1 require only Material type as Finished goods and User2 require only Material type
as Raw material, for this scenario we can use search help exit.

Go to SE11, select the search help radio button.

To restrict the values for Material by Material type search help name is: MAT1T_E

Click on change button.

For this create a function module, write the logic according to the requirement and place the function
module in marked location.

Function module structure definition: Create a parameters in changing and Tables tabs as follows.
Write the following code in the source code tab.
Code:

DATA : WA_TEMP LIKE RECORD_TAB,

IT_TEMP LIKE RECORD_TAB OCCURS 0.
IF CALLCONTROL-STEP = 'DISP'.
IF SY-UNAME = 'XXXXXX'.
LOOP AT RECORD_TAB INTO WA_TEMP WHERE STRING+3(4) = 'FERT'.
APPEND WA_TEMP TO IT_TEMP.
CLEAR: WA_TEMP.
ENDLOOP.
CLEAR: RECORD_TAB[].
RECORD_TAB[] = IT_TEMP[].
CLEAR: IT_TEMP[].
ELSEIF SY-UNAME = 'YYYYYY'.
LOOP AT RECORD_TAB INTO WA_TEMP WHERE STRING+3(4) = 'ROH'.
APPEND WA_TEMP TO IT_TEMP.
CLEAR: WA_TEMP.
ENDLOOP.
CLEAR: RECORD_TAB[].
RECORD_TAB[] = IT_TEMP[].
CLEAR: IT_TEMP[].
ENDIF.
ENDIF.

Save and activate it.

Then place the Function module above location in SE11.

Testing:

Go to any Transaction which has material number.

Ex: ME21N. Press F4 on Material Field.

User1 Result:
User2 Result:
Step-by-Step approach in creating a Function Module
By Sasidhar Reddy Matli, ROBERT BOSCH

1. Open SE37 transaction.

Go to Goto à Function groups à Create group.

2. Give the function group name and short text. And click on Save.

3. Save this function group as local object.

4. Then open the transaction se80 and select the ‘Function group’ from the drop down list. Enter the
function group name. Press Enter.

5. Right click on ZSSR and press activate.

6. Then you will get the following screen. Press Enter.

7. Go to the transaction se37 again and click on create.

8. Now it will ask for the function group. Enter the function group and give the short text. Press Save.

9. Click on the Attributes tab and give the short text.

10. Click on the Import tab and enter the Parameter name, Type and Reference type of variables A and
B.

11. Click on Export tab and enter the Parameter name, Type and reference type of RES.
12. Click on Exceptions tab and enter the Exception and short text for that exception.

13. Now click on the Source code tab and write the following lines as shown bellow.
14. Press syntax check button or Ctrl+F2.

15. Now press on Activate button or press Ctrl+F3.

16. Press Enter.

17. Now Press on Test button or Press F8.

18. Enter values for A and B. And press Execute or F8.

19. The following screen will be displayed with result.

20. If you enter A value as 5. it will throw exception.

21. Output with Exception.

 Now create and enjoy more Function Modules.
Calling an RFC function module from one system to
another
 By Gaurab Banerji
 Following are the participant system for our demo purpose:

 D05 – System where RFC function module exists

 DS3 – Calling system (an RFC call is made from this system to D05)
 Scenario:

 We would develop a small RFC function module in D05 system, which would add two
variables. We would pass two variables from DS3 to D05 and get back the sum of those
two variables back to DS3.

 Activities to be performed in the system D05

 Go to SE37.

 Under Utilities > Create Function Group (say ZGB_FUNC), if doesn’t exists.

 Now create a New Function Module ZGB_FUNC01

 Under IMPORT Tab, define the following variables

 Under EXPORT Tab

 In the Source Code

 Now set the function module as “Remote-enabled module” in the attributes tab.


 Activities to be performed in the System DS3

 Create an RFC destination from DS3 to D05.

 Go to SM59, Press Create.

 Enter the RFC Destination name: D05-205-TEST

 Connection Type: 3

 In Description: Test Connection to D05

 In The Technical Settings Tab, enter the system details

In The Logon/Security Tab, enter the logon details.

 Click on Save. A Popup will imply that connection has been created
 Now Press the TEST CONNECTION to check the connection.


  This means the connection to the remote system was successful.

 If the connection fails we get an error like this

However establishing a connection will not ensure logging on to the target system. For that we have to
test REMOTE LOGON.

Press the REMOTE LOGON button

If we can see this

And this

Then our connection was successful.

However if we see the screen as shown below then there is an authentication failure (user-id or password
is wrong).
The new connection will become visible in the SM59 list like this.

After establishing the connection, let us create a program, which would trigger the RFC in D05 system.

Go to SE38 and create a program ZGB_RFC

Write the following code

Activate (Ctrl+F3) and Execute (F8)

Type any two numbers.

Press (F8) Again. We have the desired output.

Merging multiple transport requests into one
By Piyush Mathur, Tata Consultancy Services

This document provides the step-by-step procedure to merge multiple transport requests into single
transport request.

Let’s start with small introduction with transport request.

Transport requests are available to transport the developed objects/Configurations from one system to
another system. In general, we develop the objects first in Development system and later move it to
Quality and Production system.

There are two types of transport requests:

1. Workbench Transport Request

2. Customizing Transport Request
Workbench Request:

Workbench request records client independent objects like reports, Functions, tables. Client independent
objects are available across the system irrespective of client.

Customizing Request:

Customizing request records client dependent objects like table entries, SPRO configurations. Client
dependent objects are only available to particular client.

SE01, SE09 and SE10 are the transaction codes for SAP Transport Management system.

Below are the steps to merge the transport request.

***You can only merge multiple Workbench transport requests in Workbench request and same applicable
to Customizing request.

Execute transaction code SE10, select the radio button “Workbench Requests” and click on display.

Following list is displayed with the Workbench requests (modifiable):

For example you need to merge above two transport requests into one request.

First click on New and create a workbench request.

Now select the Transport request in which you want to merge another request. Click on merge button and
give the transport request no. Cick on Green tick.
Now expand the request, you will get the entry of merged transport request.

With same steps you can add more transport requests in your request.

Above steps holds good if you need to add/merge one or two transport requests. Sometimes there might
be a requirement to merge more requests in one. In such cases, proceed as mentioned below:

First create a new transport request and click on merge as specified in above steps. Now select ‘Object
lists from multiple requests’ and press on green tick.
Following screen is displayed:

Now enter all the transports requests numbers which need to be merged and execute.
Click on “Merge”

A popup screen to confirm the action is displayed. Click on “Execute online”.

Now expand the transport request. You will find all the merged transport requests.

Similarly we can also merge customizing requests.