Background jobs in Ext. Classic not necessary

I have just learnt that if you are running extended classic scenario, it is not necessary to run the background jobs clean_reqreq_up and bbp_get_status.
Is this true? I have always scheduled these jobs when using extended classic and have never had any problems, but as I understand, they are not actually required to create PO's in EC scenario.

Monica,
You are right. These jobs donot actually create the PO's. They only update status of a PO creation. (BBP_GET_STATUS_2). CLEAN_REQ_REQ_UP cleans all unneccesary entries in EBP once the PO or PR is created.
So the answer to your question is that you dont need this job to create a PO in SRM.
Please assign points if answer is usefull.
Thanks,
Sundeep

Similar Messages

Afer background job finished, spool was not generated

hi all
Afer background job finished, spool was not generated but all background jobs is not
soem background jobs was created spool.
even if same user and same backgorund job, sometime generated spool or not.
how can I solve??
thanks

Hi,
Spool will be generated only spool specification wil be defined for that job.
Select the job go to steps spool specification you can see the device assigned to it.
Regards
Ashok

Background job in APO does not start because of invalid user name

Hello,
I have a macro in a planning book and the /sapapo/cons_check program which a triggered via a background job. Now, I have problems with the start of the job:
At the time the job was created inside SAP, an error occured. The job contains invalid values.
The user name within the job does not exist any more.
Now, I try to change the user name of the job (via step in sm37), but the error occured again.
I have the possibility to create the invalid user name once again in su01.
But I want to change the user name of the job - does somebody know how to do it?
Thanks for your help!
Kind regards
Heinz

Hello Heinz, this looks surprising.
It's quite easy to change the user name in the SM37 job step, and we haven't faced issues with this.
Could you check how many jobs are in either "scheduled" or in "released" status, and change steps for all of them? May be you changed the scheduled job, but the released job wasn't changed.
Use your job name and give a search date as 1-2 years in the past, and around 1 month in the future. With this time horizon, you should most likely be able to capture all the relevant jobs having the same name that you are using.
Now change the user name in step for all the jobs received above to be fully sure.
One more trial could be to copy the current scheduled job to another job, modify the user name in this newly created job and then delete the old one.
One of the above trials might possibly help you in some way, else its very tough to understand/explain your situation.
Thanks - Pawan

Background job - failing when file not on app server

Hi Experts,
I am facing an issue, while I am trying to run a program in background.
Let me explain u the situation.
My program runs in background and pick one file from predifined folder from application server and process that file. if file is not in the folder batch job goes into cancel status. but what i want if proposed file is not available then batch job will run and finished; it should not go into cancle status.
waiting for valuable inputs,
Prarthan.
Edited by: Julius Bussche on Feb 20, 2009 1:06 PM
Please use meaningfull subject titles

hi
below is my piece of code for application server.
thanks.
FORM application_server .
TYPE-POOLS: kcde.
DATA : lt_intern TYPE kcde_cells OCCURS 0 WITH HEADER LINE.
DATA wa_src01 TYPE string.
DATA: BEGIN OF wa_src0,
       material         LIKE bapi2017_gm_item_create-material,
       consumption_qty(13) TYPE c," like bapi2017_gm_item_create-entry_qnt,
       base_uom         LIKE bapi2017_gm_item_create-entry_uom_iso,
       movement_type    LIKE bapi2017_gm_item_create-move_type,
       cost_center      LIKE bapi2017_gm_item_create-costcenter,
       doc_date         LIKE bapi2017_gm_head_01-doc_date,
       post_date        LIKE bapi2017_gm_head_01-pstng_date,
       plant            LIKE bapi2017_gm_item_create-plant,
       storage_location LIKE bapi2017_gm_item_create-stge_loc,
       END OF wa_src0.
