Document Control

Date Author Version Change reference

13-Feb-2023 Hermanto Tjioe 0.1 Initial Document

Reviewers

No. Name Position Note

1
2
3
4

5
 AZN1.0 Is customer
Yes Decision box
Create Process step that is a identified ?
Sales Order manual activity or
happens outside Oracle
External-Amazon
No

OM-004 Subprocess. Must

OM 1.1 Process step that occurs OM-004 Hold Applied have reference to
Book Sales Order in an Oracle that Hold Applied another process
performed by a User. flow

Oracle-OM UI

Integration Flow
SO1 between Oracle,
Legacy OMS System Legacy or any
WMS 2.0 To Create/ Update/ Delete external system
Oracle Sales Order Process step that occurs in an Sales Order with Route Information
Creation Oracle RF/ UI that performed
by System automatically.
Oracle-OM UI

Receipt Extract Input to a step/

OM 3.0 loaded in process or output
Print BOL and Process step that occurs in Oracle through staging table. from a step/process
Packing Slip Shipping a RICE. Must have RICE reference
Documents RICE stands for Report, Interface,
Customization, Extension.
Oracle-OM UI
 JR286 US Warehouse
Korber WMS Oracle EBS ERP Future Roll-out Future Roll-out
Korber WMS Oracle EBS ERP Korber WMS Oracle EBS ERP
TOTAL BRAND
US Harborgate ENI-JR286, INC. (OU) DEVELOPMENT LLC
Distribution Center (OU)
(WH. Code: DC01)
JR286
Hawaii Distribution DAKINE EQUIPMENT China Distribution INTERNATIONAL,
Center LLC. (OU) Center LLC (OU)
(WH. Code: DC02) (WH. Code: DC03)

JR286 INTL Rest of the

Dakine Hawaii JR286 INTL Rest of the World.
ENI US Torrance Dakine Hawaii Inventory Organization World. Inventory Organization
ENI US Torrance Inventory Organization Korber Client Code: 452 Code: 452 Korber Client Code: 850 Code: 850
Korber Client Code: 900 Code: 900

DAKINE EQUIPMENT
LLC. (OU)

JR286 INTL APAC. JR286 INTL APAC.

Dakine Torrance Korber Client Code: 851 Inventory Organization
Dakine US Torrance Inventory Organization Code: 851
Korber Client Code: 451 Code: 451

EAI-JR286, Inc.(OU)

EAI US Torrance EAI Torrance

Korber Client Code: 400 Inventory Organization
Code: 400
 JR286 US Warehouse
Korber WMS Oracle EBS ERP

Locator DFF Hold Code

TOTAL BRAND
US Harborgate ENI-JR286, INC. (OU) DEVELOPMENT LLC
Distribution Center (OU)
(WH. Code: DC01)

ENI US Torrance
ENI US Torrance Inventory Organization
Korber Client Code: 900 Code: 900

Locator:
Hold Code = Null B1K.00.000.00.0
GOOD

Locator:
Hold Code = QCH.00.000.00.0
QCHOLD QCHOLD

Hold Code = Locator:

QCDEFECT QDF.00.000.00.0
QCDAMAGE DEFECT,DAMAGE

Hold Code = Locator:

VAS.00.000.00.0
VAS VAS

Hold Code = Locator:

VAS.00.000.00.1
VASCOMPLETE VASCOMPLETE

DAKINE EQUIPMENT
LLC. (OU)

Dakine US Torrance Dakine Torrance

Korber Client Code: 451 Inventory Organization
Code: 451

EAI-JR286, Inc.(OU)

EAI Torrance
EAI US Torrance Inventory Organization
Korber Client Code: 400 Code: 400
 Master Data Interface From ERP to Korber WMS
3. AWS to convert the data
2. Staging Table Populated with to Json format, then call
information from Oracle Korber’s WS API
1. Program to populate the
Interface staging table in Data Mart

Apps Vers. : 12.2.5 - Create

Item UOM EA/Each (Daily)
DB Vers. : 19.0.0.0.0 Data Mart Korber WMS
Item UOM CS/ Case (Daily)
Purchase Order (Daily) 4. Korber’s WS API
External Sales Order Delivery (10 Minutes) 5. Update Interface Staging returns the response
Internal Sales Order Delivery (10 Minutes) Table Status
Sales Order Return/ RMA (Daily)
Return to Supplier (Daily)

- Create and Update

Item Master (Daily)
MSRP (Daily)

Sales Order Shipment Interface From Korber WMS to ERP

3. For Parcel Shipment, auto update
tracking info, then perform ship
confirmation.
For TL/ LTL Shipment, user to update
2. End of Day Process. Fedex tracking info, then perform ship
Ship Station and UPS World confirmation. 4. AWS to consume the Ship
Ship to populate the Parcel Ship confirmation Json file generated Confirmation Json file. 6. AWS to populate the Interface 7. Oracle Concurrent Program
Staging table with tracking for Parcel, TL/ LTL Shipments. staging table in Data Mart to process the interface staging
Parcel Shipments number, ... Return to Vendor will fall under one of
table and update the status
the shipment type.

Apps Vers. : 12.2.5

Data Mart DB Vers. : 19.0.0.0.0
Korber WMS 5. AWS returns the response to
1. Korber Parcel Shipment flag that the corresponding Ship
Order Info read by Fedex Ship Confirmation Json file has been
Station and UPS World Ship consumed.

Inventory Interface From Korber WMS to ERP

1. Korber WMS generated Json file for below
• PO Receipt Confirmation
• RMA Receipt Confirmation
• Internal Requisition Receipt Confirmation
5. Oracle Concurrent Program
• Cycle Count Adjustment 4. AWS to populate the Interface
2. AWS to consume the Json file. to process the interface staging
• Manual Inventory Adjustment staging table in Data Mart
table and update the status
• Inventory Status Hold Code Update

Apps Vers. : 12.2.5

Data Mart DB Vers. : 19.0.0.0.0
Korber WMS
3. AWS returns the response to
flag that the corresponding Json
file has been consumed.

Inventory Onhand Snapshot Interface From Korber WMS to ERP (TBD)

1. Korber WMS generated Json file Daily

Inventory Onhand snapshot. 5. Oracle Concurrent Program
4. AWS to populate the Interface to process the interface staging
2. AWS to consume the Json file.
staging table in Data Mart table and update the status

Apps Vers. : 12.2.5

DB Vers. : 19.0.0.0.0
Data Mart
Korber WMS
3. AWS returns the response to
flag that the corresponding Json
file has been consumed.
 Harborgate Distribution Center
Internal Transfer Customer Returns
Factory/ Supplier
(Internal Requisition/ (Return Material
(Purchase Order/ PO) Authorization/ RMA)
IR)

- Rejection (Over ship, damaged, short)

Applicable for Dakine Entity
Receiving and Sorting

Inbound Shipment and

Sorting Area

Sorting and Palletizing

Full/ Partial Putaway

Single/ Mixed
Pallet?

If put away rules can’t find any eligible bin, then

it would be directed to Catch all Location

Putaway
- Fill Slotted Item to the Max Qty
- Non Slotted Item->Find an Empty Bin
Locate LPN

Locate LPN
Finished Goods would be completed
Locate LPN
in an IBLPN to FG Location, then
Keep Pallet ID
moved by User to Storage

Long Stock Bins/ Small Parts Bins/ Small Parts

(Reserve) (Active) Locate LPN
(Reserve) HOLD WIP Area
WIP Issue/ Backflush
Bulk Finished Goods
(Reserve) Order Based/Min-Max Hold/Quarantine Area (Kitting/ De-Kitting) (WIP Order Completion)
Long Stock Floor Pick Floor Pick
Replenishment (Reserve) (Active)
(Active)

Locate LPN

Sales Order Picking Sales Order Picking WIP Picking

WIP Picking

Outbound Staging and

Sorting Area

Load/ Unload to Trailer

Load/ Unload Area

Ship Load Confirmation

Legend:
Active/ Non-LPN Controlled

OMS/ Customer/ Others Reserve/ LPN Controlled

Facility Organization
Item Master Integration from ERP to Korber WMS

Mapping Document:
Inbound - Interface Import Design
Sheet: Item Master, Item UOM-EA, Item UOM-CS
Follow the Item Master Last Updated Date and below
Follow the Item Master Last Updated Date and below condition condition
- Scheduled Daily MTL_SYSTEM_ITEMS_B.GLOBAL_ATTRIBUTE2 <> ‘Y’ or IS NULL. MTL_SYSTEM_ITEMS_B.GLOBAL_ATTRIBUTE3 <> ‘Y’ or IS
- Program Parameters: NULL.
a. Korber Wh. Code: (LOV – Optional) Table Name: Table Name:
Oracle ERP Item Master

b. Korber Client Code: (LOV – Optional) - XXJR_KORBER_OB_ITM_MASTER_T (Oracle) - XXJR_KORBER_OB_ITM_UOM_EA_T (Oracle) Table Name:
c. Number of Days: (Number– Required) - XXJR_KORBER_OB_ITM_MASTER (DataMart) - XXJR_KORBER_OB_ITM_UOM_EA (DataMart) - XXJR_KORBER_OB_ITM_UOM_CS_T (Oracle)
Based on Item Org. last updated date Unique Record ID Sequence Name: Unique Record ID Sequence Name: - XXJR_KORBER_OB_ITM_UOM_CS (DataMart)
d. Unique Batch Num of Record (Number-Required) - XXJR_KORBER_OB_ITEM_MASTER_S - XXJR_KORBER_OB_ITEM_UOM_EA_S Unique Record ID Sequence Name:
e. Items: (200 Free Text – Optional). Using comma Host Group ID Sequence Name Host Group ID Sequence Name - XXJR_KORBER_OB_ITEM_UOM_CS_S
to separate the item that user wants to - XXJR_KORBER_OB_ITEM_GROUP_S - Same HOST_GROUP_ID that assigned from Item Master Host Group ID Sequence Name
manually extract by the program - Process Flag = N Additional Step After Extracting the UOM EA: - Same HOST_GROUP_ID that assigned from Item Master
- Update MTL_SYSTEM_ITEMS_B.GLOBAL_ATTRIBUTE2 to ‘Y’ for Additional Step After Extracting the UOM CS:
extracted record. - Update MTL_SYSTEM_ITEMS_B.GLOBAL_ATTRIBUTE3 to ‘Y’
for extracted record.

INTWMS 1.2 INTWMS 1.3 INTWMS 1.4

INTWMS 1.1
Extract the Item Master Extract the Item UOM EA Extract the Item UOM EA
Scheduled XXJR:
Start Information based on the Entered Information based on the Entered Information based on the Entered
Korber Outbound Item
Parameters and Populate Parameters and Populate Parameters and Populate
Master
Interface Table in Data Mart Interface Table in Data Mart Interface Table in Data Mart
INV INV INV INV

Process Flag
- S (Success)
- E (Error) and Error message populated

Korber Interface
Report
Data Mart

INTDM 6.1
Process Flag and Message Updated in
INTDM 2.1 INTDM 2.2 INTDM 2.3 XXJR_KORBER_OB_ITEM_MASTER End
XXJR_KORBER_OB_ITEM_ XXJR_KORBER_OB_ITEM_ XXJR_KORBER_OB_ITEM_ XXJR_KORBER_OB_ITEM_UOM_EA
MASTER Populated UOM_EA Populated UOM_CS Populated XXJR_KORBER_OB_ITEM_UOM_CS

External – Data Mart External – Data Mart External – Data Mart External – Data Mart
Amazon Web Services

INTAWS 3.2
INTAWS 3.1 INTAWS 5.1
Json File Created for
Process Staging Interface Translate Response and
Corresponding
Record with Process Flag = Update Record in Staging
host_group_id. Call Korber
N group by host_group_id Table
Item Master WS API
External – AWS External – AWS External – AWS
Korber WMS

INTKORBER 4.1
Return WS API Response to
AWS

External – Korber WS
Purchase Order Integration from ERP to Korber WMS

