| Oracle® Retail Store Inventory Management Store User Guide Release 16.0 E76179-08 |
|
 Previous |
 Next |
| Oracle® Retail Store Inventory Management Store User Guide Release 16.0 E76179-08 |
|
Previous |
Next |
This chapter covers Direct Store Delivery (DSD). The following topics are covered:
Overview: Introduction to DSD.
Functionality: Description of available screens.
Technical: Integration with Oracle Retail Integration Bus (RIB), web services, batch, and the database structure.
A direct store delivery is a delivery in which the supplier drops off merchandise directly at the store. These deliveries, received directly at the store, can be against existing purchase orders raised by the corporate or by the store, or without a purchase order. The delivery supports containers coming in directly with advance shipment notice or the system will create a container when the ASN is loaded in SIM. Even for receipts without ASN the system will allow the user to create containers.
The store can receive partial shipments, resulting in multiple deliveries against a single purchase order. When all items have been received and a delivery has been finalized, the delivery receipt can be printed.
Features:
Direct deliveries against a Purchase Order (PO) and with Advance Shipment Notice (ASN) from the supplier. This feature also supports containers coming directly from the source and allows the user to create additional containers.
Direct Deliveries against a PO and without ASN from the supplier. The user can receive the delivery by creating one or more containers.
Direct deliveries without a PO.
Receive inventory at the store directly from the vendor using the DEX/NEX method. The system will create a container and no more containers can be added.
Add extended attributes to the item.
Print delivery reports.
Scanner option to scan the data bar in the receiving process.
Business Cases
DSD Receiving Process for PO based delivery with ASN:
Corporate office places a purchase order to the vendor and instructs the vendor to supply the goods directly to the store.
Supplier ships the goods with the ASN to the store and the store receives the goods against the ASN.
DSD Receiving Process for a PO based delivery without ASN:
Corporate office places a purchase order to the vendor and instructs the vendor to supply the goods directly to the store.
Supplier ships the goods, but no ASN is sent to the store and the store receives the goods against the PO.
DSD Receiving Process for a Dex/Nex based delivery:
Supplier scans what is needed at the store, goes to the truck, and picks out the items that need to be delivered.
The supplier docks a device or sends the dex/nex delivery document to the retailer through a network.
Dex/Nex input file is uploaded into SIM and the store personnel confirm the receipt after viewing in the detail screen in SIM.
DSD Receiving Process without PO:
Stores that are allowed receiving the goods without purchase order can verbally place the order to the vendor and create those receipts on the fly.
The user can access the DSD Receiving and Purchase order from the Shipping and Receiving menu. The DSD Receiving List screen that appears after selecting the DSD Receiving option lists all the active deliveries that are available in SIM and allows the user to create or modify a receipt. The user can also create a new receipt on the fly without any purchase order by selecting the create receipt button.
After selecting the ASN, active delivery, or supplier for an on the fly delivery, the DSD Receiving detail appears and allows the user to proceed with the detailed receiving using the DSD Receiving Container Detail screen. The user can access various options such as Extended Attributes, Info, UIN, Add Item/Scan, Document, Notes, and so on, from the DSD Receiving Container Detail screen to perform various functions.
The Purchase Order List screen that appears after selecting the Purchase Order allows the user to view the Purchase Order detail and create a receipt against a PO.
When the user selects to create a receipt, the system takes the user to the DSD Receiving Detail screen and follow the same flow as described above.
This section covers system parameters, store parameters, notifications, and security.
Always Send DSD Receipt Cost
Values: Yes/No
Default: No
Topic: DSD Receiving
Editable: Yes
Yes: When the receipt is published, the unit cost will be sent if there is not an override cost.
No: When there receipt is published, only the override cost will be sent if it exists.
Disable Discrepancy Checks in DSD
Values: Yes/No
Default: No
Topic: DSD Receiving
Editable: Yes
Yes: The user will not have to review discrepancies at the end of receiving on the handheld.
No: The user will have to review discrepancies at the end of receiving on the handheld.
Display Unit Cost for Direct Deliveries
Values: Yes/No
Default: No
Topic: DSD Receiving
Editable: Yes
Yes: Display Unit Cost and allow editing on both the PC and handheld when receiving. If Yes, SIM displays the original cost and allows entering the new cost for the on-the-fly and Dex/Nex deliveries. For the delivery with PO and ASN, it displays the unit cost. Display the Unit Cost on the Direct Delivery Report when printing.
Unit cost will also be displayed in the Store Ordering dialog.
No: Do not display this data to the user in the DSD Receiving Container Detail screen. Do not display the unit cost on the Direct Delivery Report. If No, SIM does not display the unit cost and does not allow editing or entering new cost.
Unit cost will not be displayed in the Store Ordering dialog.
Direct Delivery - Preferred Currency
Values: Store Currency/Supplier Currency
Default: Store Currency
Topic: DSD Receiving
Editable: Yes
This parameter will default the store or supplier currency to newly created POs depending on preference.
DSD Receiving Search Default
Values: PO/ASN/Container/Item/Supplier
Default: Container
Topic: DSD Receiving
Editable: Yes
This is applicable on the handheld.
This parameter determines what the default search method to identify the delivery on the handheld.
Enable DSD Pack Receiving
Values: Yes/No
Default: No
Topic: DSD Receiving
Editable: Yes
Yes: When scanning an item on a handheld that is a component for a pack, the system will prompt the user "Does this item belong to a Pack." If the user selects Yes, the system will return the pack items for the item to be used on the delivery. If the user selects No, the system will put the component item on the delivery.
No: The system will not validate whether the scanned item is a component item when doing a delivery on the handheld.
Ignore the Supplier DSD Indicator to Create a PO on the Fly
Values: Yes/No
Default: Yes
Topic: DSD Receiving
Editable: Yes
Allows the system to ignore the supplier level indicator to create a PO in SIM.
Yes: The system ignores the supplier level flag and will always allow stores to create purchase orders for any supplier based on the receipt.
No: The system will verify creating a purchase order on the fly is allowed based on the supplier level flag.
Number of Days Received Direct Deliveries can be Adjusted
Values: 0-999
Default: 0
Topic: DSD Receiving
Editable: Yes
0: no adjustment
1: allowed to adjust until the end of today
2: allowed to adjust until the end of tomorrow
X: allowed to adjust until X number of days starting with today as day 1
This parameter specifies the number of days received direct deliveries can be reopened and adjusted. If a direct delivery falls within the number of days, an Adjust Delivery button will display on the received delivery. The user will be allowed to edit values and confirm the delivery.
Over Received Quantity Email Alert
Values: Yes/No
Default: Yes
Topic: DSD Receiving
Editable: Yes
This parameter will generate a notification when more than the expected quantity has been received and the store parameter Direct Delivery Auto Remove Over Received Quantity is set to Yes. The alert will include the UINs marked for removal.
Customer Order Receipt Email Alert
For additional details on this parameter, see Chapter 11, "Transfers.".
Enable Multiple Sets of Books
Values: Enabled/Disabled/SIM Only
Default: Disabled
Topic: Admin
Editable: Yes
Enabled: Multiple Sets of Books (MSOB) is enabled in RMS. Suppliers will be limited to only those locations corresponding to the operating unit for which they are set up.
Disabled:- MSOB is disabled in RMS. No validation on the operating unit is performed.
SIM Only: MSOB is disabled in RMS. SIM will utilize the operating unit validation. Limits the suppliers available for a location. The operating unit information is set up only in SIM.
This parameter defines whether to limit the supplier selection based on the supplier sites associated with the location.
|
Note: This parameter is also applicable to Finishers (Transfer to Finisher, Lookup Finisher). |
Barcode Scan/Entry Log - Receiving
Values: Yes/No
Default: Yes
Topic: Admin
Editable: Yes
Yes: Captures, on the handheld, all container and item scans or manual entries by user, location, and time at the point of receiving deliveries. Containers are captured in the quick receiving dialog when item level is captured in the Item Receiving function of the Container Summary for DSD and Transfer Receiving.
No: Does not capture any container or item information in the handheld receiving dialogs.
Allow Multiple Deliveries against PO with No ASN
Values: Yes/No
Default: Yes
Topic: DSD Receiving
Editable: Yes
Yes: The user is able to create more than one delivery for the same PO when the PO does not have an associated ASN.
No: The user can only create a single delivery against a PO when the PO does not have an associated ASN. The PO will be closed when the delivery is confirmed.
Auto Close Days after Expected Date
Values: 0-999
Default: 5
Topic: DSD Receiving
Editable: Yes
Number of days after the expected delivery date the ASN will be closed.
Auto Pick on Receive - Direct Delivery/Transfer Delivery
For additional details on this parameter, see Chapter 11, "Transfers.".
Direct Delivery Auto Remove over Received Quantity
Values: Yes/No
Default: No
Topic: DSD Receiving
Editable: Yes
Yes: The user is able to create more than one delivery for the same PO when the PO does not have an associated ASN.
No: The over received quantities will stay in the delivery transaction.
Direct Delivery Default to Shop floor Receiving
Values: Yes/No
Default: No
Topic: DSD Receiving
Editable: Yes
This parameter determines whether the receiving checkbox or handheld option on the DSD Receiving Container screen will default to receive inventory into the shop floor instead of automatically receiving into the back room.
Yes: The DSD Receiving Container workflow will default the checkbox or handheld option to receive inventory into the shop floor. The shop floor inventory bucket will be incremented instead of the backroom bucket. If a capacity is defined for the item, the maximum shop floor quantity will equal the capacity; otherwise, the shop floor will be updated to the entire receipt amount.
No: The checkbox or handheld option will be defaulted to back room and all inventory will be automatically received into the back room or delivery bay.
|
Note: With the proper permissions, the user will still have the option to receive onto the shop floor while receiving the delivery by changing the default to shop floor on the handheld or PC. |
Damaged inventory will not move to the shop floor.
Direct Delivery Invoice Entry
Values: Enabled/Disabled/Unique
Default: Enabled
Topic: DSD Receiving
Editable: Yes
Enabled: This option allows the user to enter any value for the invoice number, including duplicates.
Disabled: The Invoice Number and date fields are disabled.
Unique: The Invoice Number field will allow entry, however, the user will not be able to enter a duplicate invoice number based upon the supplier.
Upon entering an Invoice Number, the system will validate if the invoice already exists for the supplier defined on the DSD. If a duplicate exists, there will be an error. If no duplicate exists, the invoice number will be accepted.
Direct Delivery Receive Item Capacity
Values: Yes/No
Default: No
Topic: DSD Receiving
Editable: Yes
This parameter determines whether the capacity will be considered while receiving the deliveries.
Yes: While receiving, the capacity will be considered.
For example: If capacity is 50, delivery is for 100, and Available SOH is 10 on the shop floor, if this parameter is on and receive in shop floor is checked, 40 (un-damaged) will be moved to shop floor and the rest to the backroom.
No: While receiving, the capacity will not be considered.
Damaged inventory will not move to the shop floor.
DSD Receiving Auto Remove Damaged Quantity
Values: Yes/No
Default: No
Topic: DSD Receiving
Editable: Yes
Yes: All damaged items on the delivery are removed automatically when confirming the transaction.
No: All damaged items remain on the delivery when confirming the transaction.
Auto Pick Mixed Containers
Values: Yes/No
Default: No
Topic: Customer Orders
Editable: Yes
Yes: If a container has items in it that are for both customer orders and non-customer orders, SIM will auto pick the container. It will mark those items that exist on the customer order as picked.
No: If there is a mixed container of customer order and non-customer order items, it will not get auto picked and the picked quantities will not be updated.
Auto Pick on Receive - Direct Delivery
Values: Yes/No
Default: No
Topic: Customer Order
Editable: Yes
Yes: SIM will automatically fill in the pick quantities on the customer order when receiving. This can only happen if the customer order record has already come into the system. If there is no customer order, the auto picking will not happen at the time of receiving, rather it will occur when the customer order comes in.
No: SIM will not pick when receiving goods.
Reserve Customer Order Inventory upon Receiving
Values: Yes/No
Default: No
Topic: Customer Order
Editable: Yes
This store parameter will dictate when inventory for a cross channel customer order should be reserved.
Yes: Inventory will be reserved upon receiving a delivery in the store which contains the customer order (Store to store transfer, DSD, Warehouse delivery).
No: Inventory will be reserved upon getting the customer order into the store.
The Customer Order Receipt Alert notification will be triggered upon confirmation of a receipt of a DSD Receipt which is for a web order customer order. This is controlled by the Customer Order Receipt Email Alert system setting.
Security permissions exist for:
Accessing DSD Receiving, Accessing Purchase Order, Allow DSD Receiving with PO, Allow DSD Receiving without PO, Access to create a new container, Access to purchase order menu, editing, confirming delivery, over receiving, override supplier discrepancies, and so on.
Override supplier discrepancies permissions is to determine whether the user can override the supplier discrepancy check.
Hide cost.
Email notification when receiving items for a customer order.
This section describes the available screens.
The DSD Receiving List screen is accessed when the user clicks on the DSD Receiving button from the Shipping and Receiving menu.
The DSD Receiving List by default shows all the active deliveries, that is "In Progress" and "New" for the user to do the detailed receiving. It includes all types of deliveries. If the supplier has sent an ASN or a Dex/Nex file, it is uploaded and listed here with "New" status. The user can select a delivery and do the detailed receiving. If the user has started the delivery process, it shows the delivery with the "In Progress" status. The user can select the "In Progress" deliveries to continue the receiving. The user can also select the completed deliveries to do the adjustment.
The deliveries created in SIM are shown with the type On The Fly.
The deliveries that have ASN from the source are shown with the type ASN.
The deliveries that are PO based and no ASN are shown with the type PO.
For the deliveries transmitted into SIM using DEX/NEX, the type of the delivery will be shown as DEX/NEX. For more details, see "Direct Exchange and Network Exchange Receiving."
From the DSD Receiving List window, the user can do the following:
Use the Filter button to filter the list based on the given criteria.
Select Create Receipt to create a delivery without any PO (on the fly).
Select the delivery from the list and do detailed receiving or edit the delivery.
Select one or more deliveries and print a report.
The user is taken to the DSD Receiving Detail screen to access the existing delivery upon double clicking a delivery record.
The user can click the Create Receipt button which will direct the user to the DSD Receipt Create popup to create a delivery without an existing Purchase Order. The user will have to search for or select a supplier from whom the delivery is coming. The user will be directed to the DSD Receiving Detail screen. As soon as the delivery is created, a PO for it will get created internally and the user can view it using the Purchase Order dialog.
Customer Orders
DSD Receipts that are affiliated with a customer order will be denoted by having the customer order indicator checked. The customer order indicator will be displayed on the DSD Receiving List screen. The user will be able to filter on DSD Receipts that are for customer orders as well as search for receipts that are for specific customer order fulfillment orders.
For additional details, see the Multi Leg Orders section in Chapter 20, "Customer Order Management."
The DSD Receiving List Filter screen is accessed by clicking the Filter button from the DSD Receiving List screen. By default, the DSD Receiving List screen lists the active deliveries; the user can use this filter to search for deliveries on various other criteria. After applying the filter, the user will be returned to the DSD Receiving List screen with the deliveries displayed based on the entered criteria. The user can use the Reset button on this screen to reset all the filtering criteria to default values.
This popup screen appears when the user selects the Create Receipt button on the DSD Receiving List screen to create an on the fly receipt that does not have a PO in SIM.
The user can enter the supplier ID, or click the Ellipsis button to open the supplier lookup window and select the supplier.
After the user clicks Apply, it takes the user to the DSD Receiving Detail window to create new containers and do detailed item level receiving. See "DSD Receiving Detail."
The selected supplier must be allowed to create new Purchase Orders or the "Ignore the Supplier DSD indicator to create a PO on the fly" parameter has to be set to Yes to receive a delivery without a PO from that supplier.
The user can see the DSD Receiving Detail window for all type of deliveries. It appears under the following conditions:
When the user double clicks the delivery from the DSD Receiving List screen
When the user selects the Create Receipt button from the Purchase Order Detail screen
After selecting the supplier, when the user selects the Create Receipt button from the DSD Receiving List to create an on the fly delivery
If the user is receiving a delivery with an ASN or Dex/Nex type of delivery, it shows the containers. The user has to select the container and double click to go to the DSD Receiving Container Detail window to do the detailed item level receiving. With the exception of Dex/Nex deliveries, the user can also create a new container using the Create Container option which takes the user to the DSD Receiving Container Detail window to receive unexpected containers or when adding a container for a delivery without ASN.
This screen shows zero containers in case the user is creating a new receipt without a PO or with a PO and no ASN. The user has to click Create Container in that case to start the receiving process.
On this screen, the user can also select to do other operations by selecting the respective button:
Info: The user can click the info button to enter the invoice particulars. More details are explained in the later part of this guide.
Default Qty: The default quantity button will help the user to default the remaining expected quantity to the received quantity in the containers that are new and in progress. The system will not default the quantities for the items that are processed earlier and contains a value including zero. This button is not enabled for the on the fly delivery.
Confirm Delivery: Upon selecting this button, the system will confirm the delivery. This will move all the containers to "received" or "missing" if the container does not have any received or damaged quantity.
Reject Delivery: The user can click the Reject Delivery if the delivery has to be rejected. This will reject the delivery and move all the containers to canceled status and move the status of the delivery to Rejected. This will also remove any UINs present in the delivery. Rejection of a delivery is possible only for the deliveries that are in "In Progress" or "New" status and it will not allow rejecting if there are any received or damaged containers in the delivery.
Delete Delivery: The user can click the Delete Delivery if the delivery has to be deleted. This will cancel the delivery and all the containers inside the delivery.
Customer Orders: The user can select this button to view the customer orders associated to the delivery. More details are explained in the latter part of this guide. This button is not enabled for on the fly delivery.
Ext. Adjustment: The user can view any adjustments done by the external system for the delivery. More details are explained in the latter part of this guide.
Notes: The user can use this button to enter any notes for the delivery. More details are explained in the latter part of this guide.
Print: The user can use this button to print the delivery. Upon selecting the button, the system opens the Report Selection window for the user to select the format and the printer.
Header fields on this screen are as follows:
| Field | Description |
|---|---|
| ID | Unique ID created by SIM. |
| ASN | ASN number of the delivery. Data shown only if it is applicable. |
| Supplier | The supplier from whom the store is receiving this delivery. |
| Purchase Order | The purchase order number generated by SIM, or the purchase order number provided by an external system. |
| Status | The status of the delivery/receipt. |
| Expected Date | Estimated time of arrival. Data shown only if applicable. |
| Received Date | The date the receipt is first created. |
| Received User | The SIM user who received the delivery. |
| Total Container SKUs | Sum of container level unique items in the delivery. |
| Containers | Total number of containers in the delivery. |
| Documents | Total number of purchase orders associated with this delivery. |
Detail fields on this screen are as follows:
| Field | Description |
|---|---|
| Container ID | Unique ID created by SIM or container ID that came in ASN from the external vendor system. |
| Status | Current status of the container. |
| Number of SKUs | Number of SKUs present in the container. |
| Number of Docs | Total number of purchase orders the container is associated to. |
| Customer Order | Indicates whether customer order exists. |
| UIN Required | Indicates whether UIN required items present in this delivery. |
Delivery Rejections and Supplier Discrepancy Check
The system does the discrepancy check based on the supplier level "Supplier delivery exception" attribute. The attribute can indicate to "Allow any discrepancy," "Do not allow any discrepancies," or "Allow overages but not short receipts." Discrepancy checking only happens for those deliveries that have an expected quantity; this includes DSD deliveries for Dex/Nex and PO deliveries with or without ASN. Deliveries on the fly do not check for any discrepancies.
Discrepancy checking is done at the container level against the expected quantity. For an ASN or Dex/Nex, this would be the expected quantity of the container, while for a delivery on the fly against an existing PO, it is the remaining quantity of the PO.
The user has the ability to override the discrepancy check at the container level based on the "Override supplier discrepancies" security permission. Once a container is moved to submitted or received, no additional validation is performed.
Depending on the type of DSD, some containers will move to submitted and require the whole delivery to be confirmed, while others will move to a received status. The reason for this is transactional integrity.
With an ASN, the received container can move to a received status, which indicates that the Stock on Hand is updated and the merchandising system is notified that the container is received. The transaction will automatically move to confirmed when all containers are received.
Dex/Nex and PO on the fly do not update inventory until the delivery is confirmed, hence they move to a submitted state. At that time, the delivery transaction is confirmed, the merchandizing system is notified of the whole delivery, inventory is updated and the submitted containers move to received.
PO deliveries without an ASN fall into a unique case. If there is a discrepancy check performed, the container will move to submitted and require the delivery to be completed for any updates and integration. If on the other hand, the supplier does not require a discrepancy check or the supplier allows overage and it is a short receipt that is overridden, the container will be moved to a received state, the Stock on Hand will be updated, and the merchandizing system will be notified when it is confirmed. Manual closure of the delivery transaction is required in all cases because additional containers may need to be added.
The following table describes the state the container moves into or when the user is stopped when confirming a container.
| PO on the fly | PO without ASN | PO with ASN | DEX NEX | |
|---|---|---|---|---|
| Discrepancy check on carton confirm | No | Yes | Yes | Yes |
| Supplier Restricted, carton confirm status | Submitted | Submitted | Received | Submitted |
| Supplier Restricted and No override discrepancy allowed | Submitted | Hard Stop | Hard Stop | Hard Stop |
| Supplier Restricted and override discrepancy allowed | Submitted | Confirm Prompt
Submitted |
Confirm Prompt
Received |
Confirm Prompt
Submitted |
| Supplier Allow Overage, No override allowed and carton has short receiving | Submitted | Hard Stop | Hard Stop | Hard Stop |
| Supplier Allow Overage, override allowed and carton has short receiving | Submitted | Received | Received | Submitted |
Customer Orders
The DSD Receiving Detail has a customer order field at the container line level to indicate if the container is for a customer order. If all items in the container are for a customer order, it will be Yes. If no items in the container are for a customer order, it will be No. Lastly, if some items are for a customer order and some are not, it will be Mixed.
Selecting a container and then clicking the Customer Order button will display the customer orders for that container. It will display the Customer Order and fulfillment order IDs, along with the container ID, status, total SKUs, and comments for the customer order.
Upon confirmation of the receipt, the user will be prompted that the delivery is for a customer order. This will allow the user to set it aside.
The user can drill down into the details of the container by selecting the container; the system will navigate to the DSD Receiving Container Detail. The DSD Receiving Container Detail has a customer order field at the header to indicate if the container is for a customer order: Yes meaning for customer order, No meaning there are no customer orders, and Mixed meaning some items are for customer orders and some are non-customer orders.
For additional details, see the Multi Leg Orders section in Chapter 20, "Customer Order Management."
This screen is accessed from the DSD Receiving Detail screen when the user clicks the Info button.
This screen provides the header info such as delivery ID, ASN, supplier, number of containers, status, expected date, and so on. It allows the user to enter the invoice particulars of the delivery.
The user has to complete the fields that are enabled and then click Save to return to the DSD Receiving Detail window.
Invoice Number - Enter the invoice number for the delivery.
Invoice Date - Enter or select the date of the invoice.
Invoice Cost - Enter the total cost of the delivery.Carrier Entity - Enter the name of the carrier.
Carrier Type - Select the carrier type from the drop-down list.
Carrier Code - This field is enabled based on the selection in the Carrier Type field. Enter the code for the carrier. Not enabled for Corporate.
License Plate - Enter the license plate number of the carrier's truck.
From Address - Enter the address from where the delivery came. This field is enabled based on the selection in the Carrier Type field. Not enabled for Corporate.
Freight ID - Enter the freight code.
Bill of Lading - Enter the bill of lading.
It will be in view-only mode if the delivery is in Canceled, Received, or Rejected state.
This screen is accessed from the DSD Receiving Detail screen or DSD Receiving Container Detail screen when the user clicks the Notes button. This screen is used to mention any notes about the delivery which would be useful later for audit purposes. In this screen, the user can add new notes or view the existing notes.
It will be in view-only mode if the delivery is in Canceled, Received, or Rejected state.
This screen appears when the user selects the Customer Orders button on the DSD Receiving Detail screen. It will display the customer order and fulfillment order IDs, along with the container ID, status, total SKUs, and comments for the customer orders associated with the delivery. If there is no customer order associated, it will display an error upon selecting the button.
The user can access this window from the DSD Receiving Detail screen by selecting the Ext. Adjustments button. This view-only screen displays the Purchase Order Number, Date, Item, Description, and adjusted quantity for the external receiver adjustments that exists for the delivery. Users will be able to access this screen only when there are any adjustments created for the delivery from the external system. SIM adjusted deliveries are not shown here.
This screen is accessed when the user clicks Create Container or doubled clicks a container on the DSD Receiving Detail. This is the screen seen by the user for detailed item level receiving irrespective of the type of deliveries.
This screen displays the contents and details for a container on an ASN, or on the fly / Dex/Nex delivery. It is possible to mark damages for an item and receive item quantities. All this information is initially coming from the supplier ASN with the exception of the received and damaged cases. For a new ASN or Dex/Nex based delivery, the items from the container are pre loaded on the detail section from the source. Depending on system options, the user is able to add additional items to the container.
For a new container created for the on the fly delivery, the user can add/scan the items to receive.
For a new container created for a PO based but no ASN, the user can use the document option or add/scan item to add items to receive.
Containers can have the following states:
New : Containers that are still not started for processing
In Progress : Receiving process started
Missing: No items received and delivery is confirmed
Damaged: If the container contains any damaged item
Received : When the container is confirmed
Submitted : When the supplier discrepancies is not allowed for deliveries with PO/ASN if the delivery type is Dex/Nex or on-the-fly
Canceled: When the container is deleted
On this screen, the user can select the respective buttons to perform the following functions:
Info: The user can select this button to enter the container information. For more details, see "DSD Receiving Container Info."
Add/Scan Item: The user can select this button to enter the items to receive or add new items to the container.
Remove Item: The user can select the line item that has to be removed and click Remove Item.
Document: The user can select this button to add the items from the Purchase Order. Refer the Document Selection section for more details. This button is not enabled for the on the fly delivery.
Default Qty: The user can select this button to default the remaining expected quantity to received quantity and populate on the screen. Default Qty sets the status of the integrated UINs to In Receiving for the delivery. In addition, a validation check is performed to ensure the expected quantity matches the serial numbers for items, if that is not the case, the user will not be allowed to receive all. If there are no UINs available for an UIN required item, the quantity is set to zero. This button is not enabled for the on the fly delivery.
Clear Qty: The clear qty button can be used by the user to clear all the received quantities and populate zero quantity to the items.
Confirm: Upon selecting the Confirm button, the user confirms the container receipt. After selecting to confirm, the container will be received and cannot be edited.
Delete: The user can use the delete button to delete the current container. The container will be canceled after user confirms to delete the container.
Notes: The user can use this button to enter any notes for the delivery. See "DSD Receiving Notes."
Print: The user can select this button to print the delivery. Upon selecting the button the system opens the Report Selection window for the user to select the format and the printer.
Ext. Attributes: The user has to select a row item and click this button to enter the extended attributes for an item. This window captures additional information about an item. If the extended attribute is not configured for the item, the system will display an error upon selecting this button.
In general, if a PO was created by the merchandizing system, SIM does not allow the user to edit the cost as it was defined by the external system. SIM will also not communicate any cost information to the merchandising system.
If the delivery is on the fly or Dex/Nex, SIM will use the cost coming from the dex/nex file, or default based on item supplier country information. It is possible with the right permissions to edit this cost and the cost can be communicated to the external system.
The ability to view or edit the cost is configurable with the right permissions.
Header fields on this screen are as follows:
| Field | Description |
|---|---|
| Container ID | Unique ID created by SIM or container ID that came in ASN from the external vendor system. |
| ASN | ASN number of the delivery. Data shown only if it is applicable. |
| Supplier | The supplier from whom the store is receiving this delivery. |
| Customer Orders | Indicates whether customer order is associated to this delivery. |
| Receipt ID | Unique Receipt ID created by SIM for the delivery. |
| Status | Current status of the container. |
| Reference Container | Any reference container provided for this container in the info. |
| Display Only Discrepancies | The user can use this check box to filter only the items that are in discrepancy. Not enabled for on the fly delivery. |
| Expected Date | Estimated time of arrival. Data shown only if applicable. |
| Received Date | The date the receipt is first created. |
| Received User | The SIM user who received the delivery. |
| UOM | The user can select the UOM at the header level to apply that for the items received. Changing this will apply to all the items in the detail. |
| Total SKUs | Total number of items present in this container. |
| Ordered Qty | Total ordered quantity in this container. |
| Expected Qty | Total expected quantity in this container. |
| Total Qty | Total received quantity in this container. |
Detail fields on this screen are as follows:
| Field | Description |
|---|---|
| Container ID | Unique ID created by SIM or container ID that came in ASN from the external vendor system. |
| Status | Current status of the container. |
| Number of SKUs | Number of SKUs present in the container. |
| Number of Docs | Total number of purchase order the container is associated to. |
| Customer Order | Indicates whether customer order exists. |
| UIN Required | Indicates whether UIN required items present in this delivery. |
| Item | Item ID received in the container. |
| Item Description | Description of the item. |
| Primary VPN | Primary VPN of the item. |
| Order | Purchase Order number that came from external system or SIM created. |
| UOM | UOM of the item received. |
| Pack Size | The user can enter the number of packs in a case. |
| Rem | Remaining quantity of that item in the container. |
| Exp | Expected quantity of that item in the container. |
| Rcv | Received quantity. This field is editable and the value can be entered by the user to input the received quantity of the item. Quantity entered in the Item/Scan is populated in case the item was added using this button. In case the user has used the Default Qty option, the field is populated with the remaining quantity. |
| Dmg | Damaged quantity. This field is editable and the value can be entered by the user to input the received quantity of the item that damaged. Quantity entered in the Item/Scan is populated in case the item was added using this button. |
| Orig Cost | This shows the original cost of the item. |
| New Cost | The user can enter the cost of the item at which the item is received from the supplier. This is allowed for on the fly and Dex/Nex based deliveries. |
| UIN Qty | If an item requires serial number type unique identification numbers (UIN), this field displays the number of items for which UINs have been scanned or entered. |
This screen is accessed from the DSD Receiving Container Detail screen when the user clicks the Info button. It will be in view mode if the delivery is in Canceled and Completed state. This screen provides information about the container and allows the user to enter the following details.
Reference Container: This field is used to identify a misdirected container.
Receive on Shop Floor: Indicates whether the delivery will be received on the shop floor instead of automatically receiving into the back room. This allows the user to Top off the shop floor first, depending upon how it is configured.
Damage Remaining: When this field is checked, the remaining items in the container will be marked as damaged.
Damage Reason: Enter the reason for the damaged container.
SSCC: Enter the GS1 Barcode container ID.
Tracking ID: Enter the identifier assigned to a container when shipping. This can be used to track the location of the delivery.
This screen is accessed from the DSD Receiving Container Detail screen when the user clicks the Notes button. The Container ID is added before the notes; the user can choose to keep it or change it. This helps to keep notes for the container for later Audit purposes.
This pop-up can be reached through the DSD Receiving Container detail screen by clicking Document button. This popup will show the purchase orders and, when the user selects the purchase order, the items in the purchase order are shown. The user can add it to the delivery by selecting the PO and its items and apply. Multiple selections of items are allowed.
This screen is accessed when the user selects the Purchase Order button from the Shipping / Receiving screen.
The Purchase Order List is a screen that allows users to view purchase orders placed to the suppliers to supply goods for the user's store. The default is to display the list of all active status, that is "Approved" and "In Progress" purchase orders. A filter screen is available to filter out the records.
This screen provides the following header level information about the Purchase Order including the ID which is SIM generated, External ID, Supplier, Create date of the PO, current status of the PO, and also indicates whether the customer order is associated with the PO.
From the Purchase Order List screen, a user can double click a Purchase Order to go the Purchase Order Detail screen to view the details for the PO.
Purchase Orders created internally in SIM for on the fly deliveries are also shown in this list.
Customer Orders
Purchase Orders that are affiliated with a customer order will be denoted by having the customer order indicator checked. The customer order indicator will be displayed on the Purchase Order List and Detail screens. The user will be able to filter on purchase orders that are for customer orders as well as search for purchase orders that are for specific customer order fulfillment orders. The Purchase Order Detail screen will display if it is for a customer order at the header along with the customer order fulfillment order IDs. For additional details, see the Multi Leg Orders section in Chapter 20, "Customer Order Management."
This is the Purchase Order List Filter screen. It is accessed by clicking the Filter button from the Purchase Order List screen. The user can filter on various search criteria. After applying the filter, the user will be returned to the Purchase Order List screen with the Purchase Orders displayed per the entered criteria.
The Purchase Order Detail is accessed when the user double clicks the Purchase Order record from the Purchase Order list screen.
The Purchase Order Detail screen displays all of the Purchase Order header and item details for the selected purchase Order. This screen is view only for informational purposes.
The header contains the header information including: Supplier, SIM created unique Id, External Purchase Order ID, Customer Order (if applicable), Fulfillment Order (if applicable), current status of the PO, Create Date, Not before date, Not after Date, and UOM. The user can select the UOM from the dropdown to view the items based on the selected UOM.
The ordered quantity is the total quantity remaining in the order for all the items, the expected quantity is the total ordered quantity in the order for all items and the received quantity is the total of how many quantities quantity received.
The detail level has the item, description, Pack Size, as well as the On Order, Expected and Received.
The user can create a receipt from the Purchase Order Detail. The Create Receipt button will navigate to the DSD Receiving Detail screen with the existing Purchase Order applied to the delivery. The user can create container and start the receiving process as previously described.
The Adjust option on the DSD Receiving Container Detail screen allows the received container to be reopened for receiving. The system allows the user to add items, delete items, modify the quantity, save, or confirm the delivery. All options are available as if the container was never received.
It is not allowed to move a container back to In Progress if UINs that were in the container have been processed in another transaction.
The period at which the user is allowed to adjust the deliveries from the time the receipt is confirmed is based on the parameter and also the user should also have security permissions to edit the delivery. This option is applicable only on the PC and not on the handheld. Once the container is moved back to "In Progress," the user can work on it as if it was never received.
Direct Exchange (DEX) and Network Exchange (NEX) receiving are uniform communications standards. DEX is the means through which a supplier, using a handheld device, can exchange electronic invoicing information with a store's direct store delivery (DSD) system. NEX differs in its delivery system, using the web as opposed to a hand-held cradle.
SIM is designed to support the integration of a supplier's DEX/NEX information into direct delivery-related screens, thereby simplifying the receiving process. Data is transferred to a store's DSD system using the Electronic Data Interchange (EDI) transaction set 894 (delivery/return base record). The uploaded data will allow the store user to view, edit, and confirm the information contained in the file before receiving the direct store delivery. The system will automatically create a container and user will be able to do detailed receiving against that container.
A system option controls whether or not expected quantities are defaulted in for direct store deliveries with Dex/Nex. This allows more detailed control by the retailer. If the quantities are not automatically defaulted, the user can scan each unit individually to ensure that the correct quantities are recorded. If the quantities are defaulted, only a visual inspection can be done since scanning the item will automatically increase the received quantity.
DSD Receiving can be configured to reserve inventory for customer orders upon receiving and also to auto pick the inventory. For additional details on this process, see "Customer Orders.".
The DSD Receiving dialog in the PC allows receiving new deliveries that are in SIM via ASN or Dex/Nex or existing in progress deliveries or allows the user to create a new receipt without a PO.
The Purchase Order dialog on the PC allows viewing the Purchase Order and create receipts using the create receipt option from the PO dialog.
DSD Receiving exists only in PC and handheld.
TECHNICALSIM user can create DSD in the following ways:
With purchase order and without ASN:
Payload PODesc is consumed in SIM and the purchased order is available on the screen. The user views the purchase order on the detail screen, clicks Create Receipt and creates a direct delivery against the order. Multiple direct deliveries can be created against a purchase order.
With purchase order and with ASN:
Payload PODesc is consumed in SIM and the purchased order is available on the screen. An ASN with reference the purchase order is consumed and a direct delivery is created in SIM database. On the screen, the user selects a delivery and receives delivery.
Without purchase order:
The user manually receives a delivery and no purchase order is associated to the delivery. The user selects the Create Receipt option from the DSD Receiving List screen. The receipt of this delivery will create a PO.
Direct Deliveries have header information, container information, and detailed records information.
Business objects are used within the application code for all business processing.
| Business Object | Description |
|---|---|
| VendorDelivery | Contains header-level information about a direct delivery. |
| VendorDeliveryCarton | Contains carton-level information about a direct delivery. |
| VendorDeliveryLineItem | Contains detailed information about a direct delivery line item. |
| VendorDeliveryOriginType | Contains the method by which the vendor delivery was created: ASN, PO, DEX-NEX, or MANUAL. |
| VendorDeliveryQueryFilter | Contains values of various attribute of direct delivery query filter. |
| PurchaseOrder | Contains header level information of a purchase order. |
| PurchaseOrderLineItem | Contains line level information of a purchase order. |
| PurchaseOrderQueryFilter | Contains values of various attributes of purchase order query filter. |
This section covers integration through RIB and web services.
RMS publishes the Purchase Orders created for the direct store deliveries using RIB messages. SIM subscribes to these messages and stores them in the SIM database to enable receipt against Purchase Orders.
RMS publishes the unit cost of the item at the item/supplier/country level for SIM to use in the receiving process.
SIM publishes the receipts done against the Purchase Order to the merchandising system (Receiving message).
SIM publishes the DSD receipts created in SIM without a Purchase Order to the merchandising system (DSDReceipts and DSD Deals messages).
SIM publishes the receiver unit adjustment done for the deliveries that are already confirmed (receiving message).
SIM is also capable of subscribing to the vendor EDI ASNs through RIB using the ASN In message format.
RIB payloads are used to communicate information from SIM to external systems and from external system to SIM through RIB Integration.
| RIB Payload (Subscriber) | Description |
|---|---|
| PORef | RIB payload that contains reference level information of a purchase order.
This payload is used for removal of purchase orders. |
| PODesc | RIB payload that contains detailed information of a purchase order.
This payload is used for creation and modification of purchase orders. |
| ASNInRef | RIB payload that contains reference level information of an ASN. This payload is used for removal of an ASN. |
| ASNInDesc | RIB payload that contains detailed information about the ASN. This payload is used for creation of a direct delivery (document type= 'P') or a warehouse delivery (document type= 'D'). |
| RIB Payload (Publisher) | Description |
|---|---|
| ReceiptDesc | RIB payload that contains detailed information of the direct delivery receipt. This is published when the purchase order is not null. |
| DSDReceiptDesc | RIB payload that contains detailed information of the direct delivery receipt. This is published when the purchase order is null. |
| SOStatusDesc | RIB payload sent from SIM to convey changes in item status for a specific fulfillment order. |
| InvAdjustDesc | RIB payload that contains information about destination of the adjustment and an InvAdjustDtl. |
SIM supplies SOAP web service for the receiving of vendor deliveries (direct deliveries).
The following service operations are supported for the VendorDelivery web service.
| Service Operation | Description |
|---|---|
| lookupVendorDeliveryHeader | Retrieves basic header information for one or more vendor deliveries that match the input criteria. |
| readVendorDeliveryDetail | Retrieves detailed information about a vendor delivery. This does not contain any information about containers or items on the delivery. |
| createVendorDelivery | Creates a new vendor delivery. |
| updateVendorDelivery | Updates a vendor delivery. |
| receiveVendorDelivery | Moves all the containers to "In Progress" status and defaults the received quantities. It puts the delivery in "Received" status so that is can be confirmed. |
| confirmVendorDelivery | Confirms all the open cartons on the delivery and moves the delivery to received status, updating the inventory appropriates. |
| rejectVendorDelivery | Moves a vendor delivery to rejected status. This can only occur if none of the containers are received. |
| cancelVendorDelivery | Moves a vendor delivery to canceled status. This can only occur if none of the containers are received. |
| lookupVendorDeliveryCartonHeader | Retrieves basic header information about containers on a delivery. |
| readVendorDeliveryCartonDetail | Retrieves detailed information about a delivery container including the detailed item information. |
| createVendorDeliveryCarton | Creates a new container on a delivery. |
| updateVendorDeliveryCarton | Updates details information about a container and its items. |
| confirmVendorDeliveryCarton | Confirms the receipt of the container. |
| cancelVendorDeliveryCarton | Cancels a container on the delivery. |
| openVendorDeliveryCarton | Reopens an already confirmed container allowing it to be received again. |
| lookupVendorDeliveryOrders | Retrieves custom order information associated to the specified vendor delivery. |
The following batch is available:
| Batch Name | Description |
|---|---|
| DEX/NEX File Import Batch | This batch imports the direct delivery shipment records (PO, shipment and receipt) from Dex/Nex files in the DEX/NEX directory into SIM.
SIM processing creates a DEX/NEX direct delivery for the uploaded data. This process allows the store user to view, edit, and confirm the information contained in the DEX/NEX file before approving, so the information can become an in-progress direct delivery. |
| DSD Receipt Close Batch | This batch attempts to automatically confirm and open DSD that is a certain number of configurable days past its due date. |
The following database tables are used:
| Table Name | Description |
|---|---|
| DSD | Contains header level information of a direct delivery. |
| DSD_CARTON | Contains carton level information about a direct delivery. |
| RTV_SHIP
DSD_LINE_ITEM |
Contains line item level information about a direct delivery. |
| DSD_LINE_ITEM_ATT | Contains information about extended attributes of a direct delivery line item. |
| DSD_LINE_ITEM_UIN | Contains UIN level information about a direct delivery line item. |
