Export to MS Access in background job

Hi,
is it possible in ABAP to export data to MS Access file (.mdb) in background job?
We have an idea to run external program in RFC mode in .NET - but it requires to have WIndows installed on external machine which is not good.
/BR / Thank you

>We have an idea to run external program in RFC mode in .NET - but it requires to >have WIndows installed on external machine which is not good.
Seems to me the only viable solution. Otherwise, create your output as a flat file written somewhere on the server (or where the server can see or ftp to), and have your Access app pick it up from there.
matt

Similar Messages

How to change file type when exporting a report with a background job

Hi,
I've set up a background job in SM36 to execute a SAP Query I've created, set to send the results as a file to an external email address. When it arrives the file is a .htm (and it seems to cut out after a few pages of data), but I'd like it to export as a .xls, .txt or .csv.
I've checked the job, the query and my user settings, but I can't find where the change the file extension used - can anyone please tell me how to do it?
Thanks,
Tim

Hi Shiva,
Can you please confirm where in SQ01/2 the file path information / settings are?
Thanks,
Tim

EXPORT - IMPORT in BACKGROUND JOB

Hello ABAP Gurus,
There are two programs I am using.
In 1st Program I am Exporting the Data to the ABAP Memory and then after that scheduling the second program in background from 1st Program through
1 ) JOB_OPEN
2 ) SUBMIT
3 ) JOB_CLOSE
Now I am trying to Import the data that is Exported in the second program which is scheduled in background.
But I am not able to Import it.
My question is that - Does EXPORT - IMPORT Statements works in such scenario when background job is scheduled.
As it is working fine if, I only submits and does not put in the Background JOB.
Looking forward for the answer.
Helpful answers will definately be awarded.
Thanks in Advance
Sudhanshu Garg

Hi Sudhanshu,
Export/import to memory uses ABAP memory which will not be accessible by the background job.
No need of creating the structures in dictionary
You can use the Table INDX for storing your data in the database.
See the link below for an example.
http://help.sap.com/saphelp_45b/helpdata/en/34/8e73a36df74873e10000009b38f9b8/content.htm

Background job stoppped in client export

Dear all,
I am trying to do client export form one SAP system to other SAP system. I sheduled the client export process in background job,it was running for long time.
Now when i check in sm50 the BGD process is been stopped , but in scc3 it shows its processing.
What is the necessary steps i need to start the job without stopping it.
Kindly Guide me.
Regards,
Rakesh

Hi ,
I resheduled the process, once again i am getting the same error.
My Background job is been stopped after few minutes.
The reason is RFC in background. But i had defined the RFC between the two systems clearly and my customizing and workbench transports is working fine.
Kindly guide me ,
Regards,
Rakesh.

Send/export the background job spool in Excel (in MHTML format) in ECC 6.0.

Hello All,
I have a requirement to send/export the background job spool in Excel (in MHTML format) in ECC 6.0. Please help.
Thank you.
Nalini

Hi Jigar,
Thanks for your response.
Anything is like download to desktop or email is fine. But in MHTML format.
We can download the ALV report in MHTML spreadsheet format when we run the program online. But the program is running for long time and going to dump.
So i scheduled it as background job and downloading the output in .HTML format. But user wants the spool/report output in .MHTML spreadsheet format.
I can write the code. Instead of changing the existing program I would like to know is there any way (from standard SAP) that I can get the background spool in MHTML spreadsheet format.
Thanks,
Nalini

Export of report/query to a file for background job runs

I have a requirement to automate the export of a report or query to a file so when a background job runs a new file is generated to the drive.
This cannot be a customized solution for 1 report, it must be able to adapt to other reports or queries as well.
Any help will be highly appreciated.
Thank you,
Thamina

Hi,
SAP have created a standard program RSTXPDFT4 to convert your Sapscripts spools into a PDF format.
Specify the spool number and you will be able to download the sapscripts spool into your local harddisk.
It look exactly like what you see during a spool display.
Please note that it is not restricted to sapsciprts spool only. Any reports in the spool can be converted using the program 'RSTXPDFT4'.
Regards,
Pavan

GRC Access Control 5.3: Background Jobs in RAR don't start

Hi experts,
I defined background jobs in RAR (configuration -> background jobs -> schedule jobs) for initial loading. and there are 3 background tasks defined. Unfortunately the jobs are never executed (jobtype= immediately).
Any help to execute the job would be appreciated.
Kind regards,
Max

Hello Max,
Here is what you should be checking :
1) Check if the Background job daemon is running :
URL - http://<server>: port/sap/CCBgStatus.jsp
2) Check if the analysis daemon manager is running :
URL - http://<server>:<port>/sap/CCADStatus.jsp
3) Follow SAP Notes 999785 and 1176262 .
This should help you resolve the issue
Harleen
SAP GRC RIG

Problems with background job

Hi,
I have problems when creating a job that is supposed to be run once in background. I use the common steps as described below. My problem is that the report is executed twice.
- First it is executed synchronously when the job is created
- Then it is executed in the normal job step as I want it to do
I don't want it to be executed the first time because it creates data!!!
Code:
CALL FUNCTION 'JOB_OPEN'
     EXPORTING
          jobname = w_jobid
     IMPORTING
          jobcount = w_jobnr
          sdlstrtdt = sy-datum
          sdlstrttm = sy-uzeit.
