Attribute set instance allocation

29 views
Skip to first unread message

Kanat Mergenbayev

unread,
Jul 8, 2025, 10:01:28 AMJul 8
to iDempiere

Hi community,

I have a warehouse with one default locator and several non-default locators. I also have a product that exists in multiple locators, all with the same attribute set instance (serial number).

When creating a sales order line, how can I ensure that a specific locator is used for the serial number? How is this reflected in the database?

I’d like to understand:

  • Where the locator is recorded (if at all) when choosing an attribute set instance during order entry.

  • How the system determines the locator during shipment.

  • How to control or influence the locator selection when the same serial number exists in multiple locations.

Thanks in advance for your help!

Carlos Antonio Ruiz Gomez

unread,
Jul 8, 2025, 10:33:32 AMJul 8
to idem...@googlegroups.com
Hi Kanat, you can try to force some locator over others using the "Relative Priority":

As the help of that field states:
* Relative Priority
* Where inventory should be picked from first
* The Relative Priority indicates the location to pick from first if an product is stored in more than one location. (100 = highest priority, 0 = lowest). For outgoing shipments, the location is picked with the highest priority where the entire quantity can be shipped from. If there is no location, the location with the highest priority is used.
* The Priority is ignored for products with Guarantee Date (always the oldest first) or if a specific instance is selected. Incoming receipts are stored at the location with the highest priority, if not explicitly selected.


I'm not sure that the Help is in sync with the code, because from what I see in current code the Priority is taken into account always over the Guarantee Date.

But anyways, this can give you a clue to test.

BTW, as it says, locator is not taken into account "if a specific instance is selected".  But that applies to unique instance (like serial number), but non-unique instances (like lots) can be spread in different locators, so in such case the Priority must be taken into account.


Regards,

Carlos Ruiz
Reply all
Reply to author
Forward
0 new messages