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

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

Inbound idoc error in the source system

HI,experts
I manually configurate the idoc type ,message type ,etc between the BW system and r/3 source system when the automatic program encouters errors. And the communication between BW and source sysyem seems ok since the source system is activated successfully in BW side.
But when I check the inbound the idoc in source system after i triggerred a full load for the datasource 0FI_GL_4,an error occurs in the inbound process in R/3. There is no control information in the idoc which message type is RSRQST.
how can i figure this issue out ?could anyone help me ?

HI,ALL
Thanks for your replies and documents.
Now I find the problems lies in the error connection between R/3 and BW. IF the autoconfiguration is completelly correct , the table RSBASIDOC in both system should be added one record.But now when the source system is activated successfully ,the table in R/3 side has no entry while the BW side has one entry .juding from this ,there is no BW system connected to the R/3 ,which is proved when I fill the setup table for LO datasource an error message shows that there's no BW system is connected to the OLTP system.
How can i figure this issue out ?If I want to do an automatic configuration ,what shall I do ?

Restoring the source system connection in BW

Hi all,
Ive been trying to upload data for 2 of my infocubes, and the extractions are bouncing. The message in R/3 is told me to check the connection. The RFC are fine. But when I tried to restore the source system connection (RSA1 in BW), it sent me the following error messages:
1.- Basic type ZS 118 does not exist.
2.- The following error in the source system:
3.- Incorrect IDoc type ZSAB023 in the ALE definition of the source system.
The description in each error is:
Error #1:
Diagnosis
    IDoc type ZS 118 could not be found.
System response
Procedure
   Please enter an IDoc type that exists.
Error #3:
Diagnosis
    Incorrect IDoc type ZSAB023 in the ALE definition of the source system.
System response
    Error when sending data to BW.
Procedure
    Enter IDoc type ZS 118 .
They told me this IDocs are created automatically by the connection. Is that true?
How can I fix this, so that I can restore my connection and do the data extraction?
Thanks a lot
Regards,
Vic

Hi Victor Tostado
1.- Basic type ZS 118 does not exist.
Type Transaction WE30. Check iDoc types Obj. Name : RSSEND -> press F7
a.) Enter 'RSSEND' in the Obj. Name field. You will see an entry similar to the one below:
          RSSEND                          Data transfer from the source system (template)
                [-] E1RSSH               Data transfer IDoc: Header information
                         [+] E1RSHIE    Data transfer Idoc: Hierarchy header information
                                E1RSTXT   Data transfer IDoc: Texts
     b.) Enter RSREQUST in the Obj. Name field. You will see an entry similar to the one below:
            RSREQUST                    Data request to the source system
                 [-] E1RSRH               Data request IDoc: Header segment
                         [+] E1RSRHI     Data request IDoc: Hierarchy
                         [+] E1RSRTX    Data request IDoc: Texts
                         [+] E1RSRMD   Data request IDoc: Master data
                         [+] E1RSRIS      Data request IDoc: InfoSource
     c.) Enter RSINFO in the Obj. Name field. You will see an entry similar to the one below:
            RSINFO                         Info IDoc
                [-] E1RSHIN             InfoIDoc: Status segment
                        E1RSPIN            InfoIDoc: Data packet segment
                        E1RSEIN            InfoIDoc: Error segment
d.) If any of the above do not exist, contact your BASIS Team.
2.- The following error in the source system:
Type Transaction SM59. Maintain RFC destinations
a.)     Open the RFC Destinations. b.) Find your Source System and double click on it. c.) Technical setting should contain information regarding your source system d.) Logon Information should contain source system client and name & password for you remote logon.
3.- Incorrect IDoc type ZSAB023 in the ALE definition of the source system
Type Transaction WE21. iDoc Processing Ports.
receivers port is not available go to WE21 -> create port
a.) Select 'Ports' and then 'Transactional RFC'. b.) Click on the Port # for you source system. c.) Verify description & SAP R/3 versiond. RFC Destination should be one created in SM59. If non-existent then create one.
I) Type Transaction SE16. Data browser (for R/3 -> BW Connections)
Enter RSBASIDOC Print out copy of all entries in table.
II) Type Transaction SM30. Msg Types & Assignment to iDocs
Enter 'EDIMSG' in the Table/View field. Click on the 'Enter Conditions' option for Restrict Data Range. Click 'Maintain'. Select Message Type. Then enter 'RSSEND' in "From' field. Verify that the Basic Type matches what is in your RSBASIDOC table for each of your connections. If any are missing any entries you must create them as follows: Create another session and type Transaction WE30. Enter IDoc Type (ZSBAXXX) in Obj. Name field (Suggestion: Start new type with 'ZS' + Transfer Structure Prefix + (3)#'s) Select Create. Select "Create from Copy'. Enter 'RSSEND" in 'Copy From' field Enter Description (i.e. IDoc Type for BW Development) Execute (Green Check). Repeat for other missing entries.
Regards
Sangram Sutar

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.

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

