Md070-Pdh Rtods Interface 47782

x
Author: Idris Ali

Creation Date: 28 Aug 2015
Last Updated: 09_May-2019
Version: 1.3
Document Preface
Document Overview
This document contains details about functional requirements and technical design components. While
creating or updating this document, if a specific section or item is not applicable to your
requirement/need/object, remove that specific section/item – it can always be reinserted later if needed.
Whenever there are changes to this document, the “Document Revision History” section of the
“Document Preface” must be filled with appropriate information. These changes must be communicated
to all previous recipients of this document in order to review and approve the change.
Both the function analyst and the technical designer/developer will maintain this document. Additionally,
different sections of this document are written with different audiences as recipients. Below are details of
the responsibilities of each project member based on the sections of the document.
Document Revision History

Date Version Description Author Project Number/ Change ID
28 Aug 2015 1.0 Initial Version Idris Ali 42449

18 Sep 2017 1.1 Updated for 47781 Rakesh 47781
Gupta
22 Oct 2018 1.2 Updated for 47768 Mahaboob 47768

Basha
21-Mar-2019 1.2 Updated for EMEA Inderjeet 47782

WAVE2- 47782 Kaur
09-May-2019 1.3 Updated for 47782 Rakesh 47782

Gupta
Document Reviewers
Date Version Name Comments
10-May-2019 1.3 Inderjeet Kaur 1. Reviewed for 47782- EMEA

WAVE2 for new Oracle ECP view
definition.
Document Approvals
Contents
Document Preface....................................................................................................................................... 2
Contents...................................................................................................................................................... 3
1. Requirements Overview...................................................................................................................... 4
1.1 Introduction.................................................................................................................................. 4
1.2 Business Requirements <Mandatory>......................................................................................... 4
1.3 Technical Requirements <Mandatory>........................................................................................ 5
1.4 Approach <Mandatory>............................................................................................................... 6
2. Custom Objects................................................................................................................................. 10
2.1 Database Design....................................................................................................................... 10
2.1.1 Database Objects (Custom Tables/View/Sequence/Indexes etc.).............................10
3. Technical Details............................................................................................................................... 11
3.1 Program Logic and Pseudo Code.............................................................................................. 11
3.1.1. File Formats:................................................................................................................ 11
3.1.2 Modification in View Query:...........................................................................................22
3.1.3 Changes at PDH End:...............................................................................................24
3.1.4 Concurrent program to update UDAs in PDH:...............................................................36
3.1.5 PDH to P360 view Changes (Added in version 1.2)......................................................37
4. Open/Closed Issues.......................................................................................................................... 40
4.1 Open Issues............................................................................................................................... 40
4.2 Closed Issues............................................................................................................................ 41
5. Traceability Matrix............................................................................................................................. 42
1.Requirements Overview
1.1 Introduction
The purpose of this document is to describe the technical design specifications to specify how RTODS
Feeds will flow into PDH for ERP Status and ERP Hierarchy.
1.2 Business Requirements <Mandatory>

Project Number/Change ID Requirement ID Description
The system shall enable the

capability to load Product Codes
from ERP's into PDH as Registry
Style Hub Attributes once Item has
42449 been Published.
GR-1.17.2

capability to auto-associate the
Product Code to the correct item.
No user intervention shall be
required to perform relationship to
42449 item.
GR-1.17.4
The solution shall provide the ability

for the ERP status to be obtained in
42449 a batch mode once a day from ERP
GR-1.22 or RT-ODS data source
The solution shall ensure that PDH

System Names are mapped correctly
to ERP System Names in RT-ODS
to ensure ERP and Item statuses are
42449 updated for the correct System Entity
GR-1.31 and MFG-ID in PDH
Technical team shall set up a feed of

42449 PRODUCT_CODE from Global
CA13 Vista(RTODS) to Product Data Hub
Few UDAs and operational attributes

47781 to be fetched from RTODS to PDH
for SAP-UNITY
47781 UDAs added in the feed to be

updated in PDH base tables
Added in Version 1.2
47768 IDW - Bussmann, PQ,

47768 47768 Bussmnn-PQ Vista/GV- Pricing details from SAP to
IDW Mappings Design (6).xlsx P360
47782
P360.47782.005 Additional Sales Orgs option
47782
P360.44782.17 Distribution Channel
The solution should provide the

47782 Oracle Operational ability to load Oracle ERP data from
mapping.xlsx RTODS to PDH
1.3 Technical Requirements <Mandatory>

Requirement ID Description Solution Overview
capability to load Product Codes
from ERP's into PDH as Registry
Style Hub Attributes once Item has ETL Feed from RTODS to PDH to
GR-1.17.2 been Published bring Product Code Hierarchy
capability to auto-associate the
Product Code to the correct item.
No user intervention shall be ETL Feed from RTODS to PDH to
required to perform relationship to bring Product Code relationship with
GR-1.17.4 item. Item
The solution shall provide the
ability for the ERP status to be
obtained in a batch mode once a ETL Feed from RTODS to PDH to
day from ERP or RT-ODS data bring Product Details (ERP ID,ERP
GR-1.22 source Status..etc).
The solution shall ensure that PDH
System Names are mapped
correctly to ERP System Names in
RT-ODS to ensure ERP and Item
statuses are updated for the
correct System Entity and MFG-ID
in PDH
ETL Feed to use existing Mappings in
GR-1.31 RTODS for System Names
CA13 Technical team shall set up a feed The ETL Feed developed will be
of PRODUCT_CODE from Global configured for Vista and Global Vista.
Vista to Product Data Hub
New attributes will be added in

SRC_SAP_UNITY_V view and all
other ERP Views (with NULL value in
other ERP Views) in RTODS and
Few UDAs and operational XXPDH_ERP_PRODUCTS,
attributes to be fetched from XXPDH_ERP_PRODUCT_LINES
RTODS to PDH for SAP-UNITY table in PDH
A concurrent program will be created
in PDH which will fetch the data from
XXPDH_ERP_PRODUCTS TABLE
UDAs added in the feed to be and will update the item UDAs using
updated in PDH base tables API
47768 Bussmnn-PQ ETL Feed from RTODS to PDH to

Version 1.2 IDW Mappings Design (6).xlsx bring Pricing details
Additional Sales Orgs option-
Existing SRC_SAP_UNITY_V in RTODS
will be updated to add new sales_org
Additional Sales Orgs option- for EMEA WAVE2
P360.47782.005 Vkorg column of mvke table
Distribution Channel
Existing SRC_SAP_UNITY_V in RTODS
will be updated to add new
distribution channel for EMEA
Distribution Channel WAVE2
P360.44782.17 Vtweg column of mvke table
An ETL Job exists which brings the
ERPs data from RTODS to ERP
product and Product Lines table in
PDH. A new View will be created in
RTODS for Oracle ERP and
corresponding mapping will be done
47782-The solution should provide in this existing ETL job so that same
the ability to load Oracle ERP data ETL job brings the Oracle ERP data
Version 1.3 from RTODS to PDH also to PDH
1.4 Approach <Mandatory>
Interface Design
New RTODS Control Table for PDH feeds
RTODS_PDH_REFRESH_WATERMARK
JOB Source Insta Dom From Fetch To Fetch

