Job Scheduling by Redwood workcenter

Hello ,
I want to do Job Scheduling by Redwood workcenter i already imported ST-PSM Add-on in SM-system(SM007-system name) Is it necessary to do this in child system (BI008-system name)?
Problem:
When i try to creat "Job Request" in workcenter i am get this problem "Business partner SWAROOP does not exist "but i already created BP SWAROOP in SM007(Solution Manager system).
Please let me know what are the other confi i have to do ?
Regards,
Swaroop

Hi,
first of all: The Add-On ST-PSM has to be installed on the Solution Manager system only. After the installation you can activate the additional IMG activities, see SAP note 1122497.
How to create a valid business partner for Job Requests:
1. Easy Solution: Create BP for an user in a remote system automatically (as decribed in IMG activity "Create Business partner"):
Two possibilties
a) Call menu function "Edit -> Create business partner" from within any solution of transaction DSWP
b) Run report DSWP_USER_PROPAGATION_TO_CRM directly (you need to know the solution ID that gets displayed directly after creation of a new solution)
2. Create BP manually (as decribed in IMG activity "Create Business partner"):
- Start transaction BP and create a new business partner and save it
- Go to tab "Identification" and add an External System Identifier (type CRM001) in the format <system ID><space><installation number><space><client><space><user name>
- save
- Add role "Employee" to your business partner and go to tab "Identification" and enter the corresponding user name.
- save
Please also review SAP note 1229982.
Kind regards,
Martin

Similar Messages

Scheduling a BI job chain in Redwood

The problem I am having is we are trying to schedule a BI job chain via Redwood software and are not getting any response. Within Redwood, I have executed these jobs IMPORT_BW_CHAINS, IMPORT_BW_CHAIN_DEFINITION, IMPORT_BW_INFOPACKAGES using BI job chain 0fcsm_cm_10 which is defined in BI as a job chain. These jobs run to completion but nothing is moved into Redwood to schedule as you would see from a import of a CCMS job. When I run job RUN_BW_CHAIN using the same BI job chain ID I receive the below error. Not sure what Im missing or doing with the process to get to schedule the BI job chains with Redwood.
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "RSI.RSIEXEC", line 1638
ORA-06512: at "RSI.RSIEXEC", line 1759
ORA-06512: at "RSI.RSI_RUN_BW_CHAIN", line 21
ORA-06512: at "RSI.RSI_RUN_BW_CHAIN", line 80
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_SYS_SQL", line 1200
ORA-06512: at "SYS.DBMS_SQL", line 323
ORA-06512: at "SYSJCS.DDL", line 1085
ORA-06512: at "SYSJCS.DDL", line 1118
ORA-06512: at "SYSJCS.DDL", line 1177
ORA-06512: at line 3
JCS-00215: in statement RSOJ_EXECUTE_JOB

I am also seeing the same issue
anton the last information you requested
The following products are installed in the Cronacle repository:
Product                                  Version    Status
Cronacle for SAP solutions               7.0.3      Production
Cronacle Forecast Module                 7.0.3      Production
Cronacle Reports Module                  7.0.3      Production
Cronacle &module Module                  7.0.2      development
Cronacle Mail Module                     7.0.3      Production
Cronacle Audit Module                    7.0.2 r2.2 Production
Cronacle Process Manager for Web         7.0.3      Production
Cronacle Module Installer                7.0.3      Production
Cronacle Repository                      7.0.3.34   Production
Cronacle Monitor Module                  7.0.3      Production

Job Scheduling in Solution Manager - Error creating Periodic Job

Hi all,
I am in the process of testing the Job Scheduling functionality using the Solution Manager. I have setup the criteria manager, ec. in the satellite system, and done the config in Solman as well.
I am able to successfully setup up a 'on-time' job.
it's only when I try to setup a periodic job, I end up getting following error
Any thoughts? Is there any piece of config that's missing? All the SICF services needed for this functionality are running fine.
Thanks for the help.
500 Internal Server Error
Error when processing your request
What has happened?
The URL https://fsspsm.target.com:/sap/bc/webdynpro/sap/wd_ags_ejr_job_req_gaf_app was not called due to an error.
Note
The following error text was processed in the system PSM : Message was not created
The error occurred on the application server fsspsmap01_PSM_00 and in the work process 1 .
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Function: BAPI_NOTIFICATION_CREATE of program SAPLDSWP_NOTIF
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: SUBMIT_REQ_CRM_DATA of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: SUBMIT of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: PROCESS_SCENARIO_PERIODIC of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: PROCESS_JOB_SCENARIO of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: IF_AGS_EJR_JSM_PROC_FPM_CTRL~AFTER_PROCESS_EVENT of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: IWCI_IF_FPM_APP_CONTROLLER~AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: CALL_UIBB_PROCESS_EVENT of program CL_FPM========================CP

