What is : Bex? | Variables? | AWB? | BIW | Flat file | Extractor?

* What is Bex?

* Bex stands for Business Explorer. Bex enables end user to locate reports, view reports, analyze information and can execute queries. The queries in workbook can be saved to there respective roles in the Bex browser. Bex has the following components: Bex Browser, Bex analyzer, Bex Map, Bex Web.


* What are variables?

* Variables are parameters of a query that are set in the parameter query definition and are not filled with values until the queries are inserted into workbooks. There are different types of variables which are used in different application: Characteristics variables, Hierarchies and hierarchy node, Texts, Formulas, Processing types, User entry/Default type, Replacment Path.


* What is AWB. What is its purpose?

* AWB stands for Administrtor WorkBench. AWB is a tool for controlling, monitoring and maintaining all the processes connected with data staging and processing in the business information whearhousing.


* What is the significance of ODS in BIW?

* An ODS Object serves to store consolidated and debugged transaction data on a document level (atomic level). It describes a consolidated dataset from one or more InfoSources. This dataset can be analyzed with a BEx Query or InfoSet Query. The data of an ODS Object can be updated with a delta update into InfoCubes and/or other ODS Objects in the same system or across systems. In contrast to multi-dimensional data storage with InfoCubes, the data in ODS Objects is stored in transparent, flat database tables.


* What are the different types of source system?

* SAP R/3 Source Systems, SAP BW, Flat Files and External Systems.


* What is Extractor?

* Extractors is a data retrieval mechanisms in the SAP source system. Which can fill the extract structure of a data source with the data from the SAP source system datasets. The extractor may be able to supply data to more fields than exist in the extract structure.

read more...

SAP Interview Questions | Difference between OLAP and Data Mining | Extended Star Schema | Drawbacks of SAP

* How can an ERP such as SAP help a business owner learn more about how business operates?

* In order to use an ERP system, a business person must understand the business processes and how they work together from one functional area to the other. This knowledge gives the student a much deeper understanding of how a business operates. Using SAP as a tool to learn about ERP systems will require that the people understand the business processes and how they integrate.


* What is the difference between OLAP and Data Mining?

* OLAP - On line Analytical processing is a reporting tool configured to understand your database schema ,composition facts and dimensions . By simple point-n-clicking, a user can run any number of canned or user-designed reports without having to know anything of SQL or the schema. Because of that prior configuration, the OLAP engine “builds” and executes the appropriate SQL. Mining is to build the application to specifically look at detailed analyses, often algorithmic; even more often misappropriate called “reporting.


* What is “Extended Star Schema" and how did it emerge?

* The Star Schema consists of the Dimension Tables and the Fact Table. The Master Data related tables are kept in separate tables, which has reference to the characteristics in the dimension table(s). These separate tables for master data is termed as the Extended Star Schema.


* Define Meta data, Master data and Transaction data?

* Meta Data: Data that describes the structure of data or MetaObjects is called Metadata. In other words data about data is known as Meta Data. Master Data: Master data is data that remains unchanged over a long period of time. It contains information that is always needed in the same way. Characteristics can bear master data in BW. With master data you are dealing with attributes, texts or hierarchies. Transaction data: Data relating to the day-to-day transactions is the Transaction data.


* Name some drawbacks of SAP?

* Interfaces are huge problem, Determine where master data resides, Expensive, very complex, demands highly trained staff, lengthy implementation time.

read more...

Open vs Native SQL | Writing BDC | Datasets | Interview Questions

* What should be the approach for writing a BDC program? - Convert the legacy system data to a flat file and convert flat file into internal table. Transfer the flat file into sap system called “sap data transfer”. Call transaction(Write the program explicitly) or create sessions (sessions are created and processed ,if success data will transfer).

* Explain open SQL vs native SQL? - ABAP Native SQL allows you to include database-specific SQL statements in an ABAP program. Most ABAP programs containing database-specific SQL statements do not run with different databases. If different databases are involved, use Open SQL. To execute ABAP Native SQL in an ABAP program, use the statement EXEC. Open SQL (Subset of standard SQL statements), allows you to access all database tables available in the R/3 System, regardless of the manufacturer. To avoid conflicts between database tables and to keep ABAP programs independent from the database system used, SAP has generated its own set of SQL statements known as Open SQL.

* What are datasets? - The sequential files (processed on application server) are called datasets. They are used for file handling in SAP.

* What are internal tables check table, value table, and transparent table? - Internal table: It is a standard data type object, which exists only during the runtime of the program. Check table: Check table will be at field level checking. Value table: Value table will be at domain level checking ex: scarr table is check table for carrid. Transparent table: - Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.

