Error during extraction when update mode=D in RSA3

[former_member182537]

HI,

One of my delta load to dso from R3 is taking too much time.So when i checkd in RSA3 for this DATA SOURCE for update mode =D.

I entered same selection as used in Infopackage.

i am getting error "error occured during extadction".

and for update mode= FULL F .its extarction for same conditions.

any idea on this ??

Thanks

Nilesh

[Former Member]

Hi,

I have already updated the comment in your other question.

The reason is that you would have left target system as empty. Please provide target system and then try.

[former_member182537]

yes i have done that and extraction is going on.

Please tell what if this extarction takes 3-4 hours as data load takes to ODS.then what can i do improve this time

[Former Member]

Hi,

As I understand, this would go to dump in sometime(will get timeout in half an hour or so based on setting in your system).

After that you can go to st05 and click on deactivate trace and then on display trace. It will give you time taken by differnt steps.

From there, you would be able to find which step took maximum time and then you can look into improving preformance.

[Former Member]

Normally this will not take the time like the load in the BW.

As for the BW the idocs needs to be processed and then move to the BW but in RSA3 its different as it will read the content of the tables of the Delta queue in this case.

So the time taking in RSA3 shud be very less. So you dont need to worry about this..

Murali

[former_member182537]

Hi,

I tried with update mode=R in RSA3 and gicen selction as its in IP then its giving me dump with message "Result of customer enhancemnet 19571 records"

Error details are -

Short text

Function module " " not found.

What happened?

The function module " " is called,

but cannot be found in the library.

Error in the ABAP Application Program

The current ABAP program "SAPLRSA3" had to be terminated because

come across a statement that unfortunately cannot be executed.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

please guide.

[Former Member]

Hi,

Did you check in ST05 as to where it is taking maximum time in all the steps.

[former_member182537]

So this ST05 needs to be checked in BW ?

Also i dont have authorization to activate trace in BW in Prod.

[Former Member]

Hi,

As I had mentioned earlier, to get the details through ST05, you need to first activate trace in R/3, run RSA3 and once it goes to dump, go to ST05, deactivate the trace and display trace in R/3.

Did you follow these steps.

[former_member182537]

I dont have authorization to activate Trace in R3.

so whom to contact-security/basis ??

Also since delta D update mode is also taking long time in RSA3 so can ABAPer help me to debug code to identify where its taking time ??

[Former Member]

Hi,

For getting trace authorisation, you need to contact BASIS team.

Also, if its some z-code in your datasource i.e. based on function module, you may take help from an ABAPer as they may help you on any performance related issues.

[former_member182537]

Thanks a lot Rahul for help and support.i will ask basis team

[former_member182537]

Hi ,

This is log in SM21 while extarcting data in delta mode its giving dump.

Reading:

Number of records read......... 0000002885

Number of records selected..... 0000000003

Old records skipped............ 0000002865

Records of invalid users skipped 0000000017

Further selection:

Number of records read......... 0000000003

Number of records selected..... 0000000002

Parameter records suppressed... 0000000001

Number of records printed...... 0000000002

End of system log