sapbi_bbp_v04.0 06-09-10

Enterprise Structure

SAP BI Business Blue Print

SAP Business IntelligenceBusiness Blueprint

Submitted to

For

By

August, 2010Version 1.0

__________________ ___________________

Mr. Saravana Kumar

Mr. Raghu KumarTeam Lead PP

Team Lead - MM

Lanco Industries Limited


__________________

__________________

Mr. Shanmuga Rajan

Mr. R S N Datta

Team Lead - MM

Team Lead - SD



_________________ __________________

Mr. Kodandapani

Mr. Kamal KanodiaTeam Lead - FI

Team Lead FI/SDLanco Industries Limited


___________________ ___________________

Mr. CA. Niranjan .M.N Mr. Ramesh Babu .MCoordinator - BI Project Manager



___________________

Mr. A R Surana

GM Finance & IT


__________________ __________________ Mr. Shashidhar Kothapally

Mr. Uthant Yaram

Project Manager

BI Team LeadvCentric Technologies Pvt Ltd

vCentric Technologies Pvt LtdDocument Information Project NameDocument Name

AarohanSAP BI Business Blueprint

Document HistoryVersionDocument NameDateAuthorReviewed by

1.0SAPBI_BBP_V1.03rd Sep 2010Mr. Shashidar K

Mr. Uthant Y

Table of Contents71.Executive Summary

71.2.Objective

71.3.Benefits

72.Project Scope

72.1.Deliverables Considered In Scope

82.2.Deliverables Considered Out of Scope

83.Introduction and Project Goals

83.1.Introduction

83.2.Goals

94.Approach

95.KPI Dimension Matrix

95.1.Key Performance Indicator (KPI):

95.2.Dimension:

95.3.KPI Dimension Matrix:

95.4.KPI Dimension Matrix (Layout):

105.5.Constraints & Considerations:

106.System Landscape Strateg

106.1.System Names

116.2.The BI Environment:

116.2.1.Development (BID)

116.2.2.Quality Assurance (BIQ), i.e. Testing

116.2.3.Production (BIP)

116.3.Source Systems for BI:

116.3.1.ECC 6.0:

116.3.2.SAP BI (My Self Data Mart)

116.3.3.File Interface:

126.3.3.1.Supported File Formats:

126.3.3.2.Source Locations:

127.SAP BI Transport Management System

127.1.Overview

138.ETL / Scheduling Strategy

138.1.Process Chain:

149.Appendix A KPI Dimension Matrices

149.1.Finance

149.2.Material Management

149.3.Sales & Distribution

149.4.Production Planning

1410.Appendix B - SAP BI Objects

1410.1.Master Data

1410.1.1.Master Data Objects

1510.2.Tansaction Data

1510.3.Finance (FI):

1510.3.1.FI InfoProviders

1510.3.2.FI DataSources

1610.4.Sales & Distribution (SD)

1610.4.1.SD InfoProvidors

1610.4.2.SD DataSources

1610.5.Material Management (MM)

1610.5.1.MM InfoProviders

1610.5.1.MM Data Sources

1610.6.Production Planning (PP)

1610.6.1.PP Infoproviders

1710.6.2.PP Data Source

1711.Appendix C SAP BI Data Flow

1711.1.Finance

1811.2.Material Management

1911.3.Sales & Distribution

1911.4.Production Planning

2012.Appendix D - SAP BI Glossary

2012.1.Administrator Workbench

2012.2.Business Explorer

2012.3.Characteristic

2012.4.Data Extraction

2012.5.Data Mapping

2012.6.Data Transformation

2012.7.Data Warehouse

2112.8.Dimension Table

2112.9.Fact Table

2112.10.Favorites

2112.11.InfoCatalog

2112.12.InfoCube

2112.13.InfoObject

2212.14.InfoPackage

2212.15.InfoSource

2212.16.Key Figure

2212.17.Master Data

2212.18.Meta Data

2212.19.Monitor

2312.20.OLAP

2312.21.OLTP

2312.22.Operational Data Store

2312.23.Primary Key

2312.24.Query

2312.25.Relational Integrity

2312.26.Scheduler

2312.27.Source System

2412.28.Star Schema

Table of Pictures

10Picture 1: Layout of KPI Dimension Matrix

Picture 2: SAP BI ECC System Landscape Strategy12Picture 3: Sample Process Flow13Picture 4: Finance Data Flow in BI17Picture 5: Material Management Data Flow in BI18Picture 6: Sales & Distribution Data Flow in BI19Picture 7: Productin Planning Data Flow in BI19

1. Executive Summary1.1. Overview

Lanco Industries has started the Business Intelligence Proof of Concept (BI POC) Implementation with vCentric Technologies to evaluate the Business Analysis, Reports, KPIs and performance management of ECC by using the Business Intelligence. So by using the BI the entire organisation will get End to End Solution 1.2. ObjectiveObjective of this SAP BI POC Implementation is to introduce the best practices of SAP BI to the management team of Lanco.

1.3. Benefits The value of SAP Business Intelligence is best demonstrated by applying it to real business problems. The SAP BI POC jumpstarts your evaluation, while at the same time giving you a better understanding of your performance management needs.

Our goal with the BI POC is to provide you with measurable and rapid results for a defined investment, both in terms of time and money. At the end of approximately 12 elapsed weeks (consisting of an estimated Four week of preparation time and Eight week of implementation), we will have:

A realistic understanding of how Business Intelligence can represent our KPIs , Business Analysis, Complex Reports and overall performance management requirements A review of your POC with our experienced consultant will give your organization a better understanding of the monitoring and analytics components of Performance Point Services.

The opportunity to see the analytical view of SAP ECC data With the BI POC you can also evaluate the SAP ECC Functional problems and you can also increase the ECC system performance by using the BI Reports. A complete BI Proof of Concept At the completion of this effort, you will have a POC that demonstrates how a BI solution can provide value to your organization and customers. The POC can also be used as the starting point for further design.

2. Project Scope

2.1. Deliverables Considered In Scope

The following actions and deliverables are considered within the scope of the BI-POC project:

1. Functional Areas Involved:

a. Material Managementb. Production Planning

c. Financed. Sales & Distribution

2. Identifying the Key Performance Indicator (KPI) metrics and the dimensions with the functional areas involved.

3. The extraction and one time load from Lancos ECC systems of all relevant detail and master data from the different data sources, to a historical depth subject to data availability or other project team defined constraints.

4. The design and development of BI-POC InfoCubes that will provide efficient and effective end users access to the identified KPIs in each functional area.5. Define ETL Strategy for the SAP BI Info Providers and the respective Master / Text Data.

6. Performance Tuning of the SAP BI the defined data model and the ETL flow.

