You are on page 1of 36

User Acceptance Test D

Document Information
Document Title User Acceptance Test Document
Document Purpose User Acceptance Test execution as per the plan and sign-off
Test Scenarios Test Condition
TS ID TS Description Function T Code/ Test Condition
Type System ID
R01_TS001 General Report Custom Power BI
Functionality (All Pages) Report

1.1

1.2
1.3

R01_TS002 Report Specific Functionality Custom Power BI


(Summary page) Report

2.1

2.2

2.3

R01_TS002 Report Specific Functionality Custom Power BI


(DMS Page) Report

2.1

2.2

R01_TS002 Report Specific Functionality Custom Power BI


(Data Download Page) Report

2.1
R01_TS002 Report Specific Functionality Custom Power BI
(Data Download Page) Report

2.1
Acceptance Test Document
Document Information
nt
n as per the plan and sign-off
Test Conditions and Expected Results
Test Condition Description Test Condition Step Test Step Description

User with appropriate Go to https://app.powerbi.com/


authorization open the report Single sign-on should work.
and able to do slice and dice of 1.1.1
the report
Navigate to Workspaces ->
1.1.2
DMS - Operations
Go to Reports -> click on
Container Scan Completeness
PPM report and navigate to
1.1.3 different pages of the report

Check all filters are provided


1.2.1
as per the spec or not
Apply any filter and check if
report is displaying as per the
filter or not

Check all filters


1.2.2
Download report Result into Click on … dots on the top of
Excel the each visual and click on
1.3.1 Export Data to Excel option

Check if visual has all the


2.1.1 requested information in the
same order as per spec
Check if there is any visual
2.1.2
level filter as per spec
Scan PPM Overall KPI
Check whether you can see
2.1.3
data for all fields or not

Validate data of Power BI


2.1.4
report with Source data

Check if visual has all the


2.2.1 requested information in the
same order as per spec
Check if there is any visual
2.2.2
level filter as per spec
PPM by Region, by Subsi
Check whether you can see
2.2.3
data for all fields or not

Validate data of Power BI


2.2.4
report with Source data

Check if visual has all the


2.3.1 requested information in the
same order as per spec
Check if there is any visual
2.3.2
level filter as per spec
Failure Transactions
Check whether you can see
2.3.3
data for all fields or not

Validate data of Power BI


2.3.4
report with Source data

Check if visual has all the


2.1.1 requested information in the
same order as per spec
Check if there is any visual
2.1.2
level filter as per spec
q2ew
Check whether you can see
2.1.3
data for all fields or not

Validate data of Power BI


2.1.4
report with Source data

Check if visual has all the


2.2.1 requested information in the
same order as per spec
Check if there is any visual
2.2.2
level filter as per spec
Depot View
Check whether you can see
2.2.3
data for all fields or not

Validate data of Power BI


2.2.4
report with Source data

Check if visual has all the


2.1.1 requested information in the
same order as per spec
Check if there is any visual
2.1.2
level filter as per spec
Check whether you can see
2.1.3
data for all fields or not

Validate data of Power BI


2.1.4
report with Source data
Expected Result Passed/Failed

Login successful.

Passed
Navigation successful.
Passed
Report should be displayed as in
the similar format of "Mockup" tab
of the requirement spec

Passed
All filters should display as per the
requirement document Passed
Filtered Value should appear in
report

Failed
Report result should be
downloaded to Excel

Failed
All the requested information
should appear as per spec
Failed
Filter should show if it is requested
in the spec N/A
Data should appear for all the
fields Failed
Data Should match with source
after applying all the filters and
logic as per the spec Failed
All the requested information
should appear as per spec
Failed
Filter should show if it is requested
in the spec N/A
Data should appear for all the
fields Failed
Data Should match with source
after applying all the filters and
logic as per the spec Failed
All the requested information
should appear as per spec
NA - Remove
Filter should show if it is requested
in the spec NA - Remove
Data should appear for all the
fields NA - Remove
Data Should match with source
after applying all the filters and
logic as per the spec NA - Remove
All the requested information
should appear as per spec
Failed
Filter should show if it is requested
in the spec N/A
Data should appear for all the
fields Failed
Data Should match with source
after applying all the filters and
logic as per the spec Failed
All the requested information
should appear as per spec
Failed
Filter should show if it is requested
in the spec N/A
Data should appear for all the
fields Failed
Data Should match with source
after applying all the filters and
logic as per the spec Failed
All the requested information
should appear as per spec
Passed
Filter should show if it is requested
in the spec N/A
Data should appear for all the
fields Passed
Data Should match with source
after applying all the filters and
logic as per the spec

