Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. If Daily schedule is not defined on any day, the store scheduled is marked as Unscheduled for that day. The Store Schedule needs to be defined by Store initially or else the Ad-Hoc Schedule will also not be considered even if it is defined for that day.

  2. If the Store is marked as Closed in Store schedule screen or if the current time has passed from the Store Closing time defined in store schedule, then the store will be marked as OFFLINE and the store will not be eligible to get new orders.

  3. Ad-Hoc store schedule will take precedence over daily store schedule every time.

...

This implies that if the MAT defined for any store in SFS masters will be is greater than the total active time of store then the Store will not be eligible for hopping process.

...

  1. REQUESTED - The location has been requested to fulfill the sub-order.

  2. ACCEPTED - The location has ACCEPTED to fulfill the entire sub-order. In the case of WMS, an order moves to this status on ORDER_ACK.

  3. REJECTED - The location has REJECTED to fulfill the entire order

  4. PARTIALLY_ACCEPTED - The location has accepted to fulfill one or more qty but not all the qty of the SKU line item of sub-order.

  5. AUTO_REJECTED -  The store did not accept to fulfill the sub-order within the MAT time and sub-order got auto-hopped by OMS.

(Screenshots Required of Suben)

In Outward Orders section, there is a new status SPLIT_THRESHOLD_BREACHED added. If an Outward order is retried 20 times to be hopped to various fulfillment locations but all locations are disabled with Splitting Allowed in CIMS then the status of Outward Order will be marked as SPLIT_THRESHOLD_BREACHED.(Screenshots Required of Outward order screen)

Info
  1. For Sub Orders being fulfilled from  WMS, 

    1. Sub Order Acceptance will be AUTO. This means WMS need not give the explicit acceptance for a Sub Order to OMS. 

    2. WMS ORDER_ACK will be treated as an Acceptance by itself in OMS. On ORDER_ACK the Sub Order Accept Status will move to ACCEPTED.

  2. For Sub Orders being fulfilled from SFS, 

    1. Sub Order Acceptance will be MANUAL. This means SFS need to give explicit acceptance/rejection for the Sub Order to OMS within the expected MAT

...

  1. Outward Order gets created in OMS.

  2. Sub Orders get created in OMS after splitting of Outward Orders.

  3. Sub Orders get synced to SFS.

  4. SFS Accepts / Rejects the Sub Order. In order to accept/reject, user can follow below mentioned steps.

    1. Go to Accept Orders under Inventory & Order section in Increff SFS. (Screenshot of Accept orders screen is required)

    2. User can different filters like From Date, To Date, Channel, Status (ACCEPTED,REJECTED,PARTIALLY_ACCEPTED, Sort By (Order ID,ORDER_TIME,REQUIRED_TIME), Sort Order (Ascending/Descending), Page Size to check all the orders which needs to be Accepted/Rejected by Store.

    3. All Orders which are eligible for Acceptance / Rejectance for that Store will be displayed with the Order Status next to it.

    4. Click on Accept button which will display +/- Sign buttons at top right of the screen and Accept button at bottom of screen.

    5. Enter the Qty you want to Accept and Click on Accept button at botttom. If Qty entered is 0, the complete order will be considered as Rejected

  5. Available Inventory gets allocated to Sub Order which is Accepted by store in OMS.

  6. QTP is reduced for the qty’s being rejected in OMS and deallocation happens.

  7. Following cases happen afterwards:

    1. If OMS is splitting routing source 

      1. Quantity that is getting rejected also gets increased in REJECTED inventory bucket to underexpose the inventory for OMS Hopping logic so that two stores do not get stuck in an infinite loop for hopping the same sub orders again and again.

      2. Seller Cancellation won’t be allowed from OMS UI until the Sub Order is in UNFULFILLABLE status.

      3. Rejection will lead to a hopping trigger, but not auto seller cancellation

      4. Acceptance and Rejection are not communicated to channel

    2. If OMS is not splitting and routing source

      1. Rejection will lead to Auto seller cancellation

      2. Acceptance and Rejection are not communicated to channel

      3. Seller Cancellation won’t be allowed from OMS UI until the Sub Order is in UNFULFILLABLE status.

  8. OMS communicates to CIMS the current Accepted Quantity, Rejected Quantity, Seller Cancelled Quantity, Customer Cancelled Quantity.

...

  1. Go to View Client/Channel

  2. Select a channel for which the fulfillment location Splitting Allowed should be changed.

  3. Go to Associated Locations section for this channel.

  4. Select Edit Location button on the right side of any fulfillment location.

  5. Select YES in Splitting Allowed value if the fulfillment location is eligible for Splitting or else select FALSE (Screenshot required).

  6. Click on Update to save the changes for that fulfillment location.

...