7. The establishment of a technical environment supporting Business Intelligence processing, including the client landscape, transport management processes, desktop client management, naming conventions, distributed printing, security administration and end user and technical standards and procedures.

2.2. Deliverables Considered Out of Scope

The follow actions and deliverables are considered to be out of the scope of the BI-POC project, but may be considered for inclusion in a subsequent phase or project:

1. Development in the functional areas other than MM, PP, FI and SD.

2. Devolopment of BEx reports on top of the InfoProviders that are built.

3. Training on SAP BI Developments.

3. Introduction and Project Goals

3.1. Introduction

It is critical to understand that the BI-POC projects success is dependent not only on the delivered effort of the BI Project Team (both functional and technical) but also on support and delivered effort from the ABAP Team, the Basis Team and the Security Team

3.2. Goals

The Business Intelligence POC Implementation project has two major goals designed to support and compliment the decision making of the top management of Lanco Industries Limited.

These are:

1. To identify the KPIs in four functional areas i.e. SD, MM, FI and PP. For the identified KPIs, identifying the metrics that are measured against various dimensions within or cross functional area.

2. Building the InfoCubes in SAP BI according to the KPI-Dimension Matrix that is identified and finalized by Functional Team.

4. Approach

SAP BI team will conduct workshop to Lanco Industries senior management introducing the advantages and the best practices.

Meeting the heads of each department along with their Module Leads building the understanding on SAP BI and its features.

Understanding the requirement of HODs with the help of respective Module Leads.

Identifying the KPIs and the Dimensions in each functional area with the help of the requirements given by Module Leads

On receiving the initial requirement from the departments, prepare the KPI-Dimension Matrix for each department.

Review of KPI-Dimension Matrix along with respective Module Leads and finalize.

Review of KPI-Dimension Matrix with the Process Owner of Lanco Industries

For the identified KPI-Dimension Matrix, collect the source field information and the formulae to build the data model in SAP BI.

Bridge the gaps and freeze the requirements with the help of Module Leads.

Develop the InfoCubes in SAP BI according to the finalized requirements.

5. KPI Dimension Matrix

5.1. Key Performance Indicator (KPI):

KPI is the term used for a Key Perfomance Indicator i.e. is to measure the performance of an organization with some measures defined within a KPI. These KPI Metrics are measured against the meaningful dimensions pertaining to a particular functional area. 5.2. Dimension:

Dimension is a point of view to measure the organizational performance with the help of KPI Metrics in various areas of an organization.

5.3. KPI Dimension Matrix:

KPI Dimension Matrix is the consolidation and mapping of the entire KPI Metrics applicable to their respective dimensions. This document covers the entire KPI Metrics so that it can be the unique reference for building SAP BI Data Model for a particular functional area. This also helps us to identify the metrics that are measured across the other functional areas. 5.4. KPI Dimension Matrix (Layout):

This document divided into Rows and Columns. Each row represents a KPI Metric within a particular subject area (Module/Sub Module). Each KPI Metric can be either directly available in SAP ECC or it may be retrived through a defined formulae.

Picture 1: Layout of KPI Dimension Matrix 5.5. Constraints & Considerations:

Identify the KPI Metrics which are the key for top managements decision making

Eliminate the transactional level elements (both KPI Metrics & Dimensions) so that we can avoid duplication of detailed data in SAP BI.

Ensure that we are going to maintain the aggregated level information rather than the detailed level data in BI.

Business justification is mandatory for all KPI Metrics & Dimensions given in the document.

Define the Sources / Business Logic for the identified KPI Metrics and Dimensions so that the same can be incorporated into SAP BI. Otherwise it is not possible to accommodate it in SAP BI. (Ex: Source Fields in SAP, Formulae, etc..)

6. System Landscape Strateg6.1. System NamesThe following system names may be found in other SAP documentation. This section provides a cross-reference of the standard R/3 terminology and the System names used throughout this document.System NamePurposeLogical System NameSource System

BIDDevelopment (DEV)BIDCLNT444ECC DEV (CLNT 430)

BIQQuality Assurance (QAS)BIQCLNT555ECC QAS (CLNT 500)

BIPProduction (PRD)BIPCLNT666ECC PRD (CLNT 600)

6.2. The BI Environment:6.2.1. Development (BID)

All customizing and development work is performed in this system, (see above). Once all the changes have been unit tested, these changes can be transferred to the QAS system for further system testing. The customizing and development changes are transported using transport requests.

6.2.2. Quality Assurance (BIQ), i.e. Testing

After unit testing the customizing and development changes in the DEV system, the changes are transported to the QAS system. Here, the configuration is further tested and checked to ensure that it does not adversely affect other modules. When the configuration has been thoroughly tested in this system, and signed off by the Quality Assurance team, it can be copied to other system clients and to the PRD system.

6.2.3. Production (BIP)

The PRD is the system that a company uses for its production work. This system contains the company's live data and where the real business processes are performed. The other systems in the landscape must guarantee that defective programs or incorrect customizing configurations do not affect the production work.

6.3. Source Systems for BI:

SAP BI extracts the data from any of its source systems. Once the data arrives into SAP BI system, it will be stored in PSA (Persistant Staging Area). Data will be loaded from PSA to the data targets through required transformation mechanism. Current SAP BI system has the following three types of sources systems.

6.3.1. ECC 6.0:

As SAP ECC 6.0 is playing vital role in transactional data processing for Lanco Industries, this will act as a primary source of data. Data Extractors (Data Sources) will be built in ECC 6.0 to extract the data from the source tables in ECC system. These data sources will be replicated into SAP BI system for further mapping and transformations in BI system.6.3.2. SAP BI (My Self Data Mart)SAP BI acts like a source system for it self for internal data transfers. Ex: Data Loads from DSO to InfoCube, InfoCube to InfoCube, etc.

In this scenario, SAP BI source system is also called as SAP BIs My Self Data Mart.

6.3.3. File Interface:

Data can be uploaded into SAP BI in form of Flat Files. There is no physical existence maintained out of SAP BI. Rather, the File Interface Source System can be logically maintained in SAP BI.

6.3.3.1. Supported File Formats:

Any structured file format which is in CSV or Text File Format.6.3.3.2. Source Locations: Applicaton Server: There is a provision given in SAP BI to maintain the Flat Files. Respective file path should be identified while loading a particular file into the data targets. Files located in the application server can also be loaded in background. Also the files can be globally accessible from any client work station.Client Work Station: Other than the application server, we can also maintain them in the clients work station. But the background scheduling is not possible in this scenario. Moreover, files located in the client work station are not globally accessible.

Picture 2: SAP BI ECC System Landscape Strategy 7. SAP BI Transport Management System

