Skip to main content

YCLASSICAL_JOINING

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

Created structur transaction

Created structur transaction
UFD - Distribute Variant Functions
CU01 - Create Dependency
CU60 - Table Maintenance
CU02 - Change Dependency
CU65 - Create Function
CU21 - Create Dependency Net
CU61 - Create Table Structure
CU03 - Display Dependency
CU59 - Transfer Variant Table Contents
CU22 - Change Dependency Net
CU63 - Display Table Structure
CU05 - Dependency Where-Used List
CU04 - Dependency List
CU62 - Change Table Structure
CU23 - Display Dependency Net

Comments

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

What is BAPI in SAP ABAP with Example

What is BAPI in SAP ABAP with Example What is BAPI? The Business Application Programming Interface (BAPI) is a standardized programming interface (method) that allows external applications to access enterprise processes and R / 3 system data. BAPIs are defined in the Business Object repository (BOR) as SAP Business Object-type methods that perform certain business functions. They are implemented as RFC-compatible functional modules and are created in the ABAP Workbench function generator. Some BAPIs and methods provide basic functionality and can be used in most SAP business objects. These are called BAPI NORMALIZED. BAPIs for Mass Processing -ChangeMultiple(), CreateMultiple(), DeleteMultiple(). BAPIs for Reading Data - GetList() , GetDetail() , GetStatus() , ExistenceCheck(). BAPIs for Creating or Changing Data- Create() ,Change(),Delete() and Undelete() . They provide stable and standardized methods for perfect integration between the R / 3 system and external appli...