IDoc segment not reaching XI

Hi,
I have a peculiar problem where the values populated in an IDoc segment are not coming to XI, though the values are visible in the sender SAP system, they are not present in the IDoc XML generated in XI.
Please help if someone faced a similar problem.
Thanks
Pushpinder

Hi,
Check if problems are raised on Cache of Design side of your IB.
Environment - Cache Status Overview
Then "Clear Data Cache".
And try again.
Regards,
Giuseppe

Similar Messages

IDOC is not reaching SAP from XI

Hi all,
The IDOC that I'm sending from XI is not reaching SAP.
I have tried all most all possibilies. In SXMB_MONI I'm able to see the IDOC gets created successfully (with no error).
I have re-checked the partner profile, SMQ1, Config etc.
Please help me to debug.
Thanks,
AJ.

AJ,
Check if you have a chequered flag on both sides of your message ibn SXMB_MONI?
Check the log of your TRFC in transaction SM58
gards,
Bhavesh
Message was edited by: Bhavesh Kantilal

Idocs are not reaching to midleware or external Vendor

Hi Everyone,
We are sending delivery forecast idocs through a customising transaction, the idoc status is 12 but it does not reached to midleware or external vendor. When we create a new idoc through test tool(WE19) by copying the above idoc(which was created by customising transaction), its reaching midleware and vendor. Could you please tell, whats going wrong with the idocs which were created through customising program/transaction.
Thanks in advance.
Thanks and Regards
Raghu

sorry, no ideas at the moment.
You are using the same IDoc (which is in Status 12) and process it with WE19 and it´s working ?
Go to your IDoc Monitor.
OPen both IDocs and go to the STATUS Information.
Open all Status Data and read through longtext and Details, maybe you can locate it there.

Idoc segment not apperaing for PO creation.

Dear All.
Sceanrio:
Once PO is created , NEU ouptut gets triggered.On release of PO, it generates an outbound idoc.
Issue.
In this outbound idoc the segment E1EDKA1 WE is missing.This segment gives the Ship to address in the PO, ie normally the plant address to which the material is shipped.
Analysis:
This PO has 3 line items and these are created by reffering 3 different PR s.So my question here is , whether is this standarad SAP behaviour where Ship to address segment wont get populated into idocs for multiple line item POs.Why i am asking this is that, if suppose the PO has 10 different line items , with 10 different plants.Each plant has different address.Then how system will decide which ship to address will populate in E1EDKA1 WE segment.
Or is there any other behaviours, when the PO has multiple line items.
Please let me know your thoughts on this.
Regards
Shyam

Hello Shyam ,
The reason for this behavior could be that tthe items in the IDOC have a different delivery address maintained in the Ourchase Order. If the delivery address for all items is the same , the segment E1EDPA1 with qualifier WE will be not populated. Instead of generating E1EDPA1 , the system will create one E1EDKA1 segment with qualifier WE. This will prevent on receiving side the creation of the same delivery address for all items.
I hope this information has been helpful.
Best Regards,
Frank Farinella

IDOC Segment not getitng populated during message mapping

Hi,
In my scenario when i am testing, I send IDOC to XI and getting following message
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:I805_Abstr_CustOutlet_MT/Records/AMA_E1KNA1M_STATUS.
When I checked th IDOC xsd, it doesn't show the segment which mapped to above status field.
Can anyone of you please let me know what it is and how it can be resolved.
Regards
Edited by: ria sen on Jun 30, 2008 5:15 AM

