VKM1 - Job - Release

I have maintain automatic credit control for same of the sales documents (the control at the moment checks a review date that should not be in the past, from FD32. If it is in the past it blocks the sales order)
In the meanwhile, I have maintain a job that runs once a day and releases sales orders if there has been any change in the FD32 of the customer concerning the review date. If there is no change the sales order remains blocked.
There are though some cases of sales orders that the sales manager regardless of the review date wants to release them. He enters the vkm1 and releases them.
Up to this point everything is perfect.
If the sales orders that are released by sales manager using the vkm1 became delivery or invoice before the job schedueling runs there is no problem. If for any reason the sales orders are released by the manager using vkm1 but the next function (delivery or invoice) happens after the job schedueling has run again, the sales order becomes blocked again.
Is there a way that if the sales order is released by the manager using vkm1 not to become blocked again if the job runs again (so as not to have to release the same sales order more than once)

Hello,
If i understood correctly , your batch job runs to clear the credit block or releases the block .
If you say credit block is removed ny VKM1 and then the job runs, then the order is blocked .
It says that there is no logic in your batch job . If the So is releases , then it have to buy pass the SO .
Check the logic.
Thanks
RK

Similar Messages

Arrange the job released by workday in SM36

Hi everyone,
I want to arrange the job which be executed every workday and start from the second workday based on the factory calendar.
And I use the WORKDAY/TIME as the start condition to complete this.
But I found it can only be executed one time. How can I let the job be executed every workday.
p.s. I also use periodic job in DATE/TIME and give it restriction based on calendar but it can't control the job released from the second workday.
Could somebody give me an idea. Thank you

Dear Anup
Thank you. The method that you suggested is working. But our requirement is:
1. The job should be executed at every workday and start from the second workday of every month. (That means skip the first workday of the month)
2. We hope there has an ideal way to acheive this purpose without changing the holiday in the factory calendar. Because to set the first workday as a holiday may cause our user confusing. And we also has the other batch job with different start condition that apply the same factory calendar too. But if there still havn't an ideal way, it will be our secondary option.
Thank you so much.
Best regards,
Steven

Error logs in job releases forecast from DP to SNP-"Matl does not exist"

Hi Everyone,
I am facing error logs in the batch job which releases forecast from DP to SNP
Forecast release job - Weekly - Through background job
Forecast category - FA
Error 1: - Characteristic combination appears on batch job log with an error that
"GMC does not exist " Even though it exist in R/3 and APO
All products with error message "Product does not exist" from do exist and have Forecast in Product View
Error 2: - Deleted KCC keep showing up on the Demand Forecast release job log as errors even though they are invalid KCC and were deleted previously. How do they get removed from error log so they don't get created again
Material does not exist on the APO Product Master, in R3 there is a delete flag and the MRP type is set to X1 ,it does not exist in the APO Product Master and does not exist in R3.
Request you to kindly provide any way forward which may be causing error logs of the job
Thanks in advance,
Mrigendra Sharma

Hi Mrigendra,
Please re-initialize the SNP planning area (program : /SAPAPO/TS_PAREA_INITIALIZE) and then check the consistency by executing the program: /SAPAPO/TS_LCM_CONS_CHECK. If you observe any inconsistency in the log/spool, then re-run the program: /SAPAPO/TS_LCM_CONS_CHECK to observe all green.
It is recommended to run the consistency program after any master data change. The initialization program should be run at least weekly.
Try transfering the data again from DP to SNP to see if the error reappear.
Hope this helps.
Regards,
Nawanit

Two same jobs released at a time when only one job is scheduled.

Hello Team,
We are having one strange problem in one of our system from last 8-9 days.
We had scheduled some periodic background jobs. But now for each background jobs 2 jobs (same jobs) are releasing automatically at the same time.
Can you please help me to resolve this problem ASAP.
Currently we are deleting one extra job created. But since no of jobs is very high it is affecting the performance and important jobs are getting delayed.
Thanks & Best regards
Manoj somani

Hi Roberto,
Sorry for late reply...
Is there any other way ?
Because I am finding dificulty in deleting and rescheduling.These jobs are running from long period and Business team is not ready for that . They want the reason why this is happned all of a sudden.
They want the root cause why and how it is happened.
Thanks & Best regards
Manoj

VKM1 Block/Release Sales Order depending on the FI Document Type