7.1. OverviewThe SAP BI Transport Management system (formerly the Correction and Transport System) provides options for data transfer between and within R/3 Systems. The tool can be used, for example, to transport tuned and tested customizing settings between systems and clients.

The integration of the Transport Management System with customizing ensures that only individual table entries are transported, so that no unintentional transfer of test data will occur.

Using transport requests and customizing settings, development work developed in a separate DEV system can be automatically recorded in change requests and then transported into a quality assurance client and then into a production client. Once the change request has been released from the source system, it becomes a transport request.

If you do not want to record every change in a system (e.g. in a test client), the recording of customizing settings can be activated or deactivated for each client.

8. ETL / Scheduling StrategyRegular data feeds to SAP BI system will be taken care by process chains that are developed by SAP BI team and scheduled with regular intervals as required. 8.1. Process Chain:

Process Chain is a sequence of the data oploads and subsequent proceses that can be scheduled in background in SAP BI system. Process Chain takes care of the end to end data upload process until the information is ready for reporting. Picture 3: Sample Process Flow9. Appendix A KPI Dimension Matrices

9.1. Finance

9.2. Material Management

9.3. Sales & Distribution

9.4. Production Planning

10. Appendix B - SAP BI Objects

Data in SAP BI is divided majorly into two parts.

10.1. Master Data

Master data is globally unique which serves the entire reporting needs throughout the system. Following are the Important Master Data objects that are maintained in Current SAP BI system.

10.1.1. Master Data Objects

Sl NoObject NameDescription

10CUSTOMERCustomer

20MATERIALMaterial

30VENDORVendor

40PLANTPlant

50SALESORGSales Organization

60SOLD_TOSold to Party

70CUST_GROUPCustomer group

80STOR_LOCStorage Location

90COMP_CODECompany Code

100MATL_GROUPMaterial group

110GL_ACCOUNTG/L Account

120CHRT_ACCTSChart of accounts

130PRODORDERManufacturing Order

140S_OPERATSuboperation

150WORKCENTERWork Center/Resource

160WAGEGRWage Group

170PERSONPerson

180DT_ELEMENTDowntime Element

190PRODORDERManufacturing Order

200DOC_NUMBERSales document

10.2. Tansaction DataTransaction data is also called as historical data about the facts with respect to a functional area.

Ex: Sales Orders, Material Movements, Payments, Rceipts etc..

Transaction data is maintained in various InfoProviders in SAP BI. Data to loaded to these InfoProviders from the DataSources that exist in the Source System.

10.3. Finance (FI):

10.3.1. FI InfoProvidersSl NoObject TypeObject NameDescription

1InfoCube0FIGL_C10General Ledger (New): Transaction Figures

2InfoCube0FIGL_V10G/L (New): Balance Sheet and Profit and Loss

3InfoCube0FIAP_C03FIAP: Line Item

4DSO0FIAP_O03FIAP: Line item

5InfoCube0FIAR_C03FIAR: Line Item

6InfoCube0FIAR_C05FIAR: Payment History

7InfoCube0FIAR_C02FIAR: Transaction Data

8InfoCube0FIAA_C03FIAA: Transactions

10.3.2. FI DataSources


10FI_AR_3Customers: Line Items

20FI_AR_4Customers: Line Items with Delta Extraction

30FI_AR_5Customers: Payment History

40FI_AR_6Customer Sales Figures via Delta Extraction

50FI_AR_1Customers: Transaction figures

60FI_GL_10General Ledger: Leading Ledger Balances

70FI_AP_3Vendors: Line Items

80FI_AP_4Vendors: Line Items with Delta Extrcation

10.4. Sales & Distribution (SD)

10.4.1. SD InfoProvidors

Sl NoObject TypeObject NameDescription

1InfoCube0SD_C01Customer

2InfoCube0SD_C02Deliveries

3InfoCube0SD_C03Sales: Overview

4DSO0SD_O01Order Items

5DSO0SD_O06Billing: Condition Data

10.4.2. SD DataSources


12LIS_11_VAHDRSales Document Header Data

22LIS_11_VAITMSales Document Item Data

32LIS_12_VCHDRDelivery Header Data

42LIS_12_VCITMDelivery Item Data

52LIS_13_VDHDRBilling Doc. Header Data

62LIS_13_VDITMBilling Document Item Data

72LIS_11_VAKONSales Document Condition

82LIS_13_VDKONBilling Document Condition

10.5. Material Management (MM)

10.5.1. MM InfoProviders


1InfoCube0IC_C03Material Stocks/Movements (as of 3.0B)

2MultiProvider0IC_MP04Material Stocks/Movements

3InfoCube0PUR_C01Purchasing Data

10.5.2. MM Data Sources


12LIS_03_BFGoods Movements From Inventory Management

22LIS_03_BXStock Initialization for Inventory Management

32LIS_03_UMRevaluations

42LIS_02_SCLPurchasing Data (Schedule Line Level)

52LIS_02_HDRPurchasing Data (Document Header Level) as of 2.0B

10.6. Production Planning (PP)

10.6.1. PP Infoproviders


1InfoCubeL1CBPP001Production Analysis

2InfoCube0PP_C05Plan/Actual Comparison Material Consumption

10.6.2. PP Data Source


12LIS_04_P_MATNRMaterial View from PP/PP-PI

22LIS_04_P_ARBPL Work Center View from PP/PP-PI

Note: Objects in the above mentioned list are subject to customization or change during realization. 11. Appendix C SAP BI Data Flow 11.1. Finance

Picture 4: Finance Data Flow in BI11.2. Material Management

Picture 5: Material Management Data Flow in BI11.3. Sales & Distribution

Picture 6: Sales & Distribution Data Flow in BI11.4. Production Planning

Picture 7: Productin Planning Data Flow in BI12. Appendix D - SAP BI Glossary12.1. Administrator Workbench

The Administrator Workbench is the tool that you use to control how the data gets from the source systems into the InfoCubes of the Business Information Warehouse. The parts of the Administrator Workbench that you will need for the requesting and managing of the data include: Source system, InfoSource, InfoCube, InfoObject, Scheduler, and Monitor.

12.2. Business Explorer

The Business Explorer (BEx) is SAP Business Information Warehouse reporting tool.

In the Business Explorer Analyzer (BEx Analyzer) you define queries that are based on a selection of characteristics and key figures (InfoObjects) or of predefined query templates of an InfoCube. You analyze the selected InfoCube data by navigating in the query, where you generate different views of the data. You save the queries in workbooks and can assign these to one or more channels.

Using the Business Explorer Browser (BEx Browser) you access workbooks, that are assigned to you in channels. You select the workbooks with which you wish to work. You manage those workbooks with which you work frequently in your favorites.

12.3. Characteristic

A criterion to which data can be selected such as company code, product, material, customer group, fiscal year, period or region.

