Term paper v2.pdf

Building a SAP Business Warehouse for Billing Analysis

Proposal for Research to Dr. X. Wu

University of North Carolina at Charlotte

Submitted by Bjarne Berg

in partial fulfillment of requirements for Data Warehousing course

Abstract

To be written…..

Table of Content

BACKGROUND .................................................................................................................................................................................. 3

APPROACH ....................................................................................................................................................................................... 3

TARGET ARCHITECTURE .................................................................................................................................................................. 4

DATA MODEL .................................................................................................................................................................................. 5

EXTRACT TRANSFORMS AND LOADS ............................................................................................................................................... 7

WEB TEMPLATE AND WEB REPORT ................................................................................................................................................. 7

SECURITY ROLES ............................................................................................................................................................................. 9

WORK CITED.................................................................................................................................................................................. 10

APPENDIX A: SAP – PRE-DELIVERD INFOCUBE, QUERIES AND SECURITY ROLES. .................................................................... 11

APPENDIX B: TRANSFER STRUCTURE MAPPINGS AND INFOSOURCE .......................................................................................... 16

APPENDIX C: .............................................................................................................................................................................. 19

Background

This paper outlines the experiences of building a SAP Business Warehouse (BW) data warehouse,

inluding the objects that is needed to support it. The project is absed on a functional specification given by

International paper and built on a BW system located at the consulting firm MyITGroup Ltd., in Houston.

The purpose of building this proof-of-concept was not for usage by either firm, but as a project assignment

and a subsequent term paper. The functional requirement outlines the need for a datastore to analyze billing

(invoices) as generated by the SAP R/3 transaction system.

These requirement was collected as part of the EDGE project at International paper, where the author

was a project manager in the information delivery sub-team. This project include the implementation of a

complete SAP suite for Supply Chain management, and the implementation of SAP at over 100 factories,

500 distribution centers and to about 91,000 users. The project, which has over 550 team members, started in

2003 and is expected to be completed in 2008. As part of this implementation, the project is also charged

with retiering several reporting systems that were connected to the old transaction systems. As a solution to

this, the decision was made in 2003 to implement SAP’s complementary decisions support system (BW) to

the transactional tool suite (R/3). As of today, the project has had 8 different go-lives and has implemeneted

many of the modules in-scope for certain business units. However, as new business units such as box plants

are added to the scope enhancements are made to the system quarterly to make sure that the new

requirements are being met.

Approach

The approach to this project followed the standard methodology of an SAP project. This included

gathering functional requirements (for this project, it was provided by a business analysts on the EDGE order

management team), followed by technical specifications (see appendecies), configuration and content

activation, building of querie(s), mapping to composite security roles and finally testing. This modified

system development life-cycle approach (SDLC) is known as the ASAP methodology as reccomended by

SAP. In a typical setting this approach required a peer review, a structured walkthrough of each delivereables

and an approvals in order to progress to the next phase (see figure XX). For simplicity reasons, this approach

was not followed and after a copy of the functional requirements was gathered from the business analyst. a

Rapid Application Development (RAD) approach was used instead,

(Figure xx: Standard Approach to DW development following the ASAP methodology)

Create Functional

specs

Peer Review

Complete?

Complete?

Peer Review

Complete?

Complete?Structured

walkthrough

Approved?

Configuration

Unit Testing

Integration

Testing

System Testing

Structured

walkthrough

Approved?

No

No

No

No

No

Yes

Yes

Yes

Yes

Yes

Yes

No

Create Technical

specs

Under this approach, the peer reviews are completed by co-workers engaged in similar activities in a

structured setting, typically weekly meetings. Normally, once an agreement is arrived at among the peers, the

team delivereable can be scheduled for a structured walthrough with the solution architect, or the software

engineering manger. This is a session where the responsible party of the deliverable present the proposed

solution, answers questions and obtains approval to submit the deliveravle to the next step in the process.

The configuration is a step where the appropriate standard content that the vendor (SAP) has delivered is

activated and then enhanced based on approved requirements and designs as outlined in the technical