* What are the major benefits of reporting with BW over R/3? Would it be sufficient just to Web-enable R/3 Reports? - Performance — Heavy reporting along with regular OLTP transactions can produce a lot of load both on the R/3 and the database (cpu, memory, disks, etc). Just take a look at the load put on your system during a month end, quarter end, or year-end — now imagine that occurring even more frequently. Data analysis — BW uses a Data Warehouse and OLAP concepts for storing and analyzing data, where R/3 was designed for transaction processing. With a lot of work you can get the same analysis out of R/3 but most likely would be easier from a BW.

read more...

What is : IDES | WF | SAP R3 | Database \ Application Servers

* Can BW run without a SAP R/3 implementation? - Certainly. You can run BW without R/3 implementation. You can use pre-defined business content in BW using your non-SAP data. Here you simply need to map the transfer structures associated with BW data sources (InfoCubes, ODS tables) to the inbound data files or use 3rd part tool to connect your flat files and other data sources and load data in BW. Several third party ETL products such as Acta, Infomatica, DataStage and others will have been certified to load data in BW.

* What is IDES? - International Demonstration and Education System. A sample application provided for faster learning and implementation.

* What is WF and its importance? - Business Work Flow: Tool for automatic control and execution of cross-application processes. This involves coordinating the persons involved, the work steps required, the data, which needs to be processed (business objects). The main advantage is reduction in throughput times and the costs involved in managing business processes. Transparency and quality are enhanced by its use.

* What is SAP R/3? - A third generation set of highly integrated software modules that performs common business function based on multinational leading practice. Takes care of any enterprise however diverse in operation, spread over the world. In R/3 system all the three servers like presentation, application server and database server are located at different system.

* What are presentation, application and database servers in SAP R/3? - The application layer of an R/3 System is made up of the application servers and the message server. Application programs in an R/3 System are run on application servers. The application servers communicate with the presentation components, the database, and also with each other, using the message server. All the data are stored in a centralized server. This server is called database server.

read more...

SAP Interview Questions | What is ERP? | What is SAP? | Business Content | Why SAP?

* What is ERP? - ERP is a package with the techniques and concepts for the integrated management of business as a whole, for effective use of management resources, to improve the efficiency of an enterprise. Initially, ERP was targeted for manufacturing industry mainly for planning and managing core business like production and financial market. As the growth and merits of ERP package ERP software is designed for basic process of a company from manufacturing to small shops with a target of integrating information across the company.

* Different types of ERP? - SAP, BAAN, JD Edwards, Oracle Financials, Siebel, PeopleSoft. Among all the most of the companies implemented or trying to implement SAP because of number of advantages aver other ERP packages.

* What is SAP? - SAP is the name of the company founded in 1972 under the German name (Systems, Applications, and Products in Data Processing) is the leading ERP (Enterprise Resource Planning) software package.

* Explain the concept of “Business Content” in SAP Business Information Warehouse? - Business Content is a pre-configured set of role and task-relevant information models based on consistent Metadata in the SAP Business Information Warehouse. Business Content provides selected roles within a company with the information they need to carry out their tasks. These information models essentially contain roles, workbooks, queries, InfoSources, InfoCubes, key figures, characteristics, update rules and extractors for SAP R/3, mySAP.com Business Applications and other selected applications.

* Why do you usually choose to implement SAP? - There are number of technical reasons numbers of companies are planning to implement SAP. It’s highly configurable, highly secure data handling, min data redundancy, max data consistency, you can capitalize on economics of sales like purchasing, tight integration-cross function.

read more...

Material Types in Material Master

The following list shows you the material types contained, for example, in the standard SAP R/3 System, and what their different roles are:

DIEN (services)
Services are procured externally and cannot be stored. A material master record of this material type can always contain purchasing data.

FERT (finished products)
Finished products are produced by the company itself. Since they cannot be ordered by Purchasing, a material master record of this material type does not contain purchasing data.

FHMI (production resources/tools)
Production resources/tools are procured externally and used in the manufacture of products. A material master record of this material type can contain purchasing data, but no sales data. It is managed on a quantity basis. Examples of production resources/tools are apparatus, equipment, and measuring and testing devices.

HALB (semifinished products)
Semifinished products can be procured externally (sub-contracting) as well as manufactured in-house. They are then processed by the company. A material master record of this material type can contain both purchasing and work scheduling data.

HAWA (trading goods)
Trading goods are always procured externally and then sold. A material master record of this material type can contain purchasing and sales data.

HIBE (operating supplies)
Operating supplies are procured externally and required for the manufacture of other products. A material master record of this material type can contain purchasing data but no sales data.

NLAG (non-stock material)
Non-stock material is material that is not held in stock because it is consumed immediately. (Office supplies such as stationary. You need to create purchase order and accounting document for payment but the stock balance is always zero as it is issued out immediately to the various department.)

