Sequence on

how we want it
to display on
DT reporting &
UL admin
reporting

Sr. No. Error ID sequence Error Types: Clustering of Error Error Rule Engine

1 EI1 DT01 Customer PO does not meet pattern DT only R1

2 EI2 DT02 Customer PO larger than maximum length DT only R2

3 EI3 DT03 Customer PO not same like delivery ticket DT only R3

4 EI4 UL01 Date outside retailer's operation date UL only R4

5 EI5 DT07 Delivery date in the future DT only R5

Delivery date less than allowable days of
6 EI6 DT08 DT only R6
current date
7 EI7 DT09 Delivery ticket no missing DT only R7
8 EI8 DT04 Duplicate customer PO DT only R8
9 EI9 DT10 Duplicate delivery ticket no DT only R9

10 EI10 DT13 Duplicate Line Item DT only R10

11 EI11 DT12 Eaches not in full boxes DT only R11

12 EI12 DT05 / UL02 Invalid customer UL/DT R12

13 EI13 DT11 Invalid Product DT only R13

14 EI14 DT06 No delivery date DT only R14
15 EI15 DT14 No line item DT only R15
16 EI16 DT15 / UL03 Product not listed UL/DT R16

Quantity exceeds box threshold - requires

17 EI17 DT16 / UL04 UL/DT R17
verification
18 EI18 n/a Sub - Distributor Missing DT only R18

Total quantity exceeds total eaches threshold -

19 EI19 n/a UL (visible to DT) R19
Requires verification
User Story number SMTM-18

Applicability DR/CR Explanation

Some customer groups have prefix (pattern) - PO start digits/letters,

length.
DR/CR
ex. Go Puff starts with GUS and has 6 char(GoPuff),
AEFIS - Starts with 'VON' - 9 digit

Length of PO should be certain

DR/CR ex.AEFIS - 9 digit
Go Puff - 6 Digits

If customer PO number is not available then PO number should be

updated as delivery no (Except for Go Puff-96, AAFES-60, Doordash -
DR/CR
0A)
Need to add an error logic for Go puff etc to mandatorily have PO
number.

If the mapping DT-Retailer changes, the delivery date should fall

DR between new changed dates
Store closed case

DR/CR Standard check ; DT sends ticket in advance of delivery

DR/CR DT sends delivery date older than 90 days
DR/CR Mandatory field, should be equal to PO number
DR/CR Standard check for both type of DN
DR/CR Standard check for both type of DN

DR/CR Standard check for both type of DN

Partial delivery, less or more eaches than assigned boxes

DR ex. 1 box = 10 eaches but DT delivered only 8 eaches so either pack size
info on the DT end is wrong or SAP needs to correct
Either customer mapping with DT is wrong or customer doesn't exist in
DR/CR
the system

DR Non - Unilever Products, item UPC issue

DR/CR Mandatory field
DR/CR When no any line is there in the DN
DR Product to customer mapping (listing issue on either end)

5 cases or more then an error(other); GoPuff (if DN matches the order,

ok ot pass, if it is less Ok to pass. If more cases, the send to DT)
DR Food Service migration - Magento to match the DN for line item and if
cases are equal or less and must be in full cases, Ok to pass. If delivery
is for more cases then order, put DN in error
DR sub - distributors

CR b
Uploaed on JIRA - Don't change without Debdas's approval

Validation

Rules needs to be written on the customer group level and it should

be config stuff in Magento/MS admin pannel.

Rules needs to be written on the customer group level and it should

be config stuff in Magento/MS admin panel.

2 attributes : Customer PO number & Delivery Ticket no should be

compared

Need to check from Customer Master & Hierarchy; delivery date

changes
The DT that was mapped to the customer for that delivery date
should be pushed in the order interface.
system date>= delivery date
90 days (configurable in admin)

Duplicate PO number should be validated for both confirmed

delivery note and error DN
Duplicate DN check to be built in line with PO numer

DN will not be created instead drop a mail to DT and put the error
log in Micro Service for viewing.

Product Master; Pack size changes needs to be handled

Customer Master(new customer), Listing

Refer product Master, we should check active and inactive products

for DN.. To be confirm by Gina.
Delivery date is a mandatory field.
In EDl - fail in EDI but we can't track these errors
Assortment should be a part of DN creation.

needs final call; on sku level ; customer group wise can we do?
Customer group & sku level checks needs to be there.
Ex. GoPuff Group is allowed to send 9 cases or less of each SKU
Mapping needed; DTs to update mapping in the panel, but it should
be check if Sub DT is avaliable or not. If it is not there we can to
allow creating DN.

on order total level

ex. If order has total 50 eaches or more, that'll be an error
Remarks