Mapping Document:
- Scheduled Daily
Inbound - Interface Import Design - Program Parameters:
Sheet: IB - PO Master, IB - PO Detail a. Korber Wh. Code: (LOV – Optional)
b. Korber Client Code: (LOV – Optional)
c. Number of Days: (Number– Required). Table Name:
Example: User entered 10 days, then program will - XXJR_KORBER_OB_PO_T (Oracle)
extract all POs that have promised date <= - XXJR_KORBER_OB_PO (DataMart)
sysdate+10 Unique Record ID Sequence Name:
e. PO Number: (100 Free Text – Optional). Using - XXJR_KORBER_OB_PO_S
Oracle ERP Item Master

comma to separate the PO Number that user Host Group ID Sequence Name
wants to manually extract by the program - XXJR_KORBER_OB_PO_GROUP_S
Extract Condition: - Process Flag = N
PO_HEADERS_ALL.TYPE_LOOKUP_CODE = ‘STANDARD’ Additional Step:
and PO_HEADERS_ALL.ATTRIBUTE14 is null - Update PO_HEADERS_ALL.ATTRIBUTE14 with Host Group ID for extracted record.

INTWMS 1.2
INTWMS 1.1
Extract the Information based
Scheduled XXJR:
Start on the Entered Parameters
Korber Outbound
and Populate Interface Table
Purchase Order
in Data Mart
INV INV

Process Flag
- S (Success)
- E (Error) and Error message populated

Korber Interface
Report
Data Mart

INTDM 6.1
INTDM 2.1
Process Flag and Message
XXJR_KORBER_OB_PO End
Updated in
Populated
XXJR_KORBER_OB_PO

External – Data Mart External – Data Mart

Amazon Web Services

INTAWS 3.2
INTAWS 3.1 INTAWS 5.1
Json File Created for
Process Staging Interface Translate Response and
Corresponding
Record with Process Flag = Update Record in Staging
host_group_id. Call Korber
N group by host_group_id Table
Purchase Order WS API
External – AWS External – AWS External – AWS
Korber WMS

INTKORBER 4.1
Return WS API Response to
AWS

External – Korber WS
Return Material Authorization/ Sales Order Returns Integration from ERP to Korber WMS

Mapping Document:
Inbound - Interface Import Design
Sheet: IB - PO Master-RMA, IB - PO Detail-RMA - Scheduled Daily
- Program Parameters:
a. Korber Wh. Code: (LOV – Optional)
b. Korber Client Code: (LOV – Optional) Table Name:
c. Number of Days: (Number– Required). - XXJR_KORBER_OB_PO_T (Oracle)
Oracle ERP Order Management

Example: User entered 10 days, then program will - XXJR_KORBER_OB_PO (DataMart)

extract all RMAs that have last update date >= Unique Record ID Sequence Name:
sysdate+10 - XXJR_KORBER_OB_PO_S
e. RMA Number: (100 Free Text – Optional). Using Host Group ID Sequence Name
comma to separate the RMA Number that user - XXJR_KORBER_OB_PO_GROUP_S
wants to manually extract by the program - Process Flag = N
Extract Condition: Additional Step:
OE_ORDER_HEADERS_ALL.ORDER_CATEGORY_CODE = 'RETURN' - Update OE_ORDER_HEADERS_ALL.ATTRIBUTE14 with Host Group ID for
and OE_ORDER_HEADERS_ALL.ATTRIBUTE14 is null extracted record.
Note:
RMA will use Korber PO Interface with PO Type = “Return Orders”

INTWMS 1.2
INTWMS 1.1 Extract the Information
Start Scheduled XXJR: based on the Entered
Korber Outbound RMA Parameters and Populate
Interface Table in Data Mart
RMA RMA

Process Flag
- S (Success)
- E (Error) and Error message populated

Korber Interface
Data Mart

Report
INTDM 2.1 INTDM 6.1
Auto Sync Process Flag and Message
XXJR_KORBER_OB_PO Updated in End
Populated XXJR_KORBER_OB_PO

External – Data Mart External – Data Mart

Amazon Web Services

INTAWS 3.2
INTAWS 3.1 INTAWS 5.1
Json File Created for
Process Staging Interface Translate Response and
Corresponding
Record with Process Flag = Update Record in Staging
host_group_id. Call Korber
N group by host_group_id Table
Purchase Order WS API
External – AWS External – AWS External – AWS
Korber WMS

INTKORBER 4.1
Return WS API Response to
AWS

External – Korber WS
Internal Requisition – Internal Sales Order Receipt Integration from ERP to Korber WMS

Mapping Document:
- Scheduled Daily
Inbound - Interface Import Design
- Program Parameters:
Sheet: IB - PO Master-IRISO, IB - PO Detail-IRISO a. Korber Wh. Code: (LOV – Optional)
b. Korber Client Code: (LOV – Optional) Table Name:
c. Number of Days: (Number– Required). - XXJR_KORBER_OB_PO_T (Oracle)
Oracle ERP Internal Requisition

Example: User entered 10 days, then program will - XXJR_KORBER_OB_PO (DataMart)

extract all Internal Intransit Shipment that have Unique Record ID Sequence Name:
last update date >= sysdate+10 - XXJR_KORBER_OB_PO_S
e. Internal Shipment Number: (100 Free Text – Host Group ID Sequence Name
Optional). Using comma to separate the Internal - XXJR_KORBER_OB_PO_GROUP_S
Shipment Number that user wants to manually - Process Flag = N
extract by the program Additional Step:
Extract Condition - Update RCV_SHIPMENT_HEADERS.ATTRIBUTE14 with Host Group
RCV_SHIPMENT_HEADERS.RECEIPT_SOURCE_CODE = 'INTERNAL ID for extracted record.
ORDER' and RCV_SHIPMENT_HEADERS.ATTRIBUTE14 is null Note:
Internal Shipment Number (IR-ISO) will use Korber PO Interface
with PO Type = “Purchase Orders”

INTWMS 1.2
INTWMS 1.1
Extract the Information
Scheduled XXJR:
Start based on the Entered
Korber Outbound IR-
Parameters and Populate
ISO Shipment
Interface Table in Data Mart
IR IR

Process Flag
- S (Success)
- E (Error) and Error message populated

Korber Interface
Data Mart

Report
INTDM 2.1 INTDM 6.1
Auto Sync Process Flag and Message
XXJR_KORBER_OB_PO to Updated in End
Data Mart XXJR_KORBER_OB_PO

External – Data Mart External – Data Mart

Amazon Web Services

INTAWS 3.2
INTAWS 3.1 INTAWS 5.1
Json File Created for
Process Staging Interface Translate Response and
Corresponding
Record with Process Flag = Update Record in Staging
host_group_id. Call Korber
N group by host_group_id Table
Purchase Order WS API
External – AWS External – AWS External – AWS
Korber WMS

INTKORBER 4.1
Return WS API Response to
AWS

External – Korber WS
Sales Order Integration from ERP to Korber WMS

Mapping Document:
Inbound - Interface Import Design
Sheet: OB - Order Master, OB - Order Detail Lookup Name: XXJR_WMS_MARK_FOR_STORE
- Mark for Store Customer Number ATTRIBUTE1
- Mark for Store Number ATTRIBUTE2
- Mark for Store Address1 ATTRIBUTE3
- Mark for Store Address2 ATTRIBUTE4
- Mark for Store Address3 ATTRIBUTE5
- Mark for Store City ATTRIBUTE6
- Mark for Store State ATTRIBUTE7
- Mark for Store Zip Code ATTRIBUTE8
- Mark for Store Store Code ATTRIBUTE9

- Scheduled Daily
- Program Parameters:
a. Korber Wh. Code: (LOV – Optional)
b. Korber Client Code: (LOV – Optional)
c. Number of Days: (Number– Required). INTWMS 2.1
Example: User entered 10 days, then program will Populate SO Master and Detail
extract all Delivery that have creation date <= Table Name:
Mark for Store Columns
sysdate+10 - XXJR_KORBER_OB_DELIVERY_T (Oracle)
d. Delivery Batch Num of Record (Number-Required) - XXJR_KORBER_OB_DELIVERY (DataMart)
e. Delivery Number: (100 Free Text – Optional). Using WSH Unique Record ID Sequence Name:
comma to separate the Delivery Number that user Criteria - XXJR_KORBER_OB_DELIVERY_S
wants to manually extract by the program - Delivery doesn’t have any Trip assigned to it Host Group ID Sequence Name
f. Trip Number: (100 Free Text – Optional). Using - Delivery is in Open Status (WSH_NEW_DELIVERIES.STATUS_CODE <> ‘CL’) - XXJR_KORBER_OB_DELIVERY_GROUP_S
comma to separate the Trip Number that user - Have shipping line with ‘Release to Warehouse’ status. - Process Flag = N
wants to manually extract by the program -> WSH_DELIVERY_DETAILS.SOURCE_CODE = 'OE' Additional Step:
Extract Condition based on Shipment Extract Matrix. Yes -> WSH_DELIVERY_DETAILS.RELEASED_STATUS IN ( 'Y' ) - Update WSH_NEW_DELIVERIES.ATTRIBUTE14 with Host Group ID for
See next process -> Have record in WSH_DELIVERY_ASSIGNMENTS (connecting delivery with shipping line) extracted record.
- Delivery Header – Send to WMS Group ID is null (WSH_NEW_DELIVERIES.ATTRIBUTE14 is null) Host Group ID Logic:
Oracle ERP Order Management

- Crosscheck with Lookup XXJR_WMS_KORBER_SHIP_MATRIX - If parameter ‘Delivery Batch Num of Record’ value = 3, then program will
-> Ensure corresponding delivery order information not exists in assign the same Batch ID every 3 unique delivery number. Example: 5 delivery
Customer Number + Carrier + Ship Method Combination number is extracted, then program will assign Batch ID 1 to Delivery 1 to
Delivery 3, then Delivery 4 and 5 will have Batch ID 2

INTWMS 1.1
Scheduled XXJR: Korber
Start Mark For Store? INTWMS 3.1
Outbound Sales Order INTWMS 3.2
Extract Eligible Shipment
Delivery Trip Populate Interface Table in
Detail Based on Entered
Data Mart
WSH Program Parameters

