Collapse All Expand All

JAMS v. 6.4 introduced two new Execution Methods that support job execution processes using SAP.

• SAPJobV2 acts as a replacement for the current SAPJob and SAPStandardJob Execution Methods.
• SAPProcessChain provides process chain execution handling in JAMS

The two screenshots below highlights these new Execution Methods along with their respective Parameters.

 

 

 

Selection Criteria and Credentials in JAMS

The next screenshot shows the selection criteria and credentials required to retrieve a listing of available jobs in the SAP system that can be converted to JAMS Jobs.

 

Converting SAP Jobs to JAMS Jobs

Filtered jobs can now convert into JAMS jobs and placed in any JAMS folder as shown in the following three screenshots.

 

 

 

 

 Verifying the Job Conversion and Modifying Individual Job Steps in JAMS

All steps within converted SAP jobs can then be verified and examined in JAMS by opening the Job's properties Source tab, as shown in the two screenshots below.

 

 

Parallel Execution for JAMS and SAP Jobs

Once JAMS submits the Job, SAP then creates and executes a parallel job as shown in the following two screenshots.

Job Execution Logs

Once a Job executes, logs can be viewed from either the JAMS or SAP environments.

 

Authorized users may, in certain cases, cancel a currently executing Job. In SAP, such a job would go into a cancelled state. Logs can then be checked in both environments as shown below.

 

Running a JAMS Job using the SAPProcessChain Execution Method

When the user creates a Job using the SAPProcessChain execution method it is then submitted and executed normally in JAMS. The Job’s output includes a process chain number (log ID).

 The JAMS log file then displays the output of the process chain.

Using the SAP.Net Connector with the JAMS Adaptor

These permissions describe the necessary roles and permissions in SAP to allow users to run a Job using the new JAMS adapter.

SAP_BC_BATCH_ADMIN -- This role contains all authorizations for background processing administration, including the creation of background jobs and general administrations functions (SMxx transaction codes, in particular SM36, SM37, SM50, and SM51).

SAP_BC_ENDUSER -- This role contains non-critical basis authorizations for all users, including job creation and job release.

S_BTCH_ADM -- this role allows user the ability toPerform any operation on any job, including:

• Selecting jobs from all clients (from the Job Overview, Transaction SM37)
• Deleting any job
• Releasing jobs to start
• Changing jobs, including copying, canceling, checking, repeating, and capturing and debugging
•  Displaying jobs, job steps, and job logs
• Triggering events manually (transaction SM64)
• Editing system events
• Working with raised events in the event history (transaction SM62)
• Using restricted job classes A or B
• Scheduling an external program in a job

Five User Type are available in SAP. And as per SAP recommendations, the User should be “System”.

 

Type	Purpose
Dialog	Individual, interactive system access.
System	Background processing and communication within a system (such as RFC users for ALE, Workflow, TMS, and CUA).
Communication	Dialog-free communication for external RFC calls.
Service	Dialog user available to a larger, anonymous group of users.
Reference	General, non-person related users that allows the assignment of additional identical authorizations, such as for Internet users created with transaction SU01. No logon is possible.

Overview of the properties of users with different user types.

Property \ User Type	Dialog	Communication	System	Service
Dialog Logon (SAP GUI)	X	-	-	X
Multiple Logons	-	X	X	X
RFC Logon	X	X	X	X
Background Job Execution	X	-	X	X
Password Change	X	X	-	-
Logon Ticket can be Generated	X	X	-	-

 "x" represents Yes

 

 

---

Topic updated: 6/7/2017
©2017 MVP Systems Software, Inc. All Rights Reserved.

Send comments on this topic.