Process chain failing (due to back ground jobs)

Dear Friends
Did anybody help me in this topic.
The DTP's of the particular process chain is failing frequently.
The reason is background jobs causing error
why this happens every time?
Did parallel data loading in the DTP may cause any backgound error?
Is it possible for only one update to the DTP at a time?
Thanks in advance for your replies
With Regards
Riyad

Dear,
Check may be helpful and search SDN you will find many related posts.
Error Transporting Process Chain with 2 DTPs
Regards,
Syed Hussain.

Similar Messages

Infopackage in process chain failing due to short dump on regular basis.

HI Experts,
There is a daily process chain in which one of the element (infopackage) fails due to short dump on regular basis (At least twice in a week) please find the message below
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Short text
SQL error in the database when accessing a table.
And in job log it is showing ARFCSTATE = SYSFAIL
We are able to resolve it just manual update and the process goes fine no issues but my question here is what is the exact reason for this and how to resolve it permanently or decrease the frequency of the error.
Please if any one can tell the root cause and the solution to avoid the issue in future on regular basis.
and also can any one elaborate what is ARFCSTATE = SYSFAIL,for trfc check we don't have access to SM58 in ECC side
and trfc is fine in bw side
Appreciate for not giving the general solutions like repeated solutions already posted in SDN
with regards,
musai

You can contact your BASIS person he can help you reg table space issue. it says used space is 98% and free space is 1.03%.
ask your basis to set a threshold to check the space and send a mail notification to all daily regarding the space allocation and utilization.
ARFCSTATE = SYSFAIL means the TRFC did not processed properly to the BW system from source.
Monitoring object with information about tRFC and qRFC calls that are waiting to be executed in this system; after they have been executed, they are deleted from table ARFCRSTATE.
Are there any hung TRFCs which are not processed to BW side. have you checked it
first check
load monitor -- menu -- environment -- job overview -- status of job(is it finsihed or not?) - check the job log -- ther try to find out the hung TRFc
press find --tyep "sysfail" ok -- it will display all the hung or fialed TRFCs which are not processed to BW system.
if you find the hung TID with respect to your load.. next goto SM58 trasaction to process the trfcs manually or use the load monitor menu -- environment -- transaction RFC -- source sys -- it will take you to same SM58 screen -- click F8 it will display the hung TRFc in that duration.
select the TRFc and click on F6 to process them manually.
also check the loackwaits anddead locks in ST04/DB6COCKPIT.( ask basis to check) if any dead locks are there they will take care of it.
check for short dumps in st22 if any and try to analyse.
Check the SM21 system logs.

Process chain failed due to activation of a DSO

Hi friends,
Three four days back the process chain has been failed due to the activation error.The issue was with data and i have deleted the request in manage screen and reloaded again as repeat of delta with corrections in PSA. Which is afterwards activation is successful. Now process chain is getting failed daily saying that request is not present in the DSO( Request is no longer exists in the DSO ). But manual activation of DSO is successful.
Please help me in this reagrd.
Regards,
anil
PS: I tried by removing process chain from scheduling and rescheduling back.

Hi........
Deleting request from the PSA will not help............what is the update mode of ur ODS..........if it is overwritten............then no probs...load the request again in the target...........if not..........then do one thing...........push the request again in the target.........then...........make the QM status red................then delete the request again............just check whether u face the same issue again or not...........
Generally we face this issue............suppose we load a delta request successfully in the target.........then we delete the request without making the QM status red............and after that next delta also loaded............then while activation...............it will ask for the deleted request...........I think there is some confusion...........and u can try the trick..............it may work............
Regards,
Debjani........

Master Data Process chains failing due to special charecters?

hi experts,
we have done all the master data(FI,SD,LO,QM,PM,MM,PP,PS) and created process chains and transported into production system.
when we run the process chains we are facing lot of issues regarding special charecters.
for example. 0MAT_VEND_ATTR Data source.
MATERIAL VENDOR (field - IDNLF).
'UDGÅET
&''UDGÅR
&''UDGÅET
&''36/5599/LED./FÆLLES
&''SØTRANSPORT &
those are the special charecters are coming when i try to execute through RSKC the above Material Vendors, its giving different special chars for different MATERIAL VENDORS like below.
FÆLLESSØTRANSPORT
04/5160/FORSØGSAFD.
(5150)FORSØGSAFD.
like that there are about 15 master data chains are failing.
due to that reason the below transcation chars are not executing.
please suggest me is there any routine or is there any procedure to take care of unpredicted special charecters loading successfully into BW.
regards
venuscm

