gdw.td.rma balances

Technical Design Version: 1.0

EMC

TECHNICAL DESIGN

RMA BALANCES(Extract Stage to Revenue Stage)

Created By: Naveen Kumar DasuCreation Date: 9/13/11Last Updated By: Last Updated: Version: 1.2

1 Last modified by: ERG Reporting


Table of Contents

DOCUMENT CHANGE CONTROL.......................................................................................................................................3

APPROVAL.................................................................................................................................................................................3

GENERAL REQUIREMENTS.................................................................................................................................................4

1. INTRODUCTION...............................................................................................................................................................5

2. DOCUMENT SCOPE.........................................................................................................................................................5

3. DESCRIPTION...................................................................................................................................................................5

4. ASSUMPTIONS..................................................................................................................................................................5

5. EXTRACT DESIGN...........................................................................................................................................................6

6. TABLES & CONDITIONS................................................................................................................................................8

A. SOURCE TABLES................................................................................................................................................................8B. TABLE JOIN CONDITIONS...................................................................................................................................................8C. SOURCE FILTER CONDITIONS............................................................................................................................................8D. LOOKUP CONDITIONS........................................................................................................................................................9E. SOURCE TO TARGET COLUMN MAPPINGS.........................................................................................................................9F. W_ RMA_BALANCES _FS MAPPING FIELDS...............................................................................................................10G. ACQCO_FLG: ACQCO_FLG WILL BE POPULATED BASED ON THE FOLLOWING.........................................................13

7. SAMPLE DATA................................................................................................................................................................15

A) RMA BALANCES......................................................................................................................................................15Source Table:......................................................................................................................................................................15Target Table........................................................................................................................................................................16

8. PARAMETERS AND VARIABLES...............................................................................................................................18

A. SESSION NUMBERS & NAMES..........................................................................................................................................18

9. ETL MAPS.........................................................................................................................................................................18

A. MAPS TO COMPLETE........................................................................................................................................................18B. MAP(S) COMPLETED........................................................................................................................................................18

10. WORKFLOW/ SESSION SETTINGS........................................................................................................................18

11. CONTROL M JOBS.....................................................................................................................................................19

12. REFRESH FREQUENCY............................................................................................................................................19

13. SUSPENSE/ERROR HANDLING..............................................................................................................................19

14. TESTING.......................................................................................................................................................................19

15. ISSUES AND ADDITIONAL CONSIDERATIONS.................................................................................................20

16. DEPENDENCIES..........................................................................................................................................................20

17. Reviewers.......................................................................................................................................................................20

2 Last modified by: EMC PROPEL


Document Change Control

Date Author Version Change Reference

09/13/2011 Naveen Kumar Dasu 1.0 Initial draft

Approval

Name Phone # Dates

Created By: Naveen Kumar Dasu+91-9916193026

Creation Date: 13th Sep 2011

Updated ByApproved By:



General Requirements

Name: (Required)RMA Balances

Technical Design Document ID & Title: (Required) GDW.TD.RBI.0003-1 TD: RMA Balances

Application: (Required)GDW

ID: (Required) GDW.TD.RBI.0003-1 TD

Priority: (Required)

Other Affected Applications: (Required)

Functional Design Reference: (Required) BI.FD.0011.GDW:RMA Balances

Comments: (Required)

Related Work Unit(s) Work Unit Type Relation Type



1. IntroductionThis document will address the design of the ETL processes to extract data from the EXTRACT staging environment, transform it and load to the LOAD staging environment for the RMA Balances Fact will be part of the new Global Data Warehouse (GDW).

2. Document ScopeThis document will cover the technical design details related to creating maps and configuring workflows and sessions for given subject area. This document also includes

the structure of the target table(s) the data source(s) for the target table(s) join logic between source tables the ETL maps that will extract the data from the EXTRACT staging environment to the LOAD staging

environment for final load to the REVENUE HUB in the GDW.This document does not include details of the actual code used to extract data from each source table to load the target. Details on each map built will be added to this document by the assigned developer as and when each map is completed or updated.

3. DescriptionThe system of record for RMA Balances is SAP ECC this will hold the ordered but not delivered data.The RMA Balances Fact table will hold a snapshot of data which is ordered but not delivered. . This table will be refreshed 3 times a day and the final snapshot data available for some time each day. The system of record for RMA issues is SAP ECC. The data will pass into the SAP Business Warehouse (BW), be processed for GDW in BW, and provided via an Open Hub table /BIC/OHZRBAL_D01 is used to load the RMA Balances and Rollup RMA Balances data into the Extract Schema table W_BW_ZRBAL_D01.

