TROPOS™ Release Notes – New Features Included in TROPOS Release 2.4.0 June 2002 (Package Software Release 2.4.0) Version 3.0 SSI Hampshire International Business Park Crockford Lane, Chineham BASINGSTOKE RG24 8WH ENGLAND www.ssi-world.
Release Notes - New Features included in Release 2.4.0 COPYRIGHT NOTICE Copyright ã, 2002 by STRATEGIC SYSTEMS INTERNATIONAL LIMITED All rights reserved.
Release Notes - New Features included in Release 2.4.0 Contents 1. INTRODUCTION 6 2. E-TROPOS EXECUTIVE SUMMARY 7 3. PREREQUISITES FOR THE UPGRADE 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 4. LAYERED PRODUCTS TROPOS (UNIX) TROPOS (WINDOWS 2000) ORACLE DEVELOPMENT TOOLS CODA-FINANCIALS COGNOS UPGRADING TROPOS CLIENT AND NAVIGATOR NEW FEATURES 4.1 INTRODUCTION TO NEW FEATURES 4.2 BUSINESS FUNCTIONALITY 4.2.1 Cross-Module Enhancements (GENL) 4.2.1.1 4.2.1.2 4.2.1.3 4.2.1.4 4.2.1.5 4.2.1.6 4.2.1.7 4.2.1.8 4.
Release Notes - New Features included in Release 2.4.0 4.2.5.2 4.2.5.3 4.2.5.4 4.2.6 Demand Management (DEMD) 4.2.6.1 4.2.7 Exclude MPS from Schedule (SR3993) Scheduling Link (SLNK) 4.2.8.1 4.2.8.2 4.2.8.3 4.2.9 Forecast Definition and Consumption Improvements (SR3937) Scheduling (SCHD) 4.2.7.1 4.2.
Release Notes - New Features included in Release 2.4.0 4.3.4 TROPOS TIGI: Interfacing and Integration (TIGI) 4.3.4.1 4.3.4.2 4.3.4.3 4.3.4.4 4.3.5 Core Environment (AAAA) 4.3.5.1 4.3.5.2 4.3.5.3 4.3.5.4 4.3.5.5 4.3.5.6 4.3.5.7 4.3.5.8 4.3.5.9 4.3.5.10 4.3.5.11 4.3.5.12 4.3.5.13 4.3.5.14 4.3.5.15 4.3.5.16 4.3.5.17 4.3.5.18 4.3.
Release Notes - New Features included in Release 2.4.0 1. Introduction The purpose of this document is to provide TROPOS Users, System Manager and Administrators, Consultants and Support Staff with an overview of the new features included in this release. Five additional 'Release Note' Documents are also available at the release of 2.4.0 these are: • Technical Specification 2.4.0 • Product Support Matrix 2.4.0 • Third Party Product Specification 2.4.0 • Upgrading TROPOS to 2.4.
Release Notes - New Features included in Release 2.4.0 2. e-TROPOS Executive Summary In today's increasingly competitive business world, investment in product development must be seen to deliver real and tangible benefits quickly. It is against this background that our development of the TROPOS Product Portfolio has continued unabated with the next major TROPOS Release 2.4.0 shipping from May 2002.
Release Notes - New Features included in Release 2.4.0 beyond the current Quality Specification and Extra Data facilities. Its use reduces the need to hold multiple item numbers and process definitions for similar products where the only difference is in the dimensions and/or other characteristics of the item. It also provides active user defined fields, which can be used to influence the sales, manufacturing and procurement business processes.
Release Notes - New Features included in Release 2.4.0 subcontracted work, easing the planning task by automatically including subcontract activities, times and costs. Purchase and transfer orders are automatically raised reducing the amount of manual effort needed in managing the subcontracting process. Optimising Lorry Loads and Despatch Routes New facilities are provided for those businesses that manage their own lorry loading and despatch route planning.
Release Notes - New Features included in Release 2.4.
Release Notes - New Features included in Release 2.4.0 3. Prerequisites for the Upgrade 3.1 Layered Products It is the customer's responsibility to ensure they obtain the correct versions of the layered products required for the upgrade to TROPOS 2.4.0 where appropriate. 3.2 TROPOS (UNIX) TROPOS 2.4.0 runs on HP-UX 11.0, AIX 4.3.3 or Compaq Tru64 UNIX 5.1a. The operating system versions for HP-UX and Compaq Tru 64 have changed since the previous release of TROPOS.
Release Notes - New Features included in Release 2.4.0 4. New Features 4.1 Introduction to New Features This chapter identifies the significant new features that have been introduced into TROPOS at this release. All new TROPOS enhancements developed since the initial release of TROPOS 2.3.0 are included. Note: some enhancements may have already been shipped to you on a 2.3.0 platform. Full details of these features are given in the following sections. 4.2 Business Functionality 4.2.
Release Notes - New Features included in Release 2.4.0 Attribute applicability can be defined by key entity and sub reference to allow the attribute information collected to be focussed at the user's business requirements. Attributes can either be numeric (input or calculated), free text or limited to a user-defined list of values. Formulae can be defined which allow the calculated attributes to be automatically maintained e.g.
Release Notes - New Features included in Release 2.4.
Release Notes - New Features included in Release 2.4.0 consignment. The format of the new W81 form will have a separate page for each tax type being reported, with a total for each Tax Type and a Grand Total upon the last page. PKRD (Record Despatch) will now allow the transfer of goods between one business warehouse and another business warehouse.
Release Notes - New Features included in Release 2.4.0 4.2.1.7 User of printer SSISYS$NULL (SR4187) When the printer SSISYS$NULL was introduced it meant 'Do not produce or print this report'. With time, this definition has become inconsistently applied and it also means that a specific user may override printing requirements specified by the System manager via the DPMT transaction.
Release Notes - New Features included in Release 2.4.0 • The CPLQ (Call Plan Enquiry) transaction is used to view details about the Call Plans defined, and the Contacts associated with them. • The CLDQ (Calls Due Enquiry) transaction is used to list the calls that are due to be made, optionally filtered by Call Plan, Customer, Contact or Sales Representative.
Release Notes - New Features included in Release 2.4.0 CLUE (Call Look-Up Enquiry) now allows issue and reply text for each call returned to be displayed, and allows filtering by Call Sub Type and Date From. In addition, this enquiry now displays the description of the first action which has not been completed for each call that has a status of "In-progress". CLAD (Call Actions Due Enquiry) now displays the Call Sub Type and includes the option to redisplay call issue and action text.
Release Notes - New Features included in Release 2.4.0 4.2.2.4 Resultant Call Cross References (SR4073) A new call cross-reference type of 'CLR' has been introduced to allow a call which has been raised as a result of a previous call to be cross-referenced to that other call. This allows a distinction from those calls that are cross-referenced purely for informational purposes or where a call is dependent on another call. 4.2.2.
Release Notes - New Features included in Release 2.4.0 4.2.3.2 Sales Extras per Price Unit (SR4259) Sales order line extras which can be defined as being per “I”nvoice or per selling “U”nit, can now also be defined as per “P”rice unit on the SIEM (Order Line Extras) and the CPEM (Customer/Product Extras) transactions. 4.2.3.3 Payment Terms Text (SR4431) The SPTM (Payment Terms) transaction now contains an option to allow text to be defined.
Release Notes - New Features included in Release 2.4.0 The SOEN (Sales Order Entry) transaction now performs an accumulative credit check across all of the lines being entered. Credit checking now recognises invoices and credits which have not yet been extracted by LMES. This forms part of the In Progress value redisplayed by SOCC (Sales Order Credit Check). CAFD (Customer Full Details) shows the value of invoices and credits not yet extracted. 4.2.3.
Release Notes - New Features included in Release 2.4.0 the user. The number must not be within the automatically allocated run number range. A selection list should only have one run number. If this feature is used, users must manage the selection run numbers. TROPOS will not prevent users entering a previously allocated run. The reports or documents generated by a selection run may be incomplete if the wrong run number is used. 4.2.3.
Release Notes - New Features included in Release 2.4.0 A valid Document Type has to be entered. The Options allow the user to select processed or unprocessed requests or both. Processed requests are those with a printed date. 4.2.3.10 Additional Displayed Data on SOCD and SOMH (SR4247) SOCD (Consignment Detail) now displays Haulier details, Vehicle Numbers, Waybill Number and the document status. SOMH (Sales Order Line History) now displays details of SOCS (Sales Ord.
Release Notes - New Features included in Release 2.4.0 (Pack an Order Line) data but otherwise will use the weight plus tare weight defined on PDMT (Maintain Product Data). All weights are displayed in Kgs. Sales order lines selected for possible inclusion into the shipment are sorted by despatch due date, customer priority and delivery area so that the more urgent orders are displayed first and orders for a region are grouped together. NB.
Release Notes - New Features included in Release 2.4.0 Sales Order maintenance transactions SOEM (Sales Order Extras), SIEM (Sales Order Line Extras) and SCDC (Consignment Delivery Address) have been changed to allow users to change the delivery area on sales order delivery schedules and on shipments (SCDC). The delivery area is information associated with an address which is copied onto the sales orders from the delivery address data.
Release Notes - New Features included in Release 2.4.0 • CAFD – Customer Full Details 4.2.3.14 Scheduled Sales Delivery Transaction (SR4161) This enhancement introduces a new transaction SIEX (Maintain Sales Delivery) which allows users to add, change or delete individual scheduled sales order deliveries. This is a simplified version of the functionality of SOEX (Maintain Sales Schedule).
Release Notes - New Features included in Release 2.4.0 Consignment suffix 100 becomes ‘A0’. Consignment suffix 359 becomes ‘Z9’. This enhancement extends the system to use double alphabetic suffixes. Consignment suffix 360 becomes ‘AA’, 361, ‘AB’. Consignment suffix 998 becomes ‘YO’. 4.2.3.17 Selection List WPP Data (SR4048) The certificate of analysis or certificate of conformity flag on sales order lines has been added to the white paper printing (wpp) data file for sales selection lists.
Release Notes - New Features included in Release 2.4.0 • no lots are part-allocated. SOFI creates a sundry invoice using the customer and currency of the entered sales order. The invoice currency rate defaults according to the invoice date. SOFI carries out the following processing for each qualifying sales order line. An FSAL (Manual Alloc by Delivery) transaction is submitted, de-allocating the order line.
Release Notes - New Features included in Release 2.4.0 The default for the flags will replicate current functionality i.e. a warning for missing lines and no checks on credit or promise dates. 4.2.4 Fast Moving Consumer Goods (FMCG) 4.2.4.1 Various FMCG enhancements (SR4453) 1) Two new checkboxes have been added to the Order Search form. Both, either, or neither of the checkboxes may be selected.
Release Notes - New Features included in Release 2.4.0 The output file is always created in a format that the SPEX application can interpret unless the new initialisation flag CSVFORMAT is set to Y and Sales Invoices are extracted. In this case the output file is created with a suffix of CSV (rather than EXT for the SPEX format) and is written to the directory set up with the OUTPUT flag. Only the OUTPUT, CUSTPROCCDE, and UNITCOSTCODE initialisation flag settings are applicable to this flag.
Release Notes - New Features included in Release 2.4.0 between them. If no Structured Description is available then the TROPOS Item Description will be output. 4) The new initialisation flag SHIPPING has been included especially for the extract to GTA. This flag is set in the same way as CUSTPROCCDE. This flag informs the TROPOS Export Link which TROPOS Extra Data fields should be used to pass to the Shipping Marks 1 to 10.
Release Notes - New Features included in Release 2.4.0 4.2.6 Demand Management (DEMD) 4.2.6.1 Forecast Definition and Consumption Improvements (SR3937) TROPOS has been enhanced to allow greater flexibility in the definition and consumption of forecasts and their resulting impact on the production schedule.
Release Notes - New Features included in Release 2.4.0 outstanding TPS can be scheduled from the start of next week with no need to consider the resource requirements of the current week’s production orders. Production orders are excluded from a schedule by selecting new value ‘I’gnore for existing parameter ‘MPS Schedule Mode’. Existing values for this parameter are ‘A’ctual, ‘H’istoric and ‘P’lanned. A default value is defined via SHMG, Scheduling Management. The dataname is SCHSTIND.
Release Notes - New Features included in Release 2.4.0 4.2.8.2 S-Plan Interface Enhancements (SR4436) A number of changes have been made to enhance the S-Plan Interface functionality. In summary these are: • New option to filter data extracted by Controller. • New option to delay Production Order extract until order status ‘In Progress’. • Ability to define the min/max time gap allowed between S-Plan scheduled operation stages • New TROPOS enquiry to highlight changeover routines created by S-Plan.
Release Notes - New Features included in Release 2.4.0 Please note that if a reservation reference is associated with a production order, then extraction will occur at order addition, regardless of the value of the new ‘Order Status’ parameter.
Release Notes - New Features included in Release 2.4.0 4.2.9 Resources, Products and Processes (RPPM) 4.2.9.1 Automatic Item Number Generation (SR4429) A new option has been introduced to allow Item Numbers to be automatically generated. A new flag has been introduced on the FMAN (Formula Management) transaction to determine whether system generated item numbers are allowed.
Release Notes - New Features included in Release 2.4.0 4.2.9.4 Quality Assurance Enhancements (SR3770) New functionality has been introduced to the Quality Management transactions to support Inheritance, Quality Specification limits and Fault Recording.
Release Notes - New Features included in Release 2.4.0 • QSCM has been modified to allow separate sets of codes to be defined for specific items or product groups. • QSTM has been changed to allow input of the resource number associated with the test. • QSBC and QSBS have been modified to display and record new warning indicators against a V type test result which falls within the maximum/minimum but outside the new limits defined on QSCL.
Release Notes - New Features included in Release 2.4.0 • Subcontract Process Definition Within the Resources, Products and Processes module it is possible to define a process stage as a subcontract activity with a default subcontractor for that activity. Multiple alternative subcontractors for the activity can also be defined with an estimated cost and subcontract process time.
Release Notes - New Features included in Release 2.4.0 • Subcontract Process Stages A subcontract process stage will be one that utilises a subcontract resource number, i.e. with an external resource usage type. The subcontract resource defined upon the process stage will be the preferred subcontractor that will default when a production order for the finished product is raised.
Release Notes - New Features included in Release 2.4.0 • Subcontract Production Planning When a production order for a finished product with a process with subcontract process stages is raised, the order will be added with the preferred subcontractor as defined within the process. WSSC (Select a Subcontractor) can be used to display all alternative subcontractors for selection, or for confirmation of the preferred subcontractor.
Release Notes - New Features included in Release 2.4.0 Order Qty. In which case, the processing will calculate the amount of stock currently at or in-transit to the subcontract warehouse, less the current requirements, to determine if more stock is required to be sent to the subcontractor or not. The sales order line for any subcontract WIP material will have its production reserved from the production order stage prior to the subcontract process stage.
Release Notes - New Features included in Release 2.4.0 Non-Inv Goods). Any items which fail inspection should be rejected and returned to the subcontractor via GRQR (Reject Delivery Note) and QRTN (Return to Supplier). Once the material has passed inspection, WSSR (Subcontract Receipt) should be used to record completion from the subcontract stage.
Release Notes - New Features included in Release 2.4.0 4.2.10.2 Override Process Times (SR4357) At TROPOS Release 2.3.0 the processing for allowing a production rate to adjust the process lead time for an order was removed. The processing was removed to allow each process stage to be scheduled within the associated resource shift pattern rather than all stages being scheduled within the shift pattern of the process line.
Release Notes - New Features included in Release 2.4.0 4.2.11 Warehousing and Inventory (INCO) 4.2.11.1 Planned Stock Count option to exclude Locations (SR3767) A new option has been introduced on the SLAD (Location Details) transaction to identify that a particular store and location is to be included or excluded from a planned PI (Perpetual Inventory) stock check.
Release Notes - New Features included in Release 2.4.0 The INRD (Delete Reconciliation) transaction removes details of the selected reconciliation from the database. The WIMD (Inventory Management) transaction now allows the Earliest Movement Date to be maintained. Most TROPOS stock movement transactions allow the entry of a movement date and this date cannot be backdated beyond the Earliest Movement Date.
Release Notes - New Features included in Release 2.4.0 Hence the net postings are the same whether the cost of the lot is changed when the stock is classified as bin stock or consignment stock. Note: If lot costs are being changed to reflect the supplier invoice price (as opposed to the purchase order price), it is likely that postings to COSTCHG can be contra’d by the postings to INVPV (Invoice Price Variance) which are generated when the related purchase invoices are processed.
Release Notes - New Features included in Release 2.4.0 4.2.11.6 Update Actual Costs (SR4244) A new option to ‘Update Actual Costs’ has been introduced upon the PIRR (Record PI Adjustment) transaction. It allows for the situation where the assumed stock quantity has been delivered to stores from production and PIRR is being used to record the actual quantity delivered using tank dip readings, for example.
Release Notes - New Features included in Release 2.4.0 Add a Storage Location. Any location which has no storage location parameters will also be considered as being available, i.e. only locations which have location parameters where 'Include in MRP' has been set to N will be excluded. 4.2.11.11 Warehouse Rents (SR4241) The Warehouse Rents enhancement allows warehouse rents to be incurred against inventory.
Release Notes - New Features included in Release 2.4.0 This will allow the maintenance of all Customs and Excise details to be processed upon a single transaction which can be manually performed upon receipt of a lot. The receipt could be from own production, purchases or from a warehouse/business transfer. If from own production then the transaction will inspect all ingredients issued to the associated production order and default the age of youngest spirit.
Release Notes - New Features included in Release 2.4.0 used to select stock from individual locations. If the item is pallet controlled, then the partial quantity moved must be for a whole pallet quantity. • LTLI – Lot-to-Lot Issue This transaction will be used to combine stock from multiple lots/pallets into a single lot, and can be used to replicate the issuing and receipt of a single item without having to raise a reblend production order.
Release Notes - New Features included in Release 2.4.0 This enquiry transaction has been provided to allow available stock to be enquired upon within an entered A.Y.S. (Age of Youngest Spirit) range. The following existing transactions have also been amended to allow the bulk spirit process easier to manage. • ALCM – Maintain Alcohol Details This transaction has been amended to allow the number and type of container holding the alcohol within the lot to be defined.
Release Notes - New Features included in Release 2.4.0 4.2.13 Production Monitoring (PMON) 4.2.13.1 Rework Process Stages (SR4469) PMSM (Process Stage Maintenance) will allow the definition of a stage type and stage quantity when adding a new process stage. The stage type can be either a Production Process Stage, an Additional Process Stage, or a Rework Process Stage.
Release Notes - New Features included in Release 2.4.0 4.2.15 Purchase Invoice Clearance (PIME) 4.2.15.1 Update Lot Costs when Clearing Invoice (SR4042) Purchase Invoice Clearance now updates the cost of related lots so they reflect the invoiced price of the goods. Subject to the following conditions, the IVCL (Clear an Invoice or Credit Note) transaction now submits LOCC (Update Lot Costs) transactions to background in order to update the cost of the lots which are matched to the invoice line.
Release Notes - New Features included in Release 2.4.0 occurs, the IGCM should be rerun once the default VAT code has been defined for this supplier payment account. IGCM generates purchase invoices in respect of agent sales credits. Conversely purchase credits notes are generated in respect of agent debit notes. Invoices and credits are raised in the same currency as the related sales order. The currency rate defaults from the currency table as the rate effective on the date of the customer invoice.
Release Notes - New Features included in Release 2.4.0 4. Within the Oracle Financials environment, run the programs which process the fixed-filename csv files, inserting entries into the Oracle Financials OpenInterface tables. 5. Run the Oracle Financials Open Interface programs to create corresponding journals, purchase invoices and credits and sales invoices and credit notes.
Release Notes - New Features included in Release 2.4.0 Ensure the Transaction Type exists in OF Receivables and contains the account segments to be utilised by AutoAccounting. Use TOFP to specify the Transaction Types to be used by each TROPOS business. 4.2.17 Accounting Control (APME) 4.2.17.1 Inclusion of Delivery Address Number in SLED Extract (SR4334) The layout of the sales ledger extract has been enhanced to include the sequence number of the customer delivery address.
Release Notes - New Features included in Release 2.4.0 4.3.1.3 TROPOS Form dynamic database access (SR4142) TROPOS Form may now access an Oracle database via direct database accesses. Tables or views may be accessed. Manual Set-Up Procedures None is mandatory – see below for technical description: Single row, single column selects The dbacn= clause in the LOGIC section of a wppform.out file may now contain a standard SQL statement instead of a script name. The use of script names is still supported. e.g.
Release Notes - New Features included in Release 2.4.0 and a condition in a printing section (HEADER, DETAIL, FOOTER) determines whether the data is printed – the database access is done in any case, before the condition is checked.
Release Notes - New Features included in Release 2.4.0 Scenario: Given the following data file, containing ACCOUNT15 and SORDNO only, it is required to print out the order lines (in descending sequence) with the associated product. It then prints out all of the other orders on the database for the same product. Each group of [order line + product + other orders] appears in its own DETAIL section. Data file: HEADER ACCOUNT15 000010000100001 SORDNO SS000247 wppform.
Release Notes - New Features included in Release 2.4.0 >FOOTER Warning – note the looping-risks which would be involved in triggering database access on $sd (i.e. a new DETAIL section) and storing the data in a ‘nd$’ field, which will then trigger a new DETAIL ... etc. 4.3.1.4 TROPOS Form Error Handling (SR3476) It is now possible to specify whether syntax errors in TROPOS Form format files should result in system errors or simply display error details. The wppxxxx.
Release Notes - New Features included in Release 2.4.0 4.3.2 Shop Floor Data Capture (SFDC) 4.3.2.1 Shop Floor Data Capture Enhancements (SR4150) A range of enhancements have been made to the TROPOS SFDC programming language which significantly enhances the capabilities for the development of shop floor data capture systems to meet expanding customer requirements.
Release Notes - New Features included in Release 2.4.0 check=checkstring switch This does a format check on the input characters and sets w.$checkfail to 1 if it fails. Checkstring may contain: a leading number L – ignore and drop leading spaces T – ignore and drop trailing spaces N – field must consist of numeric characters only. If the leading number is supplied, then the field must consist of that number of numeric characters F – the field must consist of floating-point characters only (e.g. 3.4) e.g.
Release Notes - New Features included in Release 2.4.0 Note – this currently doesn’t work on “input” – you can’t “input w.field1[3:2]” l. It is now possible to declare and use arrays. These must be w. data types, e.g.: let w.sq=array let w.sub1=4 let w.sq[w.sub1]=w.sub1 * w.sub1 display w.sq[w.sub1] display w.sq[4] The “let w.field=array” clause creates an empty array (with a nominal 10 blank entries). The array will expand as required up to 9,999,999 entries (if memory allows!) – the statement let w.
Release Notes - New Features included in Release 2.4.0 p. The current process id is now available in w.$PID q. Verbs ‘open’, ‘write’ and ‘close’ are now available to write data to a sequential file. ‘open’ and ‘write’ take parameters in a similar way to ‘display’. ‘write’ defaults to appending a new-line character – unless the nonl switch is specified. ‘close’ doesn’t take any parameters. It is only possible to have one file open at a time. e.g. open “fil”w.$PID“.tmp” write “HEADER” write “PARTNO ”w.
Release Notes - New Features included in Release 2.4.0 4.3.3.2 PC Client Termination Messages (SR4338) The splash message displayed by the PC Client when the TROPOS manager brings it down will no longer time-out and disappear, if not acknowledged, to allow the PC Client to exit. Instead they will remain on view until acknowledged, allowing the user to be sure of seeing the message and therefore knowing why the PC Client is exiting.
Release Notes - New Features included in Release 2.4.0 • Add ABORTFLAG value of ‘S’ which (following a failure) will cause all records to be skipped up to the next record with the same layout code. • When a called transaction generated a System Error, this was reported, but details of the failed record were not shown, nor written to the reject file. This has been corrected. The error count is also now increased.
Release Notes - New Features included in Release 2.4.0 The ‘Forms queuing option’ (AF) of datei has been removed, as the forms field can now be defined by DPMT. Prior to this release, some transactions accessed BAPD information to define where documents were to be printed. This is no longer necessary and the relevant information will be transferred to the DPMT table by the 2.4.0 upgrade. Four new forms types have been added to the standard forms for the HPL4I printer.
Release Notes - New Features included in Release 2.4.0 and will insert one or more records into the background queue. Each time it runs, details will be written to the MAA100 table (BAMQ enquiry) indicating the run-time parameter, and any errors that may be detected by ith2remote. These errors will relate to the format of the parameter; the format or contents of the specific parameter or input file. In addition ith2remote will abort if it finds an error.
Release Notes - New Features included in Release 2.4.0 WARNING The records are inserted at the end of the background queue, so there may be some delay before these records are processed. If this is likely to be a problem, it may be avoided by using the existing Background Process configuration facilities (XSPA etc). The ability to specify the user name is also useful in controlling the scheduling of transactions. If no username is specified, the records will always be available to be run.
Release Notes - New Features included in Release 2.4.0 This transaction deals with the whole text entry; first extracting all the text; allowing change to the text; and then replacing or adding all text. The text is maintained in an editable 'scrolling' region. TECH performs no validation on the contents or format of the text, so any visible character may be used. At this release, this transaction is only available on the TROPOS Browser Interface and SDK applications.
Release Notes - New Features included in Release 2.4.0 This will continue to scroll and create the PROLOG date / time fields. PROLOG utility Options ‘D’ and ‘N’ will read the PROLOG.FILES file produced by logrename. This file now contains the time period for which PROLOG must extract log records to the PROLOG.OUT file. Option ‘S’ no longer exists. Log utility This will now process either the MAA170 table or a PROLOG.OUT file. The report LOG.LIS has been made the same as the report produced by logprt.
Release Notes - New Features included in Release 2.4.0 To allow these values to be entered, it is now necessary to respond to a Data-Valid prompt prior to executing the transaction. The key data names will be displayed alongside an input field. Values may then be entered in the corresponding input field to restrict the data shown.
Release Notes - New Features included in Release 2.4.0 DREQ - New Error Message Enquiry The searching criteria has been enhanced, so that all fields may be used. With the exception of the Module field, partial values may be entered into each field, which will display all entries ‘starting’ with the entered string. If the first character entered is a ‘%’, then all entries ‘containing’ the entered string will be returned. In addition, the ‘Error message’ field will perform a case insensitive search.
Release Notes - New Features included in Release 2.4.0 Client limit Changing this has no effect. Maximum clients The new maximum is used to restrict the number of concurrent clients connected to the instance. Any currently connected clients in excess of the new maximum number are allowed to remain until they are disconnected in the normal course of events. Online Server limit Changing this has no effect.
Release Notes - New Features included in Release 2.4.0 changes to the Background Server configuration, including the definition of those which are started by default. If the Background Servers are not up when a dynamic reconfiguration is requested, changing the definition of those which are started by default will have no immediate effect, but will take effect when the Background Servers are next brought up.
Release Notes - New Features included in Release 2.4.0 The first of these provides the means to force an instance to shut down after a specified period of time even if something, e.g. a child process that doesn’t exit, prevents the instance from shutting down normally within that time. This forced shut down can be achieved by using a new Operator Interface command parameter, -force, when shutting down an instance. This parameter can be used with either the down –system –shutdown or the shutdown command.
Release Notes - New Features included in Release 2.4.0 4.3.6 e-TROPOS Browser Products (BROWSER) 4.3.6.1 e-TROPOS Query Builder (SR4172) An e-TROPOS query is a customer-specific database query that can be incorporated easily into the existing e-TROPOS Browser Interface. It is designed to provide focused information to the user that is specific to his job function and implementation, and is used instead of standard enquiries.
Release Notes - New Features included in Release 2.4.0 5. Customisation and Screen Changes 5.1 New Features at 2.4.0 Some parts of the TROPOS system may be customised, for example TROPOS screens and scrolling displays. Many users will also write software and use utilities that interface to the TROPOS product, for example SDK’s and Batch Load Update’s. At previous releases, Customisation and Screen Change Information was supplied in a ‘report’ format with the Upgrade CD. At Release 2.4.
Release Notes - New Features included in Release 2.4.0 5.1.1.2 Customisation – Impact Analysis of Screen (‘cct’ File) Changes (SR4359) The program cctupdate has been enhanced to produce a summary report. The report details the impact of cct’s that are being delivered on a CD and it should be used when planning the tasks involved in implementing a Standard or Patch Release.
Release Notes - New Features included in Release 2.4.0 It will then run cctupdate for each cct file present in the new directory. The software required to enable this report is released with the standard TROPOS 2.4.0 release. It can also be patched onto TROPOS 2.3.0. If you have not received the software via a patch release and installed it on the relevant databases, then you will not be able to run this procedure prior to the 2.4.0 upgrade.
Release Notes - New Features included in Release 2.4.0 • Continue with the standard installation of the software. Apply the changes to the applications, etc, that are identified on the report as required. To compare the handover cct files with the live cct files and identify the effect on the handover database. The report can also be run to compare the handover to the live system. This can be useful as a ‘sanity’ check before the migration, but also if the CD was installed before running the report.
Release Notes - New Features included in Release 2.4.0 6. Table Changes 6.1 Introduction to Table Changes The following database tables have either been added or modified during the upgrade from Release 2.3.0 to Release 2.4.0. 6.
Release Notes - New Features included in Release 2.4.0 Table Name MBT040 MBT050 MBT100 Description Attribute Calculations Attribute UOM Conversions Attribute Values Module RPPM RPPM RPPM 6.
Release Notes - New Features included in Release 2.4.
Release Notes - New Features included in Release 2.4.0 Table Name Index Added Index Changed Column Added Column Deleted Details RESOURCENO_PSD, PRSTYPE_PSD MBJ010 MBK040 MBK120 MAP010 MBS000 MBK120_5 ELEMVALUE_PSD DESPBUFF INCWHCUSBUFF PRSTAGETYPE PRSTYP_PPS EXDATAIND_PPS VATCODE_PAC WORDSTAT_SPD * Note: PK – Primary Key.
Release Notes - New Features included in Release 2.4.0 7. Document Changes 7.1 Introduction to Document Changes The following documents have been White Paper Printing enabled at this release: • Allocations Report produced by the ALPR (Allocation / Selection Prints) transaction e.g. as a result of an FSAR (Allocation Request). (DPMT Type 024).
Release Notes - New Features included in Release 2.4.0 8. Documentation Status 8.1 Technical Manuals The following is a list of the technical manuals with their current printed status (either newly issued, updated or totally reprinted and when) as at this Release. TROPOS Core Module Technical Manuals - English Changes at 2.4.0 ? UsInstCharCellClient.pdf Using and Installing Character Cell Client (UNIX) N SetMaintPackFlags.pdf Setting and Maintaining Package Flags Y InstTROPOSUnix.
Release Notes - New Features included in Release 2.4.0 • Third Party Product Specification 2.4.0* • Upgrading TROPOS to 2.4.0 • Installation Procedures for Client Software. These will also be distributed on a CD in .pdf format with updates available through the customer area of the SSI Website. * Is available on request only.