Characteristics provide classification possiBIlities for the dataset. The master data encompasses the permitted values of a characteristic, the so-called characteristic values. Characteristic values are discrete names. The characteristic region could, for example, have the values "North", "Central" and "South".

12.4. Data Extraction

Data Extraction is the process of loading data from source systems into the BI for reporting.

12.5. Data Mapping

This is the process of assigning source system data elements to target data elements in the Data Warehouse.

12.6. Data Transformation

Transformation is the process of modifying data for accuracy and completeness in BI. Transformations that are derived from business rules can be applied to elementary data in BI to prepare it for end-user reporting.

12.7. Data Warehouse

A database that contains summarized data from transactional data found in the OLTP system(s), ECC system(s) or other sources. The data store in the BI is designed for the efficient retrieval of data and for decision support reporting. The data are organized by subject area, and the data are time dependent. The data store contains figured quantities and dimensional data.

12.8. Dimension Table

A table in a star schema with a single part primary key is called Dimension Table

(e.g., customer key, product key, time key).

12.9. Fact Table

The fact table is at the center of the star schema of an InfoCube. The data part contains all key figures (also called "Facts") of the InfoCube and the key is formed by links to the entries of the dimensions of the InfoCube.

12.10. Favorites

Channel for workbooks with which a user works frequently. Users can copy workbooks with which they frequently work from the channels into their favorites. Users manage their favorites themselves and can individually name or group their content. Users can save modified or new workbooks in their favorites.

12.11. InfoCatalog

This is a tree-like structure in the Administrator Workbench that displays Business Information Warehouse workbooks and queries. The various InfoCatalog trees contain workbooks that SAP delivers, workbooks that can be used in an enterprise, workbooks that are used by certain user groups, workbooks that an individual user is allowed to use, and Favorite workbooks (user favorites), that a user has put together. The structure of the sub-trees can be freely defined by the administrator. A user accesses his or her queries of the InfoCatalog using the Business Explorer Browser.

12.12. InfoCube

This is the central data container for queries and evaluations. InfoCubes contain two types of data, namely key figures and characteristics.

An InfoCube is a number of relational tables, which are put together according to the star schema: a large fact table in the center, surrounded by several dimension tables. The fact table is set up in order to save all key figures on the lowest level of detail while the dimension tables are used to save the characteristics that are required both in reporting and in the evaluations of these key figures. Dimension tables are seen as being independent of one another. Only the fact table connects the dimensions with the key figures. Therefore all of the data is stored multi-dimensionally in the InfoCubes.

12.13. InfoObject

Generic term in the Business Information Warehouse for characteristics and key figures. InfoObjects are used in InfoCubes and the three structures relevant for the data request (extract structure, transfer structure and communication structure).

Names for InfoObjects can only be given once.

Within the characteristic a distinction is made between time and unit characteristics. Examples for characteristics would be evaluation groups such as cost center or product group.

Key figures are currency, quantity or number fields such as sales revenue, revenue or number of employees. Key figures usually refer to unit InfoObjects.

12.14. InfoPackage

This describes which data in an InfoSource should be requested from a source system. Therefore, the data can be precisely selected using selection parameters (for example, only controlling area 001 in period 10.1997).

An InfoPackage can request transaction data or attributes or hierarchies for master data.

12.15. InfoSource

An InfoSource is a quantity of information for a unit. This information has been grouped together and can be said to belong together logically from a business point of view. InfoSources can either contain transaction data or master data (attributes, texts, and hierarchies). An InfoSource is always a quantity of InfoObjects.

12.16. Key Figure

Values or quantities such as sales revenue, fixed costs, sales quantity or number of employees.

In addition to the key figures saved on the database, there is a possiBIlity of defining derived (calculated) key figures in the query definition in the Business Explorer. Such key figures are calculated using a formula from the key figures of the InfoCube. Examples of derived key figures are sales revenue per employee (sales revenue divided by number of employees), or variance as a percentage or the contribution margin.

12.17. Master Data

This is data that remains unchanged over a long period of time. Master data contains information that is needed again and again in the same way.

12.18. Meta Data

Meta data is data about data. This means that meta data describes the origin, history and further aspects of the data. The information that is stored in the SAP Business Information Warehouse can be effectively used for reporting and analysis via the meta data.

There are different classes of meta data: technical or business-oriented.

12.19. Monitor

Monitoring tool of the Administrator Workbench. Using the Monitor you can oversee the data request and processing in the Administrator Workbench. You will be shown the status of the IDoc processing in the various levels of the detail display. A distinction is made between two types of IDoc: Data IDoc and Info IDoc.

12.20. OLAP

On-Line Analytical Processing (OLAP) is software that is used to analyze summarized On-Line Transaction Processing (OLTP) data. OLAP allows multidimensional views and analysis of that data for decision support processes.

12.21. OLTP

On-Line Transaction Processing (OLTP) is used for operational data e.g. data in the R/3 software.

12.22. Operational Data Store

The Operational Data Store (ODS) is an integrated database that contains a copy of extracted data from source systems.

12.23. Primary Key

Key field or group of fields which form the unique identification of a record (a line) in a table.

12.24. Query

Collection of a selection of characteristics and key figures (InfoObjects) for the analysis of the data of an InfoCube. A query always refers to exactly one InfoCube, whereas you can define as many queries as you like per InfoCube.

You define a query by selecting InfoObjects or predefined query templates of an InfoCube and distributing them to filters, rows, columns and free (user-defined or drilldown) characteristics to create a view of the data. You insert the query in a workbook and can then create further views of the InfoCube data via navigation. You can save data for the current navigational state of the query in the workbook.

12.25. Relational Integrity

The observation of integrity rules governing the relational data model. These include primary key integrity, value range integrity, and foreign key integrity (referential integrity).

12.26. Scheduler

The Scheduler is the nexus between the source systems and the InfoCubes. With the Scheduler you determine which data is to be requested from the source system and at which point in time. The principle of the Scheduler relies on the functionality of the R/3 background job. The data request can either be started at once or with a background job and automatically at a later date.

12.27. Source System

All systems that are available in the Business Information Warehouse for data extraction. These can be SAP R/3 Systems (from Release 3.0D) and so-called external systems (for example, so-called third party tools or files).

12.28. Star Schema

A data structure that combines fact tables and dimension tables in a way that provides easy and efficient access to the data.

20vCentric & Lanco Industries Confedential

Page 2 of 24

_1345115359.xlsTransaction Data (2)

Sl NoSubject AreaMetricUOMFormulaFormulaRegionSizeClassGroupOrderCustomerCustomer GroupSchemeCal DayCal MonthFisc YearFisc PeriodAgentDestinationMaterialMaterial TypeDivision

1SalesAverage Realization / MTINR

