Can someone tell me what the difference between backgroud processing and batch processing is. Also does the access to this function be limited.
I have a requrinment where they want everyone to have access to batch processing and just wanted to know how i should be handling this request.
Please help
Answer:
You have to get clarification from the requester. Most often Batch and background mean the same. There is a SAP useage which means Batch Data Communication ( BDC) that is sometimes refered to as Batch but most often refered to as BDC. Batch anf Background is controlles with S_BTCH_JOB and BDC is S_BDC_MONI. You need clarification fromt he requester.
Answer:
And if the user also has S_BTCH_ADM = Y and S_BTCH_NAM = DDIC (or *), then they can schedule the jobs, release, delete etc (as per S_BTCH_JOB actions permitted), but.. in the name of and with the authorizations of the other user names.
You can check with SUIM reports who can use your user account (for example) without having to know your password.
The myth that one cannot logon with a batch user is therefore true, because you don't need to logon with it...
Cheers,
Bob
Answer:
There is no myth about "loggin on to a Batch id" it does logon to run the batch job it just cannot be used in DIALOG mode. S_BTCH_NAM allows you to run a batch job using that users' access be it DDIC ( which should not have SAP_ALL) or any other id BATCH or DIALOG.
Answer:
There is no myth about "loggin on to a Batch id" it does logon to run the batch job it just cannot be used in DIALOG mode. S_BTCH_NAM allows you to run a batch job using that users' access be it DDIC ( which should not have SAP_ALL) or any other id BATCH or DIALOG.
It does logon, but unlike Communication users, the password is not critical for this login so you can change it. Like Communication users, one does not have to know what the password is... just access to see that someone once did and left it behind in the system. For Communication users one does not need to know the password either, but changing it, would make the access to the user more difficult.
Friday, February 13, 2009
Subscribe to:
Post Comments (Atom)
Archive
-
▼
2009
(74)
-
▼
February
(65)
- What database and operating systems are supported ...
- Cloning an SAP system
- Backups during upgrade
- Refreshing development system without losing syste...
- Methodology for creating indexes
- Determining the amount of data in a client
- Basic Knowledge and System Navigation Question
- SAP Background Job Administration
- background job failed because of authorization
- Background Jobs
- background jobs via background users
- Background Processing VS Batch processing
- Deleting a scheduled Background job
- Schedule Manager
- how you can assign a Background work process as a ...
- How To Delete a Scheduled Job
- Checking your program Background Job Status
- Availability Check on Quotation
- material Determination based on availability check
- Creating Multiple Materials in Material Determination
- Backward and Forward Scheduling
- Authorization Concept
- SAP’s TCODE checks with the authorization tool
- Listing TCODE transactions used to view what users...
- Authorization Check
- SAP BASIS (BC) Authorization Concepts
- Unlocking a blocked admin user ID in an Oracle DB
- How to Check Missing Authorisation for User
- SAP Profile Generator tables
- Query About Tcode PFCG
- How To Compare The Roles
- Creating New User With Authorizations
- Introduction on Authorizations
- Troubleshooting authorization in SAP R/3
- Shortcut to create role with many reports /tcode
- check which authorisation objects are checked with...
- What are the Authorizations Required
- How do I go about creating an authorization group?
- Frequently Asked Questions on Authorization
- What is an Authorisation Object?
- SAP Create authorization object
- SAP Creating an auth group and assigning a table
- SAP creating authorization levels
- SAP Creating Authorization profile
- SAP creating custamizing autharization objects
- SAP Creating new authorization object
- SAP Creating New Organizational Levels
- SAP S_TABU_LIN
- SAP S_TABU_LIN set up as organizational level
- SAP S_TCODE
- SAP S_TCODE check after upgrade to 4.7
- SAP s_tcode display only problem
- SAP S_TCODE is not in change mode
- SAP S_TCODE Lookup
- SAP S_TCODE with * Value
- SAp S_TRANSPRT versus S_CTS_ADMI
- SAP S_USER_ALL
- Auditor role/authorization
- SAP SU53 Authorization Check
- Authorizations
- System Administration: Authorization Concepts
- SAP Authorization Checks
- SAP Authorization Check
- What is authorization
- SAP auth/new_buffering
-
▼
February
(65)
Translation by Google
Subscription Free
Categories
- ABAP WORKFLOW
- Administration Faqs
- AIS - audit management preparation.sim
- AIS Implementation
- ALE
- ALE Scenario in SAP
- Alert Monitor(CCMS) in SAP
- Analyze Authorization
- Archive
- Archiving
- Auditing Information System
- Auth/new_buffering
- Authorization Concepts
- Authorizations Objects
- Availability Check
- Background Job
- Background Processing
- EDI and IDOCS
- Faqs
- Hot Packages
- Troubleshooting
No comments:
Post a Comment