SUBMIT (p_prog)
WITH p_idocnr = p_idocno
           USER            p_user
           VIA   JOB       w_jobid
                 NUMBER w_jobnr
                 AND       RETURN.
CALL FUNCTION 'JOB_CLOSE'
     EXPORTING
          jobcount         = w_jobnr
          jobname          = w_jobid
          strtimmed        = 'X'
     IMPORTING
          job_was_released = w_jobrel.
Does anyone have a clue of what I should do to prevent this?
// Regards Hans

Hi again,
1. U are right.
2. It will happen if we use SUBMIT.
3. As per the help documentation,
    it will run the program in separate session,
   ( as soon as submit statement comes)
4. and run the INITIALIZATION event.
The VIA JOB addition also loads the program accessed in a separate internal mode when the SUBMIT statement is executed and the system performs all the steps specified before START-OF-SELECTION. This means the events LOAD-OF-PROGRAM and INITIALIZATION are triggered and selection screen processing is performed. If the selection screen is not processed in the background when VIA SELECTION-SCREEN is specified, the user of the calling program can eidit it and schedule the program accessed in the background request using the function Place in Job. If the user cancels selection screen processing, the program is not scheduled in the background job. In both cases, execution of the program executed is completed after selection screen processing and the system returns to the calling program due to the AND RETURN statement.
regards,
amit m.

Sending output to a printer in a background job

I did a quick search on this issue and found a few suggestions. One suggestion was to use something like this:
SUBMIT RSFLFIND ... TO SAP-SPOOL DESTINATION 'LT50'.
I looked at the SAP help for SUBMIT and it was quite helpful however it raised a few questions. The program that am writing will be run in the background. I want to create a simple report that will print at several different printers when it is done. Looking at the help section (specifically this part):
"The SUBMIT statement accesses an executable program rep. The executable program is executed as described under Calling Executable Reports.
The program name rep can either be specified directly or as the content of a character-like data object name. The data object name must contain the name of the program to be accessed in block capitals. If the program specified in name is not found, an irretrievable exception is generated.
The selscreen_options additions can be used to determine the selection screen for the program accessed and to supply it with values.
The list_options additions allow you to influence the output medium and the page size in the basic list for the program accessed.
You can schedule the program for background processing by specifying job_options. "
It seems like I would create a simple program like this:
DATA: number TYPE tbtcjob-jobcount,
      name TYPE tbtcjob-jobname VALUE 'JOB_TEST',
      print_parameters TYPE pri_params.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
    jobname          = name
IMPORTING
    jobcount         = number
EXCEPTIONS
    cant_create_job = 1
    invalid_job_data = 2
    jobname_missing = 3
    OTHERS           = 4.
IF sy-subrc = 0.
SUBMIT submitable TO SAP-SPOOL
                    SPOOL DESTINATION 'LT50'.
                    VIA JOB name NUMBER number
                    AND RETURN.
IF sy-subrc = 0.
    CALL FUNCTION 'JOB_CLOSE'
      EXPORTING
        jobcount             = number
        jobname              = name
        strtimmed            = 'X'
      EXCEPTIONS
        cant_start_immediate = 1
        invalid_startdate    = 2
        jobname_missing      = 3
        job_close_failed     = 4
        job_nosteps          = 5
        job_notex            = 6
        lock_failed          = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
ENDIF.
That will then call the background job and the output will go to the print spool. I have a few reservations about this. The print spool will not be determined until the background job. The background job creates sales orders and the material group, in the sales order, determines the printer that the final report will go to. Also, if this is the way to do it, do I just do simple write statements in the background job?

Hi,
Please try this ... perhaps it may help.
SUBMIT submitable TO SAP-SPOOL
                  SPOOL DESTINATION 'LT50'.
                  IMMEDIATELY 'X'           "Add here
                  VIA JOB name NUMBER number
                  AND RETURN.
OR
SUBMIT submitable TO SAP-SPOOL
                  SPOOL DESTINATION 'LT50'.
                  IMMEDIATELY 'X'           "Add here
                  WITHOUT SPOOL DYNPRO      "Add here
                  VIA JOB name NUMBER number
                  AND RETURN.
Regards,
Ferry Lianto

Run the Report as a Background job and Get the Output in Excel in Local PC

Hello Gurus,
I have one following requirement.
One should be able to run the report as a background job and it should be possible to get the report in Excel format, also when running the report in background. The excel report should have the same information and look as the current SAPreport.
Please provide some solution.
Any helpful answer get surely awarded.
Thanks a lot,
Varlanir

GUI_* WS_* Function In Background, CSV Upload
GUI_* and WS_* function modules do not work in background
When scheduling a job in the background the appropriate statement to read in your file is OPEN DATASET, and the file must be on the file system that the SAP server can see.
At anytime, a user can switch of the Personal Computers even though the job is still running in the background. Therefore GUI_* and WS_* function modules are not designed to work in that way, as they need to access your personal computer file.
To choose the correct download method to used, you can check the value of SY-BATCH in your code,
if it is 'X' use OPEN DATASET and if it is ' ' use WS_UPLOAD.
*-- Open dataset for reading
DATA:
dsn(20) VALUE '/usr/test.dat',
rec(80).
OPEN DATASET dsn FOR INPUT IN TEXT MODE.
IF sy-subrc = 0.
DO.
    READ DATASET dsn INTO rec.
    IF sy-subrc <> 0.
      EXIT.
    ELSE.
      WRITE / rec.
    ENDIF.
