Importing SAP background Jobs to CPS

Hi,
We have installed free version of SAP CPS for testing. We are able to create new job through SAP CPS on Backend system.
But how to import existing jobs from backend SAP (AS ABAP) system to SAP CPS
Thanks and Regards,
Yash

Hi,
The import creates definitions in CPS that match the definitions of the jobs in SAP, you can find these under "Job Definitions" or under "Job Chains" (depending if it was a single step or multi-step job).
If you want to start running the job from CPS, you need to submit the corresponding job definition in CPS with the desired scheduling parameters and put the one directly in SAP on hold or remove it all together.
Based on your questions, monitoring of SAP jobs by CPS could also be of interest to you.
You can find more information on both topics in the administration guide that comes with the product (under the "i" icon in the user interface).
Regards,
Anton.

Similar Messages

How to Schedule SAP background job at OS Level

Hi All,
Can Anyone tell me how to Schedule SAP background job at OS Level (unix).
Regards,
Anil

Hi Anil,
I donu2019t know your requirements, anyway itu2019s possible to setup your SAP job in order to start after an event, and after that you can get the event triggered from the Operating System in the following way:
- log into you Operating System with the SIDadm user id (at the Operating System level) and go to directory /usr/sap/SID/SYS/exe/run
- Run the SAPEVT executable as follows:
sapevt YOUR_EVENT -t pf=/usr/sap/SID/SYS/profile/DEV_DVEBMGS00_server001 nr=01
This will raise the event, and cause the job scheduled within SAP to execute.
You can periodically execute this job with crontab.
Thanks,
Federico Biavati

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

Extract SAP Background Job list to excel and E-mail to User

Hi Experts,
I am a Basis consultant and have a requirement to download the list of finished & cancelled SAP BG jobs of previous week to excel and send e-mail to Users. For now we are doing this manually every week, Is this possible to automate this process? Please help to share your views.
Thank you very much in advance.
Regards,

Hi Mariano,
Thanks for your reply. Yes, I have already checked TBTC* tables but i want to know is there any standard report/program that can be scheduled on daily basis to download all the required data from SAP to excel?
Regards,

Importing background jobs

Is there a way to import SAP background jobs from one client to another? In SM37, there ia an option to export the job, but I don't see an option to import it.
Thanks

Hi,
The 'export' option you see is just a possibility to export to Excel the table of jobs in the selection.
Regards,
Eli

Background job executed as SAP*, need advice to change owner.

Hi all,
I'm facing an issue where my SAP background job currently has 2 job "SAP_CCMS_CPH_REORG" and "SAP_CCMS_CPH_HRCOLL" under the ownership of sap. I would like to move them away from SAP ID.
I have tried to recreate the job using sm36 (and using my ID with sap_all profile) in testing environment, but it not seem to work.
Highly appreciates any advices and/or pointers with regards to the above mention question.
Thank you.

Hi all,
Thank you for the reply but I have forgotten to add a few updates.
The issue is that I can change owner from SAP* to my ID with sap_all profile.
But, after execution,
Job with sap* owner ended successfully, with spool status marked as completed.
whereas
Job with my ID as owner ended successfully, but spool status marked as "waiting"
error mesage:
Description          Value
Status:              Frontend unavailable
Last event:
Message:             Request on hold
Date:                19.02.2009
Time:                11:57:28
Job status:          On hold
Error class:         Delayed
Area:                Data transfer
Printout:            Not printed
Apologies for the inconveniences caused.

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

Help required in Background Job

Hi Experts,
My client is scheduling background job for creating Cost Document. The job creates cost document and PO simultaneously.
The requirement is, i need to change the validity start and end date of the PO with the price date of the cost doc.
I am not aware of background job. Can someone let me know how this can be done.
Thanks in advance.
Regards
Balu

