Difference between Cofiguration and Customzing

[former_member660849]

Hi,

What's the difference between Cofiguration and Customzing.

BR

Govind

[dhrubacharan_behera · Accepted solution]

Hi,

Both the things are so nearer that defining these is difficult .However as I understand, configuration is arranging or mapping business scenario's provided by the sap standard where as customization arises when there is gap between the sap standard and business requirement,at that time we need to custom the sap as per requirement .For this sap has

provided us user exits, routines, and programme editors

etc., to use for customization.

Dhruba

[Former Member]

Hi,

Configuration is the mapping the business process in SAP as per client requirement.

Customization is changing the standard process given by SAP by coding as per client requirement.

Configuration example - Assigning one or more plants to company codes, doing some settings as per client requirement.

Cusomization example - Developing new program (which is not in standard SAP) to fulfil client requirement.

Hope u got it.

Regards,

Ganesh

Award if Useful

[former_member660849]

ok

[Former Member]

hi

As such there is no difference between the two.(in general both are used interchangeably).

configuration relates to general changes done in SAP standard system according to business required but no changes in coding is done.

But in customising changes in standard coding is done to make the system as per business requirement.

Regards,

Vijay

[pankaj_singh9]

Hi,

The difference between customizing and configuration is;

CONFIGURATION: - We will configure the system to meet the needs of your business by using the existing data.

CUSTOMIZING: - We will customize or adapt the system to your business requirements, which is the process of mapping SAP to your business process.

Configuration Vs Customization: -

When considering enterprise software of any type, it is important to understand the difference between configuration and customization. The crux of the difference is complexity. Configuration uses the inherent flexibility of the enterprise software to add fields, change field names, modify drop-down lists, or add buttons. Configurations are made using powerful built-in tool sets. Customization involves code changes to create functionality that is not available through configuration. Customization can be costly and can complicate future upgrades to the software because the code changes may not easily migrate to the new version. Wherever possible, governments should avoid customization by using configuration to meet their goals. Governments also should understand their vendor's particular terminology with regard to this issue since words like "modifications" or "extensions" often mean different things to different vendors.