Sage ERP X3 Configurator STUDENT CURRICULUM SAGE UNIVERSITY
Certified Course Curriculum
Sage ERP X3 Configurator CERTIFIED STUDENT CURRICULUM SAGE UNIVERSITY
Curriculum Version 1.0
NOTICE This document and the Sage ERP X3 software may be used only in a ccordance with the accompanying Sage MAS ERP X3 End User License Agre ement. You You may not use, copy, modify, or transfer the Sage ERP X3 software or th is documentation except as expressly provided in the license agreement. Visit our website at www.SageU.com, or call 1-800-944-4299 to learn about t raining classes that a re added throughout the year. Information in this document is intended solely as general information with respect to common business issues and is not to be construed as professional advice. It is always best to consult a tax or accounting professional for all tax and account related qu estions. THE INFORMATION INFORMATION HEREIN IS PROVIDED “AS IS” AND ALL WARRANTIES ARE EXPRESSLY EXPRESSLY DISCLAIMED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY: WARRANTY: OF MERCHANTABILITY; MERCHANTABILITY; OF FITNESS FOR ANY PARTICULAR PARTICULAR PURPOSE; OF NON-INFRINGEMENT OF ANY PROPRIETARY PROPRIETARY RIGHT OF ANY THIRD PARTY IN ANY COUNTRY; COUNTRY; OTHERWISE ARISING O UT OF ANY PRODUCT, PROPOSAL, SPECIFICATION SPECIFICATION OR S AMPLE; AND ANY WARRANTY THAT THE DOCUMENT I S ERROR FREE. No license, express, implied, by estoppel or otherwise, to any intellectual property right is granted by this document. Sage Software may make changes to the information in this document at any time, without notice. Recipient is solely responsible for assessing the suitability of the information and assumes all risk of use. © 2011 Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the Sage product and service names mentioned herein are registered trademarks or trademarks of Sage Software, Inc., or its affiliated entities. All other trademarks are the property of their respective owners. 05/2011
Configurator Table of Contents 1
Principle ..................................................................................................................... 4
1.1
Types ....................................................................................................................................................... 4
1.2
Scenarios ................................................................................................................................................ 4
1.3
Applications ............................................................................................................................................ 4
1.3.1 Product Selection ........................................................................................................................... 4 1.3.2 Assembly with Features/Options .................................................................................................... 4 1.3.3 Jobbing/Estimating ......................................................................................................................... 4 1.4
Usage....................................................................................................................................................... 5
1.5
Methodology ........................................................................................................................................... 5
1.5.1 Training........................................................................................................................................... 5 1.5.2 Implementation ............................................................................................................................... 5
2
Product Lines ............................................................................................................ 6
3
Selections ................................................................................................................ 10
3.1
Example of Use ..................................................................................................................................... 10
3.2
The Definition ....................................................................................................................................... 12
3.2.1 Window ......................................................................................................................................... 13 3.2.2 Secondary filters ........................................................................................................................... 13
4
Options/Variants ..................................................................................................... 14
4.1
Example of Use ..................................................................................................................................... 14
4.2
The Definition ....................................................................................................................................... 16
5
Scenarios ................................................................................................................. 19
5.1
Use ......................................................................................................................................................... 19
5.2
Definition ............................................................................................................................................... 29
5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6
Parameter definition ..................................................................................................................... 29 Parameters/Initialization ............................................................................................................... 29 Kit Creation ................................................................................................................................... 30 Select Components ...................................................................................................................... 30 Create Components ..................................................................................................................... 30 Create Operations ........................................................................................................................ 30
5.2.7 Final controls ................................................................................................................................ 30 5.2.8 Buttons.......................................................................................................................................... 30 5.3
Master Scenario .................................................................................................................................... 30
6
Configurator Scenario Details ................................................................................ 31
6.1
Parameters ............................................................................................................................................ 31
6.2
Symbols................................................................................................................................................. 31
6.3
Calculation Tables ................................................................................................................................ 36
6.3.1 Simple........................................................................................................................................... 36 6.3.2 Double Entry Tables ..................................................................................................................... 37 6.4
Forms and Templates .......................................................................................................................... 38
6.5
Procedures............................................................................................................................................ 39
6.6
Configurator Scenario ......................................................................................................................... 39
6.6.1 6.6.2 6.6.3 6.6.4 6.6.5 6.6.6 6.6.7 6.6.8
Parameter definition ..................................................................................................................... 39 Parameter/Initialization ................................................................................................................. 40 Kit (or Product) Creation ............................................................................................................... 41 Select components ....................................................................................................................... 42 Create components ...................................................................................................................... 43 Multi-level Configurator ................................................................................................................. 44 Operations .................................................................................................................................... 45 Final controls ................................................................................................................................ 46
6.7
Validation .............................................................................................................................................. 47
7
Costing ..................................................................................................................... 48
7.1
No System Processes .......................................................................................................................... 48
7.2
Cost Calculation ................................................................................................................................... 48
7.2.1 Component costs .......................................................................................................................... 48 7.2.2 Other fields ................................................................................................................................... 49 7.3
Specific.................................................................................................................................................. 50
7.3.1 Base Price or Last Cost ................................................................................................................ 50 7.3.2 Evaluation of Formula ................................................................................................................... 50 7.3.3 Other fields ................................................................................................................................... 52
8
Running Scripts ...................................................................................................... 52
8.1
Default Values ....................................................................................................................................... 52
8.2
Restart ................................................................................................................................................... 52
8.3
Re-use Existing Configurations .......................................................................................................... 53
8.3.1 Search .......................................................................................................................................... 53 8.3.2 Re-use .......................................................................................................................................... 56 8.4
Equivalent ............................................................................................................................................. 58
8.5
Entry Mode ............................................................................................................................................ 58
8.6
Automatic Configurator ....................................................................................................................... 59
9
Other Features ......................................................................................................... 60
9.1
Configurator History ............................................................................................................................ 60
9.2
Where Used ........................................................................................................................................... 60
9.3
Configurator Utilities ............................................................................................................................ 61
9.4
Activity Codes ...................................................................................................................................... 61
9.4.1 Options Activity Code (Inventory section) .................................................................................... 61 9.4.2 Screen-sizing Activity codes (Inventory section) .......................................................................... 61 9.4.3 License ......................................................................................................................................... 61 9.5
Screen Personalization ........................................................................................................................ 62
9.5.1 Creation of a Specific screen:....................................................................................................... 62 9.6
Entry Points .......................................................................................................................................... 62
10
Appendix 1 Prerequisites ....................................................................................... 64
10.1 Data........................................................................................................................................................ 64 10.2 Processes.............................................................................................................................................. 64 10.3 Configurator Scenario ......................................................................................................................... 64 10.4 Typical Exceptions ............................................................................................................................... 65 11
Appendix 2 Sample Scenario ................................................................................. 66
11.1 Header ................................................................................................................................................... 66 11.2 Initialization........................................................................................................................................... 67 11.3 Kit Creation ........................................................................................................................................... 67 11.4 Select Components .............................................................................................................................. 68 11.5 Create Components ............................................................................................................................. 68 11.6 Component Fields ................................................................................................................................ 68 11.7 Create Operations ................................................................................................................................ 69 11.8 Operation Fields ................................................................................................................................... 69 11.9 Final Controls ....................................................................................................................................... 69
1
Principle
1.1
Types
There are three basic types of Configurator:
Product Selection – this is a method of filtering the Products, either with fixed filters, or depending on some questions asked. We may allow one or many of the filtered products to be selected. Options/Variants – this allows the selections of Products as options or variants which are linked by rules, so that selections within a group can be mandatory or not, …
Scenario (or Script). These can generate new Products, Bills, and Routes. A Scenario may use a Selection, or Option/Variant, as part of its logical construct.
1.2 Scenarios The principle is to select or create products according to a scripted set of questions, and logic or formulae based on the responses. The questions are usually orie nted towards the customer‟s perception of the product, rather than the internal engineering of the product. Creation of products can include creation of new components, as well as the generation of Bills, Routes and costs.
1.3
Applications
Configurator Scenario is commonly used in the following circumstances: 1.3.1
Product Selection
The user will enter product attributes requested by the customer, and the Configurator will identify the matching product. 1.3.2
Assembly with Features/Options
An assembly will have many alternate options for many features; e.g. a computer may have selections from 2 voltages, 3 processor speeds, 6 memory configurations, 5 hard drives, 1 or 2 CD or CDR drives, etc. Often, we will use “intelligent” part numbering to identify the end product. Not all possible options will be created before we open our Sales desk. A configuration may create a new product, or select an existing product. 1.3.3
Jobbing/Estimating
These scenarios will drive estimating functions for industries such as printing, sheet-metal work, some types of general engineering. They are the most difficult to construct. They will very often involve many calculations, and many questions to denote the attributes of the product. They will usually create unique products, even if there is some leve l of “intelligence” in the part number.
1.4
Usage
In Sales (Quotes or Orders), Configurator is invoked by R-c from a line (selected by single click, NOT opened with D-c), and the user then selects the Configurator to use:
1.5 Methodology 1.5.1
Training
Initial training will be based on examining the use and definitions of Configurator in a DEMO Folder. 1.5.2
Implementation
Implementation will initially be under the guidance of the Training Consultant. There will be a number of phases: Create a trial scenario for a sub-set of the product range, using only a few attributes, components and operations o This establishes the principles, opportunities and limitations Document the scope of attributes and questions required o This may identify the need to use Forms/Templates as a means of presenting groups of questions Build the Scenario step by step, with testing at every step.
2
Product Lines
Product lines are used in a number of selection processes. A Product Line defines up to six numeric and up to six alpha fields, which will contain identifying attributes of a Product within a Product Line. A Product line is defined in Common Data > Product Tables :
Field Titles are selected from a list defined in Local Menu 760. Responses may be controlled by a Table of Responses in Parameters > Configurator :
Equivalence of selections may be made based on the definitions:
When a Product Line is associated with a Product, the attributes are defined on a second screen (Right-click from Product Line field):
3 3.1
Selections E xample of Us e
DIRECTLY IN SALES:
After choosing a Product Selection from the Configurator R-c option, the Selection criteria are shown:
Based on these entries, the user is presented with a list of items matching the criteria, and makes their selections:
On OK, the selections are added to the Sales Order or Quote.
THE DEFINITION
This is made in Parameters > Configurator > Configurator Selections.
It can be used directly in Sales if ticked Stand-alone; otherwise only within a Scenario. The Sort criteria are selected from Item Master. The Selection code defines how many lines can be selected (No selection for display only) (only in Stand-Alone). Qty column – If no, the quantity will be 1 by default; otherwise entered by the user in Sales or Stock units.
If it is used in Sales, and you need questions to be answered by the user, you need an Initial Procedure which asks the questions Parameters > Configurator > Standard Processes .
3.1.1
Window
Controls the display of fields from Product, Site, Site Totals (ITMMVT), Product-Sales (ITMSALES). 3.1.2
Secondary filters
Up to 4 Secondary filters can be based on questions in the Procedure, or fixed values. Filter Title can be text, or S_XXX for name of variable XXX.
Example: [F:ITM]CFGFLDALP1=S_FAM
Here we have applied the Filter: The product's first CFG attribute must match the response to the Question FAM.
4 Options/Variants 4.1 E xample of Us e DIRECTLY IN S ALES: Selection criteria:
Here, we can only select one of each Option category:
On OK, the selections are added to the Sales Order or Quote. Conditions within the selection may give errors:
4.2 The Definition This is made in Parameters > Configurator > Options/Variants.
Define if it is Stand alone (i.e. in Sales) or called in Scenario in Select components When stand alone, it will add the selected items as lines in the Sales order.
Define an Initial procedure if we want to ask some questions. Define the fields we want to see in the selection screen. On the Products, define groups either by common numbers, or a line which has a Filter on ITMMASTER. If relation is Forbidden with another line, then it will display * in forbidden line.
Example: Line 30 has a Condition/Filter: ([F:ITM]CFGFLDALP1 = S_FAM | [F:ITM]CFGFLDALP1 = "U") & [F:ITM]CFGFLDALP3 = "ELE"
This allows any Product where first CFG attribute matches the response to the Question FAM, or is "U", and the third CFG attribute is "ELE". In Rules, a selection from the products matching Line 30 is Mandatory if AGE is "8+". Line 10 entries Here, we introduce each Product separately, because we want to Group them (Line 10, Line 15, etc.) and then introduce further rules of exclusivity: ([F:ITM]CFGFLDALP1 = S_FAM | [F:ITM]CFGFLDALP1 = "U") & [F:ITM]CFGFLDALP2 = S_AGE
Each product is selected if the first CFG attribute matches the response to the Question FAM, or is "U", and the second CFG attribute matches the response to the Question AGE. Note: also in Rules that any "10" product is not allowed with any "15" or "20" product.
5
Scenarios
Scenarios are used to select or create Products, Bills, Components and Routes. Scenarios can be used independently of Sales.
5.1
Us e
Can be called from a Sales Quote/Order, or from Common Data > Configurator > Configurator . From Sales (single click, then right click on line), we select the Configurator, then go straight to the screen where we answer the Configurator questions.
In direct use, we start with a screen asking for some additional information (not mandatory). Common data > Configurator > Configurator
After this, we proceed to answer questions, possibly assisted by r-c selections:
In some cases, this will open a further window:
If the responses we give are not within limits, we will get an error:
After completing the questions, we may be taken to further selection screens, in this case because we ticked Illumination:
Here, we select from an Options/Variants screen.
On completion, we can review or correct the responses, Search (see Section 8.3), 8.3), or proceed to Validation :
Now, we can review the Product and Bill, which will be created:
Note: the display of costs, and in this case, the Base Price (Sales).
View the Route:
Check the inventory:
And the Standard Cost:
If we select Generation , then we return to our Sales Order with the new (or selected) product.
5.2
Definition
Parameters > Configurator > Configurator scripts The definition consists of a Header, and 7 Tabs. 5.2.1
Parameter definition
On this screen, we define various overall options for the script. 5.2.2
Parameters/Initialization
On this screen, we can define any questions we wish to be asked, generate any programmatic links between variables, and if required, select a finished product. If Questions are not placed here, then they will be asked of the user at the point in the process where they are required (End product, Components, Route).
5.2.3
Kit Creation
On this screen, we define the new End Product we are creating. It is based on a Reference Product, from which all fields will be copied except those defined in the table below. In this table, we can define fields for: Product (End Product) Product Site Product Sales BOM Header Route Header Product Customer Product Cost Product Supplier
5.2.4
Select Components
This tab can be used to Select existing components to include in the Bill of Material. This may use Selections (Section 3) or Options/Variants (Section 4). 5.2.5
Create Components
This tab is used to define new components. We define the BOM Sequence, and a Reference Component. By R-c, other fields can be defined for: Product (Component) Product Site Product Sales BOM Detail Product Customer Product Cost Product Supplier
5.2.6
Create Operations
Operations are created; some fields are available directly in the table, others by R-c from the line. 5.2.7
Final controls
Generate messages to the user, run final calculations, etc. 5.2.8
Buttons
Window
Validation
allows you to see how the Questions are presented to the user. allows you to change the presentation of the questions in the Blocks of the screen.
Test Scenario
allows you to run the Scenario up to the point of Validation, but not Generation.
Under the Functions menu of the screen, you have access to the various components of the Configurator (Symbols, Tables, etc.)
5.3
Master S cenario
We can use a Master Scenario, which allows the user to answer some questions, before leading them to a detailed scenario. The Master Scenario is defined in a parameter STO/CFGINI.
6
Configurator Scenario Details
Various tools we use in the Scenario are managed in the menu Parameters > Configurator , or from buttons within the Scenario.
6.1 Parameters In the module STO: CFGADV CFGINI CFGPICFLD CFGSSC
6.2
Advanced function (Y/N). Allows management of Costs, and links to X3 tables Master scenario by site (see Section 5.3) ITMMASTER field containing the Image of item (Used on R-c from selections) Multi-level Configurator (Y/N)
Symbols
Parameters > Configurator > Configurator Symbols There are three types of Symbol: System Question Variable
System symbols are pre-defined. Questions are used where the user will be asked for a response. Variables are used where a value will be assigned within the logic of the scenario; we do not expect the user to provide this data. Value type may be Alpha, Numeric, Date or Boolean (Yes/No). For Alpha, we can choose Upper, Lower, or either case. Control may be None, List, Table, or Range. A List is controlled by a Response Table.
Example of a Question controlled by a list, with its Table of Responses:
When we wish to refer to the value of the symbol, S_MCOU is the single or short value; L_MCOU is the long value in the case where we have an Alphanumeric list with Code and Description.
In this case, for the first choice, S_MCOU = “DB”, L_MCOU = “Dark Blue”. If we wish to refer to the symbol title, T_MCOU = “Mirror Color”.
We can create a Variable to Filter the selection Table (see notes):
A Range can be specified within the question.
If referencing a Table, we can define the returned field, and a Filter. This is a Formula, and is used to constrain the selection from the Table.
Our symbol MFST will be an ITMREF value selected from the ITMMASTER table (Products), but only from those Products which are defined with SEAKEY (Search Key) = “DFR”.
A dynamic Filter can be applied (instead of a fixed Filter) by writing the expression for the system Variable FILTER before asking the Question which uses the X3 Table. After the Question, redefine Variable FILTER to “”. If the Formula includes “, place the expression inside “.
Example; if Question MFST did not include a Filter Formula:
Operation Variable Question Variable
Symbol FILTER MFST FILTER
Index
Condition
Expression „[F:ITM]SEAKEY= “DFR”‟ “”
Other notes:
We must tick Archive if we want these responses written to the History file, and Search Criterion if we are to use archive searching (See Section 6.6.3). Where we use a table of values, we can also use a variable xxxON, or xxxOFF, to limit the allowable values. (xxx is the Response Table name). The Variable must be defined using the same Response Table, and should be set to string of numbers, which are the allowed (prohibited) line numbers of the Table. See example in Section 6.6.2. Variable RCMPnnn is the reference component for the Line Sequence nnn in the Screen Create Components. (See Section 6.6.5). o NOTE: For Seq. 20, Variable is RCMP20. No leading zero. System Variable RPAR is the reference component for the Parent item. System Variable SCESEL is the Selected Scenario; use a Master scenario – Procedure - Ask questions, derive the scenario. System Variable DYNAMT will dynamically display a value in top right of the Questions screen. You can assign whatever value you wish to this variable.
6.3 C alculation Tables There are two main types of Calculation or Conversion tables: single axis, or double axis. 6.3.1
Simple
Parameters > Configurator > Simple calculation tables The Single tables can have the origin as a Range, or a single value, according to their type. Here is an example of Range:
If it is a conversion table, we simply enter the Starting range as the origin. Also note, the option to lock the Configurator if the origin entries are not found in the table.
6.3.2
Double Entry Tables
Parameters > Configurator > Double entry table Here is an example:
Again, we can define if each axis is a Range, or single value. We would call this table with an X and Y value, and get a single value result.
6.4 Forms and Templates Parameters > Configurator > Forms and Templates These can be a series of symbols associated with a particular shape. As an example, we have certain questions to ask about the Mirror, depending on whether it is Round, or Rectangular.
As they open their own window, you can use these to ask more than the standard limitation of 36 Questions (particularly if some questions are only relevant in some conditions). In this case, tick Questions window, and make the Group and Form the same. If a Form/Template style has a number of options (as in this case), then the Form/Template is in itself a Question (Mirror Shape), requiring a Response (REC or RON), before the relevant additional screen is opened.
6.5
Procedures
Parameters > Configurator > Standard Processes These can be a set of rules, which are common to a number of scenarios, so only maintained in one place. They can also be used in conjunction with Selections.
6.6 C onfig urator S cenario Parameters > Configurator > Configurator scripts 6.6.1
Parameter definition
Tick boxes to allow or not the creation of Product, Components and Route. Multi-site – if ticked, creates new product on all sites. Normally, only created for the site associated with the scenario. Otherwise you use Symbol FCYITFn (n = 1-9) to duplicate on up to 9 defined sites. History search – just to inform the user that the same responses have previously been given. o See table CFGHIS; depends on having History tick on each symbol. Display multi-level – will display multi-level BOM in results. Quick Validation – skips the detail results screens
Select the Origin Bill and Route alternative from which copy will be made; also the Bill and Route to be built. Entry mode – see Section 8.4 Costing mode – see Section 7.
6.6.2
Parameter/Initialization
In some cases, all the questions can be asked of the user while generating the Kit (end product), or its BOM components or Routing operations. However, it is usually more convenient to define the logic in the initialization tab, where more control exists over the sequence of the questions. In this screen, symbols will be defined or used according to the logic of the Configurator. Operations can be: Question, Variable, Selection, Options/Variants, Link Table, Procedure, Message, Forms/Template and Entry Point. Examples: 1
Simple Question
Operation Symbol Index Question MCOU This simply asks the question MCOU. 2
Condition
Expression
Calc Table
X value
Conditional Variable
Operation Symbol Index Condition Expression Calc Table X value Variable MFCON S_MI="RON" "1, 3, 5, 6, 7" This sets the Variable MFCON (Filter on Response Table MFC for Question MCOU) to the string, but only if the condition MI = “RON”. Note how the variables are referenced in formulae by S_… 3
Conditional question
Operation Symbol Index Condition Expression Calc Table X value Question MNAME S_MENGR This asks the Question MNAME, but only if the condition MENGR = True (MENGR is a Boolean Question). 4
Calculation Table
Operation Symbol Index Condition Expression Calc Table X value Variable MSCR MSCRAP MSURFAC This will set the Variable MSCR equal to the result of looking up MSURFAC in the Calculation Table MSCRAP. 5
Arithmetic calculation
Operation Symbol Index Condition Expression Variable MSURFAC S_MSURFAC * (1+(S_MSCR/100)) This increases the value of Variable MSURFAC by MSCR as a %.
6
Link Table
Operation Question Variable Link Table
Symbol MFST RCMP35 ITMCOST
Variable
FCST
Index
Condition !(S_MI="REC") !(S_MI="REC") !(S_MI="REC")
!(S_MI="REC")
Expression S_MFST [F:LNK]STOFCY=S_FCY&[F:LNK]ITM REF= S_MFST&[F:LNK]CSTTYP=1&[F:LNK ]YEA=year(date$)&[F:LNK]CSTSEQ= 0 [F:LNK]MATTOT
This sequence of four lines (subject to Mirror shape not equal REC): asks the question MFST (itself defined as a filtered look-up in ITMMASTER, so returning one Product) sets the default product for BOM. Seq. 35 to this value defines a Link to the ITMCOST record with the Primary Key:- Current site, selected Product, Cost Type 1, current year, Cost Seq. 0 sets Variable FCST to a value of MATTOT from ITMCOST.
The success of the Link may be tested with Variable S_LNKOK; True if the Link is found, False if failed. Each time we encounter a new condition, or set a variable, the user process stops with OK. So, if we have a number of lines with the same con ditions, keep them together; it reduces the “OK” requirement. 6.6.3
Kit (or Product) Creation
We select a Reference Item. This will be used to fill any unspecified fields of the new product. It is mandatory, but is redundant if the System Variable RPAR is defined by the logic. See also section 8.1. Note: the right-click option here to Copy BOM (to the Create Component tab) Equivalence Search
This can only work if the reference product has a Product Line (in which fields to test for equivalence are listed). o No search – always generate Parent ITMREF – if exist, no action, otherwise create o Search – tests on nominated list of fields o Create always Parent ITMREF must be new
Operations
As well as the normal operations, we can write data to fields of: o Item Master o Product-site o Sold Product (Sales tab - ITMSALES) o BOM Header o Route Header o Product-Sales (Customer tab – ITMBPC) o Product Cost
Other columns on the screen: o Index is for dimensioned fields (e.g. TSICOD) o Parameter For fields - Re-work = recompute at end of scenario (e.g., costs) For selection = type of selection For Message Information or Locking
Item Numbering
If the Formula for the Master Product ITMREF contains # characters, these will be used as a sequential counter: "MIR-"+S_MI+"-"+"####"
6.6.4
Select components
Uses the options of Question, Variable, Selection, Options/Variants, Link Table, Procedure, Message, Forms/Template and Entry Point. Here we can see an example of selecting the Lighting Options when Illumination is ticked:
6.6.5
Create components
A reference component (Could be irrelevant if over-ridden by variable RCMPnnn) . Link qty could be on screen if a fixed value, otherwise with other fields, managed off R-c. If 0, no BOM link, just component creation. Equivalence search – as above
Lines may be Conditional, or not.
Other fields of the Product, BOM Detail, or Product Cost may be managed in the screen accessed by Right click Component fields.
6.6.6
Multi-level Configurator
It is possible for the Component to be itself the subject of another Scenario. For these definitions, parameter STO/CFGSSC must be set to “Yes”. This enables the field “Sub-procedure” in the Create Components tab. Any questions asked in the Sub-scenario will be included in the main scenario screens – you
will be advised to re-validate the main scenario after adding questions in the sub-scenario. o The main scenario will be de-activated As far as possible, the questions should be asked in the main script, otherwise they will only be asked after clicking on Validation . The Sub-scenario will only be used if the Component is new. All the attributes of the component should normally be defined in the component section of the top level scenario; only the BOM and Routing of the component will normally be managed in the sub-scenario. o It is possible to manage Product fields in the Sub-scenario in Rework mode. The sub-scenarios depend on the principal scenario and must use the following: o the same route alternative o the same BOM alternative o the same cost calculation method
This information is forced by the Configurator at execution; it is therefore advisable to ensure the consistency of the parameterisation.
6.6.7
The following actions can not be used in a Sub-scenario: o Messages o Selections o Options/Variants Operations
Basic information on main screen:
Note right click option from Reference Routing to Copy Routing. Additional operations (not copied from Reference) must be based on a Standard Operation o Manufacturing > Technical data > Routings > Standard Operations
R-c for more detail, including Lab W/c and Scheduling.
6.6.8
Final controls
e.g., Message Blocking, for example: Operation Message
Parameter Locking
Condition
Expression
S_MI ="RON" & S_MDIA <35 & S_METCH & S_MIMAGE ="M"
" Mickey Image will not fit Round mirror < 35cm"
This section can also be used for some costing functions (see section 7.3)
6.7 Validation On Validating a Scenario (or when Saving after significant changes), you have the opportunity to modify the layout of the Questions screen.
You can modify the presentation of the blocks, and the sequence of the Questions within the blocks.
7
Costing
Costing method is defined in Parameter Definitions None The new Product Cost will be a copy of the Reference Product Cost Cost calculation -- Cost Roll-up will be carried out. Source cost can be chosen from: o Standard Cost o Revised Std Cost o Budget Cost Specific -- Internal variables CST are managed. These can be evaluated from: o Base price o Last cost o Evaluation of formula
By default, the reference product costs will be copied to the new product. The same will apply to any newly created components; they will have their reference component costs copied.
7.1 No S ys tem Pr oces s es If required, you can create Variables, accumulate costs be reference in these variables, and, on the Kit Creation tab, perform a Rework update of the values in Product cost (ITMCOST).
7.2 C os t Calculation The system carries out a Cost Roll up during the Validation phase, based on the selected source costs: o Standard Cost o Revised Std Cost o Budget Cost The results are written to the Product Cost table (ITMCOST) on Generation. 7.2.1
Component costs
If required, a Component Cost can be computed and updated; this must be done by formulae. Note that the detail costs of the reference component will, by default, be copied. There are, for example, 6 elements of material cost. Therefore, it is necessary to update the correct element of cost, as well as the totals. In some cases, it may be necessary to set some unused elements to zero, where they would otherwise be copied from the reference component.
7.2.2
Other fields
Fields in other sections, such as Product-sales, can also be updated with cost values. The table ITMCOST is implied as the newly calculated costs of the generated product:
Note: the computed cost can be referenced in the ITMCOST table.
7.3 Specific This allows the computation of costs through internal variables, which can be used to update the Cost file of the new product. A number of “system” variables are managed for Costing.
These are: CSTLAB CSTMAC CSTMAT CSTOVE CSTSCO CSTTOT
Labor Cost Machine Cost Material Cost Overhead Cost Sub-Contract Cost Total Cost
The basis for these can be: o Base price o Last cost o Evaluation of formulae Whichever method is used, the cost is computed, and displayed in the Configurator results. The Cost file (ITMCOST) can be updated with these values in Kit Creation, using the Product Costs, in Rework mode. 7.3.1
Base Price or Last Cost
In the case of "Base price" and "Last cost", only CSTMAT and CSTTOT are managed. CSTMAT is the sum of values from the final components. According to the choice, the programme takes the Base Price (BASPRI field in the Product-Sales file) or the Last Receipt cost (LASRCPPRI field in the Product-Site totals file). CSTTOT is equal to CSTMAT. 7.3.2
Evaluation of Formula
The cost calculation is prompted by entries in the Final Controls. Here, a line is entered for each of the cost elements (Material, Machine, Labor, Sub-contract). The symbol in each case is CST. The formula will collect the costs from each line of the bill or route: Operation Material cost Machine cost
Symbol CST CST
Labor cost
CST
Sub-contract cost
CST
Index
Condition
Expression [F:ITC]CSTTOT [F:MWC]STDSETCST*[F:ROO]SETTIM+[F:MWC]STDOPECST* [F:ROO]OPETIM [F:MWC]STDSETCST*[F:ROO]SETTIM+[F:MWC]STDOPECST* [F:ROO]OPETIM [F:ROO]REFPRI
Five of the system variables are automatically calculated as a result of the above steps: CSTMAT CSTMAC CSTLAB CSTSCO CSTTOT
Material Cost Machine Cost Labor Cost Subcontracting Cost Total Cost
There are no processes to compute overheads. Similar rules apply to the Machine and Labor cost elements as were described for the Material elements in 7.2.1. (Note how MATCST(1) has to be set to 0).
Note that the detail costs of the reference product will, by default, be copied. There are, for example, 6 elements of material cost. There is only one value of CSTMAT, so only one element of the Material Cost (MATCST) can be updated with S_CSTMAT; the remaining elements must be set to 0 if there are values in the reference product cost. Also, the Total material (MATTOT) must be updated with S_CSTMAT. Similar rules apply to the Machine and Labor cost elements. The fields CSTTOT and VLTTOT of the cost record should also be managed (set equal to S_CSTTOT).
7.3.3
Other fields
Fields in other sections, such as Product-sales, can also be updated with cost values:
Note that the computed cost can be referenced by the CSTxxx variables.
8
Running Scripts
8.1 Default Values Parameters > Configurator > Default values In situations where there may be no reference data, for the creation of a new record, it is possible to provide Defaults for fields of: BOM (Header and Detail) Product Customer Product Cost Product Supplier
These can be specified by Scenario, or generically.
8.2 Restart If you enter again the same BP and BP reference, the system will offer the option to use the same responses again. This applies even if the previous configuration was not generated.
8.3 R e-use E xis ting C onfig urations This uses variations on the Search principle, which is based on the Responses given to certain Questions, or values assigned to Variables. It depends on the symbol being ticked for Search Criterion (for which it must also be ticked for History). 8.3.1
Search
During entry of the responses, you have the option to Search. Click the Search button on the Scenario screen. In the Search screen, it will list the Questions and variables, which are flagged as Search Criteria, and will include any conditions according to any Responses you have entered. o You may modify these Search criteria. Click the Search button on the Search screen.
The system will show how many configurations are found, in the history file, which match the criteria specified.
By right click, you can examine the detail of each of these:
A selected line can then be used in one of two modes: This will start a new configuration, defaulting to the same responses as the Selection previous one. Modification This will default to the same responses, but will take modifications. The original Product, BOM and Route may be modified by changes to the responses. The Validation display may show a new Product (if counters are used in Product creation), but warns that this is a temporary reference for display only. A new Product will only be created if the responses directly affect the Product Reference.
In our example, the only response which affects the Product reference is the Mirror shape, so Modification would generate a new reference if we took a REC mirror, and created a RON mirror (or vice versa).
8.3.2
Re-use
On the Scenario Screen, the button Re-useaconfig is a short-cut to Modification. The selection screen does not display, or allow changes to, the Search criteria; it goes directly to a list of matching configurations from the history file.
Selection will start the modification process.
Search processes may be enhanced (depending on local requirements) by setting the system variables BPRNUM and BPRREF to be Search Criteria.
8.4 Equivalent By contrast to Searches (dependant on Symbol values), Equivalence is based on matching the attributes of the Generated Product, according to the Product Line. In the Product Line of the Reference Product, the Product line fields can be nominated as Equivalence Fields. If the Product generated by the Configurator matches any existing Products on these attributes, then these will be listed at the Validation stage, and can be selected:
8.5 E ntry Mode There are choices for Entry Mode: Standard
The user will see the generated screen for the Scenario, and can enter the values directly, or choose to open the Selection screens. Assisted
The selection screens are opened by default, and information is given about ranges of values allowed. This can be reset to Standard by clicking OK. Question by question
Forces entry of each question (in some cases, not forced if the entry conditions are the same as for the previous question).
8.6 A utomatic C onfig urator This allows you to run the Configurator for a range of responses to each of the questions, and generate the Products, Bills, Routes required. As an example, for the computers quoted above in Section 1.3.2, we might want to create all the st possible configurations for one voltage, 2 of the processors, all the hard drives, either option for 1 CD, etc. After selecting the Scenario, the second screen will be loaded with the questions for the scenario. You may enter by giving first value, number and increment; or by R-c and Selection Response to populate a number of Response fields. The Scenario will calculate the number of combinations to be generated. In Test mode, it will process the first combination, to test that all necessary responses and links are in place. OK, with Simulation ticked, will process all combinations without generation of master data. OK, without Simulation ticked, will process all combinations with generation of master data.
9
Other Features
9.1 C onfig urator His tory Common Data > Configurator > Shows the details of all configurations created:
Additional tabs show the Responses and other Variables. If you Delete, you also delete Item, Bill, Route, etc. These deletions are only allowed after the usual checks.
9.2 Where Us ed Parameters > Configurator This allows the display on screen of the Where-used of any type of Configurator symbol or element. (Select “Free” as the type for Calculation Tables).
9.3 C onfig urator Utilities Parameters > Configurator
Allows global validations of Configurations. o This may often be required after an upgrade to the Configurator functionality in a Patch. Possibility to perform Where-used for Symbols. Answers are written to a .tra file. Possibility to analyse the occurrences of a Product in various Tables.
9.4 A ctivity Codes A number of Activity Codes should be reviewed when working with Configurator. 9.4.1
Options Activity Code (Inventory section)
CFG
Configurator Controls functions and tables of Configurator, Options/Variants, Selections Note: this does not control the use of Product Lines in Products, although it does control the management of Response tables.
9.4.2
Screen-sizing Activity codes (Inventory section)
CFA CFC CFO CFP CFS
Calculation table lines (Simple and double entry tables) Number of Create Component lines Number of Create Operation lines Total Number of lines in scenario (for Internal screens) Number of lines in other Scenario definition tabs
9.4.3
License
A License is required for all Configurator functions other than Product Lines and Response Tables.
9.5 S creen Pers onalization It is possible to change the screens, which are auto-created for the entry of responses to a scenario. For every Scenario, a Window and an associated Screen are created:
9.5.1
In standard: o Window WUX + name of script o Screen WUX + name of script In specific you can create: o Window ZUX + name of script o Screen ZUX + name of script Specific screens are automatically detected when running a script Creation of a Specific screen:
In order to avoid errors you should create this screen by copying the generated standard screen. The header block fields can be suppressed, by making them individually 'invisible' or globally defining the block 'invisible'. The 'question' fields ('Q_' prefix) of the entry blocks must normally be set to Enter unless no answer is expected (entry in Forms/ templates). o If not Entered, these fields must not be deleted, but defined as 'invisible'. The standard evaluated titles of the questions ($) could be redefined as specific texts. The entered lengths could be modified but the data type must stay compatible with the data type of the standard screen. o The lengths of the alphanumeric fields are limited by the data type 'DES' which is 30 characters in standard. The Response Title fields ('Z_' prefix) could be deleted, or defined 'invisible', or placed in 'invisible' blocks (number 8 or 9).
Note: Attention should be given when validating or modifying a script, in case any changes to the
standard screens need also to be applied to the specific screens.
9.6 E ntry Points It is possible to make calls to Entry points throughout the Scenario. These could be elements of programming code which make calculations, read data from other tables, display information boxes, etc. The Entry point program should be associated with the standard program CFGLIBB.
The definition would take the form: Operation Entry point
Symbol GPOINT
Index
Condition
Expression “POINT_1”
The code in the Entry point programme (ZCFGPOINT) would take the form:$ACTION Case ACTION When "POINT_1" : Gosub POINT_1 When Default Endcase Return $POINT_1 ….
Return
Variable GBOITE is the Window name (e.g. WUXMIRR2) Variable GZONE is the last field entered (e.g. Q_MCOU) All the L_ variables are available for questions already responded to. All the S_ and T_ variables are available. [M:CFGF}SCENUM holds the Scenario name (E.g. MIRR2) [M:CSCE] has all the Q_xxxx fields for the Response values.
10 Appendix 1 Prerequisites 10.1 Data The following data should have been created (possibly manually for piloting, or by data import):
A typical configured product All the standard sub-assemblies, components, and materials A typical configured component (if appropriate) A routing for the typical configured product Business Partners (Customers, Suppliers) Costs Rules, and individual Product Costs –
10.2 Processes The following processes should have been performed and validated in a Pilot session: Sales Order Entry Work Order Creation (Back-to-Back, MRP By Order, etc.?) Component procurement o MRP, Re-order point o Purchasing, component manufacture Tracking o Purchase receipts o Work Order Materials, Resources, Produced Goods, Close+Cost o Sales Shipment and Invoice Financial entries o Invoice posting o Stock Movements o WIP movements
Within all these processes, consideration should be given to the management of: Prices Costs Stock features o Location o Lot, Sub-lot, Serial o QC status control o Expiration control
10.3 C onfig urator Scenario After the completion and validation of the data and processes mentioned above, it is sensible to commence the construction of the Configurator scenarios.
10.4 Typical E xceptions It is common to use phantom sub-assemblies to make groups of components, which are required in the end-product according to a set of conditions. The users may choose to start constructing the scenario, with the conditions for the inclusion of these phantoms, before they have completed the task of identifying the contents of the phantoms, and importing the components. In this case, it is normal to have a representative selection of components defined, for piloting and validating the processes.
Configurator
11 Appendix 2 Sample Scenario www.adonix.co.uk
11.1 Header Scenario
:
Access Code
:
MIRR
Mirror
Parameter Definitions
Active
:
Exclusive site
:
X
BOM
Item Creation
:
X
Reference
:
9 Configurator
Component Creation
:
X
Creation
:
1 Production
Routing Creation
:
X
Routing
Multisite Creation
:
X
Reference
:
9 Configurator
History Search
:
X
Creation
:
1 Production Evesham
Display Multi-level
:
X
Quick validati on
:
:
Cost Calculation
Valuation Costing Mode Standard cost
Entry Mode
:
Standard
Reference Item
:
MIR-R
Mirror - Reference
Product Line
:
MIRRO
Mirror
Equivalence Search
:
Search equivalence
Reference Routing
:
MIR-R
Sub-scenarios
:
Configurator
11.2 Initialization www.adonix.co.uk Action On
Symbol
Description
Parameter Condition
Forms/ templates Variable
MI
Mirror Shape
No action
MFCON
Filter on MFC
No action
Question
MCOU
Mirror Color
No action
Question
MFRW
Mirror Frame Width
No action
Question
MFST
Mirror Frame style
No action
!(S_MI="REC")
Variable
RCMP35
Reference component
No action
!(S_MI="REC")
S_MFST
Link Table
ITMCOST
Product - Costs
No action
!(S_MI="REC")
!(S_MI="REC")
[F:LNK]STOFCY=S _FCY&[F:LNK]ITMREF=S_ MFST&[F:LNK]CSTTYP=1&[F:LNK]YEA=year (date$)&[F:LNK]CSTSEQ=0 [F:LNK]MATTOT
Variable
FCST
Frame Cost
No action
Question
MLAMP
Mirror Light
No action
Variable
MSCR
Scrap Allowance
No action
Variable
MSURFAC
Mirror Surface Area
No action
Procedure
ETCH
Etched Image
No action
Question
MENGR
Mirror Engraving
No action
Question
MNAME
Mirror Engraved name
No action
S_MI="RON"
Expression
S_MI="REC"
MSCRAP S_MSURFAC * (1+(S_MSCR/100))
S_MENGR
Product
ITMREF
Product
No action
Product
ITMDES1
Description
No action
S_MI="REC"
"MIR-"+S_MI+"-"+" ####"
Product
ITMDES1
Description
No action
!(S_MI="REC")
Product
ITMDES2
Description 2
No action
Product
CFGFLDALP1
Color
No action
Product
CFGFLDALP2
Screen printing
No action
S_METCH
S_MIMAGE
Product
CFGFLDNUM1 Length
No action
S_MI="REC"
S_MLONG
Product
CFGFLDNUM2 Width
No action
S_MI="REC"
Product Sales
BASPRI
Re work
"Rect. Mir."+"-"+S_ MCOU+""+num$(S_MLONG)+" by "+num$(S_MWIDE) "Round Mir."+"-"+S_MCOU+""+num$(S_MDIA)+" dia." "For customer "+S_BPRNUM S_MCOU
S_MWIDE [F:ITC]VLTTOT*1. 5
Comment Select shape and enter sizes Limit colors for RON
"1, 3, 5, 6, 7"
11.3 K it Cr eation
Base Price
Calc. Table X
MSURFAC
Configurator
11.4 S elect Components www.adonix.co.uk
Acti
Action On
Symbol
Description
Parameter
Condition
Comment
Yes
Options/vari ants
LAMP
Mirror Lamps
Select 1 line
S_MLAMP
Select a lamp
11.5 C reate Components Sequ Component
Equivalence
ST
Link Quantity
Link Quantity
Condition
10
MGLASS-1 Mirror glass 1mm thick
No search
EA
1
Proportional
10
MGLASS-2 Mirror glass 2mm thick
No search
EA
1
Proportional
20
MBACK-2
No search
EA
1
Proportional
20
MBACK-4
Mirror back 4mm thick
No search
EA
1
Proportional
!(S_MSURFAC < 2500)
PUR
Purchased
30
MFRM-20
Mirror frame 20mm
No search
EA
1
Proportional
S_MI="REC"
PUR
Purchased
35
MFRMPL
Plain Frame - Round Mirror
No search
EA
1
Proportional
!(S_MI="REC")
PUR
Purchased
40
MTAB-1
Wooden tablet
No search
EA
1
Proportional
S_MENGR
PUR
Purchased
Mirror back 2mm thick
Cat
Description
S_MSURF AC < 2500
PUR
Purchased
!(S_MSURFAC < 2500)
PU R
Purchased
S_MSURFAC < 2500
PUR
Purchased
11.6 C omponent Fields Line Type
Sequence Act
Action On
Symbol
Ind Parameter
Create components
30
Yes Product
ITMREF
No action
Create components
30
Yes BOM detail
LIKQTY
No action
((S_MPERI/100) + (S_MFRW * 8 / 1000)) * 1.1
Create components
35
Yes Product
ITMREF
No action
S_MFST+"-"+num$(S_ MDIA)
Create components
35
Yes Product
ITMDES2
No action
num$(S_MDIA)+"cm Diameter""
Create components
35
Yes Product
SEAKEY
No action
""
Create components
35
Yes Product
ITMSTA
No action
1
Create components
35
Yes Product costs
STOFCY
No action
"EVE"
Create components
35
Yes Product costs
YEA
No action
year(date $)
Create components
35
Yes Product costs
MATCST
Create components
35
Yes Product costs
Create components
35
Create components
35
2
Condition
Expression "MFRM-"+num$(S_MFRW)
No action
S_FCST S_MSURFAC/1500
MATTOT
No action
S_FCST*S_MSURFAC/1500
Yes Product costs
CSTTOT
No action
S_FCST*S_MSURFAC/1500
Yes Product costs
VLTTOT
No action
S_FCST S_MSURFAC/1500
Configurator
11.7 C reate Operations www.adonix.co.uk Oper Standard Op Operation Description
Main Work Operation Centre Time
Management Unit
Setup Time
Run Time
10
Cut mirror glass to size
MCUT
Proportional
Time for 1
0.1
0.1
20
Cut back and frame
BFCUT
Proportional
Time for 1
0.2
30
Assemble
MASS
Proportional
Time for 1
Condition
0.3 0.2
40
100
Etching
ETCH
Proportional
Time for 1
0.15
0.1
50
110
Lamp attachment
LASS
Proportional
Time for 1
0.15
0.3
S_METCH S_MLAMP
60
120
Engraving
ENGR
Proportional
Time for 1
0.1
0.05
S_MENGR
11.8 Operation Fields Line Type
Sequence Act
Action On
Symbol
Ind Parameter
Create operations
20
Yes Route operation OPETIM
No action
Create operations
20
Yes Route operation ROODES
No action
Create operations
60
Yes Route operation ROODES
No action
Condition
Expression
S_MI="RON"
"Cut Back only"
0.3+(S_MI=REC")*0.2 "Engrave "+S_MNAME
11.9 F inal Controls Acti
Action On Description Parameter
Condition
Expression
Yes
Message
S_MI="RON" & S_MDIA <35 & S_METCH & S_IMAGE = "M"
" Mickey Image will not fit round mirror < 35cm"
Message
Locking