DATA : lt_src0 LIKE TABLE OF wa_src0.
DATA : file1 TYPE string.
DATA : tmp0(20). " type string.
DATA : intern1 TYPE kcde_intern.
DATA : tmp_date LIKE sy-datum.
path1 = path.
replace '.txt' in PATH1 with ''.
IF path IS INITIAL.
    path = '/usr/local/interface/globalone/SFA/SFA_WORK/SFA_'.
    tmp_date0(2) = sy-datum6(2). "date dd
    tmp_date2(2) = sy-datum4(2). "month mm
    tmp_date4(4) = sy-datum0(4). "year yyyy
    CONCATENATE path plant tmp_date '.txt' INTO path.
   concatenate path tmp_date into path1.
ENDIF.
file1 = path.
file_nm = path.
FILE_NM2 = PATH1.
OPEN DATASET file_nm FOR INPUT IN TEXT MODE ENCODING NON-UNICODE.
IF sy-subrc NE 0.
   MESSAGE e000(zmm002).
   EXIT.
ELSE.
    DO.
      READ DATASET file_nm INTO wa_src01.
      IF sy-subrc = 0.
         CLEAR wa_src0.
        REPLACE cl_abap_char_utilities=>cr_lf(1) IN wa_src01 WITH ''.
        SPLIT wa_src01 AT cl_abap_char_utilities=>horizontal_tab
                            INTO wa_src0-material
                                  tmp0
                                  wa_src0-base_uom
                                  wa_src0-movement_type
                                  wa_src0-cost_center
                                  wa_src0-doc_date
                                  wa_src0-post_date
                                  wa_src0-plant
                                  wa_src0-storage_location.
        SHIFT tmp0 LEFT DELETING LEADING '0'.
        wa_src0-consumption_qty = tmp0.
        APPEND wa_src0 TO lt_src0.
      ELSE.
        EXIT.
      ENDIF.
    ENDDO.
    CLEAR wa_src0.
    LOOP AT lt_src0 INTO wa_src0.
      REPLACE ',' IN wa_src0-consumption_qty WITH '.'.
      MOVE: wa_src0-material         TO wa_srcdata-material,
             wa_src0-consumption_qty TO wa_srcdata-consumption_qty,
             wa_src0-base_uom         TO wa_srcdata-base_uom,
             wa_src0-movement_type    TO wa_srcdata-movement_type,
             wa_src0-cost_center      TO wa_srcdata-cost_center,
             wa_src0-doc_date         TO wa_srcdata-doc_date,
             wa_src0-post_date        TO wa_srcdata-post_date,
             wa_src0-plant            TO wa_srcdata-plant,
             wa_src0-storage_location TO wa_srcdata-storage_location.
      APPEND wa_srcdata TO gt_srcdata.
      CLEAR wa_srcdata.
      CLEAR wa_src0.
    ENDLOOP.
ENDIF.
DELETE DATASET file_nm.
ENDFORM.                    " application_server

Background Job & Spool List Recipient not receiving all pages

I have a program that is run during our nightly cycle and is scheduled in SM36 with a spool list recipient designated for the report to be delivered to the user's SAP Inbox. The job completes successfully and creates a report that is over 100 pages. The user is only receiving 10 pages in their SAP Inbox. Is this a Basis system setting? Can we changes this on a per user basis?
Thanks,
Holly

Hi Holly,
it's sound like the <b>SAP-Note: 329537</b>
Symptom
If a batch job creates a spool and sends it to a recipients, only the first 1000 lines are sent.
Other terms
SAPOffice, spool list recipient
Reason and Prerequisites
For performance reasons, the output sent to SAPOffice is limited to 1000 lines.
Solution
If you wish to send spools longer than 1000 lines in Releases > 4.6B, proceeed as follows:
1. Apply the support packages or correction instructions mentioned in this note.
2. Create the following two entries in table TSPOPTIONS with transaction SE16:
              option: BTC_FIRSTLINE value: < desired value, probably 1>
              option: BTC_LASTLINE value: < desired value, e.g. 99999>