Posibility to be evaluated for matching PO Number for Go Puff from

Magento orders.

Delivery date should not be greater than system date.

Need to manage 120 days of pricing information.. Challenge to mitigated.

occurs when UL changes product pack sizes; distrib is selling through old
packs and has new packs in stock as well; need to update the quantity to
reflect combined boxes sold.
For Manual is it is a system check.

Out of
errored DN, DT or UL can fix
scope?

notify need to send the mail

It will be very complex to manage @ Customer group/SKU level.

Default is RTZZ . Not manual. It should come from mapping. (this is not an
error)
 Common error types Retailer Group Responsibility
PO# (missing, incorrect) AAFES Distributor/Unilever

FS accounts Distributor/Unilever

Date Outside Retailer's Operation Date ALL Distributor/Unilever

Delivery Date In The Future Others Distributor/Unilever

FS accounts

Delivery Date Less Than Allowable Days

of Current Date ALL Distributor/Unilever
(Means over 90 day limit)

Delivery Ticket No Missing ALL Distributor/Unilever

Duplicate Customer PO AAFES Distributor/Unilever

FS accounts Distributor/Unilever

Others Distributor/Unilever
Duplicate Delivery Ticket No ALL AeV/Unilever

Duplicate Line Item ALL Unilever

Eaches Not in Full Boxes ALL Distributor/Unilever

AeV

Invalid Customer ALL Distributor/Unilever

Invalid Product ALL Distributor/Unilever

Product Not Listed ALL Distributor/Unilever

Quantity Exceeds Box Threshold - Requires FS accounts Unilever (AeV)

Others Distributor/Unilever

Retailer Not Active ALL Distributor/Unilever

Total Quantity Exceeds Total Eaches Thres ALL Unilever

 Cause(s) of Error Correction Process
not transmitted on ticket; various
contact distributor to provide
scenarios
not transmitted on ticket; various
contact distributor to provide
scenarios

every retailer has a start and end date in

SAP. Occurs when a ticket is outside that
date range. Due to master data setup
incorrectly or 2 distribs servicing the
account
determine what start date should be;
submit template to change; confirm with
distributor manager if this is the authorized
distributor

distribs send in ticket in advance of

delivery; if only 1-3 days leave as is; if
process on the delivery date
farther in advance ask distrib to change
their sending parameters

dist send in tickets when ordered -

sometimes 2 wks in advance; should not contact distrib if changes are needed
be sending in FS tickets prior to delivery
as we need 'clean' tickets

usually process it, if 1 or 2; FD is VERY strict

Dist sends in tickets more than 90 old;
sometimes missed when setting up new
retailers or retailer groups; tickets were
reversed by Revenue and dist was not
aware and did not re-send.
on their 6-month policy. Other rets allow
really old tickets. Check with Revenue
Analyst first prior to processing; advise dist.
If many tickets or often, find out why so the
problem is rectified

tickets cannot be transmitted without a

ticket number; however sometimes the resolution is to contact the distributor and
distributor deletes the ticket number and advise how to delete the entire ticket
other fields on the ticket in an attempt to
delete the ticket from SOCS

AAFES does not accept dupe tick nos;

entered incorrectly on ticket - by dist
order desk or customer entry
contact dist to provide correct #; contact
Revenue Analyst to reverse/chargeback
previous ticket if required, and have dist re-
send ticket with correct VON.

entered incorrectly on ticket - by dist contact distributor to provide; may need to

order desk have tick with incorrect PO# reversed

if no PO# is provided, usually the ticket #

is used as the PO#; distribs often 'recycle' usually this is in conjunction with a dupe
ticket numbers or use the same sequence tickect number; see dupe tick process
on multiple handhelds
 look in dist instance for that ticket; if it is a
dupe number and not a dupe ticket
distribs often 'recycle' ticket numbers or (different date and products); then process
use the same sequence on multiple the ticket 'as is'. FD will not accept dupe
handhelds tick numbers so add an 'A' prior to
processing ticket. AeV usually re-sends;
mass duplicates are handled by AeV

look in dist instance for that ticket; if it is a

dupe number and not a dupe ticket
dupe tickets are often due to
(different date and products); then process
reversing/rebilling or malfunctions in
the ticket 'as is'. FD will not accept dupe
SAP; occasionally there have been mass
tick numbers so add an 'A' prior to
duplicates
processing ticket. AeV usually re-sends;
mass duplicates are handled by AeV

occurs when UL changes product pack

sizes; distrib is selling through old packs remove the other line item and process
and has new packs in stock as well; need
to update the quantity to reflect ticket
combined boxes sold

occurs when a user is trying to make a remove the other line item and process
product change due to incorrect UPC ticket

wait 2 days for dist to correct; then send