4. AssumptionsThe accuracy of the results supplied by this design relies on several key assumptions and key facts listed below:

The BW data will be made available to GDW, likely by means of Open Hub as a table in the BW database readable by Informatica.

In GDW Open Hub we need to include the RMA_Balances fields, RollupRMA fields, Summary Rollup fields into one table.

GDW loading from Open Hub to Extract Schema will we a Pass through One to One mapping. GDW Stage Loading from Extract to Load will be incremental. Lookup on Dimensions is needed from Extract to Load Stage on the Dimension Tables. All foreign keys (the dimension IDs) should be indexed in Load Staging Area. GDW Loading from Load to Revenue will be a Pass through One to One mapping along with the Control

Columns. These should be determined by the developer as part of the individual unit testing and tuning of each map. Records can be stacked, i.e. you can run multiple times from EXTRACT to LOAD Schema

environments before loading to the final dimension table.

5. Extract Design



The extract design for RMA Balances is a straightforward extract, transform, load process. The standard order RMA Balances data will be sourced from an SAP BW Open Hub table SAPSR3. / BIC/OHZRBAL_D01 ETL Steps for Backlog Fact is as follows.

i. Create below new Tables in Extract Schema. W_BW_ZRBAL_D01

ii. Create a new Pass through one to one mapping to load the data from SAP BW Open Hub to the Extract Stage table / BIC/OHZRBAL_D01 which identifies the Incremental record changes to process for the daily load.

iii. Create New Map/Maps between the EXTRACT Stage table and the LOAD Stage table to load the data into the Stage table LOAD.W_RMA_BALANCES_FS.

iv. Lookup on the Dimensional Tables to get the data from all Dimensional tables.

v. The loading from Extract to Load will be a Truncate Load.

vi. Create new map to load the data from Load stage to Revenue stage to load the data into REVENUE.W_RMA_BALANCES_F.

vii. We need to pull the RMA_BALANCES, RMA_EVAL_BALANCES History data from BRMSMDM table in to the new REVENUE schema table REVENUE.W_BILLINGS _F

viii. Purge older daily snapshots from the EXTRACT_REV table and the REVENUE fact. Drops all date stamps in the previous two calendar months (but not the current) excepting the first day of any month, all Mondays, and any day in the last two weeks of a quarter (after the 16th).

ix. For Reporting purpose we need to pull the RMA_BALANCES data from BRMSMDM table in to the new REVENUE schema table REVENUE.W_RMA_BALANCES_F.

x. Below is the code to identify the data and delete the records from Revenue table REVENUE.W_RMA_BALANCES_F (Only SAP Data)

cursor del_daily_back is select distinct SNPSHT_DT_STMP from REVENUE.W_RMA_BALANCES_F b where SNPSHT_DT_STMP between (add_months(last_day(trunc(sysdate)), -3) + 2) and (add_months(last_day(trunc(sysdate)), -1) + 0) and to_char(sysdate,'DD') <> '01' and rtrim(ltrim(to_char(SNPSHT_DT_STMP, 'DAY'))) <> 'MONDAY' and and to_char(SNPSHT_DT_STMP,'MMYYYY') = to_char(RPTG_DT,'MMYYYY') and ( to_char(SNPSHT_DT_STMP, 'MM') not in ('03','06','09','12') or to_number(to_char(SNPSHT_DT_STMP, 'DD')) < 16 );



Then it deletes the records:

for d in del_daily_back loop DELETE from REVENUE.W_RMA_BALANCES_F where SNPSHT_DT_STMP = d.SNPSHT_DT_STMPand to_char(SNPSHT_DT_STMP,'MMYYYY') = to_char(RPTG_DT,'MMYYYY') cnt := sql%rowcount; cnt_tot := cnt_tot + cnt;

dbms_output.put_line('Rows deleted for SNPSHT_DT_STMP: ' || d.SNPSHT_DT_STMP || ' = ' || cnt); commit; end loop;

Below is the code to identify the data and delete the records from EXTRACT_REV table SAPSR3. W_BW_ZRBAL_D01cursor del_daily_back is select distinct SNPSHT_DT_STMP

