QA Approval - importing queue with background jobs

Hi all,
I have activated the QA approval in my system and it all works fine. I have scheduled a background job via STMS to import the whole test system buffer each day and this works fine too. Now I want to schedule a background job to import the production buffer automatically too. This would allow us to have all approved transports automatically imported once a day (as QA approval is activated only approved transports would be imported).
Sounds simple, but with QA approval the production buffer displays approved and non-approved requests, so the background job fails as not all transports in the buffer are in the correct status.
Any suggestions on how I can get around this problem?
Thanks
Claire.

Hello Claire,
This issue has been described in SAP Note 313991. please check.
Regards,
Debasis

Similar Messages

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.

Problem with background job using SUBMIT under different user

Hi All,
I am submitting a background job under different user name. I am submitting this job by using JOB_OPEN , SUBMIT report and JOB_CLOSE. But submit statement is returning sy-subrc 8, becuase of this the job_close is failed. Can you please help me to solve this problem.
Thanks in advance.
Tjgupta

Hi,
The user is having all authorizations. is there any difference with user types?
This user is having user type " as communication data".
Thanks,
Tjgupta

Scheduling of process chain with background job

Hello All,
I have scheduled the process chains through background jobs. I have copied the meta chain and created seven background jobs that is from Monday till sunday. The problem is most frequently the job gets cancelled with the message
Process CHAIN, variant PAA1_GS001 is not scheduled waiting for event RSPROCESS 44NRPDWZ7CQUJ92ATDTY6368H.
This is the variant for the next process after the start process. I tried by giving merge active versions, but one day the background job runs fine , but the next day it gets cancelled.
If anyone has faced this issue before kindly let me know.
Regards,
Karthik.

Hi,
It seems to be there may be in probelm in Varients, so create a separate Varient for each PC and then activate the PC and execute.
Thanks
Reddy

Issue with background job--taking more time

Hi,
We have a custom program which runs as the background job. It runs every 2 hours.
Itu2019s taking more time than expected on ECC6 SR2 & SR3 on Oracle 10.2.0.4. We found that it taking more time while executing native SQL on DBA_EXTENTS. When we tried to fetch less number of records from DBA_EXTENTS, it works fine.
But we need the program to fetch all the records.
But it works fine on ECC5 on 10.2.0.2 & 10.2.0.4.
Here is the SQL statement:
EXEC SQL PERFORMING SAP_GET_EXT_PERF.
SELECT OWNER, SEGMENT_NAME, PARTITION_NAME,
         SEGMENT_TYPE, TABLESPACE_NAME,
         EXTENT_ID, FILE_ID, BLOCK_ID, BYTES
   FROM SYS.DBA_EXTENTS
   WHERE OWNER LIKE 'SAP%'
   INTO
   : EXTENTS_TBL-OWNER, :EXTENTS_TBL-SEGMENT_NAME,
   :EXTENTS_TBL-PARTITION_NAME,
   :EXTENTS_TBL-SEGMENT_TYPE , :EXTENTS_TBL-TABLESPACE_NAME,
   :EXTENTS_TBL-EXTENT_ID, :EXTENTS_TBL-FILE_ID,
   :EXTENTS_TBL-BLOCK_ID, :EXTENTS_TBL-BYTES
ENDEXEC.
Can somebody suggest what has to be done?
Has something changed in SAP7 (wrt background job etc) or do we need to fine tune the SQL statement?
Regards,
Vivdha

Hi,
there was an issue with LMT's but that was fixed in 10.2.0.4
besides missing system statistics:
But WHY do you collect every 2 hours this information? The dba_extents view is based on really heavy used system tables.
Normally , you would start queries of this type against dba_extents ie. to identify corrupt blocks and such:
SELECT owner , segment_name , segment_type
        FROM dba_extents
       WHERE file_id = &AFN
         AND &BLOCKNO BETWEEN block_id AND block_id + blocks -1
Not sure what you want to achieve with it.
There are monitoring tools (OEM ?) around that may cover your needs.
Bye
yk

Print the order with Background Job