Hi Balu,
From this Thread, my understanding is that you are not aware of the SAP Background Job scheduling Concepts and it's implementation. Have a look at the follwing links for how to schedule a Background Job in a SAP System.
http://help.sap.com/saphelp_nw04/helpdata/en/ef/2c513897110872e10000009b38f889/frameset.htm
http://help.sap.com/saphelp_wp/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/6a56389f64246fe10000009b38f889/frameset.htm
Hope this will help.
Thanks,
Samantak.
Edited by: Samantak Chatterjee on Oct 23, 2009 11:15 AM

Scheduled Background jobs after Client Copy

Hello,
I've been doing some searching online and I don't seem to be able to find a definitive answer to this question:
Are background jobs client specific?
I've seen some discussions on here say some are and some are not. I've also seen a discussion that says ALL background jobs are client specific.
It's really related to non-SAP background jobs after a client copy.
If I have a client 100 in QA with half a dozen non-SAP standard jobs configured, and I create client 110 in QA and perform a remote client copy from PROD into client 110 on QA, will my non-SAP standard backgrounds run in Client 110, or do I need to set them all up again?
Thanks

Hello All
If I have a client 100 in QA with half a dozen non-SAP standard jobs configured, and I create client 110 in QA and perform a remote client copy from PROD into client 110 on QA, will my non-SAP standard backgrounds run in Client 110, or do I need to set them all up again?
Yes. You will need to set those non standard jobs in the new client. When you schedule a job there will be a reference to the client where the job will be executed is stored under AUTHCKMAN in the table TBTCO. If the job is scheduled periodically then the job is executed only on the client where it is scheduled.
I used SAP_ALL profile when performing the client copy. So my scheduled jobs WILL have been copied along with everything else? Is that correct?
In SAP_ALL profile the background jobs will be coming from source client not from QA client 100.
No. Background jobs are not transportable and will not be copied during a client copy. Job definitions are client independent.
Read these SAP notes.
31503 - FAQ: Background jobs
51135 - Why are bkgd processing jobs not generally transportable?
If you want to schedule those jobs in the new client the follow the suggestion in the SAP note 3150 point 6.
Regards
RB

How to Export/Import a batch job

Hi there,
I am wondering if there is/are transaction that can export/import a background job(s). Because, one of our production background jobs got deleted somehow and we have same job that sits in QA system, so we want to export that background jobs and import to Production system, since it has around 70+ steps
Thanks
Kumar

I'm not sure
but if these jobs can be put in a request and.. then transport..
U can try..

Exact Steps to schedule a background job a specific time daily :

Dear All,
Please let me know the whole process involved in schedule a background job a specific time daily. what is calender id. I could not understand what it has given in SM36.
Thanks in advance.
Rgds
Prem.

Hi prem
this is complte procedure for ur requirment.
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
Call Transaction SM36 or choose CCMS ® Jobs ® Definition .
Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
Set the jobu2019s priority, or "Job Class":
High priority: Class A
Medium priority: Class B
Low priority: Class C
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.
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.
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.
Define the jobu2019s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
Save the fully defined job to submit it to the background processing system.
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.
pls give points if it is usefull
Regards
Saimedha

I cannot cancel a background job

Hello,
I cannot cancel a background job which is running since the last Friday. I use the SM37 transacction but it doesn't stop.
Can anybody tell me how can I get to stop this job?
Thanks in advance.
Regards.

Hello friend,
I think these links will help you to stop the job running in back ground,
How to stop Active Background Jobs
http://stackoverflow.com/questions/1439033/sap-background-job-hows-it-running
If your problem still exists revert back to me i will help you.
Thanks,
Sri Hari

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

Rule set import - Background job did not run

Hi,
I am setting up my CC 5.2 production system. I have downloaded from ruleset from the dev CC and imported it into production. However the background job generated did not run. I am implementing SAP note 999785 to fix this, but am wondering what should I do about the rule set? Do I need to delete the rule set and reimport it? As this background job did not run I notice that the permission rules did not generate.
Any advice is welcome.
Thanks

Hi,
as the backgorund job never ran and no rules were created, I can just reimport the ruleset and let the job run. I have tried this and the rules were created successfully

Importing SAP background Jobs to CPS

Similar Messages

Maybe you are looking for