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

Similar Messages

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

R3 to BW Extraction fails: Non-updated Idocs found in Source System

We load data from R3 to BW and this process has been successful for the past few days except last night. The error msg is listed below in between two dashed lines:
Non-updated Idocs found in Source System
Diagnosis
IDocs were found in the ALE inbox for Source System that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually.
I checked the system connection by right click the source system in the Source System page on BW and selecting "Check" and "Customizing for Extractors" from the context menu and find everything works fine.
Any idea about the IDOC thing?
Thanks

hi Subray/Bhanu,
With WE05, find some records with yellow status. How to find some missing data here?
With BD87, under BW system folder, there are two folders:
1. IDocs in outbound processing
2. IDoc in inbound processing
Under 1st folder, there is one yellow status folder called "IDoc ready for dispatch (ALE service)", continue to expand another folder called CREMAS under it, there is a blue information line which is "Receiver found , Data filtered , No conversion , No version change".
Under 2nd folder, there is one yellow status folder called "IDoc ready to be transferred to application", continue to expand other two folder under it called "BBPIV" and "RSRQST", find there is a red flash status line which is "No resources, immed. processing not possible: Too few free dialog work" under these two folders.
I need to go ahead to select these two red flash status lines and then press the Process button at the top bar?
Thanks
Message was edited by: Kevin Smith

Error in loading data into PSA from source system.

Hi Experts !!!
Good morning .
I am trying to load data from SRM source system into BI system.When I execute infopackage,the data is not loaded into PSA and status of the process immediately becomes yellow.After sometime it gets timed out and converts to RED.When I checked the error documentation I found that the iDOCS response was not received from the source system.Detailed error is as below.
System Response
There are idocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further Analysis
Check the TRFC log
you can access this log using the wizard OR menu path "Environment > Transact. RFC> In the source system
However,I was not able to navigate to this path.I think if I can navigate to this path,I can manually push IDOCS from source system to BI system.
Regards,
Mandar.

Hi,
Check the DataSource in RSA3, if it is working fine and able to see the data in RSA3, there is no problem in DS level, then check the Mappings and any routines in BW for that DS, if this is also fine then check the below options.
See Dumps in ST22, SM21 also.
Check RFC Connection between ECC and BW systems, i.e. RSA1-->Source System->Right Click on Source system and Check.
You must have the following profiles to BWREMOTE or ALEREMOTE users.So add it. Bcoz either of these two users will use in background to get extract the data from ECC, so add these profiels in BW.
S_BI-WHM_RFC, S_BI-WHM_SPC, S_BI-WX_RFC
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
See in SDN
Re: Loading error in the production system
IDOC getting struck at TRFC (SM58)
1.Reorg of table (ARFCSSTATE )
2.Incraesing the resources in the system (no of processes and memory ) , as this issue happens owing to this.
Source system tries to send TRFC to target and if there are no WP's available it will come to Transaction Recorded state, and form here it will not try to send this TRFC.So you have to execute this manually.
Also we can increase the timeout parameter so that it can try few more times to send before actually it comes to recorded state.
Regards,
Suman

Question to Transferring Global Settings from Source Systems

1) When we do this steps, we found the following information as follows, so the question is that which fields that we should maintain?
BW User ALE
Debugging User
BEx order number
Releasest. hier
Monitor initial
Last IDoc no.
Last IS-Nr.
XPRA executed
Lock Mangr Logs
MD: Sing. Rec. Inst
RFC BI Accelerator
2) If we maintain some of fields should we do something before, and how? e.g. we know BW user ALE = aleremote, so should we maintain aleremote user using SU01 both in R/3 and BW before we do Transferring Global Settings from Source Systems
Thanks for the answer.

Is anyone know how to setting Transferring Global Settings from Source Systems, your answer will be high appreciate.

RSAR2318 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on BI + ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Error RSAR238 : IDoc type for source system T90CLNT090 is not available
I have already checked trx & dtps, but could not find resolution.
Kindly help me with this error.
Thanks and regards,
MS

M Sharma wrote:
But how exactly can I create when T90CLNT is not active? Help please.
Yes, you would need to check with BASIS team how they have created an alternate source system (for debugging) & prepare a RFC b/n these systems. Can you just check the settings in the source system and BI source system...and check the source system for the same BI system. Right click > Check and then do a restore or take the help of basis to fix it. What I think is a possible solution is : RSA1 > Source system > Search System > Right Click > Activate