I don't think its a global setting problem.
Permit the char in RSKC...
Check with the functional team why they are getting Special char values in the loads. ask them to rectify the special char so that you can extract the same to BW side.
go through the blog links provided earlier in my post...
Check the below link which might be of some use to you,..
/people/jyothi.velpula/blog/2010/12/23/removing-invalid-characters-using-field-routine
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0afbb81-f219-2c10-4181-b20f6b10e373?quicklink=index&overridelayout=true
Edited by: prashanthk on Jan 3, 2011 5:35 PM

Does back ground jobs work process go to private mode or not

Hi Experts,
Can any one tell me
Does back ground jobs work process go to private mode or not
Thanks and Regards
Dan !!

Hi Dan,
I do not think background work processes would go into PRIV mode.
the orginal information was remove by Admin because provided by Cut and Paste from SAP Online Help.
you will find it <a href="http://help.sap.com/saphelp_47x200/helpdata/en/7a/caa6f3bfdb11d188b30000e83539c3/frameset.htm">here</a>
The distribution, participation in distributing or otherwise sending of this material is against the law. The material you are requesting is copyrighted material and available ONLY to customers of SAP. If you need such documents from the SAP Service Marketplace then you must have "S" user ID and login yourself to retrieve this material. If you do not have a "S" user ID then you should contact your own internal company groups responsible and request one or request them to retrieve the document for you.
By participating and sending such documents you are at risk for legal action and a removal of your account here on SDN and BPX.
DO NOT send material via email such as this! Further actions will result in officials within your company and your SAP Sales Account being notified and could result in legal action against you as an individual.

Error while activating ODS is not caught in the back ground job..

Hi All,
We have a back ground job to load data to ODS and to activate it..If there is any error while loading or activating the data, back ground job is going into loop instead of cancelling the job..As the job is going into loop we are unable to trace the error unless we cancel the job manually and checking it..We have switched off displaying any messages while doing the back ground job...also we can not set any time limit for the job as it always depends on the volume of the data.
My requirement is , back ground job must get cancelled if there is any error while loading the ODS..Can anybody suggest any idea on this..
Thanks for reading.
Umamaheswar kumar

Hi Uma,
A few hints for running and schedule and monitoring process chains:
- always schedule the process chain in tcode RSPC
- check the log in RSPC for error messages, or
- check BW monitor for the ODS concerned (tcode RSMO, tab Details)
if anything is not working fine, the status of the corresponding load will show you the errors, warnings ...
either in RSPC - log or RSMO.
hope it helps.
Regards,
Lilly

Back ground job for dtp

hi,
is there any possibility to do back ground job for dtp.
if possible can u tell me the necessary settings?

Hi Venkat,
The way to schedule a DTP in BI in NW 2004s is by putting it inside a process chain. The process chain can be scheduled.
See the following link on process chains.
http://help.sap.com/saphelp_nw04s/helpdata/en/d5/e80d3dbd82f72ce10000000a114084/frameset.htm
Hope this helps,
Regards
Karthik
Assign points if helpful.

Back ground Jobs report

HI
I am running Process chain as a Back ground job in my user name, now i have a requirement that we need to extract a report out of my system which contains data about " At what time my process chains are running and how many data are loaded" Is that possible..do we have any TCODE or program for this..?
Regards
Arunkumar

You may have to activate the BI Admin Cockpit to capture all of the statistics for Process Chains. The BI Admin Cockpit is built off of the 0TCT* standard content in your BW environment.
Take a look at the following document:
[BI Admin Cockpit - Technical Content - BI Statistics|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90080703-4331-2a10-cd98-9c1e95acdea0?overridelayout=true]

What is the back ground job when we run an Attribute Change run ?

Dear One´s,
What is the back ground job when we run an Attribute Change run ?
Thanks in advance,
Raj

