While implementing SAP R/3 System, we often using user exit or system modification to suit our company’s specific requirements. Sometime we may be necessary to create new data fields or to use standard existing fields in functions in addition. We may also have to develop new requirements and routines.
In my experiences, sales and distribution is one of module that has many variants business process. No wonder, SAP provides more user exits and routines for SD module than others. Read more… »
The LSMW ( Legacy System Migration Workbench ) is an R/3-based tool that supports us when transferring data from non-SAP systems (Legacy Systems) to SAP systems once or periodically. The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the SAP system via batch input, direct input, BAPIs or IDocs. Furthermore, the LSM Workbench provides a recording function that allows generating a “data migration object” in an entry or changing transaction. Read more… »
InfoCubes are the central objects of the multidimensional model in SAP BW, and basis cube is one of infocube type. Reports and analysis are based on these. An Info Cube describes a self-enclosed dataset for a business area from a reporting view, that is, for the reporting end user. Queries can be defined and/or executed in the basis of an InfoCube.
Following are InfoCube type’s inSAP BW:
- RemoteCube
- SAP RemoteCube
- Virtual InfoCube with Services
BDC (Batch Data Communication) recording is a method to transfer data form SAP system to SAP system or a non-SAP system to SAP system. This method is used to transfer large amount data that available in electronic form. It uses normal transaction code to transfer data.
There are two types of methods offered by SAP:
First method is called the “classical method”. In this method, data that is read by BDC program from a sequential dataset file is stored in a batch-input session. To run the transactions in the session, we need to execute session. We can start and monitor the session from menu System –> Services –> Batch Input or using transaction code SM35. This method uses the function module BDC OPEN, BDC INSERT and BDC CLOSE to generate the session. Read more… »
SAP creates customer exits for specific programs, screens and menus within standard SAP system. There four type of exits in SAP: Menu Exits, Screen Exits, Function Module Exits, and Field Exits.
There are mainly two reasons why we need to use user exits in SAP System: Read more… »
Here are step by step how to create Key Figure in SAP BW Info Object Tree.
1. In the initial screen of the Administrator Workbench, choose the function Area Modeling (transaction code: RSA1), and Info Objects.
2. Create or maintain an Info Area within the Info Object tree. Read more… »
Here are step by step how to create characteristic in SAP BW InfoObject Tree.
To meet the user requirements, sometime we must modify original SAP ABAP program code (known as enhancement) beside add some fields or Structures into SAP tables. We must register access key for the object first to modify original SAP program code, but actually we do not need it since SAP has been provide source-code plugins. Read more… »
In SAP BW, InfoObject is defined as the smallest available information entity or object. Technically, it is same as field in a table. InfoObjects are part of the SAP BW metadata repository. They describe the properties (technical definition and business logic) of the application field as shown on the following table. Read more… »
The Administrator Workbench (AWB) is the tool for data warehouse management in SAP BW (Business Information Warehouse). Using AWB we can manage, control and monitor all relevant objects and processes in SAP BW including scheduling, data load monitoring and metadata maintenance. Following are the functions that we can perform using AWB: modeling, monitoring, transport connection, documents, business content, translation, and metadata repository. Read more… »