About Job schedule

Hi,
I use pl/sql developer---> jobs to set my job schedule.
Today,my job isn't work and error message ORA-12011 and ORA-06512.
I don't know how to edit it.
jing

This is my code:
begin
sys.dbms_job.submit(job => :job,
                      what => '
submitter.package.method;',
                      next_date => to_date('30-11-2005', 'dd-mm-yyyy'),
                      interval => 'TRUNC(SYSDATE+1)');
commit;
end;
submitter.package.method these tree parameters I have filled the correct values.
Yesterday, I clicked 'run' and it could execute but today it doesn't work.This job must run once everyday.

Similar Messages

Questions about job scheduling

i am a newbie in oracle, and i have several quesions about the scheduler.
1 If I just have one job class, and there are many concurrent jobs inside. Then, how does oracle exactly schedule those jobs with the same priority?(Will they run for several time slices each time or be executed until completed one by one?)
2 How does oracle exactly schedule those jobs with different priorities?
3 If I have two job classes, how will oracle schedule those jobs in these two classes?(each of them is assigned some time slices based on the cpu allocation?)
I have checked many turorials from oracle, but I have not got any detailed explanations or examples to show how oracle will exactly do it. I am currently doing some QoS management in an application based on oracle, so I am in great need of those information and details inside the scheduler.
Thanks a lot.

Hi,
We have a situation here. We have a Info Warehouse, against which Batch Jobs are scheduled (around 200) using a 3rd party scheduling tool. The window for these jobs is 9pm-8am EST. All the batch jobs were completed withing the SLA window of 11 hours everyday until recently. The data has been growing in the database and the batch jobs have started taking longer time to complete and hence missing out on the SLA.
We are thinking of using Database Resource Manager inorder to put the Batch Jobs in a Resource Group and bind it to Highest priotiy during the SLA window. Points to Ponder over are :
Let's assume that we have put the Bacth Jobs in Hight Priority resource group with 80% CPU allocation and it comes into effect at 9pm everyday (that's when the jobs start executing). And, we have put all other users in a different resource group with Low priority (say 10%).
The situation here is : - What if a user logs into the system at, say 8:45pm. and initiates execution of a huge reporting query against dataset. Assuming that the quesry takes about 60 minutes (during idle database condition), initially it would acquire all the CPU which it needs (as there is no load on the db at this time), and the jobs are scheduled to start at 9pm.
Q: Will the priority for jobs set per the resource directives to the resource group for jobs take preceedence over the CPU already held by the low priority User?
-- If Yes, what happens to the User session?
-- If No, what are the possible scenarios?
Q: Also, is it feasible to issue a KILL ALL SESSIONS just before the scheduled batch jobs, so that the jobs have a clear path for execution (taking into account that we have already prioritized the Jobs into High Priority Resouce group). So, that we are sure that there is no user connection right before the batch jobs start. and once they start, the resource allocation is going to be done based on the Resource Group priority and CPU assigned to respective group.?
Q: Or, if it is more feasibile/beneficial to have all other user sessions switch to lower priority after a defined interval, so that it gives the CPU for the jobs.
Q: Is there a difference between the Database Resource Manager in 9i/10g/11i.
Any detailed explanation would be appreciated.
Thanks
Gaurav

Job Scheduling -- About SM36

Hi,
       can any tell me ..how to run the bdc thru job scheduling ( SM36 ). In my BDC I have Used GUI_UPLOAD function.So I want to Upload the data thru scheduling.
Thx & Regards,
Sunder.

report zmiro
       no standard page heading line-size 255.
include bdcrecx1.
selection-screen begin of block blk3 with frame title text-019.
parameters : pa_fname type localfile.
selection-screen end of block blk3.
data : lv_fname type string.
data: begin of record occurs 2,
        bldat_003(010),
        xblnr_004(016),
        ebeln_008(010),
        zfbdt_021(010),
        xmwst_030(001),
        mwskz_031(002),
        wrbtr_050(016),
      end of record.
at selection-screen on value-request for pa_fname.
call function 'F4_FILENAME'
    exporting
      program_name = syst-cprog
      dynpro_number = syst-dynnr
      field_name    = 'PA_FNAME'
    importing
      file_name     = pa_fname.
start-of-selection.
lv_fname = pa_fname.
perform open_group.
call function 'GUI_UPLOAD'
exporting
    filename                      = lv_fname
    filetype                      = 'ASC'
    has_field_separator           = 'X'
tables
    data_tab                      = record
loop at record.
if sy-subrc <> 0. exit. endif.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'INVFO-BLDAT'
                              record-bldat_003.
perform bdc_field       using 'INVFO-XBLNR'
                              record-xblnr_004.