Hi Raj,
1. If the attribute change run is triggered through process chain the job name is 'BI_PROCESS_ATTRIBCHAN'
2. If the change run is triggered from RSA1> tools?Appl Heirarchy/Attribute changerun then the job name starts with BI_STRU*
3. If you trigger the program RSDDS_AGGREGATES_MAINTAIN from SE38 then the job name will be RSDDS_AGGREGATES_MAINTAIN
Hope this helps...

The back ground job gets cancelled which feds the delta queue?

Hi all,
I can see the delta is empty for the 2lis_11_vahdr ( sales order header datasource) when i happened to check the background job name which feds the delta queue, all the background job gets failed for the same!!
Can anyone let me know what needs to be carried out ?
Thanks

hi,
when i happened to check the logs for that back ground job i got the below message
Extraction queue processing started MCEX11 with 54,331 LUWs
ABAP/4 processor: CALL_FUNCTION_NOT_FOUND''
Thanks

Why will Process chain fail..

Hello,
Could you please provide me the reasons for failing process chains.
Thanks in advance,
G Raghu

Hi...........
1) Suppose a PC starts twice at the same time............then Start Process will fail due to Lock issue........PC will not proceed.......In this situation Start process will remain yellow for a long time......and if you check the job log.........you can see that job is cancelled.................
2) Suppose when a PC is in progress........someone again schedule the PC..........then it will stop at the point........when the PC was scheduled again..........it will not proceed furthur.........
3) Status of Data provider can fail............Suppose one target is not loaded in the defined time...........then this process will fail...........PC will stop.....
4) Drop Pass through can fail...................Suppose data is loade from Y1 to Y2.............but not loaded in Y3( Propagation memory).............this process will fail.....
5) Attribute change Run can fail................
6) * Run or Skip is fail*................Suppose whatever parameters maintained in table YGTTC_SKIP_PARAM for a IP does'nt match then this process will fail.................
7) Loads can fail due to several reasons.............
Hope this helps you........
Regards,
Debjani............

Scheduled back ground job not finishing

hie gurus, i need your help with back ground scheduling , i have created a background schedule to run my program after every 30min . in the job overview it shows my job released and active but its not finishing processing . the program being run picks up data from an external data base and then inserting via BDC call transaction. i have tried with a different program that inserts data into a database table and its executing and finishing well in the back ground. What could be the problem ? and how can i debug a back ground job ??

Daniel,
To start, BDCs are very out-dated. I would look for a BAPI if you are calling std SAP functionality.
Also - direct updates into std SAP tables is a HUGE "no-no"... I hope that you are updating custom tables only.
Pass that - to debug a b/g job--->
1) Set a breakpoint in your program
2) select the job in SM37
3) enter JDBG into the SAP fastpath of the SM37 screen and press ENTER
This will navigate you into a b/g debug - you can then press the debugger buttons to move to your breakpoint.
Hope that helps.

Back Ground Job Issue

Hi,
My report program was executing successfully in the Foreground but not in the back ground.. Can any one help me on this?
My report program has a selection screen..I entered the data for it at and through menu option Program->execute in background..I executed it..As it asked for output device i gave LP01 and No of copies to 1. and checked Radio button Print all. and clicked ok.
It asked me for start time and i selected Immediate and clicked on save.
It gave a status message "Back ground Job Scheduled".
Now when i look through SM37 under my name the job is always active and Never finished.
Can any one help me on this?
Thank in advance..

Just check whether the job is running in the background or not
Double Click on the job name and take the Server & Process Id.
Go back to the SM37 Screen.
Click on Application Servers or directly Open the transaction SM51.
Select the Server and find the process Id with the help of the things you found already
Now, you can see the database level.
Check if the values or moving or not. This way you could track the details
If not, Ask BASIS guys to check whether the job is reading from rollback or not.
If it is, cancel and rerun the job...or else..leave the job..it will finish off in some time.
Hope everything is clear

Back ground job - report, is scheduled 49 hrs ago, still ACTIVE??

Hi Experts,
Pls. clarify one of my simple doubt that, Weather a report(which has only one SELECT statement, with key in WHERE clause) wuld take 49 hours to execute? bcoz, I scheduled a back ground job for my_report, 49 hours ago, its still ACTIVE, OR does it went to infinitive loop?
thanq