ENDDO.
ENDIF.
CLOSE DATASET dsn.
*-- Open dataset for writing
DATA rec(80).
OPEN DATASET dsn FOR OUTPUT IN TEXT MODE.
TRANSFER rec TO '/usr/test.dat'.
CLOSE DATASET dsn.
What is the difference when we use upload, ws_upload, gui_upload function modules?
UPLOAD, WS_UPLOAD, GUI_UPLOAD, are used in BDC concepts. ie., Batch Data Communication.
Batch Data Conversion is a concept where user can transfer the Data from non SAP to SAP R/3. So , in these various Function Modules are used.
UPLOAD--- upload a file to the presentation server (PC)
WS_UPLOAD----    Load Files from the Presentation Server to Internal ABAP Tables.
WS means Work Station.
This is used upto SAP 4.6 version.
GUI_UPLOAD-------    Replaces WS_UPLOAD. Upoad file from presentation server to the app server. From 4.7 SAP version it is replaced.
How to Upload csv file to SAP?
Common File Download Upload Questions:
How you upload the data from text file to sap internal table? From my knowledge its by upload or gui_upload.
How you download the data from sap internal table to text file?
How you upload the data from xls (excel) file to sap internal table how you download the data from sap internal table to xls(excel) file.
You can upload data from presentation server to an internal table using gui_upload. Use gui_download to download from internal table to flat file.
Use fm ALSM_EXCEL_TO_INTERNAL_TABLE to upload data frm excel.
Use function module GUI_UPLOAD
The FILETYPE refer to the type of file format you need: For e.g 'WK1' - Excel format , 'ASC' - Text Format etc.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    FILENAME                      = 'C:\test.csv'
   FILETYPE                      = 'ASC'
TABLES
    DATA_TAB                      = itab
EXCEPTIONS
   FILE_OPEN_ERROR               = 1
   FILE_READ_ERROR               = 2
   NO_BATCH                      = 3
   GUI_REFUSE_FILETRANSFER       = 4
   INVALID_TYPE                  = 5
   NO_AUTHORITY                  = 6
   UNKNOWN_ERROR                 = 7
   BAD_DATA_FORMAT               = 8
   HEADER_NOT_ALLOWED            = 9
   SEPARATOR_NOT_ALLOWED         = 10
   HEADER_TOO_LONG               = 11
   UNKNOWN_DP_ERROR              = 12
   ACCESS_DENIED                 = 13
   DP_OUT_OF_MEMORY              = 14
   DISK_FULL                     = 15
   DP_TIMEOUT                    = 16
   OTHERS                        = 17.

What is the spool, what is its role in background job scheduling

Hi,
I want to know what is meant by Spool request and spool number generated.
Tell about transaction SP01.
How it is linked to Background job scheduling.
thanks.
sam.