perform bdc_field       using 'BDC_CURSOR'
                              'RM08M-EBELN'.
perform bdc_field       using 'RM08M-EBELN'
                              record-ebeln_008.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=HEADER_PAY'.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=HEADER_TOTAL'.
perform bdc_field       using 'BDC_CURSOR'
                              'INVFO-ZFBDT'.
perform bdc_field       using 'INVFO-ZFBDT'
                              record-zfbdt_021.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=DUMMY'.
perform bdc_field       using 'INVFO-XMWST'
                              record-xmwst_030.
perform bdc_field       using 'INVFO-MWSKZ'
                              record-mwskz_031.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=DUMMY'.
perform bdc_field       using 'BDC_CURSOR'
                              'INVFO-MWSKZ'.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'BDC_CURSOR'
                              'INVFO-WRBTR'.
perform bdc_field       using 'INVFO-WRBTR'
                              record-wrbtr_050.
perform bdc_dynpro      using 'SAPLMR1M' '6000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=PB'.
perform bdc_dynpro      using 'SAPLMR1M' '6250'.
perform bdc_field       using 'BDC_CURSOR'
                              'RM08R-SUMME_SOLL'.
perform bdc_field       using 'BDC_OKCODE'
                              '=BU'.
perform bdc_transaction using 'MIRO'.
endloop.
perform close_group.
Hi the above is my program ..thru this program i want to upload thru scheduling how can i do ..kindly modify and give me the procedure for sm36...i dont any thing..about this..
thx& Regards,
sunder

About Background job scheduling

One file will be coming from oracle system. it would be stored at a particular path.
I want to schedule for background job processing. how to do.

Hi,
You need to write a Program to place the file in the Application server, then only you can schedule a background job, you need to use the OPEN dataset, CLOSE DATASETS to do this one, then you can schedule the job .
To schedule a job in the background job, look at the below links
Re: background job schedule
http://aspalliance.com/1129_Background_Processing_SAP_R3_System
Regards
Sudheer

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

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.

Error occured while posting the job schedule for JDBCAdapter

Hi Experts,
In Application Log in Path: "/usr/sap/<SID>/DVExxxx/j2ee/cluster/server1/log", I see the error:
#/Applications/ExchangeInfrastructure/AdapterFramework/Services/Util
##com.sap.aii.af.service.scheduler.SchedulerManagerImpl.postJobScheduleOthers(String, int)
#J2EE_GUEST#0##n/a##f7956e1f6b4711e0b851001e0b5d3ac8#SAPEngine_Application_Thread[impl:3]_23##0#0
#Error#1#com.sap.aii.af.service.scheduler.SchedulerManagerImpl#Plain
###error occured while posting the job schedule for JDBCAdapter_9f0584b1bcb33b94b67ada456233bcb8 with 2#
Frequently are created Lock's and I need remove them in Visual Admin.
Any idea about this error?
Tks in advance.

Hi,
After applying the SP 23 Patch Level 08, LOCK JDBC problems stopped.
But now when a network error or database error, the JDBC Sender Communication channels that were open to connection, are blocked.
Even following the instructions in [SAP Note 1083488 - XI FTP_JDBC sender channel stop polling indefinitely (04_04S)|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1083488] the problem continues.
I've already set the parameter "taskTimeout" and selected the option "Disconnect from Database After Each Message Processing" but not resolved.
Any ideas?
Thanks in advance.

Creation of batch job Schedule

How to create new batch job Schedule ?
Regards,
Sridhar

Hi,
For more details about background processing go through the link provided.
http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a7ede505211d189550000e829fbbd/frameset.htm
Hope it helps you.
Regards
CSM Reddy

Back ground job scheduling in BDC

Hi ,
Can anybody explain about back groung job scheduling in BDC program.

Hi,
In your BDC program first create sessions, Submit the program RSBDCSUB with parameters like session name, startdate etc .
Then session will be processed in background.
Or You can write the BDC program to create sessions.
select the sessions from SM35. Then click on Process, a popup will be displayed, then choose third option(Backgound processing).
Then your session will be processed immediately..
Rewards points if helpful.
Regards,
Ashok

Backing up Jobs, Chains and Programs in Oracle Job Scheduler

What is the best way to back up Jobs, Chains and Programs created in the Oracle Job Scheduler via Enterprise Manager - and also the best way to get them from one database to another. I am creating quite a long chain which executes many programs in our test database and wish to back everything up along the way. I will also then need to migrate to the production database.
Thanks for any advice,
Susan