Hi
no one select query won't take that mucj of time
may be that program went in infinite loop
please check with that
reward if useful
<b>below is the best way to write a select query</b>
Ways of Performance Tuning
1.     Selection Criteria
2.     Select Statements
     Select Queries
     SQL Interface
     Aggregate Functions
     For all Entries
Select Over more than one Internal table
Selection Criteria
1.     Restrict the data to the selection criteria itself, rather than filtering it out using the ABAP code using CHECK statement.
2.     Select with selection list.
Points # 1/2
SELECT * FROM SBOOK INTO SBOOK_WA.
CHECK: SBOOK_WA-CARRID = 'LH' AND
         SBOOK_WA-CONNID = '0400'.
ENDSELECT.
The above code can be much more optimized by the code written below which avoids CHECK, selects with selection list
SELECT CARRID CONNID FLDATE BOOKID FROM SBOOK INTO TABLE T_SBOOK
WHERE SBOOK_WA-CARRID = 'LH' AND
              SBOOK_WA-CONNID = '0400'.
Select Statements   Select Queries
1.     Avoid nested selects
2.     Select all the records in a single shot using into table clause of select statement rather than to use Append statements.
3.     When a base table has multiple indices, the where clause should be in the order of the index, either a primary or a secondary index.
4.     For testing existence , use Select.. Up to 1 rows statement instead of a Select-Endselect-loop with an Exit.
5.     Use Select Single if all primary key fields are supplied in the Where condition .
Point # 1
SELECT * FROM EKKO INTO EKKO_WA.
SELECT * FROM EKAN INTO EKAN_WA
      WHERE EBELN = EKKO_WA-EBELN.
ENDSELECT.
ENDSELECT.
The above code can be much more optimized by the code written below.
SELECT PF1 PF2 FF3 FF4 INTO TABLE ITAB
    FROM EKKO AS P INNER JOIN EKAN AS F
      ON PEBELN = FEBELN.
Note: A simple SELECT loop is a single database access whose result is passed to the ABAP program line by line. Nested SELECT loops mean that the number of accesses in the inner loop is multiplied by the number of accesses in the outer loop. One should therefore use nested SELECT loops only if the selection in the outer loop contains very few lines or the outer loop is a SELECT SINGLE statement.
Point # 2
SELECT * FROM SBOOK INTO SBOOK_WA.
CHECK: SBOOK_WA-CARRID = 'LH' AND
         SBOOK_WA-CONNID = '0400'.
ENDSELECT.
The above code can be much more optimized by the code written below which avoids CHECK, selects with selection list and puts the data in one shot using into table
SELECT CARRID CONNID FLDATE BOOKID FROM SBOOK INTO TABLE T_SBOOK
WHERE SBOOK_WA-CARRID = 'LH' AND
              SBOOK_WA-CONNID = '0400'.
Point # 3
To choose an index, the optimizer checks the field names specified in the where clause and then uses an index that has the same order of the fields . In certain scenarios, it is advisable to check whether a new index can speed up the performance of a program. This will come handy in programs that access data from the finance tables.
Point # 4
SELECT * FROM SBOOK INTO SBOOK_WA
UP TO 1 ROWS
WHERE CARRID = 'LH'.
ENDSELECT.
The above code is more optimized as compared to the code mentioned below for testing existence of a record.
SELECT * FROM SBOOK INTO SBOOK_WA
    WHERE CARRID = 'LH'.
EXIT.
ENDSELECT.
Point # 5
If all primary key fields are supplied in the Where condition you can even use Select Single.
Select Single requires one communication with the database system, whereas Select-Endselect needs two.
Select Statements           contd.. SQL Interface
1.     Use column updates instead of single-row updates
to update your database tables.
2.     For all frequently used Select statements, try to use an index.
3.     Using buffered tables improves the performance considerably.
Point # 1
SELECT * FROM SFLIGHT INTO SFLIGHT_WA.
SFLIGHT_WA-SEATSOCC =
    SFLIGHT_WA-SEATSOCC - 1.
UPDATE SFLIGHT FROM SFLIGHT_WA.
ENDSELECT.
The above mentioned code can be more optimized by using the following code
UPDATE SFLIGHT
       SET SEATSOCC = SEATSOCC - 1.