Hello,
This is the basic Job Scheduling functionality and not the Redwood Job scheduling, correct?
Have you performed the IMG Activiteis in SPRO?
See the following Help link:
http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/c5/7edcbd58ce4e29bc1baf1c4761d71f/frameset.htm
Change a job
You can change the scheduling of a job as long as it has not been completed. Proceed as follows:
Make changes.
Note
When you change a periodic job, the system searches for the changeable successor and only changes this successor.
If there is more than one changeable job with the same name, the system does not change any of these jobs.
End of the note.
Save your entries.
To release the job in the target system, select Release.
You go to the transaction SM37 in the target system.
You just may want to ensure HTTP Services have been enabled. I realize you said the services workin SICF, but this needs to be verified as 500 Internal Server Error most often means the HTTP services are not activated.
Regards,
Paul

Requested start time during job scheduling population in local time.

Hello Experts,
Could you please help on the issue.
Requested start time during job scheduling populated with local time even though we have assigned the GMT time zone.
Could you please help , how to change the settings of request start time calender icon to populate the GMT time.
thanks,
Suresh.

Hello Gerben,
Thanks for the reply, even though the default time zone set as GMT in user settings, the requested start time calender pop up the local time instead of GMT time.
Previously requested start time poped up the GMT time, we have observed this change once we have ran the redwood script for time window elements change and imported some of the job definitions, applications & time windows from other system.
Below is the script we have ran thought shell script
Script Fuctionality
1. Take the mentioned time window
2. iteratate thought the time window elements and add 1 hour to the "time to day from" & "time to day to" parameters.
3. set the changed parametes to time window and persist the changes.
// Variable Declarations
String timewindow = null;
String query = null;
TimeWindow tw = null;
TimeWindowElement twe = null;
long otdvalue = 3600000;
long l1 = 0;
long l2 = 0;
long threshold = 0 ;
long expvalue = 82800000;
long expvalue1 = 85500000;
long indto1 = 0;
long indfrom1 = 300999;
long indto2 = 2700000;
long indfrom2 = 3000999;
Job job = null;
//Declare all the time windows in array
String[] timewindows = {"XX_TIMEWINDOW_01_GMT"};
          for( int i = 0 ; i < timewindows.length; i++)
          timewindow = timewindows<i>;
          jcsOut.println("TimeWindow"i":"+timewindows<i>);
          tw = jcsSession.getTimeWindowByName(timewindow);
          for (Iterator it1 = tw.getTimeWindowElements(); it1.hasNext();)
               twe = (TimeWindowElement) it1.next();
               Long otd = new Long(otdvalue);
               jcsOut.println("************************");
               jcsOut.println(twe.getTimeOfDayFrom());
               jcsOut.println(twe.getTimeOfDayTo());
               jcsOut.println("************************");
               Long todf = (Long) twe.getTimeOfDayFrom();
               Long todt = (Long) twe.getTimeOfDayTo();
                                  threshold = todf.longValue();
                        // if timeday from equal to 23 GMT assign the 0 GMT
                                  if(threshold == expvalue )
                jcsOut.println("timewindow with 23 GMT");
               l1 = indto1;
               l2 = indfrom1;
                        //if timedayfrom equal to 23:45 GMT assign 0:45 GMT
               else if(threshold == expvalue1)
               jcsOut.println("timewindow with 23:45 GMT");
               l1 = indto2;
               l2 = indfrom2;
                        // Add 1 hour for current time of day from
               else
               l1 = todf.longValue() + otdvalue;
               l2 = todt.longValue() + otdvalue;
               Long ll1 = new Long(l1);
               Long ll2 = new Long(l2);
               twe.setTimeOfDayFrom(ll1);
               twe.setTimeOfDayTo(ll2);
               jcsOut.println("After Change:"+ twe.getTimeOfDayFrom());
               jcsSession.persist();
Once after the script competetion the time window time zone remains in GMT.
Could you please check script once and help us the time zone change caused the by script or not?
Thanks,
Suresh

Job Scheduling tool with SAP SolMan

