Error in subroutine read_namtb for structure of infotype

Question

We are trying to transfer HR Master data between ERP 5.0 and ECC 6.0 systems .
The data transfer is successful in the development and Quality environments but fails in case of production environment.
Details are given below
Message type : HRMD_A
Idoc type : HRMD_A06    ( Release 620 )
When we try running PFAL using any evaluation path the idoc at the receiver ends up with an status 51 (error) .
The error log gives the following error .
u201CError in subroutine read_namtb for structure of infotypeu201D.
I tried posting the received Idoc again at the receiving end using the transaction WE19 with the function module u201CIDOC_INPUT_HRMDu201D .
The observations are given below.
1.     While processing some of the records the infotype table name field becomes empty .
2.     The subroutine read_namtb uses a FM u201CNAMETAB_GETu201D ,  which takes the input as the infotype table name and provides the output as all the fields of the table along with the attributes of the field.
3.     As sometimes the table name is passed empty the function module returns an error which is mentioned above.
Note : If we run PFAL without providing any evaluation path the idoc at receiver ends up with status 52 ( Application not posted completely).

Answer 1

Hi Hadiman,
I will activate those BADI's and check.
But we solved the problem in a different way.
Below is the analysis of the error.
1.     The data was getting passed in an additional segment E1PAD007 in the production environment from the sender system.
2.     During the inbound process the FM u201CRH_INFTY_OF_IDOCSEG_TYP_GETu201D is used to identify the respective infotype and the subtype
for the segment name in the receiver system.
3.     The function module searches for the tables T777D and table T77ar to fetch the infotype and the subtype.
4.     The table T77ar does not contain the relevant entry .
5.     The segment is related to a relationship u201C007u201D between jobs and positions.
6.     As we do not need jobs in the target system, we removed the object type u2018Cu2019 from the model distribution.  This resolved the error.
Note : The other way to resolve was to make an appropriate entry in the table T77AR .
Thanks a lot Hadiman for the reply, will check with those BADI's too which you mentioned
Regards,
Santosh.