Only the first carton reference field is being sent to shiprush.
Symptoms: To duplicate create an order in Macola with any two items. set the ship via to either UPS or FedEx In Agility/File/Otions/Pick Pack/Reference Fields, set a reference field for all to be the Item_no from the Oeordlin for both FedEx and UPS. In Agility using PP4(Pkg Pick/Pack and Ship) create a shipment with two separate cartons for each item on the order. Upon shipping UPS/FedEx, and on our splash screen, click special shipment. Notice on the packages in the upper right ShipRush screen that both packages have the same reference and both references are the first Item_no. According to the customer this reference was correct until the 564 update.
Create UPS Validation class in Wisys.Shipping
Symptoms: Create UPS Validation class in Wisys.Shipping. Wisys.Shipping.UPSAddressValidation class was created to validate addresses when shipping via UPS. Wisys.Shipping.UPSAddressValidation.ValidateAddress method can be called to validate an address entry. A valid UPS AccessLicenseNumber and Password are required.
Packing Kits
Symptoms: When shipping a kit in PP4 using progression, the item add function divides the qty_per_parent by 100. That is incorrect. it should not assume a kit to have a qty_per_par that is multiplied by 100. Macola writes the imordbld with a qty per equal to the qty. What this does when a 1 is wanted to be shipped sees the one and assues it should be .01 and responds with an error saying you are trying to ship too much. If it is serialized and the serial lot collection box pops up and a serial number is selected, it tries to fulfill .01 as a quantity. The bottom line is that Progression does not multiply the qty per by 100 on kit type items.
POP Reporting with MRP Demand turned on - Cost not correct
Symptoms: POP Production reporting - File > Optios >WMS > Mfg Picking Issue > MRP demand - if flag is set to "Ignore over issue" or "Allow over issue", when components are issues, the qty_per is reduced at the time of issue for a correct MRP calculation. But when production is reported, is uses the qty_per for the cost calculation and is then calculating the incorrect cost on components that have been issued.
Shipping issues no message on over under shipping.
Symptoms: To duplicate this issue set both over and under shipping to a hard stop. Also check the box that say all order lines must be on one shipment. Create an order with one item with a qty ordered of 10 Go into Pick Pack and ship and add five of them to a shipment. Then try to ship it. You will notice that clicking any shipping button produces no results(UPS LTL FedEx etc.) No message appears and no shipment formspop up. Go into setuo and remove the checkbox for all items to be on one shipment. go back to the order and try to ship it and notice that now the Hard stop message pops up.
Error received when trying to create PO with Landed Cost
Symptoms: Error received when trying to add a line item to a Printed PO with Landed Cost. Error message:PoOrdHdr:AddLineItem set OnOrder:Post :Conversion from string "" to type 'Integer' is not valid.Error point =20. This issue will also occur when printing a PO through Wisys that has Landed Costs.
PO Release class missing COM attributes
Symptoms: PO Release class missing COM attributes This simple VBA code shows the non exposure to method or object parameters for Wisys.PoTrx.v4.1.t32 Release Dim p_oRelease As New Wisys_PoTrx_v4_1.Release p_oRelease. <-------notice here that no method or object parameters are exposed for the release function this code assumes these references Wisys.Potrx.v4.1.T32 Wisys.AllSystem.v4.1.T32
AP Voucher Batch Balance incorrect when entering through Agility Explorer
Symptoms: The batch_bal when going through AE is 0 when you initially create the batch with the aptrxfil and aptrxdst entries. When you post, the transactions are processed but the batch is not removed because of the 0 balance. It remains in the table after the post and is updated with a negative balance.