RSAR238 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Kindly help me with this error.
Thanks and regards,
Dhanapal

Hi,
Check the same in SDN..
Object ZDUMMY could not be activatedMessage no. R7I028
Re: DSO Activation problem
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/test-cases-for-module-human-capital-management-1425016
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/idoc-type-for-source-system-t90clnt090-is-not-available-message-no-rsar238-1431565
Thanks
Reddy

Error in Process Chain while extracting data from source system

Hi All,
Dail we are facing problem while retrieving the data from source system for the data source 0TB_AMOUNT1 in the process chain, it is giving error "Function module BANK_TMC_API_SIM_GET does not exist Furnction module". when I repeat the step than it is going fine.
Please let me know why this error is coming for first why it is not coming after repeating the step?
Thanks & Regards,
Murali.

Hi Murali,
Hope you are doing good..
Is it a full or Delta load on a daily basis? Did you check if the FM exists in your system?
Did you try debugging the load in source system and check if the extractor is trying to call FM you mention.
If possible please post the exact error message you are receiving so that we could get an idea whats the error and why you are encountering it.
As of now what i can suggest is, go to RSA2 in source system, give the datasource name and check if the extractor code has FM in it.
Regards,
Anil Pragada.

To retain the same file name in target(File) that coming from source system(AS2).

Hi All,
I have a requirement to send the two file from the third party system(GXS) to SAP ECC via SAP PI(version - 7.4). We are using AS2 adapter at the sender side to pick the file and using File Adapter to place the file in ECC.
Its a pass through scenarion(No ESR part is used).
Requirement:
We are going to get 2 files ->Example: one from Axis and another one from ICICI -> each bank file will have a file name ->
We have to post the file at the target system with the same name as source file name, the source file name could come dynamically(with diff time stamp).
Please let me know, Is it possible to achieve the above requirement(we have to retain the file name in target that coming from source system) with Sender AS2 adapter, If yes then please suggest the best approach.
Regards,
Pradeep Bawlia

