The XI does not send messages with correct IDOC structure

[Former Member]

SAP XI 3.0 sends to ECC IDOC HRMD_A07

The XI does not send messages with correct IDOC structure.

In XI Design, Software Component RHEVOLU, I’ve imported the Objects

HRMD_A.HRMD_A07 from SAP ECC; In Tools -> Export Reduced XSD, I saved

HRMD_A.HRMD_A07.xsd in Namespace http://suezambiental.com.br/HR . At

Message Mapping -> mmAdmissao, in Imported Message -> Import XML or

XSD, I imported the reduced Idoc file generated above, mapping source

fields to target fields.

The IDOC sent from XI to ECC has this structure (template: 22122)

E1PLOGI

E1PORIG

E1PITYP

E1P0000

E1P0001

E1P0002

Status 53 -HR: ALE inbound processing for HR master data

But does not update HR Master data.

The structure expected in ECC side (template: 20376) is:

E1PLOGI

E1PORIG

E1PITYP

E1P0000

E1PITYP

E1P0001

E1PITYP

E1P0002

Status 53 -HR: ALE inbound processing for HR master data

By using WE19 transaction, this structure was changed manually; so, the

HR Master data was updated.

Witch kind of customizing or correction could be made in XI, to send

the correct structure to ECC?

Best Regards

Claudio

[former_member529475]

hi Claudio,

even though the IDOC was created with 53 status some times it may gives some internal errors. U can see that errors using the tcode wper. Check the idoc error status in the tcode

Cheers,

Vasudeva Rao. V

[Former Member]

Hi Claudio,

In your case, there are perhaps two causes:

1. perhaps when you have import the idoc, for a strange reason, a bad metadata was created by XI. You can clean this one in tcode <b>IDX2</b> (Idoc metadata cache).

2. but it's also probably an error in your Message Mapping. Have you correctly manage segment E1PITYP?

Regards

Mickael

[HarshC]

Hi Claudio,

Check the IDoc Structure in

a. IDX2

b. Integration Repository.(Message Mapping)

If you have changed the structure recently, you would need to reimport it into both a & b.

Regards,

Harsh

[moorthy]

Hi,

You can check your message in XI during runtime so that , you can analyse the error

1) Go to SXMB_MONI and check both inbound and outbound messages

2) Check the mapping ...

Probably some of the segments are not mapped, because of optional.. check this with mapping.

Regards,

Moorthy