Hi,
Refer this link.
https://www.sdn.sap.com/irj/sdn/inf?rid=/library/uuid/7a5f4061-0a01-0010-c9bc-a4e4cb100438
About SP01.
Printing does not work in SAP. There is a printer definition for your local printer, but it does not work. Presuming that you use the program SAPLPD on your computer.
Boot your computer and start only the SAPLogon and the SAPLpd program.
Delete all of your old print jobs in the SAP system (Transaction SP01).Generate only one new print job.
Check that there is enough resource in your computer. Check the free memory (Win 3.1x) and the free disk space (The lists are temporarily saved on your disk).
Open the SAPLPD and read the print log in the window. The printer definition must correspond with the parameters shown here.
Check that the standard printer is on the same lpt (Win 3.1: Control panel, Printer) as defined for the printer (usually lpt1).
In Transaction SP01 read the protocol of your print job. Do not generate new print jobs! Wait till the SAP system changes the status of the print job.
If you can not find the print job in SP01 anymore, then the print job was successfully printed out. If it didn't come out on your printer and the SAPLpd didn't indicate an incoming print job, then the connection was realised with another PC. Then SAP printer definition you used, does not correspond with your computer.
Scheduling Background Jobs:
1.        Background jobs are scheduled by Basis administrators using transaction SM36.
2.        To run a report in a background, a job needs to be created with a step using the report name
and a variant for selection parameters. It is recommended to create a separate variant for each
scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.
company codes).
3.        While defining the step, the spool parameters needs to be specified
(Step-> Print Specifications->Properties) to secure the output of the report and help authorized users
to find the spool request. The following parameters needs to be maintained:
a.        Time of printing: set to u201CSend to SAP spooler Only for nowu201D
b.        Name u2013 abbreviated name to identify the job output
c.        Title u2013 free form description for the report output
d.        Authorization u2013 a value defined by Security in user profiles to allow those users to access
this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching
authorization value in their profiles will be able to see the output.
e.        Department u2013 set to appropriate department/functional area name. This field can be used in
a search later.
f.        Retention period u2013 set to u201CDo not deleteu201D if the report output needs to be retained for more
than 8 days. Once the archiving/document repository solution is in place the spool requests could
be automatically moved to the archive/repository. Storage Mode parameter on the same screen
could be used to immediately send the output to archive instead of creating a spool request.
Configuring user access:
1.        To access a report output created by a background job, a user must have at
least access to SP01 (Spool requests) transaction without restriction on the user
name (however by itself it will not let the user to see all spool requests). To have
that access the user must have S_ADMI_FCD authorization object in the profile with
SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).
2.        To access a particular jobu2019s output in the spool, the user must have
S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used
in the Print Specifications of the job (see p. 3.d above).
3.        Levels of access to the spool (display, print once, reprint, download, etc) are
controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least
BASE access (display).
On-line reports:
1.        Exactly the same configuration can be maintained for any output produced
from R/3. If a user clicks u201CParametersu201D button on a SAP Printer selection dialog, it
allows to specify all the parameters as described in p. 3 of
u201CScheduling background jobsu201D section. Thus any output created by an online report
can be saved and accessed by any user authorized to access that spool request
(access restriction provided by the Authorization field of the spool request
attributes, see p. 3.d of u201CScheduling background jobsu201D section).
Access to reportu2019s output:
1.        A user that had proper access (see Configuring user access above) can
retrieve a job/report output through transaction SP01.
2.        The selection screen can be configured by clicking u201CFurther selection
criteriau2026u201D button (e.g. to bring u201CSpool request name (suffix 2)u201D field or hide other
fields).
3.        The following fields can be used to search for a specific output (Note that
Created By must be blank when searching for scheduled jobu2019s outputs)
a.        Spool request name (suffix 2) u2013 corresponds to a spool name in p. 3.b in
u201CScheduling background jobsu201D section above).
b.        Date created u2013 to find an output of a job that ran within a certain date range.
c.        Title u2013 corresponds to spool Title in p. 3.c in u201CScheduling background jobsu201D
section above).
d.        Department - corresponds to spool Department in p. 3.e in u201CScheduling
background jobsu201D section above).
4.        Upon entering selection criteria, the user clicks the Execute button   to
retrieve the list of matching spool requests.
5.        From the spool list the user can use several function such as view the
content of a spool request, print the spool request, view attributed of the spool
request, etc. (some functions may need special authorization, see p.3 in
Configuring user access)
a.        Click the Print button   to print the spool request with the default attributes
(usually defined with the job definition). It will print it on a printer that was
specified when a job was created.
b.        Click the u201CPrint with changed attributedu201D button   to print the spool request
with the different attributes (e.g. changing the printer name).
c.        Click the u201CDisplay contentsu201D button   to preview the spool request contents. A
Print    and Download   functions are available from the preview mode.
Exporting the Contents of a Spool Request
Use
You want to export the contents of a spool request as a text file to the SAP GUI working directory or to a directory of your choice. The content of the spool request is downloaded as plain text without, for example, graphics, images, or specific fonts.
The following procedures are irrelevant for the PDF-based form printing integrated as of SAP Web Application Server 6.40, since the print data can be opened and stored as a PDF. See also Displaying and Printing PDF-Based Forms.
Procedure
Exporting to the SAP GUI Working Directory:
Choose Spool Request ® Forward® Export as Text.
The entire text is stored in your SAP GUI working directory in ASCII format.
A file of this type is named using the following pattern:
.txt
Example: ABC0000004327.txt
You require appropriate authorization for this function.
Exporting to a Directory of Your Choice:
With this method of exporting a spool request, the content of the spool request is first displayed and you then download the screen list as a text file to the directory of your choice.
       1.      Select the spool request to be exported and choose Display Contents.
       2.      In the case of SAPScript/Smart Forms documents, activate list display by choosing Goto.
       3.      Choose System ® List ® Save ® Local File.
       4.      Choose one of the available formats and confirm your choice.
       5.      Choose a directory and save the spool request.
By default, only the first 10 pages of a spool request are saved in a file. You can increase the number of pages to be saved by choosing Goto ® Display Requests ® Settings and making the desired entries in the Display Area group box.

Background job failing - ECC 6.0, Solution Manager 7.0

