Extraction jobs

Hi all,
I have triggered a chain in system A through RSPC_API_CHAIN_START and the source system of the chain is System B but no jobs are getting triggered in system B?WHY SO?
There is no space issue,no RFC connections issue,neither the system is down.
We are able to see the process monitor tab(in the load infopackage step) in the chain but unable to see the extraction job in the source system of the chain in T-code sm37.
we are not understanding what exacthly the problem is.
Can anybody suggest what is the reason it's happening also the probable solution for it.
Thanks in advance.
Jini

Hi,
I am able to see the job name in the source system in RSMO T-code but the job is not active in the source system(i mean not there)i.e in sm37.
hence zero recs are updated.(showing ZERO FROM ZERO recs).
in the status tab it is showing
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.
Thanks,
jini

Similar Messages

Lo-Extraction Job Failed in SAP ECC 6.0

Hello,
My Lo-extraction job failed yesterday because of this I'm unable to extract the delta data from SAP ECC 6.0 to BI. When I extract the Delta data from 2LIS_11_VAITM to BI there is no data because of Job failed in SAP ECC 6.0.
How to get the data back to 2LIS_11_VAITM data source?
Thanks

Error log display as follows
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLMCEX" or "LMCEXU14"
"MCEX_UPDATE_11"
Actually I add ZZ fields to structure if that is the case do i need to delete the data from MCEX11 ?
I delete the data from setup tables but i did not delete the LUW entries?
When do we delete the LUW entries?
If the structure changes do I need to cancel the old job and re-schedule job?
Thanks

Hold extraction job in source system

Hi All,
Is there a way to hold a an extraction job in R/3. We would like to force an idoc to unprocess status (64) in R/3. Please let me know if there is a way to do this.
Thanks a ton!

Hi,
     if you can not find any reason in sm21, st22, rsa3. then try as below:
    1. replicate the datasource;
    2. activate transfer rule;
    3. quit workbench
    4. entry workbench
    5. create a new data package
    6. load data with the new data package again;
hope you good luck;

In DOE while running "EXTRACT JOB" system was shut down.

Dear Experts,
while running "EXTRACT JOB" . system was shut down.then extract queues are in ready state. it's not going to running state.long time it appears like in ready state. if i run manually then it's running for some time then again it's going ready state.how will handle this because of it consist of huge entries we couldn't do manually.if any one knows please provide solutions.
Regards,
Ashok Reddy.

Hi Ashok,
Please check whether the extract queues are in registered state. If not, please register the extract queues using QIN Scheduler (Goto --> QIN Scheduler) & then check.
Regards,
Ananth.

Extraction Job in R/3 not started

Hi Experts,
I have deleted setup tables for 12 appl area.and again filled setup table for some delivery documents.But when we are trying to do init with data transfer ,the BI* job in r/3 not started.I mean extraction is not scheduled.
We waited also for some time.in RSMO details tab -->extraction ,it showing missing message.
It very urgent ..pls help
Naween

This could possibly be also because of your ZZCPIC user authorizations.
Can you check if there have been any change in the authorizations lately ? you can check the changed docs for your user..
If this is the case then u need to get the necessary authorizations else job does not kick in R/3. Also check if the user is locked in BW.

Extraction jobs waits long time

Hi,
I tried to extract 0ORGUNIT information from one of our test systems.
As can be read from the job log at the end, the jobs sits and waits for about 14 hours before actually starting data extraction. We're talking a mere 46.000 entries here. I'm trying to understand why the jobs waits soo long.
Any idea is welcome?
16:17:18 Job started
16:17:18 Step 001 started (program SBIE0001, variant &0000000100868, user name 972044)
16:17:19 DATASOURCE = 0ORGUNIT_ATTR
16:17:19 *************************************************************************
16:17:19 *           Current values of selected profile parameter                *
16:17:19 *************************************************************************
16:17:19 * abap/heap_area_nondia......... 2000683008                              *
16:17:19 * abap/heap_area_total.......... 2000683008                              *
16:17:19 * abap/heaplimit................ 40894464                                *
16:17:19 * zcsa/installed_languages...... NEFD                                    *
16:17:19 * zcsa/system_language.......... E                                       *
16:17:19 * ztta/max_memreq_MB............ 64                                      *
16:17:19 * ztta/roll_area................ 10485760                                *
16:17:19 * ztta/roll_extension........... 2000683008                              *
16:17:19 *************************************************************************
05:54:05 BEGIN BW_BTE_CALL_BW204020_E 46.091
05:54:05 END BW_BTE_CALL_BW204020_E 46.091
05:54:05 BEGIN EXIT_SAPLRSAP_002 46.091
06:29:42 END EXIT_SAPLRSAP_002 46.091
06:29:42 Asynchronous sending of data package 000001 in task 0002 (1 parallel tasks)
06:30:33 tRFC: Data package = 000001, TID = 2DDE00246B9444ED2B370016, duration = 00:00:46, ARFCSTATE =
06:30:33 tRFC: Begin = 24.08.2006 06:29:47, End = 24.08.2006 06:30:33
06:30:33 Job finished

