No idocs arrived from sourcesystem

Hi,
Iam extracting sd ata from r/3 to bw side.in monitoring in status tab saying message like this no idocs arrived from sourcesystem.can any one give me ideas.
Thanku

Hi Chinnu,
It may be due to below reasons...
1. Check whether the Log Table is full in the BW side.
2. Check Whether the Connection to Source System is fine.
3. System might be busy , Many jobs running in system.
Go to Sm58 in Bw system , U will TRFC queue with enteries for each LUW . U can come to know why IDOC is not processed by looking at the error there . Also check whether the job is finished successfully in Source System. U can process the LUW in Sm58 manually from Edit menu entry ....
Assign points if it helps......
Regards,
Vijay.

Similar Messages

No Idocs arrived from the source system.

Dear All,
Please read this issue carefully.
Error Message is that
"No Idocs arrived from the source system."
In the Details Tab:
Trasnfer( IDOCS &TRFC):Missing Messages or warinings.
Request IDOC:Application Documnet posted from BW side and it is green..There is a request BW IDOC number sent to R3.
Where as an InfoIdocs 1:Sent not arrived :Data passes to the Port is ok.
Here i can see there is one idoc frm OLTP R3 side ansd no incomming idoc for BW side
I went to r3 side bd87 and found that idoc is posted well with status 53.
This is happing in Bw for each iinfopcakage is running?

Hi,
go through this link...
[https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=noidocsarrivedfromsource+system&adv=false&sortby=cm_rnd_rankvalue]
System.-> Check RFC connection and clear/process stuck IDOCs.
Idocs Missing or No Idocs arrived from source
For this check the TRFC que(SM58).If any Idocs r strucked up there execute them manually.checkin sm58 transactions, you can check the status of your Idocs using BD87 in R/3. Idocs may not be processed because of load on system. You can process them manually from context menu.
And go to BD87 to process the idoc's ..
check which idoc has to process...select the idoc and click process ..Then It will push the data into the data targtes,
Hope it will help you;
regards,
NR

R/3 connection to BIW - No Idocs arrived from the source system

Question,
Hi Team,
I have issues during loading attribute data from R/3 source system to BI,
I go to the path
Data Warehousing Workbench - Modeling window. In the DataSources view, my application component Group ##. On my DataSource i Create Info Package and save it,
Later I select the following options
Full Update = select
On the Processing tab page, select only PSA.
On the Schedule tab page, choose Start Data Load Immediately and start the data load.
Till here everything is in active version and saved, and connection to the source system is active and working fine.
However when I do loading I received following messages, what I observed in Monitor window,
Data was requested OK
Request still running
Diagnosis
No errors found. The current process has probably not finished yet.
System Response
The ALE inbox of BI is identical to the ALE outbox of the source system
or
the maximum wait time for this request has not yet been exceeded
or
the background job has not yet finished in the source system.
Current status
No Idocs arrived from the source system.
When I go to detail tab, under transfer section, I receive the following message
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
But when I actually go to PSA maintain section and select data and no of records, I can see the that data is loaded into PSA section,
But when I chose to run the transformation I donu2019t get data here,
Kindly help me to resolve this issue,
Regards,
BluSKy

Hi,
the BIW i am using , its compact BIW, which is in EXI, and i execute transaction /nrsa1 to go biw development workbench,
i am not sure about transactions settings about r/3 side,
could you plz throw some light on this issue,
regards
blusky

No IDOCS arrived from Source system to BI for generic extraction

Hi All,
While loading data from r\3 generic data source to BI, I am facing the below problem.
1. Using Full Load:-
The request from r\3 to psa turns red after a while. The request monitor says:
Error when updating Idocs in Source System
Diagnosis
Errors have been reported in Source System during IDoc update:
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Source System . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
Details Tab shows : request green
Under that Extraction tab shows red
missing messages.
Transfer (IDocs and TRFC): Errors occurred .
Request IDoc : Application document not posted
I ran Transaction BD87,BD73 and execute with proper selections.
Upon checking the idoc in source system Their status is 51 , which says
Diagnosis
The control parameters for communication with the BW server are not
complete. A BW PlugIn upgrade could be the cause of the problem.
System response
Procedure
Depending on the Release of the BW server, proceed as follows:
BW Server Release 1.2B: Source system: Update InfoSource metadata
BW Server Release >= 2.0A: Source system: Activate.
Manually i tried to push the idocs in the BW and source system using TRF but i dint found any records???
Soruce system connection is fine. Profile parameters are set properly and its active .. But still am getting the same problem.
Many thanks, I'll applicate your help.!
Rakesh