Hi Gurus,
I have to print the order on button click in a report.
i have done the coding and passing the parameters to a stahndard program on submit.
but problem is that order is going to spool but not printing the order.
As batch job not supporting the LOCL,please suggect the alternative to achieve the print.
Br,
Surya

Hi Lokesh,
Thanks for your quick reply.
i am using the below code for printing the order with batch job on clicking the button in my report.
     DATA: NAME TYPE TBTCJOB-JOBNAME.
DATA: NUMBER TYPE TBTCJOB-JOBCOUNT.
DATA: PRINT_PARAMETERS TYPE PRI_PARAMS.
NAME = 'ORDER_PRINTING'.
CLEAR: RANGE1.
*REFRESH: range.
RANGE1-SIGN = 'I'.
RANGE1-OPTION = 'EQ'.
RANGE1-LOW = 'BA00'.
RANGE1-HIGH = 'ZBA1'.
APPEND RANGE1 TO RANGE.             .
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 SD70AV1A WITH RG_KSCHL IN RANGE
WITH RG_VBELN IN ORDER_TAB
TO SAP-SPOOL
SPOOL PARAMETERS PRINT_PARAMETERS
WITHOUT SPOOL DYNPRO
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.
Please suggest where should i give the printer name.
fyi.. i am trying to pass the same LOCL name to the job with the FM- GET_PRINT_PARAMETERS with destinamtion 'LOCL'
Br,
Surya

Virsa CC 5.1: Issue with Background Job