Hi Susan,
Unfortunately there are not too many options.
To backup a job you can use dbms_scheduler.copy_job. I believe EM has a button called "create like" for jobs and programs but I am not sure about chains and this can be used to create backups as well.
A more general purpose solution which should also cover chains is to do a schema-level export using expdp i.e. a dump of an entire schema.
e.g.
SQL> create directory dumpdir as '/tmp';
SQL> grant all on directory dumpdir to public;
# expdp scott/tiger DUMPFILE=scott_backup.dmp directory=dumpdir
You can then import into a SQL text file e.g.
# impdp scott/tiger DIRECTORY=dumpdir DUMPFILE=scott_backup SQLFILE=scott_backup.out
or import into another database (and even another schema) e.g.
# impdp scott/tiger DIRECTORY=dumpdir DUMPFILE=scott_backup
Hope this helps,
Ravi.

Parallel processing in background using Job scheduling...

(Note: Please understand my question completely before redirecting me to parallel processing links in sdn. I hve gone through most of them.)
Hi ABAP Gurus,
I have read a bit till now about parallel processing. But I have a doubt.
I am working on data transfer of around 5 million accounting records from lagacy to R/3 using Batch input recording.
Now if these all records reside in one flat file and if I then process that flat file in my batch input program, I guess it will take days to do it. So my boss suggested
to use parallel processing in SAP.
Now, from the SDN threads, it seems that we have to create a Remote enabled function module for it and stuf....
But I have a different idea. I thought to dividE these 5 million records in 10 flat files instead of just one and then to run the Custom BDC program with 10 instances which will process 10 flat files in background using Job scheduling.
Can this be also called parallel processing ?
Please let me know if this sounds wise to you guys...
Regards,
Tushar.

Thanks for your reply...
So what do you suggest how can I use Parallel procesisng for transferring 5 million records which is present in one flat file using custom BDC.?
I am posting my custom BDC code for million record transfer as follows (This code is for creation of material master using BDC.)
report ZMMI_MATERIAL_MASTER_TEST
      no standard page heading line-size 255.
include bdcrecx1.
parameters: dataset(132) lower case default
                             '/tmp/testmatfile.txt'.
   DO NOT CHANGE - the generated data section - DO NOT CHANGE    ***
If it is nessesary to change the data section use the rules:
1.) Each definition of a field exists of two lines
2.) The first line shows exactly the comment
      '* data element: ' followed with the data element
      which describes the field.
      If you don't have a data element use the
      comment without a data element name
3.) The second line shows the fieldname of the
      structure, the fieldname must consist of
      a fieldname and optional the character '_' and
      three numbers and the field length in brackets
4.) Each field must be type C.
Generated data section with specific formatting - DO NOT CHANGE ***
data: begin of record,
data element: MATNR
       MATNR_001(018),
data element: MBRSH
       MBRSH_002(001),
data element: MTART
       MTART_003(004),
data element: XFELD
       KZSEL_01_004(001),
data element: MAKTX
       MAKTX_005(040),
data element: MEINS
       MEINS_006(003),
data element: MATKL
       MATKL_007(009),
data element: BISMT
       BISMT_008(018),
data element: EXTWG
       EXTWG_009(018),
data element: SPART
       SPART_010(002),
data element: PRODH_D
       PRDHA_011(018),
data element: MTPOS_MARA
       MTPOS_MARA_012(004),
     end of record.
data: lw_record(200).
End generated data section ***
data: begin of t_data occurs 0,
      matnr(18),
      mbrsh(1),
      mtart(4),
      maktx(40),
      meins(3),
      matkl(9),
      bismt(18),
      extwg(18),
      spart(2),
      prdha(18),
      MTPOS_MARA(4),
    end of t_data.
start-of-selection.
perform open_dataset using dataset.
perform open_group.
do.
*read dataset dataset into record.
read dataset dataset into lw_record.
if sy-subrc eq 0.
clear t_data.
split lw_record
   at ','
into t_data-matnr
      t_data-mbrsh
      t_data-mtart
      t_data-maktx
      t_data-meins
      t_data-matkl
      t_data-bismt
      t_data-extwg
      t_data-spart
      t_data-prdha
      t_data-MTPOS_MARA.
append t_data.
else.
exit.
endif.
enddo.
loop at t_data.
*if sy-subrc <> 0. exit. endif.
perform bdc_dynpro      using 'SAPLMGMM' '0060'.
perform bdc_field       using 'BDC_CURSOR'
                             'RMMG1-MATNR'.
perform bdc_field       using 'BDC_OKCODE'
                             '=AUSW'.
perform bdc_field       using 'RMMG1-MATNR'
                             t_data-MATNR.
perform bdc_field       using 'RMMG1-MBRSH'
                             t_data-MBRSH.
perform bdc_field       using 'RMMG1-MTART'
                             t_data-MTART.
perform bdc_dynpro      using 'SAPLMGMM' '0070'.
perform bdc_field       using 'BDC_CURSOR'
                             'MSICHTAUSW-DYTXT(01)'.
