Categories
BLOG

last auto pick

Blocked IP Address

Your IP address has been temporarily blocked due to a large number of HTTP requests. The most common causes of this issue are:

  • If you are using Maxthon or Brave as a browser, or have installed the Ghostery add-on, you should know that these programs send extra traffic to our servers for every page on the site that you browse. Using GameFAQs regularly with these browsers can cause temporary and even permanent IP blocks due to these additional requests.
  • Some unofficial phone apps appear to be using GameFAQs as a back-end, but they do not behave like a real web browser does. This triggers our anti-spambot measures, which are designed to stop automated systems from flooding the site with traffic. Continued use of these apps may cause your IP to be blocked indefinitely. There is no official GameFAQs app, and we do not support nor have any contact with the makers of these unofficial apps.
  • Using a script or add-on that scans GameFAQs for box and screen images (such as an emulator front-end), while overloading our search engine
  • Running a “scraper” or “downloader” program that either does not identify itself or uses fake headers to elude detection
  • Using a badly configured (or badly written) browser add-on for blocking content
  • Overusing our search engine with a very large number of searches in a very short amount of time

If you promise to stop (by clicking the Agree button below), we’ll unblock your connection for now, but we will immediately re-block it if we detect additional bad behavior.

If you do not understand what is causing this behavior, please contact us here.

Blocked IP Address on GameFAQs

WaDaCo – LOV auto pick function

I am setting up the “Report Picking Part” Data Collection Configuration. Every time that we report picking from the scan gun, we create a handling unit prior to that. The first step of the report picking process is to choose which Shipment Handling Unit ID you are attaching the parts in which you are picking.

Every time we do this process, we always choose the most recent Shipment Handling Unit ID that was created (that process never deviates). I am trying to have the system auto-pick the most recently created handling unit ID, but the auto pick function always chooses the first value in the LOV. The most recent handling unit ID created is always the last. Is there any way I can always make it choose the most recently created handling unit?

  • Like
  • Hello,

I am setting up the “Report Picking Part” Data Collection Configuration. Every time that we report picking from the scan gun, we create a handling unit prior to that. The first step of the report picking process is to choose which Shipment Handling Unit ID you are attaching the parts in which you are picking.

Every time we do this process, we always choose the most recent Shipment Handling Unit ID that was created (that process never deviates). I am trying to have the system auto-pick the most recently created handling unit ID, but the auto pick function always chooses the first value in the LOV. The most recent handling unit ID created is always the last. Is there any way I can always make it choose the most recently created handling unit?

2 replies

I guess you would need a small modification to the view that populates the LOV (to order it).

  • Like
  • I guess you would need a small modification to the view that populates the LOV (to order it).

Auto Pick LOV always fetch the first value in the select it creates, so yes you need to modify the LOV method (which is in Handling_Unit_API). It has a order by statement in the end that looks like this now:

stmt_ := stmt_ || ‘ ORDER BY Utility_SYS.String_To_Number(‘ || column_name_ || ‘), ‘ || column_name_ || ‘ ASC’;

If you want to reverse the sorting order, ASC needs to be changed to DESC.

But note that the same method is used by other processes also like Report Picking of Handling Units, Pack into Handling Unit on Shipment, Receive Shop Order and Receive Shop Order Handling Unit, so a change here will affect those processes also(even if you don’t use auto pick in those since it affects the whole sorting order for the LOV). If you don’t do additional coding to make sure it only happens for this process which is very possible to code (process id can be fetched from session id).

  • Like
  • Auto Pick LOV always fetch the first value in the select it creates, so yes you need to modify the LOV method (which is in Handling_Unit_API). It has a order by statement in the end that looks like this now:

stmt_ := stmt_ || ‘ ORDER BY Utility_SYS.String_To_Number(‘ || column_name_ || ‘), ‘ || column_name_ || ‘ ASC’;

If you want to reverse the sorting order, ASC needs to be changed to DESC.

But note that the same method is used by other processes also like Report Picking of Handling Units, Pack into Handling Unit on Shipment, Receive Shop Order and Receive Shop Order Handling Unit, so a change here will affect those processes also(even if you don’t use auto pick in those since it affects the whole sorting order for the LOV). If you don’t do additional coding to make sure it only happens for this process which is very possible to code (process id can be fetched from session id).

Hello,I am setting up the “Report Picking Part” Data Collection Configuration. Every time that we report picking from the scan gun, we create a handling… ]]>