Skip to main content

YCLASSICAL_JOINING

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

SAP Table Structure T-codes

Image
By
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 Basis - Repository BrowserFCC - Start Financial Customer Care -SLIS - FI-SL Spec.Purpose Ledg. Info.System FI - Information System
ST05 - Performance Trace Basis - Performance Monitors (TCC)
SE93 - Maintain Transaction Codes Basis - Workbench Tools: Editors, Painters, Modelers
RSA5 - Install Business Content Basis - BW Service 
APIPP01 - Maintain Plan Data (Menu-Guided) Basis - Organizational Management
SE16N - General table Display CO - ControllingPPOME - Change Organization and Staffing Basis - Organizational ManagementPPOMA_BBP - Change Attributes SRM - Enterprise/Business Partner Management
S001 - Basis - Session Manager
SE54 - Generate table view Basis - Table Maintenance ToolCORR - Collective Entry of Confirmations PP - Process Order
RSA2 - SAPI DataSource Repository Basis - BW Service
APISE12 - ABAP Dictionary Display Basis - Dictionary Maintenance
CK13N - Display Material Cost Estimate CO - Product Cost PlanningOKTZ - Cost Comp. Str (View Cluster Maint.) CO - Product Cost PlanningOMO1 - Update Maintenance: SIS Logistics - Logistics Information System (LIS)MCSI - Call Standard Analyses of Sales Logistics - Data CollectionMC94 - Change Flexible LIS Planning PP - Sales Plan
SE15 - ABAP/4 Repository Information System Basis - Workbench Tools: Editors, Painters, ModelersKEA0 - CO-PA: Maintain Operating Concern CO - Profitability AnalysisOLIX - Stat. Setup: Copy/Delete Versions Logistics - Logistics Information System (LIS)OLI7 - SIS Statistical Setup: Orders Logistics - Logistics Information System (LIS)PPIS - Human Resources Information System Personnel Mgmt - StaffingOLI9 - SIS Statistical Setup: Billing Docs Logistics - Logistics Information System (LIS)OOSP - Authorization Profiles Basis - Organizational ManagementOLI8 - Set Up SIS for Deliveries Logistics - Logistics Information System (LIS)ABAPHELP - Search ABAP Documentation Basis - Syntax, Compiler, Runtime
SE85 - ABAP/4 Repository Information System Basis - Workbench Tools: Editors, Painters, ModelersRKACSHOW - Display CO Cost Segments CO.

Comments

Post a Comment

Popular posts from this blog

ALV Field Catalog in SAP ABAP

By
ALV Field Catalog in SAP ABAP Field Catalog Field catalog is an internal table which is used to pass a list of fields to display in ALV report, we can set different properties to fields that will be display in ALV output. Type Group It is a data dictionary object which contains all the reusable user-defined types. Example for a type group is SLIS, which contains all the user-defined types for developing ALV reports. TYPE-POOLS is a keyword which is used to assign the type-group to a ALV report . Syntax : TYPE-POOLS SLIS . DATA : <IT_FCAT> TYPE SLIS_T_FIELDCAT_ALV . "INTERNAL TABLE FOR FIELD CATALOG DATA : <WA_FCAT> TYPE SLIS_FIELDCAT_ALV . " WORK AREA FOR FIELD CATLOG Field catalog types Field catalog: Field catalog is a format description of the display area. There are three procedures to build a FIELD CATALOG. 1. Automatic field catalog. 2. Semi-automatic field catalog. 3. Manual field catalog. Automatic field catalog. If the list structure has ...
Post a Comment
More

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

By
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 q...
Post a Comment
More

SAP had released a two versions for BPC 10.1; they are BPC 10.1 Classic and BPC 10.1 Embedded

By
SAP had released a two versions for BPC 10.1; they are BPC 10.1 Classic and BPC 10.1 Embedded. The Classic version can be considered an extension of previous versions in the BPC family, and can be used to implement both planning and consolidations solutions. The Embedded version utilizes Integrated Planning and BPC features, and is designed for planning only. Integrated Planning (IP) is a planning tool introduced by SAP before BPC came into effect. Let’s look some of the differences between the Classic and Embedded versions from a configuration perspective: 1. Master and transactional data objects Classic Embedded This version utilizes BPC objects i.e., Dimensions for master data and Models for transactional data. When data is saved in BPC, it will be stored in the SAP BW system under the namespace /CPMB. This method is similar to that used in earlier versions of BPC. This version uses the SAP Business Warehouse (BW) system and its objects directly. Characteri...
Post a Comment
More