Q

Guidelines or methodologies for customizing SAP

Our company would like to use SAP as close to 'vanilla' as possible - but we understand some customization is clearly...

required. Are there any published guidelines or methodologies on determining what acceptable customization/personalization a customer can make to SAP?


It is a good idea to have a policy statement that SAP will be used in it's 'vanilla' state. This will help to guide the implementation and reduce the requests for changes. As part of this document, include a process to follow should a need for customization occur. This will give a detailed record of the change that will be helpful in the future. My preference would be to avoid changing SAP code, but instead use the tools provided by SAP to tailor the system to your needs. You might want to check with your SAP rep to see if they have documented guidelines on this matter.


This was last published in July 2002

Dig Deeper on SAP application integration

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close