Gimmo,
Apart from my interactive session and the batch job nothing happens on the system.
sm50 shows no activity other than mine.
Sufficient resources are available.
What I do see in sm12 (locks) is:
Cli User         Time       Mode   Table      Lock argument
040 972044       09:27:24   E      EDIDC      0400000000005084008
Selected lock entries:              1
I suspect somethings not right in the ALE arena?
Regards,
Eric

RSCRM_BAPI scheduling of extract jobs after an event

Hi
We are using RSCRM_BAPI to extract data from 3 BW queries and export the data to a CSV file so that it can be picked up and loaded to another system.
The extracts run fine, but I am trying to find a way of including them within the BW process chains with a dependency on the final cube load. This way we can ensure that they are triggered when the data has correctly loaded.
Any suggestions please?

Get the list of Start Variants from table RSPCTRIGGER by giving the list of event ID's or EVENTID <> Blank.
Then enter this list of start variants in RSPCCHAIN to get the list of process chains.

Source system extraction job not starting

Hi,
I transported a CS,TR,UR from Development to Quality system and it worked fine.
Then i moved from Quality system to Test system .
Transports were successful.
I see UP,TR,CS in active state.
I checked the source system mapping and it is perfect.
I checked source system connection and its OK
I scheduled a IP from BI and the job did nt started any job in source system?
Request you to help me on this.

Are you scheduling the job in the foreground/Background.?.
Please schedule in foreground.
Once you are scheduling the info package go to monitor tab
and see how many records it is fetching.
Also make sure you have a immediate scheduling option.
Thanks,
Saveen Kumar

Scheduling InfoPackage fails to start extract in R/3

Hi,
We are extracting data from CO-PA using the delta infosource.
We initialised the Delta successfully (without data transfer) and have now scheduled our infopackage to extract data from R/3.
When we go to monitor, it tells us that the "Request is still running". Within Details:
Requests: Everything OK
Extraction: Missing messages
Transfer: Missing messages or data
Processing: no data
When I go to the R/3, SM37, I see that infact no extraction job has been scheduled. Consequently, the InfoPackage sits in a "Still running" status till it times out.
If I go to iDoc list in R/3 (Transaction WE05), I see within the inbox that there is a iDoc from my BW system of type "RSRQST" (BIW: Data Request message to OLTP) with a status of 64 ("iDoc ready to be transferred to application").
It seems that something is preventing this iDoc from initiating the extract.
Can anyone suggest a cause of this problem?
Thanks
Leanne

hi,
how about the other infopackage extraction ?
try to check following from monitoring of the request, menu Environment
- Transaction RFC >> in the datawarehouse
Transaction RFC >> in the source system
- ALE management >> in the datawarehouse
ALE management >> in the source system
- Check connection
- RFC log on

R/3 job and get the details of variants like (from and to)

Hi,
How to find R/3 job and get the details of variants like (from and to) for that job.
the job is extraction job and running for 4 hours in R/3 once atfer this job completes BW job will start executing. Now i have to analyse R/3 job that how many years of data it is extracting (from, to) and other useful information why it is taking time for 4 hours.
Please let me know what transaction i have to use and how to check this information in R/3 side.
Thanks,

Hi........
Go to SM37 >> select the job >> Click on Job log.........Check there whether u r getting any Clue or not...........Is this load is through PSA..........? if so check the records of the First data packet...........then the Last data packet............from there u can get some idea..................
Also u can check the data in the Extractor.......is it a full load?.............Go to RSA3 >> Execute..........there check the data........
Is it a LO datasource ? if so................Go to LBWE >> Click on maintenance link for your datasource........>> Here in the Right pane u can see the Structute associated with that Datasource ...........If u remove MC from those structure name............u will get the table name..............In those tables also u can check the data...............there should be some data field.............from where u can get some idea.........
If ur Extractor is extracting data using some Function Module.............then open the datasource using RSA2.............there double click on the Exrtractor..............u will get the function module.................u can try to analyze the function module............
For Variants..................select the job >> click on Step in the top >> then Go to in the top >> Variant..............but I don't think this will help u............this will tell u that this Extraction job is part of which chain or IP......
Regards,
Debjani..........

ABAP HR data extraction

