Doubt

[Former Member]

Hai all,

1. What is the difference between configuration and customisation?

2. What is cutover strategy?

3. What is Legacy system.

Kedar

[reazuddin_md · Accepted solution]

hi,

1<b>- Configuration</b> is nothing but map the client scenario into SAP system by using its applications without any modification.

Eg: If u r client has Over the counter sales, where the customer place an order,process del the goods n collects the bill at the same time.To map this we use the "Cash sales" Process in SAP.

Here we didnt make any changes,

<b>Customization-</b>- to meet the requirement we need to do some modifcations for the standard system.

say for eg: while creating credit memo request,billing block will be triggered through some Z* table,instead of doc type.for this we copy the credit memo request from std sap n rename it, but we remove the billing block in credit memo req-in VOV8,

2- Company is running from the last 100 years, now implementing SAP with in its organization, where company doesnt want all the 100 years data,

they want to maintain from the last 20 years data only,

then they will consolidate 80 years data, made a base line, from there 20 yrs data will be uploaded into sap servers,

this is maintained in a seperate servers, which is knows an<b> MDM- Master Data management.</b>eg: Comany has 40 yrs customer's sales data, instead of uploading 40 yrs sales data, consolidate 30 yrs data as base amount, n maintain only past 10yrs sales data. known as "<b>Business Migration Work Strategy "</b>

3- Software application which the organization using before implementing SAP is called as Legacy system , simply other than SAP system in which client is running their business.

*Hope it Clears, Reward Points

[Former Member · Accepted solution]

HI raj,

It was good explanation. Can you give a better example for Customization....

Ghassan

[reazuddin_md · Accepted solution]

HI ,

we had the client requirement for their exhbition cum sales ,for those kind of sales ,item wont be returned after it is delievered and billed .

we can do this in cash sales process.

we have created a new sales doc type(from copying standard CS),customized as the division in sales order should take always form material master record and divison should be same at both doc level and item level,

<b>Chek division should be - 2 Error,</b> in i

tem category - <b>ZBVN(copiend from BVN) ,mark off " returns</b>"-

which meant i tz not relevant for the returns.

no need to maintain Copy Control bet CS- RE.

I hope itz bit clear.

for that,

[Former Member]

hi ,

Cut over strategy: Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies

With regards

Rajesh

[Former Member]

hi,

Before starting up your SAP systme, you must adjust its business -independent functionality to the specific business needs or your company. this is called customizing.

Configuration:configure the system to meet the needs of your business by using the existing data

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

Migrate the data from Non-sap system to sap is called legacy system