MD050 APPLICATION INTERFACE FUNCTIONAL DESIGN

SUBMITTED FOR

Oracle Fusion Integration with Oracle X Store

Author: Raya for international Services

Creation Date: December 16, 2019
Last Updated:
Document Ref: 613144268.docx
Version: 1.0

Approvals
MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Document Control

Change Record
4

Date Author Version Change Reference

28 OCT 2019 1.0 No Previous Document

Reviewers

Name Position

Distribution

Copy No. Name Location

1
2
3
4

Note To Holders:

If you receive an electronic copy of this document and print it out, please
write your name on the equivalent of the cover page, for document
control purposes.

If you receive a hard copy of this document, please write your name on
the front cover, for document control purposes.

3. WMS Integration with Fusion Inventory 2iilxx67ii

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Contents

Document Control..........................................................................................ii

Introduction.....................................................................................................1
Purpose.......................................................................................................1
1. X Store Integration with Fusion Financials.....................................2
1.1 Sales Transaction...........................................................................3
1.1.1 Process Description.......................................................................3
1.1.2 Data Mapping Requirements......................................................3
1.1.3 Business Rules...............................................................................4
1.1.4 Journal Entries;..............................................................................4
1.1.5 Assumptions..................................................................................5
1.1.6 Application Setup Requirements................................................5
1.2 Return Transaction:......................................................................6
1.2.1 Process Description.......................................................................6
1.2.2 Data Mapping Requirements......................................................6
Credit Memo..............................................................................................6
Refund........................................................................................................7
1.2.3 Business Rules...............................................................................7
1.2.4 Journal Entries...............................................................................7
1.2.5 Assumptions..................................................................................8
1.2.6 Application Setup Requirements................................................8
1.3 Sales Exchange...............................................................................9
1.3.1 Process Description.......................................................................9
1.3.2 Data Mapping Requirements....................................................10
1.3.3 Business Rules.............................................................................10
1.3.4 Journal Entries.............................................................................10
1.3.5 Assumptions................................................................................12
1.3.6 Application Setup Requirements..............................................12
1.4 Receivables Receipt.....................................................................13
1.4.1 Process Description.....................................................................13
1.4.2 Data Mapping Requirements....................................................13
1.4.3 Business Rules.............................................................................13
1.4.4 Journal Entries.............................................................................14
1.4.5 Assumptions................................................................................18
1.4.6 Application Setup Requirements..............................................18
1.5 Foreign currency:........................................................................19

3. WMS Integration with Fusion Inventory 2iiilxx67iii

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1.5.1 Process Description.....................................................................19

1.5.2 Data Mapping Requirements....................................................19
1.5.3 Business Rules.............................................................................19
1.5.4 Assumptions................................................................................20
1.5.5 Application Setup Requirements..............................................20
1.6 E-Commerce................................................................................21
1.6.1 Process Description.....................................................................21
1.6.2 Data Mapping Requirements....................................................21
Invoices.....................................................................................................21
Receipts.....................................................................................................22
1.6.3 Business Rules.............................................................................22
1.6.4 Journal Entries.............................................................................23
1.6.5 Assumptions................................................................................24
1.6.6 Application Setup Requirements..............................................24
1.7 Bank Transfer...............................................................................25
1.7.1 Process Description.....................................................................25
1.7.2 Data Mapping Requirements....................................................25
1.7.3 Business Rules.............................................................................25
1.7.4 Journal Entries.............................................................................26
1.7.5 Assumptions................................................................................26
1.7.6 Application Setup Requirements..............................................26
2. X Store Integration with Fusion Inventory...........................................27
2.1 Item Master Synchronization....................................................28
2.1.1Process Description.........................................................................28
2.1.2Data Mapping Requirements........................................................28
2.1.3Business Rules.................................................................................29
2.1.4Assumptions....................................................................................29
2.1.5Application Setup Requirements..................................................29
2.2 Quantity Synchronization................................................................30
2.2.1. Process Description.......................................................................30
Misc. transaction directly created in Fusion.......................................30
Physical Inventory (adjustment)...........................................................30
2.2.2Data Mapping Requirements........................................................30
2.2.3 Business Rules.............................................................................31
2.2.4 Assumptions...................................................................................31
2.2.5 Application Setup Requirements.................................................31
2.3 Receive Goods in X store.................................................................32
2.3.1. Process Description.......................................................................32
2.3.2 Data Mapping Requirements.......................................................32
2.3.3 Business Rules.............................................................................33
2.3.4 Assumptions................................................................................33
2.3.5 Application Setup Requirements..............................................33
2.4 Purchase Order Return.....................................................................34
2.4.1. Process Description.......................................................................34
2.4.2 Data Mapping Requirements....................................................34
2.4.3 Business Rules.............................................................................35
2.4.4 Assumptions................................................................................35

3. WMS Integration with Fusion Inventory 2ivlxx67iv

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.4.5 Application Setup Requirements..............................................35

2.5 Transfer Between stores (Inter-Organization Transfer)..............36
2.5.1. Process Description.......................................................................36
2.5.2 Data Mapping Requirements....................................................36
2.5.3 Business Rules.............................................................................37
2.5.4 Assumptions................................................................................37
1.5.5 Application Setup Requirements.................................................37
2.6 Transfer Material from main warehouse to stores (IMT)............38
2.6.1. Process Description.......................................................................38
2.6.2 Data Mapping Requirements....................................................38
2.6.3 Business Rules.............................................................................39
2.6.4 Assumptions................................................................................39
2.6.5 Application Setup Requirements..............................................39
2.7 Return from stores to main warehouse (inter organization transfer)
....................................................................................................................40
2.7.1. Process Description.......................................................................40
2.7.2 Data Mapping Requirements....................................................40
2.7.3 Business Rules.............................................................................41
2.7.4 Assumptions................................................................................41
2.7.5 Application Setup Requirements..............................................41
2.8 Sales Transaction...............................................................................42
2.8.1. Process Description.......................................................................42
2.8.2 Data Mapping Requirements....................................................42
Business Rules.........................................................................................43
2.8.2 Assumptions...................................................................................43
2.8.3 Application Setup Requirements..............................................43
2.9 Sales Return Transaction..................................................................44
2.9.1. Process Description.......................................................................44
2.9.2 Data Mapping Requirements....................................................44
Business Rules.........................................................................................45
2.9.3 Assumptions................................................................................45
2.9.4 Application Setup Requirements..............................................45
2.10 isolating damaged Items (sub inventory Transfer)....................46
2.10.1. Process Description.....................................................................46
Sub inventory transfer............................................................................46
2.10.2Data Mapping Requirements......................................................46
2.10.3 Business Rules............................................................................47
2.10.4 Assumptions...............................................................................47
2.10.5 Application Setup Requirements...............................................47
2.11 Gift and adjustment Transaction..................................................48
2.11.1. Process Description.....................................................................48
2.11.2 Data Mapping Requirements...................................................48
Business Rule...........................................................................................49
2.11.3 Assumptions...............................................................................49
2.11.4 Application Setup Requirements............................................49
2.12 Issue items to Laundry Transaction.............................................50
2.12.1. Process Description.....................................................................50
2.12.2 Data Mapping Requirements...................................................50