ID System nce ain Schema Job Name Date Date STATUS
<instance>_ODS <Session Name>
1 VISTA01 VTA VTA_ODS s_load_PDH_VISTA 24-Aug-15 25-Aug-15 RUNNING

2 VISTA01 VTA VTA_ODS s_load_PDH_VISTA 23-Aug-15 24-Aug-15 COMPLETED
Informatica Workflow
Informatica Workflow
1. ERP Workflow
VISTA01 Prod Session VISTA02 Prod Session VISTA03 Prod Session CSAP Prod Session
Populate Control
Table for all ERP
HYD PUN Prod Session HYD CHY Prod Session AERO Prod Session
VISTA01 Hier Session VISTA02 Hier Session VISTA03 Hier Session CSAP Hier Session
HYD PUN Hier Session HYD CHY Hier Session AERO Hier Session
Informatica Mapping
1. Populate Control Table for all ERP
TPH_OBAW_DATASRCNUM_XREF
Get Most Recent Assign TO_date to

Lookup Source System Name based on
RTODS_PDH_REFRESH_WATERMARK record for each From_Date and TO_Date RTODS_PDH_REFRESH_WATERMARK
Instance
ERP to Today's Date
2. ERP Mapping For Product Data
RTODS_PDH_REFRESH_WATERMARK
ERP Query for

Data in Standard Upsert in Target
Product Data with Lookup For Status XXPDH_ERP_PRODUCTS
Format Table
Dates from Control
Table
XXPDH_ALT_HIER_PROD
_INT
LKUP PDH_ERP_STATUS_XREF
New mapping will be created in ETL to get the pricing details from new view from RTODS to PDH
Source and target table details
Source View :- ZQTC_SYND_PRICE_PDH_V(RTODS)
Target Table:- XXETN.XXPDH_RTODS_SYND_PRICE(PDH)
Please refer section 3.1.3 for details table structure and constraints
3. ERP Mapping for Hierarchy Data

Either All of hierarchy will be loaded , or Nothing (If any updates are made to Hierarchy in Source System)
ERP Query for

Product Hierarchy Data in Standard Insert in Target
XXPDH_ALT_HIERARCHY_INT
Dates from Control Format Table
Table (to extract all
Hierarchy nodes if
anything is modified)
2.Custom Objects
2.1 Database Design
2.1.1 Database Objects (Custom Tables/View/Sequence/Indexes etc.)

Object Name Object Type Owner Description Updated in Ver
PDH Table : Interface table for

XXPDH_ALT_HIER_PROD_INT Table Item –Hierarchy relationship
XXETN
PDH Table : Interface able for

XXPDH_ALT_HIERARCHY_INT Alternate Hierarchies
Table XXETN
PDH Table : Table to hold ERP

Product Information like Status,
MFG_Id , Quantity , Warehouse
XXPDH_ERP_PRODUCTS etc.
Table XXETN
PDH Table : Table to hold Org

XXPDH_ERP_PRODUCT_LINES specific data
Table XXETN
RTODS Table : Control table

RTODS_PDH_REFRESH_WATERM which will have details and
ARK status of Each Batch run.
Table XXETN
RTODS Table: Table with

XREF of all ERP System
TPH_OBAW_DATASRCNUM_XREF Names in PDH.
Table XXETN
A View on
XXPDH_ERP_PRODUCTS
table which will fetch only
master org level details about a
product from ERP. (All fields
which are not dependent on
XXPDH_ERP_PROD_MSTR_V View warehouse/ inventory Org).
XXETN
PDH Table : will be used to 1.2

XXPDH_RTODS_SYND_PRICE Table store pricing details in PDH
XXETN
RTOD
ZQTC_SYND_PRICE_PDH_V View RTODS View: View for pulling 1.2
price details from table
ZQTC_SYND_PRICE
RTODS Table to capture the list 1.2

XXPDH_BUSSMAN_SALES_ORG_E of sales orgs are enabled for
NABLE Table PDH
RTODS
3.Technical Details
3.1 Program Logic and Pseudo Code
3.1.1. File Formats:

Following format should be used to write the Query for each ERP for extracting the Product Data.
Sequence Attribute Description Updated in

in Query
Catalog No of the Product, this should match the catalog

1 ERP_CATALOG_NUM number in PDH.
Part No / Style No from ERP which uniquely identifies a

2. ERP_MANUFACTURING_ID Part in ERP.
Status of Part in ERP system (Active, Retired etc.).
NOTE: This should be Master Product Status and not

3. ERP_ITEM_STATUS Warehouse/Inventory Org level status.
Hierarchy Name from the ERP, this should match the