Hi Amit,
Following is the payload from SXMB_MONI
<?xml version="1.0" encoding="UTF-8" ?>
- <_-AMA_-DEBMAS06E11>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>110</MANDT>
<DOCNUM>0000000000415387</DOCNUM>
<DOCREL>700</DOCREL>
<STATUS>30</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>DEBMAS06</IDOCTYP>
<CIMTYP>/AMA/DEBMAS06E11</CIMTYP>
<MESTYP>/AMA/DEBMAS</MESTYP>
<STDMES>/AMA/D</STDMES>
<SNDPOR>SAPDAR</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>DARCLNT110</SNDPRN>
<RCVPOR>DAX_001</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>CCABASIS</RCVPRN>
<CREDAT>20080630</CREDAT>
<CRETIM>133535</CRETIM>
<SERIAL>20080627162157</SERIAL>
</EDI_DC40>
- <E1KNA1M SEGMENT="1">
<MSGFN>018</MSGFN>
<KUNNR>0001231235</KUNNR>
<BBBNR>0000000</BBBNR>
<BBSNR>00000</BBSNR>
<BUBKZ>0</BUBKZ>
<KTOKD>S</KTOKD>
<KUKLA>S</KUKLA>
<LAND1>AU</LAND1>
<NAME1>Drew Smith again</NAME1>
<ORT01>Ashfield</ORT01>
<PSTLZ>2193</PSTLZ>
<REGIO>NSW</REGIO>
<SORTL>DREW</SORTL>
<SPRAS>E</SPRAS>
<STRAS>29 Hardy Street</STRAS>
<UMJAH>0000</UMJAH>
<JMZAH>000000</JMZAH>
<JMJAH>0000</JMJAH>
<UMSA1>0</UMSA1>
<HZUOR>00</HZUOR>
<SPRAS_ISO>EN</SPRAS_ISO>
- <_-AMA_-E1KNA1M SEGMENT="1">
<_-AMA_-REF_KUNNR>200</_-AMA_-REF_KUNNR>
</_-AMA_-E1KNA1M>
- <_-SCL_-E1ADRMAS SEGMENT="1">
<QUALF>ADRMAS02</QUALF>
<OBJ_TYPE>KNA1</OBJ_TYPE>
<OBJ_ID>0001231235</OBJ_ID>
<CONTEXT>0001</CONTEXT>
<IV_CHECK_ADDRESS>X</IV_CHECK_ADDRESS>
<IV_TIME_DEPENDENT_COMM_DATA>X</IV_TIME_DEPENDENT_COMM_DATA>
- <_-SCL_-E1BPAD1VL SEGMENT="1">
<FROM_DATE>00010101</FROM_DATE>
<TO_DATE>99991231</TO_DATE>
<NAME>Drew Smith again</NAME>
<CITY>Ashfield</CITY>
<POSTL_COD1>2193</POSTL_COD1>
<STREET>29 Hardy Street</STREET>
<COUNTRY>AU</COUNTRY>
<COUNTRYISO>AU</COUNTRYISO>
<LANGU>E</LANGU>
<LANGU_ISO>EN</LANGU_ISO>
<REGION>NSW</REGION>
<SORT1>DREW</SORT1>
<TIME_ZONE>AUSNSW</TIME_ZONE>
- <_-SCL_-E1BPAD1VL1 SEGMENT="1">
<LANGU_CR>E</LANGU_CR>
<LANGUCRISO>EN</LANGUCRISO>
<ADDR_GROUP>BP</ADDR_GROUP>
<COUNTRY>AU</COUNTRY>
<COUNTRYISO>AU</COUNTRYISO>
<REGION>NSW</REGION>
<TIME_ZONE>AUSNSW</TIME_ZONE>
</_-SCL_-E1BPAD1VL1>
</_-SCL_-E1BPAD1VL>
</_-SCL_-E1ADRMAS>
<_-SCL_-DSD_FIELDS SEGMENT="1" />
<_-SCL_-E1KNA1M SEGMENT="1" />
<E1KNA11 SEGMENT="1" />
- <E1KNVVM SEGMENT="1">
<MSGFN>018</MSGFN>
<VKORG>AU01</VKORG>
<VTWEG>Z2</VTWEG>
<SPART>Z0</SPART>
<KALKS>1</KALKS>
<BZIRK>AU4</BZIRK>
<PLTYP>02</PLTYP>
<AWAHR>100</AWAHR>
<ANTLF>9</ANTLF>
<LPRIO>00</LPRIO>
<PERFK>AU</PERFK>
<PERRL>AU</PERRL>
<WAERS>AUD</WAERS>
<KTGRD>01</KTGRD>
<ZTERM>Z060</ZTERM>
<VWERK>1005</VWERK>
<VKBUR>A4TT</VKBUR>
<BOKRE>X</BOKRE>
<UEBTO>0.0</UEBTO>
<UNTTO>0.0</UNTTO>
<PODTG>0</PODTG>
- <_-SCL_-E1KNVVM SEGMENT="1">
<_-SCL_-CU_KZREG>000000</_-SCL_-CU_KZREG>
<_-SCL_-CU_KZPLP>000000</_-SCL_-CU_KZPLP>
<_-SCL_-CU_FBDWE>0000</_-SCL_-CU_FBDWE>
<_-SCL_-CU_VBDG1>0000</_-SCL_-CU_VBDG1>
<_-SCL_-CU_VBDG2>0000</_-SCL_-CU_VBDG2>
<_-SCL_-CU_VBDG3>0000</_-SCL_-CU_VBDG3>
<_-SCL_-CU_FEDWE>0000</_-SCL_-CU_FEDWE>
<_-SCL_-CU_VEDG1>0000</_-SCL_-CU_VEDG1>
<_-SCL_-CU_VEDG2>0000</_-SCL_-CU_VEDG2>
<_-SCL_-CU_VEDG3>0000</_-SCL_-CU_VEDG3>
<_-SCL_-CU_MTPST>0000000000</_-SCL_-CU_MTPST>
<_-SCL_-CU_MXHUB>0000000000</_-SCL_-CU_MXHUB>
<_-SCL_-CU_SORTR>0</_-SCL_-CU_SORTR>
<_-SCL_-PO_ZFHMG>0.000</_-SCL_-PO_ZFHMG>
<_-SCL_-PO_MXSTH>0</_-SCL_-PO_MXSTH>
<_-SCL_-PO_TWPLUS>000000</_-SCL_-PO_TWPLUS>
<_-SCL_-GC_LONGITUD>0.000000000000</_-SCL_-GC_LONGITUD>
<_-SCL_-GC_LATITUDE>0.000000000000</_-SCL_-GC_LATITUDE>
<_-SCL_-GC_REFID>0000000000</_-SCL_-GC_REFID>
</_-SCL_-E1KNVVM>
- <E1KNVPM SEGMENT="1">
<MSGFN>009</MSGFN>
<PARVW>YM</PARVW>
<KUNN2>0001231235</KUNN2>
<KNREF>00000038</KNREF>
<PARZA>0</PARZA>
</E1KNVPM>
- <E1KNVPM SEGMENT="1">
<MSGFN>009</MSGFN>
<PARVW>RE</PARVW>
<KUNN2>0001231235</KUNN2>
<PARZA>0</PARZA>
</E1KNVPM>
- <E1KNVPM SEGMENT="1">
<MSGFN>009</MSGFN>
<PARVW>RG</PARVW>
<KUNN2>0001231235</KUNN2>
<PARZA>0</PARZA>
</E1KNVPM>
- <E1KNVPM SEGMENT="1">
<MSGFN>009</MSGFN>
<PARVW>WE</PARVW>
<KUNN2>0001231235</KUNN2>
<PARZA>0</PARZA>
</E1KNVPM>
</E1KNVVM>
</E1KNA1M>
</IDOC>
</_-AMA_-DEBMAS06E11>