email advising it needs to be updated;
partial box quantities are transmitted; watch for patterns; if multiple tickets are in
some dist deliver partial boxes; caused by error with the same product, it means the
incorrect configurations in dist system; dist has it set up incorrectly in their system;
mass mistakes can be updated in databse
by AeV

UL changed box quantity and dist are still

change in box quantity by UL selling through; AeV updates database and
processes tickets

occurs when master data is setup check the master lists from retailer groups;
incorrectly (wrong info or late start date) if ret is not in the system, then email dist to
OR when retailer has not been set up at request customer info; submit all
all changes/additions on template
 email dist to make update in their system
showing incorrect one used and right one to
use; correct the ticket and process. If non-
occurs when dist sends wrong UPC
UL prods, remove from ticket and process.
(usually case UPC) OR when sending non-
If distribs are not advised to make the
UL products.
change, this will continue to happen. Does
not resolve the issue to
correct and process the ticket in SOCS
without having the distrib make the change.

occurs when dist transmits unlisted

product; ask distrib if they have
documentation showing it is authorized. Email dist with current authorized listing so
they can update their system. UL does not
There are variables in listings and
pay for unlisted prods - costs the distrib
sometimes items are missed being
money.
authorized by Unilever; contact Gina to
update.

Ask for SIGNED POD; verify the quantities

occurs when an item qty is over the
specified amount (5-7 boxes usually);
distribs cannot override this error for any Once the distrib has the calculations set up
account.
and calculations are correct then perform
override; if not correct, then email dist to
have the calculations fixed in their system.
Have the dist re-send a 'clean' ticket.
correctly, it is not necessary to do the math
for each prod. Qtys may varify from the
POD due to damages or add-ons.

If multiple tickets have the same product in

occurs when an item qty is over the
specified amount (5-7 boxes usually); if
amount looks reasonable, process the
ticket.
error, confirm with distrib re calculations in
their system. Email dist for POD for
verification of any quantity in question.
Sometimes the qty is way off and when you
email the distrib they will adjust it to the
correct qty and the ticket processes without
your intervention.

usually reserved for locations that have had

a master data error by UL and/or the
retailer has been deactivated in SAP
distrib. Investigate in SAP and advise distrib
of action. May require additional followup

retailer credits only override and process

Error Types:

1. Customer PO does not meet pattern

2. Customer PO larger than maximum length
3. Customer PO less than minimum length
4. Customer PO misising

5. Customer PO not same like delivery ticket

6. Date outside retailer's operation date

7. Delivery date before active day
8. Delivery date before active period
9. Delivery date in the future
10. Delivery date less than allowable days of current date
11. Delivery ticket no missing
12. Dispatch no exists
13. Duplicate customer PO
14. Duplicate delivery ticket no
15. Duplicate Line Item

16. Eaches not in full boxes

17. Invalid customer

18. Invalid Product
19. No delivery date

20. No line item

21. No term
22. Non - Unilever Products
23. Product not listed
24. Product not active
25. Product restricted

26. Quantity exceeds box threshold - requires verification

27. Retailer not active
28. Retailer is not OT
29. Route Missing
30. Salesman Missing
31. Stock Shortage
32. Term Mismatch
33. Total quantity exceeds total eaches threashold - Requires verification

34. Blank (this shows all the errored DNs)

Explanation Validation
ex. Gus(GoPuff), PO start digits/letters, length
mapping needed (rules)
VON - 9 digit, customer grp specific, no prefix mapping needed (rules)
mapping needed (rules)
mapping needed (rules)
If customer PO number is not available then PO
number should be updated as delivery no

If the mapping DT-Retailer changes, the delivery date

should fall between new changed dates Customer Master & Hierarchy; delivery date
Store closed case changes
Which master is it coming from?
Which master is it coming from?
Standard check system date>= today
120 days (configurable in admin)
Mandatory
?
Standard check
Standard check
Standard check
Partial delivery, less or more eaches than assigned Product Master; Pack size changes needs to
boxes be handled

Customer Master(new customer), Listing

Non - Unilever Products, item UPC issue Product Master

In EDl - fail in EDI but we can't track these

errors
?

Assortment Master
Product

5 cases or more then an error(other); GoPuff 9 cases

(we have the orders to check so it is fine) needs final call; on sku level ; customer
Food Service migration - more cases group wise can we do?

OT?
warehouses mapping needed
Needed?
Needed?
?
use only for credit; 50 eaches or over on order total level

For all the errors above, we'll keep the

delivery ticket in the error log. Once
corrected then these tickets will be
All Errors, standard query search processed
 Customer Group specific
pattern

GoPuff Duns number, Magento

needs to reprocess the
customer master. Duns number
should be on DN, retailer code
mandatory