1. Call function module RSPO_OPTION_FLUSH with value NAME = '*'.
Please note that this change may impact performance, depending on the selected line interval.
In Releases < 4.6C or if you are not able to apply the support packages or corrections, you can accomplish this with a minor code change.
In program RSBTCRTE, change the parameter sent to the function module
RSPO_SPOOLJOB_TO_OFFICE as follows:
call function 'RSPO_SPOOLJOB_TO_OFFICE'
     exporting
      rqident              =
spo_list_id
         first_line
= 1
last_line            =
1000            "<<< Delete
        last_line            =
99999           "<<< Insert
        receiver
= recipient_object
         mail_title
= document_data-obj_descr
      exceptions

Create a Excel File in a Background Job

Hi SAP Gurus,
I am trying to create an Excel file using a background job but it is not possible.
In foreground mode i get a file.
Can someone give an explanation for that? Or someone have a workaround ??
Best Regards
João Fernandes

João,
If you have successfully demonstrated that SAP can write an output to an excel file, then it can do this in background as well as foreground. The problem is probably not with the fact that it is 'Excel', but that it is trying to write a file in the background to a destination file location that is unknown to the system.
Generally, without special setup, SAP software is unaware of most file locations that are outside of the SAP system itself. When you log on through the SAP Gui, the SAP back end can "learn" about certain additional file locations through your PC setup and the SAPGUI session. This 'knowledge' is lost as soon as you commit your program to a background process.
Talk to your Basis person, and tell him what you wish to do. This functionality is possible to do, but probably not in the way you are expecting.
Best Regards,
DB49

BAPI for Scheduling a background job

Hi all,
is there any bapi for scheduling a background job?
i mean can we do background job using bapi
If not how can we create a bapi for scheduling a background job.
Thanks & Regards,
Azhar

Hi,
Use following BAPIs for scheduling a job in background
BAPI_XBP_JOB_OPEN - This BAPI solves the first step in scheduling a job in the R/3 background processing system. You can create the job with this method.
Using additional BAPI calls BAPI_XBP_JOB_ADD_ABAP_STEP and BAPI_XBP_JOB_ADD_EXT_STEP, you can add job steps to the job.
With the BAPI call BAPI_XBP_JOB_CLOSE, you can finish defining the job and transfer it to the background processing system with the status Scheduled without start date.
You have execute the job with the BAPI calls BAPI_XBP_JOB_START_IMMEDIATELY or BAPI_XBP_JOB_START_ASAP.
I hope it would help you.
Regards,
Venkatram

Spool error for background job

Hi All,
I have scheduled one job in sap for a report.I have made a distribution list via tcode SO01.
I have given this distribution list to the SPOOL RECEPIENT section in SM 36.
The job is running successfully but is giving the following error and not sending emails to the distribution list.
The error is :-
"Spool list of step 1 could not be sent due to error 7".
Does anybody has any idea about this error?
Please help its a production issue.
Thanks in advance
Vivekanand Meghmala

Look at SAP note : 760838
Symptom
Background job spool lists are not sent.
Other terms
RSBTCRTE, RSPO_SPOOLJOB_TO_OFFICE, SO_DOCUMENT_SEND_API1
Reason and Prerequisites
1. The jobs in question have recipient references in table TBTCO but these have no equivalent in the Business Object Repository.
2. An error occurs when sending in the spool or in the Sapconnect layer.
Solution
This note does not provide a direct solution to the problem but it does provide a source code enhancement that you can use to create more trace information about the cause of the error. When you copy and execute a job with spool list recipients, trace messages are output when errors occur.
After implementing the correction instructions, use transaction SE91 to create the following message:
Message class: BT
Number: 347
Text: Spool list of step &1 could not be sent due to error &2.
In detail, the error numbers mean:
1 = Spool request does not exist (or no longer exists)
2 = Spool request does not contain any data
3 = Empty page area selected
4 = No authorization to send the request
5 = Access to the spool request is not possible
6 = Read error in the Temse layer
7 = Spool request could not be sent (sending problem)
8 = Incorrect request type
9 = Other

