Z Extension ALEAUD missing in XI / PI side

[carlos_ocampos]

Hi guys..

I have an strange problem. We made an Extension of ALEAUD Idoc to add a couple of fields needed. The Z extension in R3 are created correctly and we can see the new Z segment with correct values. But when Idoc is sent to XI, this segment is missing.

We have made the configuration needed to receive ALEAUD as normal message using IDX_ALEREQUEST and it works fine. Now with Z extension, we receive the message but with missing Z segment.

We have made the following steps with no results:

1.- Check in IDX2 for metadata. (Correct).

2.- Parnet Profile in R3 are corrected updated with Z extension.

2.- Re-import several times Idoc structure in Integration Builder.

3.- Restart XI server.

xml-idoc in XI side :(Segment Z1EINFO with fields BELNR and PARTN is a child of E1PRTOB but is missing)

<?xml version="1.0" encoding="UTF-8" ?>

- <ZALEAUD01>

- <IDOC BEGIN="1">

- <EDI_DC40 SEGMENT="1">

<TABNAM>EDI_DC40</TABNAM>

<MANDT>900</MANDT>

<DOCNUM>0000000007505754</DOCNUM>

<DOCREL>701</DOCREL>

<STATUS>30</STATUS>

<DIRECT>1</DIRECT>

<OUTMOD>2</OUTMOD>

<IDOCTYP>ALEAUD01</IDOCTYP>

<CIMTYP>ZALEAUD01</CIMTYP>

<MESTYP>ALEAUD</MESTYP>

<SNDPOR>SAPDV1</SNDPOR>

<SNDPRT>LS</SNDPRT>

<SNDPRN>DV1CLNT900</SNDPRN>

<RCVPOR>SAPXID</RCVPOR>

<RCVPRT>LS</RCVPRT>

<RCVPRN>XIDCLNT700</RCVPRN>

<CREDAT>20110616</CREDAT>

<CRETIM>101559</CRETIM>

<ARCKEY>E097EEB9057BBBF1AFC2005056A915EE 0000000003785002</ARCKEY>

<SERIAL>20110616101559</SERIAL>

</EDI_DC40>

- <E1ADHDR SEGMENT="1">

<MESTYP>ORDRSP</MESTYP>

<MESTYP_LNG>ORDRSP</MESTYP_LNG>

- <E1STATE SEGMENT="1">

<DOCNUM>0000000003785002</DOCNUM>

<STATUS>51</STATUS>

<STACOD>SAPME794</STACOD>

<STATXT>Acknowledgment for PO item & & contains quantity variance</STATXT>

<STAPA1>4500979477</STAPA1>

<STAPA2>00010</STAPA2>

<STATYP>E</STATYP>

<STAMQU>SAP</STAMQU>

<STAMID>ME</STAMID>

<STAMNO>794</STAMNO>

<STAPA1_LNG>4500979477</STAPA1_LNG>

<STAPA2_LNG>00010</STAPA2_LNG>

<STAPA3_LNG>200.000</STAPA3_LNG>

<STAPA4_LNG>180.000</STAPA4_LNG>

- <E1PRTOB SEGMENT="1">

<DOCNUM>0000000007505750</DOCNUM>

</E1PRTOB>

</E1STATE>

</E1ADHDR>

</IDOC>

</ZALEAUD01>

In R3 idoc contains Z segment with correcT values.

One of the interesting things in this case is that in R3 we generate one Idoc with several E1ADHDR segments, but when we receive the messages in XI, an automatic splitting is produced and we receive one Idoc per E1ADHDR segment. Maybe in this automatic spliting we would find the solution, but I'm not able to find it.

Any ideas?

Thanks in advance.

Kind regards

Edited by: Carlos Ocampos on Jun 16, 2011 10:49 AM

[Former Member · Accepted solution]

Hi,

In IDX2, please delete the existing metadata for the Idoc and import it again.

Regards

