Approach to add new fields to FD32 Screen in SAP

Author: Suresh B Marati

Date: 02/13/2013

Objective of this paper is to present the process of adding custom fields to transaction
FD32 in SAP.

Let’s consider a scenario of adding the fields for storing the information per customer
and division, especially for the share customer between various divisions of company,
each customer will have unique information per company code or may be for any other
purpose there is a requirement to add new fields to FD32 standard transaction,
following approach can be used:

%0%.1Append the Structure in table KNKK with name ZKNKK which has fields with
necessary description with a unique field name starting with a Z, Data Element and a
Data Domain.

%0%.2.Module Pool Program has a similar sub-screen with the screen field related to
the field name from the table KNKK.
.
%0%.3.Add the code in PBO of the custom sub-screen, for making the field input to be
disabled for transaction FD33, and it should be input enabled for transaction FD32.

%0%.4.Standard SAP Program ‘SAPMF02C’ calls a function module named as

‘OPEN_FI_SUBSCREENS_GET’. In this function module there are some configuration
tables that are to be maintained for adding custom sub-screen to transaction FD32.

The function module ‘OPEN_FI_SUBSCREENS_GET’ is used to create the sub screen

and the field on the FD32 Screen.

There are four tables (T061S, TBE12, TBE22, and TBE23) as shown in the code
snippet are required to be maintained.

The following steps are used to maintain the table T061S using SM30 Transaction.

Put the table name T061S in the Table Field and click on Maintain.

Click on NEW ENTRIES button to add new entries

2
For adding sub-screen we shall create new entry where we need to fill the following details.

Program (MPOOL): Text field should have the program name which will be calling the function module
OPEN_FI_SUBSCREENS_GET.
For transaction FD32 program ‘SPAMF02C’ call the above function module.
Number (LNUMM): Text field will be the Consecutive number.
Partners (PARTY): External services supplier
Product (PRDKT): External supplier’s product
P module pool (SPOOL): This will be the module pool program name containing the custom screens.
Partner screen (SDYNN): This will be the screen no. from above program which will be added in
transaction.
Table (TNAME): Table name in which fields from custom screen should be added and updated.

Following screen shot shows if we have 6 similar entries for adding the 6 sub-screens
with different Screen nos. as shown below.

Function Module checks if there is any entry in the T061S if found for every entry it gets
the Partners (PARTY) from T061S check whether that Partner activated or not in Table
TBE12.
So we have to maintain the entry in the TBE12 for Product (PRDKT) ‘ZXXX’ as below.

TBE12 entry

3
AKTIV Specifies Partner ‘ZXXX’ active or not? If X it is active.

Similarly After getting entry from TBE12,function module check whether there is any
entry for corresponding Partners (PARTY) ‘ZXXX’ and Product (PRDKT) ‘KNKK’ in
table TBE22 and TBE23 respectively.

So we have to maintain entry in TBE22 and TBE23 as below.

TBE22

TBE23

After checking all required configuration, function module gets the custom module pool
program name and screen no. which will be later assigned to the sub-screen area of the
particular screen in the standard transaction FD32.