2CIR (Customer Independent Req)MT

3CIR (Actual)MT

4Target Order QtyMTFilescsv file

5Actual Order Received Qty (MT)MT

6Actual Order Received Qty (Mtrs)Mtrs

7Commision AmountINR

8Average Commission/MTINR

9Freight AmountINR

10Freight (Rs/MT)INR

11Outstanding Receivable AmountINR

12Number of Orders (With Gasket)Count

13Number of Orders (Without Gasket)Count

14Number of GasketsEA

15Quoted Value of GasketsINR

16Actual Value of GasketsINR

17Credit AvailabilityINR

18Total CreditINR

19Fixed Cost of Production (Amount per MT)INRFiles

20Variable Cost of Production (Amount per MT)INR

21Total Cost of Production (Amount per MT)INR

22DispatchDispatch Qty (Planned)MTFiles

23Dispatch Qty (Actual)MT

24Dispatch Qty (Actual)Mtrs

25Deviation Qty (Planned - Actual)MT

26Deviation %%

27Planned Delivery Date

28Actual Delivery Date

29Order ValueINR

30Return Order ValueINR

31Fulfillment Rate%

Transaction Data

Sl NoSubject AreaMetricUOMSource / FormulaMaterialMaterial TypeSizeClassGroupOrderCustomerCustomer GroupRegionDivisionDestinationSchemeAgentCal DayCal MonthFisc YearFisc PeriodPayerSales Org.Ship to partySold to party

1SDAverage Realization (NSR) / MTINRTotal Sale Value / Total Sales in MT

2CIR (Customer Independent Req)MTTCode: MD83 & MD85

3CIR (Actual)MTTCode: MD83 & MD85

4Target Order QtyMTThrough Files

5Actual Order Received Qty (MT)MTTCode: VA43

6Actual Order Received Qty (Mtrs)MtrsTCode: VA43

7Commision AmountINRTCode: FB03

8Average Commission/MTINRTCode: FB03

9Freight AmountINRTCode: VA43

10Freight (Rs/MT)INRTCode: VA43

11Outstanding Receivable AmountINRTCode: FD10N from FI-AR

12Number of Orders (With Gasket)CountFrom Order Items

13Number of Orders (Without Gasket)Count

14Number of GasketsEA

15Quoted Value of GasketsINRTCode: VA03

16Actual Value of GasketsINRTCode: MM5B from MM

17Credit AvailabilityINRTCode: YCREDIT_LIMIT

18Total CreditINRTCode: YCREDIT_LIMIT

19Fixed Cost of Production (Amount per MT)INR

20Variable Cost of Production (Amount per MT)INR

21Total Cost of Production (Amount per MT)INR

22Dispatch Qty (Planned)MTThrough Files

23Dispatch Qty (Actual)MTTCode: YDISPREGNEW

24Dispatch Qty (Actual)MtrsTCode: YDISPREGNEW

25Deviation Qty (Planned - Actual)MTPlanned Disp Qty - Actual Disp Qty

26Deviation %%Deviatiaon Qty /Planned Dispatch Qty

27Delivery Qty (MT)MTTCode: YDISPREGNEW

28Delivery Qty (Mtrs)MtrsTCode: YDISPREGNEW

29Planned Delivery DateTCode: VL03N

30Actual Delivery DateTCode: VL03N

31Order ValueINRTCode: VA03 & VA43

32Return Order ValueINRTCode: VA03 Order Type: ZRTN

33Fulfillment Rate%

34Increase / Decrease in SalesINRDifference in period wise Sales AmountsTCode: VA03

35No of DocumentsNo.Count of Distinct Sales DocuemntsTCode: VA03

36No of Billing ItemsCount of Distinct Sales DocuemntsTCode: VF03

37Billed QtyTOTCode: VF03

38Billing ValueINRTCode: VF03

Formula: Total Sale Value / Total Sales in MTSimilar Logic has been already built in ECC. We can incorporate the same in BI. Transactions: YOABAL - OA Balance List

CIR Information can be retrieved from the transactions MD83 - Customer Independent RequirementMD85 - List of CIRs

CIR Information can be retrieved from the transactions MD83 - Customer Independent RequirementMD85 - List of CIRs

Target Order Quantities are fed from the Files into BI system

Transaction: VA43 - Display Contract

Transaction: VA43 - Display Contract

TransactionFB03: With respect to the GL Accounts

TransactionFB03: With respect to the GL Accounts

Transaction:VA43: Display Ordre

Transaction:VA43: Display Order

TransactionFD10N from FI-AR

All the Orders where it contains the item with Material Type ZGAS

All the Orders where it contains No item with Material Type ZGAS

Quantity of Gaskets within each Order.

Transaction: VA03: Value of the items of Material Type "ZGAS".

Transaction: MB5B: Actual value of the Gaskets based on Material Type " ZGAS" for a particular period

Data is retrieved from a custom report: YCREDIT_LIMIT:

Data is retrieved from a custom report: YCREDIT_LIMIT:

This is being uploadedinto BI through Files

Custom Report in ECC: YDISPREGNEW

Customer Report in ECC: YDISPREGNEW

(Dispatch Qty Planned - Dispatch Qty Actual)

Deviation Qty (Panned - Actual)/Planned Dispatch Qty

Transaction: YDISPREGNEW

Custom Report in ECC: YDISPREGNEW

Transaction: VL03N

Transaction:VL03N

Transacton: VA43 & VA03

Transaction: Order Value where the document type is "ZRTN"

Period wise difference of Sales Amounts.

Count of distinct Sales Documens

Count of distinct Billing Documents

Sum of the Material Quantities of the selected Billing Items

Sum of the values of the selected Billing Items

_1345117754.xlsSheet1

S/L No.Subject AreaMetricUOMSource / FormulaDepreciation Area for the AssetCompany codeControlling areaCost CenterProfit CenterSegment for Segmental ReportingG/L AccountAccount typeChart of accountsVersionCurrency TypeValue Type for ReportingValuation viewCustomer numberVendor #Dunning DataPayment DataDue DatesDocument TypeFiscal year / periodFiscal year variantCalendar MonthFiscal yearPosting periodWBS Elements

1FinanceTotal Debit PostingsINRTCode: FB03

2Total credit postingsINRTCode: FB03

3Cumulative BalanceINRTotal Debets - Total Credits

4Sales for the PeriodINRTCode: FAGLB03

5Flow ValueINR

6Profit/LossINRTCode: S_PL0_86000028

7Period wise Pofit and Loss (Actual/Actual) ComparisonINRTCode: S_PL0_86000028

8Period wise Pofit and Loss (Budget vs Actual) ComparisonINRTCode: S_PL0_86000028 Budgeted Figures from Files

9Stock ValueINR

