Professional Documents
Culture Documents
DRP Testing: LEARNING Summary
DRP Testing: LEARNING Summary
DRP Testing: LEARNING Summary
LEARNING Summary
In DRP testing, I got to learn about HP-ALM tool i.e how test cases can be captured and how
defect are being inserted in the tool and assigned to individual for corrective action.
I was told to run the task of 2 Layer and 1 layer model in DRP TEST where I learned about some
procedures behind the task and also the table responsible for the same. Below are the test
cases, which I run and have put the short summary with that so that it can be shared with team
and can be used as a knowledge base for our team.
2 LAYER
1. Cutoff – Billing
Ran Task successfully and data updated in table DRP_DWH_INVOICES and correctly showing in EV
Procedure: pck_drp_cutoff.sql
Delete the data from DRP_LOGICAL_INVENTORIES and after task run, table populated again.
Procedure: pck_drp_cutoff.sql
5. Cutoff – FABOUT
In Fabout , a quantity available on particular FG and is being showing in EV after task run.
Procedure: pck_drp_cutoff.sql
6. Cutoff – GIT
Delete the data from DRP_SHP_HEADERS and DRP_SHP_ITEMS table and then ran the task and after
that same number of rows got inserted.
Procedure: pck_drp_cutoff.sql
8. Demand Adaptation
Load the delfor and then an entry got created in signal list with ‘Derived Forecast’
Also after task run, an entry created in DE_EVENT table with 'I' and picked by adapter and changed to
‘S’.
Table: DRP_SITE
1 LAYER
1. 1 Layer BAS
Model: 1 Layer Frame Shared
When the Proposed RD Backlog is generated then the entry created in DRP_DM_MAST and
DRP_DM_DET tables and exact weekly quantity is being showing in EV.
2. 1 Layer BSH
Model: 1 Layer Frame Unshared
When the Proposed RD Backlog is generated then the entry created in DRP_DM_MAST and
DRP_DM_DET tables and exact weekly quantity is being showing in EV.
3. 1 Layer CSH
Model: 1 Layer Consi VMI
When the Proposed RD Backlog is generated then the entry created in DRP_DM_MAST and
DRP_DM_DET tables and exact weekly quantity is being showing in EV.
select * from stock_reserve_condn where sga__code = '66A0000004' and sgp__item_nr = '00270' order
by last_updating_date;
desc DRP_DWH_INVOICES;
SELECT sum(ss.committed_qty)
FROM so so, so_item si,so_sub_item ssi,so_scheduled ss
where si.so__code=ssi.so__code
and ssi.so__code=ss.so__code
and ss.so__code = so.code
and si.Id = ssi.so_item__id
and ss.so_sub_item__Id = ssi.ID
and ss.LAST_COMMITTED_DATE='02-MAR-2018 00:00:00'
and not (ss.so_status__COde='70' and ss.fully_invd_flag='Y') and ss.so_status__Code not in ('40','41')
and ss.finished_good__code = 'L4979DTR-S-JLFM/';
Cancelled 5k core :
update so_Scheduled set so_status__Code='40' ,plant_so_status__Code='40' where
id='4F47N02939.176.1.1434';
select
layer_type__code,id,PROCESSING_STATUS,CUSTOMER_SHIP_TO__CODE,COMMERCIAL_PRODUCT__CO
DE,ASSOCIATION__CODE,
CUSTOMER_PART_NR,SO__CODE,NETTING_MODE,FRAME_LEVEL,SW_USER__ID,INSERTION_DATE,LAST
_UPDATING_DATE,PROCESSING_START_DATe,SALES_ORDER_TYPE__CODE,SO_SUB_TYPE__CODE from
demand_header
where customer_Ship_to__code='4010073101'
and commercial_product__Code='L4979DTR-E'
order by insertion_date;
desc RMS_PRODUCT_RETURN_REQUEST ;
UR64-TR
Previously if Process Mode is Keep Pending then it will not propose shipment
If Process Mode is Normal , then normal shipment will be triggered for 20k.
Change:
If Process Mode is 'Keep Pending' then it will propose 8k and 5k and 7k as Normal.
Product: L4979DTR-E
Shipto :4010085202
Assoc: BOWW
eul0701.sgp.st.com