Dear All,
Four days back, I have installed the Solution Manager 7.0 and ECC 6.0 on
HPUX IA64 hardware with database as Oracle 10.2.0.2.0 (Unicode).
In both server, latest kernel patch has been applied.
The Support package versions are (both server):
KERNEL (Release 700)      146
SAP_BASIS           0014
SAP_ABA           0014
PI_BASIS(2005_1_700)      0014
ST-PI                0005
SAP_BW                0016
While checking the the jobs from SM37, in both the server,
I am observing that following jobs are always failing with
same reason:
SAP_COLLECTOR_FOR_PERFMONITOR
=============================
Date       Time     Message text                                                           Message class Message no. Message type
========== ======== ====================================================================== ============= =========== ============
15.05.2008 06:25:12 Job started                                                                 00           516          S
15.05.2008 06:25:12 Step 001 started (program RSCOLL00, variant , user ID BGDUSER)              00           550          S
15.05.2008 06:25:18 Clean_Plan:Cleanup of DB13 Plannings                                       DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:started by RSDBPREV                       on server gcbeccd     DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:Cleaning up jobs of system RD3                                  DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:finished                                                        DB6PM         000          S
15.05.2008 06:25:18 Database system not supported                                               S1           101          S
15.05.2008 06:25:36 ABAP/4 processor: DBIF_DSQL2_SQL_ERROR                                      00           671          A
15.05.2008 06:25:36 Job cancelled                                                               00           518          A
SAP_REORG_UPDATERECORDS
=======================
Date       Time     Message text                                                          Message class Message no. Message type
========== ======== ===================================================================== ============= =========== ============
14.05.2008 00:31:01 Job started                                                                00           516          S
14.05.2008 00:31:01 Step 001 started (program RSM13002, variant SAP&001, user ID BGDUSER)      00           550          S
14.05.2008 00:31:01 Reorganization of update date not allowed in batch                         15           100          A
14.05.2008 00:31:02 Job cancelled                                                              00           518          A
SAP_WP_CACHE_RELOAD_FULL
========================
Date       Time     Message text                                                                                Message class Message no. Message type
========== ======== ============================================================================================ ============= =========== ============
15.05.2008 00:30:11 Job started                                                                                00           516          S
15.05.2008 00:30:11 Step 001 started (program RWP_RUNTIME_CACHE_RELOAD, variant SAP&RELOAD_ALL, user ID BGDUSER)      00           550          S
15.05.2008 00:30:11 No component system chosen                                                                   URL_GEN_MSGS      031          E
15.05.2008 00:30:11 Job cancelled after system exception ERROR_MESSAGE                                                00           564          A
Please help to resolve this issue.
Thanks in advance.
Regards
Sudip Ghosh