Idoc Not reaching PI even with 03 status

Hi everybody
There are many posts with similar question, but none of them could help me.
I am trying to post an IDOC from one SAP system 3.1 to SAP 6.0 through PI.
I added FIDCC1 to to my partner profile in BD64.
I am creating a invoice and clearing it through f-30 and using the details from the invoice i am trying to trigger an idoc through a program.
Three idocs are getting triggered
1.when i create invoice(f-22)-automatically
2.when I clear invoice (f-30)-automatically
3.When I execute my program
The first two IDOCS are reaching 6.0, but my third IDOC is not reaching. All have same port details and partner profile details.
*All have 03 status in we02 in 3.1*. I am not able to understand why those two are reaching and why the third is not reaching.
None of them are stuck in any queues.
My actual requirement is only the third IDOC to reach 6.0 and I do not even want the first two IDOCs to reach 6.0.
Pls help!
Thank you
Donny
Edited by: Donnesh on Dec 27, 2011 1:14 AM

Hi Friends,
Thanks for the suggestions.
I have checked with all the above provided suggestions.
But as I have clearly mentioned in the problem that other idocs are reaching well in XI from R3 using the same Port, Partner Profile and RFC.
The error is occuring only with only one idoc in which they have made certain changes (added new segments). I have imported the idoc in Design again and then did the mapping again with the changed idoc.
Before the changes I could receive the Idoc successfully in XI system. I don no what happened after the changes.
If it would have been an authorization problem then I guess the other idocs would not have reached the XI system as well.
I guess the problem is somewhere else..
Thanks in advance.