3. WMS Integration with Fusion Inventory 2vlxx67v

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Business Rule...........................................................................................51
2.12.3 Assumptions...............................................................................51
2.12.4 Application Setup Requirements............................................51
2.13 Receipt items From Laundry Transaction...................................52
2.13.1. Process Description.....................................................................52
2.13.2 Data Mapping Requirements...................................................52
Business Rule...........................................................................................53
2.13.3 Assumptions...............................................................................53
2.13.4 Application Setup Requirements............................................53
2.14 Ship sales orders from stores.........................................................54
2.14.1. Process Description.....................................................................54
2.14.2 Data Mapping Requirements...................................................54
2.14.3 Business Rule..............................................................................54
2.14.4 Assumptions.................................................................................54
2.14.5 Application Setup Requirements............................................55
3. WMS Integration with Fusion Inventory..............................................56
3.1 Receive goods In WMS...............................................................57
3.1.1 Process Description........................................................................57
3.1.2 Data Mapping Requirements.......................................................57
3.1.3 Business Rules................................................................................58
3.1.4 Assumptions................................................................................58
3.1.5 Application Setup Requirements..............................................58
3.2 Purchase Order Return in WMS.....................................................59
3.2.1. Process Description.......................................................................59
3.2.2 Data Mapping Requirements....................................................59
3.2.3 Business Rules.............................................................................59
3.2.4 Assumptions................................................................................60
3.2.5 Application Setup Requirements..............................................60
3.3 Confirm Pick Slip in WMS...............................................................61
3.3.1. Process Description.......................................................................61
3.3.2 Data Mapping Requirements....................................................61
Business Rules.........................................................................................62
3.3.3 Assumptions................................................................................62
3.3.4Application Setup Requirements..................................................62
Open and Closed Issues...............................................................................63
Open Issues..............................................................................................63
Closed Issues............................................................................................63

3. WMS Integration with Fusion Inventory 2vilxx67vi

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Introduction

Purpose

The purpose of the Business Data Architecture document is to describe the business architecture elements
that affect subsequent set up of the applications and integration between different systems. This work
product is used to assist in the

3. WMS Integration with Fusion Inventory 2170671

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1. X Store Integration with Fusion Financials

3. WMS Integration with Fusion Inventory 2270672

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

List of Interfaces in Scope

S.N Direction
Interface name
o
1 Sales Transactions Inbound
2 Sales Return Inbound
3 Sales Exchange Inbound
4 Receivables Receipts Inbound
5 Foreign Currency Sales Inbound
6 Bank Transfer Inbound

1.1 Sales Transaction

1.1.1 Process Description

The transaction of accrued revenue which should be collected as per of the payment method and increase the sales
revenue balance.

1.1.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Default Value Comments
No Name
1. Business Unit Organization ID Alphanumeri Oracle
c
2. Transaction Source NA Constant Oracle X-Store Imported TRX
3. Transaction Type Store ID Alphanumeri Oracle IN-Store ID
c
4. Transaction Date Transaction Date Oracle
Date
5. Units Qty Alphanumeri Oracle
c

3. WMS Integration with Fusion Inventory 2370673

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Field Fusion Field Name X Store Field Type Owner Default Value Comments
No Name
6. Unit Price Price Alphanumeri Oracle
c
7. Amount Total Amount Alphanumeri Oracle
c
8. Currency NA Alphanumeri Oracle
c
9. Customer Name Customer Name Constant Oracle Walking Customer
10. Payment Terms NA Constant Oracle Immediate
11. Item Item_ID Numeric Oracle
12. Item Description Item_Desc Alphanumeri Oracle
c
13. UOM UOM Alphanumeri Oracle
c
14. PO Number Trans_Sequence Alphanumeri Oracle Combination (Store ID + Reg
c ID + Date + TRX Seq)
15. PO Date Business_Date Date Oracle

1.1.3 Business Rules

- Business unit is the country, which can be defined as per the store country.
- X store transaction number, to be interfaced to Oracle Fusion AR transaction as PO Number and will be a
combination of the following (Store ID + Register ID + Date + Transaction Sequence).
- Detailed lines in the AR transaction, which will be imported from X Store.
- Tax will not be calculated in Fusion, but will be interfaced from Xstore transaction.
- Tax amount is included in the sales price (Prices include tax).
- The discount will be an extra line in the invoice in a negative amount and will affect the discount account in
Fusion.
- The Business date will be interfaced to the AR invoice in the PO Date Field as a reference, to be used in building
reports to compare it with Xadmin Sales reports.

1.1.4 Journal Entries;

Fusion AR Invoice:

3. WMS Integration with Fusion Inventory 2470674

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Dr. Receivables
Dr. Discount (if any)
Cr. Revenue
Cr. Tax

1.1.5 Assumptions
- No Assumptions.

1.1.6 Application Setup Requirements

- One AR Transaction type for each Branch “IN-Store ID” for the ability for reporting the invoices per branch and to
analyze the revenue accounts per branch (Accounting rule for the AR, revenue accounts will be driven from the
transaction type setup).
- Tax is inclusive.
- Customers: one customer will be used for all cash sales transactions “Walking Customer”, and for those customers
who may take on credit, other customers will be defined in Xstore and Fusion and mapped to each other’s, i.e. (‫جمعية‬
‫)البر‬.
- Transaction source: one transaction source will be created ‘X-store Imported transactions”
- Transaction Type will be created for each branch

3. WMS Integration with Fusion Inventory 2570675

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1.2 Return Transaction:

1.2.1 Process Description

- Customer Return Transaction is a credit Memo in Fusion Receivables that decrease the revenue balance due to
return or adjustments.

1.2.2 Data Mapping Requirements

Credit Memo
Field Fusion Field Name X Store Field Type Owner Default Value Comments
No Name
1. Business Unit Organization ID Alphanumeri Oracle
c
2. Transaction Source NA Constant Oracle X-Store Imported TRX
3. Transaction Type Store ID Alphanumeri Oracle CM-Store ID
c
4. Transaction Date Transaction Date Oracle
Date
5. Units Qty Alphanumeri Oracle In Minus
c
6. Unit Price Price Alphanumeri Oracle
c
7. Amount Total Amount Alphanumeri Oracle Immediate
c
8. Currency NA Alphanumeri Oracle
c
9. Customer Name Customer Name Constant Oracle Cash Customer
10. Payment Terms NA Alphanumeri Oracle
c
11. Item Item_ID Numeric Oracle