specifications. In this step I added the 28 additional fields required into the extract programs installed on the

transaction system side, the transfer rules, the persistant storage area (PSA), the updated rules and process

chains that feeds the Operational Data Store (ODS), as well as the update rules that feed the InfoCubes (data

marts) within the overall architecture.

Target Architecture

The logical target data architecture is based on the conceptual view of the Corporate Information

Factory (CIF) as proposed by William Inmon and Claudia Imhoff in 2001. This conceptual view was earlier

adapted by PricewaterhouseCooper’s global data warehouse pracice in 1999 and is illustrated in figure XX).

The implemetation of this architecture from a SAP view consists of the ETL processing occuring in two

steps, known as Transfer rules and Update rules. The transfer rules are the mapping, cleansing and

validateion that occurs before the data was loaded into the Persistant Storage Area (PSA) and the Operational

Data Store. To maintain the reconsiliation ability back to the system or record (SOR), minimal cleansing

occurred in this area. The real data integration occurred from the ODS to the InfoCubes, in the update rules

(see ETL processing for more details).

(Figure xx: Logical Data architecture)

Metadata

Data

Extraction

Integration

and

Cleansing

Processes

Data

Extraction

Integration

and

Cleansing

Processes

Custom

Developed

Applications

Data

Mining

Statistical

Programs

Query Access

Tools

Custom

Developed

Applications

Data

Mining

Statistical

Programs

Query Access

Tools

Custom

Developed

Applications

Data

Mining

Statistical

Programs

Query Access

Tools

Data Resource Management and Quality Assurance

Summarized

Data

Segmented

Data Subsets

Summarized

Data

Segmented

Data Subsets

Functional Area

Summation

Marketing

and Sales

Purchasing

Corporate

Information

Product Line

Location

Functional Area

Summation

Marketing

and Sales

Purchasing

Corporate

Information

Product Line

Location

Purchasing

Systems

Invoicing

Systems

General

Ledger

External Data

Sources

Other Internal

Systems

Purchasing

Systems

Invoicing

Systems

General

Ledger

External Data

Sources

Other Internal

Systems

Purchasing

Systems

Invoicing

Systems

General

Ledger

External Data

Sources

Other Internal

Systems

Translate

Attribute

Calculate

Derive

Summarize

Synchronize

Translate

Attribute

Calculate

Derive

Summarize

Synchronize

Translate

Attribute

Calculate

Derive

Summarize

Synchronize

Source Data Extract

Operational

Data Store Transform

Data

Warehouse Applications

Source: Bjarne Berg, “Introduction to Data Warehousing”,

Price Waterhouse Global System solution Center, 1997

Data Model

As part of a study from International Paper, I reviewed the functional specification as provided by the

business analyst on the project and determined together with him the additional fields that was needed to

build the InfoCube to analyze billing docuements and associated attributes and entities. This effort was

followed by a definition of each field. The fields requested in the functional reporting specifications, but

which were not available in the standard BW contecnt as provided by SAP, are listed in table 1 below.

(Table 1: Enhanced fields to standard content and definitions)

Entity Name Attribute Name Definition

Accounting Account assignment group The group internal to the organization where this account has been assigned (i.e.

profit center or cost center).

Accounting Profit center A general ledger account that identifies a sub-set of the organization.

Billing MSF Thousands of square feet of sold items (roll length x roll width)

Billing Numeric ERDAT The julian date of when the order was entered

Billing Numeric FKDAT The julian date of when the bill was created

Billing information ~ Batch billing indicator A navigational attribute to indicate if the account is billed periodically.

Billing information Cancelled billing doc An indicator to show is the bill has been cancelled (all line itmes).

Billing information Debit/credit reason code A code to show why a debit or credit was generated against this bill.

Billing information Output medium Shows if the bill is created as PDF, EDI, paper, PS or doc format

Billing information Payment terms Shows when the bill should be paied and what pre-paid discounts may be applied.

Billing information Pricing procedure Contains the numeric indicator for how the bill was generated and what taxes were

applied. This is the PK for the procedure table.