Different Subroutines in Background jobs and Dialog jobs

Hi guys,
I want to execute some subroutines when the program is running using a background job , and some other subroutines completely different when the user use dialog job ( program -> execute in background ) . I know that sy-batch = 'X' in both cases , but, there is something else to identify them ? , any ideas .
thank you .

It will be - he meant that they start the background job from SE38/SA38 not run it online.
SY-SLSET is a starter point for checking the variant used - dynamic variants are used when you don't pick one from the list. However, this would not help if the user picked a variant and then scheduled the job dynamically. Another option is to use function GET_JOB_RUNTIME_INFO in your program. Assuming your scheduled jobs are named differently, you can check for the condition by checking the name of the running job. Dynamically created jobs will have the program name as the job name.

Automatic Mail not getting generated through background job

Hi Experts,
We have set up a job variant with spool recipients. We are getting the automatic mail if the job is getting finished successfully. But we are not getting the automatic mail if the job is in cancelled status. Earlier we used to get the mail even if the job is in cancelled status. We are not sure if there is any setting which would restrict the automatic mail based on the job status.
Appreciate your help in this regard.
Thanks and Regards,
Ranjani.

Hi,
Just for a work around, try checking the SAP user inbox for the user who has scheduled the background job.
I don't there is any seperate configuration in Spool List Recipient for the canceled jobs. We need to confirm that the email ids provided in the Spool List recipient are correct and the background job creates a spool request even if it is canceled.
Also if possible try deleting the existing background job and create a new background job with the same parameters and valid email id's maintained in the Spool List recipient.
OR
Without deleting the existing background job, parallely create a new background job with the same parameters and valid email id's maintained in the Spool List recipient. If it works then delete the old background job.
Thanks
Harish

Background Job is not creating the List ID

Hello Experts,
I am scheduling a program as a Background Job. When I go and check the tables TBTCP & TBTCO, I see the List ID field (TBTCP-LISTIDENT or TBTCO-LISTIDENT) value as 0 .
Hence I am not able to get the Spool ID for this List.
Can anybody please let me know what is the problem?
Thanks a lot.

Hi,
See, if this piece of code can help you.
data:   sdate type sy-datum,
        stime type sy-uzeit,
        l_valid,
        ls_params like pri_params,
        l_jobcount like tbtcjob-jobcount,
        l_jobname like tbtcjob-jobname.
start-of-selection.
Get Print Parameters
call function 'GET_PRINT_PARAMETERS'
       exporting
            no_dialog      = 'X'
       importing
            valid          = l_valid
            out_parameters = ls_params.
Open Job
l_jobname = 'THIS_JOB'.
call function 'JOB_OPEN'
       exporting
            jobname = l_jobname
       importing
            jobcount = l_jobcount.
Submit report to job
submit <your_program_name
       via job     l_jobname
           number l_jobcount
       to sap-spool without spool dynpro
           spool parameters ls_params
              and return.
Kick job off 10 seconds from now.
sdate = sy-datum.
stime = sy-uzeit + 10.
Schedule and close job.
call function 'JOB_CLOSE'
       exporting
            jobcount = l_jobcount
            jobname   = l_jobname
            sdlstrtdt = sdate
            sdlstrttm = stime.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Mar 3, 2008 11:09 AM

Background job not updating data for some steps of program

We have created a custom program and submitting the standard program RPRCCC_READ_KR1025
which is used for conversion of AMEX credit card files.
Since this program can update data for 1 company id at a time,we have created a background job
for that program with 10 steps and 10 variants of data related to 10 different company codes.
when this job is executed it is not updating data for all the 10 files , sometimes it updates 5,7,etc...
If we execute the other files which didnt update in job manually they are getting updated.
All the files executed with that program can be seen in PRTA transaction.
Regards,
Gautham.
Edit: Solved.
Since the standard program updates the database every time with commit work
there should be some time until the next database update,so we can use wait command
after the submit statement which will do the trick.
Edited by: Gautham Vangaveti on Aug 5, 2010 7:20 PM