Hi
I am also facing the same problem. This happened after restoration of the original system with a copy of the production.
I am not able to get the IDOC posted in the source R3 system.
I did a debug and it failed when verifying the table, RSBASIDOC.
There appeared to be some missing records which need to be inserted.
I can't find a way to insert the missing record and since then, I am not able to proceed.
Have you resolved the issue?
can you share how it can be overcome?
Thanks a lot

Why IDocs are not arrived from Source System

Hi all,
Now a days we are facing regular problem to load master data?
We are getting Error Message - "No Idocs arrived from the Source system".
I need to know, Why this error will be occurred?
Is there any reason for this Docs are not arrived from the Source System?
Please help me to analyze this error, why its happened regularly? what could be possible reasons for this error?
Its very urgent, please help me as early as possible.
Thanks in Advance. I will asign the points for relevent answers.
Regards,
Sudharsan Reddy.

Hi ,
SOME OF THE CHECKS:
1.You can check the RFC destination using the transaction SM59 in the system. Then do Test connection and this should not cross more than 1000ms. The connection should establish within 1000ms.
If it crosses more than 1000ms the tRFC entries will not be cleared fast.There will not be any job to push Transaction recorded entries it will go through SMD(Shared Master Data) Tool.
So if it crossed more than 1000ms, then you can ask your Basis team to check the network connectivity b/w R/3 and BW system.
If there is no serialization for these IDocs then you can use button F6 to process these entries in tRFC manually.
2.Go to SM58 and check the LUW .If any error ..then selecting the failed Idoc, click edit in the menu and execute LUW.
3.If there are many Idocs with status red then check the system performance also. If performance os the system is bad then, we can put the mail to basis guys they will check and restart the BW system. (or) it may be due to problem in the coding,since data transfer is taking long time.
4. Some times it may be due to much parallel process at the info package level and make the Max parallel process into one process in RSCUSTV6, save and run the infopackage. This may be due to space problem.
( Or )sbiw>general settings>maintain control parameters for data transfer. Both in BW and R/3 we configure in the same way.
There we need to give
1.source Sys name
2.Maximum KB in one data package.
3.Maximum lines in one data package.
4. Frequency (specifies after how many no. of data records, status record should be sent)
5. Max processes ---Reduce the number process, save and try.
6.Target Sys name.
Regards,
Dhanya.

Idocs missing from source system

Hello,
I am trying to extract data from R3 to BW. I am getting an error message in BI, No idocs arrived from the source system.
In SM58 system showing the message 'No service for system SAPECC, CLIENT 800 IN INTEGRATION DIRECTORY'. Please help on this issue
Regards,
Ramesh

Hi Ramesh,
Check whether the connection is proper between BW & R/3.
Goto your Source system> Right clcik> Check.
You can also check the following :
No Idocs arrived from the source system.
Idocs missing: No selection information arrived from the source system
Error when updating Idocs in Source System
Hope it helps!
Regards,
Pavan

Sender / Receiver on DEBMAS customer IDOCs mapped from XI

Hello XI experts,
I'm hoping you can help me resolve a question.
In our system, customers are maintained in an AFS ERP system. They are then distributed to MDM, via XI, using DEBMDM messages.
We have a second (Retail) ERP system that also needs the customer data. An XI colleague has created a mapping, so that the DEBMDM IDOC from AFS is mapped to DEBMAS and ADRMAS IDOCs, which are sent to AFS.
Functionally this works fine: the customer data from AFS goes to both MDM and retail as expected.
The question is on the IDOCs arriving in Retail. They have the same logical system for the Sender and Receiver, which is the Retail logical system. So it looks like the IDOCs have been created in Retail and then processed, rather than being created in XI. However in XI, in transaction IDX5, we can see IDOC numbers. I'm a developer with no XI experience, so I may be misunderstanding how XI works.
- Does XI actually create an IDOC locally and then send it out?
- Or would XI be calling some kind of RFC in my Retail system to build the IDOC there?
- If the IDOC is built locally, can anyone suggest why I am getting the sending partner to be the same as the receiver?
Even if the sending and receiving systems are set in the XI mapping, the values still get overwritten with the Retail logical system.
Many thanks, Roger

Roger,
In the Receiver IDoc Adapter , 3 options are available.
Apply Cntrol Record Values From payload.
When you select this option, the values of these fields are filledfrom the idoc payload,
+MESCOD
· MESCFT
· TEST
· EXPRSS
· STD
· STDVRS
· STDMES
· SNDSAD
· SNDLAD
· RCVSAD
· RCVLAD
· REFINT
· REFGRP
· REFMES
· STATUS
· DIRECT
· OUTMOD
· CREDAT
· CRETIM+
Take Sender From Payload
Selecting this fills the values for Sender System with values of SNDPRN and SNDPRT.
Take receiver from payload
Receiver Partner Names values are filled from the payload with values of RCVPRN and RCVPRT.
These are the only values from which you can pass the value from payload, rest of the fields are filled by default.
More,
http://help.sap.com/saphelp_nw2004s/helpdata/en/13/95244269625633e10000000a155106/content.htm
Regards
Bhavesh