Hi Markus,
Thanks for the reply.
Below is the dump:
======
======
Runtime Errors         DBIF_DSQL2_SQL_ERROR
Date and Time          15.05.2008 06:25:36
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error 3113 occurred in the current database connection "DEFAULT".
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel"
Database error code........: 3113
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_DSQL2_SQL_ERROR" " "
"RSORAVSH" or "RSORAVSH"
"FILL_DBVSE"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 15
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 1117216
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 695792
MM Free. 400816
User and Transaction
Client.............. 000
User................ "BGDUSER"
Language key........ "E"
Transaction......... " "
Transactions ID..... "482B8A4C89F0442BE10000000A0A049E"
Program............. "RSORAVSH"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAVSH" - in "FILL_DBVSE".
The main program was "RSORAVSH ".
In the source code you have the termination point in line 48
of the (Include) program "RSORAVSH".
The program "RSORAVSH" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BGDUSER"
Job Number..... 05251100
Source Code Extract
Line
SourceCde
18
INCLUDE STRUCTURE v_system_event_struc.
19
DATA: END OF v_system_event_tab .
20
21
check sy-dbsys(3) = 'ORA' .
22
23
Get the new snapshots
24
25
PERFORM fill_dbvse TABLES v_system_event_tab.
26
27
28
Get the old snapshots from database table MONI
29
30
startday = sy-datum - days_to_keep .
31
32
33
Save new data now (otherwise these data will be selected twice)
34
35
CONCATENATE 'SYSEVENT' sy-datum sy-uzeit INTO   monikey .
36
37
EXPORT sy-datum
38
sy-uzeit
39
v_system_event_tab
40
TO DATABASE moni(db) ID monikey .
41
42
*&      Form FILL_DBVSE
43
44
FORM fill_dbvse TABLES v_system_event_tab.
45
date = sy-datum .
46
time = sy-uzeit .
47
EXEC sql performing append_v_system_event .
>>>>>
select event,
49
total_waits,
50
total_timeouts,
51
time_waited * 10,
52
average_wait * 10
53
into :v_system_event_struc
54
from v$system_event
55
ENDEXEC .
56
ENDFORM.                               " FILL_DBVSE
57
58
59
*&      Form APPEND_V_SYSTEM_EVENT
60
61
FORM append_v_system_event.
62
v_system_event_tab-date = date .
63
v_system_event_tab-time = time .
64
65
MOVE-CORRESPONDING v_system_event_struc TO v_system_event_tab.
66
APPEND v_system_event_tab .
67
ENDFORM.                               " APPEND_V_SYSTEM_EVENT
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
16
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Report for Collecting Data from V$SYSTEM_EVENT Hourly
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080515
SY-UZEIT
062520
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
2 FORM         RSORAVSH                            RSORAVSH                               48
FILL_DBVSE
1 EVENT        RSORAVSH                            RSORAVSH                               25
START-OF-SELECTION
Chosen variables
Name
Val.
No.       2 Ty.          FORM
Name FILL_DBVSE
SY-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
V_SYSTEM_EVENT_STRUC
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222222222222222220000000000000000
0000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
%_SPACE
0
0
2
0
SY
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
No.       1 Ty.          EVENT
Name START-OF-SELECTION
SY-LDBPG
SAPDB__S
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
SY-DBSYS+0(6)
ORA
000
000
454
F21
SYST
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
V_SYSTEM_EVENT_TAB[]
Table[initial]
V_SYSTEM_EVENT_TAB
00000000000000                                                                ################
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333322222222222222222222222222222222222222222222222222222222222222220000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
SY-DATUM
20080515
00000000
00000000
33333333
20080515
DAYS_TO_KEEP
30
0001
000E
STARTDAY
00000000
00000000
00000000
33333333
00000000
MONIKEY
0000000000000000000000
0000000000000000000000
2222222222222222222222
0000000000000000000000
SY-UZEIT
062520
000000
000000
333333
062520
SYST-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
MONI-CLUSTR
0
00
00
MONI
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222220022000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ExecuteCall"
of the SAP kernel, in line 1190 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080515062520.
Internal call code.........: "[DBDS/NEW DSQL]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x40000000047b51e0 Z10abdbdserriPKtiS0_P9DS_HEADERS0_iPv + 0x470 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000003d777f0 Z11ExecuteCallv + 0x11f0 [dw.sapRD3DVEBMGS00]
(5) 0x4000000003d7e7b0 Z8abjdsqlv + 0x1b0 [dw.sapRD3_DVEBMGS00]
(6) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(7) 0x4000000003f53bc0 Z9abxeventPKt + 0x3c0 at abrunt1.c:339 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003d9f210 Z8abtriggv + 0x110 at abrunt1.c:58 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003d9ebe0 ab_run + 0xc0 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001caa820 N_ab_run + 0x20 at dymainstp.c:4739 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cb40f0 dynpmcal + 0x3f0 at dymainstp.c:2281 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001caf260 dynppai0 + 0xcb0 at dymainstp.c:1107 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001fb54e0 TskhLoop + 0x5520 at thxxhead.c:3945 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(20) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(21) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAVSH
0
30.03.2005
10:21:59
19456
E
1
Prg
SAPMSSY0
1
17.12.2007
15:41:05
92160
E
2
Prg
SAPMSSYD
1
12.09.2006
11:33:31
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
8192
E
4
Prg
RSDBRUNT
0
17.12.2007
16:04:40
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
12.09.2006
11:25:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Prg
SAPLSABE
11
09.09.2004
14:18:36
13312
E
12
Prg
SAPLSECU
12
17.12.2007
15:31:45
87040
E
13
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
14
Prg
SAPLSTUP
14
17.12.2007
15:29:58
74752
E
15
Prg
SAPLCNDP
15
11.09.2007
15:24:45
195584
E
16
Prg
SAPLSCNT
16
18.02.2005
14:16:06
30720
E
17
Prg
SAPSHDTV
16
05.01.2005
16:26:16
33792
E
18
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
19
Prg
SAPLOLEA
19
11.09.2007
11:17:30
96256
E
20
Prg
SAPLSGUI
20
17.12.2007
15:41:05
84992
E
21
Prg
SAPLSTTM
21
05.07.2005
13:10:18
69632
E
22
Prg
SAPLSBDC
22
17.12.2007
15:30:54
44032
E
23
Prg
SAPLSFES
23
17.12.2007
16:04:40
260096
E
24
Prg
SAPLTHFB
24
17.12.2007
15:41:05
394240
E
25
Typ
WPINFO
0
26.02.1999
14:49:01
6144
26
Prg
SAPLURFC
26
17.12.2007
15:37:35
22528
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
29
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
30
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
31
Typ
SYST
0
09.09.2004
14:18:12
31744
32
Typ
MONI
0
31.03.2004
16:41:21
5120
Directory of Application Tables
Name                                     Date       Time       Lngth
Val.
Program RSORAVSH
SYST                                     09.09.2004 14:18:12   00004612
\0\0\0\0\0\x0010\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
MONI                                       . .       : :     00002944
\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
71
PAR2
03
0000
0014
002B
RSORAVSH
37
73
PAR2
03
0000
0015
002D
RSORAVSH
37
75
PAR2
03
0000
0016
0026
RSORAVSH
37
77
00
0000
RSORAVSH
37
78
PERP
00
0002
RSORAVSH
44
79
PERP
1C
0000
RSORAVSH
44
80
PERP
04
0000
RSORAVSH
44
81
mvqk
10
0005
0044
04EC
RSORAVSH
45
83
mvqk
0C
0005
0054
052E
RSORAVSH
46
85
DSQL
00
0017
RSORAVSH
48
86
DSQL
01
0018
RSORAVSH
48
87
DSQL
04
0025
RSORAVSH
48
>>>>>
DSQL
16
0025
RSORAVSH
48
89
BRAN
05
0004
RSORAVSH
48
90
perf
00
000A
RSORAVSH
48
91
PERP
80
0000
RSORAVSH
48
92
BRAX
00
FFFC
RSORAVSH
48
93
DSQL
23
0000
RSORAVSH
48
94
ENDF
00
0000
RSORAVSH
56
95
00
0000
RSORAVSH
56
===========
===========
Please check and advise.
Also, I am trying to search for the note 6083 in market place, but not getting the same.
Please advise.
Thanks & Regards
Sudip

Simultaneous background jobs using the same BAPI issue