10Balance Sheet ValueINRStock Value+Flow Value

11FI-AR: Payment Volume without Cash DiscountINRTCodes: FB03 & FD10N

12FI-AR: Average Arrears for Payment without Cash DiscountINRTCodes: FB03 & FD10N

13FI-AR: Number of Incoming Payments in the PeriodINRTCodes: FB03 & FD10N

14FI-AP: Payment Volume without Cash DiscountINRTCodes: FB03 & FK10N

15FI-AP: Average Arrears for Payment without Cash DiscountINRTCodes: FB03 & FK10N

16FI-AP: Number of Outgoing Payments in the PeriodINRTCodes: FB03 & FK10N

17DepreciationINRTCode: S_ALR_87012026

18Net Book ValueINRTCode: S_ALR_87011963

19Acquisition Value (wbs element)INRTCode: S_ALR_87011963

20Total Acquis.and Prod.Costs in Curr.Yr Incl. Invest. SupportINRTCode: S_ALR_87011963

21Net Book Value DifferenceINRTCode: S_ALR_87011963

22Difference in Accumulated DepreciationINRTCode: S_ALR_87012026

23Difference in Acquisition and Production CostsINRTCode: S_ALR_87011963

24Interest on LoansINRTCode: FAGLB03

FB03:This is a periodwise report

FB03:This is a periodwise report

Total Debits - Total Creditstaken fromFB03:This is a periodwise report

FAGLB03: Transaction for Cumulative Balances for Sales.

S_PL0_86000028 - Financial Statement: Actual/Actual Comparison

S_PL0_86000028 - Financial Statement: Actual/Actual Comparison (Comparison of 2 Periods)

Budgetted Figures are taken from the files into BI system and compared with Actuals that are existing in TransactionS_PL0_86000028 - Financial Statement: Actual/Actual Comparison Month wise

This can be retrieved from both the sources i.e. Tansactions FAGLB03 & MB5B

Formula: Stock Value + Flow Value

This information is gathered from both of the following transactions:FB03:Display DocumentFD10N: Customer Balance Display



This information is gathered from both of the following transactions:FB03:Display DocumentFK10N: Customer Balance Display

This information is gathered from both of the following transactions:FB03:Display DocumentFK10N: Customer Balance Display

This information is gathered from both of the following transactions:FB03: Display DocumentFK10N: Customer Balance Display

S_ALR_87012026 - Depreciation Current Year

S_ALR_87011963 - Asset Balances by Asset Number




FAGLB03: GL Accounts Balance Display

S_ALR_87012026 - Depreciation Current Year


Net Book Value Difference

Sheet2

Sheet3

_1345115360.xlsProduction KPI-Dimension Matrix

S/L No.Subject AreaMetricUOMSource / FormulaTimePlantMaterial NumberMaterial GroupMaterial TypeProductWork Center/ ResourceSales documentManufacturing OrderSub OperationReason for DeviationVendorBatch Number

1ProductionFinished ProductionMTTCode: MB5B(Movement Type: 101, 102)

2Production QuantityMTTCode: MB5B(Movement Type: 101, 102, 131, 132)

3Average Production/DayMTProduction Qty / No. of Days in the given Period

4Production Target (Planned)MTTCodes: MD61, MD62, MD63 for DIPMD81, MD82, MD83 for CIR

5No. of Production Daysnos.

6Estimated Saleable ProductionMTTCode: YREP:Total Prod Quality Product MT(ESP) = Total Prd MT- Total Rej MT

7Average Estimated Saleable Production/dayMTTCode: YREPESP / No. of Days

8Stock Quantity awaiting inspection (Stock in QI)MTTCode: QA32, MMBEMovement Types: 321,322'Stock Type: Q

9Unplanned Stock Quantity (Free Stock)MTTarget Production from CIR - Actual Production from ECC

10Stock Quantity extra produced (Against the Order)MTSales Order Qty(CIR) - Finished Production

11Total Length of pipe producedMtr.TCode: MB51Movement Type: 101, 102Value in Meters1. Size wise total length2. Total Length of Production

12Total tonnage of pipe producedMTTCode: MB51Movement Type: 101,102 in MT1.Size wise total MT2.Total Qty of Production in MT

13Total Number of pipes producedPcs.TCode: YREPOnly for Spining M/C-wise Pipes ProductionMovement Type: 131,132

14Cement Metal Lining WeightMT

15Total metal weightMTTCode: MM03Conversion Data, Material No.

16Backlog Quantity (Planned - Actual)MTCIR Qty - Actual QtyThis can be comparable monthly

17Total Rejected Percentage%YREP:% and MT1. Casting Rejection2.HPTM Rejection3.Total Rejection=1+24.Cost: MB51

18Gross WeightMTTCode: MM03

19Average WeightMTThrough Files

20Production Value of the quantityRs.TCodes: MFBF, CO03Movement Type: 131,132TCode: COOIS: Production Reporrt Order Value

21Product Rate per unitRs./pcs.

22Product Variable CostRs/MT

23Product Fixed CostRs/MT

24Product Total CostRs/MTVariable Cost + Fixed Cost

25Loss of Production Hours (Breakdown Time)Hrs.Notification: Planned Hours - Actual Production Hours

26Rejection QuantityMTTCode: YREP,Rejection Qty based on duration / key date

27Rejection%Total Rejection Tonnage / Actual Production

28Production Order QuantityMTTCode: COOIS

29Production Order ValueCurrencyTCodes: COOIS, CO03

30Material ConsumptionMTQuantity Based on Movement Type:201, 202, 261, 262

31Consumption Rate per MT ProductionKG/MT.ProdMaterial Consumption / No. of MT Produced

32Yield Percent%(Output Product Qty / Input Charging Qty) *100

33Break Down HoursHours/DaysThrough Files

34Target Capacity RequirementsHours

35Target Capacity Load UtilizationHours

36Actual Exec. TimeHours

37Target Execution TimeHours

38T/A Execution Time Deviation %Hours

39Norm ValueMTAvailable in Material BOM Data

40Actual ValueMTAvailable in Material BOM Data

41Diviation(Norm-Actual)MTNorm Value - Actual Value

42Overall Equipment Effectiveness %%(Availability % X Performace% X Yield %)/10000

43OE Performance %%((Actual Qty X Target Exc. Time Ex.)/(Target Qty X Actual Exe. Time Exact)) X 100

44OE Yield Percent%(Actual Qty/Total qty) X 100

45OE Availability %%100 X (Actual Processing Time)/((Actual Setup Time+Actual Processing Time+Actual Teardown Time))

46Coke Rate Kg/MT Hot MetalKG/MT.ProdCoal Consumption/One MT Prod. Of Liquid Hot Metal