Hi,
I mean B(Sub Assembly)
Item Rollup Flag
A No
--B Yes
---B1 No
---B2 No
---B3 No
--C Yes
In this case when we run cost rollup by giving item A, Oracle will consider below structure.
A
--C
Regards,
Sarvottam.

Page-break in alv background job for alv output variant not coming correctl

Hi,
I have created an ALV grid report. When i run the report in background i get the output with correct page-break on FIELD1. Now when i run the report in background with an "ALV output variant" (its the ALV variant that controls the fields display in the output; this is not the program variant), i do not get the page-break on FIELD1. I have already build the sort criteria and using:
gs_sort-group = '* '.     "New-Page
Please let me know what could be reason for not getting the page-break in background when i am using the alv output variant and how do i correct this problem.
Regards,
Rakesh

Hello Everyone,
I have solved the problem. While running the program in background, we get the page-breaks when we use the below part of code in the sort catalogue with the condition that the program variant should not use any ALV layout variant.
gs_sort-group = '* '.     "New-Page
If you are using the ALV layout variant in the program variant then we can check the ROWPOS, COLPOS, and NO_OUT for that ALV layout variant and pass them along in the fieldcatalog table. You should be careful with not to pass the layout variant in the DISVARIANT. You can notice that i have cleared it and simply passing the program name into that.
*C-- Process separately for jobs running in Background. Actually
*C-- sortcat-group solves the problem only in Foreground. In background
*C-- when ALV layout variant is not selected then it works otherwise it
*C-- fails. So for background jobs we are reading the fieldcat and then
*C-- passing the same in the display FM.
IF sy-batch = 'X'.
    CALL FUNCTION 'REUSE_ALV_VARIANT_SELECT'
      EXPORTING
       i_dialog                  = ' '
       i_user_specific           = ' '
       i_default                 = ' '
*   I_TABNAME_HEADER          =
*   I_TABNAME_ITEM            =
        it_default_fieldcat       = gt_fieldcat
        i_layout                  = gs_layout
*   I_BYPASSING_BUFFER        =
*   I_BUFFER_ACTIVE           =
     IMPORTING
*   E_EXIT                    =
       et_fieldcat               = lt_fieldcat
*     et_sort                   = gt_sort[]
*   ET_FILTER                 =
*     es_layout                 = gs_layout
     CHANGING
       cs_variant                = gs_disvariant
     EXCEPTIONS
       wrong_input               = 1
       fc_not_complete           = 2
       not_found                 = 3
       program_error             = 4
       OTHERS                    = 5
    IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    CLEAR gs_fieldcat.
    LOOP AT gt_fieldcat INTO gs_fieldcat.
*C-- Transfer all position changes to gt_fieldcat from lt_fieldcat
      CLEAR ls_fieldcat.
      READ TABLE lt_fieldcat
            INTO ls_fieldcat
            WITH KEY fieldname = gs_fieldcat-fieldname.
      IF sy-subrc = 0.
        gs_fieldcat-row_pos = ls_fieldcat-row_pos.
        gs_fieldcat-col_pos = ls_fieldcat-col_pos.
        gs_fieldcat-no_out = ls_fieldcat-no_out.
        MODIFY gt_fieldcat FROM gs_fieldcat INDEX sy-tabix.
        CLEAR gs_fieldcat.
      ENDIF.
    ENDLOOP.
*C-- Clear the disvariant for the background job as it contains the ALV
*C-- layout varinat
    CLEAR gs_disvariant.
    gs_disvariant-report = 'ZGPPMP0001'.