3. WMS Integration with Fusion Inventory 2670676

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Field Fusion Field Name X Store Field Type Owner Default Value Comments
No Name
12. Item Description Item_Desc Alphanumeri Oracle
c
13. UOM UOM Alphanumeri Oracle
c
14. PO Number Trans_Sequence Alphanumeri Oracle Combination (Store ID + Reg
c ID + Date + TRX Seq)
15. PO Date Business_Date Date Oracle
Refund
Field Fusion Field Name X Store Field Type Owner Default Value Comments
No Name
1. Business Unit Organization ID Alphanumeri Oracle
c
2. Refund Amount Total Amount Numeric Oracle
3. Refund Date Transaction Date Oracle
Date
4. Accounting Date Transaction Date Oracle
Date
5. Refund Payment NA Alphanumeri Oracle Cash
Method c

1.2.3 Business Rules

- The Return will be interfaced to Fusion as a credit memo against the return transaction and a refund will be created
at the same time with the total return amount, to be paid in bulk manually from Fusion using the payment process
request manger.
- All the refunds will be in Cash regardless the tender type in Xstore.

1.2.4 Journal Entries

Fusion Credit memo:
Dr. Revenue
Dr. Tax

3. WMS Integration with Fusion Inventory 2770677

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Cr. Receivables
Cr. Discount (If any)

Fusion Refund:
Dr. Receivables
Cr. Refund (Clearing Account)

Fusion AP invoice:
Dr. Refund (Clearing Account)
Cr. Liability

Fusion AP payment (Manual on Fusion)

Dr. Liability
Cr. Cash

1.2.5 Assumptions
- No Assumptions.

1.2.6 Application Setup Requirements

- One transaction type will be defined for each branch for the credit memo purposes “CM-Store ID”.
- Define receivable activity for refund “Refund”
- Define Approval Limits for users.

3. WMS Integration with Fusion Inventory 2870678

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1.3 Sales Exchange

1.3.1 Process Description
- The Sales exchange transaction is a credit memo and sales transaction at the same time, which will be happened in
case if the customer exchanged item with another.

- There are 3 cases for the sales exchange;

1- Return = Sales:
Ex. When the customer returns item with 100 SAR and buys another one for 100 SAR.
We will create a credit memo for the return and create an invoice for the new sales transaction with the
same PO number.
Then will apply the credit memo on the new invoice created.

2- Return > Sales:

Ex. When the customer returns item with 100 SAR and buys another one for 50 SAR.
We will create a credit memo for the return and create an invoice for the new sales transaction with the
same PO number.
Then will apply the credit memo on the new invoice created
And finally will issue refund in cash for the difference between the return and the sales.

3- Return < Sales :

Ex. When the customer returns item with 100 SAR and buys another one for 150 SAR.
We will create a credit memo for the return and create an invoice for the new sales transaction with the
same PO number.
Then will apply the credit memo on the new invoice created and will create applied receipt for the
difference between the sales and the return.

3. WMS Integration with Fusion Inventory 2970679

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1.3.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Default Value Comments
No Name
1. Business Unit Organization ID Alphanumeri Oracl
c e
2. Transaction Source NA Constant Oracl X-Store Imported TRX
e
3. Transaction Type Store ID Alphanumeri Oracl CM-Store ID
c e
4. Transaction Date Transaction Date Oracl
Date e
5. Units Qty Alphanumeri Oracl In Minus
c e
6. Unit Price Price Alphanumeri Oracl
c e
7. Amount Total Amount Alphanumeri Oracl Immediate
c e
8. Currency NA Alphanumeri Oracl
c e
9. Customer Name Customer Name Constant Oracl Cash Customer
e
10. Payment Terms NA Alphanumeri Oracl
c e
11. Item Item_ID Numeric Oracl
e
12. Item Description Item_Desc Alphanumeri Oracl
c e
13. UOM UOM Alphanumeri Oracl
c e
14. PO Number Trans_Sequence Alphanumeri Oracl Combination (Store ID +
c e Reg ID + Date + TRX Seq)
15. PO Date Business_Date Date Oracl

3. WMS Integration with Fusion Inventory 210706710

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Field Fusion Field Name X Store Field Type Owner Default Value Comments
No Name
e

1.3.3 Business Rules

- The invoice and the return will have the same PO number in Fusion to be a reference.

1.3.4 Journal Entries

1- Return = Sales
Fusion Credit memo:
Dr. Revenue
Dr. Tax
Cr. Receivables
Cr. Discount (If any)

Fusion AR Invoice:
Dr. Receivables
Dr. Discount (if any)
Cr. Revenue
Cr. Tax

Apply Credit Memo on AR Invoice:

XX

2- Return > Sales

Fusion Credit memo:
Dr. Revenue
Dr. Tax
Cr. Receivables

3. WMS Integration with Fusion Inventory 211706711

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Cr. Discount (If any)

Fusion AR Invoice:
Dr. Receivables
Dr. Discount (if any)
Cr. Revenue
Cr. Tax
Fusion Refund:
Dr. Receivables
Cr. Refund (Clearing Account)

Fusion AP Invoice:
Dr. Refund (Clearing Account)
Cr. Liability

Fusion AP payment Manual on Fusion)

Dr. Liability
Cr. Cash

3- Return < Sales

Fusion Credit memo:
Dr. Revenue
Dr. Tax
Cr. Receivables
Cr. Discount (If any)

Fusion AR Invoice:
Dr. Receivables
Dr. Discount (if any)
Cr. Revenue
Cr. Tax
Fusion AR Receipt:
Dr. Cash (will change based on tender type)
Cr. Receivables

3. WMS Integration with Fusion Inventory 212706712

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1.3.5 Assumptions
- No Assumptions.

1.3.6 Application Setup Requirements

- No specific setup requirements for the Exchange cycle.

3. WMS Integration with Fusion Inventory 213706713

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1.4 Receivables Receipt

1.4.1 Process Description

- Applying Receipts on Transaction automatically to close the due balance.
-

1.4.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Name Type Owner Default Comments
No Value
1. Business Unit Organization ID Alphanumer Oracl
ic e
2. Receipt Method Tender Type Alphanumer Oracl Cash-Store ID
ic e
3. Receipt Number (Authorization Alphanumer Oracl Transaction Number in
Code) ic e case of Cash.
4. Amount Total amount of Numeric Oracl
the transaction. e
5. Receipt Date Transaction Date Date Oracl
e
6. Customer Customer Name Alphanumer Oracl Walking
ic e Customer
7. Applied Transaction X Store transaction Alphanumer Oracl
number ic e
8. Currency Currency

1.4.3 Business Rules