47Blend Coal RatioRatioCoal Blends: 1. Prime Coal Blend (Prime Coal / 1 +2 +3+4)2. Hard Coal Blend (Hard Coal / 1+2+3+4)3. Soft Coal Blend (Soft Coal / 1+2+3+4)4. UHV Blend (UHV / 1+2+3+4)Transaction - MB51Movement Types: 201, 202, 261, 262

T-Code MB5BQty Restricted to Movement Type:101,102

T-Code MB5BQty Restricted to Movement Type: 131,132,101,102

Production QTY/Period which we select in dimention

Requirement:MD61,62,63, for DIPPlant CIR Reqirement :Md81,82,83NOTE: Repitative Manufacturing Pro.Planing copied from legasy

Total No. of Days No.of days data fedNote:Spinning M/C data will take

T-Code: YREP:Total Prod Quality Product MT(ESP)= Total Prd MT- Total Rej MT

YREP: ESP/No of Days

T-code: QA32: MMBE,321,322''Stock Type: Q

Target Prod form CIR-Actual Production in ECC.This is a monthly Report

Sales Order Qty(CIR)-Finished Production

MB51: 101,102 in meters1.Size wise total length2.Total Length of Production

MB51: 101,102 in MT1.Size wise total MT2.Total Qty of Production in MT

YREP:Only for Spining M/C-wise Pipes ProductionMovement Type: 131,132

MM03, conversion data,Material No.

CIR Qty-Actual Qty. This can be comparable on monthly base

YREP:% and MT1. Casting Rejection2.HPTM Rejection3.Total Rejection=1+24.Cost: MB51

MM03:

From Legasy systemwe will get

MFBF:Feeding DataMovement Type: 131,132COOIS: Production ReporrtCO03: Order Value

Variable Cost+ Fixed Cost

Notification:Planned Hours-Actual Produ. Hours

YREP:Rejection Qty based on duration,Key date

Total Rejection Tonnage /Actual Production.

T-Code: COOIS

COOISCO03

Quantity based on Movement Type:201, 202, 261,262

Material Consumption / No. Metric Tonn Produced

(Out Put Product QTY/In put Charging Qty)*100

Currently available from legasy

U Thant:

(Availability % X Performace% X Yield %)/10000

((Actual Qty X Target Exc. Time Ex.)/(Target Qty X Actual Exe. Time Exact)) X 100

(Actual Qty/Total qty) X 100

100 X (Actual Processing Time)/((Actual Setup Time+Actual Processing Time+Actual Teardown Time))

Coal Consumption/One MT Prod. Of Liquid Hot Metal

This available from BOM

This available from BOM

Norm Value - Actual Value

Coal Blends: 1. Prime Coal Blend (Prime Coal / 1 +2 +3+4)2. Hard Coal Blend (Hard Coal / 1+2+3+4)3. Soft Coal Blend (Soft Coal / 1+2+3+4)4. UHV Blend (UHV / 1+2+3+4)Transaction - MB51Movement Types: 201, 202, 261, 262

Overall Equipment Effectiveness %

OE Performance %

OE Yield Percent

OE Availability %

Dimension Structure

NameLevelsLevel IDLevel NameSample Member(s)Attribute

PlantPlantCoke Oven Plant, MBF, DIP, Cement, Captive Power PlantREASONS FOR LOW PRODUCTION

EquipmentsEquipmentSPM1, SPM2, SPM3, SPM4, SPM5, SPM6, SPM7, SPM8, I/F1, I/F2, I/F3, I/F4, I/F5, CON1, CON2, A/F1, A/F2, ZIN1, ZIN2, ZIN3,ZIN4, CML1, CML2, CML3, BIT1, BIT2, Cranes, Trolleys, Pump, Fan, Compressor, Process Eqpt, Boiler1, Boiler2, Turbine, Bat1, Bat2, Limestone crusher, Raw Mill, Kiln1, Kiln2, Drier, Cement Mill.

Maintenance TypeMaintenance TypePreventive, Breakdown

Maintenance PlantMaintenance PlantMechanical, Electrical and Instrumentation, Hydraulic

Work CentreWork Centre

Product1CategoryDI Pipe, BF Coke, Pig Iron, Cement, Power, Flange

2ClassK7, K9

3Diameter100mm, 1100mm

4CoatingZinc, Bitumen

Material TypeMaterialsStore & Spare Parts, Raw Materials, Finished Stock, Semifinished Product, Process Stock, Work-in-progress, Consumables,Item Code, Zinc Deposition, Zinc Type, Name of Outside Coating, Specification for the product to be produced, Inside Color of the Pipe, Outside Color of the Pipe, Type of Cement, Raw Material no., Cement Thickness, Zinc Thickness

Stock StatusStockStock-at-Port, In Transit, In depo, With Consignment Agent/Stock TRF

CustomerCustomer

ConsigneeConsignee

SupplierVendor

Delivery / ShipmentDeliveryDelivery OrderDelivery Order no., Delivery Instruction no., Excise Invoice Chalan, Commercial Invoice, Bundle/Carton Details, Country Name, Priority of the goods to be exported(Extra), Excise Inv. Date, Authorised Date

Q&A AgenciesInspectionInspection Agency

Cost CentreCost Centre

Time1Year2006, 2007, 2008

2Half YearHalf Year-1, Half Year-2

3QuarterQuarter-1,Quarter-2,Quarter-3,Quarter-4

4MonthJanuary, February, March

5WeekWeek-1, Week-2, Week-3

6DayDay-1, Day-2, Day-3

ScenarioActual, Budget

Assets

_1345115358.xlsMM

Sl NoSubject AreaMetricUOMSource / FormulaTIMEPlantProfit CenterTracking #MaterialMaterial GroupMaterial Sub GroupMaterial TypeBatchMRP Material TypeWBS ElementProjectMovement TypeStock TypeStorage LocationVendorPR #PO #Doc #MIR #MIRODoc TypePurchase GroupService #Service GroupRFQ NO

1MMValuated Stock QuantityTOTCode: MM5B

2Stock in Queue QuantityTOTCode: MMBE

3Stock in Transit QuantityTOTCode: MMBE

4Blocked Stock QuantityTOTCode: MMBE

5Stock in Quality Inspection QuantityTOTCode: MMBE

6Consignment Stock QuantityTOTCode: MMBE

7Receipt Stock QuantityTOTCode: MB51

8Issued Stock QuantityTOTCode: MB51

9Scrap QuantityTO

10Minimum Stock Level - QuantityTOTCode: YSTOCKREP

11Valuated Stock ValueINRTCode: MB5B

12Stock in Queue ValueINRTCode: MBBS

13Stock in Transit ValueINRTCode: MBBS & MMBE

14Blocked Stock ValueINRTCode: MMBE