from SAPSR3. W_BW_ZRBAL_D01 b where SNPSHT_DT_STMP between (add_months(last_day(trunc(sysdate)), -3) + 2) and (add_months(last_day(trunc(sysdate)), -1) + 0) and to_char(sysdate,'DD') <> '01' and rtrim(ltrim(to_char(SNPSHT_DT_STMP, 'DAY'))) <> 'MONDAY' and to_char(SNPSHT_DT_STMP,'MMYYYY') = to_char(RPTG_DT,'MMYYYY') and ( to_char(SNPSHT_DT_STMP, 'MM') not in ('03','06','09','12') or to_number(to_char(SNPSHT_DT_STMP, 'DD')) < 16 );

Then it deletes the records:

for d in del_daily_back loop DELETE from SAPSR3. W_BW_ZRBAL_D01

where SNPSHT_DT_STMP = d.SNPSHT_DT_STMP and to_char(SNPSHT_DT_STMP,'MMYYYY') = to_char(RPTG_DT,'MMYYYY') cnt := sql%rowcount; cnt_tot := cnt_tot + cnt;

dbms_output.put_line('Rows deleted for SNPSHT_DT_STMP: ' || d.SNPSHT_DT_STMP || ' = ' || cnt); commit; end loop;

xi. Suspense Table: REVENUE.W_REVENUE_SUSPENSE_S



6. Tables & Conditions

a. Source Tables

The following source system tables are required:

Source Table Name SchemaW_BW_ZRBAL_D01 Extract

Temporary and Target Tables

The following temporary and target tables are required for Backlog Fact:

Target Target Schema Target Table Target Table TypeGDW LOAD W_RMA_BALANCES_FS Fact Staging

b. Table Join Conditions

The following join conditions apply for maps pulling from more than 1 source table:

Map Name Condition Name Target Table Source Tables Join Condition

c. Source Filter Conditions

The following filter conditions apply for the following maps:

Map Name Condition Name

Target Table Source Tables Filter Condition

only newly created or

updated rows are pulled in

LOAD.W_RMA_BALANCES_FS W_BW_ZRBAL_D01

w_update_dt > ( select max(source_last_update_date) from w_dw_load_control_ds where session_number = ??? )and w_current_flg = 'c'

d. Lookup Conditions

The following extract tables should be used as lookup sources if one of the primary tables has changed:



The following lookup conditions are required:

Map Name Lookup Name Lookup Target Table Lookup ConditionMASTERDATA.W_TIME_D See Mapping sheet

MASTERDATA.W_PROFIT_CENTER_D See Mapping sheet

MASTERDATA.W_GL_COMPANY_D See Mapping sheet

MASTERDATA.W_ORGANIZATION_D See Mapping sheet

MASTERDATA.W_GL_ACCOUNT_D See Mapping sheet

MASTERDATA.W_PRODUCT_D See Mapping sheet

MASTERDATA.W_CUSTOMER_D See Mapping sheet

MASTERDATA.W_CUST_SITE_LOCTN_D See Mapping sheet

MASTERDATA.W_SALES_ORDER_TYPE_D See Mapping sheet

REVENUE.W_REVENUE_SUSPENSE_S See Mapping sheet

e. Source to Target Column Mappings

The column mappings from Source (EXTRACT_REV Stage) to Target (LOAD Stage) are attached. This does not include any intermediary table mappings or control columns.Open Hub ( RMA_Balances from Extract to Load) to GDW Mapping Sheet:

f. W_ RMA_BALANCES _FS mapping fields



This mapping is used for historical data conversion from BRMSMDM.RMA_BALANCES and RMA_EVAL_BALANCES

Source Table Column Target Table Target ColumnRMA_BALANCES, RMA_EVAL_BALANCES W_RMA_BALANCES_F ROW_WID

RMA_EVAL_BALANCES CREATION_DATE W_RMA_BALANCES_F TRNS_DTRMA_BALANCES, RMA_EVAL_BALANCES W_RMA_BALANCES_F TRNS_DT_WID

RMA_EVAL_BALANCES RMA_ORDER_NUMBER W_RMA_BALANCES_F RMA_ORD_HDR_NUMRMA_BALANCES, RMA_EVAL_BALANCES W_RMA_BALANCES_F RMA_ORD_HDR_WID

RMA_EVAL_BALANCES ORDER_NUMBER W_RMA_BALANCES_F ORD_NUM

RMA_EVAL_BALANCES W_RMA_BALANCES_F ORD_WIDRMA_BALANCES, RMA_EVAL_BALANCES

