Regional Inventory

demand and supply cycle

Regional Inventory demand and supply cycle

Demand
SCMS Supply Chain Management System
SAM Franchise Order Demands

Supply
RIFS Fulfillment
Logistics Sending Shipping Order XML to GTNexus
Logistics Sending Milestone XML to GTNexus
RIFS Invoice
RIFS eInvoice

Reporting

SODE RI Reports

1) The SCMS receives the order from

Gap Store
Franchisee order
Online Order/Customer care order

Now these order are aggregated through cross channel to form Destination
Purchase Order DPO
2) SCMS forwards DPO to RMS (Retail Merchandise System) it is a Inventory
Management system like a Virtual Ware house

3) RMS forward DPO to logistic partner Global Logistic Visibility.

4) GLV routes the DPOs to the appropriate Manufacture

5) The Manufacturer vendor fulfills the demand and ship the time to
regional warehouse HUB which has a Automated WMS Warehouse
Management System

6) The WMS forward the receipt for good received to RMS

SAM Franchise Order Demand

1.

2.
3.

4.

5.
6.
7.
8.

Sales Admin place Franchisee Order Demand (FOD's) in the SAM legacy
system
SAM Legacy will flag the FOD as HUB while saving it in DB
Sam Service periodically scans SAM DB and will pick up the new FODs
flagged as HUB
FODs are enriched with the global SKU #, style description from ITEMMASTER for Each SKU in Demand
FODs are enriched with Vendor Details from ACT
The enriched FODs are sent to SCMS via sendPlan
SCMS performs the task and reverts with the DPO details.
SAM Services add the DPO - Destination Purchase Order details to SAM
DB and flags the PO as needing to be forwarded to GTNexus.

Key Points
* Franchisee Order Demand will have one style at the style-color level and
different quantities but multiple sku(for different sizes, each size 1 sku)
For Eg.
Style -> Tshirt Color-> Red Quantity 10 in S, 20 in L, 20 in XL....(each size 1 sku)
EACH SKU is a style-color-size combination

Fullfillment Process
1.

2.

3.
4.

5.

A Fulfillment Engineer searching order in RIFS web,

RIFS application internally query SAM DB to get order
details and stock details from RMS web service.
If enough stock have arrived in RMS to satisfy the
threshold for a FO fulfillment
Fulfillment order will be submitted to RIFS application
RIFS submit Inventory allocation request to
RMS(REST Web Service)
After the fulfillment details are saved in the RIFS DB,
a Pick notification request is generated by RIFS and
placed on the WMS Queue(QA.FRN.ESB.ENT.TXN.ROUTER) as
a JMS Message(allocation xml ). `

Flow diagram of shipping order.xml

generation

Shipment
Service

5. Pick
Notification /
Allocation xml

t
en
m
l
fi
Ful ails
t
De

Logistics Sending Shipping

Order XML to GTNexus

After the fulfillment details are saved in the RIFS DB, a Pick notification request is generated
by RIFS and placed on the WMS queue as a JMS message (allocation xml ).
6. Upon WMS receiving notification, a robotic system automatically picks the FO fulfillment items
and moves them to the holding bay.
7. Each pick results in a Pick Complete Notification(PCN) being placed on a RIFS and Logistics
queue as a JMS message. A PCN is also called ASN, termed DRASN(Doc Ready Advanced Shipping
Notice) at this point.
8. Upon Logistics service receiving the first DRASN, it builds a shipment the pack control number
from the DRASN(masterBOL) and foId retrieved from RIFS and saves the Shipment to LogisticsDb.
9. Once all DRASNs have been received for a fulfillment order, it generates invoice number and
prepares shipping order.xml
10. Logistics services checks to see if shipping order.xml has previously been sent, if no then it is
placed on the GTNexus queue as a JMS message.
11. Logistics services saves the latest version of shipping order.xml to the LogisticsDb.
12. GTNexus creates custom documentation from the Shipping order xml and forwards it to the
franchise.

DRASN Audit Flow Diagram

DRASN.XML
received for
shipment.
Ye
Parsed
s
successfully?
Invali
d ASN

Ye
Is Franchisee s
ASN?
No

IC: Save
record with
total lines with
EXPECTED
status &
comment

Yes

Processing
Valid
Franchisee
ASN

Is first ASN?

No
Error while
processing?

No
Add ASN to
Shipment

Yes

En
d

IC: Save
record with
total lines as 1
with Rejected
status &
comment

Create new
shipment.

Ye
Duplicate ASN for ASN
s
Shipment
added
No
successfu
lly?

IC: Save record with total

lines as 1 with Processed
status

No

Send SO to
GTN EDI
queue

PC: Save unit count,

carton count and sku
count with EXPECTED
(from shipment entity)
and SENT (from SO XML)

Ye
s
No

SO
identical to
Previous
sent
SO?

No

Manua
l
trigger
Ye
?
s

Are all
DRASNs
receive
d?
Ye
s

Generate ship
order xml

Logistics sending Milestone

XML to GTnexus

11. The franchisee visits regional hub with their custom documents to
collect their shipment.
12. The warehouse attendant scans each cartons of shipment.
An OBASN is created for each scanned sku in each of the cartons.
These OBASNs are placed in the logistics queue as a JMS message.
13. The Logistics updates the logistics DB with the details.
14. Once all the OBASNS have been received, Logistics generates the
milestone.xml, which is a consolidation of all the OBASNs for the
particular shipping order xml.
Logistics then places the milestone.xml in the GTNexus queue as
a JMS message.

Database
RIDB
Users

- Contains authorized users list for RIFS

InvoiceMessage - Contains failed invoice details
Sequence Stores a sequence number range and current number (franchisee
allocations etc. are designated with a specified range)
UnprocessedMessage - For PickComplete and WTODetail messages, if we do not
receive all DRASNs or OBASNs in a given interval we log this abnormality.
WTODetails Contains Warehouse Turnover and Milestone details (foId,
alreadyBeenExtractedForLogistics, asnList etc.)
FOFulfillmentDetails - Contains Franchise Order Fulfillment details
OrderFullFillment
SkuFullFillment
PCNDetails - Contains pick control number and allocation details (foId, pcnId,
fulfillmentItems etc.)
OrderAllocation
SkuAllocation
PickComplete - Contains shipment details(foId, InvoiceNumber etc.)
ASN