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

ALV Field Catalog in SAP ABAP

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 the same line type as the dictionary structure, then the proxy instance
will automatically create the field catalog.
To do this, just pass the name of the dictionary structure to form using the parameter
'I_STRUCTURE_NAME'.
Semi-automatic field catalog.
All fields of the global structure type appears in the data table with the same name.
Now the requirement is to make changes to the dictionary structure or the additional columns
are to be displayed.
In this case we can call a function module (LVC_FIELDCATALOG_MERGE) that returns the field catalog
of the dictionary structure to a table of type lvc_t_fcat.
Now we can loop it and can make whatever changes we want.
Manual field catalog.
If the data table's line type does not contains the dictionary references or it only contains references to individual
global structure fields, you have to create the field catalog manually.
For this you have to create an internal table of type LVC_T_FACT and populate it manually.
SLIS_T_FIELDCAT_ALV.
SLIS_FIELDCAT_ALV.
..........................End..........................

Comments

Popular posts from this blog

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

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

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