Difference between customizing and configuration?

Is there any Difference between customizing and configuration?

Hi Rajesh,
What is Client? What is the difference between Customization and Configuration?
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.
Reg,
Ashok

Similar Messages

Difference between customization and configuration

Hi Sir's
Could i know difference between customization and configuration as well as validation and substitution
Thanks
Edited by: manjusap36 on Oct 22, 2009 7:23 PM

Hi,
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.
Moreover:
Configuration: Attaching to process flow to the existing one
Customization: Adding new fields/Tables as per client requirements. to customise or adapt the system to your business requirements, which is the process of mapping SAP to your business process. It 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/modifications may not easily migrate to the new version.
Regards
Devi

Difference between 'setup' and 'configuration' in Oracle Apps

Hi,
Thank in advance.
I want to know Difference between 'setup' and 'configuration'(Oracle Apps ). Could you provide the details with an example, please?
Regards,
Raghavendra Rao

Business Requirement:-
===============
A company may want to allow all of its employees to make purchases up to $10 without having such purchases approved. Another company may have a business rule that each employee’s approval limit depends on his or her position within the organization.
Question:-
=======
How to reach the above requirement?
Is it thorugh configuration or setup?
It must be through configuration and not set up.
Set up is something like one time.. Configuration can be changed depends on your business needs.
Like if your company wants to increases the limit from 10 to 100$, then change in configuration is needed.
Hope you got the answer.. if you want more explanation, please be specific....

Difference between customisation and configuration

hi solve the problem

Hi,
Configuration - Deals with setting up the SAP system to meet the customer requirements. Configuration generally meets the requirements based on the existing set up available in the system
Customization: It also referes to tuning the SAP system to meet the requirements. But customization may also involve, custom developed objects, user defined reports etc.
Example:
Configuration: Configuring Automatic Payment Setup
Customizing: Having the company logo available on the reports (This requires bit of changing the code)
Regards,
Sridevi
Award points, if useful

Difference between Cofiguration and Customzing

Hi,
What's the difference between Cofiguration and Customzing.
BR
Govind

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.

Difference between custom controller and component controller

Hi All,
I am a beginner in CRM SAP .
Please can anyone tell me whats the difference between custom controller and component controller with some scenario.
I am totally baffled.
Thanks in advance.
Regards
Shilpi

Hi Shilpi,
The main difference between custom and component controller is the role which they play during data transfer.
a) Custom controller is used for data transfer across two views within a component. For that you need to bind view context nodes to custom controller either through wizard or manually by adding the code in CTXT class create_contextnode method:
initial setting for depandant model node
    coll_wrapper =
      BTADMINH->get_collection_wrapper( ).
    TRY.
        entity ?= coll_wrapper->get_current( ).
      CATCH cx_sy_move_cast_error.
    ENDTRY.
    IF entity IS BOUND.
      BTOpportH->on_new_focus(
                   focus_bo = entity ).
    ENDIF.
b)Component controller is used for data transfer across two views in two different components. For this, we need to define the component usage first and then bind the context nodes in the method-WD_USAGE_INITIALIZE of the Component Controller impl class.
    WHEN 'ComponentUsageName'.
      iv_usage->bind_context_node(
                  iv_controller_type = cl_bsp_wd_controller=>co_type_custom
                  iv_target_node_name = 'ContextNodeName' "#EC NOTEXT
                  iv_node_2_bind      = 'ContextNodeName' ). "#EC NOTEXT
Hope this clears some of your doubts!
Thanks and Regards,
Rohit
P.S-This is valid for CRM 2007.Raghu is also right because Interaction Center is made up of different different components combined together.You have put your question in wrong forum.

What is the difference between Custom controller and context controller?

Hi Gurus,
What is the difference between Custom and context controller?
In which occasion we should prefer to use Custom Controller?
Thanks in Advance,
Dharani

You mean difference between custom controller and component controller???
if yes...
its been discussed many times.... just go through these threads, you will be clear
custom controller vs component controller
Component Controller and Custom comtroller
[ why we need Custom controllers in Model Applications |why we need Custom controllers in Model Applications;
[CONTROLLER AND CONTEXT|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/944ea9e5-0601-0010-65b3-b49a56eb6385]
Pradeep
Edited by: pradeep bondla on Jul 22, 2008 12:42 PM

Difference between customizing request and workbench request?

Hi ,
What is the difference between customizing request and workbench request?
please reply.........

HI,
Workbench Requests
When you change a Repository object of the ABAP Workbench, a query window appears in which you need to specify a Workbench request. You can only save the changes if you have assigned the object to a change request.
Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients. However, you can also include client-specific Customizing.
Whether the changes to Repository objects are transported depends on whether a transport route is defined from the current SAP System for the package of these objects. From the system settings, the system automatically determines whether the change requests are transportable and to which target system they should be transported.
Customizing requests
Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).
Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.
Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually.
pl reward if it helps.
Thanks
Sadhu Kishore

