Maintain System Configuration Parameters Session No: tisfc0000m000 Application: This session is used to define parameters which are basic to manufacturing. These parameters decide which key modules are to be implemented in manufacturing. Field Data: 1. MPS Implemented Indicates whether the module "Master Production Scheduling (MPS)" is implemented. Yes The module "Master Production Scheduling (MPS)" is implemented. No The module "Master Production Scheduling (MPS)" is not implemented. 2. PCF implemented Indicates whether the module "Product Configuration (PCF)" is implemented. 3. PCS Implemented Yes The module "Project Control (PCS)" is implemented. This affects the functioning of the other modules. No The module "Project Control (PCS)" is not implemented. This affects the functioning of the other modules. 4. ECOs Used Yes You can use change orders to record and apply engineering changes. No You cannot use change orders to record and apply engineering changes. 5. RPT Module Implemented The parameter that determines if the module "Repetitive Manufacturing (RPT)" is implemented. Yes The module "Repetitive Manufacturing (RPT)" is implemented. No The module "Repetitive Manufacturing (RPT)" is not implemented. Maintain BOM Parameters Session: tibom0100m000 Application: This session defines parameters relevant to Bill of Material Field Data: 1.BOM Unit of Measurement The unit in which the length and width are specified on production bills of materials. This unit is displayed after the fields "Length" and "Width" in various sessions of BAAN Manufacturing. The data to be entered must be defined in the session "Maintain Units (tcmcs0101m000)". 2. Description Description of Bill of Material. 3. Maintain BOM by Operation The value of this field determines how data is maintained in the session "Maintain Production BOMs (tibom1110m000)" and how the session "Enter Material Issue for Production Orders (ticst0101m000)" is used. If Yes, then while you enter data in the session "Maintain Production BOMs (tibom1110m000)", the system will ask you to type in the item code as well as the operation, allowing you to define a bill of material by operation. Consequently, the session "Enter Material Issue for Production Orders (ticst0101m000)" must be run by operation. In actual practice, you define a bill of material by operation for items with a longer lead time. Thus, you prevent components from being stocked too early, either in the warehouse or on the shop floor. If No, then while entering data in the session "Maintain Production BOMs (tibom1110m000)", you only type in the item code, after which you can define the components that make up the end item. Maintain CPR Parameters Session No: ticpr0100m000 Application: This session is used to define Cost Accounting Parameters. Field Data: 1. Standard Cost Price Calculation Code The module "Cost Accounting (CPR)" allows you to calculate cost prices. Each cost price calculation is saved under a cost price calculation code. This code can be used for calculating standard or simulated cost prices. This parameter indicates under which cost price calculation code the standard cost price is saved, which is important for, among other things: • Updating standard cost prices; • Calculating the estimated operation costs for budgets, projects, and production orders; • Calculating the estimated subcontracting costs for planned and unplanned subcontracting; • Determining actual operation rates for the actual costing of production orders; • Determining surcharges for the actual costing of production orders. 2. Description The description for the cost price calculation code. 3. Project Cost Revaluation The inventory of standard products issued for projects is revalued as long as the project is being executed, in order to achieve an up-to-date cost price in the module "Project Control (PCS)". This is essential because of the possible difference of time between posting to a project and the actual usage for the project. The following options are available: Yes. When the standard cost price is being updated for an item, the project costs are revalued. Revaluation of project costs only takes place if the project status is "Active" or "Finished". When project costs are revalued, the financial transactions are posted to the modules "Inventory Control (INV)" and "Project Control (PCS)". In that case, the reference to the order causing the inventory transaction is not removed. Financial transactions are posted as follows: Inventory Control (INV) The revaluation amount is saved with the transaction type "Revaluation" as defined via the parameter "Cost Price Component for Revaluation" in the session "Maintain CPR Parameters (ticpr0100m000)". You can display or print transactions using the following sessions: • Display Integration Transactions by Project / Order (tfgld4510m000) • Print Financial Inventory and WIP Transactions (tdinv8410m000) Project Control (PCS) The transaction type is changed into "Material Costs" to adjust the costs incurred for the project. In addition, the system saves a transaction of the transaction type "Transfer Result" to adjust the previously posted inventory result. You can display or print transactions using the following sessions: • Print Integration Transactions (tfgld4410m000) • Print Financial Project Transactions (tipcs8410m000) No. Project costs are not revalued when the standard cost prices of items are being updated. 4. Cost Price Component for Revaluation The cost price component to which the revaluation of project costs must be posted in the module "Inventory Control (INV)". 5. Description The description of the cost price component. 6. Type of Operation Rates This parameter indicates which type of operation rate determines the calculation of cost prices. Work Center Rate The session "Maintain Work Centers (tirou0101m000)" enables you to link an operation rate code to the work center. It then serves as the work center rate. Task Rate The session "Maintain Tasks (tirou0103m000)" enables you to link an operation rate code to the task. It then serves as the task rate. 7. Number of Years to Retain Standard Cost Price History This parameter indicates for how long the standard cost price must be retained in the system. A historical standard cost price is used, for example, to carry through inventory transactions having an "old date", as may be the case during cycle counting or when ante- dating in the modules "Purchase Control (PUR)", "Sales Control (SLS)" or the package "BAAN Service. The historical standard cost price is also used to determine the inventory value on a past date. Maintain CRP Parameters Session: ticrp0100m000 Application: This session is used to define Capacity Requirement Planning Parameters. Field Data: 1. Day Utilization This parameter determines whether capacity is recorded on a weekly basis or on both a weekly and a daily basis. This parameter setting applies to the entire BAAN Manufacturing package. By default, the system assumes capacity is recorded on a weekly basis. This parameter is used in the modules: • Shop Floor Control (SFC) • Capacity Requirements Planning (CRP) • Project Control (PCS) 2. Length CRP Time Horizon in Days This specifies length of CRP Time horizon in days. Maintain EDM Parameters Session No: tiedm0100m000 Application: This session define parameters for EDM Module Field Data: 1. Series in ECOs When you create an engineering change order ,this parameter determines whether the order number is a consecutive 1-digit/2-digit number, or an entirely free order number. One Digit The change order has a consecutive 1-digit number. Two Digits The change order has a consecutive 2-digit number. No Series The change order number can be freely defined. 2. Customize Copied Item When an engineering bill of material is copied to a customized production bill of material in the sessions "Maintain EBOM Copy Data (tiedm1220m000)" and "Finalize Engineering Data (tiedm3240m000)", several decision factors may cause a standard item to be copied to a project. These decision factors are covered by the method "Determination of Copy Method EBOM -> PBOM". The parameter determines whether the standard item in the customized bill of material remains standard or becomes a customized item. In the latter case, the standard bill of material as well as the standard routing are also copied to the project. If Yes then, the standard item copied to a customized production BOM line for a certain project becomes a customized item, and both the corresponding standard BOM and the standard routing are copied to the related project. If No then the standard item remains a standard item after it is copied to the customized production BOM. 3. PBOM History In the session "Maintain Production BOMs (tibom1110m000)" it is possible to include several BOM lines per position number. Each line is provided with a sequence number (see the field "Sequence Number"). When engineering BOMs are copied to production BOMs, the value of this field determines whether the existing BOM lines must be overwritten, or whether new BOM lines must be added, each with their own sequence number. Yes When the engineering BOM is copied to the production BOM using the sessions "Maintain EBOM Copy Data (tiedm1220m000)" and "Finalize Engineering Data (tiedm3240m000)", the old BOM data will be retained. No All old BOM data will be overwritten. 4. Directory Name for Drawing The directory on your (UNIX) system where the drawing files are located. 5. Display Drawing A shell command causing the drawing to be displayed in a window. Maintain HRA Parameters Session: tihra0100m000 Application: This session defines parameters for Hours Accounting Module. Field Data: 1. Hours Accounting Type Hours accounting can occur by week, day, employee, or order. Week / Employee: The hours account for an employee can be entered for a whole week. The system assumes that the hours transactions are entered in chronological order. This means that the system automatically determines the start day and start time of an hour transaction based on the working time table, after which you only enter the end day and end time for the hour transaction. Week / Order: The hours account for an employee can be entered for a whole week. The system assumes that the hours transactions are entered by order, which means that they are not arranged chronologically. The system asks for a start day and start time, as well as an end day and end time for the hours transactions. Day / Employee: The hours account for an employee can be entered per day. The system assumes that the hours transaction are entered chronologically. This means that it automatically determines the start time of an hours transaction based on the working time table, after which only the end time for the hours transaction must be entered. Day / Order: The hours account for an employee can be entered per day. The system assumes that the hours transactions are entered per order, which means that they are not arranged chronologically. As a result, the system asks for a start time and end time for the hours transactions. When entering hours accounts, you can always switch from "weekly hours accounting" to "daily hours accounting" and vice versa. 2. Clock Time for Hours Accounting The clock time of the hours accounting in minutes or periods. Minutes The system uses the normal time notation: minutes and hours. For example, half past eight is 08:30. Periods If a time recorder is used in your company, its notation may differ from the normal notation in hours and minutes. For example, half past eight is 08:50. Given such a case, you must choose an hours accounting based on periods. If you choose periods, use the next parameter to indicate how many minutes make up a period. 3. Period Length in Minutes The period length in minutes if the clock time is shown in periods. For the above- mentioned example, the period length is 0.6 minutes. 4. Direct Time Recording Yes With direct hours accounting, you can use the session "Enter Hours Accounting (tihra1101m000)" as a DTR (direct time recording) station. When an operation is reported completed, the hours spent are loaded immediately. With a new transaction, a previous active hours transaction is automatically closed. The result is that the planning is always up to date. This method requires additional capacity (man time) for entering hours and printing order documents as part of the issue of orders. The default value for the start time of the operation entered in the hours accounting is the value of the system time. Hours transactions that are entered automatically get the status "1-Active". No The hours spent are processed by the system based on the time records for the employees. 5. Actual Operation Rates For the actual operation rates, you can choose from the following: Estimated Rates: The rates used by the system for actual costing are equal to the rates used for standard costing. This prevents price variances in production. Man and Machine Rates: The rates used by the system for actual costing are equal to the actual man and/or machine rates as defined in the sessions "Maintain Employees (tccom0101m000)" and "Maintain Machines (tirou0102m000)". 6. Capacity Flows The system automatically records capacity flows between work centers. Capacity flows arise when operations are carried out at another work center than where they were planned according to the product's routing (for example, in the case of unexpected subcontracting). Capacity flows also arise when employees or machines are assigned to other work centers. There are two options to record capacity flows: Main Work Centers The system only records capacity flows between the main work centers of your company. Sub Work Centers The system records capacity flows between main work centers and between sub-work centers. 7. Hourly Labor Type for Backflushing The hourly labor type that will be used by the system if the hours are accounted by means of backflushing. 8. Description The description of the hourly labor type. 9. Cover Overhead Costs in Employee Work Center This field is used to specify the financial company to which overhead costs are posted. This is relevant if the work center of the employee whose hours are to be posted belongs to a company that differs from the company where the hours are posted. Yes The overhead cost cover is posted to the financial company of the employee's work center. No The overhead cost cover is posted to the same financial company as where the hours are posted. Maintain ITM Parameters Session: tiitm0100m000 Application: This session is used to define Item Control Parameters. Field Data: 1. Prefix for Item Code Container Items The item prefix will be used to automatically generate item codes for containerized items. For each container the system will insert the code of a containerized item. This code is only used by the system. Users can only view the items and the item by container. The easiest way to define a prefix for unique codes of containerized items is to use 'special' characters, e.g. '@@@@@@'. When new containerized items are inserted, the system will always check if the new item codes are unique. Example: The item 'Potato Salad' is held in three containers: 1, 3 and 5 kg. When the unit set is assigned to the item, the system will create (invisible to the user) the following four items: ? PS = Potato Salad ? @@@@@@0000000001 (1 kg container - PS) ? @@@@@@0000000002 (3 kg container - PS) ? @@@@@@0000000003 (5 kg container - PS) If you use a prefix shorter than six positions (e.g. ##), the other positions are used for counting. In the case of large item files, you are advised to use a shorter prefix. This entire coding is only applicable for Process Items. 2. Signal Code Expired Container Items The signal code used to warn the user that the containerized item is no longer valid. This signal code will be copied to the field "Signal Code" in the session "Maintain Item Data (tiitm0101m000)" for a containerized item, when the item's container unit has been made invalid. Maintain MPS Parameters Session: timps0100m000 Application: This session is used to define parameters used by MPS. Field Data: 1. IRP Implemented Indicates whether IRP is implemented. The field value can only be changed via the session "Maintain MPS Parameters (timps0100m000)". Do not reset the parameter after having changed the value from No to Yes. This may eventually result in a database corruption. 2. Actual Plan Code The code of the actual "Master Production Schedule" (MPS) or logistic plan. Although the functionality for each logistic plan in the module "Master Production Scheduling (MPS)" is in principle the same, planned MPS orders can only be generated for the actual Master Production Schedule, via the session "Generate Master Production Schedule (timps3201m000)". For example, the "available to promise" can only be updated on-line for the actual Master Production Schedule. The data to be entered must be defined in the session "Maintain Plan Codes (timps1101m000)". 3. Description The description of the code in the field "Plan Code". 4. Maximum Number of MPS Orders by Day Determines the maximum number of planned MPS orders which may be generated by the session "Generate Master Production Schedule (timps3201m000)" for each day and for each MPS item. The maximum number of planned MPS orders does NOT affect the planning of RPT-oriented MPS items. 5. Time Fence Multiplier Determines for which horizon planned MPS orders are generated by the session "Generate Master Production Schedule (timps3201m000)". This horizon always relates to the Time Fence for the Master Production Schedule (MPS). This Time Fence can be recorded for each plan item in the session "Maintain Plan Items (timps2101m000)". Here you can enter a factor by which the Time Fence for the Master Production Schedule (MPS) for each plan item must be multiplied. If the horizon for generating planned MPS orders must be equal to the Time Fence for the Master Production Schedule (MPS), enter "1.0". 6. Smoothing Factor for Reschedule-In Message Determines the smoothing factor for reschedule-in messages. These messages can be generated by the session "Generate Master Production Schedule (timps3201m000)" when planned MPS orders are generated. The smoothing factor for reschedule-in messages must be entered as a percentage of the planned inventory level. The greater the smoothing factor, the smaller the number of generated reschedule-in messages. 7. Smoothing Factor for Reschedule-Out Message Determines the smoothing factor for reschedule-out messages. These messages can be generated by the session "Generate Master Production Schedule (timps3201m000)" when planned MPS orders are generated. The smoothing factor for reschedule-out messages must be entered as a percentage of the planned inventory level. The greater the smoothing factor, the smaller the number of generated reschedule-out messages. 8. Only Reschedule Messages for Total Order Quantity Determines whether rescheduling messages must be generated if it is possible to shift the entire order quantity or to reschedule parts of orders. Yes Rescheduling messages are only generated for complete orders. No Messages may also be generated for parts of orders. The system takes the order interval into account, as messages are never created within the order interval. 9. On-Line Available To Promise Update Determines whether "available to promise" for an MPS item must be updated on-line when a planned or actual (physical) inventory transaction is recorded for the related MPS item. Inventory transactions for an MPS item are created when the following orders/quotations are recorded or generated: • sales quotations with the b-object "Sales Quotations" • sales orders with the b-object "Sales Orders" • purchase orders with the b-object "Purchase Orders" • production orders with the b-object "Production Order Control" • service orders with the b-object "Service Order Data" • planned PRP orders with the b-object "Project Planning" Yes The "available to promise" inventory for an MPS item is updated on line. In this respect, the following remarks should be made: • online updating of the "available to promise" inventory for an MPS item is only done for the ACTUAL Master Production Schedule (MPS); • consumption of the planned receipts is confined to the plan period in which the production or purchase order in question is recorded or planned. In other words: there will be NO backward and forward consumption of the planned receipts spanning more than one period. This consumption is automatically performed via the session "Generate Master Production Schedule (timps3201m000)", so that the online calculation of the "available to promise" inventory may deviate from the actual "available to promise" inventory in certain circumstances. No. The "available to promise" inventory for an MPS item is NOT updated on line. 10. Check Available-To-Promise for Sales Orders Determines whether "available to promise" for an MPS item must be checked when recording a sales quotation via the b-object "Sales Quotations" or a sales order via the b- object "Sales Orders". The system compares the quantity required with "Available to Promise Cumulative" (cumulative ATP in the relevant MPS period). In the case of a shortage, the system will give a message when the following conditions are fulfilled: • it concerns an MPS item; • no delivery for an RPL order; • the parameter "On-Line Available To Promise Update" reads "Yes"; • warehouse is nettable; • in the case of a sales quotation, the following extra conditions must be fulfilled: • the field "Aggregate Sales Quotations" reads "Yes"; • the value of the field "Success Percentage" is at least equal to the value of "Minimum Success Percentage"; Considering these conditions and the parameter "Check Available-To-Promise for Sales Orders" having the value "Yes", the system will impose a block in the following cases: • production is standard to order, that is, it concerns a generic item ("Item Type" is "Generic") for which a product variant has been configured. • when "available to promise" is less than the order quantity. Yes The "available to promise" inventory for an MPS item is automatically checked by the system when a sales quotation or sales order is recorded. If this inventory is insufficient on the planned delivery date the system will refuse the sales quotation or sales order. No. The "available to promise" inventory for an MPS item is automatically checked by the system when a sales quotation or sales order is recorded. If this inventory is insufficient on the planned delivery date, it will be reported by the system. However, the sales quotation or sales order will then NOT be refused by the system. 11. MPS Refresh Frequency This field can be used to set the frequency for automatic and repeated refreshing of the Master Production Schedule (MPS). As a result, the latest data is always shown whenever the Master Production Schedule is displayed or modified via the b-object "Master Production Schedule". The frequency of refreshing the display of MPS data can be recorded by entering the interval in seconds. Note: if you enter zero, the display will NOT be refreshed. 12. Demand Exception Message - Upper Boundary Determines the upper bound on the range of margins for generating demand exception messages via the session "Generate Master Production Schedule (timps3201m000)". If the actual demand in a plan period exceeds the upper bound on the planned demand, an exception message can be generated by the system, if desired. The upper bound must be entered as a percentage of the planned demand. 13. Demand Exception Message - Lower Boundary Determines the lower bound on the range of margins for generating demand exception messages via the session "Generate Master Production Schedule (timps3201m000)". If the actual demand in a plan period falls below the lower bound on the planned demand, an exception message can be generated by the system, if desired. The lower bound must be entered as a percentage of the planned demand. 14. Receipt Exception Message - Upper Boundary Determines the upper bound on the range of margins for generating receipt exception messages via the session "Generate Master Production Schedule (timps3201m000)". If the actual receipt in a plan period exceeds the upper bound on the planned receipts, an exception message can be generated by the system, if desired. The upper bound must be entered as a percentage of the planned receipt. 15. Receipt Exception Message - Lower Boundary Determines the lower bound on the range of margins for generating receipt exception messages via the session "Generate Master Production Schedule (timps3201m000)". If the actual receipt in a plan period falls below the lower bound on the planned receipts, an exception message can be generated by the system, if desired. The lower bound must be entered as a percentage of the planned receipt. 16. Inventory Exception Message - Upper Boundary Determines the upper bound on the range of margins for generating inventory exception messages via the session "Generate Master Production Schedule (timps3201m000)". If the actual inventory in a plan period exceeds the upper boundary on the planned inventory, an exception message can be generated by the system, if desired. The upper bound must be entered as a percentage of the planned inventory. 17. Inventory Exception Message - Lower Boundary Determines the lower bound on the range of margins for generating inventory exception messages via the session "Generate Master Production Schedule (timps3201m000)". If the actual inventory in a plan period falls below the lower bound on the planned inventory, an exception message can be generated by the system, if desired. The lower bound must be entered as a percentage of the planned inventory. 18. Device for Messages in Generate MPS Here the user can enter an output device to display or print messages originating from the subsession "Generate Master Production Schedule (timps3201s100)". This field appears in the session "Maintain MPS Parameters (timps0100m000)". Messages are only given if this has been indicated in the subsession, which is called from the session "Maintain Master Production Schedule (timps3101m000)". If no device is specified, the messages will be shown line by line on the screen. However, this may interrupt a transaction. Maintain MRP Parameters Session: timrp0100m000 Application: This session is used to define parameters used MRP module. Field Data: 1. Only Reschedule Messages for Total Order Quantity Determines whether rescheduling messages must be generated if it is possible to shift the entire order quantity or to reschedule parts of orders. Yes Only rescheduling messages are generated for complete orders. No Messages may also be generated for parts of orders. The system takes the order interval into account, as messages are never created within the order interval. 2. Display Item Foreground Yes When the MRP calculation is being performed via a main session, the system shows the items that are being processed. This allows you to view the progress. No The system does not show the items, which results in a faster MRP calculation. 3. Display Item Background Yes When the MRP calculation is being performed via a subsession, the system shows the items that are being processed. This allows you to view the progress. No The system does not show the items, which results in a faster MRP calculation. 4. Display Process Info Foreground Yes When the MRP calculation is being performed via a main session, the system shows the system messages. No The system does not show the system messages, which results in a faster MRP calculation. 5. Display Process Info Background Yes When the MRP calculation is being performed via a subsession, the system shows the system messages. No The system does not show the system messages, which results in a faster MRP calculation. 6. Length MRP Time Horizon in Days To optimize the generation of planned MRP orders, the system reads in the company calendar for a specified period. The default for this period is 2500 days. This means that for all items involved in the MRP run, the start and end dates for the orders must be within the above period. The time horizon indicates the period in which inventory transactions must fall in order to be included in an MRP run. The time horizon serves to prevent irrelevant inventory transactions from being included in MRP runs. This field contains the time horizon length, which is expressed in days. During an MRP run, only the inventory transactions in the time horizon are taken into account. The time horizon starts on the current date. 7. LTO Schedule Method This will specify if Lead Time Offset ( LTO ) Scheduling method is used or not. 8. Repeated Planning in MRP The number of times the MRP run is executed for the manufactured process items, which, in turn, are also produced as co-products or by-products of other process items. If the value of this field is greater than "1", then there will be a reduction of the inventory surplus as a result of the additional receipts (co-products or by-products). Example: Formula 1 -> 10 kg of item C; no co-products. Formula 2 -> 10 kg of item P + 10 kg of co-product C. Actual demand: item C = 20 kg; item P = 10 kg. 1) Planning item C: production batch 20 kg item P: production batch 10 kg -> resulting in 10 kg of co-product C 2) Planning item C: production batch 10 kg when taking into account the 10 kg of item C as a co-product of item P. This procedure is not applicable to standard manufactured items. This is applicable for process items. Maintain PCF Parameters Session: tipcf0100m000 Application: This session is used to define parameters required by Product Configurator Module. Field Data: 1. Multi-Level PCF Choice Structure The module "Product Configuration (PCF)" allows you to use a multi-level question structure for the configuration of product variants. The advantage of using this structure is that product features are linked to the proper generic items, which results in a more modular configuration structure. The structure also makes it possible to include or exclude certain sets of questions during the product configuration process. This parameter determines whether product configuration is applied at multiple levels of the generic product structure. Yes You can apply multi-level product configuration. No You cannot apply multi-level product configuration. 2. PCF in Customer's Language The module "Product Configuration (PCF)" is language-independent, which means that you can record, for example, the descriptions of product features and options in any language. This is especially of value for the communication with customers and other external relations. This parameter determines whether product configuration is applied in the customer's language. This means that the descriptions of product features, options and constraint validation messages are shown in the customer's language in the product configuration process. This feature is an important aid for a proper communication with the customer, particularly in the case of telephone sales. Yes The product configurator displays the descriptions of product features, options and constraint validation messages in the customer's language. No The product configurator displays the descriptions of product features, options and constraint validation messages in your own language. 3. Display Implicit Options In the product configuration process you can use constraints to determine whether or not certain product features or questions must be filled, and whether a default option value is applicable. With the input of an implicit option value (is an option value for a particular product feature, you can also use constraints to indicate whether or not the relevant product feature must be visible during the product configuration process. This parameter is used to indicate whether or not implicit option values must be visualized by the product configurator. You can always deviate from the setting by explicitly specifying this in the constraint of the relevant product feature. Yes Implicit options are visualized by the product configurator. No Implicit options are not visualized by the product configurator. 4. Generate Sales Quotation Texts Indicates whether or not the product configurator automatically generates sales quotation texts for sales quotations after the product configuration process. Yes The product configurator automatically generates sales quotation texts for sales quotations. No The product configurator does not generate any sales quotation texts. 5. Identifying Item Code The module "Product Configuration (PCF)" enables you to automatically generate new (customized) items based on the chosen product variant options and the generic product definition. To generate new items, you can define a generic item code, among other things. The format of the generic item code must be such that the product configurator or product generator can recognize product variants. This parameter is used to indicate whether the item code generated by the product configurator uniquely identifies a product variant in all cases. If this is not the case, you can use the same parameter to indicate that the product configurator must automatically generate a unique item code. The following parameter values are possible: Yes The generated item code uniquely identifies a product variant in all cases. No The generated item code does not uniquely identify a product in all cases. The product configurator itself provides the unique identification of a product variant. 6. Sequence Number of Item Code from Position If the item code generated by the product configurator does not uniquely identify a product variant, the product configurator automatically generates a unique code by adding a sequence number to the generated item code. This parameter enables you to indicate from which position in the item code the sequence number must be generated. If it becomes apparent during the product configuration or product generation process that the number of positions for the sequence number is insufficient to uniquely identify the item code, the product configurator automatically expands the sequence number either to the left or to the right. 6. Sequence Number of Item Code to Position If the item code generated by the product configurator does not uniquely identify a product variant, the product configurator automatically generates a unique code by adding a sequence number to the generated item code. This parameter enables you to indicate up to which position in the item code the sequence number must be generated. If it becomes apparent during the product configuration or product generation process that the number of positions for the sequence number is insufficient to uniquely identify the item code, the product configurator automatically expands the sequence number either to the left or to the right. 7. Product Configurator Version You can use one of the following versions of product configuration Interpreter Version: At runtime, constraints are continually read in, and interpreted or compiled. The advantage of this version is that you can immediately test a generic product model after changes to certain constraints, without first having to recompile all constraints. A disadvantage is that the performance of the product configurator is reduced. Object Version: At runtime, constraints are directly executed by the product configurator as objects, without the necessity to repeatedly read in and interpret or compile constraints at run time. As compared to the interpreter version, the object version may result in a considerable performance improvement, especially in the case of more complex constraints. Prior to using the object version, all constraints must be compiled via the session "Compile Constraints by Generic Item (tipcf2201m000)". For this purpose, you need the compiler 'bic6.1' of BAAN Tools. 8. Character for Space When constraint objects are generated in the module Product Configuration (PCF) a space is automatically replaced by the character entered in this field. 9. Input Option Value The module "Product Configuration (PCF)" enables you to record constraints per generic item. A number of variables predefined in the session "Maintain PCF Parameters (tipcf0100m000)" are used in these constraints. These variables can be filled only once. This means that once product constraints are defined, the descriptions of the variables can no longer be changed! The variable "Input Option Value" allows you to indicate for each product feature whether or not the product configurator must prompt you to enter an option value. This variable has the following features: Constraint section = "Before Input" Application = enter option value y/n Domain = true/false Initialization = true 9. Display Option Value Indicates for each product feature whether the product configurator must display that feature during the product configuration process in the case of an implicit option value. This variable has the following features: Constraint section = "Before Input" Application = Display Option Value y/n Domain = true/false Initialization = true if the parameter "Display Implicit Options" is set to "Yes" = false if the parameter "Display Implicit Options" is set to "No" Note : value is true if "Input Option Value" is true 11. Validating Indicates whether or not the product configurator must validate a given product configuration. As a result, you can control the product configuration process and also prevent the configuration or generation of unallowed product variants. It should be noted that product configuration covers all generic product information, such as product features and options, generic item data, generic bills of material, generic routing, and generic price lists. This variable has the following features: Constraint section = "Validation" Application = validating product configuration Domain = true/false Initialization = true 12. Message The variable "Message" allows you to generate messages during the product configuration process. These messages are displayed as warnings, notices or explanations. Messages can be recorded in constraints in the form of texts or text blocks. When you have chosen product configuration in the customer's language, you can enter message in constraints in any language. Consequently, the product configurator generates and displays the message in the language linked to the customer's language code. This variable has the following features: Constraint section = "Validation" Application = generating messages Domain = alfanumeric: a maximum of 80x25 lines of text Initialization = "standard" message Note = if a message is recorded in a foreign language, the (system) language code must be added to the variable "Message". 13. Item Data The variable "Item Data" allows you to let the product configurator determine the data of a product variant item, such as item code, item description, material, size, norm, and item text. The variable "Item Data" can be used in the "parameter substitution" part of a generic item data constraint. This variable has the following features: Constraint Section = "parameter substitution" Application = determine product variant item data Domain = alphabetic characters Initialization = current value of item data 14. Length The variable "Length" allows you to let the product configurator calculate the length of a BOM component, based on a formula, for example. This variable has the following features: Constraint section = "Parameter Substitution" Application = calculating length of BOM component Domain = fractions Initialization = current value of BOM component's length Note: Unit of BOM component must have physical quantity "Length" or "Area" 15. Width The variable "Width" enables to let the product configurator calculate the width of a BOM component, based on a formula, for example. This variable has the following features: Constraint section = "Parameter Substitution" Application = calculating width of BOM component Domain = Fractions Initialization = current value of BOM component's width Note: Physical quantity of BOM component's unit must be "Area". 16. Number of Units The variable "Number of Units" enables you to let the product configurator calculate a BOM component's number of units, based on a formula, for example. This variable has the following features: Constraint section = "Parameter Substitution" Application = calculation of a BOM component's number of units Domain = integers Initialization = current value of a BOM component's number of units Note: Unit of BOM component must have physical quantity "Length" or "Area" 17. Net Quantity The variable "Net Quantity" enables to let the product configurator calculate the net quantity of a BOM component, based on a formula, for example. This variable has the following features: Constraint section = "Parameter Substitution" Application = calculating net quantity of BOM component Domain = fractions Initialization = current value of net quantity of BOM component Note = If the values of length, width (if any) and number of units are known, the net quantity is automatically derived from these values assuming the net quantity is not filled. 18. Setup Time The variable "Setup Time" enables you to let the product configurator calculate the run time for an operation, based on a formula, for example. This variable has the following features: Constraint section = "Parameter Substitution" Application = calculating setup time for operation Domain = fractions Initialization = current value of operation setup time 19. Production Rate Per The number of products manufactured per unit of time (per hour or minute, depending on the parameter setup). The production rate provides an alternative to recording operation times. The operation with the lowest production rate is considered the "bottleneck" for RPT items. 20. Run Time The variable "Run Time" enables you to let the product configurator calculate the run time for an operation, based on a formula, for example. This variable has the following features: Constraint section = "Parameter Substitution" Application = calculating run time for operation Domain = fractions Initialization = current value of operation run time 21. Price The variable "price" allows you to let the product configurator calculate the purchase or sales price for a product variant, based on a formula, for example. The final purchase or sales price for a product variant may be composed of multiple price and/or surcharge components. Some data can be recorded in the generic purchase or sales price list for each generic item. This variable has the following features: Constraint section = "Parameter Substitution" Application = calculating purchase or sales price of product variant Domain = fractions Initialization = current value of purchase price or 0.0 for the sales price Maintain PCS Parameters Session: tipcs0100m000 Application: This session is used to define parameters required by Project Control module. Field Data: 1. Budget Series You can use this parameter to determine whether series are used in budget numbering. You can select: No Series The system fills the budget number by reading the first free number in the session "Maintain First Free Numbers (tcmcs0147m000)". When a budget number has been used, the first free number in this session is automatically incremented by 1, unless you entered an alphanumeric budget code. One Digit The series is the first digit of the budget number. The remaining digits are assigned by the system. The system reads the first free number which was recorded for the series in the session "Maintain First Free Numbers (tcmcs0147m000)". When a budget number has been used, the first free number is automatically incremented by 1. Alphanumeric budget codes are not allowed. Two Digits The series is the first two digits of the budget number. The remaining digits are assigned by the system. The system reads the first free number which was recorded for the series in the session "Maintain First Free Numbers (tcmcs0147m000)". When a budget number has been used, the first free number is automatically incremented by 1. Alphanumeric budget codes are not allowed. 2. Project Series You can use this parameter to determine whether series are used in project numbering. You can select: No Series When the project number is filled by the system, it reads the first free number that was recorded in the session "Maintain First Free Numbers (tcmcs0147m000)". When a project number has been used, the first free number in this session is automatically incremented by 1, unless you entered an alphanumeric project code. One Digit The series number is the first digit of the project number. Nine series can be used. The remaining digits are assigned by the system. The system reads the first free number which was recorded for the series in the session "Maintain First Free Numbers (tcmcs0147m000)". When a project number has been used, the first free number is automatically incremented by 1. Alphanumeric project codes are not allowed. Two Digits The series number takes up the first two digits of the project number. You can use up to 99 series. The remaining characters are assigned by the system. The system reads the first free number which was recorded for the series in the session "Maintain First Free Numbers (tcmcs0147m000)". When a project number has been used, the first free number is automatically incremented by 1. Alphanumeric project codes are not allowed. 3. Work-in-Process Valuation against This parameter determines how the system calculates the work-in-process values for projects. The parameter is used for calculating the cost prices of sales deliveries and for posting financial project transactions to the BAAN Finance package. You can select from: Estimated Costs The work-in-process value and the cost prices of sales deliveries are calculated on the basis of the estimated project costs. Actual Costs The work-in-process value and the cost prices of sales deliveries are calculated on the basis of the actual project costs. 4. Estimated Costs of Goods Sold Limited by WIP Value This parameter determines how the system calculates the costs of the goods sold if the parameter "Work-in-Process Valuation against" is set to "Estimated Costs". You can select: Yes The calculated estimated costs of the goods sold will never exceed the work-in- process value (per cost price component) for the project. No The calculated estimated costs of the goods sold is not limited by the work-in- process value and is only determined based on the value of the goods sold. 5. Link with Finance This parameter determines whether the module "Project Control (PCS)" is linked to BAAN Finance. Yes Financial project transactions are posted to the package BAAN Finance via the session "Post Integration Transactions to Finance Transactions (tfgld4201m000)". No Financial project transactions are not posted to the package BAAN Finance. 6. Book Cost Pr. & Sales Turnover for Non-Closed Projects This field indicates whether or not the sales cost price and the sales revenue must also be posted for non-closed projects. This a default value when projects are generated. 7. Engineering Revisions on PCS Warehouse Orders Yes You can enter revisions on warehouse orders. The order contains data about the revisions of the standard products used in a project. No The warehouse order does not contain data about revisions. 8. Transfer between TI Projects based on Cost Price If an inventory is transferred from a project to another project within BAAN Manufacturing, the goods amount is computed as follows: Yes Amount = cost price * quantity Cost price is determined on an actual costing basis. If the actual cost price has not yet been calculated, the estimated cost price is taken. No Amount = warehouse price * quantity The project result can be influenced by choosing a warehouse price that differs from the cost price. 9. Transfer between TI/TP Projects based on Cost Price If an inventory is transferred from a project in the package BAAN Manufacturing to a project in the package BAAN Project, the goods amount is computed as follows: Yes Amount = cost price * quantity Cost price is determined on an actual costing basis. If the actual cost price has not yet been calculated, the estimated cost price is taken. No Amount = warehouse price * quantity The project result can be influenced by choosing a warehouse price that differs from the cost price. 10. Book Costprice Sales based on Item The value of this field is the default value for the field "Book Costprice based on item" in the session "Maintain Projects (tipcs2101m000)". 11. Book Costprice Sales Immediately The value of this field is the default value for the field "Book Costprice Immediately" in the session "Maintain Projects (tipcs2101m000)". Maintain ROU Parameters Session: tirou0100m000 Application: This session is used to define parameters required for Routing Module. Field Data: 1. Default Routing This routing will be selected by the system if the routing is independent of the order quantity or if no routing is defined for the required quantity. 2. Production Rate Time Unit The unit of time in which the production rate is expressed. Hour The production rate is expressed in hours. Minute The production rate is expressed in minutes. When you change this parameter, the system comes up with the message "Note: prod.rate time unit '%s' already used; data will not be converted". "%s" stands for the value "Hour" or "Minute". When you have defined norm tables of the type "Production Rate", it is not possible to change this parameter without far-reaching consequences. The reason is that the units recorded in the norm table are based on the setting of this parameter. 3. Use Production Rates The system uses either operation times per item or operation times expressed in the number of items produced by hour or by minute. Depending on the value of this parameter, the system selects the value of the field "Run Time" or "Production Rate Per" (for example, in the sessions "Maintain Routing (tirou2110m000)" and "Maintain Customized Routing (tipcs2170m000)". Yes The value of the field "Production Rate Per" - as in the session "Maintain Routing (tirou2110m000)" - is used in the computation. No The value of the field "Run Time" in the session "Maintain Routing (tirou2110m000)" is used in the computation. 4. Perc. Setup Time for Rate Calculation RPT Items This field is used in the rate calculation for RPT items. It is the percentage of the setup time of an operation that must be subtracted from the basic day capacity to calculate the number of hours available for production. 5. Company Calendar Type The company calendar type indicates how the company calendar, as defined in the session "Maintain Company Calendar (tirou4101m000)", is used. Depending on this value, the system calculates the available capacity. By Work Center: Based on the calendar values entered by work center, the system calculates the available capacity via the session "Maintain Company Calendar (tirou4101m000)". By Company: Based on the calendar values entered for the company in question, the system calculates the available capacity via the session "Maintain Company Calendar (tirou4101m000)". These values are defined under work center "ZZZ". Five Days a Week: Based on the value of the field "Basic Day Capacity per Resource Unit" in the session "Maintain Work Centers (tirou0101m000)", the system computes the available capacity by week by multiplying this value by "5". 6. Stored Days into Past When the company calendar is loaded into internal memory (see the session "Maintain Use of Performance Boosters (tcmcs0197m000)"), you can specify in this field how many past days from now must be stored. The number of days to be entered in this field should cover the bulk of the planned orders. Depending on your situation, this number will vary from 30 to 100 days. For information on the consequences, you are referred to the field "Stored Days into Future". 7. Stored Days into Future When the company calendar is loaded into internal memory (see the session "Maintain Use of Performance Boosters (tcmcs0197m000)"), you can specify in this field how many future days from now must be stored. Loading the company calendar into internal memory will expedite the order planning process. The number of days to be entered in this field should cover the majority of the planned orders. Depending on your specific situation, use 300 to 1200 days. The facility to load the company calendar into internal memory requires additional memory capacity. How much exactly, depends on your specific situation. Three situations are distinguished, depending on the value of the field "Company Calendar Type": Five Days a Week: about 16 * (Stored Days into Future + Stored Days into Past) bytes By Company: about 32 * (Stored Days into Future + Stored Days into Past) bytes By Work Center: about (number of work centers for which a calendar is defined) * 16 * (Stored Days into Future + Stored Days into Past) bytes RPT Parameters Session: tirpt0100m000 Application: This session is used to define parameters required by Repetitive Manufacturing Module. Field Data: 1. Show Current Production Schedules Only This parameter determines whether all production schedules or only the current production schedules must be shown in maintain and display sessions. Yes The system only shows production schedules for the current period. If you choose the "Toggle Show Only Actual Schedules" option in the session "Maintain Production Schedules by RPT Item (tirpt1101m000)" and "Maintain Production Schedules by Scheduling Area (tirpt1111m000)", you can also maintain production schedules for the other periods, regardless of the value of this parameter. No The system shows all production schedules. 2. SFC Order Series for Transferring This order series is one of the specified series as defined in the session "Maintain First Free Numbers (tcmcs0147m000)" for the type "Production Order". Whether series are used depends on the parameter "Series in Production Order Numbers" in the session "Maintain SFC Parameters (tisfc0100m000)". The specified series is used in transferring planned orders to SFC production orders in the following sessions: • Maintain Production Schedules by RPT Item (tirpt1101m000) • Maintain Production Schedules by Scheduling Area (tirpt1111m000) 3. Always Create a New Lot This parameter determines whether a new lot must be created or an existing lot must be used, in the case of a lot item. Yes: The system always creates a new lot. This means that there may be several lots per order. No: The system checks if inventory has already been posted, and tries to use the relevant lot. If the lot is not valid (on hold, for example), it is copied. A single lot can be used for several orders. Maintain SFC Parameters Session: tisfc0100m000 Application: This session is used to define parameters required by Shop Floor Control Module Field Data: 1. Default Layout for Inter Operation Pull Notes The layout of these pull notes which is shown by default on the selection fields in the sessions: • Print Pull Notes by Item (tisfc3401m000), • Print Pull Notes by Order (tisfc3402m000) • Print Pull Notes by Replenishment Order (tisfc3403m000) The data to be entered must be defined in the session "Maintain Pull Note Layouts (tisfc3101m000)". 2. Default Layout for From WIP Pull Nts. The layout of these pull notes which is shown by default on the selection fields in the sessions: • Print Pull Notes by Item (tisfc3401m000), • Print Pull Notes by Order (tisfc3402m000) • Print Pull Notes by Replenishment Order (tisfc3403m000) The data to be entered must be defined in the session "Maintain Pull Note Layouts (tisfc3101m000)". 3. Default Layout for 'To Shop Floor' Pull Notes The layout of these pull notes which is shown by default on the selection fields in the sessions: • Print Pull Notes by Item (tisfc3401m000), • Print Pull Notes by Order (tisfc3402m000) • Print Pull Notes by Replenishment Order (tisfc3403m000) The data to be entered must be defined in the session "Maintain Pull Note Layouts (tisfc3101m000)". 4. Default Layout for Replenishment Order Pull Notes The layout of these pull notes which is shown by default on the selection fields in the sessions: • Print Pull Notes by Item (tisfc3401m000), • Print Pull Notes by Order (tisfc3402m000) • Print Pull Notes by Replenishment Order (tisfc3403m000) The data to be entered must be defined in the session "Maintain Pull Note Layouts (tisfc3101m000)". 5. Printing Production Order Documents Mandatory Use this parameter to determine if the session "Print Order Documents (tisfc0408m000)" is mandatory in the procedure. This parameter does not apply to RPT items. Yes The production order is blocked as long as the documents have not been printed. The order cannot be released for production. No Printing of the order documents is not mandatory. 6. Print Order Covering Note The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 7. Print Routing List The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 7. Print Operation Note The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 8. Print Material List The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 8. Print Material Issue Note The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 9. Print Subcontracting Note The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 10. Print Check List The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 11. Print Sawing List The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 12. Print Collective Sawing List The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 13. Print Cutting List The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 14. Print Collective Cutting List The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 14. Print Receipt Note The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 15. Print Inspection Note The default value for this field in the session "Print Order Documents (tisfc0408m000)". Yes This default value indicates that the document must be printed. No The document need not be printed. 16. Series in Production Order Numbers Determines if series are used in production order numbering. One Digit There are 10 series available (0-9). Two Digits There are 100 series available (000-999). No Series No series are available. Series must be defined in the session "Maintain First Free Numbers (tcmcs0147m000)". 17. Manual Issuing To achieve an accurate issuing procedure, you can opt for subsequent deliveries or direct issues. Yes The quantity to be issued in theory is shown on the field "Subsequent Delivery", allowing you to conduct time-phased issuing manually. No The field "Issue" is filled directly. 17. Use of WIP Warehouses Yes Components are issued from the "WIP Warehouse", either by backflushing or not by backflushing. No Components are issued directly from the warehouse as defined in the bill of material relating to those components. 18. Issue Unlinked Goods from WIP Warehouse Yes If a required component is not linked to an operation, it can be issued from the WIP warehouse linked to the work center where the first operation is performed. No If a required component is not linked to an operation, it can be issued from the warehouse as specified for the BOM component. 19. Update All./Issued Qty (Pl.Qty changes) If the quantity of an operation changes, and if there are material lines linked to that operation, this parameter determines what will happen to allocations and issued quantities (the field "Actual Quantity"). Nothing Nothing happens to allocations and issued quantities. Only Allocations The allocation of material can be reduced up to the sum of the fields "Subsequent Delivery" and "Issue". Any issued quantities remain unchanged. While calculating this reduction, the sum of the fields "Issue", "Subsequent Delivery" and "Actual Quantity" is assumed to match the planned quantity of the finished product. Alloc. and Return Booking The reduction of the allocation may exceed the sum of the fields "Subsequent Delivery" and "Issue". In that case, the field "Subsequent Delivery" is set to zero, and the value of the field "Issue" becomes negative. This means that the next time inventory is issued, the quantity in "Issue" is posted back to the inventory, and the value of the field "Actual Quantity" is reduced by this quantity. 19. Backflushing Method Automatically When quantities or operations are reported completed in the sessions "Report Operations Completed (tisfc0102m000)" and "Report Production Orders Completed (tisfc0202m000)" or via the module "Repetitive Manufacturing (RPT)", the components are automatically and immediately backflushed. Interactively When the order or operation is reported completed, the system will show the question "Backflush materials/hours immediately?". Separately The issuing of components based on theoretical consumption must be done via the session "Backflush Materials and Hours (tisfc0220m000)". 20. Backflush Goods on Outbound Priority when using ILC Yes If the module "Location Control (ILC)" is implemented, goods are automatically backflushed based on outbound priority. No If the module "Location Control (ILC)" is implemented, the normal outbound procedure must be followed. 21. Print Outbound Data on Material List Yes Outbound data is printed on the material issue list (locations, lots, dates, units and quantities). The field "Delivered" indicates if materials have been delivered from stock already. No Outbound data is not printed. 22. Print Outbound Data on Material Issue Note Yes Outbound data is printed on the material issue list (locations, lots, dates, units and quantities). The field "Delivered" indicates if materials have been delivered from stock already. No Outbound data is not printed. 23. Print Outbound Data on Checklist Yes Outbound data is printed on the material issue list (locations, lots, dates, units and quantities). The field "Delivered" indicates if materials have been delivered from stock already. No Outbound data is not printed. 24. Print Sequence of Outbound Data Location Sequence No. The outbound data is shown by location sequence number. Location Sequence The outbound data is shown by location. 24. Multiply Setup Time by Number of Partial Deliveries Yes If the production order states that partial deliveries must be planned separately, the setup time is planned anew. This must be done before you can produce the partial delivery. No The setup time is not taken into account. 25. Automatic Update of Production Order Dates Yes When the planning is modified, the order data is automatically adjusted. No The order data is not adjusted. 26. On order date prod. order (del.dt ord.>fin.dt latest operation) Determines on which date the time-phased inventory movement date for the production order is based, if the production order is expected to be delivered in time (this is the case when the earliest finish date for the latest operation of the production order lies before the delivery date for the production order). The time-phased inventory movement date is the date on which a product is expected to be received in inventory. EXAMPLE | Production Order: | | | | +---------------------------------------------------------------------------| | | Operations: A | | +--10---slack+ | | +------- - - +-----20--------+ | | +------------------30----- slack + | | +--------------+ - - - | | | Time -----> B C | A: order delivery date B: earliest finish date of latest operation C: latest finish date of latest operation If the earliest finish date of latest operation (B) lies before the order delivery date (A), this parameter is applicable. Otherwise the parameter "On order date prod. order (del.dt ord.<=fin.dt latest operation)" will be applied. Order Delivery Date If this parameter is valid, the time-phased inventory movements are based on the order delivery date (A in diagram). Earl.Fin.Date Latest Opr. If this parameter is valid, the time-phased inventory movements are based on the earliest finish date of the latest operation (B in diagram). Lat. Fin.Date Latest Opr. If this parameter is valid, the time-phased inventory movements are based on the latest finish date of the latest operation (C in diagram). Min. Order/Oper. Fin.Date If this parameter is valid, the time-phased inventory movements are based on (A) or (C), whichever comes first. Max. Order/Oper. Fin.Date If this parameter is valid, the time-phased inventory movements are based on (A) or (C), whichever comes later. 2. On order date prod. order (del.dt ord.<=fin.dt latest operation) Determines on which date the time-phased inventory movement date for the products resulting from the production order is based, if the production order is likely to be delivered late (the earliest finish date for the latest operation for the production orderlies after the delivery date for production order). The time-phased inventory movement date is the date on which a product is expected to be received in inventory. EXAMPLE: | Production Order: | | | | +----------------------------------------------------------------------------------------| | | Operations: A | | +--10---slack+ | | +------- - - +-----20--------+ | | +------------------30----- slack + | | +--------------+ - - - | | | Time -----> B C | A: order delivery date B: earliest finish date of latest operation C: latest finish date of latest operation This parameter is valid, if the earliest finish date of latest operation (B) comes after the order delivery date (A). Order Delivery Date If this parameter is valid, the time-phased inventory movements are based on the order delivery date (A in diagram). Earl.Fin.Date Latest Opr. If this parameter is valid, the time-phased inventory movements are based on the earliest finish date of the latest operation (B in diagram). 3. Reporting Method for Previous Operations Automatically When an operation is reported completed in the session "Report Operations Completed (tisfc0102m000)", the quantity reported completed for the previous operation is automatically adjusted to the quantity reported completed for the current operation. Interactively When an operation is reported completed in the session "Report Operations Completed (tisfc0102m000)", you are asked if the quantity reported completed for the previous operation should be adjusted to the quantity reported completed for the current operation. None The quantity reported completed for the previous operation is not adjusted, but must first be reported completed manually. 4. Calculation Method Remaining Production Time Planned Quantity The remaining production time is calculated by multiplying the remaining order quantity by the order-dependent run time. Time Spent The remaining production time is calculated by subtracting the hours entered in the session 5. Update Method for Estimated Hours Automatically When the planning is being modified, the cost estimate is automatically adapted. Interactively When the planning is modified, you are asked if the cost estimate must be adapted accordingly. None The cost estimate is not adapted. 6. Sorting Method Components Determines how the components, which are included in the estimate from the bill of material, are sorted in the estimate. This is especially important if use is made of phantoms. Position numbers are always increased with a factor of 10. Item All components are sorted by item code. Operation and Item Components are sorted first by operation (at the highest level), and subsequently by item code. If no materials are linked to operations, the value of this option is the same as "Item". Pos. Highest BOM Level The position number from the highest BOM level is used for sorting purposes. Own BOM Position The position number entered at component level is used for sorting purposes. 7. Device for Processing Backflushed Hours The output device where the result of the hours posted are rendered via backflushing. The device must be defined in "Device Management". 8. Device for Issuing Backflushed Materials The output device where the result of the components issued via backflushing is rendered. 8. Engineering Revisions Active This parameter is only modifiable if the parameter "ECOs Used" in the session "Maintain System Configuration Parameters (tisfc0000m000)" is set to "Yes". Yes There is a direct relationship between the modules "Engineering Data Management (EDM)" and "Shop Floor Control (SFC)" for traceability purposes, for example: which revision was used and when? No There is no direct relationship between these modules. Maintain INV Parameters Session: tdinv0100m000 Application: This session is used to define Inventory Paramaters. Field Data: 1. Block During Warehouse Cycle Counting Use this parameter to block inventory transactions for a item/warehouse combination if inventory is being taken. Yes When cycle counting is in progress in a warehouse, no transactions will be carried out for the items printed on the counting lists. No Inventory transactions are allowed during cycle counting. 2. Negative Inventory Allowed Use this parameter to indicate if transactions in the "Shop Floor Control (SFC)", "Inventory Control (INV)" and "Sales Control (SLS)" modules must be blocked if they would cause negative inventory. Yes Negative inventory are accepted. No Inventory transaction in the above modules are blocked if they would cause negative inventory. 3. Auto Refresh Inventory Display by Item/Comp./Ware- h. This parameter determines whether the inventory data about a selected standard item will be updated in the session "Display Warehouse Inventory by Item, Company and Warehouse (tdinv0515m000)". No Once read in, the inventory data about the item will be used until the session is quit. The information is not refreshed meanwhile. Yes Whenever an item is called in the session "Display Warehouse Inventory by Item, Company and Warehouse (tdinv0515m000)", the most recent data is written. The session will always show the most recent information. A disadvantage is, that such intermediate updates are time-consuming. 4. Inventory Transaction History Maintaining history records of physical inventory transactions will allow calling displays of such transactions, as well as creating daybook entries for posting them to the "BAAN Finance" package. Physical inventory transactions may be issues or receipts. Yes The system maintains a history of physical inventory transactions. No The system does not maintain a history of physical inventory transactions. 5. Item Issue History Yes The system maintains a record of the total issue for all warehouses. This data is required if you want the system to calculate a demand forecast for all warehouses in the session "Calculate Demand Forecast by Item (tdinv4230m000)". This history is also necessary when you want to use the session "Perform ABC Analysis by Item (tdinv6210m000)" at a later stage. No The system does not maintain a record of the total issue for all warehouses. 6. Item Issue History by Warehouse Yes The system maintains a history record of the item issue per warehouse. This data is required if you want the system to calculate a demand forecast by item in the session "Calculate Demand Forecast by Item (tdinv4230m000)". No The system does not maintain a history record of the item issue per warehouse. 7. Period Length for Item History This parameter determines the length of the periods used in building up history records. This period length is used in several modules. Possible values: 4 Weeks The year is divided into 13 periods of 4 weeks. Month Each calendar month constitutes a period. 8. Boundary Class A A items are the items with the highest turnover. The upper boundary of class A indicates the percentage of the total turnover which the class of A items yields as a whole. The sum of the A, B, and C boundaries must total 100%. In the ABC analysis, the system calculates the turnover by item and the total turnover of all items. It subsequently calculates the relative turnover in terms of a percentage of the total turnover. This percentage is used to classify the items into three groups. For example: A items, together contributing 80% to total turnover, B items contributing 15% and C items contributing 5%. The system follows the following procedure: The items are sorted by highest relative turnover. The turnover percentages are added in sequence of decreasing relative turnover until the boundary entered in this field is reached. The items in this group are called A items. The same procedure is followed for B and C items. 9. Counting Interval in Weeks Class A The counting interval between two subsequent counts of an A item in weeks. When executing the session "Generate Cycle Counting Orders (tdinv1220m000)", the system checks if the last counting date is longer ago than the counting interval entered. If that is the case, the item is printed on the counting list produced in the session "Print Cycle Counting Orders (tdinv1420m000)". 10. Boundary Class B B items have the highest turnover except for A items. The upper boundary of class B indicates the percentage of the total turnover which the class of B items yields as a whole. The sum of the A, B, and C boundaries must total 100%. 11. Counting Interval in Weeks Class B The counting interval between two subsequent counts of a B item in weeks. When executing the session "Generate Cycle Counting Orders (tdinv1220m000)", the system checks if the last counting date is longer ago than the counting interval entered. If that is the case, the item is printed on the counting list produced in the session "Print Cycle Counting Orders (tdinv1420m000)". 12. Boundary Class C C items have the lowest turnover. The upper boundary of class C indicates the percentage of the total turnover which the class of C items yields as a whole. The sum of the A, B, and C boundaries must total 100%. 13. Counting Interval in Weeks Class C The counting interval between two subsequent counts of a C item in weeks. When executing the session "Generate Cycle Counting Orders (tdinv1220m000)", the system checks if the last counting date is longer ago than the counting interval entered. If that is the case, the item is printed on the counting list produced in the session "Print Cycle Counting Orders (tdinv1420m000)". 14. To Turnover Rate (Upper Boundary) This field contains the upper boundary of a specific turnover rate. The value must be higher than the lower boundary of the same interval. The turnover rate of an item is calculated as follows: Turnover rate = Annual issue / Inventory On –hand If the turnover rate is greater than the upper boundary entered in the previous line and less than or equal to the value to be entered in this field, the slow-moving percentage applies which you enter into the next field. 15. Slow-Moving Percentage This field contains one of ten possible slow-moving percentages. These must be entered in order of decreasing value. The percentages are used in the session "Perform Slow- Moving Analysis by Item (tdinv6220m000)". The slow-moving percentage for the turnover rate defined on the previous field. 16. Link with FINANCE Using this parameter you can link the "Inventory Control (INV)" module to the "BAAN Finance" package. This link will allow posting of physical inventory transactions (issues and receipts) to the "BAAN Finance" package. Yes When executing the session "Post Integration Transactions to Finance Transactions (tfgld4201m000)", the system generates daybook entries for physical inventory transactions. No When executing the session "Post Integration Transactions to Finance Transactions (tfgld4201m000)", the system does not generate daybook entries for physical inventory transactions. 17. Link PUR Orders to FINANCE Using this parameter you can link the "Inventory Control (INV)" module to the "BAAN Finance" package for economic stock transactions (on order) resulting from purchase orders. When executing the session "Post Integration Transactions to Finance Transactions (tfgld4201m000)", the system generates daybook entries for economic stock transactions. Yes The link is enabled. No The link is disabled. 18. Link SLS Orders to FINANCE Using this parameter you can link the "Inventory Control (INV)" module to the "BAAN Finance" package for economic stock transactions (allocations) resulting from sales orders. When executing the session "Post Integration Transactions to Finance Transactions (tfgld4201m000)", the system generates daybook entries for economic stock transactions. Yes The link is enabled. No The link is disabled. 19. Time-Phased Order Point This parameter controls with which type of inventory the reorder point must be compared when generating order advice for items using the session "Generate Planned INV Orders (tdinv3201m000)". Yes When generating order advice the system checks if the balance of inventory on hand and planned inventory transactions during the time fence falls below the reorder point. The duration of the time fence is calculated for each item: Time Fence = Factor x Order Lead Time + Constant| An item's order lead time is defined in "Maintain Item Data (tiitm0101m000)". The "Factor" and the "Constant" are specified in the following fields. No The session "Generate Planned INV Orders (tdinv3201m000)" checks if the economic stock falls below the reorder point. 20. Time Fence If you have opted for a "time-phased" order advice, you have to define the "Time Fence". The "Time Fence" determines how far the system must look into the future when taking into account planned inventory transactions in order to determine the order advice. In this field you define the value of the parameter "Factor" in the formula: Time Fence = Factor x Order Lead Time + Constant| 21. Time Fence Constant If you have opted for a "time-phased" order advice, you have to define a "Time Fence". The "Time Fence" determines how far the system must look into the future when taking into account planned inventory transactions in order to determine the order advice. In this field you define the value of the parameter "Constant" in the Time Fence formula. Maintain Purchase Contract Parameters Session: tdpur3100m000 Application: This session is used to define parameters required by Purchase Contracts. Field Data: 1. Contract Module Implemented This parameter determines if you can control purchase contracts. Yes: You can define contracts in the session "Maintain Purchase Contracts (tdpur3101m000)". No: You cannot define contracts in that session. 2. Series in Contract Numbering With this parameter you can determine whether the system will use number series when numbering the contracts. There are three options: No Series The system fills in the number by retrieving the first free number from the session "Maintain First Free Numbers (tcmcs0147m000)". As soon as a contract number has been used, the first free number recorded in this session is automatically incremented by one. One Digit The series number is the first digit of the contract number (the first position). The remaining digits are assigned by the system. Two Digits The series number comprises the first two digits of the contract number (the first two positions). The remaining digits are assigned by the system. 3. Maintaining Contracts Always Allowed To change contract data, a contract must have the status "free". Yes: You can restore the contract status from "active" to "free" for a contract for which goods have been called off or on which turnover has already been booked. This is especially important when you want to change the data of a current contract. No: You cannot restore the contract status from "active" to "free" for such a contract. 4. Copy Special Contract to Normal Contract Yes A special contract may be copied to a normal contract. No Special contracts cannot be copied to normal contracts. This parameter setup avoids errors, because special and normal contracts may have different price policies. 5. Copy Normal Contract to Special Contract Yes A normal contract may be copied to a special contract. No Normal contracts cannot be copied to special contracts. This parameter setup avoids errors, because special and normal contracts may have different price policies. 6. Evaluate Contract before Deleting Contract evaluation means that during or at the end of the contract lead time you check whether the agreed quantities have been purchased from the supplier. Evaluation is carried out using the session "Evaluate Purchase Contracts (tdpur3420m000)". Yes Contract evaluation is mandatory. All contract lines must have been evaluated before you delete a contract with the status "terminated". No Contract evaluation is not mandatory. All contract lines need not have been evaluated before you delete a contract. Note: You can delete a contract in two ways: • manually by choosing option "Delete Record(s) [mark.delete]" in session "Maintain Purchase Contracts (tdpur3101m000)" (to be able to • using the session "Terminate and/or Delete Purchase Contracts (tdpur3203m000)" You can also remove contracts with the status "free". 7. Update Planned Inventory Transactions You can call a display of planned inventory transactions using various sessions from the "Inventory Control (INV)" module. In order to be able to use these sessions to obtain information about the quantities stated in the delivery schedules of contracts, the planned inventory transactions have to be updated from the "Purchase Contracts" module. This is accomplished by setting the present parameter to "Yes". Yes The planned inventory transactions are stored under order type "Purchase Contract". As soon as a purchase order is linked to a contract, a planned inventory transaction with order type "Purchase Order" is generated in the module "Inventory Control (INV)". This results in an increase of the planned quantity booked to this order type, and a decrease of the planned quantity with order type "Purchase Contract". No No record is kept of planned inventory transactions from the module "Purchase Contracts". 8. Log Contract Transactions If you choose to log contract header transactions, the system will retain a copy of the original contract. No logging: The system does not log what transaction has been entered by which user, and on what day and time. Last change: For reasons of system security it is useful to know which user entered a transaction, and at what moment. Therefore the system registers the transaction type, login code, transaction date and time of the last transaction. All changes: For reasons of system security it is useful to know which user entered a transaction, and at what moment. Therefore the system registers the transaction type, login code, transaction date and time of each transaction. 9. Log Contract Line Transactions If you choose to log contract line transactions, the system will retain a copy of the original contract. No logging:The system does not log what transaction has been entered by which user, and on what day and time. Last change: For reasons of system security it is useful to know which user entered a transaction, and at what moment. Therefore the system registers the transaction type, login code, transaction date and time of the last transaction. All changes: For reasons of system security it is useful to know which user entered a transaction, and at what moment. Therefore the system registers the transaction type, login code, transaction date and time of each transaction. 10. Log Turnover on Contract Yes For each contract line the called quantity, invoiced quantity and invoiced amount are displayed in the following sessions: • Display Purchase Contract Results (tdpur3513m000) • Display Turnover History by Purchase Contract (tdpur3535m000) • Display Purchase Contract Line History by Contract Number (tdpur3531s000) No The called quantity, invoiced quantity and invoiced amount are not displayed in the above sessions. 11. Print Contract Acknowledgment In the field "Contract Acknowledgement" in the session "Maintain Purchase Contracts (tdpur3101m000)" you can indicate whether a contract acknowledgement should be printed. The default field value is defined using this parameter. Printing a contract acknowledgement is not a mandatory step in the contract procedure. 12. Reprint Contract Acknowl. after Modification The field "Print Status" in the session "Maintain Purchase Contracts (tdpur3101m000)" shows whether the contract acknowledgement has been printed or changed. The possible values of the field are: "not printed", "printed" and "changed". Yes Once the contract is modified, the print status in the session "Maintain Purchase Contracts (tdpur3101m000)" is automatically set to "changed". This means that you can reprint the contract acknowledgement. No After a change to the contract, the print status remains on "printed", which means that you cannot reprint the contract acknowledgement. 13. Number of Extra Contract Acknowledgment Copies The number of contract acknowledgement copies to be printed in addition to the original. 14. Link with PCS Module You cannot create purchase contracts for customized items. If the customized item is derived from a standard item, this parameter enables you to determine whether the purchase contract for the standard item is valid for that customized item as well. Yes If a purchase order is created for a customized item, and the item is derived from a standard item, the system will check whether a purchase contract applying to that standard item exists. An item is derived from a standard item if the field "Standard Item" in the session "Maintain Customized Item Data (tipcs2121m000)" is filled. No If a purchase order is created for a customized item, the system does not check if the item is derived from a standard item. Hence, call orders for a contract are not possible (with respect to customized items). 15. Action on Exceeding Maximum Quantity You can record the maximum quantity for the item in the session "Maintain Purchase Contract Lines (tdpur3102s000)". When you create purchase orders to which a contract is applicable, the system keeps track of the total quantity purchased for the contract. This parameter enables you to determine which action is to be carried out if the maximum quantity that may be called is exceeded. The following actions are possible: Adopt contract: The purchase order line is linked to the contract. The contract agreements apply to the total quantity on the order line, irrespective of the excess of the maximum quantity. Interactive: When you create the purchase order, the system will prompt you to answer a number of questions. Skip contract: The purchase order line is not linked to the contract. 16. Several Special Contracts Allowed by Purchase Order This parameter is important to determine the default price and discount on a purchase order line. The procedure depends on the input of the field "Special Contract" in the session Maintain Purchase Orders (tdpur4101m000). You can either enter a value or leave the field blank. The "Determine Default Price and Discount" procedure when the field "Special Contract" is empty: Yes When an order line is created, the session Display Selected Purchase Contract Lines (tdpur3512s000) is automatically started. This session displays all special contract lines. Once you have marked the desired special contract, the system searches for a price and discount in that contract. If they are found, they are included in the purchase order line as default values. The system continues searching for a price and discount in the normal contract if: • there is no special contract • no special contract is selected • there is no price agreement for the item in the special contract If the price and discount are not found in the normal contract, the system continues searching in the price and discount lists. No When an order line is entered, the session Display Selected Purchase Contract Lines (tdpur3512s000) is not called. The default price and discount is determined by searching in a normal contract. • is there a normal contract for the item? • is there a normal contract for the price group? Once a contract has been found, the contract line is linked to the order. If there is no price in the normal contract, the system continues searching in the price and discount lists. The "Determine Default Price and Discount" procedure if the field "Special Contract" is filled: Yes If there is only 1 special contract, the system searches for the price and discount in this contract (recorded in the order header). If no price and discount are found, the system continues searching in an normal contract. If a contract is found, the contract line in question is linked to the order. If there is no price in the normal contract, the system continues searching in the price and discount lists. If there is more than one special contract, the session Display Selected Purchase Contract Lines (tdpur3512s000) is called when an order line is created. This session displays all special contract lines. The first contract which is displayed and marked by default is the special contract recorded in the order header. When the desired special contract has been marked, the system searches for a price and discount in this special contract. If they are found, they are included in the purchase order line as default values. The system searches for a price and discount in the normal contract if: • there is no special contract • no special contract is selected • there is no price agreement for the item in the special contract If no price and discount are found in a normal contract, the system continues searching in the price and discount lists. No The system searches for the price and discount in the special contract recorded in the order header. If no price and discount are found, the system continues searching in a normal contract. Once a contract has been found, the contract line in question is linked to the order. If there is no price in the special contract, the system continues searching in the price and discount lists. When order lines are created, the session Display Selected Purchase Contract Lines (tdpur3512s000) is not started with this parameter setup. 17. Terminate Relation after Order Line Transaction This parameter determines whether the "contract - order" relation should be retained if the price and/or discount of the purchase order is adjusted in the session "Maintain Purchase Order Lines (tdpur4102s000)". Yes The "order - contract" relation is interrupted: • if you modify the following fields in the session "Maintain Purchase Order Lines (tdpur4102s000)": * project * item code * container * price * discount • if you change the price or discount in the session "Change Prices/Discounts after 'Maintain Receipts' (tdpur4122m000)" • if you search a price in the price and discount lists on the field "Price" in "Maintain Purchase Order Lines (tdpur4102s000)" and "Maintain Purchase Order Lines (Wholesale) (tdpur4105s000)" No The relation contract - order is retained after a change in the purchase order line data. If you do want to interrupt the relation, choose option "Return to Input Field [restart.input]" in the sessions "Maintain Purchase Order Lines (tdpur4102s000)" and "Maintain Purchase Order Lines (Wholesale) (tdpur4105s000)". 18. Step Size for Purchase Contracts Interval between subsequent purchase contract position numbers. Maintain Financial Integration Parameters Session: tdpur6100m000 Application: This session is used to maintain Financial Integration Parameters. Field Data: 1. Link with FINANCE Yes You can only remove the order data and purchase invoice data (which are used in the package "BAAN Finance") in the session "Process Delivered Purchase Orders (tdpur4223m000)" if purchase invoice matching within the package "BAAN Finance" has been carried out. If the order data is removed, the purchase invoice data is removed as well. No When removing order data in the above session, the system does not check if the purchase invoice matching has taken place. Maintain Purchase Order History Parameters Session: tdpur5100m000 Application: This session is used to set purchase order history parameters. Field Data: 1. Log Purchase Order History This parameter determines whether the purchase order history will be logged, and if so, under which conditions. The following data is logged: • creations (each addition to or change of a purchase order line; in case of a change in a line, a new line is created and the original line logged as a deletion) • cancellations (canceled lines) • invoiced turnover (each invoiced purchase order line) All: Creations, cancellations and invoiced turnover are logged. Only Updates w/Chg Codes: Creations, cancellations and invoiced turnover are logged only if a “Change Type Code” or a “Change Reason Code” is entered for the change or addition. Change codes may be entered using session “Maintain Purchase Order Change Codes (tdpur5106s000)”. None: Creations and cancellations are never logged. 2. Prompt for Change Codes Use this field to specify whether prompting for purchase order change codes whenever changes are made to a purchase order (header or line). Yes You are prompted for purchase order change code information whenever changes are made to the purchase order. Once the purchase order is modified and the changes are saved in sessions "Maintain Purchase Orders (tdpur4101m000)" or "Maintain Purchase Order Lines (tdpur4102s000)", you are automatically zoomed to session "Maintain Purchase Order Change Codes (tdpur5106s000)" to enter purchase order change code information. No You are not prompted for purchase order change code information whenever changes are made to the purchase order. You are NOT automatically zoomed to session "Maintain Purchase Order Change Codes (tdpur5106s000)" to enter purchase order change code information, when changes are made to the purchase order in sessions "Maintain Purchase Orders (tdpur4101m000)" or "Maintain Purchase Order Lines (tdpur4102s000)". 3. Base Price for Gross Profit Calculation In the module "Purchase Control (PUR)" it is possible to inquire the profit percentage. Here is where you define how that percentage should be calculated. Cost Price Cost - Turnover Gross Profit(%) = --------------------- x 100% Costs Purchase Price Cost - Turnover Gross Profit(%) = ----------------------------- x 100% Turnover Maintain Purchase Inquiry Parameters Session: tdpur1100m000 Application: This session is used to define Purchase Inquiry Parameters. Field Data: 1. Log Inquiry History Yes The system keeps a record of the inquiry history. No The system does not keep a record of the inquiry history. 2. Default Term for Returning Inquiries The number of days between the inquiry date and the return date of the inquiry. The return date is the last date on which the receiver may return the inquiry. The system uses this parameter to calculate the default return date. This can be overwritten in the session "Maintain Inquiry Lines (tdpur1102s000)". 3. Number of Extra Inquiry Copies The number of copies to be printed in addition to the original inquiry in the session "Print Inquiries (tdpur1401m000)". 4. Number of Extra Inquiry Reminder Copies The number of copies to be printed in addition to the original reminder in the session "Print Inquiry Reminders (tdpur1402m000)". 5. Series in Inquiry Numbering With this parameter you can determine whether the system will use number series when numbering the inquiries. No series One digit Two digits 6. Step Size for Purchase Inquiries Interval between subsequent purchase inquiry position numbers. 7. Check On Actual Purchase Orders This parameter determines if during quotation entry the system should produce a warning if there already exist current purchase orders for the combination of item and supplier concerned. No The system does NOT display a warning. Yes The system displays a warning. Maintain Purchase Order Parameters Session: tdpur0100m000 Application: This session is used to define parameters which are used in Purchase Order Control. Field Data: 1. Goods Amount/Discount on Purchase Orders This parameter determines how the goods and discounts amounts on the purchase order are presented. The possibilities are illustrated by way of an example. The order discount on a purchase order is 10%. On the order, there are the following order lines: Quantity Price Discount 1 100 5% 2 100 10% Gross goods amount = 300 Order line discount amount = 5 + 20 = 25 Order discount amount = 10% of 275 = 27.50 Total discount amount = 52.50 Net goods amount = 247.50 You can choose from the following parameter settings: Net Amount/No Discount: The net goods amount is printed (247.50); the discount amount is not printed. Gross Amount and Discount: The following amounts are printed: • gross goods amount (300) • order line discount + order discount amount (52.50) Net Amount and Discount: The following amounts are printed: • net goods amount (247.50) • order line discount + order discount amount (52.50) 2. Manuf.Item or Components on Goods Received Notes This parameter determines whether in case of the purchase of a manufactured item, the main item, the components or both are printed on the goods received note. Manufactured Item: The manufactured item is printed on the goods received note. Components: If the field "Inventory Posting Status (Purchase)" on the order line has been set to Post to Component, the system will print the components defined in the session "Maintain Production BOMs (tibom1110m000)". Both: If the field "Inventory Posting Status (Purchase)" on the order line has been set to Post to Component, the system will print both the main item and the components which have been defined in the session "Maintain Production BOMs (tibom1110m000)". The main item is printed underscored without quantities. 3. Cost/Service Items on Goods Received Notes Indicate if the session "Print Goods Received Notes (tdpur4410m000)" should also print the non-physical items. No: Items of the item types Cost and Service will not be printed. Only Cost Items: Items of the item type Service will not be printed. Only Service Items: Items of the item type Cost will not be printed. Both: Both item types will be printed. 4. Cost/Service Items on Claim Notes Indicate if the session "Print Claims (tdpur4420m000)" should also print the non- physical items. No: Items of the item types Cost and Service will not be printed. Only Cost Items: Items of the item type Service will not be printed. Only Service Items: Items of the item type Cost will not be printed. Both: Both item types will be printed. 5. Goods Amount/Discount on Purchase Invoices This parameter determines how the goods and discounts amounts on the invoice are presented. The possibilities are illustrated by way of an example. The order discount on a purchase order is 10%. On the order, there are the following order lines: Quantity Price Discount 1 100 5% 2 100 10% Gross goods amount = 300 Order line discount amount = 5 + 20 = 25 Order discount amount = 10% of 275 = 27.50 Total discount amount = 52.50 Net goods amount = 247.50. You can choose from the following parameter settings: Net Amount/No Discount: The net goods amount is printed (247.50); the discount amount is not printed. Gross Amount and Discount: The following amounts are printed: • gross goods amount (300) • order line discount + order discount amount (52.50) Net Amount and Discount: The following amounts are printed: • net goods amount (247.50) • order line discount + order discount amount (52.50) 6. Number of Extra Reminder Copies The number of copies of a reminder to be printed in addition to the original. 7. Purchase Order Unit of Measure If an item's purchase unit has length, area or volume for its physical quantity, it is possible to enter its measures in the session "Maintain Item Dimensions (tdpur4811s000) 9. Back Orders Allowed Yes When entering receipts or approvals you may record quantities as "back order". This parameter setting also allows the user to maintain back orders in the session "Maintain Back Orders (tdpur4130m000)". No You cannot create back orders for goods to be received. The "Back Order" fields in the sessions "Maintain Receipts (tdpur4120m000)" and "Maintain Approvals (tdpur4121m000)" are always on 0 and cannot be modified. The user cannot execute the session "Maintain Back Orders (tdpur4130m000)". 10. Series in Order Numbering Using this parameter you can determine if series are to be used to number purchase orders. No Series: The system fills in the first free number as registered in the session "Maintain First Free Numbers (tcmcs0147m000)". One Digit: The series number fills the first position of the purchase order number. Two Digits: The series number fills the first two positions of the purchase order number. The remaining digits are filled by the system with the first free number registered in the session "Maintain First Free Numbers (tcmcs0147m000)". 11. Series in Invoice Numbering Using this parameter you can determine if series are to be used to number the purchase invoices in session "Print Purchase Invoices (tdpur4404m000)". It can have three options No Series One Digit Two Digit 12. Search for Price and/or Discount Based on Order Date When determining the default order line price and discount the system checks if the order date falls within the period of effectivity of the price or discount list. System Date When determining the default order line price and discount the system checks if the system date falls within the period of effectivity of the price or discount list. Delivery Date When determining the default order line price and discount the system checks if the delivery date falls within the period of effectivity of the price or discount list. 13. Step Size for Purchase Order Lines The interval between two subsequent purchase order line numbers. 14. Number of Discount Levels This parameter allows you to indicate how many discount levels should be used within the module "Purchase Control (PUR)". If multiple discount levels are used, then the eventual discount will result from the various discount percentages and/or amounts indicated at the different levels. Example: Gross Amount = 1000 (pieces) x 5 (price) = 5000 Discount Level Percentage Method Discount Net 1 10 Gross 500(0.10*5000) 4500 2 1 Gross 1000(1.00*1000) 3500 3 5 Net 175(0.05*3500) 3325 A discount percentage or a discount amount can be entered. Discount amounts refer to one unit and are deducted from the base amount (gross) or from the remaining net amount of the previous level (net). 15. Default Alt. Item Code System In the "Purchase Control (PUR)" module you can enter items into quotation inquiries, contracts and orders using an alternative item coding system. This code system should, of course, be of the type "General" (session "Maintain Item Code Systems (tcmcs0127m000)"). 16. Number of BOM-levels to be reduced In the "Purchase Control (PUR)" module you can copy bills of material to purchase orders. In addition, it is possible to post bill of material components to the inventory instead of main items. Using this parameter you can indicate the number of bill of material levels that are to be copied/posted to inventory. 17 . Check On Actual Purchase Inquiries This parameter determines if during order entry the system should produce a warning if there already exist purchase inquiries for the combination of item and supplier concerned. No The system does NOT display a warning. Yes The system displays a warning. 18.Series in Receipt Numbering Using this parameter you can determine if series are to be used for the receipt numbers under which goods received are registered in the session Maintain Receipts (tdpur4120m000). The following values are possible: No Series One Digit Two Digits 19. Maintain Receipts by Receipt Number/Order Number Receipt Number It is advised to select this setting if you wish to record the receipts on the basis of the supplier's packing slip. As more than one order may be recorded on the packing slip, you cannot work by order only. Hence, when you have selected this setting the session Select Receipts by Order Number (tdpur4224s000) is not called after you have entered a receipt number and packing slip number in Maintain Receipts (tdpur4120m000). Receipts from different orders may be recorded under the same receipt number. Order Number You should select this parameter setting if you wish to record receipts using the goods received note. As the goods receipt note is based on orders, you will wish to see the order lines on the screen. After you have entered a receipt and a packing slip number in the session Maintain Receipts (tdpur4120m000), the session Select Receipts by Order Number (tdpur4224s000) is automatically called. In this session you can assign all the lines of an order to a receipt number. Subsequently you can maintain the receipts for these lines. 20. Automatic Recalculation of Prices and Discounts This parameter indicates whether and how the session "Recalculate Purchase Price and Discount (tdpur4810s000)" is activated after session "Maintain Purchase Order Lines (tdpur4102s000)". No Session "Recalculate Purchase Price and Discount (tdpur4810s000)" is NOT activated. Interactive Session "Recalculate Purchase Price and Discount (tdpur4810s000)" is activated after CONFIRMATION. Automatic Session "Recalculate Purchase Price and Discount (tdpur4810s000)" is activated AUTOMATICALLY. 21. First Position Number for Additional Costs Sets This parameter contains the first position number, which will be used for additional costs sets. In the session "Maintain Purchase Order Lines (tdpur4102s000)" no position numbers can be entered, which are equal to or higher than this parameter. When you add item lines to a costs set in session "Maintain Items by Cost Set (tdpur4128m000)", you will not be able to enter position numbers which are lower than this parameter. 22. Automatic Recalculation of Additional Costs This parameter determines if additional costs are recalculated in case the order is modified. Changes, which might lead to recalculation of additional costs, can be made in the session "Maintain Purchase Orders (tdpur4101m000)" and "Maintain Purchase Order Lines (tdpur4102s000)". No The additional costs will not be recalculated. You'll be able to modify the additional costs using session "Maintain Purchase Order Lines (tdpur4102s000)". Interactive You'll be able to modify the additional costs using the session "Maintain Purchase Order Lines (tdpur4102s000)". Automatic You will not be able to modify the additional costs on an order. 23 . Financial Multi-Site Allowed This parameter determines if financial multi-site is allowed for purchase control. If financial multi-site if allowed, purchased goods can be stored in warehouses, which belong to other financial companies. If financial multi-site is not allowed, purchased goods can only be stored in warehouses which belong to the current (financial) company. 24. Automatic Generation of Transport Orders No The system does NOT generate transport orders. Interactive When an order has been maintained, the system maintains transport orders after confirmation by the user. Automatic When an order has been maintained, the system AUTOMATICALLY maintains transport orders. 25. New Transport Order when New By means of this parameter you can control the manner in which transportation orders are to be generated for purchase orders. Order For each purchase order a new transport order is generated in session Maintain Purchase Order Lines (tdpur4102s000). Order Line For each purchase order line a new transport order is generated in session Maintain Purchase Order Lines (tdpur4102s000). 26. Engineering Revisions Active in Purchase 27. Engineering Revisions on Purchase Documents 28. Method of Calculating Average Purchase Price Using this parameter you can determine how the average purchase price is to be calculated: Purchases (Cum.) The average purchase price is calculated on the basis of the price of a new receipt and the average price of the cumulative purchases up to the time of the new receipt: APN = [ (PR * QR) + (APO * CRO) ] / (QR + CRO) Current Inventory The average purchase price is calculated on the basis of the price of a new receipt and the average price of the current inventory. APN = [ (PR * QR) + (APO * ILO ) ] / (QR + ILO) In which: APN = average purchase price (new) APO = average purchase price (old) PR = price for the new receipt QR = quantity of the new receipt CRO = cumulative receipt quantity (old) ILO = inventory level (old) 29. Prio. of Supplier for Determining Fin. Comp. In a financial multi-site environment the financial company number for purchase inquiries and purchase orders is determined via a search structure. The levels searched are: • supplier • order series • user defaults Using three parameters you can specify the search structure for determining the financial company number. Each priority may only occur once. In order to change priorities, you must first assign priority 0 to all levels. Subsequently, you can link the desired new priority to each level. 30. Prio. of Order Series for Determining Fin. Comp. In a financial multi-site environment the financial company number for purchase inquiries and purchase orders is determined via a search structure. The levels searched are: • supplier • order series • user defaults Using three parameters you can specify the search structure for determining the financial company number. Each priority may only occur once. In order to change priorities, you must first assign priority 0 to all levels. Subsequently, you can link the desired new priority to each level. 31 . Priority of User Default for Determining Fin. Comp. In a financial multi-site environment the financial company number for purchase inquiries and purchase orders is determined via a search structure. The levels searched are: • supplier • order series • user defaults Using three parameters you can specify the search structure for determining the financial company number. Each priority may only occur once. In order to change priorities, you must first assign priority 0 to all levels. Subsequently, you can link the desired new priority to each level. 32. Delete Order Data if Received Completely By Order The order header data and the order lines are only removed when no back order quantities are registered anymore for any order line. By Order Line As soon as no item quantities are registered as back ordered anymore for the order line, the order line is removed from the system. After the last order line has been removed, the order header data is also deleted.