Failed
Actual Result

-Refer to tab PS1, selected "Period Type" - Actual and click on data table Jan-
2020, underlying data is show everything, and there is no actual date data
field to verify if the filter works correctly. Also, period type should be default
to select one value only per requirement
-refer to tab PS2, selected period per screenshot, but all pie chart now is blank
and the table is not per the filter value
-refer to tab PS3, selected period month per screenshot, but all pie chart now
is blank and the table is not per the filter value
-refer to tab PS4, field "Depot" is showing non depot value, like packer starts
with 4, 5, this field is for Depot only
-for Field "HHT", showing only value Y. this cannot be as recently we do have
scan data upload through manual process in China due to COVID19, and also
in 2018/2019 for Russia due to data protection
- For "PPM (Y/N)", underlying data table does not have the Qty information to
verify
- For "Reason Category", underlying data table does not have the Reason
category, Reason Code to verify
- refer to tab PS6 "Tagging Depot (Y/N)", when select "N", the underlying data
showing depot tha is maintain as"Y", why?
- refer to tab PS7 "Scanning Dept (Y/N)", when selected value "N", the
undelrying data is showing data on depot that is maintain as "Y" scanning,
why?
Able to download underlying table data, but many of the fields are not per req

Pie Chart is to show percentage per mock up refer to tab PS5, also label name

Label name of pie chart is mis leading, it should be "Last FY Full Year PPM", "

PPM result don’t look right, underlying data table don’t have all the specified da

Table when drill down on the year, the month is not in right sequence

Refer to tab PS8, the depot country is wrong as GPEU should not have depot co

PPM result don’t look right as all years PPM is the same by row obviously wrong, underlying data table don’t have all the s

Table when drill down on the year, the month is not in right sequence

Table when drill down on the year, the month is not in right sequence Pie Chart is to show percentage per mock up refer t

PPM result don’t look right as all years PPM is the same by row obviously wrong,
Table when drill down on the year, the month is not in right sequence .
Also, this is to show depot value at the row, not the subsi region, so thi sis
wrong

Table when drill down on the year, the month is not in right sequence Pie Char

PPM result don’t look right as all years PPM is the same by row obviously wrong,

All data fields available


All data fields available

- Filter Period is last 6 months 1-Oct-19 to 31-Mar-20 & period type actual, for
Outbound data, the actual date is not match to PGI date, refer to tab "PS13"
- the data include ITR with no depot in From and To location, this is wrong as
there will be no depot scan for these location
- for other data field validation, please refer to tab PS12
-Refer to tab PS1, selected "Period Type" - Actual and click on data table Jan-2020, underlying data is show
everything, and there is no actual date data field to verify if the filter works correctly. Also, period type should be
default to select one value only per requirement
-refer to tab PS2, selected period per screenshot, but all pie chart now is blank and the table is not per the filter value
Fixed. But changed the date hirereachy to year,qtr,month,date as week can not be used as date data type. For last 6
months, ly pie is showing.
-refer to tab PS3, selected period month per screenshot, but all pie chart now is blank and the table is not per the
filter value Fixed
-refer to tab PS4, field "Depot" is showing non depot value, like packer starts with 4, 5, this field is for Depot only
Fixed. Should we filter only for depot from source?
-for Field "HHT", showing only value Y. this cannot be as recently we do have scan data upload through manual
process in China due to COVID19, and also in 2018/2019 for Russia due to data protection Fixed
- For "PPM (Y/N)", underlying data table does not have the Qty information to verify Need More explanation
- For "Reason Category", underlying data table does not have the Reason category, Reason Code to verify Need More
explanation
- refer to tab PS6 "Tagging Depot (Y/N)", when select "N", the underlying data showing depot tha is maintain as"Y",
why? Its showing as N , dataset
- refer to tab PS7 "Scanning Dept (Y/N)", when selected value "N", the undelrying data is showing data on depot that
is maintain as "Y" scanning, why?Its showing as N
Need clear explanation

