topic Re: BDC program is not working at SE36 in Application Development and Automation Discussions

BDC program is not working at SE36

Former Member — Mon, 26 Mar 2007 02:28:06 GMT

Hi members.

I made the BDC program. and i want that it's executed everyday. so I defined Background Job at SM36. Background Job worked successfully. but data wasn't changed. I did everything I could. but I don't know why data wasn't changed.

Strangely, When I executed the program at SE38 or SE80, it worked and data was changed. Is there any special thing on BDC program for Background Job at SM36?

Re: BDC program is not working at SE36

Former Member — Mon, 26 Mar 2007 02:51:45 GMT

Hi,

Can you tell me the transaction for which you have created the BDC...

Regards,

Komal.

Re: BDC program is not working at SE36

Former Member — Mon, 26 Mar 2007 02:59:14 GMT

Hyogil,

Pls. try to follow below steps to scheduled the background jobs.

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 “Send to SAP spooler Only for now”

b. Name – abbreviated name to identify the job output

c. Title – free form description for the report output

d. Authorization – 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 – set to appropriate department/functional area name. This field can be used in

a search later.

f. Retention period – set to “Do not delete” 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 job’s 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 “Parameters” button on a SAP Printer selection dialog, it

allows to specify all the parameters as described in p. 3 of

“Scheduling background jobs” 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 “Scheduling background jobs” section).

Access to report’s 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 “Further selection

criteria…” button (e.g. to bring “Spool request name (suffix 2)” 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 job’s outputs)

a. Spool request name (suffix 2) – corresponds to a spool name in p. 3.b in

“Scheduling background jobs” section above).

b. Date created – to find an output of a job that ran within a certain date range.

c. Title – corresponds to spool Title in p. 3.c in “Scheduling background jobs”

section above).

d. Department - corresponds to spool Department in p. 3.e in “Scheduling

background jobs” 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 “Print with changed attributed” button to print the spool request

with the different attributes (e.g. changing the printer name).

c. Click the “Display contents” button to preview the spool request contents. A

Print and Download functions are available from the preview mode.

Don't forget to reward if useful.....

Re: BDC program is not working at SE36

Former Member — Mon, 26 Mar 2007 04:17:24 GMT

good

you have to schedule the the job as per your requirement,so that the data ll change everytime you runthe BDC program.

Sometime is happens that when we run the program in background it didn't run properly,so check the length of the parameters that you r passing in the backgound.

Thanks

mrutyun^

Re: BDC program is not working at SE36

Former Member — Mon, 26 Mar 2007 04:37:57 GMT

Thanks for your concerns.

I created BDC codes at transaction SHDB, and finished the BDC program at SE80 using BDC codes. Please refer to the following.

REPORT myprogram.

PERFORM BDC_DYNPRO USING 'SAPLRHV5' '2000'.

PERFORM BDC_FIELD USING 'BDC_CURSOR'

'HRVPVF-FIXMAX'.

PERFORM BDC_FIELD USING 'BDC_OKCODE'

'=PROP'.

PERFORM BDC_FIELD USING 'HRVPVF-EV_SRK'

G_OBJID.

PERFORM BDC_FIELD USING 'HRVPVF-FIXOPT'

' '.

CALL TRANSACTION 'PV12' USING BDCDATA

MODE 'N'

UPDATE 'S'

MESSAGES INTO MESSTAB.

Re: BDC program is not working at SE36

Former Member — Mon, 26 Mar 2007 05:12:36 GMT

Try this once..

Define a variable of type ctu_params

data: CTU_PARAMS like CTU_PARAMS.

CTU_PARAMS-RACOMMIT = 'X'

then in Call Transaction add this parameter

CALL TRANSACTION 'PV12' USING BDCDATA

MODE 'N'

UPDATE 'S'

options from ctu_params

MESSAGES INTO MESSTAB.

Please let me know if it still does not work..

Regards,

Komal.

Re: BDC program is not working at SE36

Former Member — Mon, 26 Mar 2007 06:17:58 GMT

it doesn't work.

On activating the program, it showed syntax error message : You cannot use the "MODE" and "UPDATE" additions together with the "OPTIONS FROM" parameter.

So I erased the part of "MODE" and "UPDATE" . but I got the same result before.

it still doesn't work.

Re: BDC program is not working at SE36

Former Member — Mon, 26 Mar 2007 09:21:40 GMT

Could you check the logs.. to see if there is any system error.. in ST22 or in SM13