Service Request or Support: Three Square - SR-0002934 - Ceres 5.1 Upgrade w/AGI Web
Issues addressed:
1. When a pallet is specified on an Agency Order and Inventory Picks are created, the pick line
information is sent to AGI. Once the pick line has been handled and communicated back to Ceres,
a quantity available calculation is run before assigning the “Qty. to Handle” on the pick lines. This
quantity available calculation incorrectly determines the pallet to have a zero quantity available.
This manifests with an WMS Integration Error Log of “Insufficient Available Quantity”.
2. Pallet quantity mismatches between Ceres and AGI can lead to a WMS Integration Error Log of
“Insufficient Available Quantity”. When Ceres has the pallets quantity on hand as zero and AGI
sends a negative adjustment, Ceres will log an error because there is no quantity on the pallet to
negatively adjust.
3. Blocked items cause the WMS Job Queue to an error state. Adjustments sent from AGI to Ceres
for items that are blocked encounter an error when attempting to create the item journal entry as
transactions are not allowed for blocked items. This error is unhandled and results the job queue
failing to the error state.
4. A negative adjustment pertaining to a Pallet whose Lot is past its consume by date result in a WMS
Integration Error Log of “Insufficient Available Quantity”. This occurs when the transaction date
sent from AGI is greater than the Lot’s consume by date as Ceres will calculate the pallet’s
available quantity as zero.
5. Erroneous errors “Pallet Not Found” and “Bin Not Found” are recorded against an outbound
inventory pick transaction.
6. AGI has a 36-character limit for Agency Name and Shipping Address data. Ceres allows these two
elements to contain up to 50 characters.
7. When changing Bin Type with WMS Setup NOT enabled, the confirmation "Changes to the Bin
Type Code are not sent to AGI. Please manually update AGI ...". If the "Exclude from WMS" flag
is set at the Location, the confirmation is not generated.
8. For an unknown reason, AGI is sending Pallets to Ceres to be picked that are long since
consumed. When this occurs, Ceres throws and error in the form of “The Quantity of X is greater
than the Available Quantity of Y.” which in turn forces the AGI Job Queue to the Error state.
9. Data for item quantity reconciliation is sent to Ceres. In many cases, the quantity sent from AGI
matches the quantity recorded in Ceres. In these cases, it is desired that a Reconciliation journal
entry is not created in Ceres.
10. Outbound (from Ceres) WMS Queue entries can force the WMS Job Queue into the error status.
This can occur when a WMS Queue does not have any related request body data.
11. When the AGI system communicates an Inventory Pick action to Ceres, an inbound WMS Queue
entry is created in Ceres having an Adjustment Type of “Invt. Pick”. When the WMS Queue entry is
processed by Ceres, it is possible to report one or more errors regarding the Inventory Pick action.
For example, the “Insufficient Available Quantity” error may be reported. It is desired that Ceres
does not allow the posting of Inventory Picks when they have one or more related WMS Queue
related errors.
12. The “Delete Invt. Pick on Post” flag was incorrectly added to the Inventory Setup table and page.
As there is no functionality related to this flag, it should be removed.
13. The "Post Phys Invt. Reconciliation" flag was incorrectly added to the Location table and card
page. This field and its intended functionality will be considered for future inclusion. In the
meantime, it should be removed from the Location Card page.
14. Ceres does not allow for the movement of a pallet when the pallet is represented on one or more
transactions. This can cause errors in Ceres as follows:
- The WMS system sends a pallet movement to Ceres.
- The movement fails in Ceres due to the pallet being specified on one or more transactions.
- The WMS system next sends and Inventory Pick update to Ceres. This pick update references the new Location/Zone/Bin (where the failed movement was intended to move the pallet). Being that the pallet was not recorded into the new Location/Zone/Bin within Ceres, the pick documents cannot be processed.
15. Currently, Ceres does not allow a WMS Queue with a status of Pending to be archived. In some
cases, such as malformed data, the WMS Queue simply cannot be processed. It is desired to
allow the archive of such WMS Queue entries.
16. When an Agency Order is excluded from WMS but is within a WMS enabled location, Ceres does
abide by the location’s “Default Qty. to Handle on Pick”. The Inventory Pick generation for Agency
Orders that are excluded from WMS should behave as if the related location was excluded from
WMS.
17. In some cases, the attempted communication of an Inventory Pick to the WMS system can result
in the 400 bad request response from the WMS system. A common reason for this error is missing
required data. Ceres should be updated to trap required data that is missing and create the WMS
Queue entry in the failure status along with errors communicating the missing data.
18. WMS Queue entries can be created prematurely. Conditions which determine whether a given
pick line is eligible to be sent to the WMS system are checked after Ceres creates an outbound
WMS Queue entry for Inventory Picks. If any one of the conditions are found to be true, line buffer
data is not created. This results in a WMS Queue entry having no related line buffer data.
19. Movements sent to Ceres by the WMS are processed via the Item Reclass. Journal. Errors can
be encountered when Ceres attempts to post the Item Reclass. Journal. In such cases, the error is
not handled properly in that the WMS Queue record is not set to the Failure status nor is a WMS
Integration Error Log entry created to communicate the issue.
Objects Affected:
Type ID Name
Table 83 Item Journal Line
Table 313 Inventory Setup
Table 5740 Transfer Header
Table 7354 Bin
Table 14012540 WMS Integration Queue
Table 14012541 WMS Integration Buffer
Page 461 Inventory Setup
Page 5703 Location Card
Codeunit 7322 Create Inventory Pick/Movement
Codeunit 7323 Whse.-Act.-Post (Yes/No)
Codeunit 14012380 WMS Outbound Transfers
Codeunit 14012381 WMS Inbound Transfers
Codeunit 14012383 WMS Process Queue
This release presents a change in system usage methodology. The following procedure documents were updated accordingly.
1. Procedure Document Name
Resolution: Ceres was enhanced as noted below.
1. The quantity available calculation was updated so that it does not include the pick line’s own
demand when calculating demand for the pallet.
2. Before Ceres processes a negative adjustment sent by AGI, Ceres will check the pallets quantity
on hand. If that quantity is zero, Ceres will not create or execute the adjustment. The WMS Queue
record will be processed successfully and archived.
3. Before Ceres processes an adjustment, Ceres will verify that the item involved is not Blocked. If
the item is blocked, the attempt to create an item journal entry will be aborted and the WMS Queue
placed in the error status. The accompanying message will be in the form of “Item XYZ is Blocked.
Transactions are not allowed.”
4. When AGI communicates a negative adjustment to Ceres, Ceres will determine whether the
related pallet exists on any other transactions. If the pallet does not exist on other transactions but
the pallet’s Lot is past its consume by date (according to the AGI transactions date), the negative
adjustment will be permitted to process.
5. The erroneous errors were addressed by first verifying that the value provided to retrieve the Bin or
Pallet is not blank.
6. Agency Name and Shipping Address data is truncated to 36 characters before it is sent to AGI.
7. The WMS confirmation message was suppressed when “Enable WMS Integration” is not enabled
on WMS Setup.
8. The condition that allowed the noted error to be encountered was updated such that if a pallet is
not open (e.g. all of its quantity has been consumed), Ceres will not attempt to update the
Inventory Pick line but rather will log the error “Insufficient Available Quantity” against the WMS
Queue entry. This approach prevents the WMS Job Queue from being forced into the Error state.
9. A reconciliation quantity received from AGI that matches the quantity recorded in Ceres will no
longer create a Reconciliation journal entry in Ceres.
10. Ceres was enhances such that outbound (from Ceres) WMS Queue entries lacking related
request body data do not force the Job Queue into the error status.
11. Resolution: Ceres was enhanced such that an Inventory Pick having one or more related WMS
Queue errors is not allowed to be posted. In such cases, an error such as the one shown below
will be displayed. See the noted procedure document for additional information.
12. The “Delete Invt. Pick on Post” flag was removed from the Inventory Setup table and page.
13. The "Post Phys Invt. Reconciliation" flag was removed from the Location Card page.
14. Ceres was enhanced to allow for the movement of a pallet when the pallet is specified on one or
more transactions. The transactions are then updated to reflect the new Location/Zone/Bin. Note –
being that Transfer Order lines cannot contain a mixture of locations, nor differ from the Transfer
from Code, Transfer-to Code, or In-Transit Code, (thus cannot be updated based on WMS
Movements), logic was added to the Transfer Order header to prevent the creation of a Transfer
Order if it involves WMS enabled locations.
15. Ceres was enhanced to provide the ability to archive a WMS Queue entry when it is in the
Pending status.
16. Ceres was enhanced to handle the pick generation process for an Agency Order that is excluded
from WMS but is within a WMS enabled location as if the related location was excluded from
WMS; including abiding by the “Default Qty. to Handle on Pick” configuration.
17. Ceres was enhanced to trap required data that is missing and create the WMS Queue entry in the
failure status along with errors communicating the missing data.
18. Ceres was enhanced such that a WMS Queue entry is not created until after the conditions have
been determined.
19. Ceres was enhanced such that posting errors are trapped and reported, the WMS Queue is set to
the Failure status, and a WMS Integration Error Log entry is created to communicate the issue.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article