Information Systems:Order Allocation - Revision history

Norwinu: /* Backorders: Out-of-stock item ordered in a quantity exceeding a future shipment. */

2019-08-12T17:16:10Z

Backorders: Out-of-stock item ordered in a quantity exceeding a future shipment.

Norwinu at 00:02, 2 February 2019

2019-02-02T00:02:30Z

Norwinu at 19:56, 30 June 2016

2016-06-30T19:56:11Z

New page

Work with Active Jobs BART
11/19/15 16:11:49
CPU %: 14.4 Elapsed time: 04:17:02 Active jobs: 473

Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...
Current
Opt Subsystem/Job User Type CPU % Function Status
MONITOR2 QSYS SBS .0 DEQW
ORDALLOCFL EODJOB BCH .3 DLY-16:30:00 DLYW

Parameters or command
===>
F3=Exit F5=Refresh F7=Find F10=Restart statistics
F11=Display elapsed data F12=Cancel F23=More options F24=More keys

DMCUPALLOC (job name ORDALLOCFL) runs every 30 minutes to perform a fair allocation of stock. A future order will not drop for picking automatically - someone must do it manually. Therefore there is a period between when an item is received and when the waiting order is dropped that another order (regular) can come in and scoop the stock. If the order allocation flag on an item is set to 'Y' no orders are dropped for picking automatically. Web Orders will allow only future orders on item that have the order allocation flag set to Yes – even if there is stock on hand.

Process -

- Drop all orders possible by printing pick lists.

- Set order allocation flag to Yes for regular stock items that have no onhand, but that have open sales orders.

- Re-plan sales orders; this will change dispatch date to today for non-promo orders that have available stock. A sales order cannot be dropped for picking if the dispatch date is in the future.

- Allocate available stock to sales orders for items set for manual allocation.

- Review allocations. Remove lines for held sales orders. Remove allocations where the available stock is less than the outstanding orders. Confirm and drop anything remaining.

- Set order allocation flag to No for regular stock items with onhands, that have no open sales orders.

- If it is Monday to Friday, between 6:30AM and 4:00PM, send alerts if there is anything to be manually allocated. If available stock is less than outstanding orders, a person has to decide which orders to give the stock to. Only run this every other time through (1 hour) to give the user time to do the processing.

==Backorders: Out-of-stock item ordered in a quantity exceeding a future shipment.==

''i.e. Store orders 100, warehouse expecting 50.''

When an order is placed for a quantity which is more than we have and more than we are expecting, Eliza handles the exception (for ALL products). By default, she will usually send all of what we have to partially fill the order, and backorder the remainder. If a customer wants the quantity in its entirety in a single shipment, then she will allocate the inbound quantity accordingly (i.e. to make some available to others and to place some on hold).
* [[Order Allocation Problems]]

[[Category: IBM i]]
[[Category: Ordering]]

Sheilav at 23:23, 17 December 2015

2015-12-17T23:23:55Z

Norwinu: /* Backorders: Out-of-stock item ordered in a quantity exceeding a future shipment. */

2015-12-02T22:23:00Z

Backorders: Out-of-stock item ordered in a quantity exceeding a future shipment.

Norwinu at 22:22, 2 December 2015

2015-12-02T22:22:52Z

Norwinu: /* Backorders: Out-of-stock item ordered in a quantity exceeding quantity a future shipment. */

2015-12-02T22:22:38Z

Backorders: Out-of-stock item ordered in a quantity exceeding quantity a future shipment.

Norwinu at 22:22, 2 December 2015

2015-12-02T22:22:06Z

Sheilav at 00:13, 20 November 2015

2015-11-20T00:13:50Z

Sheilav: Created page with " Work with Active Jobs BART 11/19/15 16:11:49 CPU %: 14..."

2015-11-20T00:13:06Z

Created page with " Work with Active Jobs BART 11/19/15 16:11:49 CPU %: 14..."

New page

Work with Active Jobs BART
11/19/15 16:11:49
CPU %: 14.4 Elapsed time: 04:17:02 Active jobs: 473

Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...
Current
Opt Subsystem/Job User Type CPU % Function Status
MONITOR2 QSYS SBS .0 DEQW
ORDALLOCFL EODJOB BCH .3 DLY-16:30:00 DLYW

Parameters or command
===>
F3=Exit F5=Refresh F7=Find F10=Restart statistics
F11=Display elapsed data F12=Cancel F23=More options F24=More keys

DMCUPALLOC runs every 30 minutes to perform a fair allocation of stock. A future order will not drop for picking automatically - someone must do it manually. Therefore there is a period between when an item is received and when the waiting order is dropped that another order (regular) can come in and scoop the stock. If the order allocation flag on an item is set to 'Y' no orders are dropped for picking automatically. Web Orders will allow only future orders on item that have the order allocation flag set to Yes – even if there is stock on hand.

Process -

- Drop all orders possible by printing pick lists.

- Set order allocation flag to Yes for regular stock items that have no onhand, but that have open sales orders.

- Re-plan sales orders; this will change dispatch date to today for non-promo orders that have available stock. A sales order cannot be dropped for picking if the dispatch date is in the future.

- Allocate available stock to sales orders for items set for manual allocation.

- Review allocations. Remove lines for held sales orders. Remove allocations where the available stock is less than the outstanding orders. Confirm and drop anything remaining.

- Set order allocation flag to No for regular stock items with onhands, that have no open sales orders.

