Query regarding HRP table updation in EHP4

Question

Hello Experts,
Recently we have upgraded our system to EHP4 and we have done data migration of the E-Recruitment to Career Profile (eg. data migration from HRP9301 to HRP7402 infotype).
The infotype HRP7402 has a field called TABNR at the last and there is an include provided where we have included 2 more essential fields.
But when i am updating the HRP7402 (internal table has the correct data), this TABNR (length 32) is getting filled in the infotype automatically which is fine but it is having leading spaces because of which the remaining 5 characters are being moved the other 2 fields (the fields which are included in the include provided) after this field.
The same TABNR is getting populated perfectly in other infotypes where it is the last field and there are no additonal enhancements done in the standard include provided.
Please let me know on how can i resolve this problem of leading spaces which are automatically getting added up.  And I am not clear on where this TABNR is getting filled up in the FM. The following is the code snippet....
        CALL FUNCTION 'RH_INSERT_INFTY'
          EXPORTING
            fcode               = 'INSE'
            vtask               = 'D'
            order_flg           = 'X'
            commit_flg          = 'X'
            authy               = 'X'
            repid               = sy-repid
            form                = 'FILL_DATA'
          TABLES
            innnn               = it_p7402
FORM fill_data TABLES ct_tabinfty_tab
  USING ct_infty TYPE any
        ct_tabix TYPE any.
  CLEAR ct_tabinfty_tab. REFRESH ct_tabinfty_tab.
  ct_tabinfty_tab = ' '.
  APPEND ct_tabinfty_tab.
ENDFORM.  
Thanks
Raj Kishore

Answer 1

Sorry to intervene here Dhina but that is just halfways correct.
If delivery class NOT = C then it is NOT a customizing table and therefore you wont get any transport request updating or deleting data from it.
But if it is a customizing table then you got to look for the recording routine. You can see this by viewing your table in SE11, then using the menu like following:
utilities->table maintainance generator.
Then look at the info in the bottowm frame. if "standard recording routine" is tagged, then you get a transport request.
If the other option is tagged you wont get it. What again means you can customize this table directly in the system where you need those entries.
why is that?
well assume there is a customizing for e.G. materials, depending on materialnumber. If that table would have a standard recording routine you would need ALL your materials in your development system which would be quite unusual.
Edited by: Florian Kemmer on Jun 9, 2011 2:00 PM
some typos corrected, left some for sure