Error while ORDERS05 IDoc transfer from R3 - PI - SNC

Hi Friends,
I am facing error in PI SXMB_MONI for ORDERS05 IDoc transfer from R3 - PI - SNC.
I have done all the configuration setup in Integration Directory for the Scenario, I am able to successfully send the IDOC for PO from R3 to PI but faced the following Error in PI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PARTY_SERVICE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
*<SAP:Stack>Party and service not defined</SAP:Stack>*
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also I am unable to Configure Sender/Receiver ID in PI > SXMB_ADMIN > Configuration, as while defining Sender/Receiver unable to add the Interface for Sender(ORDERS.ORDERS05)/Reciever(ReplenishmentOrderNotificatio_Out) although I am able to see the same in Integration Repository.
Also In Main message(Part of the message) as shown below, I am able to see Vendor in PARTY Element of xml message for which I have created the PO
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>0050568F-24A0-1DDD-B9F5-3F6DD541FF93</SAP:MessageId>
<SAP:TimeSent>2009-01-21T10:55:20Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>SAPECC6</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ORDERS.ORDERS05</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="SAPECC6" scheme="ALE#LI#LF">0000000006</SAP:Party>
<SAP:Service />
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ORDERS.ORDERS05</SAP:Interface>
<SAP:Mapping notRequired="Y" />
</SAP:Receiver>
Please Suggest the steps needs to be done for resolving the Issue.
Thanks all...
Regards,
Nitin
Edited by: Nitin Patil on Jan 21, 2009 12:18 PM

Hi Nitin,
I completed the configuraiton but the PO came in PI successfully but stuck in PI with error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Error during parsing of SOAP header</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
can you please help what is the problem , I am not able to find out.
Thanks,
Menaga

Mass processing for inbound orders idoc's from file

Hi Experts,
I have an requirement wherein we need to process all the ORDERS idocs sent from a thrid party system to a particular folder in the SAP system. Now we use a custom programme which in turn calls fn module IDOC_INBOUND_FROM_FILE to process each file. Here if the fn. module IDOC_INBOUND_FROM_FILE hits an erroneous file (control record error) it issues abend message which causes to entire programme to exit leaving rest of the files in the folder unprocessed.
Let me know if there is any other function module or way to tackle this issue so as to process all the files.
Thanks & Regards,
Jimmy.

Add the exception ERROR_MESSAGE = 99 (or some other unique number) to the standard exceptions in the function module call in your custom program. This will allow you to trap the error and continue processing.

Stop Inbound IDOC's from being created

I want to stop inbound IDOC's for a particular partner (type LS) from being created in our R/3 system. Is there a way to do this? I am aware these can be stopped in the middleware, but this is not possible in our case. I am also aware that I can stop these IDOC's from being processed via the partner profile, however, there will be a huge number of useless IDOC's that will be created in our system and I want to avoid that.
Hence, I do not want the inbound IDOC's to be created in the first place even though they are transmitted to SAP. Is this possible?
Any inputs will be highly appreciated.
Thanks,
Raghu.

Hi Satwik,
Choose Idoc in WE02.
Get port name, Then in WE21 get RFC name.
Go to transaction SMQS - Here we can block this RFC instead of blocking the queue.
Thanks,
Anil

How to generate multiple idoc's from single appl document

All,
Iam looking for a way to generate multiple idoc's from single appl document (sales order). Based on the plant details on line items in the sales order i have to generate multiple idocs, i.e., send one idoc to each plant entered in sales order line items. any help will be appreciated.
Thanks

Hi,
You can create a Z-program and call Function Module MASTER_IDOC_DISTRIBUTE.
You can make a call to this FM to send the Idoc as many times as u have plants in your Sales Order.
You can call FM IDOC_OUTPUT_ORDRSP to fill the IDoc structure.
Then u can keep the materials of only that plant for which u want to pass on the information.
Thanks,
Utsah Garg.

IDOC settings from sap r/3 to sap pi7.3

Hi Guru,
actual problem when i am triggering the idoc from ERP,it is trigeering to the abap stack in sap pi.but i am using idoc_aae adapter at sender side,the message is flowing from sap ERP to file but the message is seen in sxmb_moni,but actually it is not seen in moni .
Please if any one have the idoc setting from sap erp to sap pi7.3. and iam using ICO configuration.
Please help me
Regards
Reddy

Hi,
Please go through the below link :
http://wiki.sdn.sap.com/wiki/display/XI/ALE-Idocconfiguration-+%28R3XIFile%29
Also in your software component version please check whether import of IDocs and RFCs are allowed
from your respective ECC system, and check the ECC system parameters are correctlt maintained or not.
Try out once.

