Skip to Content
Author's profile photo Christopher Solomon

HCM Processes & Forms: PA Infotype text?… is easier than you think!

     When a developer hears the words “free form text” or a requirement involving the word “notes” or even better “we need some where for the user to enter ‘stuff’ (that most technical of technical terms!)”, it is usually either met with a groan or a panicked thought like “what?!?! how am I going to do this?!?! keep smiling…nod…say you can do it”. In the case of HCM P&F, it is actually much more painless than you might think.


      I will admit, the first time I was asked to do such a thing on a HCM P&F project, I was a bit baffled at first myself. I just kept thinking of the decoupled infotype structure fields we had available and not seeing how a “note” or “text” would get saved in there. My “plan B” (as usual) was “well if the framework can’t handle it, I can do it in an Advanced Generic Service or in a backend workflow step”. I actually found out that it was about 1000 times easier than I could have imagined.

     I have seen others come across this and ask in the forum how to do it as they too seem to be under the impression that this will be some kind of daunting combination of configuration and coding. However, it is almost as simple as adding one line in configuration.

     Here is what you do by way of an example…….

1. In your HCM P&F configuration for your SAP_PA service, let’s say you have an operation on infotype 0015 (Additional Payments).



2. Now, in the configuration for our “fields”, you will simply look in the decoupled structures for your selected infotype (here, IT0015) to find the one called HCMT_BSP_PA_TEXT and map your own form scenario field to it. This is the KEY to it all!!!


3. On our form, you can see we have the field mapped and bound to a “text edit”, multi-line field on the Adobe Interactive Form.


4. The user can simply fill it in with whatever they like…..”free form”.


5. After the user completes it and it is sent through the process to the update, we can then look in PA20 at the IT0015 record and select “Display Text” from the top menu…


….and we will see the text just as we entered it on the form!


See now…that was not so bad was it? haha Hope this helps settle any “pains” for others. As always….until next time….. (I have a series of LENGTHY blogs coming soon. You were warned. haha)….

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Good post Chris. Yes some infotypes have multiple Screen Structures which may provide additional functionality to saving backend data. Certainly makes life easier than writing custom logic in the AS.

      Author's profile photo Former Member
      Former Member

      Good one Chris...hidden feature of HCM P & F  🙂 In my previous projects, I wasted time doing this in workflow step!.

      Author's profile photo Christopher Solomon
      Christopher Solomon
      Blog Post Author

      Thanks. Sorry if it was too late for you, but maybe your work was not all in vein.

      Author's profile photo Dave Jones
      Dave Jones

      I noticed that your text string is only 73 characters.  When I apply this same process to my form, SAP is truncating the text at 78 characters.  Even though all all data definitions are type string, deep in the SAP code the sting is parsed (separated by carriage return) into 78 byte table records.  No matter what I type, SAP truncates to a single 78 character string.  I have found a way around the problem but is more of a hack than a solution.  Any ideas?

      Author's profile photo Former Member
      Former Member

      Hi Dave,

      Do you mind sharing what you did to get this to work?  I'm trying to load text on IT0183 for an awards program we have and I'm running into the same problem you had.  It only loads the first line of text from my form and truncates everything after the 78th character.

      Any help would most be appreciated.



      Author's profile photo Cody Deckard
      Cody Deckard

      Hi Bob,
      I ran into the same issue as Dave. I ended up creating a background program which is kicked off when the form is saved to the backend and I pass the infotype text container value and call the following class method.



      Author's profile photo Former Member
      Former Member

      I have searched for a solution to the truncation mentioned here and saw a couple of responses of workarounds, but I can't find any code suggestion.  Could someone share?



      Author's profile photo Martha Paget
      Martha Paget


      Looks like SAP has released a fix for the 78 char comments limit.

      2581637 - Process & Forms: Infotype Comments truncated after 78characters





      Author's profile photo Christopher Solomon
      Christopher Solomon
      Blog Post Author

      Thanks for the update!!!!


      Author's profile photo Del Roig
      Del Roig

      Finally SAP has provided a NOTE to resolve the issue of only saving 78 characters on the Infotype Text .  It took them 3 versions of the NOTE to get it correct and unfortunately my client had to experience the short-comings of the other 2 versions but here it is ....


      Note : 2654467 - HCM P&F: Infotype Comments truncated after 78 characters through SAP_PA service.

      Enjoy ......

      Author's profile photo Del Roig
      Del Roig

      FYI .... the note 2581637 – Process & Forms: Infotype Comments truncated after 78characters referenced back in January is only called if you happen to be using the SAP_PT service.