[carlos_ocampos · Accepted solution]

Hi,

Thanks for your soon reply.

I did it several times, delete and create.. and structure is correctly uploaded, but the problem still happens.

I have executed Cache refresh several times too..but no results.

Thanks

[Former Member]

Hi,

You can check the below OSS note

1391093 IDoc adapter: ALEAUD with customer enhancement

Regards,

Yogesh

[carlos_ocampos]

Thanks but this OSS note doesn't solve my problem.

[Former Member]

Hi,

The standard message ALEAUD proves useful only when this message is exchanged between two R/3 systems ie the ALEAUD IDoc only works with a SAP environment end to end.

Please create a custom IDoc- ZALEAUD and a custom report to replicate RBDSTATE. This works well with XI.

Thanks, Liz

[Former Member]

Hi Carlos,

Just a thought.

Check the data need for this segment is available in the master data you are referring to and check if your z segment is activated properlly.

For testing, you have generate the Idocs in the application server using a file port. Now have you compare the Idocs structure(the header details) with the payload that is hitting to xi system. See if you find any difference.

Thanks,

Jay

[carlos_ocampos]

Hi Jay,

Thanks for your reply. I did it yesterday and this are the results:

XI Version:

<?xml version="1.0" encoding="UTF-8" ?>

- <ZALEAUD01>

- <IDOC BEGIN="1">

- <EDI_DC40 SEGMENT="1">

<TABNAM>EDI_DC40</TABNAM>

<MANDT>900</MANDT>

<DOCNUM>0000000007505772</DOCNUM>

<DOCREL>701</DOCREL>

<STATUS>30</STATUS>

<DIRECT>1</DIRECT>

<OUTMOD>2</OUTMOD>

<IDOCTYP>ALEAUD01</IDOCTYP>

<CIMTYP>ZALEAUD01</CIMTYP>

<MESTYP>ALEAUD</MESTYP>

<SNDPOR>SAPDV1</SNDPOR>

<SNDPRT>LS</SNDPRT>

<SNDPRN>DV1CLNT900</SNDPRN>

<RCVPOR>SAPXID</RCVPOR>

<RCVPRT>LS</RCVPRT>

<RCVPRN>XIDCLNT700</RCVPRN>

<CREDAT>20110616</CREDAT>

<CRETIM>164706</CRETIM>

<ARCKEY>E097EEB9057BBBF1AFC2005056A915EE 0000000003785002</ARCKEY>

<SERIAL>20110616164706</SERIAL>

</EDI_DC40>

- <E1ADHDR SEGMENT="1">

<MESTYP>ORDRSP</MESTYP>

<MESTYP_LNG>ORDRSP</MESTYP_LNG>

- <E1STATE SEGMENT="1">

<DOCNUM>0000000003785002</DOCNUM>

<STATUS>51</STATUS>

<STACOD>SAPME794</STACOD>

<STATXT>Acknowledgment for PO item & & contains quantity variance</STATXT>

<STAPA1>4500979477</STAPA1>

<STAPA2>00010</STAPA2>

<STATYP>E</STATYP>

<STAMQU>SAP</STAMQU>

<STAMID>ME</STAMID>

<STAMNO>794</STAMNO>

<STAPA1_LNG>4500979477</STAPA1_LNG>

<STAPA2_LNG>00010</STAPA2_LNG>

<STAPA3_LNG>200.000</STAPA3_LNG>

<STAPA4_LNG>180.000</STAPA4_LNG>

- <E1PRTOB SEGMENT="1">

<DOCNUM>0000000007505750</DOCNUM>

</E1PRTOB>

</E1STATE>

</E1ADHDR>

</IDOC>

</ZALEAUD01>

File Version:

<?xml version="1.0" encoding="UTF-8" ?>

- <ZALEAUD01>

- <IDOC BEGIN="1">

- <EDI_DC40 SEGMENT="1">

<TABNAM>EDI_DC40</TABNAM>

