Receiving a pallet with mixed items based on a packing structure using License plate receiving mobile device menu item


Initial description

The license plate receiving method on a mobile device lets you expedite the receiving process. If you receive advanced shipping notices (ASNs) from a vendor, and you trust the accuracy of the document, you can use the packing structure information in the ASN to automatically create put away work. The work is created when you scan the license plate on the pallet that you are receiving.

This is a significant advantage over other mobile device receiving methods, where you would need to scan in all of the shipment contents order by order, or item by item.

The packing structure is created in the following ways:

  • Manually created. This can be done from a selected inbound load based on one or more purchase orders. Typically, this process is used when an EDI is not set up with a vendor, but ASNs are received for incoming shipments anyway.
  • Automatically created when an ASN is imported import for purchase orders. See my previous post about importing an ASN.
  • Automatically created for transfer orders that were shipped by using the waves functionality. Note that if legacy WMS processes were used to ship a transfer order, you cannot use the license plate receiving method to receive it.

Today, the license plate receiving method is the only receiving method that allows you to receive one pallet that contains multiple purchase order lines for same or different items.

 

Setting up the mobile device menu item

To receive orders, you will need to create a mobile device menu item where Mode is set to Work, and Work creation process is set to License plate receiving, as shown in the below screenshot.

Note

There is confusion in the community about this menu item because, unlike other receiving methods, it does not have an “and put away” counterpart. This is because license plate receiving always executes the put away work to move the goods from the inbound area. In fact, it could be renamed to “License plate receiving and put away.”

Mobile device menu items

Settings on the menu item

If Display disposition code is selected on the menu item, the worker will have to select a disposition code after entering the license plate ID. Disposition codes help workers to ensure that a procedure is in place for receiving items that are damaged or unusable, without knowing all the details about the process. Applicable only for purchase orders, disposition codes help ensure that the correct location directives for put away are used. Disposition codes also set the inventory status of the received items.

Example

You want to clean all items that are dirty when they arrive, and you don’t want the items to be available to other processes during cleaning. You can create a disposition named “Dirty” that puts the items is an unavailable, or blocked, status. You can also set up a location directive to move the items to a dedicated area. Workers select the disposition code “Dirty” and instructions for handling the items are displayed.

Audit template ID enables various customizable actions when performing work. Audit templates are triggered when the value in a selected field is changed. The following are some examples of actions:

  • Printing a certain report when a work order is completed.
  • Capture temperature data during the receiving process.

This field is available for the most mobile device menu items. I will not describe it in this blog post.

Display inventory status is also available for most mobile device menu items for pick and put work. If selected, the inventory status of the work line that is being processed is displayed.

Cumulative Update 8

In cumulative update 8 for Microsoft Dynamics AX 2012 R3, a check box named Print label has been added to the mobile device menu item for license plate receiving. If it is selected, and printing is configured in the Document routing form, the parent license plate ID for a pallet and all of the nested license plate IDs for cases are printed when goods are received. This happens before creating the put away work so the user can attach the labels to the cases. This is especially useful in a cross-docking scenario, where received cases are dispatched right away.

If you don’t select this check box, you can still print the parent license plate by adding a “Print” step to the work template.

 

After you create the menu item, you then need to add it to a mobile device menu so that workers can access it on mobile devices. After that, the worker needs only to provide the ID of the license plate for the received pallet. Instructions for what to do next are displayed on the mobile device.

I have added a menu item to the Inbound mobile device menu, as shown in the following illustration.

Mobile device menus

 

Walkthrough: Receive a shipment that contains multiple purchase orders

To get started, we need two purchase orders. Each purchase order will contain a line for two different WHS-enabled items. The following illustrations show the purchase orders that I have created.

Purchase order 000412

Purchase order 000413

Note

The purchase orders are for the same vendor, and the lines are coming to warehouse 42. The orders can be shipped as a consolidated shipment, and the items can be placed onto the same license plate.