Hi Experts,
Please advise on among Autosys, BMC or Redwood , which one is the best to work with Sol Man in job scheduling purpose.
Thanks

Hi Preema,
I would strongly recommend Redwood since it integrates with all SAp components including Solman.
- Bhushan

Regarding automatic job scheduling

hi experts,
i have done automatric job scheduling with the help of tc-SM36,so that the my report will run on every morning at 9oclock but in the development server i did it n it is working fine what i want to know that i have to do the same thing in the production server will i have to do it directly on the production server or will it be stored in the request number and then i have to transport it to the production server........
plz help me....

Hello Rajat,
You might want to look into SAP Central Process Scheduling by Redwood. This might solve your problems as SM36/37 is in maintanace mode and will not be developed any further this is a good step to make.
The link is:
Scheduling
The product can be downloaded from the SWDC under Application Group SAP Netweaver, Netweaver 7.0, SAP Central Process Scheduling.
if you have any questions do not hesitate to give me a call 031306354598
Regards,

Job scheduled, flow diag.s, dependencies in Graphical & Spreadsheet format

Would you please let me know if the CPS (Redwood) provides the list of all the jobs scheduled or to be executed, their flow diagrams and dependencies, both graphically as well as in a spreadsheet format, which can be exported out to a file or can be printed? If it is possible, how this can be done?

Hi Ashish,
The flows that have been built can be displayed using the "Show diagram" option (right click on job of flow, or on a job chain definition).
Tabular reports can be generated under the "Reports" option under Definitions.
Regards,
Anton.

Job scheduling

Hi Friends,
i have a problem with job scheduling.
two jobs need to be scheduled. (job1 and job2)
i used
job_open.
submit job1 using parameters.
job_close.
then for second job.
job_open.
submit job2 using parameter2.
job_close.
when i go and look in sm37. i see when job1 is running the job2 is in release status.
but what we need is when job1 is running job2 should be in schedule status. it should start only after job1 is completed.
in the job2 job_close i used job1 as the PRED_JOBNAME.
but i when i run the program job2 is in released status , not in schedule mode.
is there any way we can make the job2 in scheduled mode instead of release.
can we use event to control this. if yes please let me know how we can do it.
Thanks

Hi,
As Appana wrote - i'm not sure there's a problem, but why don't u make one job with 2 steps? this way u will be perfectly sure that job2 (2nd step in the new job) will run only after job1 (1st step n the new job)...
Good luck
Igal

Internal error occurs in background job scheduling

Hi Experts,
We are facing an error message "Internal error occurs in background job scheduling" while trying to execute a custom report(Z report) in background in SA38.
Please find the following observation on our side on this message.
1) This message is not coming for only one report not for others.
2) SU53 screen shot shows that SE38 check is failed, but the weird thing is not happening for other report.
3) Persons having SE38 auhtorization are able to run this report.
Please advise.
Thanks in advance,
Viven

What is the message ID and number? Have you tried OSS search and debugging?
What does this program do, in a nutshell?

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

Error in Backup job scheduling in DB13

Hi All
Backup job scheduled in DB13 kicks error ,I am using Oracle as database and ERP6.0
database and application are on diffrent servers.Before it was working fine,I didn't changed any password
I can run backupjob sucessfully directly from BRtools on database server.Please provide any hint
Job started
Step 001 started (program RSDBAJOB, variant &0000000000060, user )
No application server found on database host - rsh/gateway will be used
Execute logical command BRBACKUP On host DLcSapOraG08
Parameters:-u / -jid INLOG20090120204230 -c force -t online -m incr -p initerd.sap -w use_dbv -a -c force -p in
iterd.sap -cds -w use_rmv
BR0051I BRBACKUP 7.00 (31)
BR0128I Option 'use_dbv' ignored for 'incr'
BR0055I Start of database backup: bdztcorv.ind 2009-01-20 20.42.31
BR0484I BRBACKUP log file: D:\oracle\ERD\sapbackup\bdztcorv.ind
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance ERD failed
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance ERD failed
BR0056I End of database backup: bdztcorv.ind 2009-01-20 20.42.32
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0291I BRARCHIVE will be started with options '-U -jid INLOG20090120204230 -d disk -c force -p initerd.sap -cds -w use_rmv'
BR0002I BRARCHIVE 7.00 (31)
BR0181E Option '-cds' not supported for 'disk'
BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
BR0301W SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310W Connect to database instance ERD failed
BR0007I End of offline redo log processing: adztcorw.log 2009-01-20 20.42.32
BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
BR0005I BRARCHIVE terminated with errors
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.33
BR0292I Execution of BRARCHIVE finished with return code 3
External program terminated with exit code 3
BRBACKUP returned error status E
Job finished

