Skip to main content
Solved

Preassign Configurable Subassembly Serial #, Parent Move with Backflushing

  • November 10, 2023
  • 9 replies
  • 169 views

Forum|alt.badge.img+1

We build-to-order a configurable subassembly (that is linked to its parent) that we would like to pre-assign a serial # to.  When the shop floor employee does the final Move on the configurable subassembly, they will assign a serial # (system should auto-populate the pre-assigned serial # if qty = 1, but that’s a different subject).

At this point, the system should know which serialized configurable subassembly goes with the parent production order (via the references tab of the production order), and I wish I could backflush the configurable subassembly into the parent production order (by the way, the reason I have to make the serial class issue method “User Enterable” is because one configurable subassembly in inventory might cost $1,000 more than another configurable subassembly with the same Inventory ID).  But when I attempt to backflush, it says I cannot because the issue method is “User Enterable”.

If I type in the serial # that was assigned for the Move (when completing the configurable subassembly production order) into Materials LINE DETAILS of the parent production order before trying to backflush the configurable subassembly, the Move on the parent is successful.

Does anyone know of a setup in the system that would work for what I’m trying to do?  Basically, I don’t want the shop employees to have to mess around with serial #s.  Really I want the production planner to preassign a serial # to the configurable subassembly production order, and I’m wondering if the system could handle all the Move/Material transactions (auto-populating the serial #) from there without serial # input from shop employees.

Best answer by angierowley75

The current link between Parent and Child Production Orders is reference only.

We do have a project in the hopper to improve the linking build out some automation - like what you suggested with defaulting the lot/serial of the subassembly when it is issued to the parent.

9 replies

angierowley75
Acumatica Moderator
Forum|alt.badge.img+3
  • Acumatica Moderator
  • Answer
  • November 10, 2023

The current link between Parent and Child Production Orders is reference only.

We do have a project in the hopper to improve the linking build out some automation - like what you suggested with defaulting the lot/serial of the subassembly when it is issued to the parent.


Forum|alt.badge.img+1
  • Author
  • Varsity I
  • January 12, 2024

@angierowley75, do you have any vibe on when this project in your hopper would be released?  I am considering having our VAR customize Acumatica to handle this automation, but if this automation is coming in the next release, we may wait for it.


angierowley75
Acumatica Moderator
Forum|alt.badge.img+3
  • Acumatica Moderator
  • January 12, 2024

It is not coming out with 24R1, there is a possibility it will be the following release - but might be best to move forward with your VAR so you get the specific functionality you need to improve efficiencies


Forum|alt.badge.img+1
  • Author
  • Varsity I
  • May 18, 2026

@angierowley75 we did take the step of working with our VAR to develop a customization that auto-allocates the child serial to the parent material, but it does not work due to (what I believe is) a bug.  Acumatica is not allowing allocation of a serial via LINE DETAILS when a child order is linked to the material line.

Was also curious from a system roadmap perspective… is anything implemented like what you suggested?  We’re on 25R2.

We do have a project in the hopper to improve the linking build out some automation - like what you suggested with defaulting the lot/serial of the subassembly when it is issued to the parent.

 


angierowley75
Acumatica Moderator
Forum|alt.badge.img+3
  • Acumatica Moderator
  • May 18, 2026

I don’t think we did anything with pre-assigned serials when we built out our Generate Subassembly functionality.

@PragatiMalviya64  can you confirm?


Forum|alt.badge.img+1
  • Author
  • Varsity I
  • May 18, 2026

@PragatiMalviya64 can you also answer whether any logic is in place for “defaulting the lot/serial of the subassembly when it is issued to the parent.”?  Thanks!


Forum|alt.badge.img+2

I don’t think we did anything with pre-assigned serials when we built out our Generate Subassembly functionality.

@PragatiMalviya64  can you confirm?

Yes, we didn't touch lot/serial logic while building Generate Subassembly 


Forum|alt.badge.img+2

@PragatiMalviya64 can you also answer whether any logic is in place for “defaulting the lot/serial of the subassembly when it is issued to the parent.”?  Thanks!

If a serialized subassembly production order is completed and the items are moved to inventory, and those same serial numbers are later allocated to a parent production order, the system should automatically determine and assign the correct serial numbers when issuing the subassembly to the parent production order.This functionality has been available in the system for a long time.
However, there are additional factors to consider even after allocation- for example, the possibility that the same serialized item could be issued to another production order, since the system does not enforce strict restrictions on issuing items on the available quantity. 


Forum|alt.badge.img+1
  • Author
  • Varsity I
  • May 19, 2026

 and those same serial numbers are later allocated to a parent production order, the system should automatically determine and assign the correct serial numbers when issuing the subassembly to the parent production order.

Thanks for clarifying the specs you were (and were not) targeting ​@PragatiMalviya64.  Acumatica has a bug where you cannot allocate a serial to its parent if it was created via a linked production order.  Working with support on this.

Is there a mature idea out there around auto populating linked serials when issuing to parents?  Or should I start a new one?  Since Angie indicated this was in the works, maybe it’s already on the roadmap...