Home » Categories » Solutions by Business Process » Stock Control and Batch Tracking

Assemblies - Always Build Selected Sub-Assemblies

Datafile Software

Assemblies - Always Build Selected Sub-Assemblies


Where a stock assembly contains a component which is an assembly in its own right – usually referred to as a sub-assembly – then system profile settings allow you to control how that sub-assembly is processed. Options allowed include the facility to manually/never explode the sub-assembly, to always explode the sub-assembly for building or to only explode the sub-assembly where there is insufficient stock of the component.

When a set of stock items are used in several assemblies it can be useful to define this item as an assembly so that only one stock line is recorded in several assembly definitions rather than repeating (potentially) hundreds of stock lines which all have to be maintained separately in each assembly where it is used.Previously this required the ‘assembled’ stock item to be a ‘non-stock’ item but this presumes that the assembled stock item is not sold in its own right.

New in Release 6.5 is the ability to mark a stock item as a ‘phantom’ assembly. This allows the system to be set to ‘explode’ sub-assemblies generally (either manually or based on insufficient stock levels) but for phantom assemblies to always explode the components.

 Note

 Unlike a standard sub-assembly the system will not write stock transactions reflecting its build and issue for a phantom assembly (as it is a ‘place holder’ for a group of other stock lines). If the assembly is selected for build in its own right a standard build transaction would be written and physical stock increased.

Stock System Profile parameters allow control of whether demand, sales and cost values or cost prices are updated for phantom codes when used as a sub-assembly.

Installation

Database Changes

A new data item is required on the Stock file to allow flagging of a stock item as phantom assembly.To add this new item select Installationfrom the main menu followed by Application Manager and then Restructure A Database. Select the Stock Control application. Elect to update the Live Files and then select the Stock File. The existing data items are then displayed on screen, scroll-down to the next available blank entries and create the following items: File, Item, Name, Type, Description

STA PHANTOM-ASS ? Flag to identify stock item as phantom assembly.When used as a component within an assembly build the system will always explode the sub-assembly for build.

To insert a new item press <Enter> against a blank entry, enter the title as required and press <Enter>, select the item type (using the drop-down list if required), and depending on item type select the size required.

Once the additional item has been recorded press the <ESC> key and select the UPDATEbutton to save the database changes.When prompted respond ‘Y’ to the prompts to ‘Extract Existing Data to New Database Structure’ and, if appropriate, ‘Copy Table Entries from Old Database to New Database. Final prompts ask to ‘Remove (.OLD) Database’ and to ‘Carry Out the Same Restructure on the BASE File as Well’ – respond as required.If you select to update the base file you need to manually insert the new items at the same data item positions as on the live file.

Set Database Profiles

The new data item needs to be referenced within the Database Profiles. To update these settings select Installation from the main menu followed by Application Manager and Set Database Profiles. Choose the Stock Control application before selecting the Component Items screen.


On the left of the screen is the prompt Phantom Assembly– against this item reference the data item number of the equivalent item created above, <F4-Select> is available if required.

Application User Facilities

To allow stock items to be flagged as a phantom assembly you need to update the stock maintenance screen(s) to include an input item for the phantom flag. To update the screen layout(s) users can sign on as the SYSTEM user-id (or if Premier any user with Installer rights) and right-click on the Stock Maintenance menu option and choose Configure Option before selecting the Add New Stock Screen. Alternatively users can select the Installation option from the main menu followed by Application Manager and then Application User Facilities. Select the Stock Control application before selecting Maintain Stock and then Add New Stock Screen.


To insert the flag item you’ll first need to add a text label of ‘Phantom Sub-Assembly’ (or similar), to do this use the mouse to position the cursor where required and then type the required text. To insert the data items position the cursor where required and press the <F4-Select> key and choose the new flag item. Once complete choose File and then Save & Exit.

System Profiles

A new option setting has been added to the Stock and Bill of Materials parameters for ‘Expand Sub Assembly Components During Assembly’. To update the profiles select Installation from the main menu and lock out the system before selecting the System Profiles option and, firstly, the Stock Control application.


Expand Sub-Assembly Components During Assembly – controls how components which are also assemblies in their own right are treated during an assembly build. Options available include:

0 Expand Manually

1 Auto-Expand When Insufficient Stock

2 Auto-Expand Always

3 Never Expand Unless Phantom Assembly (new)

Regardless of the setting selected a phantom assembly will always be expanded for the full requirement when used as a component – this parameter relates to the processing of standard sub-assembly. If set to ‘0’ then for standard assemblies the operator will be prompted if they wish to build the sub-assembly, if set to ‘1’ will build just the shortfall required and if set to ‘2’ will build the full requirement. If set to ‘3’ then system will only explode the phantom assemblies, standard assemblies must be built manually as a separate process.

Omit Cost/Demand Update on Phantom Sub-Assembly – when a sub-assembly is processed as part of the build the demand, cost and sales values are updated to reflect the issue along with standard components, in addition the cost price is updated to reflect the sub-assembly components. With phantom sub-assemblies acting as a ‘place-holder’ then it could be undesirable to update the demand (plus cost and sales values) as the stock isn’t being issued and nor is the assembly being built.Setting this option omits the update of these values when a phantom flagged item is processed as a sub-assembly.

As with Stock Control this option has also been added to the Bill of Materials system profiles and equivalent processing takes place with regards to standard assembly handling.


Select Method for Expanding Sub Assembly Components – controls how components which are also assemblies in their own right are treated during works order create. Options available include:

0 Never Expand

1 To Always Expand

2 To Only Expand When Insufficient Stock

3 To Never Expand Unless Phantom Assembly (new)

NB: In a slight difference with Stock the 0 response will omit the explosion of phantom sub-assemblies, if you do not wish to explode sub-assemblies except for phantom flagged items this prompt should be set as option ‘3’.

Custom Fields
  • Release ID: 6.5
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
Stock Valuation and Cost Prices
Viewed 8598 times since Mon, Jun 18, 2012
Stock Reports
Viewed 1351 times since Mon, Jun 18, 2012
Multi Location Stock - Stock Control
Viewed 1397 times since Mon, Jun 18, 2012
System Status - Batch Tracking
Viewed 1346 times since Tue, Jun 19, 2012
Document Design Manager - Parameters - Stock Control
Viewed 1441 times since Tue, Jun 19, 2012
Audit Pointers: Stock to Transactions & Audit Pointers: Assembly to Component - Stock Control
Viewed 1374 times since Tue, Jun 19, 2012
Stock Analysis Summary - Stock Control
Viewed 1371 times since Mon, Jun 18, 2012
Transferring from Existing Stock Control
Viewed 1390 times since Mon, Jun 18, 2012
Stock History Analysis
Viewed 1771 times since Fri, Jun 8, 2012
Set Application Code Formats - Stock Control
Viewed 1268 times since Mon, Jun 18, 2012