Then pass gt_fieldcat to 'REUSE_ALV_GRID_DISPLAY'.
The reason i'm doing it this way is that when we pass the layout variant name, the contents in gt_fieldcat were getting modified.
One more thing i'd like to point out is that that, i tried to delete the fields with no_out = 'x'. Now when i ran the program in background with all the fields in sort catalog (suppose there are 2 fields field1 and field2) also in fieldcatalog it ran fine. In the next run in background i removed one of the fields in sort catalog from the fieldcatalog (delete the fields with no_out = 'x') and i got dump. Basically i had hidden field1 and so the code which was deleting fields with no_out = 'x' deleted this field from gt_fieldcat. So basically we should not delete fields with no_out = 'x'.
I was getting ABAP runtime errors    MESSAGE_TYPE_X in the following part of the standard code.
000310     LOOP AT CT_SORT INTO LS_SORT.
000320
000330       READ TABLE IT_FIELDCAT ASSIGNING <LS_FIELDCAT>
000340            WITH KEY FIELDNAME = LS_SORT-FIELDNAME BINARY SEARCH.
000350       IF SY-SUBRC NE 0.
     >         MESSAGE X000(0K).
000370       ENDIF.
000380
000390       LS_SORT-SELTEXT = <LS_FIELDCAT>-SELTEXT.
i have just mentioned this part because when i checked the forum many people were getting such errors "MESSAGE_TYPE_X". This could also be one of the reasons.

Certain Maintenance Plan not getting scheduled in the background job

Hi Gurus,
I am facing an issue here.
A weekly background job (RISTRA20) runs every weekend and schedules the maintenance plans.
But we have noticed that some maintenance plans are not getting scheduled. i.e no orders or schedule is getting generated.
When I run IP30 manually for these plans then the schedule gets generated and orders get called.
I have checked up the background job and it is running fine.
Also, i have noticed a similarity in all these plans which are not getting scheduled. There schedule has been restarted (through IP10) at somepoint or the other.
But i don't see any direct impact of this?
Can any of you provide some help on this?? Points will be rewarded.
Thanks and regards,
Nitin Saini

Hi Narender,
Thanks for replying.
The message number for 'Groups don't match' is ME303.
I think this does not have anything to do with the restart as i have done further investigation.
Whenever I run IP30 with sortfield input as AS02*, i get the error as mentioned above for a certain number of maintenance plans while the remaining plans get scheduled.
If i run IP30 for any other sort fields, it runs fine and i don't encounter the error
mentioned above.
If you send me ur email address, i could forward you screen-shots of the issue.

Background Job Not Reconnected After Offline Backup.

Hi all,
Background jobs which are scheduled before Databse Offline Backup are always cancelled. Reconnect WP does not happen even if following parameters are set.
We had set profile parameters in all Application Server like
   rsdb/reco_trials = 15
   rsdb/reco_sleep_time = 60
   rsdb/reco_add_error_codes = +3113 +3114 +1012 +1014 +1033 +1034 +1089 +1089 +1090 +1092
R3 Production server (640 Kernel, Patch 175 , SAP_BASIS 620 , SAP_APPL 470)
   Database : Oracle 9.2.0.6
SYSLOG Msg : SM21
<b>     Communication error, CPIC return code 020, SAP return code 497
       > CPI-C function: CMINIT(SAP)
       Operating system call gethostbyname failed (error no. 0 )
       Operating system call gethostbyname failed (error no. 0 )
       Communication error, CPIC return code 020, SAP return code 497
       > CPI-C function: CMINIT(SAP)
       Communication error, CPIC return code 020, SAP return code 497
       > CPI-C function: CMINIT(SAP)
       Communication error, CPIC return code 020, SAP return code 497
       > CPI-C function: CMINIT(SAP)                                   </b>
Thanks & Regards.
Naba

Looks like some Gateway error....though not sure...
Check Note 63347 - List: CPIC error codes and then u can try to troubleshoot further...

Background jobs in Ext. Classic not necessary

Similar Messages

Maybe you are looking for