Steps to enhance LO Datasource in SAP ECC

Enhance LO standard business content data source with a field not present in the data source extract structure

Scenario 1:

The field to be added in the LO Data source is not present in the extract structure but it is available in the communication structure.

Steps:

If the field to be added is available in the communication structure, no need to enhance the data source in such cases. You simply have to add that field from the communication structure into the extract structure. Continue reading “Steps to enhance LO Datasource in SAP ECC”

Generic Datasource extraction in BW from Master Data table in ECC

Generic Datasources / Extractors  – Cross Application (RSO2, SBIW)

Master data / Attributes extraction/ acquisition from SAP R/3 ECC (OLTP) to SAP BI (OLAP) using generic data sources – cross application

Eg. 1. Using a Database table

T-codes: SBIW, RSO2, SE11, SE16, RSA3, RSA7, RSA11, RSA13, RSA14, RSD1, RSDS, RSMO, RSMON, LISTCUBE, RSPC, RSPC1, RSPCM

Part 1: Data Modeling

Step 1: Logon to SAP R/3 system

Step 2: Check the data in the table

Enter tcode SE11 Continue reading “Generic Datasource extraction in BW from Master Data table in ECC”

How to create tables in SAP system-II

Creation of Transaction data table with variable currencies and units of measure

Method: Top down approach

Structure:

Continue reading “How to create tables in SAP system-II”

How to create tables in SAP System-I

There are three ways to create a table in SAP-

  1. Using Built in type or pre-defined type
  2. Using top-down approach (Table, Table properties, fields, data elements, domains, check fields, currency fields, technical settings,…)
  3. Using bottom-up approach (data, domains, data elements, table, table properties, fields with data element assignments, technical settings)

Creation of table:

Master data table creation using built-in type/pre-defined type-

Structure of the table

Continue reading “How to create tables in SAP System-I”

Definition of Data Dictionary in ABAP

A data dictionary in computing terms is the source of information in which the system data is defined in a logical way. The data dictionary is the centralized and structured source of information for business applications.

The ABAP data dictionary (DDIC) can be seen as a logical representation or a superior layer over the physical underlying database.

The elements that make up a DDIC are known as metadata. Metadata is the computing term for the data whose function is to describe other data.

An advantage of having a DDIC is avoiding inconsistencies when defining data types that will later be used in different parts of an application; this avoids redundancies and considerably decreases the cost of maintenance.

When a type of data is defined in DDIC, it is available to any program or function module in the application. A change in the definition of a type of data in the DDIC automatically affects any other data, module, function, or program which has data or variables defined using the modified data type.

The ABAP DDIC is the core of the R/3 development system. It is the source of every definition within R/3, from the very basic domains to the company model. It is totally integrated with the other tools of the development environment.

Transaction code SE11 for Data Dictionary and SE16 for Data Browser.

Data Dictionary Objects

abap-dictionary

  1. Database Tables
  2. Views
  3. Data Elements
  4. Structures
  5. Table Types
  6. Type Groups
  7. Domains
  8. Search Helps
  9. Lock Objects