Alternate Catalog Name in PDH.
4 ERP_HIER_NAME (Example : <ERPNAME> Prod Code
Hierarchy Node in the ERP Hierarchy this Product (part) is

5 ERP_PRODUCT_CODE linked to.
6 ERP_LEAD_TIME Lead time for the Product.
Country of Origin for this Product.This field was not

7 ERP_COUNTRY_OF_ORIGIN populated for SAP, now it will be populated
8 ERP_WAREHOUSE Warehouse or Inventory Organization for this Product.
9 ERP_QTY_ON_HAND On-Hand quantity for this Product for the given

Warehouse/Inventory Org.
10 SALES_ORG Sales Org
11 ERP_ATTR1 Last Update date
Unit of Measure(Case Pack UOM) in case of SAP-

12 ERP_ATTR2 UNITY, will be NULL for rest of the ERPs
EAN/UPC Type(Case Pack UOM) in case of SAP-UNITY,

13 ERP_ATTR3 will be NULL for rest of the ERPs
EAN(Case Pack UOM) in case of SAP-UNITY, will be

14 ERP_ATTR4 NULL for rest of the ERPs
UPC(Case Pack UOM) in case of SAP-UNITY, will be

Quantity(Case Pack UOM) in case of SAP-UNITY, will be

Gross Weight (Case Pack UOM) in case of SAP-UNITY,

Weight UOM (Case Pack UOM) in case of SAP-UNITY,

Length (Case Pack UOM) in case of SAP-UNITY, will be

Width (Case Pack UOM) in case of SAP-UNITY, will be

Height (Case Pack UOM) in case of SAP-UNITY, will be

Dimensions UOM (Case Pack UOM) in case of SAP-

23 ERP_ATTR13 Volume (Case Pack UOM) in case of SAP-UNITY, will be

NULL for rest of the ERPs
Volume UOM (Case Pack UOM) in case of SAP-UNITY,

Unit of Measure(Pallet UOM) in case of SAP-UNITY, will

25 ERP_ATTR15 be NULL for rest of the ERPs
EAN/UPC Type(Pallet UOM) in case of SAP-UNITY, will

EAN(Pallet UOM) in case of SAP-UNITY, will be NULL for

27 ERP_ATTR17 rest of the ERPs
UPC(Pallet UOM) in case of SAP-UNITY, will be NULL for

Quantity(Pallet UOM) in case of SAP-UNITY, will be

Gross Weight (Pallet UOM) in case of SAP-UNITY, will be

Weight UOM (Pallet UOM) in case of SAP-UNITY, will be

Length (Pallet UOM) in case of SAP-UNITY, will be NULL

32 ERP_ATTR22 for rest of the ERPs
Width (Pallet UOM) in case of SAP-UNITY, will be NULL

Height (Pallet UOM) in case of SAP-UNITY, will be NULL

Dimensions UOM (Pallet UOM) in case of SAP-UNITY,

Volume (Pallet UOM) in case of SAP-UNITY, will be NULL

Volume UOM (Pallet UOM) in case of SAP-UNITY, will be
Unit of Measure(Pack UOM) in case of SAP-UNITY, will

EAN/UPC Type(Pack UOM) in case of SAP-UNITY, will

EAN(Pack UOM) in case of SAP-UNITY, will be NULL for

UPC(Pack UOM) in case of SAP-UNITY, will be NULL for

Quantity(Pack UOM) in case of SAP-UNITY, will be NULL

Gross Weight (Pack UOM) in case of SAP-UNITY, will be

Weight UOM (Pack UOM) in case of SAP-UNITY, will be

Length (Pack UOM) in case of SAP-UNITY, will be NULL

Width (Pack UOM) in case of SAP-UNITY, will be NULL

Height (Pack UOM) in case of SAP-UNITY, will be NULL

Dimensions UOM (Pack UOM) in case of SAP-UNITY, will

Volume (Pack UOM) in case of SAP-UNITY, will be NULL

Volume UOM (Pack UOM) in case of SAP-UNITY, will be

Unit of Measure(MDC Transport Box in case of SAP-
EAN/UPC Type(MDC Transport Box) in case of SAP-

EAN(MDC Transport Box) in case of SAP-UNITY, will be

UPC(MDC Transport Box) in case of SAP-UNITY, will be

Quantity(MDC Transport Box) in case of SAP-UNITY, will

Gross Weight (MDC Transport Box) in case of SAP-

Weight UOM (MDC Transport Box) in case of SAP-

Length (MDC Transport Box) in case of SAP-UNITY, will

Width (MDC Transport Box) in case of SAP-UNITY, will

Height (MDC Transport Box) in case of SAP-UNITY, will

Dimensions UOM (MDC Transport Box) in case of SAP-

Volume (MDC Transport Box) in case of SAP-UNITY, will

Volume UOM (MDC Transport Box) in case of SAP-

Attribute for Future need, keep a placeholder with NULL

64 ERP_ATTR54 value
65 ERP_ATTR55 value

66 ERP_ATTR56 value

67 ERP_ATTR57 value

68 ERP_ATTR58 value

69 ERP_ATTR59 value

70 ERP_ATTR60 value

71 ERP_ATTR61 value

72 ERP_ATTR62 value

73 ERP_ATTR63 value

74 ERP_ATTR64 value

75 ERP_ATTR65 value

76 ERP_ATTR66 value

77 ERP_ATTR67 value

78 ERP_ATTR68 value
79 ERP_ATTR69 value

80 ERP_ATTR70 value
81 ERP_LINE_ATTR1 Last Update Date
Order Unit in case of SAP-UNITY, will be NULL for rest of

82 ERP_LINE_ATTR2 the ERPs
AL Content in case of SAP-UNITY, will be NULL for rest

83 ERP_LINE_ATTR3 of the ERPs
CU Content in case of SAP-UNITY, will be NULL for rest

AG Content in case of SAP-UNITY, will be NULL for rest

X-plant Material Status in case of SAP-UNITY, will be

86 ERP_LINE_ATTR6 NULL for rest of the ERPs
X-plant Material Status Valid From in case of SAP-UNITY,

87 ERP_LINE_ATTR7 will be NULL for rest of the ERPs
Material Type in case of SAP-UNITY, will be NULL for rest

X-distr.chain stat in case of SAP-UNITY, will be NULL for

89 ERP_LINE_ATTR9 rest of the ERPs
Product Attr2 in case of SAP-UNITY, will be NULL for rest


91 ERP_LINE_ATTR11 value







Item status (MVKE-VMSTA) in case of SAP-UNITY and 1.2

sales_org 1231,2031,1233,1620) , will be NULL for rest of
International Harminization Code (MARC-STAWN) from 1.2

the Delivering plant in case of SAP-UNITY and sales_org
101 ERP_LINE_ATTR21 1231,2031,1233,1620) , will be NULL for rest of the ERPs
MRP Group field (MARC-DISGR) in case of SAP-UNITY 1.2

and sales_org 1231,2031,1233,1620) , will be NULL for
Material Price Group (MVKE-KONDM) in case of SAP- 1.2

UNITY and sales_org 1231,2031,1233,1620) , will be
103 ERP_LINE_ATTR23 NULL for rest of the ERPs
Procurement type( MARC-BESKZ) ) in case of SAP-UNITY 1.2

rest of the ERPs
104 ERP_LINE_ATTR24
Planned Delivery Time (MARC-PLIFZ) in case of SAP- 1.2
105 ERP_LINE_ATTR25
MARC-WZEIT (Need to know Actual column name) ) in 1.2

case of SAP-UNITY and sales_org 1231,2031,1233,1620)
, will be NULL for rest of the ERPs
106 ERP_LINE_ATTR26
In-House Production time (MARC-DZEIT) in case of SAP- 1.2

107 ERP_LINE_ATTR27
SAP Minimum Order QTY (MVKE-AUMNG) in case of 1.2

SAP-UNITY and sales_org 1231,2031,1233,1620) , will
be NULL for rest of the ERPs
108 ERP_LINE_ATTR28
SAP Rounding Profile (MVKE-RDPRF) in case of SAP- 1.2

109 ERP_LINE_ATTR29
Numerator( MARM-UMREZ) ) in case of SAP-UNITY and 1.2

the ERPs
110 ERP_LINE_ATTR30
Denominator(MARM-UMREN) in case of SAP-UNITY and 1.2

Item Status Date(MVKE-VMSTD) in case of SAP-UNITY 1.2