Billing information Reference document Any contract or external document that is basis for this bill

Customer ~ Customer country Navigational attribute to show the customer country location

Customer ~ Customer industry cd 1 Navigational attribute to show the customer's SIC code (1st priority).

Customer Customer industry code 2 Attribute to show the customer's SIC code (2nd priority).

Customer Customer industry code 5 Attribute to show the customer's SIC code (5th group code).

Customer ~ Customer postal code Navigational attribute to show the customer's local postal code

Customer ~ Customer region Navigational attribute to show the customer' region locatio based on the sales

organizational hierarchy.

Customer Credit account The G/L account to credited for this sale

Customer Customer class The customer class based on Key, Preferred, Value & general

Customer End user The end user of the products. Used to track re-sales through distributers

Document details Sales order document type Shows if the sales order that is basis for the bill was generated, contracted,

autoship, VMI or requested.

Material Customer PO number The Purchase order placed by customer (non-native SAP number).

Material Material class The group of material being billed (see material hierarchy -BOM)

Organization Sales channel The type of channel being used to generate the sales. This comes from the sales

order based on the sales organizational hierarchy.

Personnel Account executive The identifier of the sales manager assigned to the customer

Personnel Agent The identifier of the sales person who executed the sales order.

Document details Sales document category A logical gruping of sales order types.

After reviewing the standard InfoCube as provided by SAP, a logical dimensional model using

Information Engineering notations and ERWin as a modeling tool was created. This was followed by a

mapping of the nehaced fieldws to the logical dimensions of the model. The next step was to map the

enhanced fields to see if they existed in the Logistics Cockpit (a SAP ETL tool with pre-delivered content),

or if the fields existed only in R/3, but was unavailable on the standard extractor or the LO cocpit. A color

coding scheme was used to identify these differences in the resulting data model. The modeling format was

used to only show the logical dimensions (dependent on the transactions), as well as the transactional values.

It is important to note that additional masterdata attributes that explains hundreds of fields for entities such as

material and customer is also available for the infocube, but since these are treated as conformed masterdata

tables, they are not depicted in the infocube model. The same is true for time-dependent hierarchies and

alternate hierarchies that are shared across InfoCubes.

