Support for SOTPI ASN's
Symptoms: SOTPI ASN compliance requires the ability to create shipments with mixed cartons and pallets. Some pallets only, cartons on pallets and cartons only all as EDI packages on the same shipment. Solution: Write to the OrderP table in DataMasons for all packages where the EDI flag is turned on for the PKG Type that has items directly on it.
Form Studio - Update item validations to accept lot numbers
In Agility Mobile for SAP add the ability to scan a lot number as substitute to identify the item code for the following Item Validations. Inventory TransferRequestValidateItem Inventory ValidateItem Inventory ValidateItemWarehouse Packing And Shipping LoadPalletValidatePkgItem Packing And Shipping PalletBuilderValidateItem Packing And Shipping PkgValidateSalesOrderItem Production Order ProductionIssueValidateItem Production Order ProductionReturnValidateItem Purchase Order GoodsReceiptValidatePOItem Purchase Order GoodsReceiptValidatePOItemReceiving Sales Order PickListValidateSalesOrderItem Sales Order SalesOrderValidateItem
Exception when right-clicking on a linked grid
Symptoms: Clicking on the bottom empty space of the OE Pick Management without placing any data using filters throws and object not set to an instance of an object error. It would be easy enough to tell the customer not to right click on an empty disassociated grid but Don said write it up so here ya go. To Duplicate Open OE Pick Management Do not enter any data in the filter and click OK. On the bottom grid , in any open space under the fields right click. You will receive the error
Cost different on GL when unconfirm shipping after changing iminvloc cost
Symptoms: When using OE UnConfirm Ship process and Macola OE Package Settings "Cost to Use When Posting" is set to Actual. The GL dollar amount will differ if the cost has changed between Confirm Ship and UnConfirmShip processes being run. Macola posts the same dollar amount as the original confirm ship transaction. Solution:
using PO number in a Lot number works in Form Studio Not in an agility grid.
Symptom: PO lot setup in Agility/File/Options/WMS/Serial Lot Numbers/Purchase Orders/Lots uses the Purchase order from a tablelookup poordlin_sql(or hdr) ie. Year+JulianDay+poordhdr_sql.ord_no with the ord_no being padded with zeros. Produces a proper lot number when receiving through form studio (i.e(201919900015700) However, the same PO on the PO Receipts grid in Agility, when clicking on the lot field produces 201919900000000 PO Receipts grid Lot number field fails to use the Purchase order number Resolution:Order number was not getting passed into the serial-lot builder routine. fixed code to allow passing of the order number.
Form Studio crashes when you have invalid SQL in a SQL Event Action
When you have invalid SQL in a SQL Event, Lookup, Grid definition (such as an Update statement) Form Studio will crash. A warning message will now be displayed, so the application does not exit and you can remove the invalid SQL.
Form Studio - Add Terms Maintenance Options to Grids
Add Terms Maintenance Options to Form Studio Grids. When Right Clicking on a grid column header in Form Studio the Change Column Heading screen will be presented. This will allow you to assign a Term Code to the heading or enter a hard coded column header. The right click option is available when previewing a Form at design time from Form Studio.
Material Issue can generate a Cannot insert the value NULL into column error
Transactions that insert into the MCDISFIL (i.e. Material Issue) can generate a "Cannot insert the value NULL into column error" when a field was left blank and the SDK attempted to insert a NULL value in place of the empty string. dist_type,mn_no,sb_no,dp_no,job_no,ord_no,control_no,jnl_src,id_no,par_item_no
Error Bypassed When Confirm Shipping Component Items
Symptoms: When confirm shipping a parent item in Form Studio Shipping form and a lock is encountered on a component. The inventory transaction on the component will timeout but will continue processing additional components. This only happens if the component isn't the first one in the BOM. If the component is the first component and a timeout is encountered the entire process will stop. The inventory issue transaction doesn't not happen for the components where a timeout occurred but does for all others. This is causing inventory to be off for any component items that were locked. Solution: Transaction should be aborted and all transactions should be rolled back.