- X Store transaction number will be interfaced to receipts in case if Cash and the authorization number in case if
Card Transaction.
- Standard receipt to be created with the invoice amount, and to be applied automatically to related invoice.
(related invoice will be identified with the “X Store transaction number ( PO number)

3. WMS Integration with Fusion Inventory 214706714

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

- No Customer tracking needed for the following tender types (Coupon.

1.4.4 Journal Entries

Will be based on tender types:

1- Cash Tender Type:

Invoice:
Dr. Receivables
Cr. Revenue
Receipt:
Dr. Cash
Cr. Receivables

2- Visa, Mada, Span, Amex, Master Card, STC Pay, Apple Pay Tender Types:

Invoice:
Dr. Receivables
Cr. Revenue
Receipt:
Dr. Bank Receivable Clearing Account
Cr. Receivables
Reconciliation (Fusion):
Dr. Bank
Cr. Bank Receivable Clearing Account

3. WMS Integration with Fusion Inventory 215706715

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

3- Coupon Tender Type:

AlShiaka gives Coupons to their guests, to be used in one-time purchase from the showrooms;

Invoice:
Dr. Receivables
Cr. Revenue

Receipt:
Dr. Marketing Expenses Account
Cr. Receivables

4- Voucher & Gift Card Tender Types:

There is some customers i.e. (‫ جمعية البر‬،‫)عبد اللطيف جميل‬, that can purchase some vouchers from Alshiaka and
distribute it to some other people who use it in purchasing process from showrooms.

In this case, the main customer (‫ جمعية البر‬،‫)عبد اللطيف جميل‬, pays the amount in HQ so the AR Receipt will be
created directly from Fusion manually and will be applied manually on the invoices which will be flown
from Xstore.

All the sales transactions that will be done in Xstore using the Vouchers will have the main customer
name attached to it in order that the integration can flow the transaction on the same customer in Fusion.

Receipt (Fusion Manual):

Dr. Cash/Bank
Cr. Receivables

Invoice (POS Automatic)

Dr. Receivables
Cr. Revenue

3. WMS Integration with Fusion Inventory 216706716

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Apply (Fusion Manually)

XX
5- Points (STC & Mobily):

If the walking customer pays using the STC Points or Apple points, the sales transaction should flow to
Fusion normally using the walking Customer attached to the invoice.

A dummy bank account will be created for STC and Apple that will be linked to their liability accounts.

Invoice and receipt will be created by integration, and receipt write off will be created as per the
commission percentage created on the DFF on the bank account.

The receipt will hit the STC bank account and GL liability account.

There is also a commission will be taken from AL Shiaka.

Invoice:
Dr. Receivables
Cr. Revenue
Receipt:
Dr. STC liability account
Dr. Commission (write off)
Cr. Receivables
AR invoice (Manual) at the end of the month:
Dr. Receivables
Cr. STC liability account
Receipt (Manual) at the end of the month:
Dr. Cash
Cr. Receivables

3. WMS Integration with Fusion Inventory 217706717

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

6- Loyalty points;

The loyalty points will be calculated and maintained in customer engagement then Xstore, no
calculations or points will be maintained in Fusion.

We will create a dummy bank account for redeeming the loyalty points.

A report from Xstore and Customer engagement (showing the new loyalty liability amounts added or
expired) should be submitted on monthly basis in order that a manual journal could be entered as per
this report

Normal Invoice (Integration Automatic)

Dr. Receivables
Cr. Revenue
Award points (GL Journal manually from Fusion at the end of each month)
Dr. Loyalty points Clearing
Cr. Provision for loyalty points
Invoice with redeeming Points (GL Journal manually from Fusion at the end of each month)

Invoice:
Dr. Receivables
Cr. Revenue
Receipt:
Dr. Provision for loyalty points
Cr. Receivables
At the end of the month (Fusion GL Manual, based on a report from customer engagement)

Recording the loyalty expense (points that redeemed already by clients)

Dr. Loyalty Expenses
Cr. Loyalty Points Clearing
Recording the loyalty points that expired without redeeming
Dr. Provision for loyalty points

3. WMS Integration with Fusion Inventory 218706718

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Cr. Loyalty Points Clearing

7- Free allowance

Invoice:
Dr. Receivables
Cr. Revenue
Receipt:
Dr. Employee Free Allowance
Cr. Receivables
8- Staff Discount

Fusion AR Invoice:
Dr. Receivables
Dr. Discount
Cr. Revenue
Receipt:
Dr. Cash
Cr. Receivables

1.4.5 Assumptions
- No Assumptions.

1.4.6 Application Setup Requirements

- One Receipt class per each Tender type (Cash - Visa - Master – Mada,..).
- For each receipt class a receipt method will be defined for each showroom “Cash-Store ID”, “Visa-Store ID”…
- One bank will be defined as “Stores Cashier”, and for each branch, one account will be defined.

3. WMS Integration with Fusion Inventory 219706719

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1.5 Foreign currency:

1.5.1 Process Description

- Make a receipt with foreign currency.
-

1.5.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Name Type Owner Default Comments
No Value
1. Business Unit Organization ID Alphanumer Oracl
ic e
2. Receipt Method Tender Type Alphanumer Oracl Cash-Store ID
ic e
3. Receipt Number (Authorization Alphanumer Oracl Transaction Number in
Code) ic e case of Cash.
4. Amount Total amount of Numeric Oracl
the transaction. e
5. Receipt Date Transaction Date Date Oracl
e
6. Customer Customer Name Alphanumer Oracl Walking
ic e Customer
7. Applied Transaction X Store transaction Alphanumer Oracl
number ic e
8. Currency Currency

1.5.3 Business Rules

- Transaction will be entered with SAR as a functional Currency
- Receipt will be created with foreign currency
- Receipt will be applied with exchange rates defined in Fusion.

3. WMS Integration with Fusion Inventory 220706720

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1.5.4 Assumptions
- No Assumptions.

1.5.5 Application Setup Requirements

- Enable foreign currencies on the application
- Define rates between functional currency and other foreign currencies

3. WMS Integration with Fusion Inventory 221706721

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1.6 E-Commerce

1.6.1 Process Description

- Process of selling online to customer.

1.6.2 Data Mapping Requirements

Invoices
Field Fusion Field Name X Store Field Type Owner Default Value Comments
No Name
1. Business Unit Organization ID Alphanumeri Oracle
c
2. Transaction Source NA Constant Oracle X-Store Imported TRX
3. Transaction Type Store ID Alphanumeri Oracle IN-Store ID
c
4. Transaction Date Transaction Date Oracle
Date
5. Units Qty Alphanumeri Oracle
c
6. Unit Price Price Alphanumeri Oracle
c
7. Amount Total Amount Alphanumeri Oracle
c
8. Currency NA Alphanumeri Oracle
c
9. Customer Name Customer Name Constant Oracle Walking Customer
10. Payment Terms NA Constant Oracle Immediate
11. Item Item_ID Numeric Oracle
12. Item Description Item_Desc Alphanumeri Oracle
c
13. UOM UOM Alphanumeri Oracle

3. WMS Integration with Fusion Inventory 222706722

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Field Fusion Field Name X Store Field Type Owner Default Value Comments
No Name
c
14. PO Number Trans_Sequence Alphanumeri Oracle Combination (Store ID + Reg
c ID + Date + TRX Seq)
15. PO Date Business_Date Date Oracle

Receipts
Field Fusion Field Name X Store Field Name Type Owner Default Comments
No Value
1. Business Unit Organization ID Alphanumer Oracl
ic e
2. Receipt Method Tender Type Alphanumer Oracl Cash-Store ID
ic e
3. Receipt Number (Authorization Alphanumer Oracl Transaction Number in
Code) ic e case of Cash.
4. Amount Total amount of Numeric Oracl
the transaction. e
5. Receipt Date Transaction Date Date Oracl
e
6. Customer Customer Name Alphanumer Oracl Walking
ic e Customer
7. Applied Transaction X Store transaction Alphanumer Oracl
number ic e
8. Currency Currency

1.6.3 Business Rules

- The E-commerce will be set up as a separate store on Xstore.
- The transactions will be interfaced from as same as any other store.
- There are three types of receiving Cash from clients (COD, Credit Card and from Showroom).

3. WMS Integration with Fusion Inventory 223706723

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

- The Shipping Company will be defined as a dummy bank and linked to its liability account, which will be cleared by
creating a payable invoice in the AP and payment.
- The Shipping Company will be defined also as a supplier.
- The shipping charges will be interfaced to Fusion as an amount in a separate line in Fusion with type freight.
- A DFF will be created on the dummy bank to maintain the commission percentage, which will be paid to the shipping
company, in order to generate a report which can help in calculating the shipping company commission.

1.6.4 Journal Entries

Invoice with COD tender type:
Dr. Receivables
Cr. Revenue
Cr. Shipping Charges
Receipt:
Dr. Aramex Liability Account
Cr. Receivables

Recording the amount needed from the shipping company based on a report at the end of the month:

AR invoice Manual:
Dr. Receivables (Aramex)
Cr. Aramex Liability Account
Credit memo to record the Shipping commission at the end of the month
Dr. Aramex Shipping Commission
Cr. Receivables (Aramex)
AR Receipt to receive the net from the shipping company at the end of the month
Dr. Cash

3. WMS Integration with Fusion Inventory 224706724

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Cr. Receivables

Invoice with Credit Card tender type:

Invoice:
Dr. Receivables
Cr. Revenue
Receipt:
Dr. Bank Receivable Clearing Account
Cr. Receivables
Reconciliation (Fusion):
Dr. Bank
Cr. Bank Receivable Clearing Account

Invoice from other branch:

Will be a normal invoice and receipt in the branch t=which the customer will receive the items from.

1.6.5 Assumptions
- No Assumptions.

1.6.6 Application Setup Requirements

- E-Commerce will be setup as same as normal branches.

3. WMS Integration with Fusion Inventory 225706725

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1.7 Bank Transfer

1.7.1 Process Description

- Process of Transfer funds between bank accounts.

1.7.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Name Type Owner Default Comments
No Value
1. Business Unit Organization ID Alphanumer Oracl
ic e
2. Receipt Method Tender Type Alphanumer Oracl Cash-Store ID
ic e
3. Receipt Number (Authorization Alphanumer Oracl Transaction Number in
Code) ic e case of Cash.
4. Amount Total amount of Numeric Oracl
the transaction. e
5. Receipt Date Transaction Date Date Oracl
e
6. Receivable Activity None Constant Oracl Bank
e Deposit
7. Currency Currency

1.7.3 Business Rules

- A bank transfer transaction will be created against the bank deposit transaction in Xstore with the amount and
number of buckets transferred from the branch to the head office.
- The amounts transferred to Bank will be hit the bank account after performing the bank reconciliation on Fusion.

3. WMS Integration with Fusion Inventory 226706726

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1.7.4 Journal Entries

Miscellaneous receipt (-)
Dr. Cash in transit
Cr. Showroom Cashier

Miscellaneous receipt (+)

Dr. Cash control account
Cr. Cash in transit

Cash Reconciliation (Fusion Manual)

Dr. Bank
Cr. Cash Control Account

1.7.5 Assumptions
- No Assumptions.

1.7.6 Application Setup Requirements

XX

3. WMS Integration with Fusion Inventory 227706727

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2. X Store Integration with Fusion Inventory

List of Interfaces in Scope

No. Interface name Direction

1 Item Master synchronization Outbound
2 Quantity Synchronization Outbound
3 Receive Goods in X store Inbound
4 Purchase Order Return Outbound
5 Transfer Between stores (Inter-Organization Transfer) Inbound
6 Transfer Material from main warehouse to stores (IMT) Inbound
7 Return from stores to main warehouse (inter organization transfer) Inbound
8 Sales Transaction Inbound
9 Sales Return Transaction Outbound
10 isolating damaged Items (sub inventory Transfer) Inbound
11 Gift, Test, and adjustment Transaction Inbound
12 Issue items to Laundry Transaction Inbound
13 Receipt items From Laundry Transaction Inbound
Sales Order (Confirm ship)

2.1 Item Master Synchronization

2.1.1Process Description
Whenever Item is created/updated/ Inactivated in specific inventory organizations in Oracle fusion, the records will get populated to X Center which
will then be replicated automatically to X Store POS to be available for sales and other transactions in the respective store defined in the X Store POS
and mapped to the Inventory organization available in fusion

3. WMS Integration with Fusion Inventory 228706728

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.1.2Data Mapping Requirements

Field Fusion Field Name X Store Type Owner Defaul Comments
No Field Name t Value
1. Interface Mode Oracle Item delete will be if item is set a
Create/ Update/ Delete status of (Inactive)
2. ITEM Code Parent Item Alphanumeri Oracle
c
3. Customer Order Enabled Merchandise Alphanumeri
(Yes – No) or non- c
merchandise
4. DESCRIPTION Primary Alphanumeri Oracle
Description c
5. Primary UOM UOM Alphanumeri Oracle
2 c
6. Inventory Organization ID Store ID Numeric Oracle
1
7. Catalog Alphanumeri Oracle
3 c
8. Category Category Alphanumeri Oracle
1 c
9. Item Attribute 1 (EFF) Color Alphanumeri Oracle
c
10. Item Attribute 2 (EFF) Size Alphanumeri Oracle
c
11. Item Attribute 3 (EFF) xxxx Alphanumeri Oracle
c
12. Item Lot Item patch Alphanumeri Oracle
c
13. Integration STATUS
(Pending/Processed/Error)
14. Error reason

2.1.3Business Rules
 Interface Mode:
 Create: If a new item is created, to be newly interfaced to X Store
 Update: if any of the major attributes is updated in fusion, then the updated values to be synchronized to X Store

3. WMS Integration with Fusion Inventory 229706729

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

a) Description
b) Category
c) Color
d) Size
e) Additional attribute
f) Item lot
 Delete: if the item status is updated to “Inactive” in Oracle fusion, then same item should be deactivated in X Store

 Inventory Organization ID:

 Inventory organization for which the item is assigned to (main warehouse and branches)
 Each Inventory organization assignment should be interfaced to X Store as a separate record
 Business Unit ID related to the inventory organization will be interfaced to X Store
 Unit Price:
 One unit prices will be defined and imported from Oracle Fusion, and in X store unit price will be defined per item lot (patch)