Hi guys
I need to configure the R/3 4.6C to block in VKM1 (for Credit Management) only the Sales Orders that have specific FI Document Types in FBL5N. I mean, I don't want to block documents for Static Checks (defined in OVA8) if there are only Credit Memos for the customer in FI, for example.
Is there any way to do this configuration?
I believe I will have to use the USER EXIT enabled in OVA8, but I need to be sure that there is no other way to do this.
Best regards,
Adilson Ferreira

Hi
I am not sure about your requirement. But If you want to exclude certail FI Transactions from Credit check, then you can configure the G/L accounts with the NO credit Check indicator ON.
Example, for Special Transactions like Downpayments, you can set the no credit check indicator ON in OBXR.
Otherwise, using the User exit option is always there
Hope this helps

Job Released

Hi Experts,
I checked in sm 37, 2 jobs are realesed today at 4:00 pm on my name but as per my requirment i dont want to run any chain today,
we have lot of process chains so how can i find out which process chain i scheduled? is there any way?
Help me on this?
Thanks in advance
David

hi David,
I think you are double clikcking on the program, there you wont find the Chain name.
Follow the below steps
1> select your job
2> click on steps
3>it will take you to "Steps List overview" screen -->Select the program name "RSPROCESS" -->in the menu bar select "GOTO" -->Variant --> you can find the CHAIN Name here.
Regards
KP

VKM1 - Release Sales Orders - Job schedueling

I have maintain automatic credit control for same of the sales documents (the control at the moment checks a review date that should not be in the past, from FD32. If it is in the past it blocks the sales order)
In the meanwhile, I have maintain a job that runs once a day and releases sales orders if there has been any change in the FD32 of the customer concerning the review date. If there is no change the sales order remains blocked.
There are though some cases of sales orders that the sales manager regardless of the review date wants to release them. He enters the vkm1 and releases them.
Up to this point everything is perfect.
If the sales orders that are released by sales manager using the vkm1 became delivery or invoice before the job schedueling runs there is no problem. If for any reason the sales orders are released by the manager using vkm1 but the next function (delivery or invoice) happens after the job schedueling has run again, the sales order becomes blocked again.
Is there a way that if the sales order is released by the manager using vkm1 not to become blocked again if the job runs again (so as not to have to release the same sales order more than once)

I will move this questions to SD

Job cancelled

Dear Team,
One of my user has left the job . now his Login ID has been deleted.But I am looking daily two job is cancelled because these job was scheduled by his name.
Now I want to schedule these two job with my login ID.
How I schedule these job with my Login ID.
Moni

Monika,
Goto SM37>Select that perticular job( released status)>Goto Menu Job>Change>then Select Step button , click on change & then change the user id.
As suggested by Olivier try to keep 1 batch user id by which all jobs would run, so that you wont face this kind problem in future.
Thanks
Sushil

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

Send mail to spool list recipient from dynamically generated job

Hi Friends,
We are running the SAP payment run daily in background mode using the transaction F110S (program SAPF110S). We have scheduled the program SAPF110S to run in SM36 and have specified an email address there as Spool List Recipient.
The problem is that SAPF110S itself will dynamically create two new jobs: a job for the Proposal Run and a 2nd job for the Payment Run of F110. The name the system assigns to these jobs are generated at job release/start time in the format F110_CompanyCode_yyyymmdd - X (for the proposal step) and F110_CompanyCode_yyyymmdd (for the payment step).
The proposal and payment steps can create spool output. We want to have that mailed automatically by the system to a spool list recipient.
The problem is that these proposal and payment job steps which are created do not get a spool list recipient assigned, it is empty in SM37.
Is there any way to ensure that the spool list recipient which is populated in the calling job in SM36 gets transferred to the dynamically created proposal and payment steps jobs?
Thanks for your advice.
regards
Mike

Hi,
At the moment sending custom e-mails from front-end via forms is not a feature on our road-map.
What information do you want to include in the respective form, what are the fields supposed to be present in the form? You still have the auto-responder and the custom message in the workflow that could hopefully assist.
Kind Regards,
Alex

Charms : Background job not scheduled (normal correction) ?

Hi,
I am trying to run a dry cycle for normal correction but when i go to task plan in any ticket to release a request. When i schedule this job " release a request" , i dont see any job running in background in SM37. I think job is not gettin sceduled properly.
Please help me out