Following format should be used to write the Query for each ERP system for extracting the
Product Hierarchy data.
Sequence in Attribute Description
Query
Level 1 Hierarchy Code. (Ex – Prod Family for

1 HIER1_CODE Vista)
2. HIER1_NAME Level 1 Hierarchy Name
3. HIER2_CODE Level 2 Hierarchy Code (Ex – Prod Line for Vista)
4 HIER2_NAME Level 2 Hierarchy Name
5 HIER3_CODE Level 3 Hierarchy Code (Ex – Prod Code for Vista)
7 HIER4_CODE Level 4 Hierarchy Code
9 HIER5_CODE Level 5 Hierarchy Code
ERP Hierarchy Name, this should be same as

Alternate Catalog Name.
11 ERP_HIER_NAME (CATEGORY_SET_NAME)
Vista Query For Product Data
select SP.cat_num ERP_Catalog_Number,

SP.style_num ERP_Manufacturing_id,
decode(SP.std_prst,
NULL,
'ACTIVE',
(select TABLS.table_code || ' - ' || TABLS.table_data
from VISTA_120_ODS.TABLES TABLS
where TABLS.table_name = 'PRODSTAT'
and TABLS.table_code = SP.std_prst)) ERP_It+B2em_Status,
SP.prodc ERP_Product_Code,
SP.noldtime ERP_LeadTime,
SP.country ERP_Country_of_Origin,
INV.Whse_Code ERP_Warehouse,
INV.Qty_On_Hand ERP_QTY_ON_HAND,
'VISTA' ERP_SYSTEM_NAME
from VISTA_120_ODS.STANDARD_PRODUCT SP, VISTA_120_ODS.Inventory INV

where SP.Style_Num = INV.Style_Num(+)
and SP.cat_num = 'BR120' /* THis is sample data you can remove after loading */
and (cat_num is not NULL or SP.STYLE_NUM is not NULL);
Vista Query for Hierarchy Data
select F.PROD_FAM_CODE HIER1_CODE,

F.PROD_FAM_DESC HIER1_NAME,
c.prod_line HIER2_CODE,
l.product_line_desc HIER2_NAME,
C.prod_code HIER3_CODE,
c.prod_code_desc HIER3_NAME,
C.prod_code PRODUCT_CODE,
sysdate LAST_UPDATE_DATE,
sysdate CREATION_DATE,
'E0052281' LAST_UPDATED_BY,
'E0052281' CREATED_BY,
'Vista Product Code' CATEGORY_SET_NAME,
'Item Categories' FLEX_STRUCTURE_CODE
from VISTA_120_ODS.PRODUCT_CODE c,
VISTA_120_ODS.PRODUCT_line L,
VISTA_120_ODS.PRODUCT_family f
where C.Prod_line = L.Product_Line
and L.Product_Family = F.Prod_Fam_Code
and c.prod_code in
(select distinct SP.Prodc
from VISTA_120_ODS.STANDARD_PRODUCT SP
where PRODC is not NULL
and (cat_num is not NULL or SP.STYLE_NUM is not NULL)
and sp.std_prst is NULL);
RTOD view query for Pricing for Bussmann(Added in Version 1.2)
CREATE OR REPLACE FORCE VIEW ZQTC_SYND_PRICE_PDH_V

AS
SELECT VKORG Sales_Organization,
VTWEG Distribution_Channel,
SYNDTYPE Syndication_Type,
MATNR Material_Number,
DATBI Valid_To_Date,
DATAB Valid_From_Date,
DATECHANGED Last_Changed_Date,
KBETR Amount,
KONWA Currency_Code,
KPEIN Pricing_Unit,
KMEIN Unit_of_Measure,
KSTBMMIN Minimum Scale_Quantity,
KSTBMMAX Maximum Scale_Quantity,
NULL AS ERP_ATTR1 ,
NULL AS ERP_ATTR2 ,
NULL AS ERP_ATTR3 ,
NULL AS ERP_ATTR4 ,
NULL AS ERP_ATTR5 ,
NULL AS ERP_ATTR6 ,
NULL AS ERP_ATTR7 ,
NULL AS ERP_ATTR8 ,
NULL AS ERP_ATTR9 ,
NULL AS ERP_ATTR10 ,
FROM ZQTC_SYND_PRICE WHERE (vkorg, vtweg) IN
(SELECT sales_org_id, channel_id
FROM xxpdh_bussman_sales_org_enable)—buss//Electrical EMEA/
3.1.2 Modification in View Query:

i) Query of SAP View SRC_SAP_UNITY_V will be modified to include the columns added
above in section 3.1.1
ii) Query of Views for other ERPS will be modified to include the columns added above in
Section 3.1.1 with NULL value
iii) Tables to be included in SRC_SAP_UNITY_V query:
SLT_ODS.MARM (Material UOM information)
SLT_ODS.MARC (Material Plant Information)
SLT_ODS.MVKE (Material Sales data information)
SLT_ODS.T006A (UOM Master Data)
iv) Filters to be included in SRC_SAP_UNITY_V Query:

a) Data should be fetched for below UOMs only:
SLT_ODS.T006A.MSEHL in ('Case Pack','Pallet','Pack',’ MDC Transport Box’)
b) Data should be fetched for below Lab-Offices only:
SLT_ODS.MARA.labor in ('DMB','BUE','VGC','DSA','DPA','DPC','DSA','PQ1','SIN')
v) Logic to derive Al Content, Cu Content and AG Content:

SELECT *
FROM (SELECT mandt
,matnr
,meinh
,round(umren / greatest(umrez
,1)
,6) AS factor
FROM slt_ods.marm
WHERE meinh IN ('KAL'
,'KCU'
,'GAG')) pivot(SUM(factor) FOR meinh IN('KAL' AS kal
,'KCU' AS kcu
,'GAG' AS gag))
vi) EAN and UPC are stored in same field in SAP. Since we need to store it differently in
PDH, so logic to differentiate will be taken as below:
a. If length is 13 digits, Consider it as EAN
b. If the length is 11/12 digits, consider it as UPC
vii) Modification in SAP View SRC_SAP_UNITY_V for Bussman (#47768)
1. View will be modified to include union all condition

2. Similar query will be added in union all condition with different filter conditions
3. Following columns be will be included in second query which is in union all condition
MVKE.VMSTA erp_line_attr20
,MARC.STAWN erp_line_attr21
,MARC.DISGR erp_line_attr22
,MVKE.KONDM erp_line_attr23
,MARC.BESKZ erp_line_attr24
,MARC.PLIFZ erp_line_attr25
,MARC.WZEIT erp_line_attr26
,MARC.DZEIT erp_line_attr27
,MVKE.AUMNG erp_line_attr28
,MVKE.RDPRF erp_line_attr29
,MARM.UMREZ erp_line_attr30
,MARM.UMREN erp_line_attr31
,MVKE.VMSTD erp_line_attr32
4. Where clause will be filter with table
xxpdh_bussman_sales_org_enable(sales_org,erp_wharehouse) for columns VKORG,
VTWEG wherever used in the join condition
viii) As part of 47782- EMEA WAVE2 project, a new View SRC_ORACLE_V will be created for
Oracle ERP:
a. ERP name will be used as ‘ORACLE-NON-INT’ in the view
b. Schema name in RTODS will be used as EBP_ODS to access Oracle ERP tables
c. Below Tables/Views of EBP_ODS schema will be used in the query for new View, so
PDH user in RTODS will need acces on these tables/view:
i. ebp_ods.mtl_system_items_b
ii. ebp_ods.mtl_item_categories
iii. ebp_ods.mtl_category_sets_tl
iv. ebp_ods.mtl_categories_b
v. ebp_ods.mtl_cross_references
SRC_ORACLE_V.txt
ix) Source Tables/View and corresponding mapping with PDH tables is present in attched
excel below
Mapping Sheet.xlsx
3.1.3 Changes at PDH End:

i) following highlighted columns will be updated/added in PDH tables:
PDH Table name PDH Column Source view in Field name in Source Description of
name RTODS for SAP RTODS Table/Column SAP View
Views(will be for SAP View column
same in all
ERP views)
XXPDH_ERP_PRODUCTS ATTRIBUTE1 SRC_SAP_UNITY_V ERP_ATTR1 MARA.SLT_UP

DATE Last Update date
XXPDH_ERP_PRODUCTS ATTRIBUTE2 SRC_SAP_UNITY_V ERP_ATTR2 MARM.MEINH Unit of
Measure(Case
Pack UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE3 SRC_SAP_UNITY_V ERP_ATTR3 MARM.NUMTP EAN/UPC Type
(Case Pack
UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE4 SRC_SAP_UNITY_V ERP_ATTR4 MARM.EAN11 EAN (Case Pack
UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE5 SRC_SAP_UNITY_V ERP_ATTR5 MARM.EAN11 UPC(Case Pack
UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE6 SRC_SAP_UNITY_V MARM.UMREZ Quantity(Case
ERP_ATTR6 Pack UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE7 SRC_SAP_UNITY_V MARM.BRGE Gross Weight
W (Case Pack
ERP_ATTR7 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE8 SRC_SAP_UNITY_V MARM.GEWEI Weight UOM
(Case Pack
ERP_ATTR8 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE9 SRC_SAP_UNITY_V MARM.LAENG Length (Case
ERP_ATTR9 Pack UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE10 SRC_SAP_UNITY_V MARM.BREIT Width (Case
ERP_ATTR10 Pack UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE11 SRC_SAP_UNITY_V MARM.HOEHE Height (Case
XXPDH_ERP_PRODUCTS ATTRIBUTE12 SRC_SAP_UNITY_V MARM.MEABM Dimensions UOM
(Case Pack
ERP_ATTR12 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE13 SRC_SAP_UNITY_V MARM.VOLUM Volume (Case
XXPDH_ERP_PRODUCTS ATTRIBUTE14 SRC_SAP_UNITY_V MARM.VOLEH Volume UOM
(Case Pack
ERP_ATTR14 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE15 SRC_SAP_UNITY_V MARM.MEINH Unit of
Measure(Pallet
ERP_ATTR15 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE16 SRC_SAP_UNITY_V MARM.NUMTP EAN/UPC Type
ERP_ATTR16 (Pallet UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE17 SRC_SAP_UNITY_V MARM.EAN11 EAN (Pallet
ERP_ATTR17 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE18 SRC_SAP_UNITY_V ERP_ATTR18 MARM.EAN11 UPC(Pallet UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE19 SRC_SAP_UNITY_V MARM.UMREZ Quantity(Pallet
ERP_ATTR19 UOM)
ERP_ATTR20 W (Pallet UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE22 SRC_SAP_UNITY_V MARM.LAENG Length (Pallet
ERP_ATTR22 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE23 SRC_SAP_UNITY_V MARM.BREIT Width (Pallet
ERP_ATTR23 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE24 SRC_SAP_UNITY_V MARM.HOEHE Height (Pallet
ERP_ATTR24 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE26 SRC_SAP_UNITY_V MARM.VOLUM Volume (Pallet
ERP_ATTR26 UOM)
Measure(Pack
ERP_ATTR28 UOM)
ERP_ATTR29 (Pack UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE30 SRC_SAP_UNITY_V ERP_ATTR30 MARM.EAN11 EAN (Pack UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE31 SRC_SAP_UNITY_V ERP_ATTR31 MARM.EAN11 UPC(Pack UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE32 SRC_SAP_UNITY_V MARM.UMREZ Quantity(Pack
ERP_ATTR32 UOM)
ERP_ATTR33 W (Pack UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE35 SRC_SAP_UNITY_V MARM.LAENG Length (Pack
ERP_ATTR35 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE36 SRC_SAP_UNITY_V MARM.BREIT Width (Pack
ERP_ATTR36 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE37 SRC_SAP_UNITY_V MARM.HOEHE Height (Pack
ERP_ATTR37 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE39 SRC_SAP_UNITY_V MARM.VOLUM Volume (Pack
ERP_ATTR39 UOM)
Measure(MDC
Transport Box
ERP_ATTR41 UOM)
(MDC Transport
ERP_ATTR42 Box UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE43 SRC_SAP_UNITY_V MARM.EAN11 EAN (MDC
Transport Box
ERP_ATTR43 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE44 SRC_SAP_UNITY_V MARM.EAN11 UPC(MDC
Transport Box
ERP_ATTR44 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE45 SRC_SAP_UNITY_V MARM.UMREZ Quantity(MDC
Transport Box
ERP_ATTR45 UOM)
W (MDC Transport
ERP_ATTR46 Box UOM)
(MDC Transport
ERP_ATTR47 Box UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE48 SRC_SAP_UNITY_V MARM.LAENG Length (MDC
Transport Box
ERP_ATTR48 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE49 SRC_SAP_UNITY_V MARM.BREIT Width (MDC
Transport Box
ERP_ATTR49 UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE50 SRC_SAP_UNITY_V MARM.HOEHE Height (MDC
Transport Box
ERP_ATTR50 UOM)
(MDC Transport
ERP_ATTR51 Box UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE52 SRC_SAP_UNITY_V MARM.VOLUM Volume (MDC
Transport Box
ERP_ATTR52 UOM)
(MDC Transport
ERP_ATTR53 Box UOM)
XXPDH_ERP_PRODUCTS ATTRIBUTE54 SRC_SAP_UNITY_V ERP_ATTR54 MARA.LABOR Lab Office
XXPDH_ERP_PRODUCTS ATTRIBUTE55 SRC_SAP_UNITY_V ERP_ATTR55 For Future Use
XXPDH_ERP_PRODUCT_ SALES_ORG SRC_SAP_UNITY_V
LINES SALES_ORG MVKE.VKORG Sales org
XXPDH_ERP_PRODUCT_ ATTRIBUTE1 SRC_SAP_UNITY_V ERP_LINE_A MARA.SLT_UP
LINES TTR1 DATE Last Update Date
XXPDH_ERP_PRODUCT_ ATTRIBUTE2 SRC_SAP_UNITY_V ERP_LINE_A MARA.MEINS
LINES TTR2 Order Unit
XXPDH_ERP_PRODUCT_ ATTRIBUTE3 SRC_SAP_UNITY_V MARM.
LINES ERP_LINE_A UMREN/UMRE
TTR3 Z/MEINH AL Content
TTR4 Z/MEINH CU Content
TTR5 Z/MEINH AG Content
XXPDH_ERP_PRODUCT_ ATTRIBUTE6 SRC_SAP_UNITY_V ERP_LINE_A MARC.VMSTA X-plant Material
LINES TTR6 Status
XXPDH_ERP_PRODUCT_ ATTRIBUTE7 SRC_SAP_UNITY_V MVKE.VMSTA X-plant Material
LINES ERP_LINE_A Status Valid
TTR7 From
XXPDH_ERP_PRODUCT_ ATTRIBUTE8 SRC_SAP_UNITY_V ERP_LINE_A MARA.MSTAV
LINES TTR8 Material Type
XXPDH_ERP_PRODUCT_ ATTRIBUTE9 SRC_SAP_UNITY_V ERP_LINE_A MARA.MTART
LINES TTR9 X-distr.chain stat
XXPDH_ERP_PRODUCT_ ATTRIBUTE10 SRC_SAP_UNITY_V ERP_LINE_A MVKE.PRAT2
LINES TTR10 Product Attr2
XXPDH_ERP_PRODUCT_ ATTRIBUTE11 SRC_SAP_UNITY_V ERP_LINE_A For Future Use
LINES TTR11
XXPDH_ERP_PRODUCT_ ATTRIBUTE12 SRC_SAP_UNITY_V ERP_LINE_A
LINES TTR12 For Future Use
XXPDH_ERP_PRODUCT_ ATTRIBUTE13 SRC_SAP_UNITY_V ERP_LINE_A For Future Use
LINES TTR13
#Start Changes- Added below changes Part of Bussmann (#47768) in Version 1.2
XXPDH_ERP_PRODUCT_ ATTRIBUTE20 SRC_SAP_UNITY_V Item Status will
LINES be mapped to
erp_item_status
VMSTA filed in PDH
XXPDH_ERP_PRODUCT_ ATTRIBUTE21 SRC_SAP_UNITY_V International
LINES ERP_LINE_A Harmonization
TTR21 MARC.STAWN Code
XXPDH_ERP_PRODUCT_ ATTRIBUTE22 SRC_SAP_UNITY_V ERP_LINE_A ZQTC_MPGCR Vendor Price
LINES TTR22 .MPG Group
XXPDH_ERP_PRODUCT_ ATTRIBUTE23 SRC_SAP_UNITY_V RTODS will send
LINES KONDM and
Vendor Price
Group to P360.
P360 can then do

transformation for
ERP_LINE_A Seller's Class
TTR23 MVKE.KONDM Code
XXPDH_ERP_PRODUCT_ ATTRIBUTE24 SRC_SAP_UNITY_V ERP_LINE_A Prucurement
LINES TTR24 MARC.BESKZ Type
XXPDH_ERP_PRODUCT_ ATTRIBUTE25 SRC_SAP_UNITY_V ERP_LINE_A Planned Delivery
LINES TTR25 MARC.PLIFZ Time
LINES TTR26 MARC.WZEIT
XXPDH_ERP_PRODUCT_ ATTRIBUTE27 SRC_SAP_UNITY_V ERP_LINE_A In-House
LINES TTR27 MARC.DZEIT Production time
XXPDH_ERP_PRODUCT_ ATTRIBUTE28 SRC_SAP_UNITY_V SAP Mininimum
LINES Order QTY if
ERP_LINE_A blank use Order
TTR28 MVKE.AUMNG Multiple value
XXPDH_ERP_PRODUCT_ ATTRIBUTE29 SRC_SAP_UNITY_V ERP_LINE_A SAP Rounding
LINES TTR29 MVKE.RDPRF Profile
LINES TTR30 MARM.UMREZ Numerator
LINES TTR31 MARM.UMREN Denominator
LINES TTR32 MVKE.VMSTD Item Status Date
XXPDH_RTODS_SYND_P sales_org ZQTC_SYND_PRICE VKORG Sales
RICE VKORG Organization
XXPDH_RTODS_SYND_P erp_warehouse ZQTC_SYND_PRICE VTWEG Distribution
RICE VTWEG Channel
XXPDH_RTODS_SYND_P synd_type ZQTC_SYND_PRICE SYNDTYPE
RICE SYNDTYPE Syndication Type
XXPDH_RTODS_SYND_P erp_manufactur ZQTC_SYND_PRICE MATNR
RICE ing_id MATNR Material Number
XXPDH_RTODS_SYND_P valid_to_date ZQTC_SYND_PRICE DATBI Price Expiration
RICE DATBI Date
XXPDH_RTODS_SYND_P valid_from_dat ZQTC_SYND_PRICE DATAB Price Effective
RICE e DATAB Date
XXPDH_RTODS_SYND_P last_changed_ ZQTC_SYND_PRICE DATECHANG DATECHANGE Last Changed
RICE date ED D Date
XXPDH_RTODS_SYND_P amount ZQTC_SYND_PRICE KBETR
RICE KBETR Price
XXPDH_RTODS_SYND_P currency_code ZQTC_SYND_PRICE KONWA
RICE KONWA Price Currency
XXPDH_RTODS_SYND_P pricing_unit ZQTC_SYND_PRICE KPEIN
RICE KPEIN Pricing Unit
XXPDH_RTODS_SYND_P unit_of_measur ZQTC_SYND_PRICE KMEIN
RICE e KMEIN Price Break UOM
XXPDH_RTODS_SYND_P minimum_scale ZQTC_SYND_PRICE KSTBMMIN KSTBMMIN Price Break
RICE _quantity Beginning
Quantity
XXPDH_RTODS_SYND_P maximum_scal ZQTC_SYND_PRICE KSTBMMAX Price Break Ending
RICE e_quantity Quantity
KSTBMMAX
XXPDH_RTODS_SYND_P ERP_ATTR1 ERP_ATTR1 ZPS_EFF_DAT Price Sheet
RICE ZQTC_PRICESHEET E Effective Date
XXPDH_RTODS_SYND_P ERP_ATTR2 ZPS_EXP_DA Price Sheet
RICE ERP_ATTR2 ZQTC_PRICESHEET TE Expiration Date
ERP_ATTR3 Manufacturer
XXPDH_RTODS_SYND_P MANF_PR_ZO Pricing Zone Code
RICE ERP_ATTR3 ZQTC_PRICESHEET NE
ERP_ATTR4 Previous
Manufacturer
XXPDH_RTODS_SYND_P PREV_PR_ZO Pricing Zone Code
RICE ERP_ATTR4 ZQTC_PRICESHEET NE
XXPDH_RTODS_SYND_P ERP_ATTR5 Distributor Price
RICE ERP_ATTR5 ZQTC_PRICESHEET PR_ZONE Zone
XXPDH_RTODS_SYND_P ERP_ATTR6 ZPS_DESCRIP Price Sheet
RICE ERP_ATTR6 ZQTC_PRICESHEET TION Description
XXPDH_RTODS_SYND_P ERP_ATTR7 Price Sheet
RICE ERP_ATTR7 ZQTC_SYND_PRICE ZPS_NAME Number
Attribute for Future
need, keep a
XXPDH_RTODS_SYND_P placeholder with
RICE ERP_ATTR8 NULL value For Future Use
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
XXPDH_RTODS_SYND_P ERP_ATTR24 Attribute for Future For Future Use
RICE need, keep a
placeholder with
NULL value
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
RICE need, keep a
placeholder with
NULL value
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
placeholder with
RICE NULL value
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
Attribute for Future For Future Use For Future Use
need, keep a
RICE ERP_ATTR60 NULL value
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
XXPDH_RTODS_SYND_P ERP_ATTR78 Attribute for Future For Future Use For Future Use
RICE need, keep a
placeholder with
NULL value
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
XXPDH_RTODS_SYND_P ERP_ATTR92 Attribute for Future For Future Use For Future Use
RICE need, keep a
placeholder with
NULL value
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
need, keep a
#End Changes -Changes Part of Bussmann (#47768) in Version 1.2
ii) Primary key of XXPDH_ERP_PRODUCT_LINES will be changed as below:
Existing To be updated:
ERP_SYSTEM_NM, ERP_MANUFACTURING_ID, ERP_SYSTEM_NM, ERP_MANUFACTURING_ID,

ERP_WAREHOUSE ERP_WAREHOUSE,SALES_ORG
iii) Unique keys of XXPDH_RTODS_SYND_PRICE will be created as below
New Table Updated in Version 1.2
sales_org, erp_warehouse, synd_type,

erp_manufacturing_id, valid_to_date
3.1.4 Concurrent program to update UDAs in PDH:
A new concurrent program ‘Eaton Update SAP UDAs’ will be created in PDH to update the SAP
Dimension details UDAs
1) This will fetch the SAP Dimension attributes data from XXETN.XXPDH_ERP_PRODUCTS
table for SAP-UNITY system.
2) The data will then be inserted in the standard UDA interface table
EGO_ITM_USR_ATTR_INTRFC.
3) Since the length, width and height UOM is same in SAP, so there is a single field for the
same in XXPDH_ERP_PRODUCTS table also. The program will take this value and use it
for all the 3 UDAs in PDH.
4) Data of 4 UOMs 'Case Pack','Pallet','Pack', ’MDC Transport Box’ is fetched in same row in
XXETN.XXPDH_ERP_PRODUCTS table as 4 different columns, they will be used and
stored as 4 different records of Multi Row attributes groups in PDH
5) The standard program 'EGO Spreadsheet Java Concurrent Program' will be then
submitted which will load the UDAs in PDH
6) After loading the UDAs in PDH, items will be inserted in
XXPDH_PUBLISH_TRX_LINES_ALL so that the UDA data gets passed to Consumer layer
3.1.5 PDH to P360 view Changes (Added in version 1.2)
A. PDH_SAP_UNITY_P360_V View Change
1. Above view will be modified in PDH to include non-pricing attributes for sending to P360
from RTODS for SAP data
2. Following highlighted columns will added in the exists file(PDH_SAP_UNITY_P360_V) view
as below
SELECT pid.item_number item_number

,xep.erp_system_nm system_name
,xepl.sales_org level_1
,xepl.erp_warehouse level_2
,xep.erp_manufacturing_id manufacturing_id
,xep.attribute55 base_uom
,xep.attribute56 material_type
,xep.attribute54 lab_office
,xep.attribute57 numerator_kal
,xep.attribute58 numerator_kcu
,xep.attribute59 numerator_gag
,xepl.attribute13 xplant_status
,xepl.attribute8 xdist_status
,xepl.attribute9 delivery_unit
,xepl.attribute10 mat_pricing_grp
,xepl.attribute12 commodity_code
,xepl.erp_country_of_origin country_of_origin
,xepl.attribute14 mrp_grp
,xepl.attribute15 product_attrib2
,xepl.attribute11 min_ord_qty
,xepl.attribute2 volume_rebate_group
,xepl.attribute6 lead_time
,xepl.attribute7 region_of_origin
,xepl.attribute16 base_price
,xepl.attribute17 currency
,xepl.attribute18 price_per
,xepl.attribute19 price_uom
,xepl.attribute4 default_plant
,xepl.attribute21 Inter_Harmonization_Code
,xepl.attribute22 Vendor_Price_Group
,xepl.attribute23 KONDM
,xepl.attribute24 Procurement_Type
,xepl.attribute25 Planned_Delivery_Time
,xepl.attribute26 WZEIT
,xepl.attribute27 In_House_Production_time
,xepl.attribute28 SAP_Mininimum_Order_QTY
,xepl.attribute29 SAP_Rounding_Profile
,xepl.attribute30 Numerator
,xepl.attribute31 Denominator
,xepl.attribute32 Item_Status_Date
FROM xxetn.xxpdh_erp_products xep
,xxetn.xxpdh_erp_product_lines xepl
,xxetncsrlr.pdh_prdct_rfrnc prod_ref
,xxetncsrlr.pdh_pid pid
WHERE xep.erp_manufacturing_id = xepl.erp_manufacturing_id
AND xep.erp_manufacturing_id = prod_ref.manufacturing_id
AND prod_ref.system_name = xep.erp_system_nm
AND pid.inventory_item_id = prod_ref.inventory_item_id
--AND TRIM(xepl.sales_org) IS NOT NULL
AND xep.erp_system_nm = 'SAP-UNITY'
AND xepl.erp_system_nm = 'SAP-UNITY'
B. Create new view PDH_SAP_UNITY_P360_PRICING_V
1. New view will be created for sending pricing data to P360

2. View will pull the data from base table XXETN.XXPDH_RTODS_SYND_PRICE
3. This view will have following columns part of definition
4. File name will be PDH_SAP_UNITY_P360_PRICING_V
View Name Column Name

PDH_SAP_UNITY_P360_PRICING_V Sales Organization
Distribution Channel
Syndication Type
Material Number
Price Expiration Date
Price Effective Date
Last Changed Date
Price
Price Currency
Pricing Unit
Price Break UOM
Price Break Beginning Quantity
Price Break Ending Quantity
Price Sheet Effective Date

Price Sheet Expiration Date
Manufacturer Pricing Zone Code
Previous Manufacturer Pricing Zone Code
Distributor Price Zone

Price Sheet Description
Price Sheet Number
4. for mapping details please refer section 3.1.3
C. Below new lookup code entry will have to be done in lookup ‘XXPDH_P360_INTERFACE’
LOOKUP_TYPE LOOKUP_C MEANING DESCRIPTI ATTRIBUTE1 ATTRIBUTE3

ODE ON
XXPDH_P360_IN 4070 4070 VIEW_REP PDH_ORACL Y

TERFACE L E_P360_V
D. Create new view PDH_ORACLE_P360_V :

a. This view will be used to send Oracle operational data to P360
b. This view will fetch data using below tables:
i. Xxetn.xxpdh_erp_products
ii. Xxetn.xxpdh_erp_product_lines
iii. xxetncsrlr.pdh_pid
iv. xxetncsrlr.pdh_prdct_rfrnc
c. View will have below fields:
View Name Column Name

PDH_ORACLE_P360_V ITEM_NUMBER
SYSTEM_NAME
LEVEL_1
MANUFACTURING_ID
DELIVERY_PLANT
COMMODITY_CODE
COUNTRY_OF_ORIGIN
MRP_GROUP
MATERIAL_PRICING_GROUP
PRO_LEAD_TIME
MATERIAL_TYPE
X_PLANT_MATERIAL_STATUS
DELIVERY_UNIT
MINIMUM_ORDER_QUANTITY
ORDER_CENTER_FLAG
d. Below is the View query:
pdh_oracle_p360_v.
txt
4.Open/Closed Issues
4.1 Open Issues
ID Issue Resolution Responsibility Target Date Impact Date

1 Below columns are pending
with Business for
confirmation whether they Cecile/Tom
are required or not:
Price Quantity
Min Quantity
Quantity Interval
Price amount
Price type
Currency
Tax Rate
Price factor
Lower Quantity Limit
Territory
Discount Group of the
manufcaturer
Manner of surcharge
Surcharge price amount
Step Size
Leadtime
2 List of Sales Org to be used Greath

3 1.SLT_ODS.T006A.MSEHL Brain
in ('Case
Pack','Pallet','Pack',’ MDC
Transport Box’) --UOM
 This condition
refers to the Packing
units that we need to
include for
Bussmann.?
4 SLT_ODS.MARA.labour in Brain
('DMB','BUE','VGC','DSA','
DPA','DPC','DSA','PQ1','SI
N')
 This condition
refers Lab Office that
need to include. If
there is not particular
restriction on lab
offices, we will skip
this condition
5 List Price and Currency Tom Brown

are excluded for now.
Tom to discuss with
Gerhard and confirm
4.2 Closed Issues
ID Issue Resolution Responsibility Target Date Impact Date

5.Traceability Matrix
BRD Requirement BRD Requirement BRD Document MD50 Section MD50->MD70
ID Name Name
47782-PDH 1.2
Additional Sales EMEA WAVE2
P360.47782.005 BRD 1.3
Orgs option
3.1
47782-PDH 1.2
Ingest Oracle ECP EMEA WAVE2
P360.44782.16 operational data BRD 1.3
into P360
2.1
47782-PDH 1.2
Distribution EMEA WAVE2
P360.44782.17 BRD 1.3
Channel
2.1
6.Appendix
1. 47782- EMEA WAVE2 distribution channel and sales org addition
Sequence Country SalesORG Distr.Channel
New FR 4308 30
New PL 4927 30
New NO 4912 30
New CZ 4923 30
New HU 4929 30
New UK 4947 30
New RO 4930 30
New SK 4931 30
FW Sales orgs and

distribution channels.msg

Md070-Pdh Rtods Interface 47782

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Md070-Pdh Rtods Interface 47782

Uploaded by

Copyright:

Available Formats

x

Author: Idris Ali

Document Revision History

28 Aug 2015 1.0 Initial Version Idris Ali 42449

22 Oct 2018 1.2 Updated for 47768 Mahaboob 47768

21-Mar-2019 1.2 Updated for EMEA Inderjeet 47782

09-May-2019 1.3 Updated for 47782 Rakesh 47782

10-May-2019 1.3 Inderjeet Kaur 1. Reviewed for 47782- EMEA

1.2 Business Requirements <Mandatory>

The system shall enable the

The system shall enable the

The solution shall provide the ability

The solution shall ensure that PDH

Technical team shall set up a feed of

Few UDAs and operational attributes

47781 UDAs added in the feed to be

47768 IDW - Bussmann, PQ,

The solution should provide the

1.3 Technical Requirements <Mandatory>

New attributes will be added in

47768 Bussmnn-PQ ETL Feed from RTODS to PDH to

New RTODS Control Table for PDH feeds

JOB Source Insta Dom From Fetch To Fetch

1 VISTA01 VTA VTA_ODS s_load_PDH_VISTA 24-Aug-15 25-Aug-15 RUNNING

Get Most Recent Assign TO_date to

2. ERP Mapping For Product Data

ERP Query for

Source View :- ZQTC_SYND_PRICE_PDH_V(RTODS)

Target Table:- XXETN.XXPDH_RTODS_SYND_PRICE(PDH)

3. ERP Mapping for Hierarchy Data

ERP Query for

2.1 Database Design

2.1.1 Database Objects (Custom Tables/View/Sequence/Indexes etc.)

PDH Table : Interface table for

PDH Table : Interface able for

PDH Table : Table to hold ERP

PDH Table : Table to hold Org

RTODS Table : Control table

RTODS Table: Table with

PDH Table : will be used to 1.2

RTODS Table to capture the list 1.2

3.1 Program Logic and Pseudo Code

3.1.1. File Formats:

Sequence Attribute Description Updated in

Catalog No of the Product, this should match the catalog

Part No / Style No from ERP which uniquely identifies a

Status of Part in ERP system (Active, Retired etc.).

NOTE: This should be Master Product Status and not

Hierarchy Name from the ERP, this should match the

4 ERP_HIER_NAME (Example : <ERPNAME> Prod Code

Hierarchy Node in the ERP Hierarchy this Product (part) is

6 ERP_LEAD_TIME Lead time for the Product.

Country of Origin for this Product.This field was not

8 ERP_WAREHOUSE Warehouse or Inventory Organization for this Product.

9 ERP_QTY_ON_HAND On-Hand quantity for this Product for the given

10 SALES_ORG Sales Org

11 ERP_ATTR1 Last Update date

Unit of Measure(Case Pack UOM) in case of SAP-

EAN/UPC Type(Case Pack UOM) in case of SAP-UNITY,

EAN(Case Pack UOM) in case of SAP-UNITY, will be

UPC(Case Pack UOM) in case of SAP-UNITY, will be

Quantity(Case Pack UOM) in case of SAP-UNITY, will be

Gross Weight (Case Pack UOM) in case of SAP-UNITY,