WSH WSH
Table Name:
No Delivery Level Selection - XXJR_KORBER_OB_DELIVERY_T (Oracle)
- XXJR_KORBER_OB_DELIVERY (DataMart)
Criteria
Unique Record ID Sequence Name:
- Trip is in Open Status (WSH_TRIP.STATUS_CODE <> ‘CL’)
- XXJR_KORBER_OB_DELIVERY_S
- Trip DFF - Send to WMS Status = ‘R’ (WSH_TRIPS.ATTRIBUTE12 = ‘R’
Host Group ID Sequence Name
- Trip DFF - Send to WMS Group ID is null (WSH_TRIPS.ATTRIBUTE14 is null)
- XXJR_KORBER_OB_DELIVERY_GROUP_S
- Have Delivery Number Assigned with shipping line ‘Release to Warehouse’ status.
- Process Flag = N
-> WSH_DELIVERY_DETAILS.SOURCE_CODE = 'OE'
Additional Step:
-> WSH_DELIVERY_DETAILS.RELEASED_STATUS IN ( 'Y' )
- Update WSH_TRIPS.ATTRIBUTE14 and WSH_NEW_DELIVERIES.ATTRIBUTE14
Shipment Matrix -> Have record in WSH_DELIVERY_LEGS (connecting trip with delivery number)
with Host Group ID for extracted record.
-> Have record in WSH_DELIVERY_ASSIGNMENTS (connecting delivery with
- Update corresponding extracted Trip DFF - Send to WMS Status
shipping line)
(WSH_TRIPS.ATTRIBUTE12 = ‘S’)
- Delivery Header – Send to WMS Group ID is null
Host Group ID Logic:
(WSH_NEW_DELIVERIES.ATTRIBUTE14 is null)
- 1 Trip = 1 Host Group ID

Trip Level Selection

INTWMS 4.2
INTWMS 4.1
Populate Interface Table in
Extract Eligible Trip
Data Mart

WSH WSH

Process Flag
- S (Success)
- E (Error) and Error message populated
Data Mart

INTDM 9.1
INTDM 5.1
Process Flag and Message
XXJR_KORBER_OB_DELIVERY
Updated in
End
Populated
XXJR_KORBER_OB_DELIVERY

External – Data Mart External – Data Mart

Amazon Web Services

INTAWS 6.2
INTAWS 6.1 INTAWS 8.1
Json File Created for
Process Staging Interface Translate Response and
Corresponding
Record with Process Flag = Update Record in Staging
host_group_id. Call Korber
N group by host_group_id Table
Purchase Order WS API
External – AWS External – AWS External – AWS
Korber WMS

INTKORBER 7.1
Return WS API Response to
AWS

External – Korber WS
Item Master Integration from ERP to Korber WMS

Mapping Document:
Inbound - Interface Import Design - Scheduled Daily Table Name:
Sheet: MSRP (Inbound) - Program Parameters: - XXJR_KORBER_OB_MSRP_T (Oracle)
a. Korber Wh. Code: (LOV – Optional) - XXJR_KORBER_OB_MSRP (DataMart)
b. Korber Client Code: (LOV – Optional) Unique Record ID Sequence Name:
c. Unique Batch Num of Record (Number-Required) - XXJR_KORBER_OB_MSRP_S
e. Items: (200 Free Text – Optional). Using comma Host Group ID Sequence Name
Oracle ERP MSRP

to separate the item that user wants to - XXJR_KORBER_OB_MSRP_GROUP_S

manually extract by the program - Process Flag = N

INTWMS 1.2
INTWMS 1.1
Extract the Information based
Scheduled XXJR:
Start on the Entered Parameters
Korber Outbound
and Populate Interface Table
MSRP
in Data Mart
INV INV

Process Flag
- S (Success)
- E (Error) and Error message populated
Data Mart

Korber Interface
Report

INTDM 6.1
INTDM 2.1
Process Flag and Message
XXJR_KORBER_OB_MSRP
Updated in
End
Populated
XXJR_KORBER_OB_MSRP

External – Data Mart External – Data Mart

Amazon Web Services

INTAWS 3.2
INTAWS 3.1 INTAWS 5.1
Json File Created for
Process Staging Interface Translate Response and
Corresponding
Record with Process Flag = Update Record in Staging
host_group_id. Call Korber
N group by host_group_id Table
Item MSRP WS API
External – AWS External – AWS External – AWS
Korber WMS

INTKORBER 4.1
Return WS API Response to
AWS

External – Korber WS
Receipt Confirmation from Korber WMS to Oracle ERP

Mapping Document:
Inbound - Interface Export Design
Sheet: Receipt
Korber WMS

INTKORBER 1.1
Start Receipt Confirmation
Generated

External – Korber WS
Amazon Web
Services

INTAWS 2.1
Consume and Populate
Interface Table in Data
Mart

External – Korber WS
Data Mart

INTDM 3.1
XXJR_KORBER_IB_RECEIPT INTDM 10.1
Populated XXJR_KORBER_IB_RECEIPT End
Updated
External – Data Mart
External – Data Mart

- Scheduled Every Hour

- Program Parameters:
a. Korber Wh. Code: (LOV – Optional)
b. Korber Client Code: (LOV – Optional)
c. PO Number: (100 Free Text – Optional). Using comma to separate the PO
Number if user wants to manually process/ re-process specific POs
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If user select
Yes, then system select all records with ERP_PROCESS_FLAG = ‘E’ (error)
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user select Yes,
then display complete log in the view log output.

Selection Criteria:
- PO_TYPE = ‘Purchase Orders’
- ERP_PROCESS_FLAG = ‘N’ or NULL
- Use the same logic that use for XXJR: 3PL Main PO Stage Program
- Include Lot Number logic for Lot Controlled Item

Purchase Order Receipt

INTWMS 5.1
XXJR: Korber Inbound PO
Receipt

INV

- Scheduled Every Hour Interface Table Name: Staging Table Update for corresponding record
- Program Parameters: - RCV_HEADERS_INTERFACE - ERP_PROCESS_FLAG = ‘E’
a. Korber Wh. Code: (LOV – Optional) - RCV_TRANSACTIONS_INTERFACE - ERP_PROCESS_MESSAGE = Error Message from RTI API
b. Korber Client Code: (LOV – Optional) - MTL_TRANSACTION_LOTS_INTERFACE (For Lot - Delete Corresponding Error Records in RTI and MTLI Interface Tables
c. RMA Number: (100 Free Text – Optional). Using comma to separate the PO Controlled Items)
Number if user wants to manually process/ re-process specific RMAs
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If user select Key Mapped Fields
Yes, then system select all records with ERP_PROCESS_FLAG = ‘E’ (error) - XXJR_KORBER_IB_RECEIPT.HOLD_CODE Map to
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user select Yes, MTL_SECONDARY_INVENTORIES.ATTRIBUTE4
then display complete log in the view log output. INTWMS 9.1
Update
Oracle ERP

Selection Criteria: XXJR_KORBER_IB_RECEIPT

- PO_TYPE = ‘Return Orders’
- ERP_PROCESS_FLAG = ‘N’ or NULL Error INV
- Use the same logic that use for XXJR: 3PL Main RMA Stage Program
- Include Lot Number logic for Lot Controlled Item

RMA Receipt
INTWMS 4.1
INTWMS 6.1 INTWMS 8.1
Scheduled Program to Process
Receipt Type? XXJR: Korber Inbound RMA Insert Data to Receiving Interface Status? Staging Table Update for corresponding record
Record in
Receipt Transaction Interface Table - ERP_PROCESS_FLAG = ‘S’
XXJR_KORBER_IB_RECEIPT_T

INV INV INV

Success
- Scheduled Every Hour
INTWMS 9.3
- Program Parameters: INTWMS 9.2
a. Korber Wh. Code: (LOV – Optional) Onhand Created in End
Update
b. Korber Client Code: (LOV – Optional) Destination Subinventory and
XXJR_KORBER_IB_RECEIPT
c. IR Number: (100 Free Text – Optional). Using comma to separate the PO Inventory Org.
Number if user wants to manually process/ re-process specific IRs
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If user select INV INV
Yes, then system select all records with ERP_PROCESS_FLAG = ‘E’ (error)
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user select Yes,
then display complete log in the view log output.

Selection Criteria:
- PO_TYPE = ‘Internal Orders’
- ERP_PROCESS_FLAG = ‘N’ or NULL
- Use the same logic that use for XXJR: 3PL Main IR Stage Program
- Include Lot Number logic for Lot Controlled Item

INTWMS 7.1
XXJR: Korber Inbound IR
Receipt
Internal Requisition Receipt
INV
Onhand Snapshot Reconciliation

Mapping Document:
Inbound - Interface Export Design
Sheet: Inventory Snapshot Scheduled Daily at 3 AM PST
User Story Domo Onhand Reconciliation Report Multiple Json files might be generated to handle file size
Korber WMS

INTKORBER 1.1
Start Snapshot Inventory
Generated

External – Korber WS
Amazon Web
Services

INTAWS 2.1
Consume and Populate
Interface Table in Data
Mart

External – Korber WS

Expected to be completed at 4 AM PST

Scheduled at 3 AM PST
Data Mart

INTDM 3.2
INTDM 3.1
Scheduled Job in Data Mart tp
KWMS.XXJR_KORBER_IB_INV_
Refresh Onhand Inventory Tables
SNAP Populated
XXJR_W_ONHAND_DETAIL_F

External – Data Mart External – Data Mart

Scheduled at 4 AM PST
Domo

DOMO 4.1
Domo to Create Daily
Reconciliation Report
(Data Set and Visualization)

External – Domo
Oracle ERP

Real-Time Onhand Table

Replication (Setup in AWS)

INV
Onhand Conversion Oracle

Mapping Document:
Inbound - Interface Export Design
Sheet: OH Conversion Oracle
Warehouse

Prepare/ Fix the CSV

Onhand Conversion Upload
Start
and Hand Over to Oracle
Support Team

Manual
Oracle Support

Upload the CSV File to the

Upload Folder

Manual

Displayed in Report
1. ORG_CODE
2. ITEM_NUMBER
4. FROM_SUBINV
5. FROM_LOCATOR
6. TO_SUBINV
7. TO_LOCATOR
8. LOT_NUMBER (If any)
9. UOM
10. QTY
11. REFERENCE (For reconciliation)
12. ERP_PROCESS_QUANTITY
13. ERP_PROCESS_FLAG
14. ERP_PROCESS_MESSAGE
15. FILE_NAME
Staging Table Update for corresponding record 16. CREATED_BY
- ERP_PROCESS_FLAG = ‘E’ 17. CREATION_DATE
- ERP_PROCESS_MESSAGE = Error Message from MTI API 18. REQUEST_ID
- Delete Corresponding Error Records in MTI and MTLI 19. TRANSACTION_HEADER_ID
Key Fields
Interface Tables 20. TRANSACTION_INTERFACE_ID
1. ORG_CODE
21. LAST_UPDATE_DATE
Program Parameters: 2. ITEM_NUMBER
22. LAST_UPDATED_BY
a. File Name: Free Text (Required) 4. FROM_SUBINV
b. Debug Flag: Yes/ No (LOV – Required). 5. FROM_LOCATOR
Oracle ERP

Default with No. If user select Yes, then display 6. TO_SUBINV

complete log in the view log output. 7. TO_LOCATOR
Re-use the interface program 8. LOT_NUMBER (If any)
9. UOM Interface Table Name: Update CSV Output Generated as
XXJR: Korber Inbound Subinv Transfer
10. QTY - MTL_TRANSACTIONS_INTERFACE
XXJR_INV_OH_CONV_SUBTRF View Output for User Review.
11. REFERENCE (For reconciliation) - MTL_TRANSACTION_LOTS_INTERFACE
(For Lot Controlled Items)
INV INV
Fail

Read the CSV File, Perform Simple

Run XXJR: Onhand Conversion –
Template Validation, Insert record INTWMS 8.1
into Staging Table Insert Data to Receiving Interface Status? Staging Table Update for corresponding record
Subinv. Transfer - ERP_PROCESS_FLAG = ‘S’
XXJR_INV_OH_CONV_SUBTRF (XXJR Transaction Interface Table
Schema) - ERP_PROCESS_QUANTITY

INV INV INV

Success
Onhand Increment/
Update Decrement/ Transferred in End
XXJR_INV_OH_CONV_SUBTRF corresponding Subinventory
and Inventory Org.

INV INV
Inventory Adjustment from Korber WMS to Oracle ERP

Mapping Document:
Inbound - Interface Export Design
Sheet: Inventory Adjustment
Korber WMS

INTKORBER 1.1
Start Inventory Adjustment
Generated

External – Korber WS
Amazon Web
Services

INTAWS 2.1
Consume and Populate
Interface Table in Data
Mart

External – Korber WS

INTDM 3.1
Data Mart

XXJR_KORBER_IB_INV_ INTDM 10.1

ADJUSTMENT XXJR_KORBER_IB_INV_
Populated ADJUSTMENT
End
Updated
External – Data Mart
External – Data Mart

- Scheduled Every Hour

- Program Parameters:
a. Korber Wh. Code: (LOV – Optional)
b. Korber Client Code: (LOV – Optional)
c. Item Code: (100 Free Text – Optional). Using comma to separate the Item
Number if user wants to manually process/ re-process specific Items
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If user select
Yes, then system select all records with ERP_PROCESS_FLAG = ‘E’ (error)
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user select Yes,
then display complete log in the view log output.

Selection Criteria:
- ERP_PROCESS_FLAG = ‘N’ or NULL
- Use the same logic that use for XXJR: 3PL Inventory Adjustment Program
- Include Lot Number logic for Lot Controlled Item
- Oracle Lookup to Filter the Korber Transaction Code
XXJR_KORBER_INV_ADJ_TXN_CODE
(XXJR_KORBER_IB_INV_ADJ_T.TRANSACTION_CODE)
Refer to Korber Interface Export Design for details mapping

Inventory Adjustment
INTWMS 5.1
XXJR: Korber Inbound
Inventory Adjustment
- Scheduled Every Hour
INV - Program Parameters:
a. Korber Wh. Code: (LOV – Optional)
b. Korber Client Code: (LOV – Optional) Staging Table Update for corresponding record
c. Item Code: (100 Free Text – Optional). Using comma to separate the Item - ERP_PROCESS_FLAG = ‘E’
Logic Applied to all 3 programs Number if user wants to manually process/ re-process specific Items - ERP_PROCESS_MESSAGE = Error Message from MTI API
- If XXJR_KORBER_IB_INV_ADJ_T.TRANSACTION_CODE e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If user select - Delete Corresponding Error Records in MTI and MTLI Interface
Interface Table Name:
is not exist in lookup Yes, then system select all records with ERP_PROCESS_FLAG = ‘E’ (error) Tables
- MTL_TRANSACTIONS_INTERFACE
XXJR_KORBER_INV_ADJ_TXN_CODE f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user select Yes, - MTL_TRANSACTION_LOTS_INTERFACE (For Lot
XXJR_KORBER_SUB_TRF_TXN_CODE then display complete log in the view log output. Controlled Items)
XXJR_KORBER_WO_COMP_TXN_CODE
Then update ERP_PROCESS_FLAG to ‘X’ Selection Criteria:
- ERP_PROCESS_FLAG = ‘N’ or NULL INTWMS 9.1
- Include Lot Number logic for Lot Controlled Item Update
Oracle ERP

- Oracle Lookup to Filter the Korber Transaction Code

XXJR_KORBER_IB_INV_ADJ
XXJR_KORBER_SUB_TRF_TXN_CODE
_T
(XXJR_KORBER_IB_INV_ADJ_T.TRANSACTION_CODE)
- Staging table hold_code_before <> hold_code_after Error
Refer to Korber Interface Export Design for details mapping
INV
Hold Code Update/
Subinv. Transfer
INTWMS 4.1
Scheduled Program to INTWMS 6.1 INTWMS 8.1
Adjustment
Process Record in Type?
XXJR: Korber Inbound Subinv Insert Data to Receiving Interface Status? Staging Table Update for corresponding record
XXJR_KORBER_IB_INV_ADJ Transfer Transaction Interface Table - ERP_PROCESS_FLAG = ‘S’
_T
INV INV INV

- Scheduled Every Hour Success

INTWMS 9.3
- Program Parameters: INTWMS 9.2
a. Korber Wh. Code: (LOV – Optional)
Onhand Increment/
Update End
b. Korber Client Code: (LOV – Optional) Decrement/ Transferred in
XXJR_KORBER_IB_INV_ADJ
c. Item Code: (100 Free Text – Optional). Using comma to separate the Item corresponding Subinventory
_T
Number if user wants to manually process/ re-process specific Items and Inventory Org.
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If user select INV INV
Yes, then system select all records with ERP_PROCESS_FLAG = ‘E’ (error)
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user select Yes,
then display complete log in the view log output.

- ERP_PROCESS_FLAG = ‘N’ or NULL

- Include Lot Number logic for Lot Controlled Item
Oracle Lookup to Filter the Korber Transaction Code
- XXJR_KORBER_WO_COMP_TXN_CODE
(XXJR_KORBER_IB_INV_ADJ_T.TRANSACTION_CODE)
Refer to Korber Interface Export Design for details mapping

INTWMS 7.1
XXJR: Korber Inbound Work
Order Completion
Work Order Completion
INV
Sales Order Shipment from Korber WMS to Oracle ERP – Trip Verification

XXJR: Korber Inbound Shipping – Trip Verification

Mapping Document:
Inbound - Interface Export Design
Sheet: Shipping (Invoice)
Korber WMS

INTKORBER 1.1
Start Ship Confirm Sales Order
Generated

External – Korber WS
Amazon Web
Services

INTAWS 2.1
Consume and Populate
Interface Table in Data
Mart

External – Korber WS
Data Mart

INTDM 3.1
XXJR_KORBER_IB_SHIPPING_T
Populated

External – Data Mart

Update
- ERP_PROCESS_FLAG = ‘E’
- ERP_PROCESS_MESSAGE= Error Message

INTWMS 6.1.1.1
Handle by
Update
Re-process
XXJR_KORBER_IB_SHIPPING_T
Parameter
Staging Table

Error WMS

INTWMS 6.1.1
Call Create WSH Trip API in Success/ Error?
Oracle Update
- ERP_PROCESS_FLAG = ‘T’
Update
WMS - TRIP_CREATION_FLAG = ‘Y’
- ERP_PROCESS_FLAG = ‘A’
- TRIP_ASSIGN_FLAG = ‘Y’

No
Success
Condition:
- ERP_PROCESS_FLAG = ‘N’ or NULL INTWMS 6.1.1.2
- LOAD_ID is not null Update INTWMS 6.1.3.1
- TRIP_CREATION_FLAG = ‘N’ or NULL XXJR_KORBER_IB_SHIPPING_T
Update
- Program will process the unique Trip Number Staging Table XXJR_KORBER_IB_SHIPPING_T
End
one at the time. If error, mark corresponding Staging Table
records and proceed with next eligible records WMS
WMS
Yes

Success
INTWMS 6.1 LOAD ID / Trip (Process Next Trip Number Creation)
Process Trip Level Record in Number Exist in Match with
the Staging Table Oracle ? Staging Table? Update
- ERP_PROCESS_FLAG = ‘E’
- ERP_PROCESS_MESSAGE = Mismatch Trip Number ….
Oracle ERP

WMS

No
Update
- ERP_PROCESS_FLAG = ‘T’ ORDER_NUMBER – LOAD_ID Yes INTWMS 6.1.3.2 Update
- Program Parameters: Handle by - ERP_PROCESS_FLAG = ‘E’
- TRIP_CREATION_FLAG = ‘Y’ from Staging table with Oracle Update
a. Korber Wh. Code: (LOV – Optional) Re-process - ERP_PROCESS_MESSAGE= Error Message
Delivery – Trip Relationship Match XXJR_KORBER_IB_SHIPPING_T
Parameter
b. Korber Client Code: (LOV – Optional) Staging Table
c. Trip Number: (200 Free Text – Optional). Using comma to
separate the Trip Number that user wants to process or reprocess
by the program Corresponding WMS
INTWMS 6.1.3
Yes

All programs will be grouped into Request Set in the INTWMS 6.1.2 INTWMS 6.1.3.3.1
d. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If Delivery Number Handle by
Select All Delivery Number
Yes

scheduled program. User also can run the program Update Update
user select Yes, then system select all records with Already Assigned Re-process
manually based on the interface pick status movement. XXJR_KORBER_IB_SHIPPING_T (ORDER_NUMBER) for XXJR_KORBER_IB_SHIPPING_T
ERP_PROCESS_FLAG = ‘E’ (error), TRIP_CREATION_FLAG = ‘N’ or to the Trip in Parameter
1. XXJR: Korber Inbound Shipping – Trip Verification Staging Table corresponding LOAD_ID Staging Table
NULL, TRIP_ASSIGN_FLAG = ‘N’ or NULL. Oracle?
2. XXJR: Korber Inbound Shipping – Pick Load
e. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user Yes
3. XXJR: Korber Inbound Shipping – Pick Drop
select Yes, then display complete log in the view log output. WMS WMS WMS (Process the Next LOAD_ID
4. XXJR: Korber Inbound Shipping – Update Shipment Info
Error in the staging Table)
5. XXJR: Korber Inbound Shipping – Assign Freight Cost
6. XXJR: Korber Inbound Shipping – Ship Confirmation No

LOAD_ID = TRIP Number in Oracle

ORDER_NUMBER = Delivery
Number in Oracle INTWMS 6.1.3.3 Next Eligible Trip to be
Assign Delivery Number to Success/ Error? Processed by Trip
Update Verification Program?
Corresponding Trip Number
INTWMS 4.1 - ERP_PROCESS_FLAG = ‘A’
INTWMS 5.1 - TRIP_ASSIGN_FLAG = ‘Y’
Scheduled Program to Process
XXJR: Korber Inbound Has LOAD_ID? Yes
Record in WMS
Shipping – Trip Verification At this point, all records for the same LOAD_ID will have below
XXJR_KORBER_IB_SHIPPING_T
Success - TRIP_CREATION_FLAG = ‘Y’
WMS WMS - TRIP_ASSIGN_FLAG = ‘Y’
INTWMS 6.1.3.3.2 - ERP_PROCESS_FLAG = ‘A’
All Delivery For
Update
Corresponding Trip
XXJR_KORBER_IB_SHIPPING_T
Assigned to Trip?
Staging Table

WMS

No
(Assign Next Delivery Number to Trip)
INTWMS 7.1
XXJR: Korber Inbound Shipping – Pick Load

Yes
No

(Data is ready for Pick Load Process)

Next Status:
Pick Load
Sales Order Shipment from Korber WMS to Oracle ERP – Pick Load

XXJR: Korber Inbound Shipping – Pick Load

Mapping Document:
Inbound - Interface Export Design
Korber WMS

Sheet: Shipping (Invoice)

Amazon Web
Services
Data Mart

Update Corresponding Record

Generic Logic - ERP_PROCESS_FLAG = ‘E’
Populate the Lot Number for Lot Enabled Item during Pick - ERP_PROCESS_MESSAGE= Error Message
Load Process All Lines for the same Delivery Number
If one of the record for corresponding trip or delivery not are Loaded Successfully. Next is to check
eligible for next process, then system will not process it until if all lines loaded or not for the same All Lines for the same Trip and
all records group by either delivery or trip. Trip Number because 1 Trip can have No Delivery are Loaded Successfully.
single or multiple lines for the same or ERP_PROCESS_FLAG = L
Special Logic for records with LOAD_ID Value different Delivery Number LOAD_FLAG = ‘Y’
INTWMS 7.3.1
- All Records passed previous status before eligible for Pick Handle by
Update
- Program Parameters: Load by having below status Re-process
XXJR_KORBER_IB_SHIPPING_T
Parameter
Remaining Line
a. Korber Wh. Code: (LOV – Optional) - TRIP_CREATION_FLAG = ‘Y’
Staging Table for the same
b. Korber Client Code: (LOV – Optional) - TRIP_ASSIGN_FLAG = ‘Y’
- ERP_PROCESS_FLAG = ‘A’ If LPN is not exist, call Create LPN API Trip Number?
c. Trip Number: (200 Free Text – Optional). Using comma to
- LOAD_FLAG = ‘N’ or NULL If LPN_CONTEXT = 4, call Re-Use LPN API
Error WMS
separate the Trip Number that user wants to process or reprocess
No
by the program
d. Delivery Number: (200 Free Text – Optional). Using comma to All Lines for the same LPNs are Loaded
separate the Delivery Number that user wants to process or Successfully. Next is to check if all lines loaded
reprocess by the program or not for the same Delivery Number because Yes
INTWMS 7.2 INTWMS 7.3
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If Select All Records Belong to Perform Pick Load For Every Pick Load by Line 1 delivery can have single or multiple lines for
user select Yes, then system select all records : and LPN the same or different LPNs Load Remaining
the same LOAD_ID or Trip Lines Group by Delivery
For trip, select ERP_PROCESS_FLAG = ‘E’ (error), LPNs for the
TRIP_CREATION_FLAG = ‘Y’, TRIP_ASSIGN_FLAG = ‘Y’, LOAD_FLAG
Number Number and LPNs
= ‘N’ or NULL
same Delivery
For Delivery (without LOAD_ID), select ERP_PROCESS_FLAG = ‘E’ WMS WMS Number ?
(error), LOAD_FLAG = ‘N’ or NULL
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user Success
select Yes, then display complete log in the view log output. Trip Update Corresponding Record No Yes
- ERP_PROCESS_FLAG = ‘L’
- LOAD_FLAG = ‘Y’

INTWMS 7.3.2 Load Remaining

From INTWMS 7.1 Pick Load Update
Next Status: Line for the
Status: Trip XXJR: Korber Inbound Delivery or Trip XXJR_KORBER_IB_SHIPPING_T
Pick Load
Verification Shipping – Pick Load Level? Staging Table same LPN# ?
XXJR: Korber Inbound
WMS Shipping – Pick Load
WMS
Yes

Process Next Line for

corresponding LPN Number

Next Status:
Process Next LPN Line for Pick Drop
corresponding Delivery Number

Process Next Delivery Line for

Oracle ERP

corresponding Trip Number

Update Corresponding Record

- ERP_PROCESS_FLAG = ‘E’
Delivery
- ERP_PROCESS_MESSAGE= Error Message
Generic Logic
Populate the Lot Number for Lot Enabled Item during Pick
Load Process
If one of the record for corresponding trip or delivery not
eligible for next process, then system will not process it until
all records group by either delivery or trip. INTWMS 7.5.1
Handle by
Update
Re-process
Special Logic for records with no LOAD_ID Value XXJR_KORBER_IB_SHIPPING_T
Parameter
- LOAD_ID is NULL Staging Table
- ERP_PROCESS_FLAG = ‘N’
- TRIP_CREATION_FLAG = ‘N’ or NULL WMS No
- TRIP_ASSIGN_FLAG = ‘N’ or NULL
- LOAD_FLAG = ‘N’ or NULL Error
If LPN is not exist, call Create LPN API
All Lines for the same LPNs are Loaded
If LPN_CONTEXT = 4, call Re-Use LPN API
Successfully. Next is to check if all lines loaded
All Lines for the same Delivery Number are
or not for the same Delivery Number because
Loaded Successfully.
1 delivery can have single or multiple lines for
INTWMS 7.5 ERP_PROCESS_FLAG = L
the same or different LPNs
INTWMS 7.4 LOAD_FLAG = ‘Y’
Perform Pick Load For Every Pick Load by Line
Select All Records Belong to Load Remaining
Lines Group by Delivery and LPN ?
the same Delivery Number LPNs for the
Number and LPNs
same Delivery
WMS WMS Number ?
Update Corresponding Record
Success - ERP_PROCESS_FLAG = ‘L’ No Yes
- LOAD_FLAG = ‘Y’

INTWMS 7.5.2 Load Remaining

Update
XXJR_KORBER_IB_SHIPPING_T
Line for the
Staging Table same LPN# ?

WMS
Yes

Process Next Line for

corresponding LPN Number

Process Next LPN Line for

corresponding Delivery Number
Sales Order Shipment from Korber WMS to Oracle ERP – Pick Drop

XXJR: Korber Inbound Shipping – Pick Drop

Mapping Document:
Inbound - Interface Export Design
Korber WMS

Sheet: Shipping (Invoice)

Amazon Web
Services
Data Mart

Update Corresponding Record for the same failed LPN

If one of the record for corresponding trip or delivery not - ERP_PROCESS_FLAG = ‘E’
eligible for next process, then system will not process it until - ERP_PROCESS_MESSAGE= Error Message
all records group by either delivery or trip.

Special Logic for records with LOAD_ID Value

- All Records passed previous status before eligible for Pick
Drop by having below status INTWMS 8.3.1
- TRIP_CREATION_FLAG = ‘Y’ Handle by
Update
- TRIP_ASSIGN_FLAG = ‘Y’ Re-process
XXJR_KORBER_IB_SHIPPING_T
- ERP_PROCESS_FLAG = ‘L’ Parameter
- Program Parameters: Staging Table
a. Korber Wh. Code: (LOV – Optional) - LOAD_FLAG = ‘Y’ or NULL
b. Korber Client Code: (LOV – Optional) - DROP_FLAG = ‘N’ or NULL
Error WMS
c. Trip Number: (200 Free Text – Optional). Using comma to All Lines for the same Delivery Number
separate the Trip Number that user wants to process or reprocess are Drop Successfully. Next is to check if All Lines for the same Trip and
by the program all lines Drop or not for the same Trip No Delivery are Drop Successfully.
d. Delivery Number: (200 Free Text – Optional). Using comma to Number because 1 Trip can have single ERP_PROCESS_FLAG = D
separate the Delivery Number that user wants to process or INTWMS 8.2 INTWMS 8.3 or multiple lines for the same or LOAD_FLAG = ‘Y’
reprocess by the program Select All Records Belong to Perform Pick Drop For Every Pick Drop by LPN different Delivery Number DROP_FLAG = ‘Y’
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If the same LOAD_ID or Trip Lines Group by Delivery Status Drop Remaining
user select Yes, then system select all records : Number Number and LPNs Delivery LPNs
For trip, select ERP_PROCESS_FLAG = ‘E’ (error), for the same
TRIP_CREATION_FLAG = ‘Y’, TRIP_ASSIGN_FLAG = ‘Y’, LOAD_FLAG Trip Number?
WMS WMS
= ‘Y’, DROP_FLAG = ‘N’ or NULL
For Delivery (without LOAD_ID), select ERP_PROCESS_FLAG = ‘E’
(error), LOAD_FLAG = ‘Y’, DROP_FLAG = ‘N’ or NULL Success
Trip Update Corresponding Record for
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user Yes
the same LPN
select Yes, then display complete log in the view log output. - ERP_PROCESS_FLAG = ‘D’ Yes
- DROP_FLAG = ‘Y’

INTWMS 8.3.2 Drop Remaining

From INTWMS 8.1 Pick Drop Update LPN for the
Next Status:
Status: Pick
Pick Drop
XXJR: Korber Inbound Delivery or Trip XXJR_KORBER_IB_SHIPPING_T same Delivery
Load Shipping – Pick Drop Level? Staging Table Number ? INTWMS 9.1
XXJR: Korber Inbound Shipping – Update
WMS WMS Shipment Info

Next Status:
Update
Process Next Drop LPN for Shipment
corresponding Delivery Number Info

Process Next Delivery LPNs for

Oracle ERP

corresponding Trip Number

Delivery
Update Corresponding Record
- ERP_PROCESS_FLAG = ‘E’
If one of the record for corresponding trip or delivery not - ERP_PROCESS_MESSAGE= Error Message
eligible for next process, then system will not process it until
all records group by either delivery or trip.

Special Logic for records with no LOAD_ID Value

- LOAD_ID is NULL
- ERP_PROCESS_FLAG = ‘L’ INTWMS 8.5.1
Handle by
- TRIP_CREATION_FLAG = ‘N’ or NULL Update
Re-process
- TRIP_ASSIGN_FLAG = ‘N’ or NULL XXJR_KORBER_IB_SHIPPING_T
Parameter
- LOAD_FLAG = ‘Y’ or NULL Staging Table No
- DROP_FLAG = ‘N’ or NULL
Error WMS
All Lines for the same Delivery Number are
Drop Successfully.
All Lines for the same LPNs are Loaded ERP_PROCESS_FLAG = L
INTWMS 8.5 Successfully. Next is to check if all lines loaded LOAD_FLAG = ‘Y’
INTWMS 8.4 or not for the same Delivery Number because
Perform Pick Load For Every Pick Load by Line DROP_FLAG = ‘Y’
Select All Records Belong to 1 delivery can have single or multiple lines for Remaining Line
Lines Group by Delivery and LPN ?
the same Delivery Number the same or different LPNs for the same
Number and LPNs
Delivery Number
WMS WMS ?

Success
Update Corresponding Record No Yes
- ERP_PROCESS_FLAG = ‘L’
- LOAD_FLAG = ‘Y’

INTWMS 8.5.2 Remaining Line

Update
XXJR_KORBER_IB_SHIPPING_T
for the same
Staging Table LPN# ?

WMS
Yes

Process Next Line for

corresponding LPN Number

Process Next LPN Line for

corresponding Delivery Number
Sales Order Shipment from Korber WMS to Oracle ERP – Update Shipment Info

XXJR: Korber Inbound Shipping – Update Shipment Info

Mapping Document:
Inbound - Interface Export Design
Korber
WMS

Sheet: Shipping (Invoice)

Amazon Web
Services
Data
Mart

Update Corresponding Record for the failed Delivery Update Delivery Ship Method, DFF, … TBD for more fields
If one of the record for corresponding trip or delivery not - ERP_PROCESS_FLAG = ‘E’
eligible for next process, then system will not process it until TRIP_INFO_FLAG = ‘Y’. No need to update Delivery Ship Method, but
- ERP_PROCESS_MESSAGE= Error Message Update other attributes like freight terms, waybill, etc.
all records group by either delivery or trip.

Special Logic for records with LOAD_ID Value Scenario 1 : Single Delivery have single LPN with single Tracking
- All Records passed previous status before eligible for Number
Update Shipment Info by having below status - Program will update the tracking number to LPN Level, then update
- TRIP_CREATION_FLAG = ‘Y’ the same tracking number to delivery level.
INTWMS 9.3.1 Scenario 2 : Single Delivery have multiple LPNs with different Unique
- TRIP_ASSIGN_FLAG = ‘Y’ Handle by Update Corresponding Record for the failed Delivery
Update Tracking Number
- ERP_PROCESS_FLAG = ‘D’ Re-process - ERP_PROCESS_FLAG = ‘E’
XXJR_KORBER_IB_SHIPPING_T - Program will update unique tracking number to LPN Level, then
- LOAD_FLAG = ‘Y’ Parameter - ERP_PROCESS_MESSAGE= Error Message
Staging Table update only one tracking number to delivery level.
- DROP_FLAG = ‘Y’
Update Trip Ship Method, - Example: Delivery001 have Tracking01 to LPN1, Tracking02 to LPN2,
- TRIP_INFO_FLAG = ‘N’ or Null
- SHIPMENT_INFO_FLAG = ‘N’ or NULL
DFF, … TBD for more fields Error WMS then Tracking01 assign to LPN1, Tracking02 assign to LPN2, then
Tracking01 or Tracking02 assign to Delivery001.

INTWMS 9.4.1
Handle by
INTWMS 9.2 Update
Re-process
XXJR_KORBER_IB_SHIPPING_T
Select All Records Belong to INTWMS 9.3 Parameter
Update Status Staging Table
the same LOAD_ID or Trip Perform Update Trip Info
Number Update Corresponding Record for the same Delivery Error
- Program Parameters: WMS
- TRIP_INFO_FLAG = ‘Y’
a. Korber Wh. Code: (LOV – Optional) WMS WMS - ERP_PROCESS_FLAG = ‘D’ (Still “D” because the All Lines for the same Trip and
b. Korber Client Code: (LOV – Optional) INTWMS 10.1
delivery info has not been successfully updated) Delivery are updated Successfully.
c. Trip Number: (200 Free Text – Optional). Using comma to separate
ERP_PROCESS_FLAG = U XXJR: Korber Inbound Shipping – Assign
the Trip Number that user wants to process or reprocess by the
program Success LOAD_FLAG = ‘Y’ Freight Cost
d. Delivery Number: (200 Free Text – Optional). Using comma to DROP_FLAG = ‘Y’
separate the Delivery Number that user wants to process or reprocess SHIPMENT_INFO_FLAG = ‘Y’
INTWMS 9.4 TRIP_INFO_FLAG = ‘Y’
by the program INTWMS 9.3.2 Perform Update Shipment
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If user Update
select Yes, then system select all records : XXJR_KORBER_IB_SHIPPING_T
Info For Every Unique LPN Update Status Next Status:
Trip and Delivery Number Group
For trip, select ERP_PROCESS_FLAG = ‘E’ (error), TRIP_CREATION_FLAG Staging Table Assign
by Trip Number Update Corresponding Record Freight Cost
= ‘Y’, TRIP_ASSIGN_FLAG = ‘Y’, LOAD_FLAG = ‘Y’ or NULL, DROP_FLAG =
for the same Delivery
‘Y’, SHIPMENT_INFO_FLAG = ‘N’ or NULL WMS WMS - ERP_PROCESS_FLAG = ‘U’
For Delivery (without LOAD_ID), select ERP_PROCESS_FLAG = ‘E’ If one of the record for corresponding trip or delivery not eligible for next - SHIPMENT_INFO_FLAG = ‘Y’ All Lines for the same Delivery are
(error), LOAD_FLAG = ‘Y’ or NULL, DROP_FLAG = ‘Y’, process, then system will not process it until all records group by either No
updated Successfully.
SHIPMENT_INFO_FLAG = ‘N’ or NULL delivery or trip. ERP_PROCESS_FLAG = U
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user Success LOAD_FLAG = ‘Y’
select Yes, then display complete log in the view log output. Special Logic for records with no LOAD_ID Value DROP_FLAG = ‘Y’
- LOAD_ID is NULL Update SHIPMENT_INFO_FLAG = ‘Y’
- ERP_PROCESS_FLAG = ‘D’ INTWMS 9.4.2 Remaining
Update
Oracle ERP

- TRIP_CREATION_FLAG = ‘N’ or NULL Delivery Info for

- TRIP_ASSIGN_FLAG = ‘N’ or NULL XXJR_KORBER_IB_SHIPPING_T
Staging Table the same Trip
INTWMS 9.1 - LOAD_FLAG = ‘Y’
Next Status: Number?
From - DROP_FLAG = ‘Y’
Update XXJR: Korber Inbound Delivery or Trip
Status: Pick - SHIPMENT_INFO_FLAG = ‘N’ or NULL WMS
Drop
Shipment Shipping – Update Shipment Level?
Info Yes
Info Scenario 1 : Single Delivery have single LPN with single Tracking Number
- Program will update the tracking number to LPN Level, then update the
WMS same tracking number to delivery level. Update Next Delivery Info for
Scenario 2 : Single Delivery have multiple LPNs with different Unique corresponding Trip Number
Tracking Number Update Corresponding Record for the failed Delivery
- Program will update unique tracking number to LPN Level, then update - ERP_PROCESS_FLAG = ‘E’
only one tracking number to delivery level. - ERP_PROCESS_MESSAGE= Error Message
- Example: Delivery001 have Tracking01 to LPN1, Tracking02 to LPN2, then
Tracking01 assign to LPN1, Tracking02 assign to LPN2, then Tracking01 or
Tracking02 assign to Delivery001.
Delivery

INTWMS 9.4.1
Handle by
Update
Re-process
XXJR_KORBER_IB_SHIPPING_T
Parameter
Staging Table

Error WMS

INTWMS 9.5
Perform Update Shipment
Update Status
Info For Every Unique LPN
and Delivery Number Update Corresponding Record
for the same Delivery
WMS - ERP_PROCESS_FLAG = ‘U’
- SHIPMENT_INFO_FLAG = ‘Y’

Success

INTWMS 9.4.2
Update
XXJR_KORBER_IB_SHIPPING_T
Staging Table

WMS
Sales Order Shipment from Korber WMS to Oracle ERP – Assign Freight Cost

XXJR: Korber Inbound Shipping – Assign Freight Cost

Mapping Document:
Korber
WMS

Inbound - Interface Export Design

Sheet: Shipping (Invoice)
Amazon Web
Services
Data
Mart

If one of the record for corresponding trip or Check if there is unique freight cost number
delivery not eligible for next process, then system group by trip, delivery or LPN.
Update Corresponding Record for the failed Delivery
will not process it until all records group by either Example:
- ERP_PROCESS_FLAG = ‘E’
delivery or trip. Scenario 1: 1 Trip have 3 deliveries with 3
- ERP_PROCESS_MESSAGE= Error Message
different LPNs and freight cost value is same
Special Logic for records with LOAD_ID Value for all records in this trip. For this case,
- All Records passed previous status before program will assign the freight cost in the
eligible for Assign Freight Cost by having below Trip Level.
status Scenario 2: 1 Trip have 1 deliveries with 3
- TRIP_CREATION_FLAG = ‘Y’ different LPNs and freight cost value is
different for each LPNs on that delivery. For
INTWMS 10.3.1
- TRIP_ASSIGN_FLAG = ‘Y’ Handle by
this case, program will assign the freight Update
- ERP_PROCESS_FLAG = ‘U’ Re-process
cost in the LPN level. XXJR_KORBER_IB_SHIPPING_T
- LOAD_FLAG = ‘Y’ Parameter
Scenario 3: 1 Trip have 1 deliveries with 3 Staging Table
- DROP_FLAG = ‘Y’
- TRIP_INFO_FLAG = ‘Y’ different LPNs and freight cost value is the
- SHIPMENT_INFO_FLAG = ‘Y’ same for all records on that trip, delivery Error WMS
- FREIGHT_COST = ‘N’ or NULL and LPN. For this case, program will assign
the freight cost in the delivery level.

INTWMS 10.2
Select All Records Belong to INTWMS 10.3
Update Status
the same LOAD_ID or Trip Assign Freight Cost
- Program Parameters: Number
Update Corresponding Record for the same Delivery
a. Korber Wh. Code: (LOV – Optional)
b. Korber Client Code: (LOV – Optional) WMS WMS - FREIGHT_COST_FLAG = ‘Y’
- ERP_PROCESS_FLAG = ‘F’
c. Trip Number: (200 Free Text – Optional). Using comma to separate
the Trip Number that user wants to process or reprocess by the
program Success
d. Delivery Number: (200 Free Text – Optional). Using comma to
separate the Delivery Number that user wants to process or reprocess
by the program
INTWMS 10.3.2
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If user
Update
select Yes, then system select all records :
Trip XXJR_KORBER_IB_SHIPPING_T
For trip, select ERP_PROCESS_FLAG = ‘E’ (error), TRIP_CREATION_FLAG
= ‘Y’, TRIP_ASSIGN_FLAG = ‘Y’, LOAD_FLAG = ‘Y’ or NULL, DROP_FLAG = Staging Table
‘Y’, TRIP_INFO = ‘Y’, SHIPMENT_INFO_FLAG = ‘Y’, COST_FLAG = ‘N’ or
Null WMS
For Delivery (without LOAD_ID), select ERP_PROCESS_FLAG = ‘E’ If one of the record for corresponding trip or delivery not eligible for next
(error), LOAD_FLAG = ‘Y’ or NULL, DROP_FLAG = ‘Y’, process, then system will not process it until all records group by either
SHIPMENT_INFO_FLAG = ‘Y’, COST_FLAG = ‘N’ or Null delivery or trip.
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user
select Yes, then display complete log in the view log output. Special Logic for records with no LOAD_ID Value
- LOAD_ID is NULL
- ERP_PROCESS_FLAG = ‘U’ All Lines for the same Trip and
Oracle ERP

- TRIP_CREATION_FLAG = ‘N’ or NULL Delivery are updated Successfully. INTWMS 11.1

- TRIP_ASSIGN_FLAG = ‘N’ or NULL ERP_PROCESS_FLAG = F XXJR: Korber Inbound Shipping –
From
- LOAD_FLAG = ‘Y’ or NULL LOAD_FLAG = ‘Y’
Status: Next Status: INTWMS 10.1 Ship Confirm
Delivery or Trip - DROP_FLAG = ‘Y’ or NULL DROP_FLAG = ‘Y’
Update Assign XXJR: Korber Inbound SHIPMENT_INFO_FLAG = ‘Y’
Shipment Freight Cost Level? - SHIPMENT_INFO_FLAG = ‘Y’
Shipping – Assign Freight Cost TRIP_INFO_FLAG = ‘Y’
Info
Check if there is unique freight cost number group by delivery or LPN. FREIGHT_COST_FLAG = ‘Y’
WMS Example:
Next Status:
Scenario 1: 1 deliveries with 3 different LPNs and freight cost value is Ship
Update Corresponding Record for the failed Delivery
different for each LPNs on that delivery. For this case, program will assign Confirm
- ERP_PROCESS_FLAG = ‘E’
the freight cost in the LPN level. - ERP_PROCESS_MESSAGE= Error Message
Scenario 2: 1 deliveries with 3 different LPNs and freight cost value is the All Lines for the same Delivery are
same for all records on this delivery and LPN. For this case, program will updated Successfully.
assign the freight cost in the delivery level. ERP_PROCESS_FLAG = U
LOAD_FLAG = ‘Y’
Delivery DROP_FLAG = ‘Y’
INTWMS 10.5.1 SHIPMENT_INFO_FLAG = ‘Y’
Handle by FREIGHT_COST_FLAG = ‘Y’
Update
Re-process
XXJR_KORBER_IB_SHIPPING_T
Parameter
Staging Table

Error WMS

INTWMS 10.5
Assign Freight Cost Group by Update Status
Delivery and LPN
Update Corresponding Record
for the same Delivery
WMS - ERP_PROCESS_FLAG = ‘F’
- FREIGHT_COST_FLAG = ‘Y’

Success

INTWMS 10.5.2
Update
XXJR_KORBER_IB_SHIPPING_T
Staging Table

WMS
Sales Order Shipment from Korber WMS to Oracle ERP – Ship Confirmation

XXJR: Korber Inbound Shipping – Ship Confirmation

Mapping Document:
Korber
WMS

Inbound - Interface Export Design

Sheet: Shipping (Invoice)
Amazon Web
Services
Data
Mart

If one of the record for corresponding trip or

delivery not eligible for next process, then system Update Corresponding Record for the failed Trip
will not process it until all records group by either - ERP_PROCESS_FLAG = ‘E’
delivery or trip. - ERP_PROCESS_MESSAGE= Error Message

Special Logic for records with LOAD_ID Value

- All Records passed previous status before
eligible for Ship Confirm by having below status
- TRIP_CREATION_FLAG = ‘Y’
- TRIP_ASSIGN_FLAG = ‘Y’ INTWMS 11.3.1
- ERP_PROCESS_FLAG = ‘F’ Handle by
Update
- LOAD_FLAG = ‘Y’ Re-process
XXJR_KORBER_IB_SHIPPING_T
- DROP_FLAG = ‘Y’ Parameter
Staging Table
- TRIP_INFO_FLAG = ‘Y’
- SHIPMENT_INFO_FLAG = ‘Y’
- FREIGHT_COST_FLAG = ‘Y’ Error WMS
- SHIP_CONFIRM_FLAG = ‘N’ or NULL

INTWMS 11.2
Select All Records Belong to INTWMS 11.3
Update Status
the same LOAD_ID or Trip Call Ship Confirm Trip API
- Program Parameters: Number
Update Corresponding Record for the same Delivery
a. Korber Wh. Code: (LOV – Optional)
b. Korber Client Code: (LOV – Optional) WMS WMS - SHIP_CONFIRM_FLAG= ‘Y’
- ERP_PROCESS_FLAG = ‘S’
c. Trip Number: (200 Free Text – Optional). Using comma to separate
the Trip Number that user wants to process or reprocess by the
program Success
d. Delivery Number: (200 Free Text – Optional). Using comma to
separate the Delivery Number that user wants to process or reprocess
by the program
INTWMS 11.3.2
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If user
Update
select Yes, then system select all records :
Trip XXJR_KORBER_IB_SHIPPING_T
For trip, select ERP_PROCESS_FLAG = ‘E’ (error), TRIP_CREATION_FLAG
= ‘Y’, TRIP_ASSIGN_FLAG = ‘Y’, LOAD_FLAG = ‘Y’ or NULL, DROP_FLAG = Staging Table
‘Y’, TRIP_INFO = ‘Y’, SHIPMENT_INFO_FLAG = ‘Y’, COST_FLAG = ‘Y’, SHIP
For Delivery (without LOAD_ID), select ERP_PROCESS_FLAG = ‘E’ WMS
(error), LOAD_FLAG = ‘Y’ or NULL, DROP_FLAG = ‘Y’,
SHIPMENT_INFO_FLAG = ‘Y’, FREIGHT_COST_FLAG = ‘Y’,
SHIP_CONFIRM_FLAG = ‘N’ or NULL
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user
select Yes, then display complete log in the view log output.

All Lines for the same Trip and

Oracle ERP

Delivery are updated Successfully.

ERP_PROCESS_FLAG = S
LOAD_FLAG = ‘Y’
From INTWMS 11.1
Next Status: DROP_FLAG = ‘Y’
Status: Delivery or Trip
Ship XXJR: Korber Inbound SHIPMENT_INFO_FLAG = ‘Y’
Assign
Confirm Level? If one of the record for corresponding trip or delivery not eligible for next TRIP_INFO_FLAG = ‘Y’
Freight Cost Shipping – Ship Confirm
process, then system will not process it until all records group by either FREIGHT_COST_FLAG = ‘Y’
delivery or trip. SHIP_CONFIRM_FLAG = ‘Y’
WMS
Special Logic for records with no LOAD_ID Value
End
- LOAD_ID is NULL Update Corresponding Record for the failed Delivery
- ERP_PROCESS_FLAG = ‘F’ - ERP_PROCESS_FLAG = ‘E’
- TRIP_CREATION_FLAG = ‘N’ or NULL - ERP_PROCESS_MESSAGE= Error Message All Lines for the same Delivery are
- TRIP_ASSIGN_FLAG = ‘N’ or NULL updated Successfully.
- LOAD_FLAG = ‘Y’ or NULL ERP_PROCESS_FLAG = U
- DROP_FLAG = ‘Y’ or NULL LOAD_FLAG = ‘Y’
Delivery - SHIPMENT_INFO_FLAG = ‘Y’ DROP_FLAG = ‘Y’
- FREIGHT_COST_FLAG = ‘Y’ SHIPMENT_INFO_FLAG = ‘Y’
- SHIP_CONFIRM_FLAG = ‘N’ or NULL INTWMS 11.5.1 FREIGHT_COST_FLAG = ‘Y’
Handle by
Update SHIP_CONFIRM_FLAG = ‘Y’
Re-process
XXJR_KORBER_IB_SHIPPING_T
Parameter
Staging Table

Error WMS

INTWMS 11.5
Call Ship Confirm Trip Update Status
Delivery
Update Corresponding Record
for the same Delivery
WMS - ERP_PROCESS_FLAG = ‘S’
- SHIP_CONFIRM_FLAG = ‘Y’

Success

INTWMS 11.5.2
Update
XXJR_KORBER_IB_SHIPPING_T
Staging Table

WMS
Sales Order Shipment from Korber WMS to Oracle ERP
Korber WMS

INTKORBER 1.1
Start Ship Confirm Sales Order
Generated

External – Korber WS
Amazon Web
Services

INTAWS 2.1
Consume and Populate
Interface Table in Data
Mart

External – Korber WS
Data Mart

INTDM 3.1
XXJR_KORBER_IB_SHIPPING_T
Populated

External – Data Mart

Update
- ERP_PROCESS_FLAG = ‘E’
- ERP_PROCESS_MESSAGE= Error Message

INTWMS 6.1.1.1
Handle by
Update
Re-process
XXJR_KORBER_IB_SHIPPING_T
Parameter
Staging Table

Error WMS

INTWMS 6.1.1
Call Create WSH Trip API in Success/ Error?
Oracle Update
- ERP_PROCESS_FLAG = ‘T’
Update
WMS - TRIP_CREATION_FLAG = ‘Y’
- ERP_PROCESS_FLAG = ‘A’
- TRIP_ASSIGN_FLAG = ‘Y’ FILE_NAME

No
Condition:
Success CREATION_DATE
- ERP_PROCESS_FLAG = ‘N’ or NULL INTWMS 6.1.1.2 CREATED_BY
- LOAD_ID is not null Update INTWMS 6.1.3.1
- TRIP_CREATION_FLAG = ‘N’ or NULL XXJR_KORBER_IB_SHIPPING_T
Update ERP_PROCESS_FLAG
- Program will process the unique Trip Number Staging Table End
one at the time. If error, mark corresponding
XXJR_KORBER_IB_SHIPPING_T LAST_UPDATE_DATE
Staging Table
records and proceed with next eligible records WMS LAST_UPDATED_BY
WMS REQUEST_ID
Yes
ERP_PROCESS_MESSAGE
Success
INTWMS 6.1 LOAD ID / Trip (Process Next Trip Number Creation) ERP_PROCESS_DATE
Process Trip Level Record in Number Exist in Match with ERP_PROCESS_QUANTITY
the Staging Table Oracle ? Staging Table? Update
- ERP_PROCESS_FLAG = ‘E’ MOVE_ORDER_LINE_ID
- ERP_PROCESS_MESSAGE = Mismatch Trip Number ….
WMS TRANSACTION_TEMP_ID
LOAD_FLAG
No
Update
DROP_FLAG
ORDER_NUMBER – LOAD_ID INTWMS 6.1.3.2 Update
- Program Parameters:
- ERP_PROCESS_FLAG = ‘T’
from Staging table with Oracle
Yes
Update
Handle by - ERP_PROCESS_FLAG = ‘E’ COST_FLAG
- TRIP_CREATION_FLAG = ‘Y’ Re-process
a. Korber Wh. Code: (LOV – Optional)
b. Korber Client Code: (LOV – Optional)
Delivery – Trip Relationship Match XXJR_KORBER_IB_SHIPPING_T
Parameter
- ERP_PROCESS_MESSAGE= Error Message SHIPCONFIRM_FLAG
Staging Table
c. Trip Number: (200 Free Text – Optional). Using comma to TRIP_NUMBER
separate the Trip Number that user wants to process or reprocess
by the program INTWMS 6.1.3 Corresponding WMS TRIP_ID
Yes

All programs will be grouped into Request Set in the INTWMS 6.1.2 INTWMS 6.1.3.3.1
d. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If Delivery Number Handle by
Select All Delivery Number ASN_FLAG
Yes

scheduled program. User also can run the program Update Update
user select Yes, then system select all records with Already Assigned Re-process
manually based on the interface pick status movement. XXJR_KORBER_IB_SHIPPING_T (ORDER_NUMBER) for XXJR_KORBER_IB_SHIPPING_T
1. XXJR: Korber Inbound Shipping – Trip Verification
ERP_PROCESS_FLAG = ‘E’ (error), TRIP_CREATION_FLAG = ‘N’ or
Staging Table corresponding LOAD_ID
to the Trip in
Oracle?
Staging Table
Parameter
DERIVED_CUST_PO_NUMBER
NULL, TRIP_ASSIGN_FLAG = ‘N’ or NULL.
2. XXJR: Korber Inbound Shipping – Pick Load
3. XXJR: Korber Inbound Shipping – Pick Drop
e. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user
WMS WMS
Yes ORDER_SOURCE_ID
select Yes, then display complete log in the view log output. WMS (Process the Next LOAD_ID
4. XXJR: Korber Inbound Shipping – Update Shipment Info
Error in the staging Table)
5. XXJR: Korber Inbound Shipping – Assign Freight Cost
6. XXJR: Korber Inbound Shipping – Ship Confirmation No

LOAD_ID = TRIP Number in Oracle

ORDER_NUMBER = Delivery
Number in Oracle INTWMS 6.1.3.3 Next Eligible Trip to be
Assign Delivery Number to Success/ Error? Processed by Trip
Update Verification Program?
Corresponding Trip Number
INTWMS 4.1 - ERP_PROCESS_FLAG = ‘A’
INTWMS 5.1 - TRIP_ASSIGN_FLAG = ‘Y’
Scheduled Program to Process
XXJR: Korber Inbound Has LOAD_ID? Yes
Record in WMS
Shipping – Trip Verification
XXJR_KORBER_IB_SHIPPING_T
Success
At this point, all records for the same LOAD_ID will have below TRIP_CREATION_FLAGTRI
- TRIP_CREATION_FLAG = ‘Y’
WMS WMS - TRIP_ASSIGN_FLAG = ‘Y’ P_ASSIGN_FLAGLOAD_FL
INTWMS 6.1.3.3.2 - ERP_PROCESS_FLAG = ‘A’ AGDROP_FLAGCOST_FLA
All Delivery For
Update
Corresponding Trip GSHIP_CONFIRM_FLAG
XXJR_KORBER_IB_SHIPPING_T
Assigned to Trip?
Staging Table

WMS

No
(Assign Next Delivery Number to Trip)

Yes
(Data is ready for Pick Load Process)

Update Corresponding Record

Generic Logic - ERP_PROCESS_FLAG = ‘E’
Populate the Lot Number for Lot Enabled Item during Pick - ERP_PROCESS_MESSAGE= Error Message
Load Process All Lines for the same Delivery Number
If one of the record for corresponding trip or delivery not are Loaded Successfully. Next is to check
eligible for next process, then system will not process it until if all lines loaded or not for the same All Lines for the same Trip and
all records group by either delivery or trip. Trip Number because 1 Trip can have No Delivery are Loaded Successfully.
single or multiple lines for the same or ERP_PROCESS_FLAG = L
Special Logic for records with LOAD_ID Value different Delivery Number LOAD_FLAG = ‘Y’
INTWMS 7.3.1
No

- All Records passed previous status before eligible for Pick Handle by
Update
- Program Parameters: Load by having below status Re-process
XXJR_KORBER_IB_SHIPPING_T
Parameter
Remaining Line Update Corresponding Record for the same failed LPN
a. Korber Wh. Code: (LOV – Optional) - TRIP_CREATION_FLAG = ‘Y’
Staging Table for the same - ERP_PROCESS_FLAG = ‘E’
b. Korber Client Code: (LOV – Optional) - TRIP_ASSIGN_FLAG = ‘Y’ If one of the record for corresponding trip or delivery not
- ERP_PROCESS_FLAG = ‘A’ Trip Number? - ERP_PROCESS_MESSAGE= Error Message
c. Trip Number: (200 Free Text – Optional). Using comma to If LPN is not exist, call Create LPN API eligible for next process, then system will not process it until
- LOAD_FLAG = ‘N’ or NULL If LPN_CONTEXT = 4, call Re-Use LPN API
Error WMS
separate the Trip Number that user wants to process or reprocess all records group by either delivery or trip.
No
by the program
d. Delivery Number: (200 Free Text – Optional). Using comma to All Lines for the same LPNs are Loaded Special Logic for records with LOAD_ID Value
Generic Logic
Oracle ERP

separate the Delivery Number that user wants to process or Successfully. Next is to check if all lines loaded - All Records passed previous status before eligible for Pick
reprocess by the program or not for the same Delivery Number because Yes If one of the record for corresponding trip or delivery not eligible for next
INTWMS 7.2 INTWMS 7.3 Load by having below status INTWMS 8.3.1
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If 1 delivery can have single or multiple lines for - TRIP_CREATION_FLAG = ‘Y’ Handle by process, then system will not process it until all records group by either
Select All Records Belong to Perform Pick Load For Every Pick Load by Line Update delivery or trip – delivery are in the same process message.
user select Yes, then system select all records : the same or different LPNs Load Remaining - TRIP_ASSIGN_FLAG = ‘Y’ Re-process
the same LOAD_ID or Trip Lines Group by Delivery and LPN XXJR_KORBER_IB_SHIPPING_T
For trip, select ERP_PROCESS_FLAG = ‘E’ (error), - ERP_PROCESS_FLAG = ‘L’ Parameter
Number Number and LPNs LPNs for the - Program Parameters: Staging Table Update Corresponding Record for the failed Delivery Special Logic for records with LOAD_ID Value
TRIP_CREATION_FLAG = ‘Y’, TRIP_ASSIGN_FLAG = ‘Y’, LOAD_FLAG - LOAD_FLAG = ‘Y’ or NULL
= ‘N’ or NULL
same Delivery a. Korber Wh. Code: (LOV – Optional) If one of the record for corresponding trip or delivery not - ERP_PROCESS_FLAG = ‘E’ - All Records passed previous status before eligible for Pick Load by having Update
b. Korber Client Code: (LOV – Optional) - DROP_FLAG = ‘N’ or NULL - ERP_PROCESS_FLAG = ‘E’
WMS WMS Number ? Error WMS eligible for next process, then system will not process it until - ERP_PROCESS_MESSAGE= Error Message below status
For Delivery (without LOAD_ID), select ERP_PROCESS_FLAG = ‘E’ All Lines for the same Delivery Number
c. Trip Number: (200 Free Text – Optional). Using comma to all records group by either delivery or trip. - TRIP_CREATION_FLAG = ‘Y’ - ERP_PROCESS_MESSAGE= Error Message
(error), LOAD_FLAG = ‘N’ or NULL are Drop Successfully. Next is to check if
separate the Trip Number that user wants to process or reprocess All Lines for the same Trip and - TRIP_ASSIGN_FLAG = ‘Y’
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user Success all lines Drop or not for the same Trip
Trip No by the program No Delivery are Drop Successfully. Special Logic for records with LOAD_ID Value - ERP_PROCESS_FLAG = ‘D’
select Yes, then display complete log in the view log output. Update Corresponding Record Yes Number because 1 Trip can have single
d. Delivery Number: (200 Free Text – Optional). Using comma to ERP_PROCESS_FLAG = D - All Records passed previous status before eligible for Pick - LOAD_FLAG = ‘Y’
- ERP_PROCESS_FLAG = ‘L’ separate the Delivery Number that user wants to process or INTWMS 8.2 INTWMS 8.3 or multiple lines for the same or LOAD_FLAG = ‘Y’ Load by having below status All Lines for the same Trip and - DROP_FLAG = ‘Y’
- LOAD_FLAG = ‘Y’ different Delivery Number
reprocess by the program Select All Records Belong to Perform Pick Drop For Every Pick Drop by LPN DROP_FLAG = ‘Y’ - TRIP_CREATION_FLAG = ‘Y’ INTWMS 9.3.1 Delivery are updated Successfully. - SHIPMENT_INFO_FLAG = ‘N’ or NULL INTWMS 8.2.1
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If Drop Remaining - Program Parameters: Handle by
the same LOAD_ID or Trip Lines Group by Delivery Status - TRIP_ASSIGN_FLAG = ‘Y’ Update ERP_PROCESS_FLAG = U Handle by
a. Korber Wh. Code: (LOV – Optional) Re-process Update
user select Yes, then system select all records : Number Number and LPNs Delivery LPNs - ERP_PROCESS_FLAG = ‘L’ XXJR_KORBER_IB_SHIPPING_T LOAD_FLAG = ‘Y’ Special Logic for records with no LOAD_ID Value Re-process
b. Korber Client Code: (LOV – Optional) Parameter XXJR_KORBER_IB_SHIPPING_T
INTWMS 7.3.2 For trip, select ERP_PROCESS_FLAG = ‘E’ (error), for the same - LOAD_FLAG = ‘Y’ or NULL Staging Table DROP_FLAG = ‘Y’ - LOAD_ID is NULL Parameter
INTWMS 7.1 Pick Load Load Remaining TRIP_CREATION_FLAG = ‘Y’, TRIP_ASSIGN_FLAG = ‘Y’, LOAD_FLAG c. Trip Number: (200 Free Text – Optional). Using comma to separate Staging Table
Next Status: Update WMS WMS Trip Number? - DROP_FLAG = ‘Y’ or NULL SHIPMENT_INFO_FLAG = ‘Y’ - ERP_PROCESS_FLAG = ‘D’
XXJR: Korber Inbound Delivery or Trip XXJR_KORBER_IB_SHIPPING_T
Line for the = ‘Y’, DROP_FLAG = ‘N’ or NULL the Trip Number that user wants to process or reprocess by the - LOAD_FLAG = ‘Y’
Pick Load - SHIPMENT_INFO_FLAG = ‘N’ or NULL Error WMS Error WMS
Shipping – Pick Load Level? Staging Table same LPN# ? For Delivery (without LOAD_ID), select ERP_PROCESS_FLAG = ‘E’ program - DROP_FLAG = ‘Y’
(error), LOAD_FLAG = ‘Y’, DROP_FLAG = ‘N’ or NULL Success d. Delivery Number: (200 Free Text – Optional). Using comma to - SHIPMENT_INFO_FLAG = ‘N’ or NULL
Trip Update Corresponding Record for
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user Yes separate the Delivery Number that user wants to process or reprocess
WMS the same LPN
WMS select Yes, then display complete log in the view log output. Yes by the program
Yes - ERP_PROCESS_FLAG = ‘D’ INTWMS 9.3 INTWMS 9.3
e. Re-process Flag: Yes/ No (LOV – Optional). Default with No. If user INTWMS 9.2 Remaining Line
- DROP_FLAG = ‘Y’ Perform Update Shipment Perform Update Shipment
select Yes, then system select all records :
Select All Records Belong to for the same INTWMS 8.2
Process Next Line for For trip, select ERP_PROCESS_FLAG = ‘E’ (error), TRIP_CREATION_FLAG Info For Every Unique Info For Every Unique Update Status
corresponding LPN Number = ‘Y’, TRIP_ASSIGN_FLAG = ‘Y’, LOAD_FLAG = ‘Y’ or NULL, DROP_FLAG =
the same LOAD_ID or Trip Delivery Number Update Shipment Info by Trip/ Delivery
Drop Remaining Delivery Number Group by Delivery Number Group by Success/ Error?
INTWMS 8.3.2 ‘Y’, SHIPMENT_INFO_FLAG = ‘N’ or NULL Number ? Delivery Number or Trip Level? Update
INTWMS 8.1 Pick Drop Update LPN for the Trip Number Trip Number - ERP_PROCESS_FLAG = ‘D’
Next Status: For Delivery (without LOAD_ID), select ERP_PROCESS_FLAG = ‘E’ Update Corresponding Record Number (ORDER_NUMBER)
Pick Drop
XXJR: Korber Inbound Delivery or Trip XXJR_KORBER_IB_SHIPPING_T same Delivery WMS WMS WMS - SHIPMENT_INFO_FLAG = ‘Y’
Process Next LPN Line for (error), LOAD_FLAG = ‘Y’ or NULL, DROP_FLAG = ‘Y’, for the same Delivery Yes
Shipping – Pick Drop Level? Staging Table Number ? SHIPMENT_INFO_FLAG = ‘N’ or NULL
corresponding Delivery Number - ERP_PROCESS_FLAG = ‘U’ No WMS
f. Debug Flag: Yes/ No (LOV – Optional). Default with No. If user Trip - SHIPMENT_INFO_FLAG = ‘Y’
WMS WMS select Yes, then display complete log in the view log output. Success
Process Next Delivery Line for Trip Level = Record with LOAD_ID value Success
corresponding Trip Number Delivery Level = Record without LOAD_ID All Lines For
Update INTWMS 8.2.2
INTWMS 8.3.2 value Corresponding Trip or
Remaining Update
Delivery Number have
Update XXJR_KORBER_IB_SHIPPING_T
Update Corresponding Record Next Status: INTWMS 9.1 Delivery for the ERP_PROCESS_FLAG =
Pick Drop XXJR_KORBER_IB_SHIPPING_T Staging Table
- ERP_PROCESS_FLAG = ‘E’ Update XXJR: Korber Inbound Staging Table same Trip D?
Delivery Delivery or Trip
- ERP_PROCESS_MESSAGE= Error Message Process Next Drop LPN for Shipment Shipping – Update Shipment Number?
Info Level? WMS
Generic Logic corresponding Delivery Number Info WMS
Populate the Lot Number for Lot Enabled Item during Pick Yes
Load Process WMS
If one of the record for corresponding trip or delivery not Process Next Delivery LPNs for
eligible for next process, then system will not process it until corresponding Trip Number
Process Next Delivery for
all records group by either delivery or trip. INTWMS 7.5.1
Handle by corresponding Trip Number
Update
Re-process
Special Logic for records with no LOAD_ID Value XXJR_KORBER_IB_SHIPPING_T
Parameter
- LOAD_ID is NULL Staging Table
- ERP_PROCESS_FLAG = ‘N’ Delivery
Update Corresponding Record
- TRIP_CREATION_FLAG = ‘N’ or NULL WMS No - ERP_PROCESS_FLAG = ‘E’
- TRIP_ASSIGN_FLAG = ‘N’ or NULL If one of the record for corresponding trip or delivery not - ERP_PROCESS_MESSAGE= Error Message No
- LOAD_FLAG = ‘N’ or NULL Error eligible for next process, then system will not process it until (Process Next Line for corresponding
If LPN is not exist, call Create LPN API
All Lines for the same LPNs are Loaded all records group by either delivery or trip.
If LPN_CONTEXT = 4, call Re-Use LPN API Trip Number or Delivery Number)
Successfully. Next is to check if all lines loaded
All Lines for the same Delivery Number are
or not for the same Delivery Number because Special Logic for records with no LOAD_ID Value
Loaded Successfully.
1 delivery can have single or multiple lines for - LOAD_ID is NULL
INTWMS 7.5 ERP_PROCESS_FLAG = L
the same or different LPNs - ERP_PROCESS_FLAG = ‘N’ INTWMS 8.5.1
INTWMS 7.4 LOAD_FLAG = ‘Y’ Handle by
Perform Pick Load For Every Pick Load by Line - TRIP_CREATION_FLAG = ‘N’ or NULL Update
Select All Records Belong to Load Remaining Re-process Delivery
Lines Group by Delivery and LPN ? - TRIP_ASSIGN_FLAG = ‘N’ or NULL XXJR_KORBER_IB_SHIPPING_T
the same Delivery Number LPNs for the Parameter
Number and LPNs - LOAD_FLAG = ‘Y’ or NULL Staging Table No
same Delivery - DROP_FLAG = ‘N’ or NULL
WMS WMS Number ? Error WMS
Update Corresponding Record All Lines for the same Delivery Number are
Success - ERP_PROCESS_FLAG = ‘L’ No Drop Successfully.
- LOAD_FLAG = ‘Y’ Yes All Lines for the same LPNs are Loaded ERP_PROCESS_FLAG = L
INTWMS 8.5 Successfully. Next is to check if all lines loaded LOAD_FLAG = ‘Y’
INTWMS 8.4 or not for the same Delivery Number because
Perform Pick Load For Every Pick Load by Line DROP_FLAG = ‘Y’
Select All Records Belong to 1 delivery can have single or multiple lines for Remaining Line
Lines Group by Delivery and LPN ?
the same Delivery Number the same or different LPNs for the same
Number and LPNs
INTWMS 7.5.2 Load Remaining Delivery Number
Update WMS WMS ?
XXJR_KORBER_IB_SHIPPING_T
Line for the
Staging Table same LPN# ?
Success
Update Corresponding Record No Yes
WMS - ERP_PROCESS_FLAG = ‘L’
Yes - LOAD_FLAG = ‘Y’

Process Next Line for

corresponding LPN Number
INTWMS 8.5.2 Remaining Line
Update
XXJR_KORBER_IB_SHIPPING_T
for the same
Process Next LPN Line for
Staging Table LPN# ?
corresponding Delivery Number

WMS
Yes

Process Next Line for

corresponding LPN Number

Process Next LPN Line for

corresponding Delivery Number
 ▪ Mom/ Pop Stores
▪ Total Brand Development ▪ Discount Stores (Ross, T.J.
Scheduled Order by Customer (TBD) Ship to Canada Maxx, Winners, …)
Demand Class Priority Key Accounts
▪ Finish Line ▪ Sell by Case
Reservation Run for next 4 weeks ▪ DSG
▪ ...
order Priority ▪ Academy
▪ Hibbett
▪ Nike Banner (Nike.com, Nike
Factory, Employee, In-line) Value Channel
Parcel (Take All Inventory)
SO Created, Booked,
Customer/
Scheduled and
Order Profile?
Reserved Mid Tiers
▪ Big 5
Oracle – OM ▪ Dunham ▪ Sport Expert
▪ Finish Line ▪ Sporting Life
Oracle Sales Order

▪ ... ▪ Canadian Tire (CA)

▪ Required Pre-ASN

Forzani Group Ltd.

(FGL Sports Ltd.)
Integration
Korber WMS
Item Master Integration

WMS-003:
WMS-003: Pick and Ship
Pick and Ship to Vending End
User assign OB LPNs to a to Vending Machine
different OB Load Machine
OWMS – Packer/ Shipper

No

Confirm Scanned
WMS 1.1 WMS 1.2
Start OBLPN# to a
Scan Load# Scan OBLPN# New OB Load#?

OWMS - RF OWMS - RF
Yes

WMS 1.3
OBLPNs assigned to
Scanned Load#

OWMS
Data Mart
Amazon Web Services
Korber WMS