MODEL_INVENTORY_ITEM_ID / MODEL_DIM_ID W_RMA_BALANCES_F MDL_ITEM_NUM

RMA_BALANCES, RMA_EVAL_BALANCES W_RMA_BALANCES_F MDL_PROD_CUR_WID

RMA_BALANCES, RMA_EVAL_BALANCES W_RMA_BALANCES_F MDL_PROD_WID

RMA_BALANCES, RMA_EVAL_BALANCES

PART_INVENTORY_ITEM_ID / PART_DIM_ID W_RMA_BALANCES_F PART_ITEM_NUM

RMA_BALANCES, RMA_EVAL_BALANCES W_RMA_BALANCES_F PART_PROD_CUR_WIDRMA_BALANCES, RMA_EVAL_BALANCES W_RMA_BALANCES_F PART_PROD_WID

PART_QTY W_RMA_BALANCES_F RMA_QTYRMA_BALANCES, RMA_EVAL_BALANCES BRM_QTY W_RMA_BALANCES_F BRM_QTYRMA_EVAL_BALANCES ORDER_CHANNEL W_RMA_BALANCES_F ORD_CHNLRMA_BALANCES, RMA_EVAL_BALANCES ORDER_TYPE_ID W_RMA_BALANCES_F ORD_TYPE_WIDRMA_EVAL_BALANCES COST_CENTER W_RMA_BALANCES_F GL_COST_CTR_WIDRMA_EVAL_BALANCES DISTRICT W_RMA_BALANCES_F SLS_DSTRCT_IDRMA_EVAL_BALANCES ORGANIZATION_ID W_RMA_BALANCES_F ORG_WIDRMA_BALANCES, RMA_EVAL_BALANCES EXPECTED_RETURN_DATE W_RMA_BALANCES_F EXPEC_RTN_DTRMA_EVAL_BALANCES W_RMA_BALANCES_F EXPEC_RTN_DT_WIDRMA_BALANCES, RMA_EVAL_BALANCES DATE_STAMP W_RMA_BALANCES_F RMA_ACTV_DT

RMA_EVAL_BALANCES W_RMA_BALANCES_F RMA_ACTV_DT_WIDRMA_BALANCES, RMA_EVAL_BALANCES RMA_HEADER_ID W_RMA_BALANCES_F RMA_ORD_HDR_WIDRMA_BALANCES, RMA_EVAL_BALANCES

PSI_INVENTORY_ITEM_ID/PSI_DIM_ID W_RMA_BALANCES_F PSI_ITEM_NUM

RMA_BALANCES, RMA_EVAL_BALANCES W_RMA_BALANCES_F PSI_PROD_CUR_WID

RMA_EVAL_BALANCES W_RMA_BALANCES_F PSI_PRODUCT_WIDRMA_BALANCES, RMA_EVAL_BALANCES LINE_ID W_RMA_BALANCES_F SLS_ORD_LN_ID


mailto:TIER_@_PRTNR_LOC_WID


RMA_BALANCES, RMA_EVAL_BALANCES ORG_ID W_RMA_BALANCES_F COMPANY_CDRMA_BALANCES, RMA_EVAL_BALANCES RMA_LINE_NUMBER W_RMA_BALANCES_F RMA_LN_NUMRMA_BALANCES, RMA_EVAL_BALANCES ACTIVATE_DATE W_RMA_BALANCES_F ACTVT_DTRMA_BALANCES, RMA_EVAL_BALANCES W_RMA_BALANCES_F ACTVT_DT_WID

SHIP_TO_LOCATION_DIM_ID W_RMA_BALANCES_F SHIP_TO_LOC_WIDRMA_EVAL_BALANCES BILL_TO_LOCATION_DIM_ID W_RMA_BALANCES_F BILL_TO_LOC_WIDRMA_BALANCES, RMA_EVAL_BALANCES DEAL_NUMBER W_RMA_BALANCES_F DEAL_NUMRMA_BALANCES, RMA_EVAL_BALANCES RMA_LINE_COMMENTS W_RMA_BALANCES_F RMA_LN_CMNT

RMA_EVAL_BALANCES CATEGORY_CODE W_RMA_BALANCES_F CAT_CDRMA_BALANCES, RMA_EVAL_BALANCES TRY_BUY_FLAG W_RMA_BALANCES_F TRY_BUY_FLGRMA_BALANCES, RMA_EVAL_BALANCES PSI_LINE_ID W_RMA_BALANCES_F LIC_MDL_PROD_WIDRMA_BALANCES, RMA_EVAL_BALANCES PSI_LINE_NUMBER W_RMA_BALANCES_F PSI_LN_NUM

