Material holders and locations

A Material holder represents a tray, trolley, rack or other container used for production output. A Location identifies where a holder is situated. A Holder group organizes holders for navigation and selection. Configure them in Operations Studio → Material holders / Locations before publishing Apps that place or release output.

These definitions support material handoff. Creating a holder does not produce a quantity, move inventory or confirm a production step.

Create the setup

1. Select the intended site and environment.
2. Create the required Location with a clear name and unique code.
3. Create a Holder group when several holders belong together.
4. Create the holder with its name/code and select Location and group where applicable.
5. Add named positions when the holder has distinct slots. Give scanable positions distinct codes.
6. Choose whether mixed contents are allowed.
7. Save and reopen the definition to check its stored values.

Choose codes that match the labels operators scan. A code conflict means an existing record already uses the proposed code in this context. Resolve it deliberately instead of creating two indistinguishable containers.

Connect the operational App

For a new React App, ask Konnie to build placement, holder selection, inspection and permitted release actions through the material-flow SDK. Configure allowed holders, quantity and verification requirements in the published App. Existing component-based Apps can retain Place Output and Holder Overview; both must use the intended holder selection and mixed-content policy. See Custom App operations.

Place Output uses the selected order's producing-operation context. Verify the operation and any selected split; a bound work center can resolve the operation automatically. Choose the producing step explicitly if the context is ambiguous. Holder Overview shows actual stored assignments; releasing contents is a separate action from editing the holder's master data.

Test one agreed fictional handoff: place output, inspect the holder/position from the receiving view, then perform the permitted release and read the result back. Changing a layout or creating a holder is not that test.

Change an occupied holder

Editing uses the current revision so one editor cannot silently overwrite another. A revision conflict requires reloading the saved definition and comparing your intended change. The editor retains a stable baseline while you work; a background refresh is not permission to overwrite newer content.

An occupied position cannot simply be removed. Empty/release its contents through the authorized operational workflow before changing the position definition. Turning off mixed contents can also conflict with existing assignments. Resolve the contents first rather than using schema changes to hide them.

If saving has an uncertain outcome, use the offered retry/reload to check the existing request. Avoid immediately creating another holder after a lost response.

Rename, copy or remove setup

Use an entry's Explorer menu to rename, duplicate or delete it. A copy gets its own code and contains the setup only; it does not copy material assignments. Deletion archives the definition and removes it from live selection while keeping its history. Deleting a group keeps its holders and clears their group assignment.

Release a holder's contents before deleting it. Before deleting a location, move its holders and stock and settle outstanding reservations or returns. These dependencies block removal so physical material and accounting remain visible. A revision conflict means the setup changed; reload it and review the change before retrying.

Troubleshoot

Problem	Check
Cannot create/edit	Selected site/environment and material-flow management permission.
Code already used	Holder, Location and position labels/codes in the intended scope.
Holder missing in App	Published component selection and the App's permitted scope.
Cannot remove position	Existing assignments at that position.
Mixed contents rejected	Holder policy, component policy and current contents.
Placement has no output context	Selected order, operation and permitted quantity.

See Building Apps and Warehouse for the operational surfaces.