Fixed

We are showing scanned vs unscanned , so when

Need clear explanation

Fixed. But changed the date hirereachy to year,qtr,month,date as week can not be used as date data type.

It is as per spec mapping logic.It is happening for ITR_type repositioning

ously wrong, underlying data table don’t have all the specified data fields, unable to verify. Refer to tab9.

fixed. Different hirerachy order

ce Pie Chart is to show percentage per mock up refer to tab PS10

Fixed

Subsi Region is top in the hirerachy order

Fixed

Fixed
- Filter Period is last 6 months 1-Oct-19 to 31-Mar-20 & period type actual, for Outbound data, the actual date is not
match to PGI date, refer to tab "PS13" Fixed
- the data include ITR with no depot in From and To location, this is wrong as there will be no depot scan for these
location Need more explanation
- for other data field validation, please refer to tab PS12
-Refer to tab PS1, selected "Period Type" - Actual and click on data table Jan-2020,
underlying data is show everything, and there is no actual date data field to verify if the filter
works correctly. Also, period type should be default to select one value only per requirement
Umesh: product limitation. We can not apply filters to data points while exporting.
-refer to tab PS2, selected period per screenshot, but all pie chart now is blank and the table
is not per the filter value Fixed. But changed the date hirereachy to year,qtr,month,date as
week can not be used as date data type. For last 6 months, ly pie is showing.
-refer to tab PS3, selected period month per screenshot, but all pie chart now is blank and
the table is not per the filter value Fixed
-refer to tab PS4, field "Depot" is showing non depot value, like packer starts with 4, 5, this
field is for Depot only Fixed. Should we filter only for depot from source?
-for Field "HHT", showing only value Y. this cannot be as recently we do have scan data
upload through manual process in China due to COVID19, and also in 2018/2019 for Russia
due to data protection Fixed
- For "PPM (Y/N)", underlying data table does not have the Qty information to verify Need
More explanation
- For "Reason Category", underlying data table does not have the Reason category, Reason
Code to verify Need More explanation
- refer to tab PS6 "Tagging Depot (Y/N)", when select "N", the underlying data showing
depot tha is maintain as"Y", why? Its showing as N , dataset
- refer to tab PS7 "Scanning Dept (Y/N)", when selected value "N", the undelrying data is
PS1, Periodshowing data on depot that is maintain as "Y" scanning, why?Its showing as N
Recommennd to download data download page
S/N
Report Name Container Scan Completeness PPM
To measure the number of containers not scanned by ITR/Booking level u
Parts Per Million (PPM) level.

Note:
Data will come from both ITR and Booking.
It will filtered on if to or from location is depot. I.e. it only relates to wareh

For Depot to Depot Transfers, the transaction will have to appear twice in
Outbound

Server: bi-production
Database: INSIGHTSAPDB
Table: ITR_Scanned_Data
Field TRANSTYPE should be used to identify whether the data is related t

Report Description
1. Transactional
2. BI BI
New / Existing New
Internal / External Internal
External Customer Name
1 - Less Critical NA
5 - Very Critical 3
Impact of not having
Real time No
Report Run Frequency Daily
Auto/Manual Auto
Report Owner Yii Kii
Function / Process Depot
Table Name ITR_Scan_Data

Data Fields - Dimension (for underlying data)


