Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

00057 - Problems with BDCUSER background jobs

00057 - Problems with BDCUSER background jobs

rdisp/max_wprun_time - Maximum work process run time   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Problems with BDCUSER background jobs

Hey Mike.

The transaction is SM35, "Batch Input: Session Overview".




Session Created byDate Time Lock date Authorizat.
Status Transact. Screens Queue ID
L103V1 SASMLEWI 12/13/2000 10:13:26 BDCUSER New
4,726 14,178 00121310132670
L103V1 AABBROWN 12/13/2000 09:47:44 BDCUSER In
background 4,726 14,178 01023500000128
L110H1A_1056 AABBROWN 12/13/2000 08:22:55 AABBROWN Errors
3 22 12130822557025

Also, the TYPE did change since we went to 4.6D. SU01 now looks like this:

User Type
. Dialog
. Service
. Reference
. System

We use the System type now as the Background type like in 4.6B. Its still
strange that it worked ok yesterday. We did just upgrade the kernel level
to 308 but there is nothing in OSS about this problem. Atleast my remote
client copy is finally working after 27 transports, 5 table deletes and
numerous field, table and domain activations........

Thanks














-----Original Message-----
From: Mike Martin, IS, Sousa [mailto:MMartinZs...]
Sent: Wednesday, December 13, 2000 1:16 PM
To: 'Sugg, Chris'; SAPLIST (E-mail)
Subject: RE: Problems with BDCUSER background jobs



Chris,

I assume that you meant 'SM36'? If so, set the type, via SU01 to
'background'. This value prohibits dialog signon for that user, but will
enable it to run batch jobs. Another user ID, of type 'Dialog', will be
required to schedule the job, but each step can still be assigned to
BDCUSER.

Another question, at least for 4.5B there is not user type called 'system'.
Is this a 4.6x user type?

Regards,
Mike D. Martin
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106
mmartinZs...


-----Original Message-----
From: Sugg, Chris [ mailto:aacsuggZn... <mailto:aacsuggZn...> ]
Sent: Wednesday, December 13, 2000 8:59 AM
To: SAPLIST (E-mail)
Subject: Problems with BDCUSER background jobs


We are having a problem with certain background jobs running. When the
developer submits a backgorund job per SM35, it ends and SM21 has this in
the log:


SM35 EF2 BP_STEPLIST_EDITOR: Invalid step values (step 1 ) found. Reason:
SM35 EFV > User BDCUSER cannot be scheduled due to its type
SM35 EFN BP_JOB_EDITOR: Job L103V1 is invalid. Reason:
SM35 EFT > Step 1 contains illegal values


BDCUSER is type SYSTEM, with all the roles that our developers have. I
found note 27255 (look at the bottom of the note for a chuckle!) and it
talks about background authorizations. Do these need to be added for
BDCUSER? If so, where? I can not add it in SU01 because it says it does
not exist. Does it need to be added to the report that submits the jobs?
This has just started happening. We also just applied lvl. 308 for the 4.6D

kernel and are at HP 11. Any suggestions???

Thanks


Chris Sugg
SAP Basis Administrator
NACCO Materials Handling Group
1400 Sullivan Drive
Greenville, NC 27834-2011
AACSUGGZN...
Phone: (252) 695-1912
Fax #: (252) 931-0934



[Non-text portions of this message have been removed]


Durban Tours - Südafrika Safari

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 4279 Date: 20230207 Time: 131430     sap01-206 ( 3 ms )