2.1.4Assumptions
 All mandatory attributes of the items must be first defined, in order for the item to be interfaced to X Store including:
1- Item Definition: Item Code – Description – UOM – Customer Order enabled-item additional attribute –shippable…)
2- Categories assignments for the item
3- Organization (Branch) assignment (item should at least be assigned to one Inventory Organization)
4- Store ID in X Store will be mapped in a DFF on the inventory Organization definition
5- When an item assigned to different organization, there should be separate record for each organization, other field cannot be the same.

2.1.5Application Setup Requirements

1- One master Org will be defined and all items shall be created and associated with the appropriate Inventory Org through this master org.
2- Inventory Org will be defined for each store, and main warehouse, the appropriate items will be associated to these Orgs
3- One catalog only will be defined at least
4- A single price list for all salable items, prices will be imported from fusion and will be another price list in X store according to Item Patch

2.2 Quantity Synchronization

2.2.1. Process Description

Any Inventory transaction that occurs in fusion that results in changes of on hand quantities in the organization will be interfaced to X Store and update item
balance by transaction total …. And DFF will be defined in oracle fusion transaction to consider this transaction in X store integration or not,

3. WMS Integration with Fusion Inventory 230706730

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

For example opening balance will be considered as an X store integration and will update x store on hand at the same time x Store return will not be
considered as an X Store integration to prevent looping it again to x store. So we do not recommend to do any transaction related to X store from oracle fusion
Examples:
Misc. transaction directly created in Fusion
 It can be increment or decrement to on-hand
