Solved: IDOC with custom segment: z-fields out of order

Hi experts,

I'm working in an IDOC 2 IDOC scenario with a graphical mapping. The IDOCs have a custom segment.

When processing the IDOC is well generated at origen then well mapped in PI (the fields match with the expected values in SXMB_MONI). But, when arriving to destiny the values of the fields of the custom segment doesn't match with their expected values. So, the IDOC fields are fine in PI in SXMB_MONI but are out of order in WE19. The expected values are disgregated between the different fields.

This problem just happend in the custom segment fields, for the standard fields everything is fine.

Any idea?

Regards

Gonzalo

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi Gonzalo,

As I understood your query properly , you are not able to get the new updated custom z fields segment at recieving application. Correct me If I am wrong in understanding your query.

If that is the case just then do the step as mentioned below:

Request you to delete the earlier content of IDOC metadata from IDX2 and import the new content of Standard IDOC with custom field segments.

Thanks & Regards

Prabhat

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Answers (4)

Finally the problem lied in the IDX2 import of the IDOC in PI. I have importedit in a first moment, then the IDOC fields where changed in R3 source and that was the reason why the fields were wrong populated.

Thanks for your help.

Regards

Gonzalo

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Gonazalo,

So the solution I mentioned was correct for you.

Thanks for updating the forum.

if you have assigned the points request you to close the thread.

Thanks & Regards

Prabhat

Hi,

I have changed the communication channel parameter (Apply Control Record Values from payload) but the the problem remains.

In the SXMB_MONI I have the maximum trace level and I'm watching the message before the mapping (response- > Payload). You can see here an example:

[Comparation SXMB_MONI - and WE19|http://img291.imageshack.us/img291/8357/erroridocbk6.jpg]

As you can see the segment Z1BKPF changes somewhere before it is send from PI and/or it is not well interpreted in the backend. However the standart segment fields, for example fields in E1F1EKPF, arrive fine.

Regards

Gonzalo

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

did u checked the input and output payload in moni,whether both the values are same.

Which data type is used for both the elements in R3 system for that custom segment.

chirag

Hi Chirag,

did u checked the input and output payload in moni,whether both the values are same.

Are you talking about the XML before and after the mapping in the moni? If it is that the answer is yes. And it is as I said. The IDOC is well mapped and in the last trace in the moni the XML payload is fine.

Which data type is used for both the elements in R3 system for that custom segment.

The basic IDOC type is FIDCCP2. I show you the entire XML as it is in the moni:

<?xml version="1.0" encoding="UTF-8"?>
<ZFIDCCP2><IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>002</MANDT>
<DOCNUM>0000000006681051</DOCNUM>
<DOCREL>700</DOCREL>
<STATUS>30</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>FIDCCP02</IDOCTYP>
<CIMTYP>ZFIDCCP2</CIMTYP>
<MESTYP>FIDCC2</MESTYP>
<SNDPOR>SAPHD1</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>HD1</SNDPRN>
<RCVPOR>A000000050</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>MOSXD30</RCVPRN>
<CREDAT>20081125</CREDAT>
<CRETIM>113325</CRETIM>
</EDI_DC40>
<E1FIKPF SEGMENT="1">
<BUKRS>0172</BUKRS>
<GJAHR>2008</GJAHR>
<BLART>ZZ</BLART>
<BLDAT>20080201</BLDAT>
<BUDAT>20080229</BUDAT>
<MONAT>02</MONAT>
<WWERT>20081125</WWERT>
<USNAM>SE04059</USNAM>
<TCODE>FB01</TCODE>
<BKTXT>Cesión personal 02 2008</BKTXT>
<WAERS>EUR</WAERS>
<GLVOR>RFBU</GLVOR>
<AWTYP>BKPF</AWTYP>
<HWAER>EUR</HWAER>
<Z1BKPF SEGMENT="1">
<PROV_LUGAR_EMISION>          FIFI                     I</PROV_LUGAR_EMISION><PROV_PAIS>492BE96CC583113</PROV_PAIS>
<PROV_PROVINCIA>8E1</PROV_PROVINCIA>
<PROV_CODPOS>000000AC1A</PROV_CODPOS>
<CLI_CALLE>405D        492BE971C5831138E1000000AC1A405D</CLI_CALLE><REGISTRO>MADRID</REGISTRO>
<LIBRO></LIBRO>
<HOJA>M-44194 INSCR 1</HOJA>
<INGRESO_GASTO>I</INGRESO_GASTO>
<URL_PERSONAS>                          ICCP</URL_PERSONAS>
<IBAN3>              0</IBAN3>
<CANTIDAD>170</CANTIDAD>
</Z1BKPF><E1FISEG SEGMENT="1">
<BUZEI>001</BUZEI>
<BSCHL>01</BSCHL>
<KOART>D</KOART>
<SHKZG>S</SHKZG>
<GSBER>VDA</GSBER>
<MWSKZ>R1</MWSKZ>
<DMBTR>22133.32</DMBTR>
<WRBTR>22133.32</WRBTR>
<PSWBT>22133.32</PSWBT>
<PSWSL>EUR</PSWSL>
<HWBAS>22133.32</HWBAS>
<MWART></MWART>
<KTOSL></KTOSL>
<VALUT>20081125</VALUT>
<SGTXT>Cesión personal 02 2008</SGTXT>
<VORGN>RFBU</VORGN>
<KOKRS>0172</KOKRS>
<KOSTL></KOSTL>
<SAKNR></SAKNR>
<HKONT></HKONT>
<PRCTR></PRCTR>
<Z1BSEG SEGMENT="1">
<CONCEPTO>Texto a determinar</CONCEPTO>
<CANTIDAD>1</CANTIDAD>
<pre><code>22133.32</code></pre>
<IMPORTE>22133.32</IMPORTE>
<TIPO_POSICION>TER</TIPO_POSICION>
</Z1BSEG>
<E1FINBU SEGMENT="1">
<KUNNR>0000038651</KUNNR>
<SKFBT>     138333.26</SKFBT>ç
</E1FINBU>
</E1FISEG>
<E1FISEG SEGMENT="1">
<BUZEI>002</BUZEI>
<BSCHL>50</BSCHL>
<KOART>S</KOART>
<SHKZG>H</SHKZG>
<GSBER></GSBER>
<MWSKZ>R1</MWSKZ>
<DMBTR>22133.32</DMBTR>
<WRBTR>22133.32</WRBTR>
<PSWBT>22133.32</PSWBT>
<PSWSL>EUR</PSWSL>
<HWBAS>22133.32</HWBAS>
<MWART>A</MWART>
<KTOSL>MWS</KTOSL>
<VALUT>20081125</VALUT>
<SGTXT>Cesión personal 02 2008</SGTXT>
<VORGN>RFBU</VORGN>
<KOKRS>0172</KOKRS>
<KOSTL></KOSTL>
<SAKNR>4770000000</SAKNR>
<HKONT>4770000000</HKONT>
<PRCTR></PRCTR>
<Z1BSEG SEGMENT="1">
<CONCEPTO>Texto a determinar</CONCEPTO>
<CANTIDAD>1</CANTIDAD>
<pre><code>22133.32</code></pre>
<IMPORTE>22133.32</IMPORTE>
<TIPO_POSICION>IVA</TIPO_POSICION>
</Z1BSEG></E1FISEG><E1FISEG SEGMENT="1">
<BUZEI>003</BUZEI>
<BSCHL>50</BSCHL>
<KOART>S</KOART>
<SHKZG>H</SHKZG>
<GSBER>VDA</GSBER>
<MWSKZ>R1</MWSKZ>
<DMBTR>17229.92</DMBTR>
<WRBTR>17229.92</WRBTR>
<PSWBT>17229.92</PSWBT>
<PSWSL>EUR</PSWSL>
<HWBAS>17229.92</HWBAS>
<MWART></MWART>
<KTOSL></KTOSL>
<VALUT>20081125</VALUT>
<SGTXT>Cesión personal 02 2008</SGTXT>
<VORGN>RFBU</VORGN>
<KOKRS>0172</KOKRS>
<KOSTL>CECO</KOSTL>
<SAKNR>7590000000</SAKNR>
<HKONT>7590000000</HKONT>
<PRCTR></PRCTR>
<Z1BSEG SEGMENT="1">
<CONCEPTO>Texto a determinar</CONCEPTO>
<CANTIDAD>1</CANTIDAD>
<pre><code>22133.32</code></pre>
<IMPORTE>22133.32</IMPORTE>
<TIPO_POSICION>GL</TIPO_POSICION>
</Z1BSEG></E1FISEG>
<E1FISEG SEGMENT="1">
<BUZEI>004</BUZEI>
<BSCHL>50</BSCHL>
<KOART>S</KOART>
<SHKZG>H</SHKZG>
<GSBER>VDA</GSBER>
<MWSKZ>R1</MWSKZ>
<DMBTR>4903.4</DMBTR>
<WRBTR>4903.4</WRBTR>
<PSWBT>4903.4</PSWBT>
<PSWSL>EUR</PSWSL>
<HWBAS>4903.4</HWBAS>
<MWART></MWART>
<KTOSL></KTOSL>
<VALUT>20081125</VALUT>
<SGTXT>Cesión personal 02 2008</SGTXT>
<VORGN>RFBU</VORGN>
<KOKRS>0172</KOKRS>
<KOSTL>CECO</KOSTL>
<SAKNR>7590000000</SAKNR>
<HKONT>7590000000</HKONT>
<PRCTR></PRCTR>
<Z1BSEG SEGMENT="1">
<CONCEPTO>Texto a determinar</CONCEPTO>
<CANTIDAD>1</CANTIDAD>
<pre><code>22133.32</code></pre>
<IMPORTE>22133.32</IMPORTE>
<TIPO_POSICION>GL</TIPO_POSICION>
</Z1BSEG></E1FISEG>
</E1FIKPF>
</IDOC>
</ZFIDCCP2>

Regards

Gonzalo

why there is an extra spaces in between ur data in custom segement.

can u take the IDOC no and go to WE19 and remove the extra spaces in all the elements of custom segment and post the IDOC manually and check the IDOC custome data in We02 tcode again.

chirag

OK, doing wat you said I have just find out that the IDOC fields went wrong since they arrive to PI.

My scenario is R3- > PI -> R3 (IDOC 2 IDOC) with the same IDOC type in both systems. And what I have just find out is that the message is not well sent from R3 in first place.

In We19 for example there are 2 fields with values 'FIFI' and 'I'. And in PI arrives both fields concatenated in another different field as <PROV_LUGAR_EMISION> FIFI I</PROV_LUGAR_EMISION>.

Does that helps?

Regards

Gonzalo

can u check the value of input payload and output payload in SXMB_MONI for that custome segment whether both are same or not?

chirag

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi ,

The records gets filled up because of the ALE configuration which is done .

to sort out this problem uncheck the parameter "Apply control records from payload" at the communication channel.

Do give SOme default values to the Segment parameters.

If still the problem still exists ....

Please provide me the payload which is coming in XI @ sxmb_moni and the original data which you recive @ the IDOC

Edited by: Sainath Chutke on Nov 25, 2008 10:59 AM

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Ask a Question

Top Q&A Solution Author

User

Count

IDOC with custom segment: z-fields out of order

Accepted Solutions (1)

Accepted Solutions (1)

Answers (4)

Answers (4)

Iterating through JSONModel with multiple nested a...

Re: Connecting SAP CAP with SAP Cloud ALM

How to use CopyProvider on Table created by TypeSc...

How to execute/fire onPost when user press enter o...

Re: Connecting SAP CAP with SAP Cloud ALM