Back ground job work in MM

CAN ANY BODY TELL ME WHAT IS A BACK GROUND JOB WORK IN MM pls explain it with good example tell me 1 or 2back ground job work relevent transactions
good answer will be awarded
kiran

Hi,
Background job means system will automatically perform some transaction / actions at perdetermined time based on the variants selected for that program.
Ex 1: You want to see the list of PO or PR or Production order created for a day, you can create a ABAP program and give the creation date in selction screen.
Provide the Plant or doc type, file path to download the report etc..
and save the variant.
You can set this program to run during mid night( 11.00 p.m) with the sysytem date (crrent date).
So system will run this program and extract the report in Application server level as per the file location given in the program selection screen.
Ex 2:
MRP program
Ex 3.
Auto PO creation program
Thanks,
Kumar Arcot

Similar Messages

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.

Back Ground Job not Working

Hi,
I have watched all the threads regarding Back Ground job like SE36 & SE37. I have given a back ground job and its not working.
Its an ABAP Program which is creating an OLEDB Connection to MSACCESS and then retrieving and updating database table. The program is working very fine on foreground but when it is given to back ground job then it shows that the program is running, i mean in delay the time is ticking. But at last it is canceled by the system.
What's the thing i am missing or what should i do here? I have already set my program at high priority.
Thanks.

Hi Atish,
Are you sure that we cannot run in background? Can you please explain me why it cant be done.
Thanks,
Inder.

RMCB0300 is not working in back ground job

Hi
I call t-code MC.9 program (RMCB0300) in back ground by using sample code given below.
SUBMIT RMCB0300 WITH SL_WERKS-LOW = u2018ABCDu2019
                  WITH SL_LGORT = 'W001'
                  EXPORTING LIST TO MEMORY AND RETURN.
CALL FUNCTION 'LIST_FROM_MEMORY'
    TABLES
      LISTOBJECT = LISTOBJECT
    EXCEPTIONS
      NOT_FOUND = 4
      OTHERS     = 8.
IF SY-SUBRC <> 0.
ENDIF.
The 'LIST_FROM_MEMORYu2019 is getting correct output in four ground but
not in back ground job.
Kindly help.

When you use 'LIST_FROM_MEMORY' it basically imports the memory id '%_LIST'.
When running MC.9 in foreground the memory id '%_LIST' is saved (you can check in debugging) but in background the memory id is not saved
This is why you are not getting the data correctly in background.
BR,
Suhas

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 - 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 Printing Problem

Dear Experts,
We schedled one back ground job with spool generation. Ecery thing is working fine but in printing selecton parameters are printing along with out put data.
That means, if i gave 1000 materials in my variant, in spool first 1000 materials are printing an then actually out put is printing. i need to avoid these printing of selection set.
Please help me...
Thanks in advance

Hello,
Pleas find if there is any "PRINT_SELECTION" function module in report, which should be responsible for printing selection screen parameter values.
Thanks.

Back ground job bdc session

Hai All,
Can any one tell me how to catch the erros in BDC session method back ground job.
I need to update Sales orders in BDC session, back ground job.
Finally at the end I need to generate a report which contains all the succesfull updates & errors.
I tried this using call transaction with messtab and is working fine.
Please tell me how to do this in Session method.
Thanks & Regards,
Bhaskar.

Hi Bhaskar,
In Session method what you need to do is before processing of hte BDC first you need to check all the data. And if any error found then populate it into the internal table. And that internal table you need to display it on the output......
I think this is the solution but I am not to sure........
&********Reward Point if helpful*******&

Genetare the back ground jobs of the program from the SM36 tcode

Hi All,
Consider the following points:
-- My main program will schedule the jobs using the CALL TRANSACTION method
-- Now i want to create a Variant for the Main program and generate the back ground job using the SM36 Tcode
-- Finally it has all the jobs of the main program
-- Program is working fine from the Frontend only.....
Please provide solution for the same.
Thanks in Advance.
Regards,
Ramana

Sravya,
On SM36 when you schedule jobs, you will see options like AFTER EVENT and AFTER JOB. You can use these to schedule you jobs accordingly. Else you can also think of making each of these jobs as a steps in one single job if your requirement allows you to do the same.
In case of using events, you should make sure to raise the event using available FMs.
thanks,
Vikram.M

Back ground jobs excluding

Dear SDExperts
i using this program RVV50R10C To exclude some sales documents in back ground jobs
ex : i have 100000 to 1000050 sales doc no are there so in this i dont want to some sales documents nors in background like 1000015,17,22,
But i am not able to it
i am using this program ..RVV50R10C is it right ?

vemuri santosh kumar
In one line, you were indicating that the program would not work but in the next line you have suggested the same program. Please check.
G. Lakshmipathi

Define back ground job for Maintenance Order Settlement through KO8G

Hi Experts,
I need to define back ground job for Maintenance Order Settlement through KO8G transaction code.
Here are the requirements
1. The job should run on weekly basis automatically.
2. The settlement period and posting period should be taken care by the job dynamically. i.e. if the job runs in July, the job should pick up Settlement period and posting period as 7 automatically.
Kindly let me know the steps to define the back ground job as per above requirement.
Sanjeev

To run the KO8G each week, the a RECURRING job has to be created. At my job, Basis/Ops department would create and schedule the job.
To have the posting periods, dates etc dynamically determined at the time the job runs:
Create the variant and save.
In 5.0, KO8G does not save a variant, therefore, go to SE38 and create a variant for program: RKO7KO8G
When you go to the ATTRIBUTES screen, to add a name and description, you will see a list of all the fields that are part of the selection criteria.
For an example, I frequently use the Posting Date. To the right of the screen is a field called Selection Variable, click on the drop box and select D - Dynamic Date Calculation.
Go to field NAme of variable, click on drop box and select the variable you want.
Each field has its own list of selection variable and name of variable depending on how it works in the progra.
If you look at Posting period you will see:
T: Table Variable from TVARVC
B: User-defined variables
I do not know about User defined variables, but for TVARC there is thread that leads to a "how to" blog
[How create a variable in the TVARVC that calculate the last week]
do some more searching and you should find more answers
Good luck
Althea