ROH (raw materials)
Raw materials are always procured externally and then processed. Since raw materials cannot be sold, a material master record of this material type contains no sales data.

UNBW (non-valuated materials)
Non-valuated materials are managed on a quantity basis, but not by value.

VERP (packaging materials)
Packaging materials are used to transport goods and come with the goods free of charge. A material master record of this material type is managed both on a quantity basis and by value.

WETT (competitive products)
Competitive products have their own material master records created from the Basic Data view. The competitor's number, which is stored in the material master record, assigns the material to a particular competitor.

read more...

List of SAP MM Transaction codes

Transaction for MM module start with M.

IH09 - Display Material
MM01 - Create Material
MM02 - Change Material
MM03 - Display Material
MM50 - List Extendable Materials
MMBE - Stock Overview
MMI1 - Create Operating Supplies
MMN1 - Create Non-Stock Material
MMS1 - Create Service
MMU1 - Create Non-Valuated Material

ME51N - Create Purchase Requisition
ME52N - Change Purchase Requisition
ME53N - Display Purchase Requisition
ME5A - Purchase Requisitions: List Display
ME5J - Purchase Requisitions for Project
ME5K - Requisitions by Account Assignment
MELB - Purch. Transactions by Tracking No.

ME56 - Assign Source to Purch. Requisition
ME57 - Assign and Process Requisitions
ME58 - Ordering: Assigned Requisitions
ME59 - Automatic Generation of POs

ME54 - Release Purchase Requisition
ME55 - Collective Release of Purchase Reqs.
ME5F - Release Reminder: Purch. Requisition

MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment

MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents

MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment

MBRL - Return Delivery per Mat. Document

MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents

MB1B - Transfer Posting

MIBC - ABC Analysis for Cycle Counting

MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock

MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock

MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock

MI21 - Print physical inventory document

MI04 - Enter Inventory Count with Document
MI05 - Change Inventory Count
MI06 - Display Inventory Count
MI09 - Enter Inventory Count w/o Document
MI34 - Batch Input: Enter Count
MI35 - Batch Input: Post Zero Stock Balance
MI38 - Batch Input: Count and Differences
MI39 - Batch Input: Document and Count
MI40 - Batch Input: Doc., Count and Diff.

MI08 - Create List of Differences with Doc.
MI10 - Create List of Differences w/o Doc.
MI20 - Print List of Differences

MI11 - Physical Inventory Document Recount

MI07 - Process List of Differences
MI37 - Batch Input: Post Differences

CT01 - Create Characteristic
CT02 - Change Characteristic
CT03 - Display Characteristic

CL01 - Create Class
CL02 - Classes
CL03 - Display Class
CL04 - Delete Class
CL2B - Class Types

read more...

Common tables used by SAP MM | SAP R/3 | Material Management

Below are few important Common Tables used in Materials Management Modules:

EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types

read more...

Material Management Table | SAP MM

Following are the list of Important MM tables. Please check if its useful.

Inventory Management:
|-------------------------+--------+-----------------------------------------|
| | Table | Description |
|-------------------------+--------+-----------------------------------------|
| Material | MSEG | Material document / transaction details |
| Document/Movements | MKPF | Material document header information |
|-------------------------+--------+-----------------------------------------|
| Material Stock Balances | MARD | Material stock |
| | MBEW | Material stock with valuation |
|-------------------------+--------+-----------------------------------------|
| Sales Order Stock | MSKA | Stock balance with associated sales |
| | | order data |
|-------------------------+--------+-----------------------------------------|
| Stock Transport | EKUB | Index for Stock Transport Orders for |
| | MDUB | Material |
| | | Reading View of Stock Transport Ord. for|
| | | Release Ord. |
|-------------------------+--------+-----------------------------------------|
| Special Stocks | MKOL | Consignment, material provided to |
| | | vendor, etc. |
|-------------------------+--------+-----------------------------------------|

Material Master Data:
|-------------------------+---------+--------------------------------------|
| |Table | Description |
|-------------------------+---------+--------------------------------------|
| Materials | MARA | General Data, material type, group, |
| | | configurable & batch ind. |
| | MAKT | Short Texts, descriptions |
| | MARM | Conversion Factors |
| | MVKE | Sales Org, distribution channel |
| | MLAN | Sales data, tax indicator, tax |
| | MARC | classification |
| | MBEW | Plant Planning Data |
| | MLGN | Valuation Data |
| | MLGT | Warehouse Management Inventory Data |
| | MVER | Warehouse Management Storage Type |
| | MAPR | Data |
| | MARD | Consumption Data |
| | MCHA | Pointer for Forecast Data |
| | MCHB | Storage location data with stock |
| | | balances |
| | | Batches |
| | | Batch Stocks |
|-------------------------+---------+--------------------------------------|

read more...