# Field Name Description sample data Calculation
1 Datasource Type To indicate if source of data comes from SAP or ITR, booking N
2 Region Depot Region According to the Subsi Code Match
CIST & Middle East, EuropN
3 Subsi Depot Subsi GPME, GPUS N
4 From Location From Location 830044 N
5 To Location To Location 830044 N
6 From Code From Location Name JiCHENGJIAXIN-JXCN N

7 To Code To Location Name JiCHENGJIAXIN-JXCN N


8 From Country From Country Name China N
9 To Country To Country Name China N
10 Job Type Job Type ITR Manual PO N
11 SKU SKU MB3, MB4, MB5 N
12 HHT Hand-Held Device Indicator Y/N N
13 Tagging Depot Tagging Depot Flag Y/N N
14 ITR/Booking ETA ETA for job and ITR 1/1/2019 Y
15 ITR/Booking ETD ETD for Job and ITR 1/1/2019 Y
16 ITR PGI/Job Dispatch ITR PGI and Job Dispatch Dates 1/1/2019 Y
17 ITR CR/Job GR ITR PGI and Job Dispatch Dates 1/1/2019 Y
18 Transaction No ITR No and Booking No 5002419583 Y
19 Booking/ITR type Booking and ITR Type Collection Y
20 Inbound/Outbound Indicate Inbound or Outbound Inbound, Outbound Y
21 Actual Date Actual Date of Scan 1/1/2019 Y
22 Estimated Date Estimated Date of Scan 1/1/2019 Y
23 Depot ID Depot ID 830044 Y
24 Depot Name Depot Name JiCHENGJIAXIN-JXCN Y
25 Depot Country Depot Country China Y
26 Depot Concatenation of Depot ID and Depot Name 830044 - JiCHENGJIAXINY
27 Dimension Allow switching of header fields Region, Subsi, SKU, Cou Y
NEW Reason Description The detail reason description of why the Booki Depot Missed Scan
NEW Reason Code Grouping of Reason Description Missed Scan
NEW ReasonCategory Indicate if the Reason code is Goodpack Contro Goodpack Controllable
NEW Scanning Depot (Y/N) Indicator if the depot has scanning capability Y
eteness PPM
er of containers not scanned by ITR/Booking level upon Outbound/Inbound. The measure are presented at
) level.

oth ITR and Booking.


r from location is depot. I.e. it only relates to warehouse inbound and outbound.

ansfers, the transaction will have to appear twice in the data. One line for Inbound and One line for

DB
ata
d be used to identify whether the data is related to Inbound (IB) or Oubound (OB).

Do we need to restrict source only for Depot (83%)? da

Data Field - Measure (for underlying data)


Field Name Venkat Comments Calculation formula # Field Name
Source AP means Booking & Goodpack means I 1 Scanned Qty
Depot_Region 2 T2 Qty
Depot_Subsi 3 IBC Qty
ITR_From 4 Scan PPM
Depot 5 Booking Qty
From_Code 6 US/OS Qty

To_Code 7 Scan Rate