MATMAS01 IDOC not reaching to SAP XI via report program.

Dear Experts,
WE are facing small challenge.
I searched on SDN on scenarios: IDOC not reaching to SAP XI. But could not find exact solution t oour scenario.
Problem:
MATMAS01 IDOC is not reaching to SAP XI via report program and is in status of 03 on SAP system. And there are not entries under SM58.
Under SAP XI system IDOC entry is not reflecting under IDX5 transaction, I tried to delete meta data of MATMAS01 thru IDX1 and uploaded again but still IDOC is not reaching to SAP XI.
The strange is that MATMS01 IDOC is reaching to XI via WE19 test tool. So PORT and RFC destination settings betweeen R3 and XI is also correct.
What could be the wrong ?
Thanks
Divyesh

When sending Idoc from R/3,
Settings at R/3
create one port at WE21,
Create Partner Profile for Outbound Message type in WE20.
settings at XI
Create one port in IDX1
Import Matadata in IDX2.
Create complete scenario in ESR for Idoc sender, also import IDoc in Imported Objects.
Check these settings & send test idoc using WE19.

Idocs not reaching SAP R3 from XI

Hi All,
I have a File to IDOC scenario, in which i need to process a text file of size 1 Mega Byte. The file from Leagacy reached XI and this has to create 12000 idocs in target R3 system. I can see the idocs(12000) in the IDOC Adapter but these idocs have not reached R3.
In SM58 I see an entry for this with the status "Transaction Executing". This entry is pending since 3 days. This always results in "Time exceeded out", and Iam manually executing it with F6 but still the status shows "Transaction executing".
There are no entries in SMQ1 & SMQ2
I want to push these idocs to R3.
Any suggestions on this will be helpful
Regards,
Santosh

Santosh,
Use IDOC packaging as shown in Michal's blog
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Also, try increasing time out values
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Regards,
Jai Shankar

IDocs are not transfering to XI

Hi,
When we create Shopping cart, in the back PO will create and it woould convert to IDoc and send to XI. But PO's are creating, IDocs are not reaching to XI, please let me know what would be the issue.
Thanks

HI,
Try this URL , i hope it will help u ,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a?quicklink=index&overridelayout=true
Regards,
S.Saravana

Replaced value is not getting relected in IDOC segment field

Hi,
Need your help for the below issue.
I am replacing the PO # with Delivery Doc # . But the replaced value is not getting reflected in the IDOC segment field(e1bp2017_gm_item_create-po_number.).
Function Module which I am using is IDOC_INPUT_MBGMCR as a copy.
Here is my code given below:
SELECT
            SINGLE vbeln
              INTO lx_vbeln
              FROM lips
             WHERE vgbel EQ e1bp2017_gm_item_create-po_number.
Move lx_vbeln TO e1bp2017_gm_item_create-po_number.
MOVE-CORRESPONDING e1bp2017_gm_item_create
               TO goodsmvt_item.
Then this is passed as TABLE in "BAPI_GOODSMVT_CREATE".
Please do the needful.

Hi Dheepa,
Check it in debug whether the filed is empty or having po#, when ur code is executed for the replacement. if it is empty, po# is populated after ur code. in this case you need to write the code in suitable place.
Reddy

Custom idoc segment fields not populated