Incorrect IDoc type ZSWA003 in the ALE defintion of the source system.

Hi !
When I triggering the load from BW it is giving me an error Incorrect IDoc type ZSWA003 in the ALE defintion of the source system.
When I am checking the connection in source system with R3 system , it is giving me this error and asked me to Enter IDoc type ZSWA011 .
Please tell me how to do this.

Hi,
I assume that the source system has been copied fom production onto quality-system (or somothin likely).
To solve that, plase refer to the oss-note 886102.
https://websmp130.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=886102
https://service.sap.com/sap/support/notes/886102
Hope that helps.
cheers
Sven
Edited by: Sven Muntermann on Mar 26, 2009 6:21 PM

Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR

Hi Experts,
Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR 373 error is coming .
Some one suggested note no 886102 but i went inside i did not find correction or code for implementing please any body suggeste for rectifying this error.
Please tell correct aproach for solving the issue.

Hi,
there is some problem with your RFC connection
just go to WE20 T code and expand partner type LS
here search your r/3 system and click on that here you can find the details of idoc
if you are not able to correct yourself you can contact basis team for that.
just go to RSA1--> using the conxt menu doa check of Source system you will get the error message
just send the screen shot of the same to Basis team they will take care of the same.
Br
santosh

RFC Error:The BW IDoc type ZSBA011 is not the same as the source system

Hi Experts,
RSA1Source System (Context Menu) Check
I am getting the below error
The BW IDoc type ZSBA011 is not the same as the source system IDoc type ZSBD012 
What might happened wrong.When i checked with my Basis Consultant who is new to job,Replied every this is ok with regeards to RFC.
Where should i check to correct the error
Thanks

Hi,
Did you do a system copy for BW ?
Try a restore (rightclick on your source system) in most cases this will solve the problem.
If not check the notes below:
184322 Procedure after DB copy of BW source systems
886102 System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
325470 Activities after client copy in BW source systems
325525 Copying and renaming systems in a BW environment
184754 Procedure after BW database copy
184447 Building a BW-system landscape
184971 Notes on BW source system connections
140276 Error in source system assignment
524554 Storing destinations in the BW environment
538052 Maintenance of Myself destination in BW
Regards, Patrick Rieken
Message was edited by:
 Patrick Rieken - BI-Formance B.V.

An FTP Error occured - cannot make connection to host. No response from the server

"An FTP Error occured - cannot make connection to host. No response from the server".
As of today this is all i get when trying to connect to every single ftp account i have. It's not the server cause it's every one and there is several different. Tried passive and non-passive same result. I've connected fine with other FTP clients. So this must be another dreamweaver bug. Anyone know what to do?

Very hard to diagnose these problems, particularly as you can connect using a 3rd party program.
See if the 'timeout' issue could be at play here:
http://forums.adobe.com/message/708941#708941

Getting valid idoc number from the sales document

hi,
Iam sending the code for getting the idoc number from sales document.
but iam not getting the result.
please see the code and correct the code so that i will get the idoc number from the sales document.
tables edid4.
data l_docnum like edid4-docnum.
parameters:p_vbeln like vbak-vbeln.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
exporting
 input = p_vbeln
IMPORTING
 OUTPUT = p_vbeln
select single docnum from edid4 into l_docnum where sdata like '&p_vbeln&'.
if sy-subrc = 0.
write edid4-docnum.
else.
write ' the record is not found'.
endif.
it is very urgent..............
thanks in advance......

See the below code :
report zxyz.
tables edid4.
data l_docnum like edid4-docnum.
parameters:p_vbeln like vbak-vbeln.
data sdata like edid4-sdata.
start-of-selection.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
exporting
input = p_vbeln
IMPORTING
OUTPUT = p_vbeln
concatenate '%' p_vbeln '%' into sdata.
select single docnum from edid4 into l_docnum
 where sdata like sdata.