I scheduled 2 simultaneous background jobs on a custom program using the same BAPI (closing PM orders).
Run 1 to CLSD orders created on year 2001
Run 2 to CLSD orders created on year 2000
What happened was while run 1 was still active, run 2 encountered a dump and was cancelled.
Upon checking in ST22, dump was generated in CO_ZV_CONSISTENCY_CHECK.
Also, Run 2's dump happened when it encountered a data inconsistency for an order number being processed for Run 1.
Since the BAPI is being accessed at the same time by the two jobs, Is it possible that the commit work on run 1 could affect the processing for the Run 2, hence the data inconsistency?
Is this a buffer issue?
Additionally, no dump is encountered when Run 1 or Run 2 is run by itself.
I also encountered this issue before for creating Project and WBS using BAPI, but the solution we came up with was not to do parallel runs to avoid the error as this was a one time upload only.

If the second job is dependent on the 1st job, then use following logic which will let you know the status of 1st job. Once 1st job is completed, call JOB_OPEN of 2nd job.
ENDLESS loop till 1st job is completed
DO.
CALL FUNCTION 'BP_JOB_READ'
    EXPORTING
      job_read_jobcount     = w_jobcount
      job_read_jobname      = w_jobname
      job_read_opcode       = '20'
    IMPORTING
      job_read_jobhead      = wa_jobhead
    TABLES
      job_read_steplist     = i_jobsteplist
    EXCEPTIONS
      invalid_opcode        = 1
      job_doesnt_exist      = 2
      job_doesnt_have_steps = 3
      OTHERS                = 4.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
To Display the status text as per the status type
CASE wa_jobhead-status.
    WHEN 'S'. WRITE: / text-006. "'Scheduled'.
    WHEN 'R'. WRITE: / text-007. "'Released'.
    WHEN 'F'. WRITE: / text-008. "'Completed'.
    WHEN 'A'. WRITE: / text-009. "'Cancelled'.
    WHEN OTHERS.
ENDCASE.
IF wa_jobhead-status = 'F'.
exit.
ENDIF.
ENDDO.
PERFORM OPEN_2nd_JOb.

Problems creating background job for program (job open, submit and close)

Hi gurus,
im trying to start a background job using the FM BP_START_DATE_EDITOR to show the start date to the job or if it's imediate. this FM it's working fine, after call it im opening a job, submiting it and call the job close FM and the job close FM creates me the job.
The problem it's when i go to the sm37 to see the job status the job has been canceled, and the job log says that i have to give a start date to the job.
What i dont understand it's either the job is imediate or i choose a date to start the job always gives me this error...
Below goes my code,
any ideas will be rewarded
CLEAR: stdt_modify_type, stdt_output.
CALL FUNCTION 'BP_START_DATE_EDITOR'
       EXPORTING
            stdt_dialog                    = 'Y'
            stdt_input                     = stdt_input
            stdt_opcode                    = 14
       IMPORTING
            stdt_modify_type               = stdt_modify_type
            stdt_output                    = stdt_output
       EXCEPTIONS
            fcal_id_not_defined            = 1
            incomplete_last_startdate      = 2
            incomplete_startdate           = 3
            invalid_dialog_type            = 4
            invalid_eventid                = 5
            invalid_opcode                 = 6
            invalid_opmode_name            = 7
            invalid_periodbehaviour        = 8
            invalid_predecessor_jobname    = 9
            last_startdate_in_the_past     = 10
            no_period_data_given           = 11
            no_startdate_given             = 12
            period_and_predjob_no_way      = 13
            period_too_small_for_limit     = 14
            predecessor_jobname_not_unique = 15
            startdate_interval_too_large   = 16
            startdate_in_the_past          = 17
            startdate_is_a_holiday         = 18
            startdate_out_of_fcal_range    = 19
            stdt_before_holiday_in_past    = 20
            unknown_fcal_error_occured     = 21
            no_workday_nr_given            = 22
            invalid_workday_countdir       = 23
            invalid_workday_nr             = 24
            notbefore_stdt_missing         = 25
            workday_starttime_missing      = 26
            no_eventid_given               = 27
            OTHERS                         = 28.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    MOVE 'X' TO gv_flag.
ENDIF.
DATA jobname LIKE tbtcjob-jobname.
DATA jobcount LIKE tbtcjob-jobcount.
DATA job_release LIKE btch0000-char1.
DATA job_imediate TYPE c.
CLEAR: jobname, jobcount, job_release.
CONCATENATE 'MAPAEXEC' sy-uname sy-datum
               INTO jobname SEPARATED BY space.
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            jobname          = jobname
       IMPORTING
            jobcount         = jobcount
       EXCEPTIONS
            cant_create_job = 1
            invalid_job_data = 2
            jobname_missing = 3
            OTHERS           = 4.
IF sy-subrc <> 0.
    MESSAGE i003(zmapas).
    EXIT.
ENDIF.
SUBMIT z_mapa_execucao_orcamental
         VIA JOB jobname NUMBER jobcount
         WITH ano EQ ano
         WITH so_perio IN so_perio
         WITH so_date IN so_date
         WITH so_org EQ so_org
         WITH so_num IN so_num
         AND RETURN.
IF stdt_output-startdttyp EQ 'I'.
    CLEAR job_imediate.
    job_imediate = 'X'.
