Professional Documents
Culture Documents
MOUNIKA BANDAM
CONTENTS
Slide 2
W_PURCH_COST_F
Dimensions Used
Details Of Dimensions
Schema Design
Metrics
Source Tables
SDE Mapping
SIL Mapping
EBS Form
W_PURCH_COST_F
Slide 3
W_PURCH_COST_F table is used to capture all the purchase costs related info that are distributed
on the basis of amount or value by the purchasing unit of a business organization (purchasing
organization).
There could be many types of purchase orders and would typically include one-time, regular, blanket,
release, and so on.
The data in this table is stored at the purchase order distribution level. Purchase orders, or the
shipments, are distributed among different receivers, accounts, or cost centers.
Dimensions Used
Slide 4
W_LEDGER_D
W_INT_ORG_D
W_BUSN_LOCATION_D
W_STATUS_D
W_XACT_TYPE_D
W_USER_D
W_PROJECT_D
W_SUPPLIER_ACCOUNT_D
W_INVENTORY_PRODUCT_D
W_SUPPLIER_PRODUCT_D
W_TASK_D
W_PRODUCT_D
W_GL_ACCOUNT_D
W_CODE_D
W_PARTY_ORG_D
W_EMPLOYEE_D
W_PROFIT_CENTER_D
W_COST_CENTER_D
Details Of Dimensions
Slide 5
1. W_LEDGER_D
This table is used to store the ledger information.
This table is designed to be a slowly changing dimension that supports Type-1 changes.
The Grain of W_LEDGER_D is LEDGER_ID, which is sourced from GL_LEDGERS.
The INTEGRATION_ID in this table is the LEDGER_ID.
2. W_INT_ORG_D
The W_INT_ORG_D is the primary table for storing the Organizations from the OLTP
System.
The Grain of W_INT_ORG_D is ORGANIZATION_ID, which is sourced from
HR_ALL_ORGANIZATION_UNITS.
This table is designed to be a slowly changing dimension that supports Type-2 changes.
The INTEGRATION_ID in this table is the ORGANIZATION_ID.
Details Of Dimensions
Slide 6
3. W_BUSN_LOC_D
This Dimension stores the information about the locations. The locations used in this fact are
Storage, Plant and Receiving the goods.
The INTEGRATION_ID for Storage Location is 'STORAGE_LOC' || '~' ||
TO_CHAR(ORGANIZATION_ID) || '~' || SECONDARY_INVENTORY_NAME || '~'
The INTEGRATION_ID for Plant Location is 'PLANT' || '~' ||
TO_CHAR(ORGANIZATION_ID).
The INTEGRATION_ID for Receiving Location is 'RECIPIENT_LOC' || '~' ||
TO_CHAR(LOCATION_ID).
This table is designed to be a slowly changing dimension that supports Type-2 changes.
4. W_STATUS_D
The W_STATUS_D dimension table is used for tracking attributes associated with statuses.
The INTEGRATION_ID in this table is the 'ACCT_DOC_STATUS'||'~'||STATUS_CODE||'~'||
STATUS_CAT.
This table is designed to be a Type-1 dimension.
Details Of Dimensions
Slide 7
5. W_XACT_TYPE_D
W_XACT_TYPE_D dimension table defines various transaction types as available from the
domain and client value lists.
The transaction types used to populate this fact are: Consigned Code, Invoice Line Type, PO
Payment Type, PO Shipment Type, Agreement Leverage Type.
This table is designed to be a Type-1 dimension.
6. W_USER_D
W_USER_D dimension table contains information about users who created or modified
records
in the source system, from which the rows have been extracted.
The grain of this table is at a single 'User' level.
The INTEGRATION_ID is TO_CHAR(USER_ID).
This table is designed to be a slowly changing dimension that supports Type-2.
Details Of Dimensions
Slide 8
7. W_PROJECT_D
The project dimension contains various attributes defining a Project, like Project Name,
Project
Type, Priority, Cost and Revenue Accrual methods, Invoicing and billing methods.
The Grain of W_PROJECT_D is PROJECT_ID, which is sourced from PA_PROJECTS_ALL.
The INTEGRATION_ID is TO_CHAR(PROJECT_ID).
This table is designed to be a slowly changing dimension that supports Type-2 changes.
8. W_SUUPLIER_ACCOUNT_D
This table tracks all the attributes associated with supplier accounts.
This table is designed to be a slowly changing dimension that supports Type-2 changes.
The INTEGRATION_ID is TO_CHAR(VENDOR_SITE_ID).
The Grain of W_SUUPLIER_ACCOUNT_D is VENDOR_SITE_ID, which is sourced from
PO_VENDOR_SITES_ALL.
Details Of Dimensions
Slide 9
9. W_INVENTORY_PRODUCT_D
This dimension table is used to maintain information on the inventory policies and processes
followed for handling products for a specific
organization.
The Grain of this dimension is ORGANIZATION_ID and INVENTORY_ITEM_ID, which is
sourced from MTL_SYSTEM_ITEMS_B.
The INTEGRATION_ID is TO_CHAR(INVENTORY_ITEM_ID) ||~||
TO_CHAR(ORGANIZATION_ID).
This table is designed to be a slowly changing dimension that supports Type-2 changes.
10. W_SUUPLIER_PRODUCT_D
W_SUPPLIER_PRODUCT_D dimension table is used to maintain information on products
supplied by specific suppliers for a specific purchasing organization.
This table is designed to be a slowly changing dimension that supports Type-2 changes.
The INTEGRATION_ID is TO_CHAR(INVENTORY_ITEM_ID) || '~' ||
TO_CHAR(VENDOR_ID) || '~' ||IIF(USING_ORGANIZATION_ID = -1,
'G~'||TO_CHAR(OPERATING_UNIT_ID_VAR),
TO_CHAR(USING_ORGANIZATION_ID))|| '~' || TO_CHAR(VENDOR_SITE_ID)).
'L~'||
Details Of Dimensions
Slide 10
11. W_TASK_D
The Task dimension table stores task related attributes like task name, task type, task service
type, billable flag etc and also the scheduling information like start date and completion date etc.
This table is designed to be a slowly changing dimension that supports Type-2 changes.
The Grain of this dimension is TASK_ID, which is sourced from PA_TASKS.
The INTEGRATION_ID is TO_CHAR(TASK_ID).
12. W_PRODUCT_D
Product entity stores information about the Products of various product types.
The grain of this table is at the level of Unique Product defined in the source systems Product
Master.
The INTEGRATION_ID in this table is the INVENTORY_ITEM_ID (EBS) or Product Num.
This table is designed to be a slowly changing dimension that supports Type-2 changes.
Details Of Dimensions
Slide 11
13. W_GL_ACCOUNT_D
This dimension table stores your General Ledger accounts. The GROUP_ACCOUNT_NUM field
categorizes GL accounts into various groups.
The Grain of this table is CODE_COMBINATION_ID, which is sourced from
GL_CODE_COMBINATIONS.
The INTEGRATION_ID is TO_CHAR(CC_ID).
This table is designed to be a slowly changing dimension that supports Type-2 changes.
14. W_CODE_D
W_CODE_D is the Data Warehouse Codes Table that stores all the standardized Code and Name
combinations for all languages within the Data Warehouse based on the source codes and
descriptions.
The grain of this table is a combination of columns that define the Source System it originated
from (DATASOURCE_NUM_ID), the source code used in that system (SOURCE_CODE), the
code categorization (CATEGORY) and the language in which the standardized description is
provided (LANGUAGE_CODE).
Details Of Dimensions
Slide 12
15. W_PARTY_ORG_D
Party Organization Dimension includes B2C Customer , Supplier, Competitor data.
The grain of this table is PARTY_ID of HZ_PARTIES.
The INTEGRATION_ID in this table is the PARTY_ID.
16. W_EMPLOYEE_D
W_EMPLOYEE_D dimension table stores personal information about employees belonging to
this organization as well as its 'extended organization'.
The grain of this table is at a single 'Employee' level, which is sourced from
PER_ALL_PEOPLE_F.
The INTEGRATION_ID is TO_CHAR(PERSON_ID).
This table is designed to be a slowly changing dimension that supports Type-2 changes.
Schema Design
Slide 13
W_BUSN_LOCATION_D
W_PROFIT_CENTER_D
W_STATUS_D
W_XACT_TYPE_D
W_TASK_D
W_PRODUCT_D
W_SUUPLIER_PRODUCT_
D
W_PROJECT_D
W_PURCH_COST_F
W_LEDGER_D
W_USER_D
W_EMPLOYEE_D
W_GL_ACCOUNT_D
W_INT_ORG_D
W_INVENTORY_PRODUCT
_D
W_SUPPLIER_ACCOUNT_
DW_COST_CENTER_D
W_PURCH_COST_F
Slide 14
Column Name
Description
SUPPLIER_WID
This indicates the supplier on whom the purchase order has been
placed.
PRODUCT_WID
This indicates the product which is being sourced from the supplier
on the purchase receipt line item.
INVENTORY_PROD_WID
SUPPLIER_PROD_WID
REQUESTOR_WID
PLANT_LOC_WID
INVENTORY_ORG_WID
STORAGE_LOC_WID
W_PURCH_COST_F
Slide 15
Column Name
Description
RCPT_LOC_WID
COST_CENTER_WID
This indicates the cost center to which the expenses incurred in sourcing
would be distributed to.
PROFIT_CENTER_WID
This indicates the profit center to which the purchase cost that is
distributed is booked into This helps accumulate revenues against
profit centers as part of inventory transactions.
PURCH_ORG_WID
BUSN_AREA_ORG_WI
D
CTRL_AREA_ORG_WI
D
GL_ACCOUNT_WID
This is the General Ledger account number into which the payables
entries generated as part of the purchase order execution would be
posted into.
W_PURCH_COST_F
Slide 16
Column Name
Description
COMPANY_ORG_WID
BUYER_WID
This indicates the buyer who placed the purchase order/helped prepare
it.
OPERATING_UNIT_ORG_W
ID
APPROVAL_STATUS_WID
This indicates the current approval status of the purchase order. This
could change during the lifecycle of the purchase order.
XACT_TYPE_WID
This indicates the specific type of the purchase order. There could be
further sub-classifications to these purchase order types. There could be
domain values mapped for each of these transactions into the W_ type
domain value columns in W_XACT_TYPE_D.
DIST_QTY
The quantity that was distributed or assigned to this cost center. The
total quantity distributed for all cost centers equals the total quantity
ordered in the schedule line.
W_PURCH_COST_F
Slide 17
Column Name
Description
LINE_AMT
GLOBAL1_EXCHANGE_RATE
PURCH_ORDER_NUM
PURCH_RQSTN_NUM
Metrics
Slide 18
Distributed PO Quantity determines the quantity of a total order distributed to a cost center. It
tracks how much of a purchase order has gone to a particular cost center when the ordered product
has been split across multiple cost centers.
Distributed PO Amount tracks the distributed amount of the purchase order that will be charged to a
cost center. The amount is displayed in a standard currency.
# Of PO is the number of distinct purchase orders for an entity such as Supplier, Buyer, or Receiving
Location. The PO Volume metric is used to identify ordering volume for a particular entity.
# Of Requisition is the number of distinct purchase requisitions the purchase orders come from. The
Requisition Volume metric is used to identify requisitioning volume for a particular entity.
PO Input Ratio tracks the Input ratio, which is a measure of buyer performance. It is calculated by
dividing the number of order distributions created from purchase requisition by total number of order
distributions.
W_PURCH_COST_F
Slide 19
PO_DISTRIBUTION
S_ALL
SDE_ORA_PurchaseCostFact
PO_LINE_LOCATIO
NS_ALL
PO_LINES_ALL
PO_HEADERS_ALL
W_PURCH_COST_FS
W_PURCH_COST_F
PO_REQUISITION_
LINES_ALL
PO_DOC_STYLE_H
EADERS
PO_RELEASES_ALL
SIL_PurchaseCostFact
Source Tables
Slide 20
SDE MAPPING
Slide 22
SIL MAPPING
Slide 23
EBS FORM
Slide 24
PO_DISTRIBUTIONS_ALL
Slide 25
THANK YOU