if sy-subrc = 0.
write edid4-docnum.
else.
write ' the record is not found'.
endif.
Thanks
Seshu

IPod updates 2 touch with the new software, and from the update they are not connected with Time phase. They appear calling but never they enter the calls. I make calls with other users and if one connects but in these two not from the update

iPod updates 2 touch with the new software, and from the update they are not connected with Time phase. They appear calling but never they enter the calls. I make calls with other users and if one connects but in these two not from the update

I use Firefox 95% of the time, and there's no problem with flash content (and I'm still at .55 - downloaded .64 last week but I haven't got round to making the change yet). At the rate they've been changing it recently it may well be out of date already .
I've been trying it in Safari, too with no problems apart from You Tube, but that's because I'm blocking Google cookies.
One thought does occur - if your Flash preferences are set to block all Local Storage, it may be that the problem site is trying to use Flash cookies (LSOs). I had this problem recently with the BBC iPlayer streaming content. Little Snitch notified an attempt to connect to a new URL - emp.bbci.co.uk.
If I disallowed it, no streaming; when I allowed the connection, it still wouldn't stream, so I did a bit of digging and came to the conclusion that it was trying to set a Flash cookie. When I unblocked, lo and behold - streaming resumed as normal.
I now have LSOs blocked in a more subtle way that lets the site think it's being set (but it ain't) and the streaming still works.
As for permissions repair - always repair from local; the permissions on the original disc will have been superceded by updates and new installations of Apple software.
DU needs to be reading the packages on the HD, not the (now out of date) install disc.
The recurring repair messages are normal and don't mean anything's wrong. As long as the final message is 'repair complete' there's no need to dwell on it.
http://support.apple.com/kb/TS1448 (for Leopard and Snow Leopard - Lion no doubt has it's own set).

How to verify the Source systems connectivity with BWQ System.

Hi All,
I have diff source systems. And my requirement is to check the source systems connectivity with BWQ (BW Quality sys). please any body tell me the steps how to check the source system connectivity ?
Thanks & Regards,
Manju

Hi Manjula,
If you encounter problems when establishing a connection to your target server, check the following:
A message box appears while performing one of the following actions:
      Setting connection by choosing Apply to local session.
      Testing connection settings by choosing Test settings.
      Creating SAP TSQL objects
If errors occurred, they are displayed in the respective message box.
   Check developer trace files in ST11.
Test connection:
     For RFC related errors, check the RFC connection via SM59
     For database multi-connect errors, check if you can connect to the target SQL Server with the SQL Server Query Analyzer. Also check if the DBCON entries are correct.
Regards,
RK

Database Connection Error: Cannot obtain error message from the server

I have a SQL statement that wants to add a temp table to the database.   The SQL statement works fine but when I try to add it via 'Add Command' feature in Crystal XI R2, I get the following error message:
Database Connection Error: Cannot obtain error message from the server
Any ideas?
Thanks in advance,
Zack H.

Hi Raghavendra,
I am using this in the 'Add Command' feature but I get the error message displayed in the subject line:
CREATE TABLE #TibetanYaks(
YakID char(4),
YakName char(20) )
INSERT INTO #TibetanYaks (YakID, YakName)
SELECT LastName, FirstName
FROM      Employee
WHERE      EmployeeID between '2000' and '3000'
I haven't tried to add this as a stored procedure but I imagine it will work as I have no problems yet with stored procedures. I simply want to be able to use temporary tables for the sole purpose of that session and not creating anything static in the database.
By the way, even though I get the error message, when I look on the backend database, I see that the temporary table was successfully created...its just not brought across correctly in Crystal.
Any ideas?
Zack H.

How we can import an IDOC structure from one SAP system to another w/o ALE

Hi Gurus,
How we can import an IDOC structure from one SAP system to another? we're not able to use ALE tech, these two sap systems are isolated.
Any response will be awarded!
Thanks a lot.
Samson

hi,
1.One is by change pointer concept i.e by executing the RBDMIDOC.We can generate the idoc and automatically to the inbound System.
2.By executable program also like bd10 and bd11.
Regards,
SHIVA(reward if helpful).

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

Similar Messages

Maybe you are looking for