• SAP Tutorial
  • SAP Useful Resources
  • Selected Reading

Good morning,I was told that batch job entries that are made using SM36 are nottransportable to other systems QA, PRD or clients when theyve been donein DEV. Are there any tools or shortcuts. Double check that the first job is in scheduled status. Hit Own Jobs in the SM36 screen. Our job is in scheduled status. You have done the first part correctly. Also Read: How to create and change variant in SAP Production System without Fire Fighter Id.

Sap sm36 start status dependentSap sm36 standard jobs

Transaction codes are used in SAP for getting an easy access to custom applications or to call predefined processes. Transaction codes are a kind of shortcuts for different applications. Various categories of transaction codes are defined according to application area and modules. Some common and most widely used transaction codes are defined below.

ABAP / Tables / Data Dictionary

  • SE11 − Dictionary definitions

  • SE14 − Database utility

  • SE16 − Data Browser (display only)

  • SE16n − Modify: “&sap_edit” (uase16n)

  • SD11 − Data model

  • SM30/SM31 − SAP Table view maintenance

  • SE54 (SOBJ) − Table / View Cluster

  • SE37 − Function module editor

  • SE38 / SE39 - Program editor / split screen

  • SA38 − Program execution

  • SE80 − ABAP development workbench

  • SE84 − Object navigator

  • SE18 − BAdI definitions

  • SE19 − BAdI implementations

  • SE24 − Class builder

  • SWO1/2 − Business object builder / browser

  • SMARTFORMS − Smart forms administration

  • SE71 − SAP script (Form painter)

  • SE43 − Area menu maintenance

  • SE91 − Message maintenance

  • SE93 − Transaction maintenance

Runtime / Logs / Database

  • SM21 − System log sm13 Update requests

  • ST22 − ABAP Runtime Error (Dump)

  • SM12 − Table look entries

  • SM56 − Number range buffers

  • SNRO − Number ranges

  • SE30 − Runtime analysis

  • ST01 − System trace

  • ST05 − SQL Trace

  • DB02, ST04 − Database tools / performance

  • ST02, ST06 − Database tune summary

  • SCU3 − Table logging (see V_DDAT_54)

Sap Sm36 Job Wizard

Jobs / Batches / Events

  • SM36 − Job definition

  • SM37 /SMX − Job overview

  • SM50 − Process overview

  • SM34 − View cluster maintenance

  • SM49/SM69 − External commands

  • SM66 − Process overview

  • SM62/SM64 − Event overview / administration

  • STVARV(C) − Selection fields variables

User Administration

  • SM04 − User overview

  • SU53 − Check authorization data for user

  • SUIM − User information / authorization

  • SU20 / SU21 − Authorization object and class / field

  • SU01 − User maintenance PFCG roles

  • SU03 − Authorization Archive Development Kit (ADK)

Batch Input

Sap sm36 sm37

Sap Sm36 Table

  • SM35 − Batch Input: session overview

  • SHDB − Batch input recorder

Paths & Connections

Sap Sm36 Change Job

  • AL11 − SAP file directory

  • FILE − Logical file path

  • SM58 − Transactional RFC

  • SM59 − RFC connections

Sap sm36

Spool (Print Output)

  • SP01 − Spool request selection

  • SP02 − List of own spool requests

  • SPAD − Spool administration

Sap sm36 time restriction

SAP TCode (Transaction Code) - SM36

SAP TcodeSM36
DescriptionSchedule Background Job
PackageSBTI
Program NameSAPLBTCH
Screen Number2050
Transaction TypeT
ModuleBasis Components ► Use Subcomponents ► Background Processing

The SAP TCode SM36 is used for the task : Schedule Background Job. The TCode belongs to the SBTI package.

What Is Sap Sm36


SAP Background Processing Tcodes

TcodeDescriptionModule
SM36Schedule Background JobBC-CCM-BTC
SMXDisplay Own JobsBC-CCM-BTC
ESDLExternal Scheduler ApplicationBC-CCM-BTC
SM39Job AnalysisBC-CCM-BTC
SPBMMonitoring parallel background tasksBC-CCM-BTC
SM37Overview of job selectionBC-CCM-BTC
SM62Event History and Background EventsBC-CCM-BTC
SM69Maintain External OS CommandsBC-CCM-BTC
SM63Display/Maintain Operating Mode SetsBC-CCM-BTC
SBITBAPI Test EnvironmentBC-CCM-BTC
Full List of SAP Background Processing Tcodes