Now that we have the purchase orders, we need to create a load, shipment, and packing structure. To simulate the receipt of an ASN from a vendor, I will import an ASN document with the XML shown below. The XML file for the ASN is also available in my OneDrive.

 1: <?xml version="1.0" encoding="utf-8"?>
 2: <Envelope xmlns="http://schemas.microsoft.com/dynamics/2011/01/documents/Message">
 3:     <Header>
 4:         <MessageId>{5603D03A-4473-404D-9F27-738BE0FEA99E}</MessageId>
 5:         <Action>http://tempuri.org/WHSShipmentASNService/create</Action>
 6:     </Header>
 7:     <Body>
 8:         <MessageParts>
 9:             <WHSShipmentASN xmlns="http://schemas.microsoft.com/dynamics/2008/01/documents/WHSShipmentASN">
 10:                  <WHSShipmentTable class="entity">
 11:                      <ShipmentId>CUSTREF-004</ShipmentId>
 12:                      <WHSUOMStructure class="entity">
 13:                          <LicensePlateId>LP2POs001</LicensePlateId>
 14:                          <WHSASNItem class="entity">
 15:                              <ItemId>000148_202</ItemId>
 16:                              <PurchId>000412</PurchId>
 17:                              <Qty>15</Qty>
 18:                              <UOM>ea</UOM>
 19:                              <InventDim class="entity">
 20:                              </InventDim>
 21:                          </WHSASNItem>
 22:                          <WHSASNItem class="entity">
 23:                              <ItemId>000147_202</ItemId>
 24:                              <PurchId>000413</PurchId>
 25:                              <Qty>10</Qty>
 26:                              <UOM>ea</UOM>
 27:                              <InventDim class="entity">
 28:                              </InventDim>
 29:                          </WHSASNItem>                         
 30:                      </WHSUOMStructure>
 31:                      <DirPartyPostalAddressView class="entity">
 32:                          <City>Redmond</City>
 33:                          <CountryRegionId>USA</CountryRegionId>
 34:                          <State>WA</State>
 35:                          <Street>123 Coffee Street</Street>
 36:                          <ZipCode>98052</ZipCode>
 37:                      </DirPartyPostalAddressView>
 38:                  </WHSShipmentTable>
 39:              </WHSShipmentASN>
 40:          </MessageParts>
 41:      </Body>
 42:  </Envelope>

As you can see from the file, both purchase orders are part of a shipment with the reference number CUSTREF-004, and both items are placed on the same pallet with license plate ID LP2POs001.

After importing the ASN, a load with the following packing structure will be created.

Packing structure

We are now ready to use the License plate receiving menu item that we created earlier. But before we do, I want to show some additional setups. These setups will ensure that items are put on the same pallet and in the same location when they are received:

  • Location directives
  • Location profiles for the locations
  • Stocking limits for the locations

We need to ensure that the locations are allowed to have multiple different items (as shown in the example above), and that the quantity can fit in the location. We’ll have a problem if the entire quantity won’t fit, because our location directive doesn’t allow us to split quantities across locations.

Here’s how I have set up my location directives and the location profile.

Location directives

Location profiles

I have assigned the location profile to location LP-002, which has enough room to store the 25 pieces I am about to receive (it is currently empty) and the stocking limit allows up to 5 PL.

On hand by location

We can now receive the shipment, so let’s open the Warehouse Mobile Device Portal (WMDP) and go to the menu item we created for License Plate receiving.

Step 1

As described above, the mobile device user only needs to scan the license plate on the received pallet.

License plate receiving, step 1

Note

You cannot partially receive a pallet by scanning one of the nested license plates for cases. You must always scan in the parent license plate ID.

Step 2

After confirming the license plate, a confirmation screen displays a list of the contents of the pallet. This includes the order information and the item quantities on the pallet. Quantities are shown as totals for each item, even though the item is on more than one order line.

License plate receiving, step 2

Note

The Exception button lets you indicate that the receipt did not go as planned. You can select a work exception of the type Receiving to add an entry to the work exceptions log.

Step 3

When you confirm the receipt, work is created to put away the goods and the Pick screen is displayed. We are picking up the pallet with the license plate ID at the inbound dock location shown below. The pallet contains multiple items with a total quantity of 25 eaches.

The corresponding work line #1 changes status to In process.

License plate receiving, step 3

Step 4

Confirming the pick closes the pick work line and starts the put work line. We are putting multiple items on the same pallet that they were received on at location LP-002.