Difference between WinentupgradeforSA and Winentupgrade license do both these licenses help customer downgrade to Win7 enterprise .

Difference between WinentupgradeforSA and Winentupgrade license do both these licenses help customer downgrade to Win7 enterprise .

Hi,
Just to make a supplement, you can refer to the contents of the link below for the description about SA:
http://www.microsoft.com/licensing/software-assurance/
Roger Lu
TechNet Community Support

Key Configuration differences between SAP and ORACLE Financials

Hello,
After spending good 7 years in SAP related projects recently I started working in ORACLE Applications. I used to be an ORACLE programmer years back. To my surprise the same ORACLE Forms are still very much the heart of the ORACLE UI.
Then I thought what will be the key differences between ORACLE and SAP in terms of configuration elements. While I know a bunch of configuraion items in SAP , I am not sure about the same in ORACLE world. I am not even sure some of the configuration items that are available in SAP exists in ORACLE.
Does anyone know both sides of the coin ? The terminology and design ?
SAP has
Client,Company code, Business area, Functional Area, GL, Posting Key, Document Type.
I am trying to get the details of the equivalents of these in ORACLE.
Does anyone know it ?
For e.g , when you post to AP or AR in SAP , GL is updated automatically. In ORACLE you post to a AP Book or AR Book then Run a batch to move them to GL Book.
ORACLE uses SQLLoader to load data . You can write a PL SQL and update the tables directly, which is not the case in SAP. For dataloads and conversions, SAP uses BDC's ( though XI can be used but its slow).For ORACLE its the good old SQL and PlSQL combo.
What are the equivalents of the configuration elements in ORACLE world ?
Also what are the major differences between these two in terms of designing a financial system.
Does any one know ?

Genie,
I agree that a case is made on how well these two ERPs solve the day to day tasks before a company chooses one of these two. But my question is aimed at finance to begin with. You are going to need a general ledger for any company or government regardless of ERP. And how well you can drive the ledger to map your business is the key here.
The way ledger is built is around a business area ,company or country and is very tighly designed in SAP. I would like to know if there is any equivalent of the configuration items in ORACLE. I am more interested in terminology of ORACLE.
For example ,
SAP ====> ORACLE
GL ==> Book In ORACLE
Document Number ===> Invoice Number
Posting Period in SAP ==> Posting period In ORACLE
Most of the terms are finance terms , so they are common ( eg. an account number is an account number in ORACLE and SAP ) between two systems. I am interested in any specific thing that is available in ORACLE but not in SAP and vice verse.
thanks for the link you have provided.
Its very useful.

Difference between Customer Include and Append

Hi all,
We are using a special customer namespace /XXX/. Regarding to this I can not use the Customer Includes (CI_Include) in the SAP tables anymore to add own fields.
To create my own fields anyway I create a append in the /XXX/ namespace and add my /XXX/fields to this Append.
It is working, but I want to know if there are situations where the use of an append instead of an include can cause errors?
What is the difference between include and append?
Thanks in advance for your help,
Fabian

Hi
NO, because they are the same thing, you use both includes to enhance a standard structure.
But the Append Include is only used in the structure where it's defined, CI_INCLUDE is used by enhancement so perhaps it can be used in many structures.
So you have to use CI_INCLUDE only if you need to you its enhancement.
If the name of include begin of CI_, you won't have any error if that include doesn't exist.
You can try to build a Z-TABLE and insert the include CI_ZMYINCLUDE after try to check your table: any errors'll occur.
The same this is for the include with the name begining with ZX...
Max

Difference between customer exit and user exit?

hi experts
difference between customer exit and user exit?