Physical Inventory (adjustment)
 It can be increment or decrement to on-hand
 It is done on daily, weekly and monthly basis

2.2.2Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Default Comments
No Name Value
1. Transaction Number Transaction Number
2. Transaction Type (+) ve or (-) ve
3. Source NA
(Account Alias
Name)
4. Business Unit Organization ID
5. Organization Store ID
6. Quantity Quantity It can be -Ve or +Ve
Quantities
7. Item Code Item ID
8. Lot Number NA
9. Expiry Date NA
10. UOM UOM
11. Sub inventory NA Store

3. WMS Integration with Fusion Inventory 231706731

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.2.3 Business Rules

2.2.4 Assumptions

2.2.5 Application Setup Requirements

 DFF will be defined on the sub inventories to flag the sub inventories for which this web service should consider its
transactions

3. WMS Integration with Fusion Inventory 232706732

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.3 Receive Goods in X store

2.3.1. Process Description

The Receiving transactions in Xstore is Covering the following points:

1- PO Receiving
2- IMT ‘Internal Material Transfer’ from MWH
3- Receiving of Shipments from Other Stores

Once the Store manager receives the transferred items in X Store (populated from the previous web service) then this receiving transaction will be populated
to oracle fusion as a final receiving transaction (Put Away transaction)

2.3.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Defaul Comments
No Name t Value
1. Shipment Number/ PO Shipment
number /transfer order Number/purchase
Number order Number
2. Receipt number Receiving
Transaction Number
3. Supplier/Source Source In case of internal transfer, the
Organization supplier will be the source
organization
4. Destination Destination Store ID The receiving store or main
Organization warehouse
5. Item Code Item ID
6. UOM UOM
7. Lot number Item Patch Item lot
8. Expiry Date Expiry Date Receiving date + shelf life days
(Automatically generated) if case
of PO

3. WMS Integration with Fusion Inventory 233706733

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.3.3 Business Rules

 Lot number and expiry date, will be picked from the shipping transaction that was populated to X Store in the previous web service.
 Partial Shipments receipt scenario should be taken into consideration, in this case the shipment document will remain open.
 X store has to show only the open shipments With taken into consideration the PO status (Open only) ignoring closed, finally closed,
cancelled, closed for receiving and closed for invoicing.

2.3.4 Assumptions
N/A

2.3.5 Application Setup Requirements

 Receiving parameters should be set for each organization

2.

3. WMS Integration with Fusion Inventory 234706734

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.4 Purchase Order Return

2.4.1. Process Description

Purchase order return will be handled in X store and oracle fusion … user will select closed purchase orders And select Return type which will be (return to
receiving Area or return to Supplier)
In case of select return to vendor it will deduct the quantity directly

2.4.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Default Comments
No Name Value
1. Purchase order number PO Number Number
2. Purchase Order Line PO Line Number
3. Item Number Item ID Alpha
Numeric
4. Quantity Qty Number
5. Lot number Lot Number Alpha
Numeric
6. Expiry Date Expiry Date Date
7. Unit of Measure UOM Alpha
Numeric
8. Return to Return to Alpha Supplier/receiving Area
Numeric
9. Return Date Return Date Date
10. Integration STATUS Status Alpha
(Pending/Processed/Error) Numeric
11. Error reason Alpha
Numeric

2.4.3 Business Rules

 Lot Number should be interfaced to X Store interface tables.

3. WMS Integration with Fusion Inventory 235706735

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.4.4 Assumptions
After return process purchase order will back to status open again

2.4.5 Application Setup Requirements

3. N/A

3. WMS Integration with Fusion Inventory 236706736

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.5 Transfer Between stores (Inter-Organization Transfer)

2.5.1. Process Description

 Inter-Organization transfer
 Once a shipment is created in oracle fusion , the source organization will transfer items to the other store
 The inter-org transfer deducting form the source org on hand quantity.
 The other part of the process which is the receiving process will be done on X store and reflect on Oracle Fusion inventory.

2.5.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Default Comments
No Name Value
1. Shipment number Shipment number Alpha
Numeric
2. Shipped quantity Transaction quantity number
3. Item Code Item ID Alpha
Numeric
4. Lot Number Item lot
5. Expiry Date Expiry date Date
6. UOM UOM Alpha Primary
Numeric
7. Quantity Quantity Number
8. Transaction date Transaction Date Date
9. Source Sub inventory Source Sub inventory Alpha
Numeric
10. Distention Sub inventory

3. WMS Integration with Fusion Inventory 237706737

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.5.3 Business Rules

2.5.4 Assumptions

1.5.5 Application Setup Requirements

 Inter- organization must to be defined between the stores

4.

3. WMS Integration with Fusion Inventory 238706738

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.6 Transfer Material from main warehouse to stores (IMT)

2.6.1. Process Description

 Internal material transfer will be created to handle store’s request from main warehouse
 Internal material transfer can be raised in these ways
o In X store and will generate transfer order in oracle fusion
o Manual transfer order in oracle fusion
o Min-Max Replenishment (Automatic)