REPORTING_DATE W_RMA_BALANCES_F RPTG_DT

REPORTING_DATE_TIME_DIM_ID W_RMA_BALANCES_F RPTG_DT_WID


SOLD_TO_LOCATION_DIM_ID W_RMA_BALANCES_F SOLD_TO_LOC_WID


INSTALL_AT_LOCATION_DIM_ID W_RMA_BALANCES_F INSTL_AT_LOC_WID

RMA_EVAL_BALANCESENDUSER_LOCATION_DIM_ID W_RMA_BALANCES_F ENDUSR_LOC_WID

APPROVAL_DATE W_RMA_BALANCES_F APRVL_DTRMA_BALANCES, RMA_EVAL_BALANCES W_RMA_BALANCES_F APRVL_DT_WIDRMA_BALANCES, RMA_EVAL_BALANCES

OPERATING_UNIT_ORGNZTN_DIM_ID W_RMA_BALANCES_F OPER_UNIT_ORG_WID

RMA_BALANCES, RMA_EVAL_BALANCES EVAL_MARGIN_FIELDCOST W_RMA_BALANCES_F EVAL_MRGN_FLD_COSTRMA_BALANCES, RMA_EVAL_BALANCES EVAL_BLP_DOLLARS W_RMA_BALANCES_F EVAL_BLP_USDRMA_BALANCES, RMA_EVAL_BALANCES EVAL_LIST_DOLLARS W_RMA_BALANCES_F EVAL_LIST_USDRMA_BALANCES, RMA_EVAL_BALANCES

BUNDLE_INVENTORY_ITEM_ID W_RMA_BALANCES_F BNDLE_ITEM_NUM

RMA_EVAL_BALANCES W_RMA_BALANCES_F BNDLE_PROD_WID

UNBUNDLED_INVENTORY_ITEM_ID W_RMA_BALANCES_F UNBNDLE_ITEM_NUM

RMA_EVAL_BALANCES W_RMA_BALANCES_F UNBNDLE_INV_ITEM_WIDRMA_BALANCES, RMA_EVAL_BALANCES REVENUE_FLAG W_RMA_BALANCES_F REV_FLGRMA_EVAL_BALANCES TRX_UPD_REASON W_RMA_BALANCES_F TRNS_UPDT_RSN ORIGINAL DISTRICT W_RMA_BALANCES_F ORIG_DSTRCT



GEO_FLAG W_RMA_BALANCES_F GEO_FLG TIER_2_PARTNER W_RMA_BALANCES_F TIER_2_PRTNER_CUST_LOC_WID ACQUIRED_COMPANY_FLAG W_RMA_BALANCES_F ACQCO_FLG

REPORTING_YEAR_QUARTER ABBREVIATION W_RMA_BALANCES_F RPTG_YR_QTR_ABBRV

DELETED FLAG W_RMA_BALANCES_F DEL_FLGRECEIPT_LINE_ID

W_RMA_BALANCES_FRMA_DURATION

W_RMA_BALANCES_F COST W_RMA_BALANCES_F COST DOLLARS W_RMA_BALANCES_F DOLLARS W_RMA_BALANCES_F PLANT_WID TIER_2_PARTNER W_RMA_BALANCES_F TIER_2_PRTNER_LOC_WID

ACQUIRED_COMPANY_FLAG W_RMA_BALANCES_F

ENDUSR_CUST_WID

REPORTING_YEAR_QUARTER ABBREVIATION W_RMA_BALANCES_F

INSTL_AT_CUST_WID

DELETED_FLAG W_RMA_BALANCES_F OPP_HRD_ROW_WID RECEIPT_LINE_ID W_RMA_BALANCES_F QUOTE_HDR_WID RMA_DURATION W_RMA_BALANCES_F SLSREP_RSRC_ID

COST W_RMA_BALANCES_F SOLD_TO_CUST_WID

DOLLARS W_RMA_BALANCES_F SOLUTN_ID

See ETL Standard Document W_SESSION_NUMBER

See ETL Standard Document W_LAST_UPDATED_BY

See ETL Standard Document W_INSERT_DT

See ETL Standard Document W_UPDATE_DT