Hi,
All right. We need to dig this one
I guess you schedule the import by going the the tasklist
and you get a red flag for this activity in the calendar ? do you have any error message ?
If the messagein the task-list is not self-explanatory you can check the SLG1 log in SOLMAN. Which error message do you get there. (select the correct time frame, the log could be big)
My guess is that some S_RFC authorisation is still missing there
This authorisation is outside SAP_ALL and is often the cause of this kind of issue
Tell me the error message and we will hopefully fix this (I had the same kind of issue when I started last year)
best regards Xavier

How to view ALL batch job details (SM37) at one glance ?

Dear all,
I am documenting all released batch job details, the information required includes the job name, client number, job frequency .. etc.
In order to see that information, i go to SM37 and click on each job to see the details. I have about 60 jobs released, to get their details i have to click on them at least 60 times.
Is there a report or table that i can refer to that provides me the information of all the jobs in one screen ?
Thanks.
Advice and comment will be appreciated.
Regards,
Kent

Dear Prashanth,
Thanks for the link, I managed to get the required information from table TBTCO or TBTCP with below selected fields.
JOBNAME = Background job name
SDLSTRTDT = Planned Start Date for Background Job
SDLSTRTTM = Planned start time for background Job
SDLUNAME = Initiator of job/step scheduling
PRDMINS = Duration period (in minutes) for a batch job
PRDHOURS = Duration period (in hours) for a batch job
PRDDAYS = Duration (in days) of DBA action
PRDWEEKS = Duration period (in weeks) for a batch job
PRDMONTHS = Duration period (in months) for a batch job
PERIODIC = Periodic jobs indicator ('X')
STATUS = State of Background Job, S = Released, F = Finished
AUTHCKMAN = Background client for authorization check
EVENTID = Background Processing Event
EVENTPARM = Background Event Parameters (Such as, Jobname/Jobcount)
Dear Juan,
Thanks for your reply.
Regards,
Kent

How to stop the v3 jobs?

how to stop the v3 jobs?

Goto SM37... Give Job Name as LIS. User *.
Enable Scheduld, Released and Active Check boxes...execute.
check job belongs to your Application.
You cancel the Active Job if you stop the Job.
or
You can make Released Job to Scheduled (Menu option Job --< Released --> Scheduled.).
Hope this helps.
Nagesh Ganisetti.

How to stop jobs after a system copy

Hi All,
After doing a system copy from the Production system to some test system, all the jobs that are supposed to be triggered in the production server will also trigger in the test system which is not good.
For example, If we have a payroll running every month. After i do a system copy the same payroll will also be triggered in the test server which is un acceptable.
How do we go about it and what are all the steps that we need to follow after a system copy?
Points will be rewarded.
Thanks
Vijay

Hello Vijay,
you surely need background processes in a running system.
But you can start a SAP system without any background processes.
When the system is up you go to sm37 and delete (or de-release) all the jobs you don't need in the target system. Then set the number of batch processes to the amount you want and restart the system.
Alternatively you can prepare your source system accordingly with the SAP System Copy Guide - Section 3.2 Technical Preparations:
"Set all released jobs from Released to Scheduled:
Tools -> CCMS -> Background Processing -> Jobs - Overview and Administration (transaction SM37)
You also need to do this for jobs that must run periodically (see SAP Note 16083).
Select all jobs (include start after event) as follows:
Job -> Released -> Scheduled"
I think the best way for you is to read this guide!
Everything is explained very well there.
Goto:
https://service.sap.com/systemcopy
In the left tree select:
-> SAP Netweaver
-> SAP Netweaver in Detail
-> Software Life-Cycle Management
-> System Copy & Migration
-> Media Library
There are all the Guides for the current releases.
Regards, Michael
Message was edited by:
Michael Teubner

Scheduled back ground job not finishing

hie gurus, i need your help with back ground scheduling , i have created a background schedule to run my program after every 30min . in the job overview it shows my job released and active but its not finishing processing . the program being run picks up data from an external data base and then inserting via BDC call transaction. i have tried with a different program that inserts data into a database table and its executing and finishing well in the back ground. What could be the problem ? and how can i debug a back ground job ??

Daniel,
To start, BDCs are very out-dated. I would look for a BAPI if you are calling std SAP functionality.
Also - direct updates into std SAP tables is a HUGE "no-no"... I hope that you are updating custom tables only.
Pass that - to debug a b/g job--->
1) Set a breakpoint in your program
2) select the job in SM37
3) enter JDBG into the SAP fastpath of the SM37 screen and press ENTER
This will navigate you into a b/g debug - you can then press the debugger buttons to move to your breakpoint.
Hope that helps.

VKM1 - Job - Release

Similar Messages

Maybe you are looking for