Skip to Content
avatar image
Former Member

difference between customization and configuration


what is the difference between customization and configuration.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Mar 17, 2007 at 07:00 AM

    Hi Raju,

    In a simple way, sap to business mapping is configuration and business to

    sap is customization. In the sense, if whatever functionality is provided by

    can work then we just go by that. But in reality generally there are some

    differences between whats provided in sap as a standard and what the client

    needs. so SAP is modified as per that requirement which is nothing but

    customization.Ex: In SAP standard customer analysis is T-code MCTA which displays customer incoming orders,sales & credit memo value but the client may need more data like price,tax,discount etc. which can be customised in Z-REPORTS.


    Message was edited by:

    rajib mahalik

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      The difference between cutomizing and configuration is:

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

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

      - CLIENT: A client is a unique one in organizational structure, can have one or more company codes. Each company code is its own legal entity in finance.

      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



  • avatar image
    Former Member
    Mar 17, 2007 at 11:01 PM

    Check the link below:




    Add comment
    10|10000 characters needed characters exceeded