See ETL Standard Document W_SOURCE

See ETL Standard Document W_ROW_HASH

g. ACQCO_FLG: ACQCO_FLG will be populated based on the following.

ACQCO_FLG - Reusable Stored Procedure ACQCO_FLG_CALC – This should connect to MASTEDATA schema .For this Stored Procedure we need to pass 2 values BILL_TO_LOC_WID, TRANSACTION_DATE.

The Logic Below is for reference.

SELECT B.CUST_SITE_NUM, UPPER (SUBSTR (C.ENTITY_NAME, 0, 3)) AS WHICH_CUSTFROM EXTRACT.W_BW_ZRBAL_D01 A



MASTERDATA.W_CUST_SITE_LOCTN_D BMASTERDATA.W_CUSTOMER_D CWHERE A./BIC/OHZRBAL_D01 =B.CUST_SITE_NUMANDN B.CUST_ID=C.CUST_IDAND ( UPPER (C.ENTITY_NAME) LIKE 'NETWORK INTELLIGENCE%' OR UPPER (C.ENTITY_NAME) LIKE 'RSA%' OR UPPER (C.ENTITY_NAME) LIKE 'VMWARE%' OR UPPER (C.ENTITY_NAME) LIKE 'VM WARE%' OR UPPER (C.ENTITY_NAME) LIKE 'TABLUS%' OR UPPER (C.ENTITY_NAME) LIKE 'X-HIVE%' OR UPPER (C.ENTITY_NAME) LIKE 'DATA DOMAIN%' OR UPPER (C.ENTITY_NAME) LIKE 'DATADOMAIN%' OR UPPER (C.ENTITY_NAME) LIKE 'CONFIGURESOFT%' OR UPPER (C.ENTITY_NAME) LIKE 'KAZEON%' OR UPPER (C.ENTITY_NAME) LIKE 'FASTSCALE%' OR UPPER (C.ENTITY_NAME) LIKE 'DECHO%' OR UPPER (C.ENTITY_NAME) LIKE 'GREENPLUM%' OR UPPER (C.ENTITY_NAME) LIKE 'BUSTECH%' OR UPPER (C.ENTITY_NAME) LIKE 'ISILON%' OR UPPER (C.ENTITY_NAME) LIKE 'NETWITNESS%' )

AND C.ENTITY= '097447148'

From the above query you get the CUST_SITE_NUM and WHICK_CUST Below is the logic to get the acquired company flag. WHICH_CUST will be taken from the above query.