ENDIF.
CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
            calendar_id                 = stdt_output-calendarid
            event_id                    = stdt_output-eventid
            event_param                 = stdt_output-eventparm
            event_periodic              = stdt_output-periodic "?
            jobcount                    = jobcount
            jobname                     = jobname
            laststrtdt                  = stdt_output-laststrtdt
            laststrttm                  = stdt_output-laststrttm
            prddays                     = stdt_output-prddays "??
            prdhours                    = stdt_output-prdhours "?
            prdmins                     = stdt_output-prdmins "??
            prdmonths                   = stdt_output-prdmonths
            prdweeks                    = stdt_output-prdweeks "?
            predjob_checkstat           = stdt_output-checkstat
            pred_jobcount               = stdt_output-predjobcnt
            pred_jobname                = stdt_output-predjob
            sdlstrtdt                   = stdt_output-sdlstrtdt
            sdlstrttm                   = stdt_output-sdlstrttm
            strtimmed                   = job_imediate
            targetsystem                = stdt_output-instname
            start_on_workday_not_before = stdt_output-notbefore
            start_on_workday_nr         = stdt_output-wdayno
            workday_count_direction     = stdt_output-wdaycdir
       IMPORTING
            job_was_released            = job_release
       EXCEPTIONS
            cant_start_immediate        = 1
            invalid_startdate           = 2
            jobname_missing             = 3
            job_close_failed            = 4
            job_nosteps                 = 5
            job_notex                   = 6
            lock_failed                 = 7
            OTHERS                      = 8.
IF sy-subrc <> 0.
    MESSAGE i003(zmapas).
    EXIT.
ELSE.
    MESSAGE i004(zmapas) WITH jobname.
ENDIF.
Thanks in advance,
Best Regards
João Martins

Hello João.
In debug mode, check the value of variables you passed to parameters sdlstrtdt and sdlstrttm.
As aditional info, I usually achieve your goal without FM BP_START_DATE_EDITOR.
Check this code:
CALL FUNCTION 'JOB_OPEN'
      EXPORTING
           jobname          = w_jobname
      IMPORTING
           jobcount         = w_jobcount
      EXCEPTIONS
           cant_create_job = 1
           invalid_job_data = 2
           jobname_missing = 3
           OTHERS           = 4.
CHECK sy-subrc = 0.
CLEAR seltab_wa.
MOVE: t_jobs-param TO seltab_wa-selname,
t_processar-line+34 TO seltab_wa-low.
APPEND seltab_wa TO seltab.
seltab_wa-selname = 'P_LOJA'.
seltab_wa-low = t_processar-ficheiro+7(4).
APPEND seltab_wa TO seltab.
*** Submete o programa para o JOB
SUBMIT (t_jobs-repid)
WITH SELECTION-TABLE seltab
USER sy-uname
   VIA JOB w_jobname NUMBER w_jobcount
   AND RETURN.
*** Encerra o JOB
l_hora = sy-uzeit.
ADD 60 TO l_hora.
CALL FUNCTION 'JOB_CLOSE'
   EXPORTING
      jobcount           = w_jobcount
      jobname           = w_jobname
      sdlstrtdt            = sy-datum
      sdlstrttm           = l_hora
      targetserver       = w_servidor
   IMPORTING
      job_was_released     = l_liberado
   EXCEPTIONS
      cant_start_immediate = 1
      invalid_startdate    = 2
      jobname_missing      = 3
      job_close_failed     = 4
      job_nosteps          = 5
      job_notex            = 6
      lock_failed          = 7
      OTHERS               = 8.
Regards.
Valter Oliveira.

Submit RSEOUT00 as background job

Hi all,
Here is my requirement.There is a Z program from which RSEOUT00 program has to be called , so that it will change the Idoc status to '03'. I tried using Submit RSEOUT00..and return and also tried JOB_open and then SUBMIT rseout00 WITH docnum EQ p_idocno user sy-uname via job jobname number jobcount and return and then JOB_CLOSE .I checked SM37 also where i can see this job as finished..
I tried COMMIT WORK statement and also WAIT statement .
But still the idoc status wont change to '03' .
Can anyone plase advise on how to correct this .
Regards,
Sudheer

Hi,
I have created background job for RSEOUT00 and written the below code. It worked.
DATA: w_number           TYPE tbtcjob-jobcount,
           w_name              TYPE tbtcjob-jobname VALUE 'ZTEST_JOB'.
   CALL FUNCTION 'JOB_OPEN'
     EXPORTING
       jobname          = w_name
     IMPORTING
       jobcount         = w_number
     EXCEPTIONS
       cant_create_job = 1
       invalid_job_data = 2
       jobname_missing = 3
       OTHERS           = 4.
   IF sy-subrc = 0.
     SUBMIT rseout00 VIA JOB w_name NUMBER w_number AND RETURN.
     IF sy-subrc = 0.
       CALL FUNCTION 'JOB_CLOSE'
         EXPORTING
           jobcount             = w_number
           jobname              = w_name
           strtimmed            = 'X'
         EXCEPTIONS
           cant_start_immediate = 1
           invalid_startdate    = 2
           jobname_missing      = 3
           job_close_failed     = 4
           job_nosteps          = 5
           job_notex            = 6
           lock_failed          = 7
           OTHERS               = 8.
       IF sy-subrc <> 0.
       ENDIF.
     ENDIF.
   ENDIF.
Thanks,
Appanaboina

Export to MS Access in background job

Similar Messages

Maybe you are looking for