<MANDT>900</MANDT>

<DOCNUM>0000000007505770</DOCNUM>

<DOCREL>701</DOCREL>

<STATUS>30</STATUS>

<DIRECT>1</DIRECT>

<OUTMOD>2</OUTMOD>

<IDOCTYP>ALEAUD01</IDOCTYP>

<CIMTYP>ZALEAUD01</CIMTYP>

<MESTYP>ALEAUD</MESTYP>

<SNDPOR>SAPDV1</SNDPOR>

<SNDPRT>LS</SNDPRT>

<SNDPRN>DV1CLNT900</SNDPRN>

<RCVPOR>ZXI_XML</RCVPOR>

<RCVPRT>LS</RCVPRT>

<RCVPRN>XIDCLNT700</RCVPRN>

<CREDAT>20110616</CREDAT>

<CRETIM>160953</CRETIM>

<SERIAL>20110616160953</SERIAL>

</EDI_DC40>

- <E1ADHDR SEGMENT="1">

<MESTYP>ORDRSP</MESTYP>

<MESTYP_LNG>ORDRSP</MESTYP_LNG>

- <E1STATE SEGMENT="1">

<DOCNUM>0000000003785002</DOCNUM>

<STATUS>51</STATUS>

<STACOD>SAPME794</STACOD>

<STATXT>Acknowledgment for PO item & & contains quantity variance</STATXT>

<STAPA1>4500979477</STAPA1>

<STAPA2>00010</STAPA2>

<STATYP>E</STATYP>

<STAMQU>SAP</STAMQU>

<STAMID>ME</STAMID>

<STAMNO>794</STAMNO>

<STAPA1_LNG>4500979477</STAPA1_LNG>

<STAPA2_LNG>00010</STAPA2_LNG>

<STAPA3_LNG>200.000</STAPA3_LNG>

<STAPA4_LNG>180.000</STAPA4_LNG>

- <E1PRTOB SEGMENT="1">

<DOCNUM>0000000007505750</DOCNUM>

- <Z1EINFO SEGMENT="1">

<BELNR>4500979477</BELNR>

<PARTN>11291</PARTN>

</Z1EINFO>

</E1PRTOB>

</E1STATE>

</E1ADHDR>

</IDOC>

</ZALEAUD01>

As you can see the only thing different is Z1EINFO with BELNR and PARTN filled in file version and in XI version the field ARCKEY. No more differences. We have in SAP R3 SAP_BASIS 701 and in XI SAP_BASIS 700.

But we dont have any chance to change release of Z idoc to 700 because is something done by system automatically.

Thanks,

Cheers

[Former Member]

1. In SAP System, go to se19 and generate an IDOC with providing the extended idocs type and check the same if this is working fine or not.

2. Go to your partner profile and check the functional module assign to it, to see if this is reflecting with the correct structure and the auth code for the same.

• see ru importing the extended idoc type type or the basis idoc type. I belive once you are extending the segments using for zfeilds you have to create the extended idoc type and that once should be imported in XI syste.

3. In XI system, delete the meta data in idx2.

4. Import the IDOC structure once again.

5. create the meta data in idx2.

6. In the message mapping, map the z fields with the correct node once again.

7. in the configuration reinitiated all the interface mapping and message mapping in receiver determination and interface determination.

8. check your CC channel is reflecting with the correct fields, if this is a idoc to file scenerio then check for the extra feilds updated in the cc.

Each idoc is independenet of the other one.

Hope this helps.

Cheers.

Jay.

[Former Member]

Hi ,

Pls try to do the following in this order.

1. Check the Parner Profile in R3 are corrected updated with Z extension and hope the extended idoc type and any custom segments are released in R/3 thru Tcodes WE30/31 before they are imported in step 3 below.

2. Check in IDX2 for the metadata and delete the existing one.

3. Re-import Extended Idoc structure in Integration Builder and activate the same.

