Segment E1PITYP occurs for each subtype of Infotype 1001 in update mode

[Former Member]

Hi,

I am using transaction PFAL and IDoc HRMD_A for transferring HR data.

In update mode the resulting IDoc contains segment E1PITYP for each subtyp (for example A002) of Infotype 1001 even if it contains no segments of type E1P1001.

Could somebody explain this and is it possible to avoid this behavior?

Thanks and regards

Patrick

[Former Member]

hi,

go to Transaction WE30 and look for the segment definition for your Messagetype (Basistype).

Segment E1PITYP occurency is defined from 1 to 99999999 and not mandatory.

(SUB)Segment E1P1001 is ordered under E1PITYP and if you make a filter or deletion of this segment, the higher segment is still existing.

If the there is no higher Segment, the IDoc will not be created.

[Former Member]

Hi,

thanks for your answer.

Still I am little bit confused and want give an more detailed description of my problem.

If I export an organizational unit in initial mode I have for example 5 segments of type E1PITYP and each of them has a subsegment (for example E1P1001).

Export of the same organizational unit in update mode results in more than 200 segments of type E1PITYP and all of them without subsegment.

This seems to happen for all infotypes (not only 1001 like I thought before).

Now I want to understand why this happens and if it's possible to update an organizational unit without segments of type E1PITYP that don't have a subsegment.

Regards

Patrick

[Former Member]

Hello,

I am having the same problem described above:

For all employees I see all infotypes and subtypes of the distribution model in the idocs. Even if the employee does not have an infotype or one specific subtype. In this case, node E1PITYP appears without child node.

Did you finally manage to solve this error?

Thanks a lot for your help

Br,

Jesus

[pamela20]

Hi,

We are currently experiencing the same issue where a parent node E1PITYP is shown without a child node.

Can someone please confirm if they were able to resolve this issue?

Thanks!