Hi,
not sure if the recommendations given will address this issue.
You are getting this error:
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
the log file indicates:
> No application server found on database host - rsh/gateway will be used
This indicated that the user that is connecting from the AS to the DB server is not properly configured to perform the DB tasks on it.
So, first question would be to know if you have configured a gateway on the DB server and how, or if you are using remote shell.
Second question, you can do backups on the DB server.
> I can run backupjob sucessfully directly from BRtools on database server
How did you run exactly the backup job (what is the exact command line, what is the exact OS user that executed it)?
What is the OS of the DB server?
I have reread your post, your OS is windows therefore you fall in the "typical" error in Windows.
You have executed your backup as <sid>ADM and it works. Unfortunatelly, in windows, SAP is exectuted by SAPSERVICE<sid>, and this is the user who should be connecting to your DB server, and this is the user who cannot execute the backup.
The fact that you can run the backup with <sid>ADM in Windows does not means that you have SAPService<sid> properly configured.
For the error (see before) I think your ops$ user for this user is not properly configured in the DB server. take a look at the note mentioned by KT and pay attention to the SAPSERVICE<sid> configuration
Edited by: Fidel Vales on Jan 24, 2009 12:45 AM

Regarding Background Job scheduling for file to file scenario

Hi Guru's
Good morining all of u
I have one doubt on ...
can we do background job scheduling for file to file scenario?
Please give me response as early as possible.
thanks and regards
sai

background jobscheduling for file adapter...
you can schedule the file adapter according to your requirement as follows:
In the Communication Channel Monitoring Locate the link Availability Time Planning, In Availability Time Planning, choose the Availability time as daily and say create, give the time details, select the communication channel in your case file adapter , goto the Communication Channels tab and filter and add the respective channel, save it
/people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-

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

Hi any one please explain background job scheduling

Hi any one please explain background job scheduling . Good answer can be rewarded.
Thanks

Background jobs are pgms that are scheduled to be run in the Background without user interaction. So this can be done only for Type 1(executable) Program and not for Module-Pool Programs. Typically, a variant is defined and the pgm is run using the same.
The transaction code is sm36 -Define Background job. Using the Start Condition tab you can define when you want the job to run (specific time or if it has to follow after a particular job is done etc.,) Using the Step tab you can assign the pgm name and variant.
After the job is scheduled, you can check the status in sm37, along with the Job log and Spool.
For more info:
http://help.sap.com/saphelp_bw30b/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm

Background job scheduling for report

Hi can any one explain me how to do background job scheduling for report periodically for every 15 min.

Hi Rajesh thanks for your brief explanation.
but I am new to abap so I can't understand exactly will you please make it clear for the below program
REPORT zklj.
data: begin of itab occurs 0,
      partner type but000-partner,
      type     type but000-type,
      BU_SORT1 type but000-BU_SORT1,
      end of itab.
select partner type from but000 into table itab.
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
BIN_FILESIZE                    =
    FILENAME                        = 'd:\al1\ahaj.xls'
    FILETYPE                        = 'DAT'
APPEND                          = ' '
WRITE_FIELD_SEPARATOR           = ' '
HEADER                          = '00'
TRUNC_TRAILING_BLANKS           = ' '
WRITE_LF                        = 'X'
COL_SELECT                      = ' '
COL_SELECT_MASK                 = ' '
DAT_MODE                        = ' '
CONFIRM_OVERWRITE               = ' '
NO_AUTH_CHECK                   = ' '
CODEPAGE                        = '400'
IGNORE_CERR                     = ABAP_TRUE
REPLACEMENT                     = '#'
WRITE_BOM                       = ' '
TRUNC_TRAILING_BLANKS_EOL       = 'X'
WK1_N_FORMAT                    = ' '
WK1_N_SIZE                      = ' '
WK1_T_FORMAT                    = ' '
WK1_T_SIZE                      = ' '
WRITE_LF_AFTER_LAST_LINE        = ABAP_TRUE
SHOW_TRANSFER_STATUS            = ABAP_TRUE
IMPORTING
FILELENGTH                      =
TABLES
    DATA_TAB                        = itab.

Job Scheduling by Redwood workcenter

Similar Messages

Maybe you are looking for