DYNPRO_SEND_IN_BACKGROUND when submitting a background job, when creating a

Hi.
We create sales orders via EDI. When certain sales orders are created, we execute user exists on the Sales Order save. During the User Exit, we submit/create (job_open_adk function, the submit command, and the job_close_adk function) a background job.
The background, is created and executed successfully, but we get 2
short dumps everytime.
The short dump is:
DYNPRO_SEND_IN_BACKGROUND
The description is:
Screen output without connection to user.
The short dump is for the user WF-BATCH.
I've used DEBUG and the shortdump occurs on the submit command.
submit zsd
to sap-spool
destination 'null'
immediately ''
keep in spool 'X'
without spool dynpro
and return
user l_user via job tbtcjob-jobname
number tbtcjob-jobcount
with p_vbeln = l_order
with p_ebeln = l_po
with p_uname = l_user.
Nothing should be displayed on the screen.
I used 'without spool dynpro' to prevent the 'Print Screen List' window
from appearing.
I've put this code into a TEST program. I ran the test program
myself. (under my ID) The program run perfectly. No
shortdump.
Similar code is used in other programs and it works perfectly - no shortdumps.
The short dump occurs when we use ALE/EDI to create a sales order.
The short dump has the ID WF-BATCH on it.
I'm guessing the problem is with the WF-BATCH ID. Are printer setting
missing on a Work Flow ID?
Any ideas why the 'without spool dynpro' parameter doesn't work for the
WF-BATCH ID?
I've tried searching OSS and I looked at the on-line help/documentation
on Submit. I saw a recommentation to use the
fuction 'GET_PRINT_PARAMETERS' to set all of the print parameters. I
tried this, but still got the short dumps.
Any suggestion on how I can run the Submit command and not get a short dump?
thanks,
Michelle