Dear All,
I almost finished configuration of our new Compliance Calibrator dashboard (Java stack of NW'04). But, unfortunately, have an issue with SoD analysis now.
Using SAP Best Practice recommendations, we have uploaded all functions, business processes and risks into CC database, and then successfully generated new rules (there are about 190 active ones in our Analysis Engine).
I also configured JCo to R/3 backend and was able to extract the full list of our users, roles and profiles. But somehow background analysis job fails.
In job history table I see the following message: "Error while executing the Job:null", and in job log there is an entry, saying that "Daemon idle time longer than RFC time out, terminating daemon 0". But it's quite strange, as we use default values: RFC Time Out = 30 min, and daemons are invoked every 60 seconds.
Please, advise whether you had similar issues in your SAP environment and, if yes, how you resolved them.
Thanks,
Laziz

Hi Laziz
I am now just doing the first part of CC. May I know your details in how to configured Jco To R/3 Backend? Do you need to create any SM59 for connection T in R/3? If yes, I am lacking of the details to do that if you could help? Thank you.
Regards
Florence

Problem with background job schedule

Hi friends,
How to schedule more than one data loading jobs in backround??
When i try to schedule the second job,the first scheduled job is getting overwritten,and only this job is active.
I tried in infopack,scheduler...
How to overcome this???
Regards
sudhakar

Hello Ragu,
How r u ?
Use Process Chains for this multiple Job Scheduling.
I think u r teying to schedule the same InfoPackage !
Could u elobrate ur issue ?
Best Regards....
Sankar Kumar
+91 98403 47141

Scheduled TMS_ # TMS_TP_IMPORT background jobs fail with error code 0232

Is anyone else having the problem we've just encountered since upgrading to ECC 6.0 and CRM 2007, where once setting up the automatic import ALL background jobs, to have all of the Transport Change Requests imported into the Q-Prod testing systems automatically, fail after several successful runs?
After setting up the automatic import background job to run every 15 minutes, the first few run successfully (importing any transports as it should), then the transports stop being imported.
The background jobs continue to run, but have the following in the job log overviews CRM 2007 - "Could not start transport control program tp". R\3 ECC 6.0 - "Transport control program tp ended with error code 0232".
Only by deleting the background job and recreating it (or manually importing) from STMS, can the transports continue to be imported. Although I have noticed that there are multiple tp.exe processes started, which need to be deleted before the STMS and TMS Background jobs work again.
The:
   DB is SQL Server 2005
   disp+work is at version 7000.150.14.48855
   R3Trans is at version 7000.149.14.47907
   tp is at version 7000.144.14.39594
Any suggestions on how to cure this for good?

Thanks All
FYI
SAP first suggested the following notes: 19466, 1150361, and to add a Startup profile parameter rfc/use_gwstart = 1. Which was only partially successful.
I guess it had more to do with RFC processes hanging than it did with the tp, which was fixed in a later kernel patch level.
I've upgraded the kernel to the latest (70000.181.0.0) and my problem was fixed.
Ken

Background Job is not running in KW

Hi All,
I have problem with background job.
I am working on Knowledge warehouse server.
And I am scheduling background job to upload contents.
But background job is not finishing at proper time.
And while displaying trace it is giving following error.
ERROR => BtcCleanUp: BtcLgAp-call failed (rc = 4) [btcjcntl.c   1251]
Please help me to resolve this.
Regards,
Payal patel

Hi Juan,
I have tried with process as well as instance restart.
It didn't help me.
Hi Santosh,
Following is the part of trace file (level -2).
First line shows error.
Tell me if you need any other log file.
L *** ERROR => BtcCleanUp: BtcLgAp-call failed (rc = 4) [btcjcntl.c   1251]
M read msgserver-list from MBUF
M ThSemRq (4, 1, 0, 0)
M ThSemRel (4, 1)
M ThSetBtcName: found batch server sapbl4_KW7_00
M ThScheduler2: server name: sapbl4_KW7_00
M ThISendMsg: send message (5) to server (wp) with name >sapbl4_KW7_00                           <
M ThISndName: send to name: >sapbl4_KW7_00                           <
M ThISend: (tm/type/info = 10/0x2000/0x0, mode_deleted=0)
M ThRqOutCheck: o.k.
M abap strategy ROLL / O.K.
M ThNewWpStat (type=0x2000, task_switch=0, inline_hold=0, hand_shake=0, debug=0, ..)
M ThNewWpStat: new state of T10/M0 = 0x3c
M ThISend: new wp stat: 0x0
M Adresse   Offset Message by name (one way)
M -
M 06C60600 000000 00000000 05000000 255f4556 454e545f |........%_EVENT_|
M 06C60610 000016 53434845 44554c45 52202020 20202020 |SCHEDULER       |
M -
M ThMkReq: send output to canceled mode
M make DISP owner of wp_ca_blk 180
M DpRqPutIntoQueue: put request into queue (reqtype 0, prio LOW, rq_id 19358)
M -OUT- sender_id WORK_PROCESS      tid 10    wp_ca_blk   180     wp_id 10
M -OUT- action    SEND_MSG_ONEWAY   uid 11    appc_ca_blk -1      type NOWP
M -OUT- new_stat NO_CHANGE         mode 0     len         268     rq_id 19358
M -OUT- forward   DIA
M -OUT- req_info CANCELMODE MSG_WITH_REQ_BUF MSG_WITH_OH
M nihsl-getHostAddr: got hostname 'localhost' from operation system
M nihsi-getHostAddr: hostname 'localhost' = addr 127.0.0.1
M nihsl-getServNo: got servicename 'sapdp00' from operation system
M nihsi-getServNo: servicename 'sapdp00' = port 0C.80/3200
M NiIInitSocket: set default settings for socket 1196
M NiCreateHandle: state hdl 1 / socket 1196 NI_INITIAL
M NiIDgSend: init datagram send hdl 1 / socket 1196
M CPU byte order: little endian, reverse network, low val .. high val
M NiIDgSend: connect dgram to: host 127.0.0.1, port 0C.80/3200, fam 2 (low adr..high adr)
M NiIDgsend: sending on connected datagram-handle
M LOCK WP ca_blk 181
M ThResFree: free resources of U11 M0 I2 (normal mode, complete free) at level 3, errno=23, db_action=TH_DB_NO_ACTION, pooling=1
M ThResFree: reset spa state for user T10/U11/M0
M ThCallHooks: call hook >RtmClearSession< for event BEFORE_SESSION_CANCEL
M ThCallHooks: call hook >HttpClearSession< for event BEFORE_SESSION_CANCEL
M ThCallHooks: call hook >SpoolHandleHook< for event BEFORE_SESSION_CANCEL
M SosSearchAnchor: search anchor for 2
M PfStatDisconnect: disconnect statistics
M ThDealComm: del 1 cpic conn(s) of T10/U11/M0 (errno/deal_r2/free_level = 23/1/3)
M ThCPICFree: send DEAL to U11/M0
M ThICMDEAL (14030609, ..)
M ThCPIC: execute cpic func DEALLOCATE
M ThCPIC: last_ftype/last_timeout/last_requested_length/last_receive_data 1/-1/-1/0
M ThCPIC: allowed rq_type of T10/M0 = TH_APPC_RC_RQ
M ThConnectToLocGw: connect to local gateway
M GwConnectSapWp: connect to gateway >localhost< >sapgw00<
M nihsl-getHostAddr: found hostname 'localhost' in cache
M nihsi-getHostAddr: hostname 'localhost' = addr 127.0.0.1
M nihsl-getServNo: got servicename 'sapgw00' from operation system
M nihsi-getServNo: servicename 'sapgw00' = port 0C.E4/3300
M NiCreateHandle: state hdl 2 / socket -1 NI_INITIAL
M NiIBlockMode: switch off block-mode for hdl 2 / socket -1
M NiLowLevCon: connect to: host 127.0.0.1, port 0C.E4/3300, fam 2 (low adr..high adr)
M NiIInitSocket: set default settings for socket 1140
M NiISocket: hdl 2 got socket 1140
M NiPConnect: connect in progress
M SiPeekPendConn: connection of socket 1140 established
M NiLowLevCon: took local port 0E.51/3665
M nilh-localCheck: using local address list
M NiSetStat: state hdl 2 NI_CONNECTED
M NiIWrite: write 64, 1 packs, MESG_IO, hdl 2, data complete
M NiIPeek: peek successful for hdl 2 / socket 1140 (r)
M NiIRead: read 64, 2 packs, MESG_IO, hdl 2, data complete
M GwConnectSapWp: connect to gateway localhost / sapgw00 (pid = 6184) o.k.
M ThISend: (tm/type/info = 10/0x80/0x0, mode_deleted=0)
M ThRqOutCheck: o.k.
M abap strategy ROLL / O.K.
M ThNewWpStat (type=0x80, task_switch=0, inline_hold=0, hand_shake=0, debug=0, ..)
M ThNewWpStat: new state of T10/M0 = 0x3c
M ThISend: new wp stat: 0x0
Regards,
Payal Patel
Message was edited by:
        Payal Patel

Background Job hangs!

Hello Friends,
I am encountering a problem with background jobs which has driven me crazy.
The background job hangs and when I try to debug it using the JDBG command the results are surprising.
When the program control reaches a particular PERFROM statement, then no matter what command I give (F5, F6 or if I double click on any of the variables) it hangs. When I press F5, it should atleast go in to the corresponding FORM, and hang during some processing or it should go into an infinite loop but this is not the case. The system hangs even when I press F5 on the PERFORM. The FORM routine exists in the program, so that possibility is ruled out.
Actually the job processes records of a custom table, this problem starts with a particular record and if I skip the processing of this record then it happens with almost all the records after this one. Also, this does not happen every time the job is run, but whenever it does, it starts with a particular record.
When the system hangs then even if I try to stop the transaction by right clicking on the task bar then it has no effect, the only way to close the session is by using the 'Windows task manager'.
I tried transaction SM50, but there were no changes on that screen for this particular session indicating that it has hanged.
Please let me know if you require any more information.
Thanks and Regards,
Haseeb.

Hi,
Debug it in Sm66.
kishore.

Background Job Scheduling

Hi,
I am scheduling a report to run in background.
In this report it is creating background jobs automatically for different company codes.
It submits the 1st background job and waits until it finishes.
Then 2nd job starts in background and continues with other jobs.
At end it finishes all the jobs and closes.
Now my problem is.
1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
2.       If possible how can we do that.
What I have written is
loop at companycode.
Create job name.
call fun 'Job_Open'.
submit xxxx user sy-uname via job job_name numer job_count
to sap-spool
spool parameters l_spool_parameter
without spool dynpro
with companycode
with ......
and return.
endloop.
Please help ASAP, urgent.

hi praveen,
Job Scheduling Explained
Definition
Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the jobs definition. There are several ways to schedule jobs:
From Transaction SM36 (Define Background Job)
With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
Through the background processing systems own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
Through an external interface.
Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
       1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
       2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
       3.      Set the jobs priority, or Job Class:
·         High priority:      Class A
·         Medium priority: Class B
·         Low priority: Class C
       4.      In the Target server field, indicate whether to use system load balancing.
·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
·         To use a particular application server to run the job, enter a specific target server.
       5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
       6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
       7.      Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
       8.      Save the fully defined job to submit it to the background processing system.
       9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
Specifying Job Start Conditions
Use
When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
Procedure
Choose the Start condition button at the top of the Define Background Job screen.
Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
Once youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
Managing Jobs from the Job Overview
Use
The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
Procedures
To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
To copy a single existing job, choose Job ® Copy.
To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
To repeat a single job, choose Job ® Repeat scheduling.
To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
To review information about a job, choose Job ® Job details. Details displayed can include:
current job status
periodicity, or the repetition interval
other jobs linked to the current job, either as previous or subsequent jobs
defined job steps
spool requests generated by the current job
To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
regards
karthik
reward me points if helpfull

How to Execute WebDynpro Applications as Background Job ?

Hi Gurus,
We have developed a lot of WDJ applications with component reusage; ie,
quite a lot of business logic are wrapped in WDJ Components which are
re-used by other WD UIs.
Now we'd like to automate some of the processes with background jobs
and faced with a few problems :
#1. How can we write a background WD application which can be
triggered by external mechanism and without presenting any UI?
#2. If we write the background program in a Java DC, how can we
invoke existing methods in WD components ?
Anyone got a clue ??
Ying-Jie Chen

Hello Amit,
> Well I can think of a workaround in this case.If you are aware
> of the suspend-resume functionality of the WD application then
> its possible to run the WD application virtually in background.
[ stuffs deleted ...]
It sounds like a possible alternative to our requirement, I'll
spend some time to investigate on the WD suspend-resume mechanism !
> Also let me know why are you preffering the WD if you dont
> require its UI
Our application requires the process to be performed with UI interaction;
with some instances it should be run as a background job. Either case involves
RFC calls to backend SAP R/3 and it's easy for RFC access with WD
Component. Though it's also possible to use CAF application service for
RFC access; due to some technical constrains, we did not use CAF
framework. Therefore it ends up where we are now ...
Thanks for your tip!
Ying-Jie Chen

Low disk space while background job?

Hi All,
I am facing problem with background job which is making low disk space. daily few background jobs are running in 2 or 3 application servers with one user. At OS level file srdrr4 size increasing in Directory usr\sap\<SID>\DVEBMGS00\work.
I restarted dispatcher problem is clreared. But the background job running on another application server.
What could be the reason behind this.
Thanks in advance.
Regards
Ganesh

Hi
Check the trace file of those wp at the os level(more dev_xx) in order to see if this job is filling the log file for example with an error.
Maybe this is the problem....
Z report with problems???? no I don´t think so !!! ahahahahha
Hope this help !!!!

Background jobs html output not allowed 1 MB size

hi experts,
We are facing an issue with backgrounds jobs HTML output. we are running some backgrounds jobs for Std reports, and we are facing if the HTML output is <1 MB, the std sap is cutting/reducing the content only 1 MB. I think somewhere the background jobs HTML output is fixed 1MB, request kindly let us know how & where we can modify/allow the HTML output <1 MB size for background jobs.
Please help.
thanks in advance
Srihari

thanx so much for the solution, but i wanted to fix permanently at the time of html output after the job is finished itself, but when i change the parameters from 1 to 9999 pages, it is showing information message and SAP recommends the spool output is fixed from 1 to 10 pages only, if i go beyond 10 pages, i get message memory slow and impact on memory, etc.,
I wud like to know expert opinion whether doing from 1 to 100 pages thru SP01, what are consequences are to be faced wrt to memory and other aspects. Also i wanted to know these permanent changes will affect entire system or only specific jobs?
I wanted for 2 to 5 background jobs, which are having more than 10 to 30 pages,
Please advise
thanx in advance
srihari

QA Approval - importing queue with background jobs

Similar Messages

Maybe you are looking for