cancel
Showing results for 
Search instead for 
Did you mean: 

Extraction Issue

Former Member
0 Kudos

HI all

I have full load which is part of process chain and runs on daily basis.It updates around 300 records only.

However it takes more than 3 hours to complete.

I have check the job log in source system

Date Time Message text Message class Message no. Message type

17.03.2009 18:58:09 Job started 00 516 S

17.03.2009 18:58:09 Step 001 started (program SBIE0001, variant &0000000010365, user ID ALEREMOTE) 17.03.2009 18:58:09 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks) 17.03.2009 18:58:09 DATASOURCE = 0BP_UNAME_ORGUNIT_ATTR 17.03.2009 18:58:09 ************************************************************************* 17.03.2009 18:58:09 * Current Values for Selected Profile Parameters 17.03.2009 18:58:09 ************************************************************************* 17.03.2009 18:58:09 * abap/heap_area_nondia......... 2000683008 * 17.03.2009 18:58:09 * abap/heap_area_total.......... 4000000000 * 17.03.2009 18:58:09 * abap/heaplimit................ 40894464 * 17.03.2009 18:58:09 * zcsa/installed_languages...... ED * 17.03.2009 18:58:09 * zcsa/system_language.......... E * 17.03.2009 18:58:09 * ztta/max_memreq_MB............ 500 * 17.03.2009 18:58:09 * ztta/roll_area................ 3500032 *

17.03.2009 18:58:09 * ztta/roll_extension........... 2000683008 *

17.03.2009 18:58:09 *************************************************************************

17.03.2009 19:05:12 BEGIN EXIT_SAPLRSAP_002 287

17.03.2009 19:05:12 END EXIT_SAPLRSAP_002 287

17.03.2009 19:05:12 Asynchronous send of data package 1 in task 0002 (1 parallel tasks)

17.03.2009 19:05:12 IDOC: Info IDoc 2, IDoc No. 7367574, Duration 00:00:00

17.03.2009 19:05:12 IDoc: Start = 17.03.2009 18:58:09, End = 17.03.2009 18:58:09 17.03.2009 19:05:12 tRFC: Data Package = 1, TID = 13C502E513C049BF83E801E2, Duration = 00:00:00, ARFCSTATE = RECORDED R3 038 S

17.03.2009 19:05:12 tRFC: Start = 17.03.2009 19:05:12, End = 17.03.2009 19:05:12

17.03.2009 19:05:12 Asynchronous transmission of info IDoc 3 in task 0003 (0 parallel tasks)

Please let me know what is the problem with this issue

suggest the solution???

Regards

Edited by: Bi power on Mar 17, 2009 2:49 PM

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member184494
Active Contributor
0 Kudos

Your job log in the source system seems to suggest about8 minutes or so ...

You should get the time taken in the infopackage also ..?

Former Member
0 Kudos

HI arun

Thanks for the reply.Could u please suggest me how to get the time taken for the infopackage.

regards

former_member184494
Active Contributor
0 Kudos

You should get the same in the detail part of the infopackage where the ending time for each stage will be shown..

Also do you have any complex routines in the update rules / transformations - this might be delaying the load...

Former Member
0 Kudos

HI arun

I appreciate ur valuble and quick response.

I checked in the detail tab..all the datapacket are taking aroung 3hours 15 mins to complete.

Please let me know what is causing this issue and how to resolve it.

former_member184494
Active Contributor
0 Kudos

It is not the data packet - you will have various stages - like Data selection , transfer rules etc etc ... which is taking the bulk of the time here?

Former Member
0 Kudos

Hi arun

I chekd the time taken for the diff sections in details tab.Please see below

*request message : 1 sec*

*Extraction message:3 hrs 12 min*

*Transfer : 3 hrs 12 min*Processing datapacket: 3 hrs 5 min

Hope this info will help to investigate??

I would like to add some info..

1. once load start after few minutes except the "Extraction Tab" ,remaining section are in "Green".

2.Extraction section will remain in yellow.

Regards

Edited by: Bi power on Mar 17, 2009 3:44 PM

Edited by: Bi power on Mar 17, 2009 3:51 PM

former_member184494
Active Contributor
0 Kudos

Looks like there is some code in your Transfer / Update routines..

also try extracting only to PSA and this is the time taken to extract from source system the rest is in BI which is usually due to routines etc...

Former Member
0 Kudos