2.6.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Default Comments
No Name Value
1. Transfer Order Number Request Number Available only in case of manual IMT
Number raised by X store.
Not Available in case of Automatic
replenishment (MIN-MAX).
2. Transfer Order Line Number Line Number Number
3. Supply Type Transfer
4. Item Number Item ID Alpha
Numeric
5. Quantity Qty Numeric
6. Unit of Measure UOM Alpha
Numeric
7. Source Organization Store ID Alpha
(Warehouse) Numeric
8. Destination Organization Store ID Alpha
(Requesting Numeric
Store)
9. Destination Sub inventory Store (Store ID) Store
Code
10. Requisition Date Transfer Date Date
11. Preparer Alpha Default
Numeric
12. Supply Order Reference Line NA
13. Integration STATUS Status Alpha
(Pending/Processed/Error) Numeric
14. Error reason NA

3. WMS Integration with Fusion Inventory 239706739

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.6.3 Business Rules

2.6.4 Assumptions

2.6.5 Application Setup Requirements

 Inter- organization must to be defined between main warehouse and all stores

5.

3. WMS Integration with Fusion Inventory 240706740

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.7 Return from stores to main warehouse (Inter-Organization transfer)

2.7.1. Process Description

 Inter-Organization transfer
 Once a shipment is created in oracle in X store , the source organization will Ship the returned Quantity to Main warehouse
 The inter-org transfer deducting form the source org on hand quantity.
 The other part of the process which is the receiving process will be
done in main warehouse

2.7.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Name Type Owner Default Comments
No Value
Shipment number Shipment number Alpha
1.
Numeric
2. Shipped quantity Transaction quantity Number
Item Code Item ID Alpha
3.
Numeric
Lot Number Item lot Alpha
4.
Numeric
5. Expiry Date Expiry date Date
UOM UOM Alpha Primary
6.
Numeric
7. Quantity Quantity Number
8. Transaction date Transaction Date Date
Source Org & Sub Source Sub inventory Alpha
9.
inventory Numeric
Distention org & Sub Distention Sub inventory Alpha
10.
inventory Numeric

3. WMS Integration with Fusion Inventory 241706741

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.7.3 Business Rules

2.7.4 Assumptions

2.7.5 Application Setup Requirements

 Inter- organization must to be defined between main warehouse and all stores

6.

3. WMS Integration with Fusion Inventory 242706742

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.8 Sales Transaction

2.8.1. Process Description

Once a sales transaction is done in X Store, then the same transaction will be interfaced to oracle as a miscellaneous issue and will deduct item on
hand (balance) with transaction quantity

2.8.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Default Comments
No Name Value
1. Transaction Number Transaction
Number
2. Transaction Type(Issue) Sales
3. Source Sales Accounting
(Account Alias Name)
4. Organization Store ID
5. Item Code Item ID
6. Lot Number Item Lot
7. Expiry Date Expiry Date
8. UOM UOM
9. Sub inventory Sub inventory Store
10. Quantity quantity

3. WMS Integration with Fusion Inventory 243706743

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Business Rules
 Lot number and expiry date, need to be selected from X store from the “Issuing” Organization.

 One price list will be defined in oracle fusion and Prices will be maintained in X store

 Items will should be issued through miscellaneous issue functionality.

2.8.2 Assumptions
No Assumptions

2.8.3 Application Setup Requirements

SLA cost accounting need to be set to automate COGS ‘Cost of Goods sold ‘account in miscellaneous transactions

3. WMS Integration with Fusion Inventory 244706744

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.9 Sales Return Transaction

2.9.1. Process Description

Once a sales Return transaction is done in X Store, then the same transaction will be interfaced to oracle as a miscellaneous Receipt and will
increase item on hand (balance) with transaction quantity

2.9.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Default Comments
No Name Value
11. Transaction Number Transaction
Number
12. Transaction Return
Type(Receipt )
13. Source Sales Accounting
(Account Alias Name)
14. Organization Store ID
15. Item Code Item ID
16. Lot Number Item Lot
17. Expiry Date Expiry Date
18. UOM UOM
19. Sub inventory Sub inventory Normal
20. Quantity quantity

3. WMS Integration with Fusion Inventory 245706745

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Business Rules

 One price list will be defined in oracle fusion and Prices will be maintained in X store

 Items will should be receipt through miscellaneous Receipt functionality.

2.9.3 Assumptions
No Assumptions

2.9.4 Application Setup Requirements

SLA cost accounting need to be set to automate COGS ‘Cost of Goods sold ‘account in miscellaneous transactions

3. WMS Integration with Fusion Inventory 246706746

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1.

2.10 Isolating damaged Items (sub inventory Transfer)

2.10.1. Process Description

Isolating damaged quantity will be handled through X store and Sub-inventory transaction will be created in oracle fusion to
transfer item balance from normal bucket to damaged bucket

Sub inventory transfer

 Transfer between sub inventories at the same store.
 The transfer will transfer items from normal bucket to damaged bucket
 The integration should create sub inventory transaction in oracle fusion

2.10.2Data Mapping Requirements

Field No Fusion Field X Store Field Type Owner Default Comments
Name Name Value
1. Transaction Transaction Number Numeric
Number
2. Transaction Transaction type Alpha Numeric Xstore
type Damage
Transfer
3. Source Sub Source Sub inventory Normal
inventory
(Normal)
4. Destination sub Destination sub Damage
inventory inventory
(Damage)
5. Organization Store ID Alpha Numeric It will be store name
6. Quantity Quantity Number
7. Item Code Item ID Alpha Numeric
8. Lot Number Lot number Alpha Numeric
9. Expiry Date Expiry Date DAte
10. UOM UOM Alpha Numeric

3. WMS Integration with Fusion Inventory 247706747

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.10.3 Business Rules

2.10.4 Assumptions
N/A

2.10.5 Application Setup Requirements

 N/A

2.11 Gift and Adjustment Transaction

2.11.1. Process Description

Gift and testing items will be raised in X Store, then the same transaction will be interfaced to oracle as a miscellaneous issue and will deduct item
on hand (balance) with transaction quantity

3. WMS Integration with Fusion Inventory 248706748

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.11.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Default Comments
No Name Value
1 Transaction Number Transaction
Number
2 Transaction Gifts
Type(Gift and
adjustment )
3 Source Sales Accounting
(Account Alias
Name)
4 Organization Store ID
5 Item Code Item ID
6 Lot Number Item Lot
7 Expiry Date Expiry Date
8 UOM UOM
9 Sub inventory Sub inventory Normal
10 Quantity quantity

3. WMS Integration with Fusion Inventory 249706749

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Business Rule.

 Prices will be maintained in X store in zero price

 Items will should be issued through miscellaneous issue functionality.

2.11.3 Assumptions
No Assumptions

2.11.4 Application Setup Requirements

SLA cost accounting need to be set to automate COGS ‘Cost of Goods sold ‘account in miscellaneous transactions

3. WMS Integration with Fusion Inventory 250706750

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.12 Issue items to Laundry Transaction

2.12.1. Process Description

When user send goods to laundry the inventory balance has to be updated and decrease the balance with this quantities till completing the
washing issue transaction will be raised in X Store, then the same transaction will be interfaced to oracle as a miscellaneous issue and will deduct
item on hand (balance) with transaction quantity