Output should be in Text format from Back ground job

Hi friends,
I have scheduleda back ground job. In the receipent i ahve put my user mail ID. when the job was finished the output came as HTML file. where as my user wants a Text file or excel file.
We are in ECC 5.0 and i am just scheduling standard ABAP program( costing run
Is it possible , if yes then, please let me know where to change the setting.
Cheers
PK

Hi,
I tried the same , it did not work for me. But when i contacted my Basis Guy through SCOT he changed. Now the text file has started coming.
But now next problem is my spool request is of 215 pages but system is sending the text file for only first 10 pages..
I have changed the setting for display from 10 pages 215 pages . and belwo even changed the seeting to permanenet between logons..Still system did not send the file to email Id.
can you help mein this regards
cheers
PK

How to download data which comes in back ground job to presentation server.

HI ,
I am creating one job which has to download data to presentation server.
for back ground jobs gui_download will not work..
plz sugest the alternative for this...
thakns in advance,
khasimsa

there are so many posts in SCN , please search .
write data to application server in background and then download to presentation server online.

How To Handle With Back Ground JOB From WEBUI When Click On "Appove"

Hi
How To Scheduled A Job Through ABAP Report In back end Of CRM when i click on "Approve" Button in WEBUI From result list.
As per My requirement I have a Search View and Result View
In Search View I have Below Fields
ITC Vendor ID
Claim Status
User status (date status changed)
Model
Serial Number
Date completed of Service Completion
Based on Search Criteria I will get Result In Result View.(Suppose 10 Records I got In Result View)
In the Result View I need to Add one Button As "Approve"
When i Click On Approve button One Pop up Message Need to Open And In that popup window I need to Display Below Text
"Approve Claim Job Has Started In Background
Note: Only Claims Which are in Submitted Status Will be Approved. you May Close This Window"
In SAP CRM System Back Ground Job Need To Start When Click On "Approve" Button In WEBUI .
In the Back Ground ABAP Report which will validate based on Result List Records"
In the Result List we may have all types of Claims which are status in "Submitted" "Pending" "Rejected" "Approve".
I need to collect all records from Result list and validate Those Records who's Status in "Submitted
1)Sort all the claims based on ITC Vendor ID.
2)Grouped all the submitted claims against each ITC Vendor ID from the search result
3)Change the status of the selected submitted claims to Approved.
4)Displays information messages as mentioned whenever a claim is approved, the same message will be captured in the job log.
‘Claims <ClaimID 1>,…<ClaimID N> now approved for ITC Vendor ID’.
5)Sending Email to each IRC.
6)Capture all the approved claims in the below format (Format Attached "Screen Shot Attachment")
7)Store the file in the Application Server AL11 in .csv format
Please Find Attachement For Reference.
1)ITC Claim Screen Shot
2)Screen Shot For Attachment
Thanks
Raj

Hi,
You can add the following code in on approve method to show popup to the user,
IF req_edit IS NOT BOUND. " gloabl attribute in impl class of the view
    REFRESH lt_buttons.
    lss_button-id = 'btnyes'.
    lss_button-text = 'YES'.
    lss_button-on_click = 'YES'.
    APPEND lss_button TO lt_buttons.
    CLEAR lss_button.
    lss_button-id = 'btnno'.
    lss_button-text = 'NO'.
    lss_button-on_click = 'NO'.
    APPEND lss_button TO lt_buttons.
    CLEAR lss_button.
    CALL METHOD comp_controller->window_manager->create_popup_2_confirm
      EXPORTING
        iv_title          = 'ATTENTION'
        iv_text           = 'Are you sure you want to edit this document?'
        iv_btncombination = '99'
        iv_custombuttons = lt_buttons
      RECEIVING
        rv_result         = req_edit.
    req_edit->set_on_close_event( iv_event_name = 'EDIT' iv_view = me ). "#EC NOTEXT
    req_edit->open( ).
    RETURN.
ELSE.
    lr_node ?= req_edit->get_context_node( 'OUTPUTNODE' ).
    lv_outbound = lr_node->get_event_name( ).
* CLEAR ptc_pricing_status.
*    lv_outbound = req_edit->get_fired_outbound_plug( ).
    IF lv_outbound = 'YES'.
you can use the submit report code here and you can al the validations here
    ELSE. " No
if user clicks no nothing to do..
    ENDIF.
    CLEAR req_edit.
ENDIF.
Best Regards,
Dharmakasi.

How to find the back ground job details

Hi All,
   I have a back ground job running from many days, now we would like to know when this job was created on what date this job actvlly created and schuduled.
           Please informe me how to check this.
Thanks & Regards,
Muralikrishna

On SM37 screen there is plenty of options are there:
This is what i got from SAP help
Explanation for each selection field:
o   Jobname: Name of the job as an identifier.
o   Username: Name of the user who designed and planned the job.
o   Start date: The start condition of the job, which could be a time
frame or an event that the job is waiting for. Specifying both will
yield jobs whose starting condition is either of the two
conditions.
ABAP program step: Name of an ABAP program that acts as a step in a
job.
Status selection: The current status of the job. By default, the
SCHEDULED option is not marked. To see the scheduled jobs, you must
explicitly check this.
also give the proper values in Job Satus also.

Back ground job work in MM

Similar Messages

Maybe you are looking for