Point # 2
SELECT * FROM SBOOK CLIENT SPECIFIED INTO SBOOK_WA
WHERE CARRID = 'LH'
    AND CONNID = '0400'.
ENDSELECT.
The above mentioned code can be more optimized by using the following code
SELECT * FROM SBOOK CLIENT SPECIFIED INTO SBOOK_WA
WHERE MANDT IN ( SELECT MANDT FROM T000 )
    AND CARRID = 'LH'
    AND CONNID = '0400'.
ENDSELECT.
Point # 3
Bypassing the buffer increases the network considerably
SELECT SINGLE * FROM T100 INTO T100_WA
BYPASSING BUFFER
WHERE     SPRSL = 'D'
        AND ARBGB = '00'
        AND MSGNR = '999'.
The above mentioned code can be more optimized by using the following code
SELECT SINGLE * FROM T100 INTO T100_WA
WHERE     SPRSL = 'D'
        AND ARBGB = '00'
        AND MSGNR = '999'.
Select Statements       contd           Aggregate Functions
     If you want to find the maximum, minimum, sum and average value or the count of a database column, use a select list with aggregate functions instead of computing the aggregates yourself.
Some of the Aggregate functions allowed in SAP are MAX, MIN, AVG, SUM, COUNT, COUNT( * )
Consider the following extract.
            Maxno = 0.
            Select * from zflight where airln = LF and cntry = IN.
             Check zflight-fligh > maxno.
             Maxno = zflight-fligh.
            Endselect.
The above mentioned code can be much more optimized by using the following code.
Select max( fligh ) from zflight into maxno where airln = LF and cntry = IN.
Select Statements    contdFor All Entries
     The for all entries creates a where clause, where all the entries in the driver table are combined with OR. If the number of entries in the driver table is larger than rsdb/max_blocking_factor, several similar SQL statements are executed to limit the length of the WHERE clause.
     The plus
     Large amount of data
     Mixing processing and reading of data
     Fast internal reprocessing of data
     Fast
     The Minus
     Difficult to program/understand
     Memory could be critical (use FREE or PACKAGE size)
Points to be must considered FOR ALL ENTRIES
     Check that data is present in the driver table
     Sorting the driver table
     Removing duplicates from the driver table
Consider the following piece of extract
Loop at int_cntry.
       Select single * from zfligh into int_fligh
where cntry = int_cntry-cntry.
Append int_fligh.
Endloop.
The above mentioned can be more optimized by using the following code.
Sort int_cntry by cntry.
Delete adjacent duplicates from int_cntry.
If NOT int_cntry[] is INITIAL.
            Select * from zfligh appending table int_fligh
            For all entries in int_cntry
            Where cntry = int_cntry-cntry.
Endif.
Select Statements    contd Select Over more than one Internal table
1.     Its better to use a views instead of nested Select statements.
2.     To read data from several logically connected tables use a join instead of nested Select statements. Joins are preferred only if all the primary key are available in WHERE clause for the tables that are joined. If the primary keys are not provided in join the Joining of tables itself takes time.
3.     Instead of using nested Select loops it is often better to use subqueries.
Point # 1
SELECT * FROM DD01L INTO DD01L_WA
WHERE DOMNAME LIKE 'CHAR%'
        AND AS4LOCAL = 'A'.
SELECT SINGLE * FROM DD01T INTO DD01T_WA
    WHERE   DOMNAME    = DD01L_WA-DOMNAME
        AND AS4LOCAL   = 'A'
        AND AS4VERS    = DD01L_WA-AS4VERS
        AND DDLANGUAGE = SY-LANGU.
ENDSELECT.
The above code can be more optimized by extracting all the data from view DD01V_WA
SELECT * FROM DD01V INTO DD01V_WA
WHERE DOMNAME LIKE 'CHAR%'
        AND DDLANGUAGE = SY-LANGU.
ENDSELECT
Point # 2
SELECT * FROM EKKO INTO EKKO_WA.
SELECT * FROM EKAN INTO EKAN_WA
      WHERE EBELN = EKKO_WA-EBELN.
ENDSELECT.
ENDSELECT.
The above code can be much more optimized by the code written below.
SELECT PF1 PF2 FF3 FF4 INTO TABLE ITAB
    FROM EKKO AS P INNER JOIN EKAN AS F
      ON PEBELN = FEBELN.