License plate receiving, step 4

Note

You can click Override to change the put location for the items. This button is available because the Allow put location override is selected on the work user setup for Worker 42.

Step 5

When we confirm that the put work is completed, we’re finished receiving the license plate and can move on to receive the next pallet.

License plate receiving, step 5

Result of license plate receiving

The following status changes happen as a result of license plate receiving:

  • The status of the work becomes Closed
  • The status of the load becomes In process
  • The status of the purchase orders remains Open.

The following illustration shows the work that was performed.

Work

Note

If you look closely at the work lines you will notice that we actually had two separate put lines, one for each of the items, but we only saw one step on the mobile device. This is how WMDP optimizes the process when items are going to the same location, which in our case they were.

What next?

You should then follow the process your company uses for completing procurement, for example, by posting the product receipt document to update the status of the purchase orders on the load to Received.

 

Walkthrough: Receiving a transfer order shipped using Warehouse management features

A walkthrough is already provided in the Warehouse management system implementation guide, so I’ll just link to it here instead of duplicating it.

You will note that, from a receiving standpoint, the process is the same for purchase orders. All you have to do is scan the license plate and perform the put away work.

 

How license plate receiving actually works

The following list summarizes what the system does if you use license plate receiving on a mobile device to process a receipt.

 

  • Examine the packing structure for the specified license plate, taking the pallets first and then cases for that pallet.
    • Create the license plate specified on the packing structure (pallet or case) in AX.
    • Register the items on the parent license plate by looping through all the ASN items with the specified license plate. Even if cases are used, the items are still registered on the parent license plate.
      • For purchases, register items at the default receiving location for the warehouse that the worker is in. If a worker selects a disposition code, the inventory status for the code is used. Otherwise, the inventory status for the purchase order line is used.
      • For transfers, register items at the default receiving location of the “To warehouse” from the transfer order. When the line is registered in inventory, also receive the corresponding transfer order line.  You can later view the history of the transfer order history to see that each line was received separately.
    • Revisit the ASN items for the specified license plate, and create put work for each item.
      • If multiple lines are linked to the same load line, and they have the same inventory dimensions, group them by consolidating the quantity to put away on the work lines that are already created.
      • Update each processed ASN item line by increasing the value in the WorkCreatedQty field (Quantity for which work has already been created). Also update the corresponding field on the related load line.
      • Use location directives for purchase orders and transfer orders to determine the put away location, and break work into multiple pieces where necessary. This process is not specific to license plate receiving. It is the same for all processes that create put work in the Warehouse management module.
      • Create the work header, set the appropriate warehouse and target license plate on the license plate from the packing structure.
      • Create the pick line. There will only be one pick line for the aggregated quantity to put away. Use the location that is specified as the default receipt location for the warehouse.
      • Create work inventory transactions for all the work lines.
    • If labor standards are enabled for the warehouse, calculate the estimated execution time for each work line.
    • (CU8) If the mobile device menu item is set up to print labels, print the labels for the parent and nested license plates (pallet and cases).
    • Proceed to actually performing the work.
      • The work execution is not specific to license plate receiving, so all of the mechanisms are identical to other Pick/Put operations.
Technical information

Most of the non-generic business logic of processing the receipt of a license plate is consolidated in the following classes:

Classes\WHSWorkExecuteDisplayLPReceiving

Classes\WHSWorkCreateLP

The code is similar to other classes for mobile device receiving and work creation, debugging should not be a problem.

 

All right, that’s it. If you have questions or comments, don’t be shy 🙂

 

P.S. Download this post as a Word document