These r the main differences between user exits and customer exits
1) user exits r subroutines where as customer exits r function modules
2) user exits r not upgraded where as customer exits r will upgrade
3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
4) customer exits r reusable where as user exits r not reusable.
Also:
1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
Please go through the following link which will help you understand the exits in a much better way:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://sap.niraj.tripod.com/id21.html
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/ab038.htm
User Exits.
http://www.erpgenie.com/sap/abap/code/abap26.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
1. Previously there were only user-exits.
2. Then came the concept of customer-exits.
3. user exits were nothing but subroutines
FORM/PERFORM
called from standard programs.
4. The FORM defintion was placed inside
an empty include file.
5. So It was called EVERYTIME.
and we need to MODIFY/REPAIR the
standard include .
6. Then it came with concept of customer-exit
7. It consists of calling a FUNCTION MODULE,
which is called only if
the user-exit is ACTIVATED (other wise not called)
In this case, the code in put inside
a pre-defined Z include.
8. Functionality of both is same, howerver
we can note the following important differences
a) Customer exit is called only if activated.
(hence, it does not waste resources)
b) in customer exit, REPAIR does not happen
to the standard include.
Exits are basically the hooks whcih SAP has provided to add your own code.
User Exits: These are provided only SD module .
They are Empty subroutines with naming like USEREXIT_.
We need to have Access key to implement them.
Customer Exits: These are enhancement techniques.
There are defined in SMOD and implemented in CMOD.
Types of Customer exits: Function exit, Screen Exit, Menu exit.
User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
Customer Exit,
Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
Customer Exit
SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
They do not affect standard SAP source code
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
They do not affect software updates
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
User Exits: allow you to add additional functions to the SAP standard.
Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors
reward points if found useful
regards
palak

Difference between Customer Generated Extractors and Generic Extractors

Hi all,
Can anyone please tell me the difference between Customer Generated Extractors and Generic Extractors. I know that for all modules Generic extraction is possible by creating a datasource(RSO2) on top of a table, View or SAP Query in SE11. What are customer generated extractors like LIS, CO/PA and FI/SL.
What kind of extraction is used for FI/AR and FI/AP. To my understanding we have BW Content Extractors. Can anyone explain the extraction method and delta extraction for AR and AP.
Thanks,
Sabrina.

Hi,
Customer generated extractors are running on top of statistics data collection process in R/3. They extract data from statistical tables already available in R/3 and also use the mechanism already provided in R/3 to capture the delta.
For example, PO data goes to statistical table S012 (it is an LIS table) and you can build a generated extractor on top of it. The difference between such extractor and a generic one is the fact that these extractors (eg LIS) use the same mechanism of capturing delta that the statistics table was doing (for example data that goes into S012 is also captured by these generated extractors). Some system tables and structures are generated automatically to support this functionality, you do not have to develop anything for this.
Generic extractors on the other hand simply let you pull data from table/view/query etc. You have to develop code/functionality to support delta capturing for such extractors. If you built a generic extractor on top of S012 (it is a statistical table - LIS), you can pull its data to BW, but you do not have the delta capturing functionality in such case, you will have to code it yourself.
As a thumb rule, you go with the standard/generated extractors, and use generic extractors only if it is necessary to be so.
FI/AR and FI/AP extractors are part of business content (I think) and support delta functionality. To get detailed info on these, you can also look at help documentation -
http://help.sap.com/saphelp_nw04/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
cheers,

What is the difference between customer exits and user exits?

hello friends,
what is the difference between customer exits and user exits?

Hi
User exit - A user exit is a three character code that instructs the system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP.   XX represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.     *-- Mani
The following document is about exits in SAP :-
The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications.
SAP creates user exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
Types of Exits
There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
Menu Exits
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Screen Exits
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
Function Module Exits
Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.
When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.
Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.
These calls have the following syntax:
CALL CUSTOMER-FUNCTION 001.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
    CASE okcode.
        WHEN 'BACK OR EXIT'.
            CASE sy-dynnr.
                    WHEN '100'.
                         SET SCREEN 0.
                         LEAVE SCREEN.
                    WHEN '200'.
                         SET SCREEN 100.
                         LEAVE SCREEN.
             ENDCASE.
      ENDCASE.

Difference between customer exits and user exits

difference between customer exits and user exits

Hi,
USER EXITS->
1. Introduction:
User exits (Function module exits) are exits developed by SAP.
The exit is implementerd as a call to a functionmodule.
The code for the function module is writeen by the developer.
You are not writing the code directly in the function module,
but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
CUSTOMER EXITS-> t-code CMOD.
As of Release 4.6A SAP provides a new enhancement technique, the Business Add-Ins.
Among others, this enhancement technique has the advantage of
being based on a multi-level system landscape (SAP, country versions, IS solutions, partner,
customer, and so on)
instead of a two-level landscape (SAP, customer) as with the customer exits.
You can create definitions and implementations of business add-ins at any level of the system landscape.
To unify enhancements of the SAP Standard you can migrate customer exits to business add-ins.
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
In order to find out the user exits for any tcode,
1. get the developement class of the tcode from SE93.
2. Now goto transaction SMOD and press F4,
3. give in the Deve class in the dev class and Press ENTER
this will show u the exits for any tcode.
or execute this report
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
Regards
Kiran Sure

Difference between customizing and configuration?

Similar Messages

Maybe you are looking for