- If it is Monday to Friday, between 6:30AM and 4:00PM, send alerts if there is anything to be manually allocated. If available stock is less than outstanding orders, a person has to decide which orders to give the stock to. Only run this every other time through (1 hour) to give the user time to do the processing.

← Older revision		Revision as of 00:02, 2 February 2019
Line 43:		Line 43:
	[[Category: IBM i]]		[[Category: IBM i]]
	[[Category: Ordering]]		[[Category: Ordering]]
		+	[[Category: Sales Orders]]

← Older revision		Revision as of 23:23, 17 December 2015
Line 39:		Line 39:

	When an order is placed for a quantity which is more than we have and more than we are expecting, Eliza handles the exception (for ALL products). By default, she will usually send all of what we have to partially fill the order, and backorder the remainder. If a customer wants the quantity in its entirety in a single shipment, then she will allocate the inbound quantity accordingly (i.e. to make some available to others and to place some on hold).		When an order is placed for a quantity which is more than we have and more than we are expecting, Eliza handles the exception (for ALL products). By default, she will usually send all of what we have to partially fill the order, and backorder the remainder. If a customer wants the quantity in its entirety in a single shipment, then she will allocate the inbound quantity accordingly (i.e. to make some available to others and to place some on hold).
		+	* [[Order Allocation Problems]]

← Older revision		Revision as of 22:22, 2 December 2015
Line 33:		Line 33:

	- If it is Monday to Friday, between 6:30AM and 4:00PM, send alerts if there is anything to be manually allocated. If available stock is less than outstanding orders, a person has to decide which orders to give the stock to. Only run this every other time through (1 hour) to give the user time to do the processing.		- If it is Monday to Friday, between 6:30AM and 4:00PM, send alerts if there is anything to be manually allocated. If available stock is less than outstanding orders, a person has to decide which orders to give the stock to. Only run this every other time through (1 hour) to give the user time to do the processing.
		+
		+	==Backorders: Out-of-stock item ordered in a quantity exceeding quantity a future shipment.==
		+
		+	i.e. Store orders 100, warehouse expecting 50.
		+
		+	When an order is placed for a quantity which is more than we have and more than we are expecting, Eliza handles the exception (for ALL products). By default, she will usually send all of what we have to partially fill the order, and backorder the remainder. If a customer wants the quantity in its entirety in a single shipment, then she will allocate the inbound quantity accordingly (i.e. to make some available to others and to place some on hold).

@@ Line 38: / Line 38: @@
 ''i.e. Store orders 100, warehouse expecting 50.''
-When an order is placed for a quantity which is more than we have and more than we are expecting, Eliza handles the exception (for ALL products). By default, she will usually send all of what we have to partially fill the order, and backorder the remainder. If a customer wants the quantity in its entirety in a single shipment, then she will allocate the inbound quantity accordingly (i.e. to make some available to others and to place some on hold).
+When an order is placed for a quantity which is more than we have and more than we are expecting, it has to be allocated/handle manually. Eliza handles the exception (for ALL products). By default, she will usually send all of what we have to partially fill the order, and backorder the remainder. If a customer wants the quantity in its entirety in a single shipment, then she will allocate the inbound quantity accordingly (i.e. to make some available to others and to place some on hold).
 * [[Order Allocation Problems]]

@@ Line 36: / Line 36: @@
 ==Backorders: Out-of-stock item ordered in a quantity exceeding a future shipment.==
-'''i.e. Store orders 100, warehouse expecting 50.'''
+''i.e. Store orders 100, warehouse expecting 50.''
 When an order is placed for a quantity which is more than we have and more than we are expecting, Eliza handles the exception (for ALL products). By default, she will usually send all of what we have to partially fill the order, and backorder the remainder. If a customer wants the quantity in its entirety in a single shipment, then she will allocate the inbound quantity accordingly (i.e. to make some available to others and to place some on hold).

@@ Line 34: / Line 34: @@
 - If it is Monday to Friday, between 6:30AM and 4:00PM, send alerts if there is anything to be manually allocated.  If available stock is less than outstanding orders, a person has to decide which orders to give the stock to.  Only run this every other time through (1 hour) to give the user time to do the processing.
-==Backorders: Out-of-stock item ordered in a quantity exceeding quantity a future shipment.==
+==Backorders: Out-of-stock item ordered in a quantity exceeding a future shipment.==
 i.e. Store orders 100, warehouse expecting 50.

@@ Line 16: / Line 16: @@
  F11=Display elapsed data   F12=Cancel   F23=More options   F24=More keys
-DMCUPALLOC runs every 30 minutes to perform a fair allocation of stock.  A future order will not drop for picking automatically - someone must do it manually.  Therefore there is a period between when an item is received and when the waiting order is dropped that another order (regular) can come in and scoop the stock.  If the order allocation flag on an item is set to 'Y' no orders are dropped for picking automatically.  Web Orders will allow only future orders on item that have the order allocation flag set to Yes – even if there is stock on hand.
+DMCUPALLOC (job name ORDALLOCFL) runs every 30 minutes to perform a fair allocation of stock.  A future order will not drop for picking automatically - someone must do it manually.  Therefore there is a period between when an item is received and when the waiting order is dropped that another order (regular) can come in and scoop the stock.  If the order allocation flag on an item is set to 'Y' no orders are dropped for picking automatically.  Web Orders will allow only future orders on item that have the order allocation flag set to Yes – even if there is stock on hand.
 Process -