Salesforce

"Destination Too General" Error in Mass Pick Operation from JDA GUI Dlx Client

« Go Back

Information

 
Title"Destination Too General" Error in Mass Pick Operation from JDA GUI Dlx Client
SummaryWhen picking loose picks (Each / case level UOM) or using Mass Pick Operations screen this error is shown up if policy ATTACHMENT-STRATEGY-FOR-AREAS is not configured for the destination Area
URL NameDestination-Too-General-Error-in-Mass-Pick-Operation-from-JDA-GUI-Dlx-Client
Resolution
For 2014 and below:-
Follow the below steps to resolve the issue:
  1. Login to JDA Warehouse Management
  2. Open policy maintenance or policy maintenance override screen
  3. Find MOVE-INVENTORY -> ATTACHMENT-STRATEGY-FOR-AREAS
  4. Create policy value NEVER-ATTACH (Confirm with your business on what policy value suits your site)
  5. Fill desired destination area in string one filed
  6. Click Save
  7. Restart WMS to activate the policy change

  For 9.1 and above:-
  Follow the below steps to resolve the issue:

      1.Login to the WEBUI
      2.Configuration->Outbound->Movement->Movement Zone
      3.Select the Movement Zone 
      4.Attachment Strategy and select value NEVER-ATTACH (Confirm with your business on what policy value suits your site)
User-added image
        5.Click Next and Finish
NOTE: Restart WMS to activate the policy change
 
ProductsWarehouse Management
ModulePicking
VersionALL
Error Message Code
"Destination Too General"
Cause
Additional Information
Destination Too General is shown up when we try to deposit Each / Case level inventory in an area which has the attachment strategy policy to attach to existing LPNs in the location and location has more than one load.

Based on customer business an attachment policy value can be varied, so please refer ATTACHMENT-STRATEGY-FOR-AREAS before defining actual attachment policy value.
Application’s help text will give more information on ATTACHMENT-STRATEGY-FOR-AREAS

The attachment strategy only applies to the deposit of sub-LPNs and detail LPNs; full LPNs are not attached to other LPNs based on the attachment strategy.
Publication StatusPublished

Powered by