15Stock in Quality Inspection ValueINRTCode: MB51

16Consignment Stock ValueINRTCode: MB51

17Receipt Stock ValueINRTCode: MB51

18Issued Stock ValueINRTCode: MB51

19Scrap ValueINR

20Opening Stock QTYTOTCode: MB5B

21Closing Stock QtyTOTCode: MB5B

22Raw Material Consumptiom QtyTOTCode: MB51

23Production QTYTO

24Opening Stock ValueINRTCode: MB5B

25Closing Stock ValueINRTCode: MB5B

26Raw Material Consumptiom ValueINRTCode: MB51

27Production ValueINR

28Minimum Stock Level - ValueINRTCode: MM03

29Moving Avg PriceINRTCode: MM60

30Last Period Moving Avg PriceINRTCode: MM03

31Last Year Moving Avg PriceINRTCode: MM03

32Scrap ValueINR

33Stock Holding (In Number of Days)No.sTCode: YSTOCK_HOLD

34Shelf Life of Materials (Days)No.sTCode: MB5M

35Ordered QtyTOTCode: ME2N

36Pending Order QtyTOTCode: ME2N

37Receipt QtyTOTCode: ME2N

38Ordered ValueINRTCode: ME2N

39Pending Order ValueINRTCode: ME2N

40Receipt ValueINRTCode: ME2N

41No. of PR sEATCode: ME5A

42No. Of Pending PR sEATCode: ME5A

43No. Closed PR sMTTCode: ME5A

44Material PriceINRTCode: ME23N

45Delay in DeliveryNo.s (Days)(Planned Delivery Date - Actual Delivery Date)

46Fulfilment Rate DeliveriesActual GR Qty %A PO Qty

47VdrCnsgnmntStck CnVlINR

48Average Stock ValueINR

49Inventory TurnoverRatioIssueVal. Valuated Stock /Average Stock Value

50Inventory Aging%Avg.Stck Value %A ValIssValStck

51Material Range of Coverage in DaysNo. of DaysValStckVal / ValIssValStock*365

52Proportion of Total Stock Quantity%Issue qty:Scrap %A ( Qty of Total Stock + Issu qty:Scrap)

53Proportion of Total Stock Value%Issue value:Scrap %A ( ValStockValue+ Issu value:Scrap)

54Consignment Stock at CustomerTOCnsgtStckQty (Stock Type: L M K)

55Issue Quantity: Consignment Stock at CustomerTOCnsgtStckQtyIssued (Stock Type: L M K)

56Receipt Quantity: Consignment Stock at CustomerTOCnsgtStckReceipts (Stock Type: L M K)

57Vendor Consignment StockTOCnsgtStckQty (Stock Type: K)

58Quality Parameters for Material (Norms vs Receipt)%TCode: YRMIREP

MB5B - Closing Stock Qty

MMBE

MMBE

MMBE

MB51

MMBE

MB51

MB51

MB51

YSTOCKREP

MB5B

MBBS

MBBS

MMBE

MB51

MB51

MB51

MB51

MB5B

MB5B

MB5B

MB51: 201,202,261,262.Material Type and Material Group

MB5B: 101,102.Material No.Material TypeMaterial Group

MB5B

MB5B

MB51

MB5B

MM03

MM60

MM03

MM03

MB5BMaterial No.Material TypeMaterial Group

YSTOCK_HOLD

MB5M

ME2N

ME2N

ME2N

ME2N

ME2N

ME2N

ME5A

ME5A

ME5A

ME23N

YRMIREP

Actual GR Qty Percentage in the purchase order qty: Actual GR Qty %A PO Qty

MB5B

MC44Valuated stock value based on calender day

Iss.ValStck/Avg.StckVal.MB5B

details

TIMEDAY

WEEK

MONTH

QUARTER

YEAR

PLANTPLNAT WISE

PROFIT CENTRE WISE

MATERIALMATERIAL NO

MATERIAL DESCRITPION

VENDORVENDOR NAME

VENDOR CODE

MATERIAL PRICE (Price Breakup)BASIC PRICE

DISCOUNT

P&F

CIF VALUE

EXCISE DUTY DEDUCTABLE

EXCISE DUTY NON DEDUCTABLE

VAT DEDUCTABLE

VAT NON DEDUCTABLE

SERVICE TAX DEDUCTABLE

SERVICE TAX NON DEDUCTABLE

CST

OTHER TAXES

OTHER EXPENCES

CD

CVD

ADD.DUTY

FREIGHT

LANDED PRICE

PURCAHSE ORDERDELIVERY DATE VRS ACTUAL RECEIPTS

PRICE BREAK-UP

FREIGHT VENDORS

FREIGHT CHARGES

SPECIFICATIONS

PO RELEASE STATUS / DATES

MINIMUM STOCK LEVELMINIMUM STOCK

BELOW MINIMUM LEVEL

BELOW AVG LEVEL

PUR GROUPWISE

PLANT WISE

MATERIAL MASTERMATERIAL CODE / DESCRIPTION

UOM

MRP MATERIAL TYPE*

PROFIT CENTRE

PLANT

MATERIAL TYPE

MATERIAL GROUP

MVG AVG PRICE

STOCK

CONSUMPTION DETAILS

MIN STOCK QTY

SHELF LIFE TIME

PO TEXT

VENDOR MASTERVENDOR CODE / DESCRIPTION

ADDRESS

LOCATION

STATE

CONTACT NOS

E-MAIL ID

PAYMENT TERMS

CURRENCY

DOMESTIC / IMPORT

VENDOR ACCOUNT?

CIN MASTERCHAPTER ID

MATERIAL CHAPTER ID COMBINATION

MATERIAL OUT PUT DETERMINATION

VENDOR STATUS

EXCISE CONDITIONS

PURCHASE REQUISITIONSMATERIAL CODE / DESCRIPTION

UOM

QTY

TRACKING NO

RELEASE CODE /DATES

DOCUMENT TYPE

PR STATUS

DOCUMENT NOSMIGO

MIRO#*

VARIOUS RECEIPT / ISSUE DOCUMENTS BASED ON MOV TYPE**

DOCUMENT DATE*

MOVEMENT TYPE*

MATERIAL CODE / DESC*

UOM*

QTY*

VALUE*

PO NO* for migo

PR NO*

RFQ NO*

VENDOR /CUSTOMER NO / NAME*

DOCUMENT REF NO / DATECFORM CANBE REMOVEDnot required

POSTING DATE

ACTUAL POSTING DATE*

DOCUMENT DATE*

TAXES*

OTHER DETAILSOther financial details for a PO

sapbi_bbp_v04.0 06-09-10

Documents

tansaction data

data mapping

data transformation

data warehouse

data sources

data extraction

meta data

pp data source