Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Customizing Switch

Former Member
0 Likes
1,169

Hi

i am confusing about customizing switches and profile parameters.

1. What are the customizing switches?

2. What are all the tables like PRGN_CUST, SSM_CUST ?

3. We have profile parameters to configure settings in the Profiles, So why we need Customizing settings ?

4. What is the diff between customizing switches and profile parameters ?

Thanks in Advance

NAG

3 REPLIES 3
Read only

jurjen_heeck
Active Contributor
0 Likes
721

One of the major differences between profile parameters and customizing switches I can think of is that profile parameters are for the whole instance whereas some customizing switches are client dependent.

Interesting question.

Read only

Former Member
0 Likes
721

HI

The customizing proceedure is affecting on the clients (in) dependent and generate the TR to move into the other system, but the parameters settings are affecting only the system instances.

Regards

Anwer Waseem

SAP BASIS

Read only

Former Member
0 Likes
721

>

> Hi

> i am confusing about customizing switches and profile parameters.

>

> 1. What are the customizing switches?

> 2. What are all the tables like PRGN_CUST, SSM_CUST ?

> 3. We have profile parameters to configure settings in the Profiles, So why we need Customizing settings ?

> 4. What is the diff between customizing switches and profile parameters ?

>

> Thanks in Advance

> NAG

Hi,

1. Customising switches refer to configuration settings which define the way that the SAP application works. Generally used to modify standard SAP to meet your requirements

2. Some common security relevant customising tables are PRGN_CUST, SSM_CUST, USERS_SSM and SSM_VAR

If you do an F4 lookup in these table fields you will (mostly in PRGN_CUST) often see settings and a related OSS note created to fix a problem or offer an alternative behaviour. If you log into OSS and enter those table names you will get a number of high level OSS notes which detail what they can be used for and various options available.

3. As with many things in SAP there are always lots of different ways to do things. Profile parameters generally operate at the lowest level and involve system and kernel activity. Customising often refers to the application level behaviour of your SAP system. When making fixes, it is much easier to change the ABAP side than to create a kernel patch. In situations like frequent setting users and menu's via USERS_SSM or variables via SSM_CUST, you don't want to have to modify a profile parameter and potentially have to bounce the box. You also wouldn't want config people having access to maintain the profile params either.

4. See answer to number 3