Skip to main content

YCLASSICAL_JOINING

*&---------------------------------------------------------------------* *& Report  YCLASSICAL_JOINING *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT   yclassical_joining  NO   STANDARD   PAGE  HEADING                               LINE - SIZE   110                               LINE - COUNT   255                               MESSAGE - ID  zsan. ** T Y P E    D E C L A R A T I O N ** TYPES  :  BEGIN   OF  ty_mara,          matnr  TYPE  matnr,          ernam  TYPE  ernam,          pstat  TYPE  pstat_d,          END   OF  ty_mara,          BEGIN   OF  ty_makt,          matnr  TYPE  matnr,          spras  TYPE  spras,          maktx  TYPE  maktx,          END   OF  ty_makt,          BEGIN   OF  ty_final,          matnr  TYPE  matnr,          ernam  TYPE  ernam,          pstat  TYPE  pstat_d,          maktx  TY

Transaction Code For Basis Administration.

Transaction Code For Basis Administration.

SU01 User Maintenance
AL11 Display SAP Directories
SU01D User Display
BD54 Maintain Logical Systems
SU02 Maintain Authorization Profiles
OSS1 Logon to Online Service System
SU03 Maintain Authorizations
SALE IMG Application Link 
SU05 Maintain Internet users
SARA Archive Management
SU10 User Mass Maintenance
SICK Installation 
SMLG Maintain Logon Group
SM14 Update Program Administration
SUPC Profiles for activity groups
SM35 Batch Input Monitoring
SUIM Info system Authorizations
SM56 Number Range Buffer
PFCG Profile Generator
SM58 Asynchronous RFC Error Log
PFUD User Master Data Reconciliation
SM59 RFC Destinations (Display/Maintain)
S002 Easy System Administration Menu
SAINT SAP Add-on Installation Tool
ZAUT maintenance. Requesting new users, changing authorisation, etc.&nbsp
SPAM SAP Patch Manager (SPAM)
Client Administration
SPAU Display modified DE objects
SPDD Display modified DDIC objects
SCC3 Checking Client Copy Log
ST11 Display Developer Traces
SCC4 Client Administration
Daily monitoring TCodes:
SCC7 Client Import Post-Processing
SM04 User List
SCC8 Client Export
AL08 Current Active Users
SCCL Local Client Copy
SM12 Display and Delete Locks
SCC9 Remote client copy
SM13 Display Update Records
SM21 System Log
Database Administration:
SM50 Work Process Overview
SM51 List of SAP Servers
DB01 Analyze exclusive lock waits
SM66 System Wide Work Process Overview
DB02 Analyze tables and indexes
ST22 ABAP/4 Runtime Error Analysis
DB12 DB Backup Monitor
ST01 System Trace
DB13 DBA Planning Calendar
ST02 Setups/Tune Buffers
DB15 Data Archiving: Database Tables
ST04 Select DB activities (SQL Server Performance Analysis)
ST04 SQL Server Performance Analysis
ST05 Performance trace
DB50
ST06 or ST06N Operating System Monitor
RZ20
ST10 Table call statistics
Transport Management System:
ST03 Performance, SAP Statistics, Workload
SU56 Analyze User Buffer
STMS Transport Management System
STAD User transaction Analysis
SE01 Transport and Correction System
OS07N
SE06 Set Up Workbench Organizer
SM02 System Message
SE07 CTS Status Display
Other Monitoring Tcodes:
SE09 Workbench Organizer ( Release Transport )
SE10 Customizing Organizer
OS01 LAN check with ping
SE11 ABAP/4 Dictionary Maintenance
RZ01 Job Scheduling Monitor
SE16 Data Browser
RZ03 Presentation, Control SAP Instances
SE80 Repository Browser
ST07 Application monitor
SM30 Call View Maintenance
STAT Local transaction statistics
SM31 Table Maintenance
SFW5 - Change Business Function Status
SCC1 Transport Role from one Client to Other

Comments

Popular posts from this blog

BADI in SAP ABAP Step by Step

BADI in SAP ABAP Step by Step BAdI Acronym of Business Add Ins As a customer outsider, it helps BAdI to improve SAP functionality. Why is BADI? Unlike previous improvement methods, BADI continues the approach aimed at re-use objectives. BADI can be used in a number of times that these standard evaluation techniques can only be used once. For example, if you are upgrading a custom project, you can not map the extension on other custom projects. In order to overcome this disadvantage, SAP provided a new evaluation technique called BADI. Code of transaction for BADI definition: SE18 When you create a BAdI definition, you create a class interface automatically and you can define the methods in the interface. The application of the methods can be made in SE19 transactions. When created BAD, they are generated automatically: An interface with 'IF_EX_' is inserted between the first and second characters of the BAdi name Class classified as 'CL_EX_' inserted betwee

How to Create SAP ABAP Query Using SQ01 Step by Step Guide

How to Create SAP ABAP Query Using SQ01 Step by Step. You can create ABAP query objects ,if they are not exist in the SAP system. You can create SAP query without  ABAP programming knowledge. ABAP Query provides users with a variety of ways to define and create different types of  reports , such as  Basic Lists ,  Stats , and  Sorted Lists . ABAP query consists of four elements: Queries InfoSets Groups Translation query Queries The query component is used by end users for Queries. You can create queries, change and queries executed. Transaction  SQ01. Trnslation component / QUERY Many texts to define queries, InfoSets and user groups are generated. These texts are displayed in the language we choose to access the SAP system. We can compare the text or languages ​​that use this component. InfoSets InfoSets are the views of the Special Data Sources. An InfoSet Describes the fields of a data source that can be reported in the query. An InfoSet can be assig

BDC Recording in SAP ABAP

BDC Recording in SAP ABAP Here ,I explained The Steps to record any  Transaction (Example: VA01) to create BDC(Batch Data Communication) Program. Step 1  Execute transaction  SHDB  . Step 2  Enter  name  for recording  Step 3  Enter  transaction  to be executed Step 4  The transaction will now be executed, simply enter the values in the screen fields which you want to record.  Step 5  Once you have finished the recording and selected the  save  button or exit the transaction you  Creating an ABAP program Using a BDC recording   Go to SHDB Transaction Code and Click on New Recording. Give the Record name and Transaction code and click on Start New Recording Button. Now enter the Bank country and Key Now enter the Bank name ,City ,country and street.  Now Save the Recording . Now select the created record and click on Program. Now give the program title and select radio button transfer from recording. Now give the program title and click on