Comments (56)

  1. Todd says:

    Excellent notes on LP receiving.  Do you know if there is similar functionality on the shipping side of the world?  i.e. can you scan and ship a single LP that contains multiple items/quantities?

  2. Hi Todd,

    There is nothing like the License plate receiving functionality in AX 2012 R3.

    There is something that I cannot yet talk about that might be available in CU8 for R3. So stay tuned, or join one of the TAP programs / Yammer group to get more insight into CU8 release plans and features.

  3. Dimitri Noyen says:

    Hi Vanya and others

    I did the exercise of this blogpost, which is very well explained btw, but I get an error, for which I can't find the solution. When I pick on the RF device the LP with 2 different product, he gives me:

    "License plate already exists in another location. Update has been canceled".

    Do you have any idea what the problem could be? Thanks!

    FYI: all my pick and put locations are set to "allow mixed items".

  4. Hi Dimitri,

    The error means that when trying to commit an inventory transaction with the dimensions having the license plate = X (I assume it is the one specified in the packing structure), it found that there is already on-hand or planned inbound work with the same license plate X for a different location.

    A license plate can only exist in 1 location at a time (as in, it's a physical tag on a pallet, for example, so it can't be 2 places at once).

    Try using a different license plate number when receiving (change the packing structure / ASN file)

  5. James says:

    Hi Ivan

    Any update on the new things in CU8 you mentioned to Todd?

    Thanks

  6. James says:

    Hi Ivan,

    Also any chance you might have an idea what to check/setup for this

    I have tried to setup a basic system (AX 2012 R3 CU7) but am getting the following error when I try a PO Receive (not yet got to doing advanced stuff like ASN and Packing structure 🙂 )

    "Movement not valid on user locations except by the system. Update has been cancelled. Assign dimensions to LP"

    Steps To Produce:

    3. Click Inbound>Purchase Receive.

    4. Enter "P-000002" to purchase order, press enter.

    5. Enter "item number" , "6582J" press enter.

    6. Enter "Qty" = 1

    7. Select UOM "Roll 1000.00 x 900.00"

    8. Press OK button.

    9. Enter LP number "123"

    10. Enter Batch number "123"

    11. Enter Expiry date "5/5/2015"

    12. You will get error message below

    Movement not valid on user locations except by the system. Update has been cancelled. Assign dimensions to LP

    Many thanks in advance for any assistance or hints you can provide

  7. Hi James,

    Thanks for the reminder, I've updated the post with the few changes related to CU8.

    The part I mentioned to Todd is used as part of the Cross-docking functionality, and it not part of this post. I assume there will be a separate post (or whitepaper) describing this functionality in the future.

  8. Hi James,

    As for your question about PO receive.

    It looks like based on your location directive setup, you are trying to put the goods away to the locations which are assigned to the work users (each work user has a corresponding location assigned to him, that has the same identifier as the ID of the user)

    That is not allowed.

  9. Magnus Rohlén says:

    Hi Ivan,

    I'm working in a project with the new WHS-module. We have vendors that delivers multiple batches for same item on same LP. We are not receiving an ASN from them which makes it complex to do the receiving og those Lp's.

    Do you have any of how to receive those LP's without doing any modifications? We will use the RF for all inventory transactions.

    Br,

    Magnus

  10. Hi Magnus,

    Well, as I mentioned in the post, the packing structure required for using "License plate receiving" does not necessarily need to be based on importing an ASN. You can also create it manually, if you know the details of what's on the LP being received.

    If that is not sufficient, you will most probably need a modification.

    Can you describe the specific flow? How exactly do you want to process the receipt of such shipments?

  11. Magnus Rohlén says:

    Hi again Ivan,

    thanks for your response!

    My client is in the food-industry and therefore have to keep track of all batches, both on finished goods and raw material. Quality control is performed on all batches on finshed- and rawmaterial. FEFO is used on all batch-handled goods.

    Scenario:

    – Purchase order is sent to vendor on 1200 kg of item A (raw material)

    – Truck arrives to warehouse, containing 2 LP's

    – Pallet 1 contains 600 kg of item A, splitted into 400 kg of batch 1 and 200 kg of batch 2

    – Pallet 2 contains of 600 kg of item A, splitted into 200 kg of batch 1 and 200 kg of batch 3 and 200 kg of batch 4

    On inbound the worker will use the rf to receive the pallets, via  menu item based on the work cretin process "Purcahse order Item Receiving and put away". We will generate our own LP and use the vendor batch and expire date. We will not split the LP per batch, so after receiving the pallets each pallet should have invent-onhand like it was received. I have read the code behind and can't find anyway to do this in standard…..

    BR,

    /Magnus

  12. Yep, so I wrote above, you can use the LP receiving to keep the pallets as is – but you'll need to find some sort of a process, where the pallet content information is entered into the system.

    Outside of the above method, there is no way to accomplish this in standard.

  13. Nico says:

    I'm a bit confused about LP validation that must exist only in 1 location. My question is, how the vendor knows that its LP will be unique in my system?

  14. Hi Nico,

    The Vendor does not know or care. But, if you use SSCC codes, they contains the company ID as part of it, so there is very low probability of duplicates.

    Generally speaking, you would need to ensure that they are unique. You could generate new IDs in case a duplicate was found (or always).

    It all depends on how your company operates

  15. Joost says:

    Hi,

    When I check the data policies for the document WHSShipmentASN, I see that some fields in path /WHSShipmentASN/WHSShipmentTable/WHSUOMStructure/WHSPackUOMStructure/.. are enabled and required, and cannot be disabled or made optional.

    However, I don't see these elements in your XML. When I generate a sample XML with VS, these elements are generated in my sample XML.

    What are these elements for and where do I use them for?

    P.s. I'm running on R3 CU8.

  16. The WHSPackUOMStructure is a data source that is "optional", so even though the fields on it are required, the schema should say that it is ok to contain 0 or more of this element.

    This is used if you have a nested packing structure (HasPacks = true)

    A Pallet that contains 1 or more cases, that contain 1 or more items

    The cases would be in this data source

    1. isha says:

      Hi Ivan – or anyone. I am trying to find a model XML file (example – not an XSD) in order to learn how to import an ASN with the following scenario.

      1 packing structure for 1 Purchase order. Purchase order has Multiple SKUs.
      I want 1 license plate to hold multiple sku’s.

      I have tried to manually build the XML file to test this scenario, before sending it out to development, but I cannot get this right. I could really use some assistance. I know this is an old topic, so I’m crossing my fingers.

      1. Isn’t that the example from this blog post (with the only difference being that in my sample file the 2 lines on the license plate belong to different purchase orders instead of the same PO)?
        If you are looking for something else, ping me on e-mail, and I’ll try to help

  17. Joost says:

    Hi,

    Thanks for the fast response.

    I've been trying to import the nested packing structure, but I think something goes wrong with the data.

    I have a XML file with two items, both on one purchase order and on one pallet. But each item is packed on a case on the pallet.

    – The AIF exception log does nog show any exception.

    – The load is created along with a packing structure

    – The shipment is created

    However, the packing structure is wrong:

    – Fasttab pallets:The pallet is created with the correct license plate, but incorrect quantity: 1

    – Fasttab cases: The cases are created with the correct license plates, but incorrect quantity: 0

    – Fasttab items: The items are not shown in the grid. However, the records are created in WHSASNItem with the correct load, shipment, quantities and the license plate id (the parent one).

    Do you recognize this situation?

  18. Joost says:

    In response to above post: in the WHSUOMStructure for the cases, the LoadId is missing.

  19. Hi Joost

    Can you share your XML file with me, I'll take a closer look. Just upload it to OneDrive or somewhere and send me a link. Thanks (Replace the company-specific info with demo data or whatever, if necessary)

  20. nikodg says:

    Hi Ivan, thanks for your response 🙂

  21. Joost says:

    Hi Ivan,

    Sorry for my late response… here are the files:

    onedrive.live.com/redir

  22. Hi Joost,

    So I looked at and tried to process the file you included above.

    The problem with it is that you have two extra sections in it describing the items.

    The Packing structure needs to either have all items in cases, or none. In your XML, you have both – some items on the parent pallet, and some in cases on this pallet.

    It is a bug that we do not fail on such a file, but as I mentioned in my other post about ASN, we are currently not very good at catching erroneous input in the ASN. You would however not be able to create such a packing structure manually, if you tried.

    Remove the below two sections, and your file will process successfully:

    <WHSASNItem class="entity">

    <ItemId>A0001</ItemId>

    <PurchId>000129</PurchId>

    <Qty>1</Qty>

    <UOM>Pcs</UOM>

    <InventDim class="entity">

    </InventDim>

    </WHSASNItem>

    <WHSASNItem class="entity">

    <ItemId>A0002</ItemId>

    <PurchId>000129</PurchId>

    <Qty>1</Qty>

    <UOM>Pcs</UOM>

    <InventDim class="entity">

    </InventDim>

    </WHSASNItem>

  23. Maurice says:

    Hi Ivan,

    Good info on pallet receiving. I have a question. We want to receive pallets with a disposition code of "Inspection". It does not block inventory it just prevents reservation on sales order. The question is how can we change the status back to available during the put away process. The disposition code is not available for put away. We tried to use the change status work type on the work template but it does not work or we could not figure out how it's supposed to work. We would like to avoid an additional step after it's already put away especially to location that are not LP tracked. We also looked at receiving and put away directly into QMS and then create a put way work from QMS but the movement work template does not support the consolidate strategy. Do you have any suggestions?

    Thanks

  24. Hi Maurice,

    Having disposition codes work with LP receiving is on our backlog long-term, but was postponed again just recently

    Change status work type might very well go away in future AX versions, so I would not use it.

    Movement by template will support the "Consolidate" strategy – that is on our backlog as well, and will hopefully converge into a hotfix in the near future.

    This is a scenario multiple people have asked us about, and sadly there is no good answer for you. So if you are OK with the last process, wait for the hotfix and then use that with consolidate at putaway

  25. Maurice says:

    Hi Ivan,

    Thanks for the response. Manually changing the status after the put away is an additional step that makes the process clunky in a high volume warehouse and most of our picking locations are not LP tracked so the user has to scan the location, item and manually enter the quantity. Is there a way to automate that step?

    We wouldn't mind doing the status change after the receipt and before the put away because at this point it is still LP tracked and we could capture when the QC team has given the ok but the system does not allow it because the put away work is reserving the quantities.

    Also would you consider using the custom work type to achieve the status change during put away. we started looking at it and successfully were able to change the status on the put away work lines but we still have to figure out how to sync InventTrans. Any help would be appreciated.  

  26. Maurice says:

    Ivan,

    I have a different question regarding LP receiving. Why is there no option to separate the receipt from the put away like other receipt types? It is nice to receive by LP but we may not want to start the put away until later and would also like to group the put away as in the regular PO put away. I tried to add another pick / put pair to the work template (direct put away to dock and then put away to stock). The system cannot resolve the location for the second put away.

  27. Hi Maurice,

    Yes, we've heard the feedback about LP receiving not having a corresponding separate menu item type that would not have Putaway as part of it. It's on the backlog, but no ETA

    As for the status change, as I said, it's the way it is for the moment, I am afraid. The only thing that you might want to investigate is the quality orders – you should be able to change the inventory status from there when completing the quality inspection – maybe that would work for your scenario.

    There is no way to automate steps on the mobile device right now.

    As for custom work type – that could of course be used to do whatever you need, that's why it's custom. Just make sure you test it properly.

  28. Steven Hermans says:

    Hi Vanya,

    Thank you for this interesting post. I have 2 questions related to this:

    * for a nested packing structure: how would the process continue in WMS to split the received top-level LP into the cases? Can this be done through the mobile device? I'm looking for some 'reverse containerization' function… Right now, I can receive the top level LP but then I'm stuck: split it up into the lower level cases/LP's.

    * once items are received in with a specific inventory status on a specific location: how does the process continue? What are the options to 'recondition' these items in AX?

    My customer receives pallets with mixed items and splits these pallets (composed of a lot of boxes) over different locations…

    Looking forward to your advice!

  29. Hi Steven,

    1. Well, there was this new feature developed in CU8 that transfers the inventory from the parent LP to the child LPs, basically breaking down the LP. It is a mobile device menu item function. That sounds like what you are looking for here.

    2. This is a very broad question, it really depends on the business. You could do a movement by template after this (see some of the QMS videos / scenarios uploaded for WHS). Or just use them up from that location. Or change the status through one of the possible ways (there a few). It really depends on what process you have.

    3. Note, that in the example above, I specifically set up the system so that it puts away the items onto the same license plate on the same location. That does not necessarily need to happen. Depending on your location directive and other setup, you would be asked to put the items away on separate license plates into different locations just as well.

  30. Sergio says:

    Hi Ivan,

    I have read some of your posts and i found them very useful.

    I would like to ask you a question related to "LP receiving" menu item. I was trying to receive a transfer order through the "Transfer order line receiving" menu item, however i'm receiving the following error in the mobile device:

    "Transfer order must be received using LP receiving"

    Is the "LP receiving" menu item the only way available to receive a transfer order? If previous question's answer is 'yes', which scenario the "Transfer order line/item receive" will apply to?

    Thank you very much for your time, look forward to hear from you soon!

  31. Hi Sergio,

    Transfer order line/item receiving should be used, when the transfer order was shipped using the legacy processes (without work).

    LP receiving is the only way to receive a transfer order that was shipped using WHS processes (as we know exactly what we shipped, and which LP corresponds to that, so can improve the speed of receiving by just scanning the LP)

  32. Sergio says:

    Ok, thank you very much for your help.

    One more question. I agree with you the receiving will be better while doing it through the "LP receiving" menu item, however, as soon as i have been using that menu item i couldn't see and option to receive a less quantity than it was sent (i.e if some units were damaged during the transfer), is that possible to do or do i need to receive the whole quantity and do an adjustment later?

    If it is possible to receive a less quantity, just tell me that i can and i will find out how to do it.

  33. Yes, I am afraid that is how it is. You'll need to receive everything and adjust the damaged items out as a second step.

  34. Sergio says:

    Thank you again!

    Your answers were very useful.

  35. Keith Woznica says:

    Ivan, Thanks for taking the time to write this blog and get back to folks like myself. I appreciate the fact that mixed items on a license plate is possible with ASN's and hope to use them one day.

    My company deals with over 10,000 suppliers and at the moment 99% of them don't use ASN's. We will receive parcels from carriers in the U.S. with multiple PO's to put away. It is common to have 10 or more items for a put away process on a pallet. How could we accommodate such a situation with mixed inbound inventory so that we have 1 license plate to initiate the putaway process?

    I do understand that License plates could be printed for every item and then I believe there is a feature for nesting the license plates to give a parent license plate. The problem is that as the volume of inbound inventory goes up the put away process becomes more complex and constantly printing labels for items to have license plates . If there was just one license plate for the worker performing the put away to scan and have the system direct the worker to locations that would be the most optimal situation.

    Any suggestions you have would be appreciated.  Please let me know what you think.

  36. Hi Keith

    The only way available now is to manually create a load and a packing structure describing the contents of the pallet.

    We do have the item of building up a mixed pallet during receiving on our backlog though, but with no ETA to give you at the moment.

  37. Maurice says:

    Hi Ivan,

    Any ETA on new functionality? We already had to customize the system several times to fix what I would consider basic requirements or just to match AX existing functionality.

  38. Keith Woznica says:

    Ivan,

    This is a great post and I really appreciate the detail you put into it. The majority of suppliers we work with do not provide ASN's and this is our challenge. We have over 10,000 suppliers in our vendor master data and over 50,000 active sku's we'll receive. Are you aware of whether or not the future road map will have the capability for receiving mixed inventory to a single LP# ?

  39. As I said, it is on our backlog, but there is no ETA, as the resources allocated to this are few. But improvements for this are on the plan

  40. Oleksandr says:

    Hi Vanya,

    Thanks a lot for making our lives with WMS easy 🙂

    Could you please clarify the following: does the current CU8 allow picking for production from LP with mixed items?

    For example, I have a storage Unit (one Licence plate) with 3 different products on it. All these items are the raw materials for production of a BOM. I wan't to consume the whole LP for that production.

    Is this scenario supported?

    In my case I was able to complete works without any issues, but my target LP was empty.

    Thanks!

  41. Well, it allows it, sure. You will just need to provide a license plate to put stuff on during picking, as you won't be able to pick up the pallet that is in the location, as it has other items on it.

    An unexpected coincidence is that it does not pick the entire quantity on the license plate in that case. I suggest you open a support request for this case, as I would expect it to work differently.

  42. Rob says:

    Hi Vanya, thanks for the blog. I have question on the sending side. So in our case we have multiple transfer orders. The requirement is to have just one license plate for these orders. I have tried to use License plate build but currently I can't make it work, when I scan the child LP, it says, it is invalid.

    Also there is a License plate build work type option on the work template, however it seems it can't be added to any work template type. Can you give an example how to build a parent license plate from multiple child license plates? Thanks

  43. License plate build can't be used for this case. And, in general, in the current solution you have no control over the packing structure of the outbound load. Many partners have integrated containerization flow with the packing structure, generating the ASN based on how the items were actually packed (including the multi-level container structure). That's the best I can give you, I am afraid.

  44. Hatice says:

    Hello İvan!!! Thanks for your wonderful posts!…. İ would like to know about the funcionality in CU8 for to break Lps  in the Lps receiving process in transfers orders. İs only  cross-droking  funcionality- İ want to receive the pack after open it and the childrens Lps. Thanks in advance.

  45. Hi Hatice, sorry, I must have missed your question before.

    The "Break LP" is used in conjunction with the xDock functionality we built in CU8. When LP receiving is used, the goods are placed on the parent license plate, if the packing structure has nested LPs on the pallet (cases, in AX terms). This will unpack the pallet, so the inventory on hand is placed on the child/case level instead of the parent level. These would then be shipped further to individual stores using transfer orders.

  46. Rob says:

    Hi again Ivan,

    When using LP receive, is there a way to have a user directed option so that use can scan which item to be received first? So scenario is the user want to receive 1 LP with several lines of item. Using the LP receive AX will assign them items one by one for put-away. User wants the ability to select which item to be put-away first (as the item first suggested by AX is probably on the bottom of stack of this pallet).

    Thanks

  47. Hi Rob,

    It's a good question. Currently there's no mechanism to control the order in which work lines are created. At the time of work execution, regardless of which method is used, it would go in the same order the work lines were created (driven by LineNum field). For LP receiving there's currently no particular sorting defined when work lines are created (apart from one on RecId of the packing structure, meaning lines will generically speaking be created in the same order as they are met in the ASN xml file)

    What if you had the option of Skipping over the puts, getting to the one you want to put away first? (Like we have for Picks on outbound) Would that be a feasible workaround? We have a DCR coming out soon that will add that and other capabilities.

    If we were to make this configurable, how and where would you envision this configuration?

    Thanks

  48. Rob says:

    Hi Ivan, thanks for your reply. Skipping option will help but probably not so much help if a license plate has hundreds of lines. The possible configuration probably will be similar to the directed by option for the work: system or user, but this one is for the item, so if it is system directed, it will be as per current behaviour, but if it is user directed, user can scan item to be put away (probably with no option to enter quantity to ensure what have been shipped are equal to what will be received). Thanks.

  49. Thanks for the feedback Rob

    We'll add it to our (rather large) backlog of ideas. If you were to create a Feature request (DCR) through the standard support channel, that would get more attention to this work item however.

  50. jochen says:

    Hi Ivan, thanks for your blog.

    I have a Problem with the "Pack to nested license plates" function after LP Receive. it does not seam to work if i have items with Serial numbers. the items withour Serial numbers work fine.

    am i overlooking something?

  51. Hi Jochen

    I believe we've tested Serial-tracked items as part of delivering the Cross-Docking feature (which Pack to nested license plates is part of).

    Can you please open a support case with your detailed repro steps, and we'll take a look?

    Thanks

  52. Valentinas says:

    Thank you for all the Blogs you write!

    I miss one important documentation.

    How to auto-nest LPs into Parent LP during Receiving?

    Nested LP would be a trackable Bottle, Parent LP – a Pallet.

    There is a "Nest…" step in Work Template, but it does not allow to select it. Work Template does not allow to add "Nest…" line, which intuitively, should do the job.

    Also, are nested Containers the same as nested LPs?

  53. Dave says:

    Hi Vanya, can nested license plates created and used for inventory movements. Our finished goods production jobs are small, but each one goes on an LP. We want to combine those LPs onto one pallet which is the parent LP. The pallet goes several movements before it reaches a destination in the warehouse where we would break the parent pallet and put away the individual child LPs. Is this possible?

    1. Not at the moment, no.
      We are adding the ability to consolidate LPs into 1, but not through nesting at this point.
      We still lack the ability to split an LP.

Skip to main content