Skip to main content

Posts

Showing posts from 2017

YCLASSICAL_JOINING

*&---------------------------------------------------------------------* *& Report  YCLASSICAL_JOINING *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT   yclassical_joining  NO   STANDARD   PAGE  HEADING                               LINE - SIZE   110                               LINE - COUNT   255                               MESSAGE - ID  z...

YCLASSICAL_JOINING

*&---------------------------------------------------------------------* *& Report  YCLASSICAL_JOINING *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT   yclassical_joining  NO   STANDARD   PAGE  HEADING                               LINE - SIZE   110                               LINE - COUNT   255                               MESSAGE - ID  z...

YINTERACTIVE_REPORT

*&---------------------------------------------------------------------* *& Report  YINTERACTIVE_REPORT *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT   yinteractive_report1  NO   STANDARD   PAGE  HEADING                               LINE - SIZE   60                               LINE - COUNT   255                               MESSAGE - ID  zsan....

Popular posts from this blog

ABAP/4 DEVELOPMENT STANDARDS

ABAP/4 DEVELOPMENT STANDARDS These slides covers Object naming standards, ABAP/4 Programming standards and procedures. These programming standards are intended to aid ABAP/4 programming in the SAP R/3 software development. Naming standards SAP provides their clients with a separate name space for their custom development so that during an upgrade no custom development will be lost (see OSS note 16466).Generally speaking, customer defined objects have to start with a ‘Y’ or ‘Z’.  Naming standards SAP provides their clients with a separate name space for their custom development so that during an upgrade no custom development will be lost (see OSS note 16466). Generally speaking, customer defined objects have to start with a ‘Y’ or ‘Z’.  Following, we will define the standards for the use in this Project. Program The following program naming conventions have to be followed for creating ABAP/4 programs, functions, includes and reports.  Refer to Maintai...

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...

Overview of ABAP Programming Language

 Overview of ABAP Programming Language Basic Syntax of ABAP *ABAP 4 is a programming language developed by SAP for the interactive development of application programming. *ABAP 4 is a fourth generation language. ABAP 4 is tightly integrated across all the modules viz like SD, MM, HR etc and most or all of the modules and transactions(like screens are created using ABAP). *All application programs, along with parts of the R/3 Basis system, are written in the ABAP Workbench using ABAP, Sap's programming language. The individual components of application programs are stored in a special section of the database called the R/3 Repository. The R/3 Repository serves as a central store for all of the development objects in the R/3 System ABAP Programs are objects of R/3 Repository. You maintain them using ABAP WorkBench Tool- in this case its ABAP Editor(Transaction SE38). R/3 applications are written in the ABAP programming language, and run within the application layer ...