Skip to Content

Changing Standard Position Text Field (HRP1000-STEXT) Length

Dear Folks,

There is ask from my Customer to increase the Position Text field (HRP1000-STEXT) length from 40 to 80. I understand we already have some threads, recommending that it is better to avoid the change, and if we still need the change, using IT1002(Descriptions) is mentioned to be the preferred approach.

My question here is;

  1. Can we update the field length of the Standard Position Text field (HRP1000-STEXT) from 40 to 80?
  2. If I can update, would it impact the existing Position data already present?
  3. If I can update, and as it is one of the Foundation table for Org. Mgmt Data, will it impact the integrations with other modules like PA, Payroll etc., and any other impact that we need to be aware because of this change in the Standard field.

Kindly help me clarify these questions, so that we can work on the possible options.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Mar 12 at 03:52 PM

    You are wanting to change the SAP standard data element HR_MCSTEXT from 40 to 80 fields??? Dont do it.

    >> 1. Can we update the field length of the Standard Position Text field (HRP1000-STEXT) from 40 to 80?

    Yes, but it is a modification. Whenever there is a SAP upgrade, this modification has to be confirmed everytime, otherwise it will be reset to the original SAP definition.

    >> 2. If I can update, would it impact the existing Position data already present?

    No, because you are not changing the data type but only making the field larger. The database management system (e.g. Oracle, HANA, etc.) does not have a problem with that and old values will be stay the same.

    >> 3. If I can update, and as it is one of the Foundation table for Org. Mgmt Data, will it impact the integrations with other modules like PA, Payroll etc., and any other impact that we need to be aware because of this change in the Standard field.

    Yes, there will be an impact and you will have to check the functionality of all transactions/reports that use that field directly or through other objects (e.g. tables, views, structures). For example the GUIs will not neccessarily automatically update the field, as it might be copied from/to another data type and also the field visibility length might be restricted to 40 characters and there might not be enough space to display all 80 characters.

    If there is a alternative preferred approach, as you mentioned, I would suggest you take that road.

    Add a comment
    10|10000 characters needed characters exceeded

    • Parthasarathy Sathyanarayanan, if you post an answer, it will only notify the author of the question and nobody else. If you want someone to be notified, either comment that persons answer, or mention them directly in the post, like this Parthasarathy Sathyanarayanan.

      Regarding your question, you ask me to elaborate on it, which I think I have done with the comments to your questions 1, 2 and 3.

      But here a little bit more info about 1:

      • This you can find online in SAP ABAP documentations: Modifications should only be made to the standard when they are necessary for the optimization of specific business processes. Before modifying the standard, it is essential that you are well acquainted with an application's construction and flow logic since such knowledge is necessary if you want to evaluate modification possibilities.The responsibility for a modification's semantic correctness ultimately lies with the person making the modifications.
      • Be aware, that when you upgrade the system, this modification might be reversed, if the people responsible for the upgrade are not thoughful enough, this will lead to you loosing the information that was part of the value greater than the standard length in the database
      • Also, when you are requesting support of SAP that might even only have minimal impact on the modified field, SAP might decline the support, claiming that they cant check that for you, unless all modifications of the standard are not reversed, so that they can reproduce the issue with a standard only coding
  • Posted on Mar 15 at 07:58 AM
    -1

    Thank you Michael and I really appreciate the reply!

    At the very first line of your reply- you mentioned 'Don't Do it'. Can you please elaborate a little more on that? if you see any major risk on this, so that we can make a right decision.

    In summary, based on your overall reply, I understand that the update of standard field is possible and like you said, we need to be careful while handling the SAP Upgrades and other dependent transactions/ reports. But, want to understand if there is any other major risk due to this change.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.