From_Country_Name 8 Unscanned Qty
To_Country_Name
"ITR"
Checkwhen Yii Kii agreed to remove
table Source is GoodPac
SAPBIData.T_GEMS_SCAN_
ITR_SKU
DEPOT. If the depot is on It should indicate whether the
this table then "Y" else "N" data was scanned or
Depot_Tagging uploaded.
ITR_ETA
ITR_ETD
ITR_PGI_DATE
ITR_CRDATE
ITRNO
ITR_TYPE
If from location = IF From Location is a depot THEN
TRANSTYPE scan_location "OutBound" ELSEIF To Location is
where
then you will get Job FR? IF Inbound/Outbound
a depot THEN "Inbound" = END
Scan_Date Wences will discuss this with
"outbound" "Inbound" THEN ITR CR/Job GR
IF "Inbound/Outbound field"
venkat/narayana/business
else IF Inbound/Outbound
ELSEIF
Umesh: Inbound/Outbound
How can we get= if =From
ITR_ETD calculated
and get on row 20
back.
if to_location = is "Inbound"
"Outbound"
Location andTHEN
THEN ITR/Booking
is a ETA
Job Dispatch
To Location
"Outbound"
scan_location IF
ENDInbound/Outbound
ELSEIF
depot Inbound/Outbound
Umesh:
or = =
not?ITR CR means
Depot then then "Outbound"
ITR_CRDATE?, THEN
fromFrom
ITR/Booking
whereLocation
ETD
we
ITR_ETD"inbound" ELSEIF
will getInbound/Outbound
END Job GR and what is =the
else else "Inbound" THEN
logic to select To Location
between END
this two?
IF "Inbound/Outbound
"unknown" Umesh: from which fields we can
field" end
calculated on row 20 is get From location and To
"Inbound"
end Location, It should be code or
ITR_ETA description
end
IF Inbound/Outbound =
Depot_Name "Outbound" THEN From Location
IF Inbound/Outbound =
Code
Depot_Country_Name "Outbound" THEN From Country
ELSEIF Inbound/Outbound =
Concat(Depot
ELSEIF ID,To
" -Location
", Depot
Inbound/Outbound
"Inbound" THEN =
Depot + Depot_Name Name)
"Inbound" THEN ToWhich
Code END Umesh: Country END
filed
Wences will discuss this with IFcanDimension
be refered(Parameter) =
for From Location
- business on Wednesday and Region THEN Region Code Removed as we are shwoing as per subsi hirerachy
code and To Location
BI-Production
get back. (192.168.3.94 ) ELSEIF Dimension = Subsi THEN
Subsi
IF Inbound ELSEIF Dimension = SKU THEN
join SKU
IF Inbound
T_TBL_REASON_IBSCAN1D ELSEIF Dimension = Country
join SKU and
using THEN Country
Check table
T_TBL_REASON_IBSCAN1D
ITR_NO/bookinNumber ELSEIF Dimension = Depot THEN
T_GEMS_SCAN_DEPOT.
using SKU and
IF Outbound Depot
If Depot code is on this table, ELSEIF Dimension = ITR No THEN
ITR_NO/bookinNumber
join
than
IF Y else N.
Outbound
T_TBL_REASON_OBSCAN1D ITR No
join
using SKU and
T_TBL_REASON_OBSCAN1D
ITR_NO/bookingNumber
using SKU and
ITR_NO/bookingNumber
**Attention: Need to remove
duplications on tables
**Attention: Need to remove
T_TBL_REASON_IBSCAN1D
duplications
and on tables
T_TBL_REASON_IBSCAN1D
T_TBL_REASON_OBSCAN1D
and
T_TBL_REASON_OBSCAN1D
source only for Depot (83%)? data since yii kii wants to see only depot data in depot filters according to uat comments

asure (for underlying data)