(figure xxx: The logical star-schema and enhanced field mapping

Billing

Number of billing documentsNumber biling line itemsBilled item quantityNet weightSubtotal 1Subtotal 2Subtotal 3Subtotal 4Subtotal 5Subtotal 6Net valueCost standardTax amountVolumeNumeric ERDATNumeric FKDATMSF

Customer

Sold-toShip-toBill-toPayerCustomer classCustomer group~ Customer country~ Customer region~ Customer postal code~ Customer industry code 1End userCustomer industry code 2Customer industry code 5Credit account

Material

Material numberMaterial enteredMaterial groupItem categoryProduct hierarchyMaterial classCustomer PO number

Time

Calendar yearCalendar monthCalendar weekCalendar day

Unit

Currency KeyUnit of MeasureBase unit of measureSales unit of measureVolume unit of measureWeight unit of measure

Billing information

Billing documentBilling itemBilling typeBilling categoryBilling dateCreation dateCancel indicatorOutput medium~ Batch billing indicatorDebit/credit reason codeReference documentPayment termsCancelled billing documentPricing procedure

Organization

Company codeDivisionDistribution channelSales organizationSales groupSales officeSales districtSales channel

Logistics

PlantShipping/receiving point

Document details

Sales order document typeSales document categorySales document

Accounting

Cost centerProfit centerControlling areaAccount assignment group

Personnel

Sales rep numberAccount executiveAgent

LEGEND

Delivered in standard extractorsDelivered in LO extractorNot in delivered Content -but in R-3

(figure xxx: Available hierarchies and navigational attributes).

InfoObject Description Navigation attributes available? External hierarchy available?

0D_CO_CODE Company code Yes No

0D_COUNTRY Country Yes No

0D_DIS_CHAN Distribution channel No No

0D_DIV Division No No

0D_INDUSTRY Industry code Yes No

0D_MATERIAL Material Yes Yes

0D_MTLGROUP Material group Yes No

0D_PROD_HIE Product hierarchy No Yes

0D_SALE_EMP Sales employee No No

0D_SALE_ORG Sales organization No No

0D_SOLD_TO Sold-to party Yes No

0D_VERSION Version No No

Extract Transforms and Loads

The Data being populated into the infocube is being extracted from the source system and poupluated

in a transfer structure (table) on the source system, which is SAP R/3. This transfer structure is replicated

inside the Persistant Storage Area (PSA) of SAP BW. This allowes the movement between thsese structures

and also manipulation of the data values through transfer rules. The combination of the extract programs that

maps tables inside R/3, the transfer structures that stores that data temporary on the R/3 and the BW side, as

well as the ransfer rules are collectivly known as “InfoSources”. SAP BW provides hundreds of pre-

delivered InfoSources that has to be enhanced based on customer needs. In this project, the trasfer structures

and the extractor programs (refered to as “extractors”) where enhanced to accomondate the data extraction of

the 28 additional fields added to the ODS and the InfoCube (SD_C05). In the update rules additional unit of

measures was added based on the posting keys. This included adding the sales unit of measure, the volume

unit of measure and the weight unit of measure.

These are standard fields provided by SAP, but which resides on the material masterdata and

therefore had to be looked up based on the base unit of measure before it was added back to the InfoCube

(see the ‘unit’ dimension in the data model for details). Additional calculated key figures (CKF) and

Restrictive Key figures(RKF) was added to measure returned items. This included to look at negative unit

postings (returns) and present these to the OLAP processors for the queries as an available measure that

could be included as a separate field on the query (see figure xx). These key figures were not physically

stored in the cube, but defined and made available at run-time to the query development. I did not add any

virtual key figures to the system (VKF).

Web Template and Web Report

A web report was developed using the SAP Business Explorer (BEx) query designer. This tool

created a graphical user interface based on the data source (i.e. InfoCube) that the tool was connected to

(infocube SD_C05). For this project I used the dimensions given in this InfoCube as well as attributes from

the masterdata that was extracted into the masterdata (not depicted in the data model cince it is seperated

from the InfoCube). Since the Infocubes can access the fact tables, the dimensions as well as the masterdata,

a query can contain hunders of fields that can be navigated to and conditioned. The challenge was therefore

to create a system where the optimal initial interface is accessed. This will reduce the number of naviational

steps users had to take before the query became useful. It is important to note, that the user could also create

“favorites” based on the navigational steps and therefore can have his/her’s own version of the global query

and its default view.

(figure xxx: The SAP Business Explorer Query Designer_(Bex)

The next step was to publish the query into a global web template. The effort of creating a web

template is quite large. It is also a one time effort that a data warehouse developer would normally not be

involved in. The web template used for this puspose had previously been developed by using Business

Server Pages (BSP), vendor provided Business Application Programing Interfaces (BAPIs) and Java

scriping. The web template also contains functionality that was added using the web application designer

(WAD). WAD is a SAP tool to build web applications and to interact with portals and custom templates. In

this project the BW query was manipulated in WAD for better display. The purpose of this was to leverage a

better user interface with pre-defined control objects. While WAD can be used by developers without

extensive HTML and Java scripting knowledge, these skills were very useful when adding new layouts (see

figure xx). The enhanced web template implemented the provided set of features in the custom toolbar and

added query specific features in the navigation block. The navigation block I created in the query designer is

a web item where users can navigate the query in rows, columns and by filer values as found in the data set

inside the cube (provided by hierarchies, masterdata and ‘select distinct’ queries on dimensional

characteristics).

(figure xxx: The customized global web template with an exception based query published

Security Roles

Work Cited

Berg, Bjarne (1997) “Introduction to Data Warehousing”., module 2., pp.88-107. New York.,

NY., Price Waterhouse LLP. October 1997.

Berg, Bjarne (2004) “Managing BW projects – part-2”., SAP project management conference,

Las Vegas, NV, WIS publishing, November.

Boehm, Barry (1986) "A Spiral Model of Software Development and Enhancement", ACM SIGSOFT

Software Engineering Notes, August.

Boehm, Barry (1988) "A Spiral Model of Software Development and Enhancement"

IEEE Computer, vol.21, #5, May, pp 61-72.

Damian, Adrian., Hong Danfeng., Li, Holly., Pan, Dong (1999) "Joint Application Development

and Participatory Design". University of Calgary, Dept. of Computer Science.

Dennis, Alan R., Hayes, Glenda S., Daniels, Robert M. Jr. (1990) "Business process modeling

with group support systems". Journal of Management Information Systems. 115-142. Spring.

Gilb, Tom (1989)., “Principles of Software Engineering Management”., Addison-Wesley Longman.

McDonald, K., Wilmsmeier, A., Dixon D. (2003) “Mastering the SAP Business Information

Warehouse”., Weily

APPENDIX A: SAP – Pre-Deliverd InfoCube, Queries and Security Roles.

This is an overview of the pre-delivered InfoCube, Queries and Security roles delivered content that was

activated in SAP BW before it was enhanced for the project.

Elements of the SAP Sales SD_C03

InfoSource: 0D_SD_C03_TD

Application component: 0D_SD

Characteristics:

InfoObject Description Attributes

0D_CO_CODE Company code 0D_COUNTRY

0DIS_CHAN Distribution channel No

0D_INDUSTRY Industry key No

0D_PLANT Plant No

0D_SALE_ORG Sales organization 0D_COUNTRY

0D_SALE_GRP Sales group No

0D_SHIPTO Ship-to party No

0D_SOLD_TO Sold-to party 0D_COUNTRY

0D_INDUSTRY

0D_VERSION Version No

0D_VTYPE Value type for report No

0D_DIV Division No

0D_MATERIAL Material No

0D_PAYER Payer No

0D_DOCCLASS Document class order/delivery/invoice No

0D_DEBCRED Credit/debit posting No

0D_COUNTRY Country No

0D_REGION GIS region No

Time-characteristics:

InfoObject Description

0CALYEAR Calendar year

0CALMONTH Calendar year/month

0FISCVARNT Fiscal year variant

Key Figures:

InfoObject Description Units - InfoObject Aggregation process

0D_OORQTYBM Open order quantity 0BASE_UOM Summation

0D_OORVALSC Open order net value 0STAT_CURR Summation

0D_QUANT_B Quantity in base units of measure 0BASE_UOM Summation

0D_DOCUMENT Number of documents COUNTER Summation

0D_DOCITEMS Number of document items COUNTER Summation

0D_NETVAL_S Net value 0STAT_CURR Summation

0D_COSTVALS Cost value 0STAT_CURR Summation

0D_GR_WT_KG Gross weight in kg (Kilograms) Summation

0D_NT_WT_KG Net weight in kg (Kilograms) Summation

0D_VOLUMCDM Volume in CDM (Cubic decimeters) Summation

Units:

InfoObject Description Type

0STAT_CURR Statistics currency Currency

0BASE_UOM Base unit of measure Base UM

Pre-Delivered Queries

The queries described here are examples. As well as the completed queries delivered by SAP, you can, of course, create new queries that are based on the SAP Sales InfoCube: overview, and the corresponding data.

Delivered queries: Technical name:

Returns per customer and month (0D_SD_C03_Q003) Incoming orders (0D_SD_C03_Q004) Credit memos (0D_SD_C03_Q005) Deliveries (0D_SD_C03_Q006) Billing documents (0D_SD_C03_Q007) Fulfillment rates (0D_SD_C03_Q008) Order- and sales values (0D_SD_C03_Q009) Order-, delivery- and sales quantities (0D_SD_C03_Q010) Correct sales order processing (0D_SD_C03_Q011)

Pre-Delivered SAP BW Workbooks (Excel hosted queries through ODBO), by Security Roles.

(A) Sales Manager

(B) Key Account Manager

(C) Sales Employee

(D) Product Manager

(E) Sales Controller

(F) Sales planner

(1) Short-term profit

Incoming orders per division

Incoming orders per customer

Incoming orders per sales org.

Incoming orders – product analysis

(2) Long-term profit

Sales org. fulfillment rate

Correct order processing – sales org.

Order- and sales values per sales org.

Correct order processing – customer analysis

Order- and sales values per customer

Fulfillment rate per customer

(3) Determining profit for the period

Billing documents per sales org.

Order-, delivery- and sales quantities per customer

Order-, delivery- and sales values per sales org.

Billing documents – product analysis

(4) Early-warning information

Credit memos per sales org.

Credit memos per customer

Returns per customer

Returns per sales org.

Credit memos – product analysis

Returns by product

Deliveries per sales org.

Deliveries – customer analysis

Pre-Delivered SAP BW Relevant Security Roles for the InfoCube

(A) Sales Manager

Short-term profit: (A1) The workbook Incoming orders per division shows the Sales Manager how the incoming orders quantity and –values, or the corresponding purchase order costs, are distributed among the divisions of his/her company. The selection takes place on a monthly basis and uses the value type (actual).

(2) Long-term profit: (A2) The workbook Sales organization fulfillment rates contains information on incoming order quantities, open purchase order quantities and the fulfillment rates of the individual sales organizations.

The workbook Error-free order processing – sales organization contains details on, among others, incoming order- and return quantities, as well as on order and return values.

The workbook Order- and sales values per sales organization shows the incoming order-, return-, billing document- and credit memo values of the sales organizations. The selection takes place with all three workbooks on a monthly basis and uses the value type (actual).

(3) Profit for the period: (A3) The workbook Billing documents per sales organization allows, for example, an insight into billing document quantities and -values, and the billing document costs of the sales organizations. The selection takes place on a monthly basis and uses the value type (actual).

(4) Early-warning information: (A4) The workbook Credit memos per sales organization provides the Sales Manager and others with information on credit memo quantities and –values in relation to the billed quantities and values. The selection takes place on a monthly basis and uses the value type (actual).

(B) Key Account Manager

Short-term profit: (B1) The workbook Incoming orders per customer shows the Key Account Manager how the incoming order quantities and –values, or the corresponding purchase order costs, are shared between the customers. The selection takes place on a monthly basis and uses the value type (actual).

(2) Long-term profit: (B2) The workbook Error-free order processing – customer analysis contains, for example, details on incoming order- and return quantities, as well as order and return values per sold-to party. The selection takes place on a monthly basis and uses the value type (actual).

(4) Early-warning information: (B4) The workbook Credit memos per customer provides the Key Account Manager and others about credit memo quantities and –values in relation to the billed quantities and values. The selection takes place on a monthly basis and uses the value type (actual).

The workbook Returns per customer reveals the relationship between returns quantity and incoming orders quantity, or returns value and incoming orders value for the sold-to party. The selection takes place on a monthly basis and uses the value type (actual).

(C) Sales Employee

Short-term profit: (C1) The workbook Incoming orders per sales organization shows the Sales Employee how the incoming orders quantity and –values, or the corresponding purchase order costs, behave in the sales organization. The selection takes place on a monthly basis and uses the value type (actual).

(3) Profit for the period: (C3) The workbook Order- and delivery- and sales quantities per customer gives the Sales Employee an overview over incoming orders-, delivery-, billing documents-, returns-, return delivery- and credit memo quantities, and how they are divided among the individual customers. The selection takes place on a monthly basis and uses the value type (actual).

(4) Early-warning information: (C4) The workbook Returns per sales organization reveals the relationship between returns quantity and incoming orders quantity, or returns value and incoming orders value, per sales organization. The selection takes place on a monthly basis and uses the value type (actual).

(D) Product Manager

Short-term profit: (D1) The workbook Incoming orders – product analysis shows the Sales Manager how the incoming orders quantities and –values, or the corresponding purchase order costs, are made up for the individual products. The selection takes place on a monthly basis and uses the value type (actual).

(4) Early-warning information: (D4) The workbook Credit memos - product analysis provides the Sales Manager and others with information on credit memo quantities and –values in relation to the billed quantities and values of the products. The selection takes place on a monthly basis and uses the value type (actual).

The workbook Returns by product reveals the relationship between returns quantity and incoming orders quantity, or returns value and incoming orders value, for the individual products. The selection takes place on a monthly basis and uses the value type (actual).

(E) Sales Controller

(2) Long-term profit: (E2) The workbook Order- and sales values per customer shows the incoming orders-, returns-, billing document- and credit memo values of the customers.

The workbook Fulfillment rates per customer contains information on incoming order quantities, open purchase order quantities and the fulfillment rates for the individual customers. The selection takes place with all three workbooks on a monthly basis and uses value type (actual).

(3) Profit for the period: (E3) The workbook Order-, delivery- and sales quantities per sales organization assigns the incoming order-, delivery- return-, return delivery-, billing document- and credit memo quantities to the sales organizations.

The workbook Billing documents – product analysis allows, for example, an insight into sales quantities and –values that were reached when the products were sold. The selection takes place with both workbooks on a monthly basis and uses the value type (actual).

(F) Sales Planner

(4) Early-warning information: (F4) The workbook Deliveries – customer analysis gives the Sales Planner information about delivery quantities, gross and net weight of the delivery, as well as the delivery volume. These statistics can be analyzed per customer.

In the workbook Deliveries per sales organization, the Sales Planner can see the delivery quantities, the delivery gross and net weight, as well as the delivery volumes for the sales organizations. The selection takes place with both workbooks on a monthly basis and uses the value type (actual).

APPENDIX B: Transfer Structure Mappings and InfoSource

Technical Name: 2LIS_01_S262

Use

SD key figures for the billing document: This InfoSource provides records similar to a document for all

billing documents for which sales orders have been created.

Characteristics

InfoObject Description Data Element Field in Transfer

Structure

Source

0MATL_GRP_2 Material group 2 MVGR2 MVGR2 MVGR2





0CUST_GRP5 Customer group 5 KVGR5 KVGR5 KVGR5



0CO_AREA Controlling area KOKRS KOKRS KOKRS

0REFER_ITM Reference item VGPOS VGPOS VGPOS

0REFER_DOC Ref. document VGBEL VGBEL VGBEL

0S_ORD_ITEM Item POSNR_VA AUPOS AUPOS

0DOC_NUMBER Sales document VBELN_VA AUBEL AUBEL

0SALESEMPLY Sales employee VRTNR PVRTNR PVRTNR

0FORWAGENT Forwarding agent SPDNR PSPDNR PSPDNR

0BILLTOPRTY Bill-to party KUNRE PKUNRE PKUNRE

0SHIP_TO Ship-to party KUNWE PKUNWE PKUNWE


0COMP_CODE Company code BUKRS BUKRS BUKRS

0PAYER Payer KUNRG KUNRG KUNRG

0SOLD_TO Sold-to party KUNAG KUNAG KUNAG

0CUST_GROUP Customer group KDGRP KDGRP KDGRP

0SALES_DIST Sales district BZIRK BZIRK BZIRK

0BILL_DATE Billing date FKDAT FKDAT FKDAT

0CREATEDON Created on ERDAT ERDAT ERDAT

0CH_ON Changed on AEDAT AEDAT AEDAT

0STAT_DATE Statistics date STADAT STADAT STADAT

0DISTR_CHAN Distribution channel VTWEG VTWEG VTWEG

0REVERSEDOC Cancel STORNO STORNO STORNO

0VTYPE Value type RSVTYPE WRTTP WRTTP

0VERSION Version VRSIO VRSIO VRSIO

0BILL_NUM Billing document VBELN_VF VBELN VBELN

0BILL_ITEM Item POSNR_VF POSNR POSNR

0BILL_TYPE Billing type FKART FKART FKART

0BILL_CAT Billing category FKTYP FKTYP FKTYP

0DOC_CATEG SD document

category

VBTYP VBTYP VBTYP

0SALESORG Sales organization VKORG VKORG VKORG

0PROV_GROUP Commission group PROVG PROVG PROVG

0SALES_GRP Sales group VKGRP VKGRP VKGRP

0SALES_OFF Sales office VKBUR VKBUR VKBUR

0DIV_HEAD Division SPART_AK SPARA SPARA

0MATERIAL Material MATNR MATNR MATNR

0MATL_GROUP Material group MATKL MATKL MATKL

0BATCH Batch CHARG CHARG CHARG

0STGR_LOC Storage location LGORT LGORT LGORT


0REBATE_GRP Volume rebate group BONUS BONUS BONUS

0PRICE_DATE Pricing date PRSDT PRSDT PRSDT

0SERV_DATE Serv.rendered date FBUDA FBUDA FBUDA

0ITEM_CATEG Item category PSTYV PSTYV PSTYV

0ITM_TYPE Item type POSAR POSAR POSAR

0PROD_HIER Product hierarchy PRODH PRODH PRODH

0SHIP_POINT Shipping point VSTEL VSTEL VSTEL

0DIVISION Division SPART SPART SPART

0PLANT Plant WERKS WERKS WERKS

0COSTCENTER Cost center KOSTL KOSTL KOSTL

0CREATEDBY Created by ERNAM ERNAM ERNAM

0CREA_TIME Time ERZET ERZET ERZET

0WBS_ELEMT PSP element PS_POSID PS_POSID PS_POSID

Time Characteristics


Structure

Source

0CALMONTH Cal. year / month RSCALMONTH SPMON SPMON

0CALDAY Calendar day RSCALDAY SPTAG SPTAG

0CALWEEK Calendar year / week RSCALWEEK SPWOC SPWOC

0FISCPER Fiscal year/period RSFISCPER SPBUP SPBUP

0FISCVARNT Fiscal year variant PERIV PERIV PERIV

Units


Structure

Source

0DOC_CURRCY Document currency WAERK WAERK WAERK

0STAT_CURR Statistics currency STWAE STWAE STWAE

0LOC_CURRCY Local currency HWAER HWAER HWAER

0UNIT_OF_WT Unit of weight GEWEI GEWEI GEWEI

0VOLUMEUNIT Volume unit VOLEH VOLEH VOLEH

0SALES_UNIT Sales unit VRKME VRKME VRKME

0BASE_UOM Base unit of measure MEINS MEINS MEINS

Key Figures


Structure

Source

0EXCHG_RATE Exchange rate KURSK KURSK KURSK

0DENOMINTR Denominator UMVKN UMVKN UMVKN

0NUMERATOR Numerator UMVKZ UMVKZ UMVKZ

0GRS_WGT_DL Gross weight BRGEW_15 BRGEW BRGEW

0NET_WGT_DL Net weight NTGEW_15 NTGEW NTGEW

0BILL_QTY Billing qty in SKU FKLMG FKLMG FKLMG

0REQ_QTY Required quantity LMENG LMENG LMENG

0SCALE_QTY Scale quantity SMENG SMENG SMENG

0INV_QTY Invoiced quantity FKIMG FKIMG FKIMG

0EXCHG_STAT Exchange rate stats. STCUR_AP STCUR

0VOLUME_DL Volume VOLUM_15 VOLUM VOLUM

0SUBTOTAL_5 Subtotal 5 KZWI5 KZWI5 KZWI5

0EXRATE_ACC Exchange rate-accntg KURRF KURRF KURRF


0REBATE_BAS Rebate basis BONBA BONBA BONBA

0TAX_AMOUNT Tax amount MWSBP MWSBP MWSBP

0NO_INV Total of billing docs. MC_ANZFK COUNTER ANZFK

0NO_INV_IT Total of billing items MC_ANZFKPO COUNTER ANZFKPOS

0NETVAL_INV Net value NETWR_FP NETWR NETWR

0CSHDSC_BAS Cash disc. basis SKFBP SKFBP SKFBP

0COST Cost WAVWR WAVWR WAVWR





APPENDIX C:

Documents

Term paper v2.pdf