Idoc lost from SAP R/3 to XI

Hi experts,
I have the following problem:
sometimes an idoc fired from SAP (not through WE19) does not reach XI (I cannot see it in SXI_MONITOR). I've checked the following facts:
1. SAP R/3 status of the idoc is 03 (direction outbound).
2. SM58 produces no result.
3. IDX5 produces no result for that idoc.
4. 99,9% idocs of the same type fired in the same day work fine.
Resending manually the same Idoc using WE19 gives no problem and the idoc reaches XI.
any idea?
Thanks a lot,
Daniele

You must see this in WE05 or BD87. Just release the idoc and have a look at we05 or bd87 and limit down the time where to search. in sm58 you can only see the idoc ith the system can not log on to the remote system. Did you check sm58 in the target system? did you check bd87 in the target system?

Unable to import IDOC metadata from 4.6C based R/3 system

As part of a project we are trying to import IDOC interface definition into XI3.0 from our 4.6C based R/3 System. I have gone through the pre-requisites mentioned at
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/frameset.htm
One of the OSS notes 672745 in the above pre-requisites talks about applying basis component patch SAPKB46C46. Our current R/3 System is on the basis patch SAPKB46C39. Is there a way to import just the required function modules without applying the whole patch so that we can
continue with the projet ?
cheers.
Ramesh Babu

There is no SM59 RFC destination involved.
Go to SM59 of the XI box and check, the R/3 system for which XI is having RFC destinations.
And before importing, hope you have given R/3 system IP address, client , user id and Password correctly in the Software componenet version.
Is there a workaround for this?. I remember reading in this forum, that there are other ways of importing IDOC message and interface objects as XSD files directly instead of using import wizard.
>> For this you need to download the Idoc Schema from the R/3 system and then import this schema in the External Definition as a xsd type.
But you need to connect to R/3 system and import the Idoc, Because in the directory, you are going to use Idoc itself as an Message Interface. So the xsd used for changing the occurence of the Idoc type, so that you can post mulitiple idocs.
Hope this helps,
Regards,
Moorthy

Get IDoc-number from flat IDoc using dynamic configuration

Dear experts
In an IDoc2File scenario I have added the IDoc-number to dynamic configuration using the folling code in an UDF:
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey FileName = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File","DOCNUM");
conf.put(FileName, a);
The information is stored in the SOAP message
<SAP:DynamicConfiguration SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="DOCNUM">0000000000012345</SAP:Record>
</SAP:DynamicConfiguration>
Can anybody tell me how I can access this information in the "variable substitution" section of the CC? Perhaps something like "message:docnum"?
Additional information:
Taking the IDoc-number from the payload using e.g. "payload:ORDERS05,1,IDOC,1,EDI_DC40,1,DOCNUM,1" does not work, since the XML-IDoc has been converted to an flat-IDoc.
Thanks in advance for any good ideas
Markus

Dear Rodrigo and Sarvesh
Thanks for your help so far! I applied your hints and now it is working fine.
But now I have the following additional questions
1.) My message mapping only maps the input IDoc to an output IDoc of the same type and structure. The MM is only required to process the UDF. Is there another, better solution to achieve my requirement that the IDoc-number shall be part of the filename?
2.) In the CC you have the possibility to use temporary files (section "Processing", Option "Put File" = "Use Temporary File". I think this will not work with the given solution, will it?
To possibly help somebody else or clarify the mechanism once again, I wrote down how my solution now looks like.
My UDF in the message-mapping looks like this
- Input = DOCNUM of IDoc, e.g. ORDERS05/IDOC/EDIDC/DOCNUM
- Outpt = DOCNUM of IDoc, e.g. ORDERS05/IDOC/EDIDC/DOCNUM
- UDF:
public String putDynamicConfiguration(String docnum, Container container) throws StreamTransformationException{
try
 DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
 DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
 String filename = "Prefix_" + docnum + ".txt";
 conf.put(key, filename);
 return docnum;
catch (Exception e)
 return docnum;
In the CC the settings are now as follows
File Name Scheme = . -> only a dot or something else, because this field is obligatory, even if it is not used in this case.
Variable substitution (...)
 Enable -> unchecked
Adapter-Specific Message Attributes
 Use Adapter-Specific Message Attributes -> checked
 Fail If Adapter-Specific Message Attributes Missing -> checked
 File Name -> checked
 Directory, File Type, Temporary Name Scheme for Target File Name -> unchecked
When I send an IDoc to PI and view the Adapte-Engine Version of the message (the SOAP-document, not the payload) I can find the Filename:
<SAP:DynamicConfiguration SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">Prefix_0000000000012345.txt</SAP:Record>
</SAP:DynamicConfiguration>

No idocs arrived from sourcesystem

Similar Messages

Maybe you are looking for