4. If you are having any mappings for the same, then drag and drop the new structure and remap the fields and activate the message mapping and interface mappings. The mapping could be the reason why you are having your messages split across based on the header of the idoc.

5. In your configuration scenario do check your integrated configuration/receiver determination is using the correct extended idoc type names and if yes activate the config scenario components as well.

6. Trigger it from the testing tool in R/3 and see whether its producing the segments.

Cheers

[carlos_ocampos]

Hi , Jayakrishnan Nair

Thanks for your reply.

I have done all steps in order, with no results..

1.- Parner Profile is correct and Z Extension and Z segment are relased.

2.- IDX2 same. I have deleted almos 15 times, and same result.

3.- I have reimport several times too, and structure is correct inside Integration Builder , same as IDX2.

4.- Mappings are updated too

5.- I have created a new scenario, to simplify, just Idoc to file with no mapping, and it doesn't work properly.

The problem is in the source message. I have created a xml file port in R3 to generate Idoc as a file and file are correct with Z extension. As a workaround I could change Idoc per files but from my point of view this is not an elegant scenario.

I have worked many times with this Extension and sometimes I had cache problems, but now I'm a little fustrated.

Thanks anyway,

I'll try to find a solution.

Kind regards.

[carlos_ocampos]

Hi Jay,

Thanks for your reply,

I have followed all your steps in order, with no results.

1.- I think you refers to we19 Idoc tool, and yes when you use it Z segment is there.

Even I have created and Idoc xml file using a xml file port and Z segment is there. See below:

<?xml version="1.0" encoding="UTF-8" ?>

- <ZALEAUD01>

- <IDOC BEGIN="1">

- <EDI_DC40 SEGMENT="1">

<TABNAM>EDI_DC40</TABNAM>

<MANDT>900</MANDT>

<DOCNUM>0000000007505770</DOCNUM>

<DOCREL>701</DOCREL>

<STATUS>30</STATUS>

<DIRECT>1</DIRECT>

<OUTMOD>2</OUTMOD>

<IDOCTYP>ALEAUD01</IDOCTYP>

<CIMTYP>ZALEAUD01</CIMTYP>

<MESTYP>ALEAUD</MESTYP>

<SNDPOR>SAPDV1</SNDPOR>

<SNDPRT>LS</SNDPRT>

<SNDPRN>DV1CLNT900</SNDPRN>

<RCVPOR>ZXI_XML</RCVPOR>

<RCVPRT>LS</RCVPRT>

<RCVPRN>XIDCLNT700</RCVPRN>

<CREDAT>20110616</CREDAT>

<CRETIM>160953</CRETIM>

<SERIAL>20110616160953</SERIAL>

</EDI_DC40>

- <E1ADHDR SEGMENT="1">

<MESTYP>ORDRSP</MESTYP>

<MESTYP_LNG>ORDRSP</MESTYP_LNG>

- <E1STATE SEGMENT="1">

<DOCNUM>0000000003785002</DOCNUM>

<STATUS>51</STATUS>

<STACOD>SAPME794</STACOD>

<STATXT>Acknowledgment for PO item & & contains quantity variance</STATXT>

<STAPA1>4500979477</STAPA1>

<STAPA2>00010</STAPA2>

<STATYP>E</STATYP>

<STAMQU>SAP</STAMQU>

<STAMID>ME</STAMID>

<STAMNO>794</STAMNO>

<STAPA1_LNG>4500979477</STAPA1_LNG>

<STAPA2_LNG>00010</STAPA2_LNG>

<STAPA3_LNG>200.000</STAPA3_LNG>

<STAPA4_LNG>180.000</STAPA4_LNG>

- <E1PRTOB SEGMENT="1">

<DOCNUM>0000000007505750</DOCNUM>

- <Z1EINFO SEGMENT="1">

<BELNR>4500979477</BELNR>

<PARTN>11291</PARTN>

</Z1EINFO>

</E1PRTOB>

</E1STATE>

