without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business
ByDesign, and other SAP products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects S.A. in the United States and in other countries. Business Objects is an
SAP company.
All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP
AG and its affiliated companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
8SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Introduction
chapter
Introduction
1
What is a Rapid Mart?
What is a Rapid Mart?
SAP BusinessObjects Rapid Marts packages are blueprints for building data
marts with SAP BusinessObjects technology:
•Data Services
•Universe Designer
•Web Intelligence.
Rapid Marts packages deliver jump-start ETL (extract, transform & load)
mappings, schema, and initial reporting content, accelerating the deployment
of BI (business intelligence) for enterprise applications from SAP, PeopleSoft,
Oracle, and Siebel.
Each Rapid Mart is designed to address the reporting needs of a specific
business area (or department) like accounting, sales, or purchasing. A
component-based framework allows conducting analysis across these
selected business areas by combining different packages within the same
source application suite.
Rapid Marts focus on basic standard configuration of the enterprise
applications. They are country and industry neutral templates meant to be
easily modified and extended to suit customer specific application
implementation and reporting needs.
Rapid Marts incorporate best practices, and provide easily modifiable
templates. With Rapid Marts total development time of a data mart solution is
greatly reduced.
Each customer situation is different. You will probably encounter one or more
of these:
•Customizations you have made to SAP solutions the Rapid Mart does not
cover.
•Standard SAP solutions data fields important for your specific business,
but not included in the Rapid Mart templates.
•Optimization and performance challenges unique to your environment.
•Reporting requirements not covered within the Rapid Mart template
reports.
Rapid Marts are flexible templates that you can adjust to account for these
unique situations. It is expected that some customization and optimization will
be needed to suit your individual environment. Rapid Marts are not an
out-of-the-box solution.
10SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
BI tools and analytic tools can access Rapid Mart data through SQL queries.
Rapid Marts can be implemented individually, or in any combination, to form a
single platform that delivers the infrastructure for your company’s internal and
external information needs. They can also serve as a staging area for
enterprise analytic applications.
Rapid Marts provide your business with an accelerated time to value through
rapid BI deployments because you can implement them quickly and easily
customize them to meet specific analytic requirements.
Rapid Marts packages accelerate Time to Value
Rapid Marts are packaged data solutions that you can quickly deploy to
address specific areas of business analysis.
Available Rapid Marts packages for SAP solutions include:
Financial Suite:
•SAP BusinessObjects General Ledger Rapid Mart, version for SAP
solutions
•SAP BusinessObjects Accounts Payable Rapid Mart, version for SAP
solutions
•SAP BusinessObjects Accounts Receivable Rapid Mart, version for SAP
solutions
•SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions
Operational Suite:
•SAP BusinessObjects Inventory Rapid Mart, version for SAP solutions
•SAP BusinessObjects Purchasing Rapid Mart, version for SAP solutions
•SAP BusinessObjects Sales Rapid Mart, version for SAP solutions
Manufacturing Suite:
•SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP
solutions
•SAP BusinessObjects Production Planning Rapid Mart, version for SAP
solutions
•SAP BusinessObjects Project Systems Rapid Mart, version for SAP
solutions
Human Capital Management (HCM) Suite:
•SAP BusinessObjects Human Resources Rapid Mart, version for SAP
solutions
Introduction
What is a Rapid Mart?
1
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide11
Introduction
1
What is a Rapid Mart?
You can combine multiple Rapid Marts packages into a single environment to
build the foundation for your data warehouse or use them as a staging area
for business intelligence applications.
SAP BusinessObjects Rapid Marts packages architecture
Rapid Marts architecture is driven by SAP BusinessObjects technology.
Rapid Mart Architecture:
Rapid Marts packages include the following components:
12SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Introduction
About this document
•Data Movement Jobs - packaged source-to-target mappings and data
transformations. Each job is designed to perform initial and incremental
data movement;
•Data Model & Schema - set of dat a mart database objects designed with
dimensional data modeling approach. Rapid Marts packages for SAP
solutions has a single integrated data model. The schema are available
for Oracle, SQL Server IBM DB2, and Teradata;
•Semantic Layer (Universes) - SAP BusinessObjects metadata packages
for efficient query generation. There can be one or more universes per
Rapid Mart. Each universe is developed using Rapid Marts design
principles to ensure compatibility, code readability, and component
re-use. In addition, there is one Master universe for
development/maintenance of multiple use objects (like Customer,
Material, Currency, etc.);
•Reports (Samples) - set of 15-20 Web Intelligence reports per Rapid
Mart. They represent answers to mostly asked business questions (for
example, in the SAP BusinessObjects Sales Rapid Mart, version for SAP
solutions - 'What is the monthly Revenue trend by Division for this
year?'). The reports are developed using Rapid Mart color/layout
templates. Reports are examples of Web Intelligence best practice
development (trends, listing, guided analysis, roll ups and downs, etc.).
1
About this document
This document describes the SAP BusinessObjects Purchasing Rapid Mart,
version for SAP solutions. This document contains information for a variety of
users—information that helps you understand the use of the Rapid Mart, the
data in the Rapid Mart, the reports you can create with the Rapid Mart, and
how to use and update the Rapid Mart.
This document contains the following chapters:
•Chapter 2: Overview — Describes the business problems you can solve
and the types of analyses you can do with this Rapid Mart
•Chapter 3: Subject Areas — Contains detailed information about each
componentized section in the Rapid Mart, including the processes each
section captures
•Chapter 4: Reports — Provides examples of reports you can produce
•Chapter 5: Universe — Describes the Business Objects Universes upon
which the reports are built.
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide13
Introduction
1
About this document
•Chapter 6: Installing the Rapid Mart — Contains the information you need
to install the Rapid Mart
•Chapter 7: Using the Rapid Mart —Describes how to execute the Rapid
Mart, including information about setting parameters and considerations
you need to make when customizing the Rapid Mart
•Chapter 8: Technical Implementation — Describes each componentized
section and the work flows that run to load that section
•Chapter 9: Documentation References — Information about where to find
related to the Rapid Mart technical documentation on Data Services and
BusinessObjects Enterprise
•Appendix A: Rapid Mart Data Schema — Contains a detailed list of the
tables and views in the Rapid Mart
14SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Overview
chapter
Overview
2
Overview
Overview
This chapter describes the business problems you can solve with the SAP
BusinessObjects Purchasing Rapid Mart, version for SAP solutions and the
types of analyses you can do with this Rapid Mart. The information in this
chapter is useful for those who want a business-level overview of the Rapid
Mart and its benefits.
This chapter contains the following sections:
•What you can do with this Rapid Mart
•Supported analyses
•Related Rapid Marts
•Purchasing Rapid Mart schema
•Where the Rapid Mart fits in the materials management process
What you can do with this Rapid Mart
The SAP BusinessObjects Purchasing Rapid Mart, version for SAP solutions
supports analysis of purchasing activities initiated within the Material
Management (MM-PUR) module. Purchasing is the process of externally
procuring materials and services in order to meet production schedules,
maintain stock levels, and meet internal needs for materials consumed within
the company.
Using this Rapid Mart you can:
•Analyze vendor delivery efficiency
•monitor purchasing expenditures
•monitor purchasing delivery schedules
•compare performance by different parts of your purchasing organization
•perform pricing trend analyses
•Analyze upcoming purchase requisitions
With the SAP BusinessObjects Purchasing Rapid Mart, version for SAP
solutions you can answer these types of questions:
•Which vendors are consistently late on delivery?
•Can I procure parts at a lower cost if I use a different vendor?
•How much will the initial stocking ramp up for an new product line cost?
•Which of my buyers can negotiate the best prices?
•Is one plant buying more than another plant producing the same product?
•How are my purchasing costs trending over time?
16SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Overview
What you can do with this Rapid Mart
•Which purchase order deliveries need to be expedited for an unexpected
jump in sales?
•Are invoice receipts matching goods receipts?
Selection of a vendor or supplier is a continuous and integral component of
the purchasing process. An effective relationship between companies and
suppliers helps reduce inventory levels and costs for both entities. The SAP
BusinessObjects Purchasing Rapid Mart, version for SAP solutions provides
a framework for assessing this relationship through comparison of prices,
supplier performance, transaction history , contract conditions, payment terms,
and purchasing organization effectiveness.
The SAP BusinessObjects Purchasing Rapid Mart, version for SAP solutions
is made up of several componentized sections. Each section supports a
subject related to these types of purchasing analysis:
•Purchase Requisition Section — The purchasing process begins with a
need or requirement for a certain material or service by a certain date. A
purchase requisition document detailing the requirement goes to the
purchasing organization for follow-up action. If the requirement can not
be met using internal supplies, the external procurement process begins.
•Purchase Document Section — Purchasing Documents include all
types of transactions between ourselves and our vendors or suppliers:
•RFQ’s (Requests for Quotation) - represent a preliminary step,
asking the vendor to supply pricing and availability information about
their products, but without a commitment to purchase.
•Purchase Orders - a commitment to have a vendor to supply a
quantity of materials on a specific date or set of planned delivery
dates. The price for the materials may be determined from
contract-based pricing conditions, previous quotations, or set at the
time the purchase order is created.
•Contracts - In the SAP solutions Purchasing component, a type of
"outline agreement", or longer-term buying arrangement. The
contract is a binding commitment to procure a certain material or
service from a vendor over a certain period of time.
•Scheduling Agreements - Another type of "outline agreement", or
longer-term buying arrangement. Scheduling agreements provide for
the creation of delivery schedules specifying purchase quantities,
delivery dates, and possibly also precise times of delivery over a
predefined period.
2
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide17
Overview
2
Supported analyses
•Purchase Pricing Section — Detailed pricing conditions for purchasing
documents. Includes payment terms, price history and info records for
analysis. and other supplier-related information. The Info Record
contains information on a specific material and a vendor supplying the
material. It provides the basis for vendor comparison and selection.
•Purchase Schedule Line Section — The purchase document’s delivery
schedule. Allows detailed analysis by delivery date or planned delivery
date, including number of days a delivery is early or late.
•Invoice Receipt Section — Prior to vendor payment, allows invoice to
be compared to the purchase order and goods receipt to verify price and
quantity. Results of invoice verification can be used to block invoice
payments for discrepancies in price, quantity, delivery schedule, or
quality. Can be linked to purchase orders, vendors, delivery schedules,
etc.
•Purchase Document History Section — A subject area that combines
Purchase Schedule Lines, Purchase Requisitions and Invoice Receipts
to show the full cycle of the purchasing process.
Chapter 3: Subject Areas discusses each of these sections in more detail and
how to link them together for a complete Purchasing Analysis solution.
Supported analyses
The SAP BusinessObjects Purchasing Rapid Mart, version for SAP solutions
supports several types of analyses.
Business functionTypes of analysisMeasures available in the Rapid Mart
Contract Negotiation Price analysisAggregate analysis of pricing conditions
including volume discounts across purchasing
organizations for purposes of cost reduction
and consolidation
Invoice VerificationDetailed ListingDetailed invoice listing including posting date
and quantities / values received.
Exception reportingCompare purchase order quantities, prices, and
currencies to invoiced quantities, prices, and
currencies with exceptions highlighted
Organization
Efficiency
18SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Purchasing
organization
performance
Purchasing
organization
performance
Expenditures, price comparison by purchasing
organization
Scheduling efficiency (Days early or late) by
purchasing organization.
Overview
Related Rapid Marts
Business functionTypes of analysisMeasures available in the Rapid Mart
Purchase Order
Analysis
Requisition Analysis Detailed ListingRequisition details including expected delivery
Vendor Performance ABC analysisAssign vendor ranking scores based on total
Cycle and lead time
analysis
Organizational
statistics
Price analysisDetailed pricing condition analysis and trending
Purchase order
history
Purchase order status Purchase order status including open, blocked,
Top 10Listing of top 10 purchase orders by material,
Summary ListingValue of Requisitions by Plant, or Company,
Ranked listingRank vendors by price, order fulfillment, and
Calculation of elapsed times between purchase
requisition, quotation, scheduled delivery , actual
delivery, and goods receipt by material, vendor,
and purchasing organization
Counts and values of Purchase Orders created
by various entities in your Purchasing
Organization, or by Vendor, or by Material
Grouping
of pricing condition values for purchase orders.
Summarized purchase order status by vendor,
material, and purchasing organization
received, and invoiced quantities by date
vendor, plant, and purchasing organization
ranked by expenditure and volume
dates, values, and Processing Status.
Trending by Company and Quarter
order value
on-time delivery performance
2
To support these analyses the Rapid Mart contains a number of dimension
tables; including material master data, plant, plant-specific material master
data, storage location, vendor, condition types, currency, inforecords,
payment terms, purchasing groups, and time-related dimensions such as
fiscal period, calendar date, month, and quarter.
Related Rapid Marts
Components of the SAP BusinessObjects Purchasing Rapid Mart, version for
SAP solutions are related to other SAP BusinessObjects Rapid Mart
components, as follows:
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide19
Overview
2
Related Rapid Marts
•Material movement, physical inventory, stock valuation, and batch
information is included in the SAP BusinessObjects Inventory Rapid
Mart, version for SAP solutions.
•Accounts payable information related to purchase orders is included in
the Accounts Payable SAP BusinessObjects Accounts Payable Rapid
Mart, version for SAP solutions.
•Costing Detail for materials purchased are in the SAP BusinessObjects
Cost Center Rapid Mart, version for SAP solutions.
•Production Orders, Planned Orders, and Reservations of materials
procured are in the SAP BusinessObjects Production Planning Rapid
Mart, version for SAP solutions.
•Sales Orders, Deliveries, and Backlog for materials procured are in the
SAP BusinessObjects Sales Rapid Mart, version for SAP solutions.
Sharing Components
The same components can be used in multiple Rapid Marts. For example, a
component that extracts information about materials bought, produced, and
sold is needed for a Rapid Mart that supports sales analysis and also for a
Rapid Mart that supports inventory analysis. Work flows that extract star
schema “dimensions” are components. You can add a component to any
Rapid Mart using a simple import procedure.
A Data Services job can include multiple instances of a component. For
example, each section includes all the required dimension components.
Therefore, a job with several sections may include several instances of a
particular dimension component. Components are set to execute only once
within a job. This “execute once” feature ensures that shared components do
not cause duplicate data extraction from SAP solutions. For more information
about the “execute once” feature, see the Data Integrator/Data Services Designer Guide.
Each of the sections listed in “What you can do with this Rapid Mart” on
page 16 are considered components. You can identify a component within a
Data Services job by a “C_” prefix before its name. For example, the
component that contains material movements and the associated reporting
dimensions is named C_MaterialMovement_Section.
20SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Purchasing Rapid Mart schema
The following diagram shows an overview of the SAP BusinessObjects
Purchasing Rapid Mart, version for SAP solutions components and their
relationships. The tables in the center represent the various fact tables or
subject areas in the Rapid Mart. Those on the sides are the associated
dimensions. Those on the bottom are associated auxiliary, hierarchy or
staging tables.
Overview
Purchasing Rapid Mart schema
2
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide21
Overview
2
Purchasing Rapid Mart schema
22SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Where the Rapid Mart fits in the materials management process
Inventory & Material
Movements
Stock
Valuation
Production
Orders
Reservations
Master Data
Purchase
Requisitions
Schedule
Lines
Purchasing
Documents
Purchasing
Production
Planning and
Inventory
Invoice
Verification
Pricing
Conditions
Where the Rapid Mart fits in the materials
management process
You can combine the purchasing components contained in the SAP
BusinessObjects Purchasing Rapid Mart, version for SAP solutions with
inventory components from the Inventory Rapid Mart to create a
comprehensive supply-side view of the SAP solutions materials management
process. Purchasing, material movement, inventory, and master data
components are shared across these Rapid Mart applications.
Overview
2
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide23
.
Overview
2
Where the Rapid Mart fits in the materials management process
24SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
chapter
Subject Areas
3
Overview
Overview
Each section in the SAP BusinessObjects Purchasing Rapid Mart, version for
SAP solutions pertains to a particular subject area. This chapter describes
each section and the processes each section captures.
The information in this chapter is useful for readers who use the Rapid Mart to
design and support a real-time system, such as a Web application, and need
to understand the data in the Rapid Mart and how it relates to SAP solutions.
This chapter gives some background on the Purchasing Module (MM-PUR) in
SAP solutions:
•Purchasing Module Overview
•Purchasing Module Organization
It then discusses each of the Rapid Mart Subject Areas (or sections):
•Purchase Requisition Section
•Purchase Document Section
•Purchase Pricing Section
•Purchase Schedule Line Section
•Invoice Receipt Section
•Purchase Document History Section
26SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Purchasing Module Overview
Purchasing is a component of Materials Management (MM-PUR). The
Materials Management (MM) module is fully integrated with the other
modules of the SAP solutions System. It supports all the phases of materials
management: materials planning and control, purchasing, goods receiving,
inventory management, and invoice verification.
The tasks of the MM Purchasing component are as follows:
•External procurement of materials and services
•Determination of possible sources of supply for a requirement identified
by the materials planning and control system or arising directly within a
user department
•Monitoring of deliveries from and payments to vendors
•Good communication between all participants in the procurement
process is necessary for Purchasing to function smoothly.
The typical procurement cycle for a service or material consists of the
following phases:
•Determination of Requirements
Materials requirements are identified either in the user departments or via
materials planning and control. (This can cover both MRP proper and the
demand-based approach to inventory control. The regular checking of stock
levels of materials defined by master records, use of the order-point method,
and forecasting on the basis of past usage are important aspects of the latter .)
You can enter purchase requisitions yourself, or they can be generated
automatically by the materials planning and control system.
In the Rapid Mart, the Purchase Requisition Section covers this phase.
•Source Determination
The Purchasing component helps you identify potential sources of supply
based on past orders and existing longer-term purchase agreements. This
speeds the process of creating requests for quotation (RFQs), which can be
sent to vendors electronically via EDI, if desired.
In the Rapid Mart, use analysis of Info-records (a dimension shared across
several sections) to determine which vendors supply which materials.
Info-record is short for information record. The info-record contains concise
information about a vendor and a material that Purchasing already procures
from that vendor. An info record thus represents a material-vendor
relationship.
Subject Areas
Purchasing Module Overview
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide27
Subject Areas
3
Purchasing Module Overview
The info-record indicates the units of measure in which materials are ordered
from the vendor, and the applicable reminder levels. It also shows price
changes affecting the material in question. This information can be useful in
the process of evaluating quotations to determine the successful bidder.
Info records are created automatically when you order a material. You can
also create, change, and delete info records yourself.
To store information on a vendor and a material as master data at purchasing
organization or plant level; you can create Purchasing Info-records. These
are also represented as a dimension in the Rapid Mart. They represent a finer
level of granularity.
•Purchase Order Processing
The Purchasing system adopts information from the requisitions and the
quotations to help you create a purchase order. As with purchase requisitions,
you can generate these yourself or have the system generate them
automatically. Vendor scheduling agreements and contracts (in the SAP
solutions System, types of longer-term purchase agreement) are also
supported.
In the Rapid Mart, the Purchase Document Section tracks the purchase
orders as well as contracts, and scheduling agreements.
•Purchase Order Price Determination
When you create a purchase order or scheduling agreement, the system
searches for valid conditions and inserts them into the new document (this is
the process of price determination).
A buyer can enter further conditions in the purchase order - over and above
those inserted by the system - and a new effective price results.
In the Rapid Mart the Purchase Pricing Section cross-references purchasing
documents with the various pricing conditions assigned to them. This allows
analysis of all aspects of the pricing procedures.
•Delivery Schedules
If delivery of the total purchase order quantity is to be spread out over a
certain period according to a prearranged schedule, you can enter each
desired delivery date in schedule lines (e.g. 20 pcs. on 5 May , another 20 pcs.
on 6 May, and 60 pcs. on 10 May).
In the Rapid Mart, these delivery schedules are the Purchase Schedule Line
Section. You can analyze schedule lines to determine how your vendors are
performing to schedule, anticipate bottlenecks in material delivery. Use this
information to identify critical material in short supply and expedite delivery.
•Invoice Verification
28SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Purchasing Module Overview
The SAP solutions system supports the checking and matching of invoices.
The accounts payable clerk is notified of quantity and price variances
because the system has access to PO and goods receipt data. This speeds
the process of auditing and clearing invoices for payment.
In the SAP BusinessObjects Purchasing Rapid Mart, version for SAP
solutions the Invoice Receipt Section allows you monitor invoices received.
The Purchase Document History Section provides a complete document flow
cross-referencing deliveries on the Purchasing Schedule Lines with Invoice
Receipts.
Functionality similar to Invoice Verification is also available in the SAP BusinessObjects Accounts Payable Rapid Mart, version for SAP solutions. in
the Purchase Document Financial Section. For more details, consult the user
guide for the SAP BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions.
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide29
Subject Areas
3
Purchasing Module Organization
Purchasing Module Organization
To better acquaint you with the fundamentals of how the Purchasing
(MM-PUR) module is organized in SAP solutions, we will go through some of
the fundamentals of how your business or enterprise can be organized in
SAP solutions to facilitate your purchasing requirements. We will also cover
key auxiliary data such as the Info-Record and Order Price History to show
how they assist in giving a full picture of Purchasing functionality in SAP
solutions.
Organizational Levels
The structure of an enterprise is represented in the SAP solutions System by
the following organizational levels:
•Company code - This level represents an independent accounting unit
within a client. Each company code has its own balance sheet and its
own profit and loss statement.
Example: a subsidiary company, member of a corporate group.
•Plant - An operational unit within a company code. This is typically a
logical or physical factory.
Example: a production facility, or branch office.
•Purchasing organization - An organizational unit responsible for
procuring materials or services for one or more plants and for negotiating
general conditions of purchase with vendors. The purchasing
organization assumes legal responsibility for all external purchase
transactions.
•Purchasing group - The purchasing organization is further subdivided
into purchasing groups (buyer groups or single buyers), which are
responsible for day-to-day buying activities. A purchasing group can also
act for several purchasing organizations.
Note: In the individual purchasing documents you are required to enter a
purchasing group and a purchasing organization. There is no explicit link in
the SAP solutions system between these two organizational units.
Structure Assignments of Organizational Levels
•Plant – purchasing organization/company code
In the SAP solutions system, a plant must be assigned to one or more
purchasing organizations. Furthermore, a plant must always be assigned
to a company code.
30SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
•Purchasing organization – company code
A purchasing organization can (but need not) be assigned to a company
code. If you do not assign a company code to a purchasing organization,
the latter can engage in procurement operations for every company code.
Note: A prerequisite for this is that the plant for which procurement is
carried out is assigned to the purchasing organization.
Sample Organizations in Purchasing
You can organize your purchasing functions in the following ways:
•Centralized purchasing, with just one purchasing organization
•Distributed purchasing, with a number of different purchasing
organizations each responsible for different plants.
The following diagram illustrates the different ways of organizing the
purchasing module in the SAP solutions System:
Subject Areas
Purchasing Module Organization
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide31
Subject Areas
3
Purchasing Module Organization
In the Rapid Mart there are several dimensions that cover the organization of
the purchasing module:
•Company Code
•Controlling Area - Organizational unit within a company, used to
represent a closed system for cost accounting purposes. A controlling
area may include single or multiple company codes that may use dif ferent
currencies. These company codes must use the same operative chart of
accounts.
•Plant
•Purchase Group
•Purchase Organization
•Valuation Area - Describes level at which stocks are valuated together,
generally a company, plant or group of plants.
These dimensions cover all possible combinations of purchasing organization
as shown in the diagram above.
Purchasing Info-Records
These serve as a source of numerous information for Purchasing. The
purchasing info record (also referred to in abbreviated form as the "info
record") contains information on a specific material and a vendor supplying
the material. For example, the vendor's current pricing is stored in the info
record.
The info record allows buyers to quickly determine:
•Which materials have been previously offered or supplied by a specific
vendor
•Which vendors have offered or supplied a specific material
Structure
The info record contains:
•Data such as prices and conditions that you can store for the relevant
purchasing organization or plant
•The number of the last purchase order
•Tolerance limits for over deliveries and under deliveries
•The planned delivery time (lead time required by the vendor to deliver the
material)
•Vendor evaluation data
32SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
•An indicator showing whether the vendor counts as the regular vendor for
the material
•The vendor sub-range to which the material belongs
•The availability period during which the vendor can supply the material
The info record contains quotation and ordering data. The data in the info
record (prices for example) are also used as default data for purchase orders.
For instance, you can store the current and future quotation conditions
(discounts, fixed costs etc.) in the info record, in order to be able to copy them
into Purchase Orders. You can also maintain the vendor ’s conditions directly
in the info record.
Organizational Levels in Info Records
An info record can apply to the following organizational levels:
•Purchasing organization
•Plant
Procurement Types in Info Records
•Standard - A standard info record contains information for standard
purchase orders. The info records can be created for materials and
services with and without master records.
•Subcontracting - A subcontractor info record contains ordering
information for subcontract orders. For example, if you subcontract the
assembly of a component, the subcontractor info record would include
the vendor's (subcontractor’s) price for assembling the component.
•Pipeline - A pipeline info record contains information on a vendor’s
commodity that is supplied through a pipeline or pipes (for example, oil or
water) or by similar means (for example, electricity through the mains).
The info record contains the vendor’s price for the consumption of such
commodities by the buyer ("pipeline withdrawals"). You can store
withdrawal/usage prices for different validity periods.
•Consignment - A consignment info record contains information on a
material that vendors keep available at their own cost on the orderer’s
premises. The info record contains the vendor’s price for withdrawals by
the orderer from consignment stock. As in the case of the pipeline info
record, you can store prices for different validity periods.
In the Rapid Mart, Info Records are implemented as two dimensions that are
used across subject areas:
•Info-Record - details the basic material to vendor relationship
Subject Areas
Purchasing Module Organization
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide33
Subject Areas
3
Purchasing Module Organization
•Info-Record By Purchasing Organization - details the organizational
attachments to Plant and Purchasing Organization. Also details the
various procurement types associated with Info-Records.
Order Price History
The purchase order price history logs the various prices charged for a
material by a vendor.
A price history record is generated for each purchase document item. Each
price change affecting an item that is linked to an info record causes the price
history record to be updated.
You can analyze the order price history and display the individual documents
it is based on. You obtain information on a particular vendor’s past price
changes with regard to a certain material.
In the Rapid Mart, the Order Price History is implemented as the dimension
Purchase Document Price History.
Document Category and Document Type
Purchasing documents are broadly divided by Document Category:
The Document Categories are further divided into Document Types. Among
other things, document type determines the relevant number range and the
fields that are available for maintenance.
Document
Category
ARequest for quotationABRequest for GP bid
34SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Note: The values shown in the two tables above are examples only. Your
SAP solutions system may have different values.
In the Rapid Mart, we carry dimensions for both Document Category and
Document Type.
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide35
Subject Areas
3
Purchase Requisition Section
Purchase Requisition Section
The purchase requisition section of this Rapid Mart stores data that tracks
internal requests for materials processed through the purchasing
organization. For this section, this chapter includes information about:
•Rapid Mart processing
•Rapid Mart data
The SAP BusinessObjects Purchasing Rapid Mart, version for SAP solutions
tracks the flow of purchasing documents beginning with the purchase
requisition. A number of circumstances result in the generation of a purchase
requisition. For example, SAP solutions may automatically generate a
purchase requisition when certain stocks reach a minimum safety level. In this
case, the SAP solutions material requirements planning (MRP) component
may trigger an automatic replenishment order.
A purchase requisition contains a requisition document identifier and
individual line items. These are stored in a single SAP solutions table (EBAN).
Each line item refers to a specific material, including the amount needed and
the required delivery date. A price may be required in order to determine the
release strategy for the requisition. A requisitioner may suggest a vendor if
one has not been fixed as the source of supply for the material. After the
requisition has been converted to a purchase order, it can be linked to RFQs,
contracts, purchase orders, info records, delivery schedules, pricing
conditions, and goods receipts via the purchasing document and line item
identifiers.
The Rapid Mart selects new or changed purchase requisitions using the
document change date (EBAN.ERDAT). There is no document creation date
in EBAN. Instead the change date records date of requisition creation, and
any subsequent changes.
Using this date, the Rapid Mart initial load job selects requisitions created or
changed during the initial load time frame defined by global variables
$G_SDATE and $G_EDATE and loads them into the PURCH_REQ_FACT
target table. The initial load can cover several years of historical data.
Incremental (Delta) loads use the same logic, however the interval between
$G_SDA TE and $G_EDATE is typically a day or two. Thus the data volume is
much smaller than the initial load. During incremental loads the Table Comparison transform is used to add new or update existing records in table
PURCH_REQ_FACT.
36SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Rapid Mart processing
Purchase Requisitions are stored in the PURCH_REQ_FACT table of the
target database. This section also captures these dimensional attributes and
their associated dimension tables.
Organization
Material and Product HierarchyMATERIAL &
Material By PlantMATERIAL_BY_PLANT
Material GroupMATERIAL_GROUP
PlantPLANT
Purchasing GroupPURCH_GROUP
Purchasing Item CategoryPURCH_ITEM_CATEGORY
Purchasing OrganizationPURCH_ORGANIZATION
Purchasing Requisition ControlPURCH_REQ_CONTROL
Purchasing Requisition Process
Status
Purchasing Requisition Release
Status
Storage LocationSTORAGE_LOCATION
Time DimensionTIME_DIM
Unit Of MeasureUNIT_OF_MEASURE
Valuation AreaVALUATION_AREA
VendorVENDOR
Vendor By CompanyVENDOR_BY_COMPANY
Subject Areas
Purchase Requisition Section
DOCUMENT_CATEGORY
INFORECORD_BY_ORG
PRODUCT_HIERARCHY
PURCH_REQ_PROCESS_STATUS
PURCH_REQ_RELEASE_STATUS
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide37
Subject Areas
3
Purchase Requisition Section
Fact Table Fields
The Purchase Requisitions table (PURCH_REQ_FACT) contains the
following measures:
Column NameDescription
AMT_PO_TRXCalculated purchase order amount
resulted from PR in Document
Currency
AMT_REQ_PRICEEBAN.PREIS - Price in the purchase
requisition
AMT_REQ_TRXCalculated purchase requisition
amount in Document Currency
DAYS_GR_PROCESSEBAN.WEBAZ - Goods receipt
processing time in days
QTY_POEBAN.BSMNG Quantity ordered
against this purchase requisition
QTY_PRICE_UNITEBAN.PEINH - Price unit
QTY_REQEBAN.MENGE Purchase requisition
quantity
38SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Rapid Mart data
The following diagram shows the purchase requisition section and the
components used as reporting dimensions.
Subject Areas
Purchase Requisition Section
3
You can analyze Purchase Requisitions along several Dimensions
•Account Assignment Category
•Company Code
•Currency
•Document Category
•Document Type
•Info-record - An info-record thus represents a material-vendor
relationship.
•Info-record By Purchasing Organization - A snowflaked dimension that
cross-references Info-records with Purchasing Organizations
•Material
•Material By Plant - A snowflaked dimension that cross-references
Material with associated plants
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide39
Subject Areas
3
Purchase Document Section
•Material Group
•Plant - Typically a logical or physical Factory
•Purchasing Group - Typically the Buyer
•Purchasing Item Category
•Purchasing Organization
•Purchasing Requisition Control
•Purchasing Requisition Process Status
•Purchasing Requisition Release Status
•Storage Location - Storage Locations within Plants
•Time Dimension
•Unit Of Measure
•Valuation Area
•Vendor
•Vendor By Company - A snowflaked dimension that cross-references
Vendors with Company Codes
Typical queries include:
•What is the status of purchase requisitions by purchasing group?
•What is the average cycle time from requisition release to date of goods
receipt?”
•How many Requisitions were generated by the last MRP run?
•Which Buyers are slowest at converting requisitions to Purchase Orders?
•What is the net quantity of a material requisitioned this month?
•Which vendors are suggested as suppliers for a certain material?
•How may requisitions were cancelled (marked for deletion) this month?
•Is my requisition blocked for release (prevented from becoming a
purchasing document)?
Purchase Document Section
The purchase order section stores information about purchase orders,
purchase order delivery schedules, and pricing conditions. This chapter
describes
Purchase orders request the supplier or vendor to provide the materials in the
quantities listed by the date specified in the delivery schedule. The price on
the purchase order is determined based on the purchasing info record, prices
or conditions specified in a contract, a previous purchase order, a requisition,
40SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Purchase Document Section
or RFQ document. Prices in the purchase order are not time-dependent. The
net price and any other terms or conditions apply only to the quantity and the
items listed on the order. A purchase order history table tracks all the
transactions that have occurred for a PO item to date (for example goods and
invoice receipts relating to the item, incurrence of delivery costs,
down-payments, and so on).
Different types of purchasing documents, including contracts, RFQs, and
purchase orders, reside in the same SAP solutions source table. Each
purchasing document consists of a header record containing data applicable
to the entire document including a document type identifier to differentiate
between the different types of purchasing documents. Individual line items
are used for each item or material being purchased. Purchase orders contain
many of the same fields as those included in contracts and quotations
(payment terms, net price, currency). Added fields for purchase orders
include planned delivery days, goods receipt processing days, a link to the
base contract or scheduling agreement covering the order, and various
indicators tracking the status of the order.
Orders for materials which are purchased frequently, such as office supplies,
may be covered by a quantity or value-based contract instead of a purchase
order. A delivery schedule determines timing of multiple deliveries under the
same contract or purchase order. Deliveries spread out over a certain period
according to a prearranged schedule, are maintained in schedule lines.
SAP solutions stores multiple purchasing document types in a single source
table and uses a document type identifier to differentiate between types of
documents (RFQ, purchase order, contract, scheduling agreement).
Purchase order fields include the contract creation date, validity dates, total
value, currency, and payment terms. These are extracted from the SAP
solutions purchasing document header table (table EKKO). Fields
corresponding to individual contract line items include the material identifier,
item price, date of price determination, target quantity (quantity based
agreement), and target value (value based agreement). These are extracted
from the SAP solutions purchasing line item table (table EKPO).
In the Rapid Mart, table PURCH_DOC_FACT contains header information,
such as the vendor, currency, purchasing organization, and payment terms. It
also contains line item information, such as material ordered, gross price, net
price, and order quantity.
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide41
Subject Areas
3
Purchase Document Section
Rapid Mart processing
Purchase documents are stored in the PURCH_DOC_FACT table of the
target database. Additionally, this section captures the following dimensional
attributes and their associated dimension tables.
Status
Purchasing Document SourcePURCH_DOC_SOURCE
Purchasing GroupPURCH_GROUP
Purchasing Item CategoryPURCH_ITEM_CATEGORY
DOCUMENT_CATEGORY
INFORECORD_BY_ORG
PRODUCT_HIERARCHY
PRICING_PROCEDURE_VR
PROFIT_CENTER_HIER,
PROFIT_CENTER_HIER_HZ,
PROFIT_CENTER_HIER_VR,
PROFIT_CENTER_BAD
PURCH_DOC_RELEASE_STATUS
42SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Attribute NameDimension Tables
Purchasing OrganizationPURCH_ORGANIZATION
Special Stock IndicatorSPECIAL_STOCK_INDICATOR
Storage LocationSTORAGE_LOCATION
Time DimensionTIME_DIM
Unit Of MeasureUNIT_OF_MEASURE
VendorVENDOR
Vendor By CompanyVENDOR_BY_COMPANY
Fact Table Fields
The PURCH_DOC_FACT table contains the following measures:
Column NameDescription
AMT_AGREE_PLAN_TRXEKKO.KTWRT- Cumulative planned
AMT_GROSS_LOCPurchase order gross value (in Local
AMT_GROSS_TRXEKPO.BRTWR - Purchase order
AMT_NET_LOCPurch. Order Net Value (in Local
AMT_NET_PRICE_LOCNet price in purchasing document (in
AMT_NET_PRICE_TRXEKPO.NETPR - Net price in
AMT_NET_TRXEKPO.NETWR - Purchase order net
AMT_SUBTTL_01_LOCEKPO.KZWI1- Subtotal 1 from
AMT_SUBTTL_01_TRXEKPO.KZWI1- Subtotal 1 from
AMT_SUBTTL_02_LOCEKPO.KZWI2 - Subtotal 2 from
AMT_SUBTTL_02_TRXEKPO.KZWI2 - Subtotal 2 from
Subject Areas
Purchase Document Section
value
currency)
gross value in order currency
currency)
Local currency)
purchasing document (in document
currency)
value in order currency
pricing procedure for condition in
Local Currency
pricing procedure for condition
pricing procedure for condition in
Local Currency
pricing procedure for condition
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide43
Subject Areas
3
Purchase Document Section
Column NameDescription
AMT_SUBTTL_03_LOCEKPO.KZWI3 - Subtotal 3 from
pricing procedure for condition in
Local Currency
AMT_SUBTTL_03_TRXEKPO.KZWI3 - Subtotal 3 from
pricing procedure for condition
AMT_SUBTTL_04_LOCEKPO.KZWI4 - Subtotal 4 from
pricing procedure for condition in
Local Currency
AMT_SUBTTL_04_TRXEKPO.KZWI4 - Subtotal 4 from
pricing procedure for condition
AMT_SUBTTL_05_LOCEKPO.KZWI5 - Subtotal 5 from
pricing procedure for condition in
Local Currency
AMT_SUBTTL_05_TRXEKPO.KZWI5 - Subtotal 5 from
pricing procedure for condition
AMT_SUBTTL_06_LOCEKPO.KZWI6 - Subtotal 6 from
pricing procedure for condition in
Local Currency
AMT_SUBTTL_06_TRXEKPO.KZWI6 - Subtotal 6 from
pricing procedure for condition
AMT_TRGT _LOCT arget value for outline agreement (in
Local currency)
AMT_TRGT_TRXEKPO.ZWERT- Target value for
outline agreement in document
currency
AMT_VALID_LOCEKPO.EFFWR - Effective value of
item in Local Currency
AMT_VALID_TRXEKPO.EFFWR - Effective value of
item
DAYS_GR_PROCESSEKPO.WEBAZ - Goods receipt
processing time in days
DAYS_PLAN_DELIVEKPO.PLIFZ - Planned delivery time
PURCH_DOC_FACT table and associated dimension tables are organized
as a star schema, as shown below:
order quantity
tolerance limit
Subject Areas
Purchase Document Section
3
You can analyze Purchasing Documents along several dimensions:
•Account Assignment Category
•Company Code
•Controlling Area
•Monetary Currency
•Document Category - Broadly defines Purchase Documents as Purchase
Orders, Contracts, Scheduling Agreements, Quotations, etc.
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide45
Subject Areas
3
Purchase Document Section
•Document Type
•Info-record - Cross References Vendors with the materials you purchase
from them
•Info-record By Purchasing Organization - Cross References V endors with
Purchasing Organizations and the materials you purchase from them
•Inter Company Terms - Determines where in the purchasing cycle you
take ownership of materials delivered to you
•Material & Product Hierarchy
•Material By Plant - A snowflaked dimension that cross-references
Material with associated plants
•Material Group
•Payment Term
•Plant - Typically a physical or logical factory
•Pricing Procedure
•Profit Center & Hierarchy
•Purchasing Document Price History
•Purchasing Document Release Status
•Purchasing Document Source
•Purchasing Group
•Purchasing Item Category
•Purchasing Organization
•Special Stock Indicator
•Storage Location - Storage Locations within Plants
•Time Dimension
•Unit Of Measure
•Vendor
•Vendor By Company
46SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Purchase Pricing Section
Typical queries for Purchasing Documents are:
•How do vendors rank according to total purchase order value (ABC
analysis)?
•What is the average time between the expected and actual delivery dates
or this vendor?
•Show me which purchasing groups have reduced raw material
expenditures by 10% this quarter.
•What is the value of purchasing documents with blocked release status
•Which plants are purchasing the most each fiscal quarter?
•Which company codes have the longest Goods Receipt Processing
Time?
•Which materials are sourced from only one vendor?
•Have prices for certain materials been trending up or down over the past
year?
•Is there a surge in new purchase orders towards the end of a fiscal
quarter?
•What is the average planned delivery time (in days) for certain materials
this fiscal quarter?
3
Purchase Pricing Section
This section allows you to analyze pricing stipulations on purchase
documents (such as applicable discounts or surcharges, or stipulations
regarding the payment of freight costs).
There are three kinds of price in Purchasing:
•Gross price - Price without taking any possible discounts and
surcharges into account.
•Net price - Price taking any applicable discounts and surcharges into
account.
•Effective price - Net price after deduction of cash discount (prompt
payment discount), with allowance for any miscellaneous provisions,
delivery costs, and non-deductible taxes.
When you create a purchase order or scheduling agreement the system
searches for valid conditions and inserts them into the new document (this is
the process of price determination).
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide47
Subject Areas
3
Purchase Pricing Section
Price determination uses only already existing conditions. Thus, if the buyer
enters further conditions in the purchase order - over and above those
inserted by the system - and a new effective price results, the latter is not
calculated via the price determination process.
In the Rapid Mart we show the conditions assigned to each purchase
document. Thus, we show the net effect of price determination plus any
further conditions entered on the documents.
In the Rapid Mart, the PURCH_PRICE_FACT table combines data from the
SAP solutions tables EKKO (Purchasing Document Header), EKPO
(Purchasing Document Line Items), and KONV (Conditions Transaction Data)
Rapid Mart processing
Purchase Document Pricing conditions are stored in the
PURCH_PRICE_FACT table of the target database. Additionally, this section
captures the following dimensional attributes and their associated dimension
tables.
Organization
Material & Product HierarchyMATERIAL &
DOCUMENT_CATEGORY
INFORECORD_BY_ORG
PRODUCT_HIERARCHY
48SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Purchase Pricing Section
Attribute NameDimension Tables
Material By PlantMATERIAL_BY_PLANT
Material GroupMATERIAL_GROUP
Payment TermPAYMENT_TERM
PlantPLANT
Pricing ConditionPRICING_CONDITION
Pricing ProcedurePRICING_PROCEDURE_HZ &
PROFIT_CENTER_BAD
Purchasing Document Price HistoryPURCH_DOC_PRICE_HISTORY
Purchasing Document SourcePURCH_DOC_SOURCE
Purchasing GroupPURCH_GROUP
Purchasing Item CategoryPURCH_ITEM_CATEGORY
Purchasing OrganizationPURCH_ORGANIZATION
Storage LocationSTORAGE_LOCATION
Time DimensionTIME_DIM
Unit Of MeasureUNIT_OF_MEASURE
VendorVENDOR
Vendor By CompanyVENDOR_BY_COMPANY
3
Fact Table Fields
The PURCH_PRICE_FACT table contains the following measures
Column NameDescription
AMT_CONDITN_LOCCalculated Condition value in Local Currency
AMT_CONDITN_TRXKONV.KWERT -Condition value in Doc Currency
AMT_ORDER_GROSS_LOCCalculated Net price in purchasing document (in Local
currency)
AMT_ORDER_GROSS_TRXEKPO.BRTWR - Purchase order gross value in order
currency
AMT_ORDER_NET_LOCCalculated Net price in purchasing document (in Local
currency)
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide49
Subject Areas
3
Purchase Pricing Section
Column NameDescription
AMT_ORDER_NET_PRICE_LOCCalculated Net price in purchasing document (in Local
currency)
AMT_ORDER_NET_PRICE_TRXEKPO.NETPR - Net price in purchasing document (in
document currency)
AMT_ORDER_NET_TRXEKPO.NETWR - Purchase order net value in order currency
AMT_ORDER_TRGT_LOCCalculated Net price in purchasing document (in Local
currency)
AMT_ORDER_TRG T_TRXEKPO.ZWERT- Target value for outline agreement in
document currency
QTY_CONDITN_UNITKONV.KPEIN- Condition Price unit
QTY_ORDEREKPO.MENGE - Purchase order quantity
QTY_ORDER_TRGTEKPO.KTMNG - Target quantity
Rapid Mart Data
PURCH_PRICE_FACT table and associated dimension tables are organized
as a star schema, as shown below
You can analyze this section along several dimensions:
•Account Assignment Category
50SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Purchase Pricing Section
•Calculation Type
•Company Code
•Pricing Related Dimensions - these dimensions help you understand and
analyzed the different components of pricing in a Purchasing Document.
• Condition Category
• Condition Class
• Condition Control
• Condition Origin
• Condition Type
• Pricing Condition
• Pricing Procedure
•Controlling Area
•Monetary Currency
•Info-record
•Info-record By Purchasing Organization
•Material Related Dimensions
• Material & Product Hierarchy
• Material By Plant
• Material Group
•Payment Term
•Plant
•Profit Center & Hierarchy
•Purchasing Document Related Dimensions
•Document Category
•Document Type
• Purchasing Document Price History
• Purchasing Document Source
• Purchasing Group
• Purchasing Item Category
• Purchasing Organization
•Storage Location
•Time Dimension
•Unit Of Measure
•Vendor
•Vendor By Company
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide51
Subject Areas
3
Purchase Schedule Line Section
Typical queries for this section include:
•Which vendors offer better discounts on a material?
•Which Buyers (Purchasing Groups) are negotiating better prices for
similar materials?
•Do certain factories (plants) get better pricing for the same materials?
•Are discounts and other price adjustments trending up or down?
•How often do we take advantage of prompt payment discounts (p ayment
terms)?
•How often are vendors changing prices for materials ordered?
Purchase Schedule Line Section
Purchasing Schedule Lines determine a time schedule for the successive
delivery of parts of the total quantity of a material included as an item of a
purchasing document.
A schedule line specifies the quantity to be delivered, the date, and time of
delivery. Once a delivery has been received, the delivery quantity is also
shown.
In the Rapid Mart, the PURCH_SCHED_LINE_FACT table combines data
from the SAP solutions tables EKKO (Purchasing Document Header), EKPO
(Purchasing Document Line Items), and EKET (Scheduling Agreement
Schedule Lines)
Note: Although the descriptive name for EKET is “Scheduling Agreement
Schedule Lines”, the table is used for all types of purchasing documents, not
just Scheduling Agreements.
Rapid Mart processing
Purchase Schedule Lines are stored in the PURCH_SCHED_LINE_FACT
table of the target database. Additionally, this section captures the following
dimensional attributes and their associated dimension tables:
Status
Purchasing Document SourcePURCH_DOC_SOURCE
Purchasing GroupPURCH_GROUP
Purchasing Item CategoryPURCH_ITEM_CATEGORY
Purchasing OrganizationPURCH_ORGANIZATION
Special Stock IndicatorSPECIAL_STOCK_INDICATOR
Storage LocationSTORAGE_LOCATION
Time DimensionTIME_DIM
Unit Of MeasureUNIT_OF_MEASURE
VendorVENDOR
Vendor By CompanyVENDOR_BY_COMPANY
INFORECORD_BY_ORG
PRODUCT_HIERARCHY
PROFIT_CENTER_HIER,
PROFIT_CENTER_HIER_HZ,
PROFIT_CENTER_HIER_VR,
PROFIT_CENTER_BAD
PURCH_DOC_RELEASE_STATUS
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide53
Subject Areas
3
Purchase Schedule Line Section
Fact Table Fields
The PURCH_SCHED_LINE_FACT table contains the following measures:
QTY_ISSUEEKET.WAMNG Issued quantity'
QTY_ITEMUse for aggregation at Document line
QTY_PREVEKET.AMENG - Previous quantity
QTY_REDUCEDEKET.DABMG Quantity reduced
QTY_SCHEDEKET.MENGE Scheduled quantity'
QTY_TTLEKPO.MENGE - Purchase order
net value in order currency'
or Late (St atistics Delivery Date Less
Delivery Date)'
in days'
(Number of days from Purch. Doc.
creation to delivery)'
received to date'
(stock transfer)'
item level: for the first schedule line it
is EKPO.MENGE - Purchase order
line quantity for the rest of schedule
lines it is 0'
(delivery schedule lines)'
(MRP)'
quantity'
Note: The fields below are used for aggregation. They only carry values on
the first (lowest numbered) schedule line of a purchase document line item.
See description of each of these items (in table above) for more detail.
•AMT_ITEM_GROSS_LOC
•AMT_ITEM_GROSS_TRX
•AMT_ITEM_NET_LOC
•AMT_ITEM_NET_TRX
•QTY_ITEM
56SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Rapid Mart Data
PURCH_SCHED_LINE_FACT table and associated dimension tables are
organized as a star schema, as shown below
Subject Areas
Purchase Schedule Line Section
3
You can analyze this section along several dimensions:
•Account Assignment Category
•Company Code
•Controlling Area
•Monetary Currency - including local (company code) currency and
transaction currency
•Document Category
•Document Type
•Info-record
•Info-record By Purchasing Organization
•Inter Company Terms - describes when you take ownership of goods
purchased.
•Material Related Dimensions
•Material & Product Hierarchy
•Material By Plant
•Material Group
•Payment Term
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide57
Subject Areas
3
Invoice Receipt Section
•Plant
•Profit Center & Hierarchy
•Purchasing Document related Dimensions
•Purchasing Document Price History
•Purchasing Document Release Status
•Purchasing Document Source
•Purchasing Group
•Purchasing Item Category
•Purchasing Organization
•Special Stock Indicator
•Storage Location
•Time Dimension
•Unit Of Measure
•Vendor
•Vendor By Company
Typical queries for this section include:
•Are deliveries on time (days early or late)?
•Which vendors are or are not delivering to schedule?
•Are there excessive gaps in scheduled deliveries for a material?
•How efficient are my buyers at scheduling deliveries?
•What quantity of a material is scheduled for delivery in the next month,
quarter, week, etc.?
•Which deliveries are outstanding (past delivery date, and not yet
received)?
•Who are my top (or bottom) 10 vendors for delivery to schedule?
Invoice Receipt Section
Invoice receipts appear in the Purchase Document History in SAP solutions.
They represent the vendor’s bill for items purchased. They are matched to the
Purchasing Document and should correspond to the quantities delivered
(Goods Received).
They are a point of intersection with the SAP BusinessObjects Accounts
Payable Rapid Mart, version for SAP solutions. The invoice appears as an
accounting (financial) document in the SAP BusinessObjects Accounts
Payable Rapid Mart, version for SAP solutions.
58SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
In the Purchasing Rapid Mart the INVOICE_RECEIPT_FACT table combines
data from the SAP solutions tables RBKP (Incoming Invoice Header), and
RSEG (Incoming Invoice Line Items).
Rapid Mart processing
Invoice receipts are stored in the INVOICE_RECEIPT_FACT table of the
target database. Additionally, this section captures the following dimensional
attributes and their associated dimension tables:
Fiscal PeriodFISC_PERIOD
Material & Product HierarchyMATERIAL &
Material By PlantMATERIAL_BY_PLANT
Material GroupMATERIAL_GROUP
Payment TermPAYMENT_TERM
PlantPLANT
Purchasing Item CategoryPURCH_ITEM_CATEGORY
Purchasing OrganizationPURCH_ORGANIZATION
Time DimensionTIME_DIM
Unit Of MeasureUNIT_OF_MEASURE
Valuation AreaVALUATION_AREA
VendorVENDOR
Vendor By CompanyVENDOR_BY_COMPANY
Invoice Receipt Section
DOCUMENT_CATEGORY
PRODUCT_HIERARCHY
Subject Areas
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide59
Subject Areas
3
Invoice Receipt Section
Fact Table Fields
The INVOICE_RECEIPT_FACT table contains the following measures
Column NameDescription
AMT_INV_CASH_DISCNT_LOCUse for Aggregation - Cash discount
amount in Local currency. Only Line
Item 1 carries the value; the rest of
lines are set to 0
AMT_INV_CASH_DISCNT_TRXUse for Aggregation - Cash discount
amount in document currency. Only
Line Item 1 carries the value; the rest
of lines are set to 0
AMT_INV_GROSS_LOCUse for aggregation - Gross invoice
amount in Local currency. Only Line
Item 1 carries the value; the rest of
lines are set to 0
AMT_INV_GROSS_TRXUse for aggregation - Gross invoice
amount in document currency. Only
Line Item 1 carries the value; the rest
of lines are set to 0
AMT_INV_TAX_LOCUse for Aggregation - Tax amount
(+/-) in Local currency . Only Line Item
1 carries the value; the rest of lines
are set to 0
AMT_INV_TAX_TRXUse for Aggregation - Tax amount
(+/-) in document currency. Only Line
Item 1 carries the value; the rest of
lines are set to 0
AMT_LOCCalculated field - Line item invoice
amount in Local currency
AMT_TRXRESG.WRBRW- Line item invoice
amount in document currency
AMT_TTL_CASH_DISCNT_LOCCalculated field - Cash discount
amount in Local currency
AMT_TTL_CASH_DISCNT_TRXRBKP.WSKTO - Cash discount
amount in document currency
AMT_TTL_GROSS_LOCCalculated field - Gross invoice
amount in Local currency
AMT_TTL_GROSS_TRXRBKP.RMWWR- Gross invoice
amount in document currency
60SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Invoice Receipt Section
Column NameDescription
AMT_TTL_TAX_LOCCalculated field - Tax amount (+/-) in
Local currency
AMT_TTL_TAX_TRXRBKP.WMWST1- T ax amount (+/-) in
document currency
QTYRSEG.MENGE - Line item invoice
quantity
QTY_PRCUOMRSEG.BPMNG - Quantity in order
price unit
Note: The fields below are used for aggregation. They only carry values on
the first (lowest numbered) line of an invoice. See description of each of these
items (in table above) for more detail.
•AMT_INV_CASH_DISCNT_LOC
•AMT_INV_CASH_DISCNT_TRX
•AMT_INV_GROSS_LOC
•AMT_INV_GROSS_TRX
•AMT_INV_TAX_LOC
•AMT_INV_TAX_TRX
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide61
Subject Areas
3
Invoice Receipt Section
Rapid Mart Data
INVOICE_RECEIPT_FACT table and associated dimension tables are
organized as a star schema, as shown below
You can analyze this section along several dimensions:
•Account Assignment Category
•Company Code
•Condition Type
•Controlling Area
•Monetary Currency
•Debit Credit Indicator
•Document Type- This is the Financial Document Type of the Invoice
•Fiscal Period
•Material Related Dimensions
• Material & Product Hierarchy
• Material By Plant
• Material Group
•Payment Term
•Plant
•Purchasing Document Related Dimensions
62SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Purchase Document History Section
• Purchasing Item Category
• Purchasing Organization
•Time Dimension
•Unit Of Measure
•Valuation Area
•Vendor
•Vendor By Company
Typical queries for this section include:
•Which invoices are blocked for payment?
•What is the value of invoices received from a vendor for a given fiscal
period?
•Have we received the invoice for a particular purchase order?
•Do invoiced quantities match goods received quantities for the same
purchase document?
Purchase Document History Section
Purchase Document History is processed entirely in the Rapid Mart. It is a
union of Purchasing Schedule Lines, Purchase Requisitions, and Invoice
Receipts. The purpose is to provide you with a complete document flow
showing how a material requirement progresses from a requisition through to
invoicing for goods purchased.
The Rapid Mart contains a view PURCH_DOC_HISTORY_VIEW that
combines data from PURCH_REQ_FACT, PURCH_SCHED_LINE_FACT,
and INVOICE_RECEIPT_FACT. The view is joined to the
PURCH_DOC_FACT table in the Universe (semantic layer) to provide a
complete history and document flow for the purchasing life cycle.
See Chapter 5: Universe for more details on how this is presented for
reporting and analysis purposes.
Subject Areas
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide63
Subject Areas
3
Purchase Document History Section
Rapid Mart processing
The Purchase Document History is stored in the
PURCH_DOC_HISTORY_VIEW view of the target database. Additionally,
this section captures the following dimensional attributes and their associated
dimension tables:
Material By PlantMATERIAL_BY_PLANT
Material GroupMATERIAL_GROUP
PlantPLANT
Purchasing GroupPURCH_GROUP
Purchasing Item CategoryPURCH_ITEM_CATEGORY
Purchasing OrganizationPURCH_ORGANIZATION
Time DimensionTIME_DIM
Unit Of MeasureUNIT_OF_MEASURE
VendorVENDOR
Vendor By CompanyVENDOR_BY_COMPANY
DOCUMENT_CATEGORY
PRODUCT_HIERARCHY
Fact Table Fields
The PURCH_DOC_HISTORY_VIEW contains the following measures:
Column NameDescription
AMT_BILLED_LOCCalculated field - Line item invoice
amount in Local currency
AMT_BILLED_TRXRESG.WRBRW- Line item invoice
amount in document currency
64SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Purchase Document History Section
Column NameDescription
AMT_ORDERED_LOCUse for aggregation: for the first
schedule line it is - Calculated Net
order line value in purchasing
document (in Local currency); for the
rest of schedule lines it is 0
AMT_ORDERED_TRXUse for aggregation at Document line
item level: for the first schedule line it
is EKPO.NETWR - Purchase order
line net value in order currency; for
the rest it is set to 0
AMT_REQUISITN_LOCRequisition Amount in Local
amount in Document Currency
QTY_BILLEDRSEG.MENGE - Line item invoice
quantity
QTY_ORDEREDUse for aggregation at Document line
item level: for the first schedule line it
is EKPO.MENGE - Purchase order
line quantity; for the rest of schedule
lines it is 0
QTY_REQUISITNEBAN.MENGE Purchase requisition
quantity
3
Note: The fields below are used for aggregation. They only carry values on
the first (lowest numbered) line of a document. See description of each of
these items (in table above) for more detail.
•AMT_ORDERED_LOC
•AMT_ORDERED_TRX
•QTY_ORDERED
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide65
Subject Areas
3
Purchase Document History Section
Rapid Mart Data
PURCH_DOC_HISTORY_VIEW and associated dimension tables are
organized as a star schema, as shown below
You can analyze this section along several dimensions:
•Account Assignment Category
•Company Code
•Controlling Area
•Monetary Currency
•Material Related Dimensions
• Material & Product Hierarchy
• Material By Plant
• Material Group
•Plant
•Purchasing Document Related Dimensions
• Document Category
• Document Type
• Purchasing Group
• Purchasing Item Category
• Purchasing Organization
•Time Dimension
•Unit Of Measure
•Vendor
66SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Purchase Document History Section
•Vendor By Company
Typical queries for this section include:
•What is the average length (in days) between requisition and purchase
document generation?
•How many unconverted (no purchasing document generated)
requisitions are there this month by Company Code?
•What is the value of requisitions that have been converted to purchasing
documents for this quarter for a certain material group?
•For which purchasing documents have we not been invoiced?
•Did the quantity ordered or price change from requisition to purchasing
document?
•Does the quantity and price invoiced match the quantity and price
ordered?
3
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide67
Subject Areas
3
Purchase Document History Section
68SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
chapter
Reports
4
Overview
Overview
You can use the SAP BusinessObjects Purchasing Rapid Mart, version for
SAP solutions to do ad hoc analyses and produce many kinds of reports. This
chapter provides examples of reports you could produce. The information in
this chapter is useful for those who analyze and produce reports with the
Rapid Mart data.
This chapter provides a sample report and the recommended joins for each
componentized section in the Rapid Mart:
•Purchase Requisition
•Purchase Document
•Purchase Pricing
•Purchase Schedule Line
•Invoice Receipt
•Purchase Document History
SAP Master Data Reports are also described at the end of this chapter . These
reports are common across all Rapid Marts and are intended for hierarchy
discovery and record validation.
Purchase Requisition
The purchase requisition section allows you to analyze data and produce
reports for purchase requisition documents. The requisitions are detailed at
the line-item level. Various dimensions such as vendor, time dimension,
info-record, material, plant, etc. are available for analyses. This section also
tracks measures in both transaction (document) monetary currency and local
(company code) currency.
Reports
The Rapid Mart includes two reports for Purchase Requisitions:
•Requisition Listing
•Requisition Analysis
70SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Requisition Listing
View details of purchasing requisitions, including vendor, material, expected
delivery date, values in transaction currency, proc ess status, and purchasing
group (commonly the buyer).
SS_STATUS.REQ_PROCESS_STATUS_ID )
AND ( PURCH_REQ_FACT.MATERIAL_ID=MATERIAL.MATERIAL_ID )
AND
(
( COMPANY_COD E. CMPNY_CODE_NAME = 'IDES US INC'
)
AND
TIME_CREATE.CALENDAR_YEAR = 2000
AND
TIME_CREATE.CALENDAR_MONTH BETWEEN 1 AND 12
)
GROUP BY
COMPANY_CODE.CMPNY_CODE_FULL_NAME,
PURCH_REQ_FACT.REQUISITN_DOC_ID,
PURCH_REQ_FACT.REQUISITN_LINE_ITEM_ID,
PURCH_REQ_FACT.PURCH_REQ_DESCR,
PURCH_REQ_FACT.REQ_DATE,
PURCH_REQ_FACT.REQ_EXP_DELIV_DATE,
UOM_ORDER.UOM_DESCR,
PURCH_REQ_PROCESS_STATUS.REQ_PROCESS_STATUS_DESCR,
PURCH_REQ_FACT.CURR_ID_TRX,
PURCH_DOC_CATEGORY.DOC_CATEG_DESCR,
PURCH_GROUP.PURCH_GRP_DESCR,
PURCH_ORGANIZATION.PURCH_ORG_DESCR,
PURCH_ITEM_CATEGORY.PURCH_ITEM_CATEG_DESCR,
72SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
_CATEGORY.DOC_CATEG_ID and
DOCUMENT_CATEGORY.DIM_SRC_ID = 'PURCH'
_FACT.DOC_CATEG_ID and
DOCUMENT_TYPE.DOC_TYPE_ID=PURCH_REQ_
FACT.DOC_TYPE_ID and
DOCUMENT_TYPE.DIM_SRC_ID = 'PURCH'
ACT.INFORECORD_ID
H_REQ_FACT.INFORECORD_ID AND
INFORECORD_BY_ORG.PURCH_ORG_ID=PURCH
_REQ_FACT.PURCH_ORG_ID AND
INFORECORD_BY_ORG.PLANT_ID=PURCH_REQ_
FACT.PLANT_ID AND
INFORECORD_BY_ORG.INFORECORD_CATEG_ID
= @prompt('Enter Inforecord Category:','A',
'Inforecord by Org\Inforecord Category
Id',Mono,Free,Persistent,,User:0)
TERIAL_ID
ANT.PLANT_ ID and
PURCH_REQ_FACT.MATERIAL_ID=MATERIAL_BY
_PLANT.MATERIAL_ID
ROUP.MTRL_GRP_ID
SUPPLNG
IERARCHY.PROD_HIER_ID
ACT.PURCH_GRP_ID
76SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
RCH_REQ_FACT.STORAGE_LOCATN_ID and
STORAGE_LOCATION.PLANT_ID=PURCH_REQ_F
ACT.PLANT_ID
CHANGE_DATE
REQ_DATE
PO_DATE
T.UOM_ID_REQ
ON_AREA.VALUATN_AREA_ID
OR_ID
Q_FACT.VENDOR_ID and
VENDOR_BY_COMPANY.CMPNY_CODE_ID=PUR
CH_REQ_FACT.CMPNY_CODE_ID
4
Purchase Document
The purchase document section allows you to analyze data and produce
reports for purchase documents. The documents are detailed at the line-item
level. Various dimensions such as vendor, time dimension, info-record,
material, plant, etc. are available for analyses. This section also tracks
measures in both transaction (document) monetary currency and local
(company code) currency.
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide77
Reports
4
Purchase Document
Reports
The Rapid Mart includes these reports for Purchase Documents:
•Purchase Order Listing
•Purchase Order Details
•Top 10 Purchased Item Analysis
•Purchase Order Statistics
Purchase Order Listing
Overview of Purchase Orders at header level by Vendor. Includes Purchase
Order values in local (company code) currency, creation and validity dates,
and deletion indicator. Includes a hyperlink on Purchase Document Id to view
Purchase Order Details.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
“\Sample\DML”.
78SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Purchase Order Details
Shows details of Purchase Orders (header and line-item level detail).
Includes Purchase Order line item values in local (company code) currency,
creation and validity dates. This report includes a hyperlink for each purchase
order line-item to view its Purchase Pricing Conditions.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
“\Sample\DML”.
Reports
Purchase Document
4
Top 10 Purchased Item Analysis
Shows top 10 materials purchased for a month & year by values in local
(company code) currency. Also shows breakdowns by company code and
plant.
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide79
Reports
4
Purchase Document
Overall
View top 10 purchased items overall for the calendar year and month.
By Company
View top 10 purchased items for each Company.
80SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Purchase Document
By Plant
View top 10 purchased items for each Plant.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
“\Sample\DML”.
Reports
4
Purchase Order Statistics
Shows purchase order (document) counts as well as values for a month &
year. Available views include Overall By Company & Vendor, by Material
Group, and by Vendor.
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide81
Reports
4
Purchase Document
Overall
View purchase order statistics for all companies by local currency.
82SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Purchase Document
By Material Group
View purchase order statistics by company and material group.
Reports
4
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide83
Reports
4
Purchase Document
By Vendor
View purchase order statistics for all companies and displayed by vendor.
Calculations
•Purch Doc - AVG Net Loc = [Purch Doc - Net Loc]/[Purch Doc - Count
Purchase Documents]
Report SQL
All report SQL is located in the Rapid Mart installation directory under
“\Sample\DML”.
84SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Purchase Document
Recommended Table Joins
To analyze Purchase Document data you will need to create joins between the
fact and dimension tables as follows:
Note: Additional joins between dimension and hierarchy tables are shown in
“Recommended table joins” on page 124 for master report.
_CATEGORY.DOC_CATEG_ID and
DOCUMENT_CATEGORY.DIM_SRC_ID = 'PURCH'
_FACT.DOC_CATEG_ID and
DOCUMENT_TYPE.DOC_TYPE_ID=PURCH_DOC_
FACT.DOC_TYPE_ID and
DOCUMENT_TYPE.DIM_SRC_ID = 'PURCH'
ACT.INFORECORD_ID
H_DOC_FACT.INFORECORD_ID AND
INFORECORD_BY_ORG.PURCH_ORG_ID=PURCH
_DOC_FACT.PURCH_ORG_ID AND
INFORECORD_BY_ORG.PLANT_ID=PURC H_DOC_
FACT.PLANT_ID AND
INFORECORD_BY_ORG.INFORECORD_CATEG_ID
= @prompt('Enter Inforecord Category:','A', 'Inforecord
by Org\Inforecord Category
Id',Mono,Free,Persistent,,User:0)
_TERM.PAYMNT_TERM_ID AND
PAYMENT_TERM.PAYMNT_TERM_DAY_LIMIT = '?'
SUPPLNG
CING_PROCEDURE_HZ.PRICE_PROCEDURE_ID
and PRICING_PROCEDURE_HZ.APPLICTN_ID = 'M'
and PRICING_PROCEDURE_HZ.USAGE_ID = 'A'
IERARCHY.PROD_HIER_ID
ENTER.PROFIT_CNTR_ID AND
PURCH_DOC_FACT.CTRL_AREA_ID=PROFIT_CE
NTER.CTRL_AREA_ID
PURCH_DOC_FACT.CTRL_AREA_ID=PROFIT_CE
NTER_HIER_HZ.CTRL_AREA_ID and
PURCH_DOC_FACT.PROFIT_CNTR_ID=PROFIT_C
ENTER_HIER_HZ.PROFIT_CNTR_ID
PURCH_DOC_FACT.CTRL_AREA_ID=PROFIT_CE
NTER_HIER_VR.CTRL_AREA_ID and
PURCH_DOC_FACT.PROFIT_CNTR_ID=PROFIT_C
ENTER_HIER_VR.CHILD_ID
PURCH_DOC_PRICE_HISTORY.INFORECORD_ID=
PURCH_DOC_FACT.INFORECORD_ID AND
PURCH_DOC_PRICE_HISTORY.PURCH_DOC_ID=
PURCH_DOC_FACT.PURCH_DOC_ID AND
PURCH_DOC_PRICE_HISTORY.PURCH_LINE_ITE
M_ID=PURCH_DOC_FACT.PURCH_LINE_ITEM_ID
RCH_DOC_FACT.STORAGE_LOCATN_ID and
STORAGE_LOCATION.PLANT_ID=PURCH_DOC_F
ACT.PLANT_ID
CREATE_DATE
CHANGE_DATE
PURCH_DOC_DATE
T.UOM_ID_ORDER
T.UOM_ID_PRICE
OR_ID
C_FACT.VENDOR_ID and
VENDOR_BY_COMPANY.CMPNY_CODE_ID=PURC
H_DOC_FACT.CMPNY_CODE_ID
Purchase Pricing
4
The purchase pricing section allows you to analyze pricing conditions on
purchasing documents. These include list price, gross price, discounts to list
price, and net price after discounts. Pricing conditions are at a finer level of
detail than the line-items on the documents (there can be multiple pricing
conditions per line-item). Various dimensions such as Condition Category,
Condition Class, Condition Type, purchase document history vendor, time
dimension, info-record, material, plant, etc. are available for analyses. This
section also tracks measures in both transaction (document) monetary
currency and local (company code) currency.
Reports
The Rapid Mart includes these reports for Purchase Pricing:
•Purchase Pricing Conditions
•Purchase Pricing Condition Trend
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide87
Reports
4
Purchase Pricing
Purchase Pricing Conditions
Lists detailed pricing conditions for a particular purchasing document and
line-item. Includes all conditions assigned to the document and line-item.
Shows local (company code) currency rates for the conditions.
Calculations
•Rate Unit = If([Calculation Type Id] = "A"; "%"; [Currency Id Loc])
Report SQL
All report SQL is located in the Rapid Mart installation directory under
“\Sample\DML”.
Purchase Pricing Condition Trend
Shows changes over time (months) of the values for a particular pricing
condition type in a single year. Can be displayed by Plant or Purchasing
Organization.
88SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
By Plant
View purchase pricing trend measures by plant.
Reports
Purchase Pricing
4
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide89
Reports
4
Purchase Pricing
By Purchasing Organization
View purchase pricing trend measures by purchase organization.
Calculations
•Rate Unit = If([Calculation Type Id] = "A"; "%"; [Currency Id Loc])
Report SQL
All report SQL is located in the Rapid Mart installation directory under
“\Sample\DML”.
Recommended Table Joins
To analyze Purchase Document data you will need to create join s between the
fact and dimension tables as follows:
90SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Purchase Pricing
Note: Additional joins between dimension and hierarchy tables are shown in
“Recommended table joins” on page 124 for master reports.
T_CATEGORY.DIM_SRC_ID and
DOCUMENT_CATEGORY.DIM_SRC_ID = 'PURCH'
E_FACT.DOC_CATEG_ID and
DOCUMENT_TYPE.DOC_TYPE_ID=PURCH_PRICE
_FACT.DOC_TYPE_ID and
DOCUMENT_TYPE.DIM_SRC_ID = 'PURCH'
FACT.INFORECORD_ID
_PRICE_FACT.INFORECORD_ID AND
INFORECORD_BY_ORG.PURCH_ORG_ID=PURCH
_PRICE_FACT.PURCH_ORG_ID AND
INFORECORD_BY_ORG.PLANT_ID=PURCH_PRIC
E_FACT.PLANT_ID AND
INFORECORD_BY_ORG.INFORECORD_CATEG_ID
= @prompt('Enter Inforecord Category:','A', 'Inforecord
by Org\Inforecord Category
Id',Mono,Free,Persistent,,User:0)
ATERIAL_ID
4
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide91
LANT.PLANT_ID and
PURCH_PRICE_FACT.MATERIAL_ID=MATERIAL_B
Y_PLANT.MATERIAL_ID
GROUP.MTRL_GRP_ID
T_TERM.PAYMNT_TERM_ID AND
PAYMENT_TERM.PAYMNT_TERM_DAY_LIMIT = '?'
DITION.CONDITN_ID AND
PURCH_PRICE_FACT.CONDITN_SEQ_ID=PRICING
_CONDITION.CONDITN_SEQ_ID
ICING_PROCEDURE_HZ.PRICE_PROCEDURE_ID
and PRICING_PROCEDURE_HZ.APPLICTN_ID = 'M'
and PRICING_PROCEDURE_HZ.USAGE_ID = 'A'
HIERARCHY.PROD_HIER_ID
CENTER.PROFIT_CNTR_ID AND
PURCH_PRICE_FACT.CTRL_AREA_ID=PROFIT_CE
NTER.CTRL_AREA_ID
PURCH_PRICE_FACT.CTRL_AREA_ID=PROFIT_CE
NTER_HIER_HZ.CTRL_AREA_ID and
PURCH_PRICE_FACT.PROFIT_CNTR_ID=PROFIT_
CENTER_HIER_HZ.PROFIT_CNTR_ID
PURCH_PRICE_FACT.CTRL_AREA_ID=PROFIT_CE
NTER_HIER_VR.CTRL_AREA_ID and
PURCH_PRICE_FACT.PROFIT_CNTR_ID=PROFIT_
CENTER_HIER_VR.CHILD_ID
PURCH_PRICE_FACT.PURCH_DOC_ID=PURCH_D
OC_FACT.PURCH_DOC_ID and
PURCH_PRICE_FACT.PURCH_LINE_ITEM_ID=PUR
CH_DOC_FACT.PURCH_LINE_ITEM_ID
PURCH_DOC_PRICE_HISTORY.INFORECORD_ID=
PURCH_PRICE_FACT.INFORECORD_ID AND
PURCH_DOC_PRICE_HISTORY.PURCH_DOC_ID=
PURCH_PRICE_FACT.PURCH_DOC_ID AND
PURCH_DOC_PRICE_HISTORY.PURCH_LINE_ITE
M_ID=PURCH_PRICE_FACT.PURCH_LINE_ITEM_I
D
RCH_PRICE_FACT.PURCH_DOC_SRC_ID
FACT.PURCH_GRP_ID
D=PURCH_PRICE_FACT.PURCH_ITEM_CATEG_ID
92SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
RCH_PRICE_FACT.STORAGE_LOCATN_ID and
STORAGE_LOCATION.PLANT_ID=PURCH_PRICE_
FACT.PLANT_ID
T.CREATE_DATE
T.CHANGE_DATE
T.PURCH_DOC_DATE
CT.UOM_ID_ORDER
CT.UOM_ID_CONDITN
CT.UOM_ID_BASE
DOR_ID
CE_FACT.VENDOR_ID and
VENDOR_BY_COMPANY.CMPNY_CODE_ID=PURC
H_PRICE_FACT.CMPNY_CODE_ID
4
Purchase Schedule Line
The Purchasing Schedule Line details delivery information for purchasing
documents. There can be multiple schedule lines for each purchasing
document line-item. Each schedule line details a different delivery of the
line-item.
Example: a line item of quantity 50 could be broken down into two
deliveries of 30 (on May 01), and 20 (on May 15). Each of these deliveries
would be a separate schedule line.
Various dimensions such as purchase document price history, vendor, time
dimension, info-record, material, plant, etc. are available for analyses. This
section also tracks measures in both transaction (document) monetary
currency and local (company code) currency.
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide93
Reports
4
Purchase Schedule Line
Reports
The Rapid Mart includes one report for Purchase Schedule Lines, called
Goods Receipt Scheduling Efficiency.
Goods Receipt Scheduling Efficiency
Shows “Average Days Goods Receipt” for a Company and a range of years.
Available views by Plant, and by Storage Location.
By Plant
View goods receipt scheduling efficiency (according to pre-defined intervals)
by Plant.
94SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Purchase Schedule Line
By Storage Location
View goods receipt scheduling efficiency (according to pre-defined intervals)
by Storage Location.
4
Report SQL
All report SQL is located in the Rapid Mart installation directory under
“\Sample\DML”.
Recommended Table Joins
T o analyze Purchase Schedule Line data you will need to create joins between the
fact and dimension tables as follows:
Note: Additional joins between dimension and hierarchy tables are shown in
“Recommended table joins” on page 124 for master reports.
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide95
Reports
4
Purchase Schedule Line
Note: In these joins, we use PURCH_DOC_FACT as a dimension.
CUMENT_CATEGORY.DOC_CATEG_ID and
DOCUMENT_CATEGORY.DIM_SRC_ID = 'PURCH'
_SCHED_LINE_FACT.DOC_CATEG_ID and
DOCUMENT_CATEGORY.DIM_SRC_ID = 'PURCH'
ED_LINE_FACT.DOC_CATEG_ID and
DOCUMENT_TYPE.DOC_TYPE_ID=PURCH_SCHE
D_LINE_FACT.DOC_TYPE_ID and
DOCUMENT_TYPE.DIM_SRC_ID = 'PURCH'
_LINE_FACT.INFORECORD_ID
H_SCHED_LINE_FACT.INFORECORD_ID AND
INFORECORD_BY_ORG.PURCH_ORG_ID=PURCH
_SCHED_LINE_FACT.PURCH_ORG_ID AND
INFORECORD_BY_ORG.PLANT_ID=PURCH_SCHE
D_LINE_FACT.PLANT_ID AND
INFORECORD_BY_ORG.INFORECORD_CATEG_ID
= @prompt('Enter Inforecord Category:','A', 'Inforecord
by Org\Inforecord Category
Id',Mono,Free,Persistent,,User:0)
AYMENT_TERM.PAYMNT_TERM_ID AND
PAYMENT_TERM.PAYMNT_TERM_DAY_LIMIT = '?'
ANT_ID
ANT_ID_SUPPLNG
DUCT_HIERARCHY.PROD_HIER_ID
ROFIT_CENTER.PROFIT_CNTR_ID AND
PURCH_SCHED_LINE_FACT.CTRL_AREA_ID=PRO
FIT_CENTER.CTRL_AREA_ID
FIT_CENTER_HIER_HZ.CTRL_AREA_ID and
PURCH_SCHED_LINE_FACT.PROFIT_CNTR_ID=P
ROFIT_CENTER_HIER_HZ.PROFIT_CNTR_ID
FIT_CENTER_HIER_VR.CTRL_AREA_ID and
PURCH_SCHED_LINE_FACT.PROFIT_CNTR_ID=P
ROFIT_CENTER_HIER_VR.CHILD_ID
PURCH_SCHED_LINE_FACT.PURCH_DOC_ID=PU
RCH_DOC_FACT.PURCH_DOC_ID and
PURCH_SCHED_LINE_FACT.PURCH_LINE_ITEM_I
D=PURCH_DOC_FACT.PURCH_LINE_ITEM_ID
PURCH_DOC_PRICE_HISTORY.INFORECORD_ID=
PURCH_SCHED_LINE_FACT.INFORECORD_ID
AND
PURCH_DOC_PRICE_HISTORY.PURCH_DOC_ID=
PURCH_SCHED_LINE_FACT .PURCH_DOC_ID AND
PURCH_DOC_PRICE_HISTORY.PURCH_LINE_ITE
M_ID=PURCH_SCHED_LINE_FACT.PURCH_LINE_I
TEM_ID
RCH_SCHED_LINE_FACT.STORAGE_LOCATN_ID
and
STORAGE_LOCATION.PLANT_ID=PURCH_SCHED
_LINE_FACT.PLANT_ID
NE_FACT.CREATE_DATE
NE_FACT.CHANGE_DATE
NE_FACT.PURCH_DOC_DATE
NE_FACT.UOM_ID_ORDER
NE_FACT.UOM_ID_PRICE
T.VENDOR_ID
HED_LINE_FACT.VENDOR_ID and
VENDOR_BY_COMPANY.CMPNY_CODE_ID=PURC
H_SCHED_LINE_FACT.CMPNY_CODE_ID
Invoice Receipt
Invoice Receipts detail the invoices received from the vendors. They
represent the vendor’s bill for items purchased. They are matched to the
Purchasing Document and should correspond to the quantities delivered
(Goods Received).
Various dimensions such as purchase document price history, vendor, time
dimension, info-record, material, plant, etc. are available for analyses. This
section also tracks measures in both transaction (document) monetary
currency and local (company code) currency.
Reports
The Rapid Mart includes these reports for Invoice Receipts:
•Invoice Receipt Detail
•Receiving Plant Trend Analysis
98SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Invoice Receipt Detail
For a company and fiscal period, details all invoices received. Invoices are
cross-referenced to their purchase document line-item. The report includes
quantity and amount invoiced.
Reports
Invoice Receipt
4
Report SQL
All report SQL is located in the Rapid Mart installation directory under
“\Sample\DML”.
SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide99
Reports
4
Invoice Receipt
Receiving Plant Trend Analysis
For a Company and Calendar Year, shows values of invoices received by
receiving plant, plant’s city, and plant’s country.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
“\Sample\DML”.
Recommended Table Joins
To analyze Invoice Receipt data you will need to create joins between the fact and
dimension tables as follows:
100SAP BusinessObjects Purchasing Rapid Mart XI 3.2 for SAP solutions User Guide
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.