Point # 3
SELECT * FROM SPFLI
INTO TABLE T_SPFLI
WHERE CITYFROM = 'FRANKFURT'
    AND CITYTO = 'NEW YORK'.
SELECT * FROM SFLIGHT AS F
    INTO SFLIGHT_WA
    FOR ALL ENTRIES IN T_SPFLI
    WHERE SEATSOCC < F~SEATSMAX
      AND CARRID = T_SPFLI-CARRID
      AND CONNID = T_SPFLI-CONNID
      AND FLDATE BETWEEN '19990101' AND '19990331'.
ENDSELECT.
The above mentioned code can be even more optimized by using subqueries instead of for all entries.
SELECT * FROM SFLIGHT AS F INTO SFLIGHT_WA
    WHERE SEATSOCC < F~SEATSMAX
      AND EXISTS ( SELECT * FROM SPFLI
                     WHERE CARRID = F~CARRID
                       AND CONNID = F~CONNID
                       AND CITYFROM = 'FRANKFURT'
                       AND CITYTO = 'NEW YORK' )
      AND FLDATE BETWEEN '19990101' AND '19990331'.
ENDSELECT.
1.     Table operations should be done using explicit work areas rather than via header lines.
2.     Always try to use binary search instead of linear search. But dont forget to sort your internal table before that.
3.     A dynamic key access is slower than a static one, since the key specification must be evaluated at runtime.
4.     A binary search using secondary index takes considerably less time.
5.     LOOP ... WHERE is faster than LOOP/CHECK because LOOP ... WHERE evaluates the specified condition internally.
6.     Modifying selected components using MODIFY itab TRANSPORTING f1 f2.. accelerates the task of updating a line of an internal table.
Point # 2
READ TABLE ITAB INTO WA WITH KEY K = 'X BINARY SEARCH.
IS MUCH FASTER THAN USING
READ TABLE ITAB INTO WA WITH KEY K = 'X'.
If TAB has n entries, linear search runs in O( n ) time, whereas binary search takes only O( log2( n ) ).
Point # 3
READ TABLE ITAB INTO WA WITH KEY K = 'X'. IS FASTER THAN USING
READ TABLE ITAB INTO WA WITH KEY (NAME) = 'X'.
Point # 5
LOOP AT ITAB INTO WA WHERE K = 'X'.
ENDLOOP.
The above code is much faster than using
LOOP AT ITAB INTO WA.
CHECK WA-K = 'X'.
ENDLOOP.
Point # 6
WA-DATE = SY-DATUM.
MODIFY ITAB FROM WA INDEX 1 TRANSPORTING DATE.
The above code is more optimized as compared to
WA-DATE = SY-DATUM.
MODIFY ITAB FROM WA INDEX 1.
7.     Accessing the table entries directly in a "LOOP ... ASSIGNING ..." accelerates the task of updating a set of lines of an internal table considerably
8.    If collect semantics is required, it is always better to use to COLLECT rather than READ BINARY and then ADD.
9.    "APPEND LINES OF itab1 TO itab2" accelerates the task of appending a table to another table considerably as compared to LOOP-APPEND-ENDLOOP.
10.   DELETE ADJACENT DUPLICATES accelerates the task of deleting duplicate entries considerably as compared to READ-LOOP-DELETE-ENDLOOP.
11.   "DELETE itab FROM ... TO ..." accelerates the task of deleting a sequence of lines considerably as compared to DO -DELETE-ENDDO.
Point # 7
Modifying selected components only makes the program faster as compared to Modifying all lines completely.
e.g,
LOOP AT ITAB ASSIGNING <WA>.
I = SY-TABIX MOD 2.
IF I = 0.
    <WA>-FLAG = 'X'.
ENDIF.
ENDLOOP.
The above code works faster as compared to
LOOP AT ITAB INTO WA.
I = SY-TABIX MOD 2.
IF I = 0.
    WA-FLAG = 'X'.
    MODIFY ITAB FROM WA.
ENDIF.
ENDLOOP.
Point # 8
LOOP AT ITAB1 INTO WA1.
READ TABLE ITAB2 INTO WA2 WITH KEY K = WA1-K BINARY SEARCH.
IF SY-SUBRC = 0.
    ADD: WA1-VAL1 TO WA2-VAL1,
         WA1-VAL2 TO WA2-VAL2.
    MODIFY ITAB2 FROM WA2 INDEX SY-TABIX TRANSPORTING VAL1 VAL2.