</E1ADHDR>

</IDOC>

</ZALEAUD01>

Step 2. Partner profile is ok, this in an outbound idoc and you dont need to configure any functional module, just Basic type (ALEAUD01), Extension (ZALEAUD01), Receive port (XI port)

Steps 3,4,5 are done several times and structure looks like good.

Steps 6. I have created a simply scenario without mapping. Idoc to xml file, but source Idoc has Z segment missing.

Step 7. The Idoc->File scenario is totally new.

Step 8. The result file is this:

<?xml version="1.0" encoding="UTF-8" ?>

- <ZALEAUD01>

- <IDOC BEGIN="1">

- <EDI_DC40 SEGMENT="1">

<TABNAM>EDI_DC40</TABNAM>

<MANDT>900</MANDT>

<DOCNUM>0000000007505775</DOCNUM>

<DOCREL>701</DOCREL>

<STATUS>30</STATUS>

<DIRECT>1</DIRECT>

<OUTMOD>2</OUTMOD>

<IDOCTYP>ALEAUD01</IDOCTYP>

<CIMTYP>ZALEAUD01</CIMTYP>

<MESTYP>ALEAUD</MESTYP>

<STDMES>ALEAUD</STDMES>

<SNDPOR>SAPDV1</SNDPOR>

<SNDPRT>LS</SNDPRT>

<SNDPRN>DV1CLNT900</SNDPRN>

<RCVPOR>SAPXID</RCVPOR>

<RCVPRT>LS</RCVPRT>

<RCVPRN>XIDCLNT700</RCVPRN>

<CREDAT>20110616</CREDAT>

<CRETIM>171608</CRETIM>

<ARCKEY>E097EEB9057BBBF1AFC2005056A915EE 0000000003785002</ARCKEY>

<SERIAL>20110616164706</SERIAL>

</EDI_DC40>

- <E1ADHDR SEGMENT="1">

<MESTYP>ORDRSP</MESTYP>

<MESTYP_LNG>ORDRSP</MESTYP_LNG>

- <E1STATE SEGMENT="1">

<DOCNUM>0000000003785002</DOCNUM>

<STATUS>51</STATUS>

<STACOD>SAPME794</STACOD>

<STATXT>Acknowledgment for PO item & & contains quantity variance</STATXT>

<STAPA1>4500979477</STAPA1>

<STAPA2>00010</STAPA2>

<STATYP>E</STATYP>

<STAMQU>SAP</STAMQU>

<STAMID>ME</STAMID>

<STAMNO>794</STAMNO>

<STAPA1_LNG>4500979477</STAPA1_LNG>

<STAPA2_LNG>00010</STAPA2_LNG>

<STAPA3_LNG>200.000</STAPA3_LNG>

<STAPA4_LNG>180.000</STAPA4_LNG>

- <E1PRTOB SEGMENT="1">

<DOCNUM>0000000007505750</DOCNUM>

</E1PRTOB>

</E1STATE>

</E1ADHDR>

</IDOC>

</ZALEAUD01>

Z segment is missing as if by magic.

Thanks a lot for your help,

I'll try to find a solution,

Cheers

[carlos_ocampos]

Hi again,

I have a feeling about release of Idoc, because I'm comparing with others Z extension searching differences and the only one is release. Release of Z segment is 701, Release of Z extension is 701. We work with other Z extension with 700 Release. In transaction We82 we change manually release to 700 but in XI we receive 701. And in IDX2 we have the following release for each segment of Z extension:

E1ADHDR E2ADHDR 30C

E1ADHDR E2ADHDR001 40A

E1STATE E2STATE 30C

E1STATE E2STATE001 30E

E1STATE E2STATE002 40A

E1PRTOB E2PRTOB 30C

Z1EINFO Z2EINFO000 701

What do you thins about that? Do you think that this could be the reason? Our version of XI (3.0) sp 18 release 700.

Thanks in advance.

Kind regards.