Description sample data Calculation (YField
SAP Name
Scan Qty 86 N T2ScanQty = 0
Scan_Qty
Insight Need access to sharepoint
T2 Qty (No 1D or 2D barc 4N T2 SCAN QTY on file Report_RPT0000139.csv
location to import the file.
IBC Qty 100 N ITR_CRQTY
Scan Parts Per Million 100000 Y check calculation formula
ITR Qty and Booking Qty 110 Y Booking Qty need more explanation
Under Scan or Over Scan -10 Y check calculation formula

Scan Rate 90% Y check calculation formula


Unscanned Quantity 10 Y check calculation formula
woing as per subsi hirerachy
Filter/Parameter
Calculation formula Calculation f #
1
2
Yii Kii agreed to remove 3
1-scan rate * 1000000 Can scan ppm be negative figure? 4
Booking Qty (only consider container and exclude acessories) 5
When ITR_STATUS is COMPLETED: Scanned Qty + T2 qty – Booking Qty Removed as pe 6

if (reason code = Goodpack Uncontrollable or Exempted, then 100%, else (Scanned Qty + T2 Qty) / (Booking
qty + OS/US Qty). Do the result need to multiply with 100 to get the percentage of it? Or if the result is 1 then
we need to consider scan rate as 1 in the scan ppm formula? 7
Booking Qty + US/OS Qty - Scanned Qty - T2 Qty, Can unscanned qty be negative figure? 8
9
10
11
12
13
14
15
16
NEW
NEW
Filter/Parameter can be
Field Name Description Filter Type Mandatory Removed as
Period Type Parameter for swit Single Y we
Is itare
applicable for data download tab
shwoing as
Transaction Type Parameter to switcSingle Y subsi
hirerarchy
Dimension Parameter for SelecSingle N now
Period Parameter for swit Single Y
Target Parameter to set taSingle Y
Period Month Date Filter Multi/Single Y YYYY MMM

SKU SKU Filter Multi/Single Y


Subsi Region Subsi Region Filter Multi/Single Y
Subsi Subsi Filter Multi/Single Y
Depot Depot Filter Multi/Single Y
Depot Country Depot Country FilteMulti/Single Y
Tagging Depot Tagging Depot FilteMulti/Single Y
Direction Direction Filter Multi/Single Y
Data Source Type Data Source Type FiMulti/Single Y
SKU SKU Filter Multi/Single Y
HHT HHT Filter Multi/Single Y
Scanning Depot (Y/Drop down of valueSingle
PPM (Y/N) Indicator for PPM, Single
Reason Category
Hirerachy
Subsi Region REMOVE: Remove Failture Transaction, add in the newly added filt
Subsi
Depot Country
Depot (id+name)
Directions

Goodpack financial year = july YYYY -june YYYY

1st Pie chaLast FY July 18 - June 19


2nd Pie chaLast FY YTD July 18 - Till Date
3rd Pie chaCFY YTD July 19 - Till Date

Dimension Field
For Switching
between different
basis

When the above


visual is selected,
bottom visual should
filter to selection.
d in the newly added filter, add the dimension to the bar chart table. Umesh- Instead of adding dimension to top right visual, create h

PPM
< Target = Green
> Target = Fail

Note:
Data for this view should be filtered to o
Estimated date =< Today

Period parameters will apply on Actual

Transaction No

HHT
Data to be refreshed
at 11am daily
to top right visual, create hirerachies as mentioned here

Green
= Fail

view should be filtered to only within


te =< Today

meters will apply on Actual Date

Data to be refreshed
at 11am daily
NEW CHANGE: enable hierachy on the date to be able to drill up from

PPM
< Target = Green
> Target = Fail
if Estimated Date >
Today() then Grey

When the above


visual is selected,
bottom visual should
filter to selection

Dimension Field
For Switching
between different
basis
te to be able to drill up from Date to Week and Month, add in new filters. Umesh - Date hirerachy on the visuals

Note:
Unlike summary Tab, the data will not ha
estimated date. but rather, colours will a

HHT

Data to be refreshed
at 11am daily
calendar week.strat Monday

mmary Tab, the data will not have any filters on


date. but rather, colours will apply differently.

Data to be refreshed
at 11am daily
NEW CHANGE: add in new filters
CrossTab for users to download underlying data
All measures and dimensions to be included.
HHT
Region Subsi
CIS & Middle East GPME
CIS & Middle East GPRU
Europe & Africa GPEU
Europe & Africa GPSA
Latam GPBR
North & Central America GPUS
North East Asia GPCN
North East Asia GPJP
North East Asia GPKR
North East Asia GPTW
Singapore & Thailand GPID
Singapore & Thailand GPPH
Singapore & Thailand GPSG
Singapore & Thailand GPTH
Singapore & Thailand GPVN
South East Asia & Australasia GPAU
South East Asia & Australasia GPIN
South East Asia & Australasia GPMY
South East Asia & Australasia GPNZ
ITR_SCAN_DATA SP TBL_OBSCANQTY_1D SP TBL_IBSCANQTY_1D
DEPOT DEPOT DEPOT
DEPOT_CITY DEPOT_CITY DEPOT_CITY
DEPOT_CODE DEPOT_CODE DEPOT_CODE
DEPOT_COUNTRY DEPOT_COUNTRY DEPOT_COUNTRY
DEPOT_COUNTRY_NAME DEPOT_COUNTRY_NAME DEPOT_COUNTRY_NAME
DEPOT_LATITUDE DEPOT_LATITUDE DEPOT_LATITUDE
DEPOT_LONGITUE DEPOT_LONGITUE DEPOT_LONGITUE
DEPOT_NAME DEPOT_NAME DEPOT_NAME
DEPOT_REGION DEPOT_REGION DEPOT_REGION
DEPOT_REGION_NAME DEPOT_REGION_NAME DEPOT_REGION_NAME
DEPOT_SALESORG DEPOT_SALESORG DEPOT_SALESORG
DEPOT_SCAN_CAPABILITY DEPOT_SCAN_CAPABILITY DEPOT_SCAN_CAPABILITY
DEPOT_STATE DEPOT_STATE DEPOT_STATE
DEPOT_STATENAME DEPOT_STATENAME DEPOT_STATENAME
DEPOT_SUBSI DEPOT_SUBSI DEPOT_SUBSI
DEPOT_TAGGING DEPOT_TAGGING DEPOT_TAGGING
FROM_CITY FROM_CITY
FROM_CODE FROM_CODE
FROM_COUNTRY FROM_COUNTRY
FROM_COUNTRY_NAME FROM_COUNTRY_NAME
FROM_LATITUDE FROM_LATITUDE
FROM_LOCATION_TYPE FROM_LOCATION_TYPE
FROM_LOCATION_TYPE_NAME FROM_LOCATION_TYPE_NAME
FROM_LONGITUE FROM_LONGITUE
FROM_NAME FROM_NAME
FROM_REGION FROM_REGION
FROM_REGION_NAME FROM_REGION_NAME
FROM_SALESORG FROM_SALESORG
FROM_STATE FROM_STATE
FROM_STATENAME FROM_STATENAME
FROM_SUBSI FROM_SUBSI
ITR_COUNT ITR_COUNT ITR_COUNT
ITR_CRDATE ITR_CR_DATE ITR_CRDATE
ITR_CRQTY ITR_CR_QTY ITR_CRQTY
ITR_ETA ITR_ETA ITR_ETA
ITR_ETD ITR_ETD ITR_ETD
ITR_FROM ITR_FROM
ITR_PGI_DATE ITR_PGI_DATE ITR_PGI_DATE
ITR_QTY ITR_QTY ITR_QTY
ITR_SKU ITR_SKU ITR_SKU
ITR_STATUS ITR_STATUS ITR_STATUS
ITR_TYPE ITR_TYPE ITR_TYPE
ITRNO ITRNO ITRNO
REASON_CATEGORY REASON_CATEGORY REASON_CATEGORY
REASON_CODE REASON_CODE REASON_CODE
REASON_DESC REASON_DESC REASON_DESC
REASON_RECS REASON_RECS REASON_RECS
RFID_No
SCAN_DATE SCAN_DATE SCAN_DATE
SCAN_ITR_COUNT SCAN_ITR_COUNT SCAN_ITR_COUNT
SCAN_QTY SCAN_QTY SCAN_QTY
SCAN_UNKNOWNASSET_QTY SCAN_UNKNOWNASSET_QTY SCAN_UNKNOWNASSET_QTY
TO_CITY TO_CITY
TO_CODE TO_CODE
TO_COUNTRY TO_COUNTRY
TO_COUNTRY_NAME TO_COUNTRY_NAME
TO_LATITUDE TO_LATITUDE
TO_LOCATION_TYPE TO_LOCATION_TYPE
TO_LOCATION_TYPE_NAME TO_LOCATION_TYPE_NAME
TO_LONGITUE TO_LONGITUE
TO_NAME TO_NAME
TO_REGION TO_REGION
TO_REGION_NAME TO_REGION_NAME
TO_SALESORG TO_SALESORG
TO_STATE TO_STATE
TO_STATENAME TO_STATENAME
TO_SUBSI TO_SUBSI
TRANS_DATE TRANS_DATE
TRANSTYPE TRANSTYPE TRANSTYPE

You might also like