HI arun

I have just one routine , which will assing the sy-datum to the infoobject. Datatarget contains totally 5

infoobject only.Any valuable inputs on what is causing issue.I appreciate ur help

Can anyone give the valuable inputs???

regards

Edited by: Bi power on Mar 17, 2009 7:15 PM

Edited by: Bi power on Mar 18, 2009 12:29 PM

Former Member
0 Kudos

Try to pull the data till PSA and see the time it takes. As Arun has pointed out it takes hardly 8 minutes in the source system.

Thanks.

Former Member
0 Kudos

HI

I tried to pull till Psa and then into BI. However in extacts quickly till PSA.Then its taking more than 3

hrs to finish in BI. Infoprovider has just 5 object.Out of 5 infoobject 4 are having direct mapping.Other one

has a routine which is simple which assing sydatum to the infoobject.

Please suggest what to do to resolve the issue??

Regards

Former Member
0 Kudos

Its taking time in the BW side. It can be because of multiple resons (ABAP codes, expensive sql statements).

But in your case as you have mentioned there is only one routine .. It should not take time.. If its development sytem, could you try the load after taking out this routine .. and see if the routine is the one which actually is taking time ..

Thanks.

Former Member
0 Kudos

HI

This issue is in the production system.It is updating only aroung 300 records only.

What could be the other reasons???Please give ur valuable inputs..

Regards

Former Member
0 Kudos

Could you copy-paste the routine here, so that it becomes easy to identify the expensive statement.

Thanks.

Former Member
0 Kudos

Hi

Please see the below routine and give suggestions..

PROGRAM CONVERSION_ROUTINE.

  • Type pools used by conversion program

TYPE-POOLS: RS, RSARC, RSARR, SBIWA, RSSM.

  • Declaration of transfer structure (selected fields only)

TYPES: BEGIN OF TRANSFER_STRUCTURE ,

  • InfoObject 0BPARTNER: CHAR - 000010

  • PARTNER(000010) TYPE C,

  • InfoObject 0USER_SYST: CHAR - 000010

  • OLTP_SYSTEM(000010) TYPE C,

  • InfoObject 0USER_NAME: CHAR - 000012

  • OLTP_USERNM(000012) TYPE C,

  • InfoObject 0ORGUNIT: NUMC - 000008

  • ORGEH(000008) TYPE N,

  • dummy field to avoid syntax error

$dummy(1) type c,

END OF TRANSFER_STRUCTURE .

  • Global code used by conversion rules

$$ begin of global - insert your declaration only below this line -

  • TABLES: ...

  • DATA: ...

$$ end of global - insert your declaration only before this line -

----


  • FORM COMPUTE_/BIC/ZLASTDATE

----


  • Compute value of InfoObject ZLASTDATE

  • in communication structure /BI0/MBPARTNER

*

  • Technical properties:

  • field name = /BIC/ZLASTDATE

  • data element = /BIC/OIZLASTDATE

  • data type = DATS

  • length = 000008

  • decimals = 000000

  • ABAP type = D

  • ABAP length = 000016

  • reference field =

----


  • Parameters:

  • --> RECORD_NO Record number

  • --> TRAN_STRUCTURE Transfer structure

  • <-- RESULT Return value of InfoObject

  • <-> G_T_ERRORLOG Error log

  • <-- RETURNCODE Return code (to skip one record)

  • <-- ABORT Abort code (to skip whole data package)

----


FORM COMPUTE_/BIC/ZLASTDATE

USING RECORD_NO LIKE SY-TABIX

TRAN_STRUCTURE TYPE TRANSFER_STRUCTURE

G_S_MINFO TYPE RSSM_S_MINFO

CHANGING RESULT TYPE /BIC/OIZLASTDATE

G_T_ERRORLOG TYPE rssm_t_errorlog_int

RETURNCODE LIKE SY-SUBRC

ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel datapackage

$$ begin of routine - insert your code only below this line -

  • DATA: l_s_errorlog TYPE rssm_s_errorlog_int.

RESULT = sy-datum.

  • returncode <> 0 means skip this record

RETURNCODE = 0.

  • abort <> 0 means skip whole data package !!!

ABORT = 0.

$$ end of routine - insert your code only before this line -

ENDFORM.

Regards

Edited by: Bi power on Mar 18, 2009 11:46 PM

Edited by: Bi power on Mar 19, 2009 3:05 PM