IIF(ISNULL(W_BW_ZRBAL_D01./BIC/OHZRBAL_ DO1),'N', IIF (IN (W_BW_ZRBAL_D01./ BIC/OHZRBAL_ DO1, 'DDUP-MISC-HW', 'DDUP-MISC-HWM', 'DDUP-MISC-PS', 'DDUP-MISC-SW', 'DDUP-MISC-SWM', 'DDUP-MISC-TRA'),'N',IIF((WHICH_CUST='NET' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('7/1/2006','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='RSA' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('7/1/2006','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='VMW' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('1/1/2004','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='VM ' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('1/1/2004','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='TAB' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('7/1/2007','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='X-H' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('7/1/2007','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='DAT' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('7/17/2009','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='CON' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('6/1/2009','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='KAZ' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('9/15/2009','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='FAS' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('8/31/2009','MM/DD/YYYY')),'Y',



IIF((WHICH_CUST='DEC' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('11/17/2008','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='GRE' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('7/29/2010','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='BUS' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('11/08/2010','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='ISI' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('12/22/2010','MM/DD/YYYY')),'Y',IIF((WHICH_CUST='NET' AND ADD_TO_DATE(SNPSHT_DT_STMP,'DD',-1) >= TO_DATE('4/4/2011','MM/DD/YYYY')),'Y','N')))))))))))))))))

REV_FLG - Reusable Mapplet mplt_revenue_flag_calc

7. Sample Data

The following are sample records of how the Fact records should look when populated.

a) RMA BALANCES

Source Table:

RMA Balances Extract Schema table name: W_BW_ZRBAL_D01

Source Column Sample DataCREATEDON REFER_DOC DOC_NUMBER /BIC/ZMATLV2 ORDER_QTY DISTR_CHAN DOC_TYPE COSTCENTER /BIC/ZGLISTDO /BIC/ZGSTCOST CONTR1END /BIC/ZMATLV1 STS_ITM CREATEDON SOLD_TO SHIP_TO BILLTOPRTY /BIC/ZGREDAT /BIC/ZGRETIM /BIC/ZGBPA11I /BIC/ZGSOT11I



/BIC/ZGSHP11I /BIC/ZGINP11I /BIC/ZGCOSTDT /BIC/ZGCOEDDT /BIC/ZGBUNMO /BIC/ZGUNBUN

Target Table

W_RMA_BALANCES_FS

Target Column Sample DataROW_WID TRNS_DT TRNS_DT_WID RMA_ORD_HDR_NUM RMA_ORD_HDR_WID ORD_NUM ORD_WID MDL_ITEM_NUM MDL_PROD_CUR_WID MDL_PROD_WID PART_ITEM_NUM PART_PROD_CUR_WID PART_PROD_WID RMA_QTY BRM_QTY ORD_CHNL ORD_TYPE_WID GL_COST_CTR_WID SLS_DSTRCT_ID ORG_WID EXPEC_RTN_DT EXPEC_RTN_DT_WID RMA_ACTV_DT RMA_ACTV_DT_WID RMA_ORD_HDR_WID PSI_ITEM_NUM PSI_PROD_CUR_WID PSI_PROD_WID



SLS_ORD_LN_ID COMPANY_CD RMA_LN_NUM ACTVT_DT ACTVT_DT_WID SHIP_TO_LOC_WID BILL_TO_LOC_WID DEAL_NUM RMA_LN_CMNT CAT_CD TRY_BUY_FLG PSI_LN_ID PSI_LN_NUM RPTG_DT RPTG_DT_WID SOLD_TO_LOC_WID INSTL_AT_LOC_WID ENDUSR_LOC_WID APRVL_DT APRVL_DT_WID OPER_UNIT_ORG_WID EVAL_MRGN_FLD_COST EVAL_BLP_USD EVAL_LIST_USD BNDLE_ITEM_NUM BNDLE_PROD_WID UNBNDLE_ITEM_NUM UNBNDLE_PROD_WID REV_FLG TRNS_UPDT_RSN ORIG_DSTRCT GEO_FLG TIER_2_PRTNER_CUST_LOC_WID ACQCO_FLG RPTG_YR_QTR_ABBRV DEL_FLG COST DOLLARS PLANT_WID TIER_2_PRTNER_LOC_WID ENDUSR_CUST_WID INSTL_AT_CUST_WID OPP_HRD_ROW_WID



QUOTE_HDR_WID SLSREP_RSRC_ID SOLD_TO_CUST_WID SOLUTN_ID W_SESSION_NUMBER W_LAST_UPDATED_BY W_INSERT_DT W_UPDATE_DT W_SOURCE W_ROW_HASH

8. Parameters and Variables

The following are the parameters and variables required for this process <to be completed>:

Parameters / Variable Name Type Data Type Initial Value DescriptionNA NA NA NA NA

a. Session Numbers & Names

Session Numbers/Names are used to keep track of what maps were run, what tables were updated and also to keep a record count on the tables updated.

Session Numbers & Names are assigned by the ETL team and can be found in e-room at the following link:

9. ETL Maps

a. Maps to complete

The following is a list of maps required for this subject area:

Map Name Source Tables Target Tables Map Type Map Purpose

Component Type Description

b. Map(s) Completed



Map Name Source Tables Target Tables Map Type Map Purpose

Component Type Description

10. Workflow/ Session Settings

11. Control M Jobs

<to be completed>

Control M Job Workflow Name

12. Refresh Frequency Three times a Day. (Tentatively 1 AM, 9 AM, and 3 PM ET)

13. Suspense/Error Handling

Please refer to the ETL Development Guidelines for EXTRACT_REV to LOAD Schema for further details on Suspense/Error Handling Processes on W_REVENUE_SUSPENSE_S Table.

14. Testing

Unit test Docs are available on the below E-ROOM link:



Test No Test Scenario Details Test Result Date Completed

15. Issues and Additional Considerations

The following Issues were defined during Technical Design:

Issue Raised By / Date Needed

Resolution/Answer Resolved By / Date Completed

We need to give names for the Open Hub fields and Lookup Condition in Extract_to_Load Sheet which are left blank.

Naveen Dasu

The required link is to be given in Section 10 (a) to access the ERoom for Session Numbers and Names.

Naveen Dasu

16. Dependencies

17. Reviewers

Name Date Team


gdw.td.rma balances

Documents