perform bdc_field       using 'BDC_OKCODE'
                             '=ENTR'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(01)'
                             'X'.
perform bdc_dynpro      using 'SAPLMGMM' '4004'.
perform bdc_field       using 'BDC_OKCODE'
                             '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                             t_data-MAKTX.
perform bdc_field       using 'BDC_CURSOR'
                             'MARA-PRDHA'.
perform bdc_field       using 'MARA-MEINS'
                             t_data-MEINS.
perform bdc_field       using 'MARA-MATKL'
                             t_data-MATKL.
perform bdc_field       using 'MARA-BISMT'
                             t_data-BISMT.
perform bdc_field       using 'MARA-EXTWG'
                             t_data-EXTWG.
perform bdc_field       using 'MARA-SPART'
                             t_data-SPART.
perform bdc_field       using 'MARA-PRDHA'
                             t_data-PRDHA.
perform bdc_field       using 'MARA-MTPOS_MARA'
                             t_data-MTPOS_MARA.
perform bdc_dynpro      using 'SAPLSPO1' '0300'.
perform bdc_field       using 'BDC_OKCODE'
                             '=YES'.
perform bdc_transaction using 'MM01'.
endloop.
*enddo.
perform close_group.
perform close_dataset using dataset.

Third party Job Scheduling?

Hi P6 Guru.
Our customer is looking for the solution of job scheduling to control the jobs for P6 Web services API programs with other Web services programs outside P6. Some jobs would be triggered by scheduled date&time, some would be triggered by success states of predecessor jobs.
IBM Tivoli workload scheduler(TWS), HP OpenView are what I can image easily for the solution. But I'm wondering it is popular to use such kind of system.
Do you have any experiences or idea about how you or your customers control the job scheduling of running tasks or programs?

AppWorx, now UC4, is one possibility but there is little, if anything, they can do that can not be done through the proper use of the DBMS_SCHEDULER package.
I would suggest that, before you spend or waste money, you look at the docs on DBMS_SCHEDULER and determine that there is something you need that you have not already purchased. Using OEM to schedule jobs is far from giving you access to the full functionality.

Delay between step in job scheduling

Hi Experts,
Can anyone give me a idea about steps in job scheduling,and how to set a delay between steps in job scheduling in Tcode SM36 metion if there is any settings available or i have to code it in SE38.
Thanks in advance.

Check this link:
http://help.sap.com/saphelp_nw70/helpdata/en/c4/3a7f87505211d189550000e829fbbd/frameset.htm
Regards,
Ravi

Best SAP Security Practices Print,file,job schedule, archiving

Hello All, i would like to know in your experience which will be the best practices for Security for this list below:
- Printer security (especially check printing)
- File path security for export/import
- Best Practice for Job Schedule and Spool file
- Archiving process (I can't think of any specific to security, other than Security Audit Logs)
Are there any special transactions/system settings/parameters that must be on place in order to hard SAP Systems?
Do you have any documentation related?
I mean for example Job, spool i think user must just only run heir own jobs,and se their own works for printing, is there a paremeter to athenticate Prints/user, etc.
Please let me know your comments about those related issues.
I appreciate your help.
Thanks a lot.
Ahmed

Hi,
PFCG_TIME_DEPENDENCY
This is best to run once a day mostly after 12.01 am as it removes the roles which are invalid for current date. As role assignment is on date basis there is no advantage of running it hourly.
/VIRSA/ZVFATBAK
This is for GRC 5.3, and this job is to collect FFID logs from backend to GRC repository, so if you have frequent FFID usage you can schedule it hourly or for every 30 min too, if you have enough bandwidth in your server to get the latest log report. or else you can have it scheduled for twice a day too, so it is purely based on your need.
Hope this helps.
BR,
Mangesh

Obtain Job invoker for a SSIS job scheduled in SQL Server Agent

Hello,
I was required to tell the job runner of a particular SSIS job scheduled in SQL Server Agent (in SQL Server Management Studio 2008 R2). I noticed that after running the job, a record can be found in msdb.dbo.sysjobhistory in the [message] columm saying that
the job is invoked by 'Domain\User'. Is there anyway I can acquire and upload that information into an audit table by adding some additional script into the job? I heard about using token to get job_ID, but what about the actual user name who runs
the job?
Thanks

Just add retry attempts to whatever number you want (2 as per your original explanation) in Job step properties as below
Have a logic to include a delay of 10 mins . You can make use of WAITFOR function for that
see
http://www.mssqltips.com/sqlservertip/1423/create-delays-in-sql-server-processes-to-mimic-user-input/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

About Job schedule

Similar Messages

Maybe you are looking for