Skip to main content

Posts

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
Recent posts

YINTERACTIVE_REPORT

*&---------------------------------------------------------------------* *& Report  YINTERACTIVE_REPORT *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT   yinteractive_report1  NO   STANDARD   PAGE  HEADING                               LINE - SIZE   60                               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. ** D A T A     D E C L A R A T I O N ** DATA  : it_mara   TYPE   STANDARD   TABLE   OF  ty_mara,        it_makt   TYPE   STANDARD   TABLE   OF  

Popular posts from this blog

SAP Table Structure T-codes

SAP table structure tcodes E11 - ABAP Dictionary Maintenance Basis - Dictionary Maintenance SE14 - Utilities for Dictionary tables Basis - Activation Program, Conversion Program, DB Utility, MC,  SPDDCU61 - Create table structure Cross Application - Object Dependencies CU63 - Display table structure Cross Application - Object Dependencies CU62 - Change table structure Cross Application - Object Dependencie CU64 - table structure List Cross Application - Object Dependencies LBWE - LO Data Ext.: Customizing Cockpit Logistics - Logistics Information System (LIS)RSA6 - Maintain DataSources Basis - BW Service APIRSO2 - Oltp Metadata Repository Basis - BW Service  APISE84 - Repository Information System Basis - Workbench Tools: Editors, Painters, Modelers SE38 - ABAP Editor Basis - ABAP Editor SE16 - Data Browser Basis - Workbench Utilities SM30 - Call View Maintenance Basis - Table Maintenance Tool SE37 - ABAP Function Modules Basis - Function Builder SE80 - Object Navigator

ABAP Code Inspector Tool

ABAP Code Inspector Tool The Code Inspector is a tool for checking static ABAP coding and DDIC objects . It helps developers to adhere to programming standards and guidelines by creating messages on less-than-optimal coding. The Code Inspector offers various possibilities to define object sets and to combine multiple single checks in so-called "check variants". Single object checks from the Development Workbench You can check a single object with the Code Inspector from the ABAP Editor (transaction SE38), the Function Builder (transaction SE37), the Class Builder (transaction SE24), or the ABAP Data Dictionary (transaction SE11). To do this, choose <object> > Check > Code Inspector from the menu, where <object> can be a program, function module, class, or table. Checks on transport objects from the Transport Organizer You can invoke the Code Inspector from within the Transport Organizer (transaction SE09) to check objects in a transport reques

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