2.12.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Default Comments
No Name Value
1 Transaction Number Transaction
Number
2 Transaction Laundry issue
Type(issue to
laundry)
3 Source Issue Accounting
(Account Alias
Name)
4 Organization Store ID
5 Item Code Item ID
6 Lot Number Item Lot
7 Expiry Date Expiry Date
8 UOM UOM
9 Sub inventory Sub inventory Normal
10 Quantity quantity

3. WMS Integration with Fusion Inventory 251706751

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Business Rule.

 Prices will be maintained in X store in zero price

 Items will should be issued through miscellaneous issue functionality.

2.12.3 Assumptions
No Assumptions

2.12.4 Application Setup Requirements

SLA cost accounting need to be set to automate COGS ‘Cost of Goods sold ‘account in miscellaneous transactions

2.13 Receipt items From Laundry Transaction

2.13.1. Process Description

When user Receive goods from laundry the inventory balance has to be updated and increase the balance with this quantities

3. WMS Integration with Fusion Inventory 252706752

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Receipt transaction will be raised in X Store, then the same transaction will be interfaced to oracle as a miscellaneous Receipt and will increase
item on hand (balance) with transaction quantity

2.13.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Default Comments
No Name Value
1 Transaction Number Transaction
Number
2 Transaction Laundry Receipt
Type(Receipt from
Laundry)
3 Source Issue Accounting
(Account Alias
Name)
4 Organization Store ID
5 Item Code Item ID
6 Lot Number Item Lot
7 Expiry Date Expiry Date
8 UOM UOM
9 Sub inventory Sub inventory Normal
10 Quantity quantity

3. WMS Integration with Fusion Inventory 253706753

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Business Rule.

 Prices will be maintained in X store in zero price

 Items will should be issued through miscellaneous Receipt functionality.

2.13.3 Assumptions
No Assumptions

2.13.4 Application Setup Requirements

3. WMS Integration with Fusion Inventory 254706754

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.14 Shipping Sales Orders from stores

2.14.1. Process Description

When sales order created in main warehouse (Fusion) but the shipping will be from stores, user in store will ship this sales order with X-Store

2.14.2 Data Mapping Requirements

Field Fusion Field Name X Store Field Type Owner Default Comments
No Name Value
Sales order Number Transaction
1
Number
2 Shipment number
4 Organization Store ID
5 Item Code Item ID
6 Lot Number Item Lot
7 Expiry Date Expiry Date
8 UOM UOM
9 Sub inventory Sub inventory Store
10 Quantity quantity

2.14.3 Business Rule

 Sales order will be created in main warehouse and shipping will be from stores

2.14.4 Assumptions
No Assumptions

3. WMS Integration with Fusion Inventory 255706755

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

2.14.5 Application Setup Requirements

Shipping parameter for store must be defined

3. WMS Integration with Fusion Inventory 256706756

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

3. WMS Integration with Fusion Inventory

List of Interfaces in Scope

No. Interface name Direction

1 Receive goods In WMS Inbound
2 Purchase Order Return In WMS Outbound
3 Confirm Pick Slip In WMS Outbound
4

3.1 Receive goods In WMS

3.1.1 Process Description

The Receiving transactions in WMS is Covering the following points:

3. WMS Integration with Fusion Inventory 257706757

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

1- PO Receiving in main warehouse

2- Sales order return from customers
3- Receiving of Shipments from Other Stores

Once the Store manager receives items in MWS (populated from the previous web service) then this receiving transaction will be populated to oracle fusion as
a final receiving transaction (Put Away transaction)

3.1.2 Data Mapping Requirements

Field Fusion Field Name WMS Field Name Type Owner Defaul Comments
No t Value
9. Shipment Number/ PO Shipment
number /transfer order Number/purchase
Number /RMA number order Number
10. Receipt number Receiving
Transaction Number
11. Supplier/Source Source In case of internal transfer, the
Organization / supplier will be the source
Customer organization
12. Destination Destination Store ID The receiving store or main
Organization warehouse
13. Item Code Item ID
14. UOM UOM
15. Lot number Item Patch Item lot
16. Expiry Date Expiry Date Receiving date + shelf life days
(Automatically generated) if case
of PO

3.1.3 Business Rules

 Lot number and expiry date, will be picked from the shipping transaction that was populated to WMS in the previous web service.
 Partial Shipments receipt scenario should be taken into consideration, in this case the shipment document will remain open.

3. WMS Integration with Fusion Inventory 258706758

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

3.1.4 Assumptions
N/A

3.1.5 Application Setup Requirements

 Receiving parameters should be set for each organization

7.

3. WMS Integration with Fusion Inventory 259706759

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

3.2 Purchase Order Return in WMS

3.2.1. Process Description

Purchase order return will be handled in MWS and oracle fusion … user will select closed purchase orders And select Return type which will be (return to
receiving Area or return to Supplier)
In case of select return to vendor it will deduct the quantity directly

3.2.2 Data Mapping Requirements

Field Fusion Field Name WMS Field Type Owner Default Comments
No Name Value
1 Purchase order number PO Number
2 Purchase Order Line PO Line
3 Item Number Item ID
4 Quantity Qty
5 Lot number Lot Number
6 Expiry Date Expiry Date
7 Unit of Measure UOM
8 Return to Return to Supplier/receiving Area
9 Return Date Return Date
10 Integration STATUS Status
(Pending/Processed/Error)
11 Error reason

3. WMS Integration with Fusion Inventory 260706760

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

3.2.3 Business Rules.

3.2.4 Assumptions
After return process purchase order will back to status open again

3.2.5 Application Setup Requirements

N/A

3. WMS Integration with Fusion Inventory 261706761

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

8.

3.3 Confirm Pick Slip in WMS

3.3.1. Process Description

Once a sales order transaction is done in oracle fusion, user will create pick wave in oracle fusion, then confirm pick slip will be raised in WMS
through integration and record item lot. After that ship confirmation will be raised in oracle fusion.

3.3.2 Data Mapping Requirements

Field Fusion Field Name WMS Field Name Type Owner Default Comments
No Value
1 Pick slip Number Transaction
Number
2 Organization Store ID
3 Item Code Item ID
4 Picked Quantity Quantity
5 Lot Number Item Lot
6 Expiry Date Expiry Date
7 UOM UOM
8 Source Sub inventory Sub inventory Normal

3. WMS Integration with Fusion Inventory 262706762

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Business Rules
 Lot number and expiry date, need to be selected from X store from the “Issuing” Organization.

 One price list will be defined in oracle fusion and Prices will be maintained in X store

 Items will should be issued through miscellaneous issue functionality.

3.3.3 Assumptions
No Assumptions

3.3.4Application Setup Requirements

N/A

3. WMS Integration with Fusion Inventory 263706763

MD050_Al shiaka_APPLICATION_INTERFACE_FUNCTIONA_DESIGN_V01

Open and Closed Issues

Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

3. WMS Integration with Fusion Inventory 264706764