ELSE.
    INSERT WA1 INTO ITAB2 INDEX SY-TABIX.
ENDIF.
ENDLOOP.
The above code uses BINARY SEARCH for collect semantics. READ BINARY runs in O( log2(n) ) time. The above piece of code can be more optimized by
LOOP AT ITAB1 INTO WA.
COLLECT WA INTO ITAB2.
ENDLOOP.
SORT ITAB2 BY K.
COLLECT, however, uses a hash algorithm and is therefore independent
of the number of entries (i.e. O(1)) .
Point # 9
APPEND LINES OF ITAB1 TO ITAB2.
This is more optimized as compared to
LOOP AT ITAB1 INTO WA.
APPEND WA TO ITAB2.
ENDLOOP.
Point # 10
DELETE ADJACENT DUPLICATES FROM ITAB COMPARING K.
This is much more optimized as compared to
READ TABLE ITAB INDEX 1 INTO PREV_LINE.
LOOP AT ITAB FROM 2 INTO WA.
IF WA = PREV_LINE.
    DELETE ITAB.
ELSE.
    PREV_LINE = WA.
ENDIF.
ENDLOOP.
Point # 11
DELETE ITAB FROM 450 TO 550.
This is much more optimized as compared to
DO 101 TIMES.
DELETE ITAB INDEX 450.
ENDDO.
12.   Copying internal tables by using ITAB2[ ] = ITAB1[ ] as compared to LOOP-APPEND-ENDLOOP.
13.   Specify the sort key as restrictively as possible to run the program faster.
Point # 12
ITAB2[] = ITAB1[].
This is much more optimized as compared to
REFRESH ITAB2.
LOOP AT ITAB1 INTO WA.
APPEND WA TO ITAB2.
ENDLOOP.
Point # 13
SORT ITAB BY K. makes the program runs faster as compared to SORT ITAB.
Internal Tables         contd
Hashed and Sorted tables
1.     For single read access hashed tables are more optimized as compared to sorted tables.
2.      For partial sequential access sorted tables are more optimized as compared to hashed tables
Hashed And Sorted Tables
Point # 1
Consider the following example where HTAB is a hashed table and STAB is a sorted table
DO 250 TIMES.
N = 4 * SY-INDEX.
READ TABLE HTAB INTO WA WITH TABLE KEY K = N.
IF SY-SUBRC = 0.
ENDIF.
ENDDO.
This runs faster for single read access as compared to the following same code for sorted table
DO 250 TIMES.
N = 4 * SY-INDEX.
READ TABLE STAB INTO WA WITH TABLE KEY K = N.
IF SY-SUBRC = 0.
ENDIF.
ENDDO.
Point # 2
Similarly for Partial Sequential access the STAB runs faster as compared to HTAB
LOOP AT STAB INTO WA WHERE K = SUBKEY.
ENDLOOP.
This runs faster as compared to
LOOP AT HTAB INTO WA WHERE K = SUBKEY.
ENDLOOP.

Back ground job scheduling(urgent)

Hi all,
can anybody will help me ,regarding the step by step procedure to schedule the background job.
i have to do back ground job scheduling for one program so that in that specified time my report will execute?
plz suggest.
ur idea will be highly appreaciated.
Regards
pabitra

HI
Please follow the below steps to schedule a background job.
First - create a Report-Variant for your print programm using the SE38.
Then...
1.) Call the transaction SM36
Enter a Job Name / You may set a job class other
than 'C' (See online Help on that field).
2.) Push the STEP Button
3.) Push the ABAP Program button
Enter der programm name an the variant name
save that window
4.) Push "BACK"
5.) Push "Start Condition"
6.) Push Date/Time
Enter Date + Time for the first start
Mark "Periodic Job" !!
7.) Push "Period Values"
Set the period you want the job to be started
Save everything
For more info please refer to this link:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a7ed1505211d189550000e829fbbd/content.htm">Background Processing</a>
Kind Regards
Eswar

Process chain failing (due to back ground jobs)

Similar Messages

Maybe you are looking for