Hi,
My query is related to ABAP HR.
I have to extract Job record for the
employee where hiredate lies within the set period ( 60 days in my case
i.e.
PN-BEGDA = ( SY-DATUM ) - 60. "Begin date
PN-ENDDA = ( SY-DATUM ) - 1 . "End date)
if no record exists within the set period i have to check the history for the same employee and extract the latest record for the same.
Please suggest me what can be done.
Regards,
Richs

Hi Richs,
write this way.
PN-BEGDA = sy-datum - 60.
PN-ENDDA = sy-datum - 1.
RP_PROVIDE_FROM_LAST P0000 space PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
*print the pernr.
ELSE.
PN-BEGDA = '18000101'.
PN-ENDDA = '99991231'.
RP_PROVIDE_FROM_LAST P0000 space PN-BEGDA
PN-ENDDA.
IF PNP-SW-FOUND = 1.
print the pernr
ELSE.
REJECT.
ENDIF.
ENDIF.
Edited by: Velangini Showry Maria Kumar Bandanadham on Feb 11, 2008 4:58 PM

Processing overdue error during delta extraction from datasource 0CO_OM_CCA

Hi,
I'm getting "Processing overdue error" in BW while extracting delta from datasource 0CO_OM_CCA_9. all other extraction jobs from R3 -> BW are successful. Even Delta init on this datasource is successful & problem is only with delta package.
I appreciate if someone could provide information based on the following error details on this issue.
here are the extraction steps we followed.
Full load of fiscal years 2006 & 2007 Into transactional cube.
load budget data into transactional cube.
compression of the cube with "0 elimination"
Delta Initialization with fiscal period selections 1/2008 to 12/9999
all the above steps were successful.
and when delta package is scheduled, we are getting following errors.
BW system log
BW Monitoring job is turning red with following message.
Technical : Processing is overdue
Processing Step : Call to BW
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in
the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely
connected to the SAP BW. Check especially the authorizations of the
background user in the source system.
R3 Job Log
Even after BW job turns to red, R3 job continues to run for 2 hours and
eventually gets cancelled with an ABAP dump & here is the log.
Job
started
Step 001 started (program SBIE0001, variant &0000000110473, user ID
BWREMOTE) DATASOURCE = 0CO_OM_CCA_9
Current Values for Selected Profile Parameters
abap/heap_area_nondia.........2000000000 *
abap/heap_area_total..........2000000000 *
abap/heaplimit................20000000 *
zcsa/installed_languages......EDJIM13 *
zcsa/system_language..........E *
ztta/max_memreq_MB...........2047 *
ztta/roll_area................6500000 *
ztta/roll_extension...........2000000000 *
ABAP/4 processor: SYSTEM_CANCELED
Job cancelled
Thanks,
Hari Immadi
http://immadi.com
SEM BW Analyst

Hi Hari,
We were recently having similar problems with the delta for CCA_9. And activating index 4 on COEP resolved our issues.
Yes, by default there is a 2 hour safety interval for the CCA_9 DataSource. You could run this extractor hourly but at the time of extraction you will only be pulling postings through 2 hours prior to extraction time. This can be changed for testing purposes but SAP strongly discourages changing this interval in a production environment. SAP does provide an alternative described in OSS note 553561. You may check out this note to see if it would work for your scenario.
Regards,
Todd

Job-scheduling on a specific instance on source system

Hello All,
Is there any possibility to schedule an infopackage in BW and tell the job that the corresponding job on source system (e.g. R/3-system) should run on a specific instance?
Thanks,
Pavan

Hi,
I guess the job is related to extraction job in R/3 that relates to the BI load..
Here if this job runs on a particaular RFC user always , depending on the user u can resrtict the instance on which it is supposed to run...
Take the help from BASIS they can fix the issue....
rgds,

Extract data from Retai & AFS system

Hi , Guys,
If there are SAP Retail & AFS system with different master data and transactional data , how can I extract master data and transactional data from these two system into SAP BW?
For example , if i want to extract the stock management data , how do I create the two Souce system in BW, both as SAP souce system or not?
Thanks !

Hi Yong,
1. Should I create both systems as SAP source system or not?
Yes, both should be created as SAP source systems.
2. If I want to extract the master data of 0MATERIAL , should I do the extraction job from the two source system with "0LOGSYS" ?
You have to understand the business process of how material master data flows across these two systems with the help of the functional team.
In our scenario, we have not used '0LOGSYS', because the same material code coming from both the systems were one and the same.
3. If I want to extract the transactional data of stock movement data from both systems, which infocube in BI content can I use?
I suggest you implement standard business content ( 0IC_C03, I guess ) and utilize that for one source system ( Say AFS). Copy this cube into Z cube called ZIC_C03 and connect the retail data sources to this cube. If you want to combine stock reporting from both the systems, you can create a multiprovider on top of this.
Thanks,
Krishnan

Failure when extracting data from R/3

We have many InfoPacjkages running business content extractors from R/3 into PSA Occaisonally these extracts fail with the following message:
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.
The failure appears to be caused by the extract job in R/3 not starting, no job BIREQU* in SM37.
When this situation occurs the BW job waits a lenth of time, in our case approximately 8 hours, before going red.
Does anyone else suffer this kind of issue and if so is there any way in reducing the time elapsed before BW errors?

Hi Terry,
you can reduce BW job waits a lenth of time at Infopackage level.
RSA1-> select you infopackage -> Schedule (menu) -> Timeout time -> Maximum wait time for this infopackage (here you can se 1 or 2 hrs).
Best Regards.

Extraction jobs

Similar Messages

Maybe you are looking for