Hi Guys,
The above requirement is solved now.
Solution - I used java mapping for extracting the same source file name and assignning the same to the target system.
Code:
public class ExtractFileName_ASMA extends AbstractTransformation{
public void transform(TransformationInput in, TransformationOutput out) throws StreamTransformationException
DynamicConfiguration conf=in.getDynamicConfiguration();
DynamicConfigurationKey key_AS2FileNmae = DynamicConfigurationKey.create("http://sap.com/xi/XI/AS2/AS2", "AS2Filename");
DynamicConfigurationKey key_FileNmae = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File", "FileName");
String As2FileName=conf.get(key_AS2FileNmae);
conf.put(key_FileNmae, As2FileName);
try{
byte b[]=new byte[in.getInputPayload().getInputStream().available()];
in.getInputPayload().getInputStream().read(b);
out.getOutputPayload().getOutputStream().write(b);
catch(Exception e)
2. Another solution we can use the graphical mapping and need to use the dynamic config UDF at mapping level to acheive this requirement but here is one drawback - we need to do content conversion is this case.
In case of Java mapping, no need to play with source file.
WITHOUT USING ESR, WE CAN NOT ACHEIVE THIS REQUIREMENT.
Regards,
Pradeep Bawlia

Mapping new product code from source system to old product code in Oracle COA

Mapping new product code from source system to old product code in Oracle COA
Here is the situation:
One of our legal entities is changing their product codes in their COA segment. We are not changing the code structure in the global SOB. Is there a workaround to pull the source system information into ADI (or any other tool) and map it to the current Oracle product code?
Thanks and regards,
[email protected]

Only The Data of Your Code will Change
then if you are trying to copy a standarad sap-code , you need to copy
every include, FM
there is a Copy option over there in program
you can do tat
thnkx bhanu

How to check the Idocs sent from SAP system

How to check the outbound Idocs sent from SAP system to target systems.
How to know the message types and target systems.

Hi,
In Addition with the above mentioned transaction code(WE02), u can check out idocs in these table - EDIDC, EDID4, EDIDS. Depending on different status you can differentiate them as Inbound or Outbound Idocs...
Cheers...
Santosh.
<i><b>Mark All Usefull Answers...</b></i>

DataSource extraction very slow ( from Source System to PSA it takes 23 hrs

Friends,
We have enhanced the datasource 0CRM_SALES_ORDER_I with the user exit....after the enhancement i.e (adding the new fields and wrote some coding to enhance ...) the data extraction takes place for around 23 hours. there is approximately 2,50,000 records.
Can you please suggest any steps to tune up the performance of the datasource.
NOTE: Data Extraction from source system to PSA alone takes 23 hrs.once the data is arrived in PSA then the loading of data to cube is fast.
PLZ help me to solve this issue.
BASKAR

Hi Friends,
This is the code used for the datasource enhancement.(EXIT_SAPLRSAP_001)
DATA : IS_CRMT_BW_SALES_ORDER_I LIKE CRMT_BW_SALES_ORDER_I.
DATA: MKT_ATTR TYPE STANDARD TABLE OF CRMT_BW_SALES_ORDER_I.
DATA: L_TABIX TYPE I.
DATA: LT_LINK TYPE STANDARD TABLE OF CRMD_LINK,
      LS_LINK TYPE CRMD_LINK.
DATA: LT_PARTNER TYPE STANDARD TABLE OF CRMD_PARTNER,
      LS_PARTNER TYPE CRMD_PARTNER.
DATA: LT_BUT000 TYPE STANDARD TABLE OF BUT000,
      LS_BUT000 TYPE BUT000.
DATA: GUID TYPE CRMT_OBJECT_GUID.
DATA: GUID1 TYPE CRMT_OBJECT_GUID_TAB.
DATA: ET_PARTNER TYPE CRMT_PARTNER_EXTERNAL_WRKT,
      ES_PARTNER TYPE CRMT_PARTNER_EXTERNAL_WRK.
TYPES: BEGIN OF M_BINARY,
       OBJGUID_A_SEL TYPE CRMT_OBJECT_GUID,
        END OF M_BINARY.
DATA: IT_BINARY TYPE STANDARD TABLE OF M_BINARY,
      WA_BINARY TYPE M_BINARY.
TYPES : BEGIN OF M_COUPON,
         OFRCODE TYPE CRM_MKTPL_OFRCODE,
         END OF M_COUPON.
DATA: IT_COUPON TYPE STANDARD TABLE OF M_COUPON,
      WA_COUPON TYPE M_COUPON.
DATA: CAMPAIGN_ID TYPE CGPL_EXTID.
TYPES : BEGIN OF M_ITEM,
         GUID TYPE CRMT_OBJECT_GUID,
        END OF M_ITEM.
DATA: IT_ITEM TYPE STANDARD TABLE OF M_ITEM,
      WA_ITEM TYPE M_ITEM.
TYPES : BEGIN OF M_PRICE,
              KSCHL TYPE PRCT_COND_TYPE,
              KWERT TYPE PRCT_COND_VALUE,
              KBETR   TYPE PRCT_COND_RATE,
        END OF M_PRICE.
DATA: IT_PRICE TYPE STANDARD TABLE OF M_PRICE,
      WA_PRICE TYPE M_PRICE.
DATA: PRODUCT_GUID TYPE COMT_PRODUCT_GUID.
TYPES : BEGIN OF M_FRAGMENT,
         PRODUCT_GUID TYPE COMT_PRODUCT_GUID,
         FRAGMENT_GUID TYPE COMT_FRG_GUID,
         FRAGMENT_TYPE TYPE COMT_FRGTYPE_GUID,
       END OF M_FRAGMENT.
DATA: IT_FRAGMENT TYPE STANDARD TABLE OF M_FRAGMENT,
      WA_FRAGMENT TYPE M_FRAGMENT.
TYPES : BEGIN OF M_UCORD,
      PRODUCT_GUID TYPE     COMT_PRODUCT_GUID,
      FRAGMENT_TYPE     TYPE COMT_FRGTYPE_GUID,
      ZZ0010 TYPE     Z1YEARPLAN,
        ZZ0011 TYPE Z6YAERPLAN_1,
        ZZ0012 TYPE Z11YEARPLAN,
        ZZ0013 TYPE Z16YEARPLAN,
        ZZ0014 TYPE Z21YEARPLAN,
     END OF M_UCORD.
DATA: IT_UCORD TYPE STANDARD TABLE OF M_UCORD,
      WA_UCORD TYPE M_UCORD.
DATA: IT_CATEGORY TYPE STANDARD TABLE OF COMM_PRPRDCATR,
      WA_CATEGORY TYPE COMM_PRPRDCATR.
DATA: IT_CATEGORY_MASTER TYPE STANDARD TABLE OF ZPROD_CATEGORY ,
      WA_CATEGORY_MASTER TYPE ZPROD_CATEGORY .
types : begin of st_final,
           OBJGUID_B_SEL TYPE CRMT_OBJECT_GUID,
           OFRCODE TYPE CRM_MKTPL_OFRCODE,
           PRODJ_ID TYPE CGPL_GUID16,
           OBJGUID_A_SEL type     CRMT_OBJECT_GUID,
          end of st_final.
data : t_final1 type standard table of st_final.
data : w_final1 type st_final.
SELECT bOBJGUID_B_SEL aOFRCODE aPROJECT_GUID bOBJGUID_A_SEL INTO table t_final1 FROM
   CRMD_MKTPL_COUP as a inner join CRMD_BRELVONAE as b on bOBJGUID_A_SEL = aPROJECT_GUID .

Doesn't load from source system to PSA and DSO

Hi Gurus,
We have launched a Delta load from Source System (POSDM) to DSO. In the source system there are 5000000 rows but none was loaded into DSO or PSA. The delta load was ok, but any data was loaded.
If the delta load was lunch again, would be loaded those 5000000 rows. Or those 5000000 rows wouldn't be able to load again.
Any idea abut this issue? Any feedback will be really appreciated.
Thanks in advance.

Hi David,
Are you sure this 5 million records are delta records and should be pulled into BW as delta??
did you count the number of records in the underlying tables??
which data source you are using??
Delta loads are suppose to bring the new records or changed records since the last data load and not all the records.
Since the request is green as you said and still it shows 0 records then it is possible that nothing has changed since last delta.try to see the details of the data load... if it failed...may be thats the reason you are not able to see any records.
If you schedule the delta again it will bring the records changed or created after last delta.
If the delta was unsuccessfull then turn the QM status and overall status of request to red manually in the monitor of the request and delete it from PSA and all the targets in which its loaded and schedule the delta again and it should bring the delta.
Thanks
Ajeet
Thanks
Ajeet

How to upload Transaction data from source system to BI 7.0

Dear friends,
I want to know how to upload Transaction data from source system to BI 7.0.
if anybody having step by step material for this process ,please send it to my
mail id.
[email protected]
[email protected]
Thanks,
D.prabhu

Hi,
it works in the same way as before in case you are not using the new features like the dtp and the transformations. Using the new features, you schedule a infopackage to load the data up to psa and schedule a dtp to post the data to the targets.
regards
Siggi
PS: We want to share knowledge in sdn and not keeping it private by having the information sent to our email adresses.

Non-updated Idocs found in Source System

Hi Experts,
I am getting an error Non-updated Idocs found in Source System
Plz help me to resolve this issue.

Hi
BD87 Update Idocs manually.
1. When you look in the Monitor screen for the first time on a day you mostly will see some Loads that have yellow traffic lights. When you click on the lowest line of the Load (with the time of Load start) you will get the next popup screen:
2. Here you can click on the "Yes" button. The Load specification window (right side of the screen) will now be filled with data.
3. You can now start the manual processing of the IDocs. You go to the "Details" tabpage of the right window. You right click on the line with the red traffic light stating "Request IDoc : IDoc ready to be transferred to application" on the "Details" tab page of the Load. In the option menu that appears choose the option "Update manually in OLTP" (click it).
4. You will get to the next screen (which is in fact a transaction in the source system (SAP R/3) where you can update the IDoc that is send by the source system)
5. Now click the "Excecute" button on the left of the screen (or press the F8 button on your keyboard). You will get to the next screen:
6. This states that the IDoc has been passed through to BW. You return to BW by clicking the "Back" button (or pressing the F3 button on your keyboard) twice. After the first time you will see the previous screen and after that the Monitor screen again.
7. You will now see that the Status of the Load has turned to yellow or green. When it is yellow you will have to wait a little time (the execution of the Load in BW is still running) and by clicking "Refresh Details" button on the left upper side of the screen (or pressing the F8 button on your keyboard) you will see the Load turn green.
Hope it helps

Idocs missing from source system

Similar Messages

Maybe you are looking for