Hi,
Try this notes:
0100915 RSBDCREO: System hangs or parameters not effective
0377038 HR-CA-ALE: DYNPRO_SEND_IN_BACKGROUND for HR doc. d
0105165 Dump "DYNPRO_SEND_IN_BACKGROUND" in prog.SAPMSSY0
0169303 Warning messages displayed for settlement mass pro
0428489 VL10: Dump 'DYNPRO_SEND_IN_BACKGROUND' with backgr
[[http://forums.sdn.sap.com/thread.jspa?threadID=14875|http://forums.sdn.sap.com/thread.jspa?threadID=14875]]
Regards
HM

Similar Messages

ALV List only 80 Columns when runinning as background job

Hello Guys,
I have a Problem with an ALV List.
We use the FM REUSE_ALV_HIERSEQ_LIST_DISPLAY for a Document Journal.
When I run it in foreground it works fine. But when I view the spool in background the list makes a break at excactly 80 signs, but the line size should be about 120.
In the report the Line-Size is set correctly, even the print parameters seem to be ok. We are running it with X_65_255.
I saw that there are some SAP Notes to this topic, but on our release (SAP_BASIS 700) the notes are already implemented.
Has anyone a solution to this topic?
Thanks and regards
Roland

Try this.
[ALV List only 80 Columns when running in background job|https://forums.sdn.sap.com/click.jspa?searchID=25735042&messageID=5686003]

Configuration for creat auto background job to create outbound delivery

Dear Experts,
Kindly let me know where and how can I configure auto background job for creating outbound delivery, TO and Print picking list
Thanks in advance
Shetty

< Job for delivery creation:>
1. you can run tcode vl10batch to schedule a job with your own variant.
2. alternatively, you can directly schedule a job in SM36 -> program RVV50R10C, variant
When define variant for background delivery creation, please make sure:
- "Select rule" must be set to '2'.
- "F code profile" should be '5001' (Fcodes GET, PREPARE, SAMD should be included.)
<Job for TO creation>
1. Run tcode VL06p with your own varinat -> click button "create TO in background"
2. Alternatively, you can directly define a job in SM36. -> program name WS_MONITOR_OUTB_DEL_PICK.
<Job for printing pick list>
1. run tcode VL70 with your own variant -> goto menu bar / program / execute in background -> then a job is created.
2. Alternatively, you can schedule a job in SM36 -> program SD70AV4A.

Limit user from submitting a background job

Hi,
Is there a parameter that would limit the user from submitting a background job?
Regards,
Raquel

Read about Authorization object S_BTCH_JOB
http://help.sap.com/saphelp_nw70/helpdata/en/86/f7f3393bef4604e10000000a11402f/content.htm
Regards
Juan

Start background Job when another is finished (NOT with the JobSteps)

Hi guys,
i need your help.
I've already searched here in forum, but i wasn't able to find a good solution.
I have this problem.
I have a program that create a background job with the FM FM JOB_OPEN.. SUBMIT report with parameters .. JOB_CLOSE.
I want that if i run this report again (20 secs after for example) it does:
- Check if there is an already running Job with the same name (means with state 'R') (This task is simply, with a select on TBTO table)
- If it's found, it have to create a new job with the same name that starts automatically AFTER the first running job is finished (don't care about the end-state of the first job).
I've already tried with pred_jobcount & PRED_JOBNAME parameters of the JOB_CLOSE FM but it doesen't works!
The JOB_CLOSE, creates a job in Planned state. But when the first Job is finished, the second job(Planned) doesen't start automatically.
In this scenario, i CANNOT use endless loops (wait until the first job is finished and then submit the second) Job-steps (one job that contains multiple steps) events (i have to start only one job after the predecessor is finished), because this report could be run many times and each job should be collected like a "stack" (only when the first job is finshed the second "registered" should be started and so on, until the aren't more planned jobs).
<REMOVED BY MODERATOR>
Thx a lot for your help.
Andrea
Edited by: Alvaro Tejada Galindo on Jun 12, 2008 12:19 PM

Hi Veda
i can tell u but ... some reward points are very appreciated ....
I'm joking (of course)
Here the question:
I have a program (called A) that submit a new program (called B) with the JOB_OPEN .. submit JOB_CLOSE. The program B should start only if another program B (called before for example) is finished.
Here the solution.
I add a parameter (with no-display clausole) to the program B. In this parameter i pass to the program, the job number returned by the JOB_OPEN function.
When i create the JOB with the function, the "jobname" parameter is set with value 'G_DELIVERY' (Here u can change the name of the job as u want : this is the jobname that u see in SM37 transaction).
In the start-of-selection of program B i put a "waiting" procedure like this :
First i save a timestamp of system-date and system-time (called for example r_date and r_time)
select from table TBTCO all the jobs called "G_DELIVERY" with jobnumber <> from the jobnumber parameter (that means exclude itselfs) with status running ('R') -> that have startdate /starttime less than the r_date and r_time <- (this is the key of the selection that solve the problem).
if it is found (means there is another running job started before this one).
wait up to 60 seconds. "for example
repeat the selection.
endif.
When the job called before ends, this one programs exits from the loop and continues. If u submit more programs "B", they'll works like a stack.
I should say to u just one thing.... I solved my problem in another way (because i've changed the logic so this problem was no more) so i didn't implemented that logic, but it should works very good.
Try it and tell me!
Bye
Andrea

Some records are missing in the mail, when scheduled a background job.

There is a Z report, which will display some details from SD, MM , WM every day , and the same thing need to be mailed to the user through background Job.
Issue is that spool is correct and it is missing some records ( Billing due list ), even internal table have records and displayed in the spool , in the mail it says
No Entries Found.
Is there any chance of debugging background job.
Good thing is that when executed in foreground it is working fine. Both mail and report display.

EM_BODY = '4) VF04 -- Processing Billing document due list.'.
APPEND EM_BODY.
EM_BODY = ' '.
APPEND EM_BODY.
IF IT_FINAL3[] IS INITIAL.
    EM_BODY = '        No Entry Found'.
    APPEND EM_BODY.
    EM_BODY = ' '.
    APPEND EM_BODY.
ELSE.
    CONCATENATE 'Delivery No' 'Created By' 'Created On'
                 'Reason' INTO HEAD SEPARATED BY '     '.
    EM_BODY = HEAD.
    APPEND EM_BODY.
    EM_BODY = ' '.
    APPEND EM_BODY.
    CLEAR V_TEXT.
    CLEAR ITEM.
    LOOP AT IT_FINAL3.
      CONCATENATE IT_FINAL3-VBELN IT_FINAL3-ERNAM IT_final3-ERDAT
                  IT_FINAL3-RESO INTO ITEM SEPARATED BY '     '.
      V_TEXT = ITEM.
      EM_BODY = V_TEXT.
      APPEND EM_BODY.
    ENDLOOP.
    EM_BODY = ' '.
    APPEND EM_BODY.
ENDIF.
This is the part where it is failing, where it_final3[] is initial.
but whereas in the spool i can view those records.

Report program when run in background job getting cancelled immediately

Hi
When i run a program in foreground i am able to see the output. But when run in background not able to run the job successfully. The job is getting cancelled immediately.
I am using the below function module for output display. Should i need to pass any parameters in the below function module so that i can run the program in background successfully.
CALL METHOD DETAIL_GRID->SET_TABLE_FOR_FIRST_DISPLAY
      EXPORTING
        IS_LAYOUT         = IS_LAYOUT
        I_SAVE            = 'A'
        IS_VARIANT        = GS_VARIANT
      CHANGING
        IT_FIELDCATALOG   = IT_FIELDCATALOG
        IT_OUTTAB         = BLOCKED_STOCK_TAB_ALV[].
Please suggest.
Thanks and regards
Rajani Yeluri

Hi Rajani.
ALV require the DRYPOR(screen) for display but incase you run in back ground which have to write to spool but in spool we can only write in format of LIST REPORT not inter-active report like ALV. That why
system cancelled your process immediately.
Hope it helps.
Sayan.

Force Dialog in ATP when run in Background Job

Hi gurus,
Can we set the ATP to always show even if in Background Job? I have a requirement to run a program in background job and set the confirmed qty to 0. In foreground the process is ok (the ATP screen shows up so my BDC is correct). But when I run the program in background, I have an error in my BDC because the screen for the ATP does not show up.
Best regards,
Andre
Edited by: Andre Reforma on Jun 5, 2009 9:28 AM

chdir("..") Err#13 EACCES [file_dac_search]
I suspect that an underlying mount point has improper file access.
Unmount the ZFS filesystem (either /zones or /zones/test) and check the perms on the directory that it's mounted on.
Darren

Different result when running as background job

Hi,
We got a program which has a selection screen with a couple of select-options.
When we start this programm with a specified variant, it proceeds to a result screen. If we click back now (to the selection-screen) and run the programm with the exactly same settings again, one select-option is getting ignored and therefore we get incorrect results.
This happens only, if you go back from the result screen and excecute it again from the selection screen or if we start it as a background job.
If you exit the programm completely and restart it, the results are correct again.
It makes no sense to post any code snippets here, since the program is very complex. I just can't imagine any reason, why the select-option is sometimes getting ignored.
Does anyone have an idea?
Thanks in advance.
Regards,
Tobi

oh well it DOES explain it.
just think of following select:
Select *
from vbap
into ls_vbap
where vbeln not in lr_vbeln.
if lr_vbeln is not cleard you will run into problems maybe.
anyway, may it be that somewhere in coding you are manually modifying your select option?
It´s just an internal table of type range, so have a look there.

Getting Message as "File not open", when I ran background Job

Hi,
I developed a Migration Program, Which reads the data from Application serever and procced with further process in back ground mode.
Same program is workind fine in Development System in Back ground mode (SY-BATCH = 'X', Scheduled a batch Job). So I transported to Quality system.
Now When I run the program in background mode (SY-BATCH = 'X', Scheduled a batch Job), getting Message as "File is not Open" at Quality system. So I debugged the Batch job through "JDBG", and found file opening and reading the content sucessfully.
But its not working without debugging mode and getting message as "File not open".
Is there any Authorizations required for background mode (without debugging).
So can you please help me on this how to solve this issue.

Try this code:
DATA: PATH_NAME(80) TYPE C,
        LV_FILENAME TYPE STRING.
DATA: LW_XSTRING         TYPE XSTRING,
        X_LEN             TYPE I.
DATA: FILE_AUTH_ERR TYPE REF TO CX_SY_FILE_AUTHORITY,
        FILE_OPEN_ERR TYPE REF TO CX_SY_FILE_OPEN,
        FILE_OPEN_MODE_ERR TYPE REF TO CX_SY_FILE_OPEN_MODE,
        FILE_CLOSE_ERR TYPE REF TO CX_SY_FILE_CLOSE,
        FILE_CONVERSION_ERR TYPE REF TO CX_SY_CONVERSION_CODEPAGE,
        FILE_TOO_MANY_ERR TYPE REF TO CX_SY_TOO_MANY_FILES,
        MESS TYPE STRING,
        W_TEXT TYPE STRING.
DATA: L_RC TYPE INT4.
concatenate pathname lv_filename into lv_filename.
TRY.
      OPEN DATASET LV_FILENAME FOR INPUT IN BINARY MODE MESSAGE MESS.
    CATCH CX_SY_FILE_OPEN_MODE INTO FILE_OPEN_MODE_ERR.
      W_TEXT = FILE_OPEN_MODE_ERR->GET_TEXT( ).
      L_RC = 1.
    CATCH CX_SY_FILE_AUTHORITY INTO FILE_AUTH_ERR.
      W_TEXT = FILE_AUTH_ERR->GET_TEXT( ).
      L_RC = 2.
    CATCH CX_SY_CONVERSION_CODEPAGE INTO FILE_CONVERSION_ERR.
      L_RC = 3.
      W_TEXT = FILE_CONVERSION_ERR->GET_TEXT( ).
    CATCH CX_SY_TOO_MANY_FILES INTO FILE_TOO_MANY_ERR.
      L_RC = 4.
      W_TEXT = FILE_TOO_MANY_ERR->GET_TEXT( ).
    CATCH CX_SY_FILE_OPEN INTO FILE_OPEN_ERR. "File already open
      L_RC = 5.
      W_TEXT = FILE_OPEN_ERR->GET_TEXT( ).
ENDTRY.
IF L_RC = 0.
    L_RC = SY-SUBRC.
ENDIF.
IF L_RC <> 0 OR SY-SUBRC NE 0.
Issue Error message in open file.
   CONCATENATE MESS 'Open dataset failed' w_text INTO MESS SEPARATED BY SPACE.
   message Exx(yyy) with mess.
      ELSE.        "file exists and can be opened
ENDIF.

Changing the file format of spool output when scheduling a background job.

Hello Experts,
I have an issue. It is related to Spool output format. I created a job for one report program for which the output is a list output. I have added one recipient in the 'Spool list recipient' while creating the job SM36. After the job is finished the spool output is sent to the recipient mail id as .htm format as an attachment. But the attachment should be excel sheet or text file. No coding in the program should be used to convert the file format. Only settings in the spool while creating job should be manipulated. Please help me in solving this issue.
Regards.

Hi Sunil,
You can use the logic for converting spool to PDF using program : RSTXPDFT4 . Alternatively you can use FM: CONVERT_ABAPSPOOLJOB_2_PDF . In this FM you need to pass the Spool id .
u can make use of these FM's SO_DOCUMENT_SEND_API1
SO_NEW_DOCUMENT_SEND_API1
Check out the following wiki:
https://wiki.sdn.sap.com/wiki/display/Snippets/ConvertsspoolrequestintoPDFdocumentand+emails
hope this will use full to you.
Thanks!!

Missing AW Maintenance Details When Submitting to Oracle Job Queue

Is there a way to know the number of added/deleted members or the processed/ rejected records of a dimension/cube maintenance that was submitted to the Oracle Job Queue?
The following is the log of my recent maintenance task that was submitted to the Oracle Job Queue:
18:59:03 Attached AW OLAP_TEST.AW_TEST in RW Mode.
18:58:27 Completed Build(Refresh) of OLAP_TEST.AW_TEST Analytic Workspace.
18:58:27 Finished Parallel Processing.
18:58:21 Running Jobs: AWXML$_2534_1. Waiting for Tasks to Finish...
18:58:21 Started 1 Finished 0 out of 1 Tasks.
18:58:21 Running Jobs: AWXML$_2534_1.          Usually, there would be a line in the XML_LOAD_LOG table where the added/deleted members or processed/rejected records can be found. In this case, there is none.

Usually the entries you want are before these lines (time-wise). The parallel processing only handles aggregating fact partitions in parallel, not loading the base level data.

Background job to create/update vendors.

Hello,
We need to create/update vendor records for travel expenses reimbursement. So far we try to create it as background scheduled job for transaction PRAA, but in fact PRAA transaction only creates batch input session and donu2019t process it. In fact we end up with out updates for vendors.
Usual manual routine is:
Call PRAA to create batch input session for create/update vendor records from HR Master data.
Call SM35 to process creates batch input session.
We would like to avoid this manual routine and run it on background as scheduled job. Is it possible? How it possible to combine this 2 processes?
BR, Maija

the process can only be run in a two step process.
You could have a BASIS program that automatically processed all sessions in SM35 with a certain Batch name, this will remove the manual step, however someone will still need to monitor it, as there may be errors.

Submitting a updates in a prog to a background job

Hello everyone,
I am generating a alv report with production orders.In the toolbar i created a button for updating data.When i select some production orders in the alv list and select the button then transaction co02 is called and some updates are done.I done that the updating by using bdc recording and the updates are working fine.
But my problem is
1. when the user selects the updates button in the toolbar these updates should take place via. a background job.
2. Before submitting the background job the program needs to check if a version of a prog is running,the check should look for the prog name and the triggering user, if a match is found the user should receive a error message.
3. If a match is not found then the background job should be scheduled immediately and should be created with a name of prog name and the triggering user.
I need to these steps,can anyone please give me a sample code for this.
Thank you.
dp.

The approach I would probably take for this would be:
1. Write the records that need processing to a "Z" table from the ALV, and delete these back out (or mark as "done") once processed by the batch job.
2. It is possible to check for a batch job name and its status, but I've usually found an easier and more reliable way is to use a lock object to check this e.g. you could use and existing object such as ESRDIRE with a dummy lock argument such as 'CO02_IS_LOCKED' . The batch job should contain code to set the enqueue... if this enqueue fails it means another job / program is already processing the requests so this instance can stop, otherwise the batch program can continue the CO02 processing. In other words, you are creating a doorway through which only one instance of the job can pass at a time.
3. A couple of easy ways to do this are (a) event triggered jobs, wherein you define the job and have it fire up when an event is raised (e.g. by calling function BP_EVENT_RAISE) or (b) use the SIMPLE_BATCH_JOB_SUBMIT (which calls the JOB_OPEN, JOB_SUBMIT, JOB_CLOSE functions for you).
Jonathan

Submitting a update in a porg to a background job?

Hello everyone,
I am generating a alv report with production orders.In the toolbar i created a button for updating data.When i select some production orders in the alv list and select the button then transaction co02 is called and some updates are done.I done that the updating by using bdc recording and the updates are working fine.
But my problem is
1. when the user selects the updates button in the toolbar these updates should take place via. a background job.
2. Before submitting the background job the program needs to check if a version of a prog is running,the check should look for the prog name and the triggering user, if a match is found the user should receive a error message.
3. If a match is not found then the background job should be scheduled immediately and should be created with a name of prog name and the triggering user.
I need to these steps,can anyone please give me a sample code for this.
Thank you.
dp.

The approach I would probably take for this would be:
1. Write the records that need processing to a "Z" table from the ALV, and delete these back out (or mark as "done") once processed by the batch job.
2. It is possible to check for a batch job name and its status, but I've usually found an easier and more reliable way is to use a lock object to check this e.g. you could use and existing object such as ESRDIRE with a dummy lock argument such as 'CO02_IS_LOCKED' . The batch job should contain code to set the enqueue... if this enqueue fails it means another job / program is already processing the requests so this instance can stop, otherwise the batch program can continue the CO02 processing. In other words, you are creating a doorway through which only one instance of the job can pass at a time.
3. A couple of easy ways to do this are (a) event triggered jobs, wherein you define the job and have it fire up when an event is raised (e.g. by calling function BP_EVENT_RAISE) or (b) use the SIMPLE_BATCH_JOB_SUBMIT (which calls the JOB_OPEN, JOB_SUBMIT, JOB_CLOSE functions for you).
Jonathan

DYNPRO_SEND_IN_BACKGROUND when submitting a background job, when creating a

Similar Messages

Maybe you are looking for