Changing standard SAP field descriptions
Sep
01
2005

Sometimes you absolutely need a couple of fields to input all your information, so you end up using an unused field. What happens if the field description does not match, not even closely the information you put in it?

Well you have several choices:
- You could live with it.
- You could create your own data dictionary for your users, so that they know that field X in fact represents Y (but this has to be for a very limited number of fields)
- You could change the standard SAP description of the field – but bear in mind that you’ll probably need to multiply that effort by the number of languages used within your company.

So here it goes – what I will show here is by no way a recommendation and I take no responsibility for you doing it!

To illustrate this example we will change the description of a field from the material master. In this case I selected the field ‘Prod./Insp. Memo’ (Production/Inspection memo) which is usually found in the basic data views. It is a nice field because it is an information field: There is no customizing table behind it.


Before we do anything, we need to get some technical information on that field. So position the cursor on the field for which you want to change the description, display the technical information and note the data element (do function key F1 / technical information to get it). In this case the data element is ‘FERTH’.


Now follow the path to select the transaction indicated.
menu path

or simply type the transaction code CMOD in the transaction window.
CMOD

You’ll be sent to a screen called ‘Project Management of SAP Enhancements’. In that screen select the menu as indicated (Goto / Text enhancements / Keywords / Change).


You’ll then have to select the language in which you want to change the description (if you are working in a multi-language environment, you’ll have to repeat this step for every language maintained).
In the field ‘Data Element’, type the Data Element name noted earlier.


The following screen will then be displayed. That screen has several fields. They contain the various descriptions for the data element selected. Depending on what screen/layout this data element is used the system will use one of the short, medium or long description fields. The Heading field will as its name suggests be used in the list header row of a layout. The Short Description field will be used when you select the function key F1 (help) on that field.

The length of each field is :
- Short field label: 10 characters
- Medium field label: 20 characters
- Long field label: 40 characters
- Heading: 55 characters
- Short Description: 60 characters

Replace the texts with those that you want to appear. For example: Save your changes (depending on your setup, record this in a customising request). Note that this is a cross client change.

Now if you go back in the material master for example, the field displays the new information.

And if you select the function key F1 (help) you’ll actually see the text corresponding to the Short description appear – Note that the downside of this is that only the first line is changed. The rest of the help text refers to the standard help documentation.

This technique should be used when all other options have been investigated and there is no other way around. Don’t go on a SAP renaming spree!

Technorati tag:

17 Responses to “Changing standard SAP field descriptions”

  1. Gravatar of Amit Amin Amit Amin

    thanks for such a nice posting.

  2. Gravatar of Vhong Reymar Vhong Reymar

    Hi,

    Thanks for this great page!

    Is there any way that we can change the Standard Domain of the Standard Data Element?

    For example, the data element PREIS has a domain WERT11 with data type CURR and length of 11. The requirement is to extend the data type of PREIS into data type TB_CURR_11_5 with a length of 16.

    Can we do this enhancement? And how?

    Thank you very much!

  3. Gravatar of Murali Murali

    Thanks for this post. It is really helpful.

  4. Gravatar of renet@web renet@web

    Glad to be of help. Thanks for the comment.

  5. Gravatar of Anjani Anjani

    I have a quick question – If you change the label using CMOD as described by you guys, is there any chances that it would get over written during upgrades?

    Thanks

  6. Gravatar of renet@web renet@web

    Anjani, yes I think that would happen.

  7. Gravatar of Sheryl Dickert Sheryl Dickert

    Very informative and concise. Thanks so much.

  8. Gravatar of Babusingh Babusingh

    Hi,

    Reali It is Woderfull information

    Thanks

  9. Gravatar of Sharik Sharik

    Hi,

    This solution is simple, easy and works very well. Why is it recommended to use it as a last resort?

    Regards,
    Sharik

  10. Gravatar of Zakir Zakir

    Keep the good work up, buddy !!!

  11. Gravatar of fenny fenny

    hai, i will ask about how to call function module in SAP with PHP. I’m so confused, how to insert the import value in function with php ?? i have tried many times, but, the always no value. If I check in SAP, there is a value.
    Can you tell me how to call it ? thank you.

  12. Gravatar of Marcos Marcos

    Thanks for this post. It is really helpful.

  13. Gravatar of cá estamos » alterar descrições de campos no SAP cá estamos » alterar descrições de campos no SAP

    [...] http://www.renet-web.net/2005/09/01/changing-standard-sap-field-descriptions/ [...]

  14. Gravatar of victort victort

    its’ really appreciate you share it with us, thank you very much :)

  15. Gravatar of Piyush Dhyani Piyush Dhyani

    Great document, its is very userful. It is well eloborated and clearly explained

    THanks for publishing such a nice document

  16. Gravatar of harry harry

    What a splendid way to share your knowledge. Thanks Pascal, it’s exactly the input I needed for my decision making.

  17. Gravatar of Isuru Isuru

    Great help. thanx!

Leave a Reply



Other entries you might like

You only need to go through the forums on SDN to realise that there are people out there that actually write programs or develop LSMW’s to upload Planned Independent Requirements (PIR) into SAP. Whilst I am sure that there are many valid reasons for wanting to develop your own upload programs, it is a shame [...]

Read more


This is really a quick tip that I’m posting more for me, but which I thought I’d share with the rest of the community.
If you are using the Service Desk functionality of Solution Manager, you may know that it is possible to create support requests right from your satelite SAP system. This is a really [...]

Read more


What I will explain here is particularly useful if you are using SAP Solution Manager, but it could also be applied to SAP CRM.
Solution Manager offers a very powerful functionality in that which is Service Desk. However I think that you are missing an important aspect of it if you do not set up automatic [...]

Read more


The details herein contained in this post relate to the solution manager VAR scenario – i.e your organisation acts as a service desk for your SAP customers. Whilst some of the concepts explained here might be of use to a CRM consultant, they are first and foremost destined for Solution Manager consultants setting up their [...]

Read more


According to Wikipedia, “Rich Internet Applications are web applications that have most of the characteristics of desktop applications, typically delivered by way of standards based web browser plug-ins or independently via sandboxes or virtual machines”. I don’t think that this definition does do it any justice – I think that RIA’s are:

Applications that offer a [...]

Read more