Defining Customising Table

Customising is very important tool in SAP to modify behaviour of SAP programs to suit business requirement. You can argue that customising is one of the way of removing hard-coding from a program and making it future proof. There are many parameters in program which can be either hardcoded or store in some kind of table which then modify the behaviour of program by having different value in table. I am sure you can think of many scenario which fits the bill and sure you have created many custom customising table during implementation. In this blog I will explain how to define a customising table in such a way that every time you make change to its record it will prompt for customising request. And later explains you how to add this customising table in SPRO as a node so all your customising table remains organised and accessible to people who are responsible to make configuration.

For the purpose of this blog let’s consider this scenario

I have custom data entry screen in purchase contract transaction ME31K which should only work for certain purchase contract type. Now I can either hard code this in screen exit stating specific contract type in ABAP code or read a table which list all contract type that would require the custom data entry. I choose to create table instead of putting contract type in code because with table future requirement will just require new entry in table instead of modification of ABAP code.

1. Defining customising table

Assuming that you already know how to define custom table, I am just highlighting what specific things you need to consider if you like to use customising transport for move value across you landscape. Define table with delivery class C and ‘Display/Maintenance Allowed’.

Next step add fields to your table. Make sure to add MANDT field, otherwise table will be client independent and instead of customising request system will prompt for workbench request. If defining client independent table is indeed you intention then just be informed that you will be saving you values in workbench request.

In technical setting choose data class as APPL2 and check ‘Log change data’.

Save and activate the table.

Create table maintenance screen using table maintenance generator.

2. Create parameterise transaction for table maintenance generator

Go to transaction SE93 type in transaction name and press new button, choose transaction with parameters.

On next screen enter SM30 as transaction, check ‘Skip initial screen’ and enter fields name as shown in screen shot below.