Way back in 1999 someone create a custom Idoc type with custom Idoc segments in it. Unfortunately, they forgot to release one of the segments.
Recently a change was request to add new fields to this custom segment. In order to get the fields transported the segment had to be released.
All worked fine in Dev and the new Idoc segments were populated as expected. However when the idoc segment was moved to the test system all visually appears to be fine but when the idoc is created (status 50) the new fields are not popultated.
In 40B the start of the inbound process was IDOC_INBOUND_DATA. Does anyone know what the new starting point is in 4.7??
I beleive the error is actually that SData is not reading all the input values and stopping right where the old fields end in teh custom segment.
Thanks,
Anthony

additionally,
SAP will not allow us to release the basic idoc type because it was released in 40B. It also will not allow us to cancel the release since we are now in 620. So, unless anyone has input for this I think the only solution will be to create a successor IDoc type and change our apps to use the new IDoc type with it's enhancements.

Idoc status is in 12, but it does not reached to Target.

Hello Experts,
We are facing a problem with outbound Idoc.
The problem details are as below.
We have generated an Idoc(Without message Control) and dispatched it to external vendor. Idoc status is 12, when we check it in midleware(seebeyond) it does not reached.
There is no error with RFC and Port definition.
Could you please suggest us whats wrong with it or where its gone.
Thanks in advance.
BR//
Raghu

Hi Siva Prakash,
Thanks for your response.
There is no error with RFC, its working perfectly.
BR//
Raghu

IDOCs sent from sender R/3 system do not reach XI system

Hello everyone,
We have a IDOC to JDBC scenario in place.
Sender R/3 system is R1A. XI system is XDA.
IDOCs are successfully sent out of R1A:
On R1A.(R/3)
1. WE05 shows data passed to Port OK
2. SM58 does not show the IDOC to be stuck in TRFC queue
On XDA (XI)
1. Port has been mentioned in IDX1
2. IDOC Adapter monitoring (IDX5) does not show any message from R1A.
3. SXMB_MONI does not show any message from R1A.
The above scenario is for acceptance box.
On Dev boxes (RDD and XDD)the same scenario works OK.
Could we be missing something in the ALE configuration?
If there was something wrong in the Integration Scenario, then atleast the IDOCs should have reached XDA right?
Please assist.
Ashwin Bhat

The option to Transfer IDOCS Immediately was not working. All IDOCs were later sent Batchwise successfully.
The Basis team is investigating why IDOCs are not transferred immediately.
Thanks for all your help Guys.
Regards,
Ashwin

Idocs not reaching new PI server

Hi Experts,
We have cloned SAP-PI 7.0 server and SAP-ISU server. Now idocs from from SAP-ISU is not reaching SAPI-PI at all.
Could you pls suggest how to anlayse and solve this problem?
Regards
Anupam

Hi,
Also Could you please try refreshing CACHE and also check the configuration of Integration server in sxmb_adm.please refer this similar threads below for reference.
Link: [https://forums.sme.sap.com/message.jspa?messageID=7947041]
Link: [https://forums.sdn.sap.com/thread.jspa?messageID=374227#374227]
Also check this [https://forums.sdn.sap.com/thread.jspa?threadID=1236817]
Regards,
Venkata S Pagolu

IDOCS not reaching XI

Dear all,
I found a peculiar issue. A set idocs are being posted from SAP to XI.
Always the last IDOC in that set doesn't reach XI. But the status of that IDOC in we02 is 03.
I've even checked for SM58 in SAP, it also clear.
At XI, everything is fine, all the IDOCs reach but only the last IDOC doesn't reach. We have checked in smq2 and idx5, there are no blockages.
This last idoc has some critical data, cases where in it doesn't reach xi, the whole interface may fail.
If any one has faced a similar issue, kindly provide your inputs to solve the same.
Thanks in advance,
Younus

It is weird problem.
What i can suggest is, reload the IDOC Meta Data in XI using IDX2 & refresh the cache because I don't see other problems since you are able to send IDOCs to XI the problem comes only with last IDOC.
Regards,
Sarvesh

IDoc segment not reaching XI

Similar Messages

Maybe you are looking for