Utilities and Tools Fourth Shift Release 7worthen.xdatasync.com/support/PrintDoc/UtilitiesTools.pdf · Fourth Shift Release 7.50 Utilities Quick Reference Utilities and Tools 5 Utilities

Utilities and ToolsFourth Shift Release 7.50

Fourth Shift HelpRelease 7.50E

Important Notices

Copyright © 2014 Infor. All rights reserved.

The material contained in this publication (including any supplementary information) constitutes and contains confidential and proprietary information of Infor.

By gaining access to the attached, you acknowledge and agree that the material (including any modification, translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or interest in the material (including any modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solely in connection with and the furtherance of your license and use of software made available to your company from Infor pursuant to a separate agreement, the terms of which separate agreement shall govern your use of this material and all supplemental related materials ("Purpose").

In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such material in strict confidence and that your use of such material is limited to the Purpose described above. Although Infor has taken due care to ensure that the material included in this publication is accurate and complete, Infor cannot warrant that the information contained in this publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication (including any supplementary information), whether such errors or omissions result from negligence, accident or any other cause.

Without limitation, U.S. export control laws and other applicable export and import laws govern your use of this material and you will neither export or re-export, directly or indirectly, this material nor any related materials or supplemental information in violation of such laws, or use such materials for any purpose prohibited by such laws.

Trademark Acknowledgements

The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other company, product, trade or service names referenced may be registered trademarks or trademarks of their respective owners.

Fourth Shift Release 7.50

Utilities and Tools 3

ContentsUtilities and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Standard Location References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Utilities Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Enable DOS Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Full Path to Utility Not Specified. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Full Path to Utility Specified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Fourth Shift Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7AAC2STD—Average Actual to Standard Costing Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Pre-conversion Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Conversion Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Post-conversion Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

ARCREORG—Archive Reorganization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10CFG2DOS/CFG2CMD—Configuration Variable Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11CHOOSE2—Selection Window Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

CHOOSE2: Window Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13CHOOSE2: Processing Control Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14CHOOSE2: Selection Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15CHOOSE2: Available Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15CHOOSE2: Sample Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

FS_TABLE—Verification Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18FS_TABLE: Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18FS_TABLE: Value File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19FS_TABLE: Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

FSLICENS—Fourth Shift Workstation License Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21FSLICENS: Review Total Workstation Licenses Installed . . . . . . . . . . . . . . . . . . . . . . . . . . 21FSLICENS: SQL Server Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

FSVBUFF.exe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22FSSCREEN.exe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22KBD—Keyboard Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Special Key Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

MAKEPATH—Fourth Shift Security Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25PARAM—Parameter Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26PIPEDOS—Pipe to DOS from Microsoft Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

General Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Other Sample Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

SETCFG—Set Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Setting the Configuration Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

STD2AAC—Standard to Average Actual Costing Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Conversion Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Pre-conversion Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Post-conversion Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Fourth Shift Release 7.50

Utilities and ToolsThe Utilities and Tools manual provides instructions on how to use the utilities included with the system. These utilities are used outside of Fourth Shift for database and transaction history maintenance. See the System Administration manual for suggestions on when to use these utilities.

This manual assumes you have all modules installed. Some utilities may not be available based on the modules you have installed.

Standard Location ReferencesInstructions and examples provided for the system utilities refer to locations and filenames based on the standard system configuration. The configuration variables and the standard locations used in this manual include these examples:

Use the configuration variables listed to identify the correct location and filenames in the configuration file if your system does not use the standard configuration. See "Configuration Variables" in the System Administration manual for more information.

Standard Location Configuration Variable Example Files in Location

root directory FSScripts FSLICENS.EXE

MFGSYS AuxDataFiles ARCHIVE.FIL;BATCHUPD.FIL


Fourth Shift Release 7.50 Utilities Quick Reference

Utilities Quick ReferenceSeveral types of utilities are available.

• External utilities used outside the system, such as the ARCREORG utility, allow you to perform administrative activities outside the system. These utilities are designed to operate in any system configuration. These utilities are not designed to work while you are signed onto the system.

• Command line task utilities, such as SETCFG, allow you to use command line tasks to perform functions in a batch process. In most cases, these utilities are not useful when you are not signed onto the system.

See also the database-specific utilities information in the "SQL Server Database Utilities" topic of the SQL Server Administration and Utilities manual.

Enable DOS Configuration VariableAt Fourth Shift Release 7.50C, several utilities will have two versions: one is the original DOS-based and the other is a new Windows-based version. In most cases, these utilities have the same file name but are located in different directories. The use of these utilities will be governed by two factors:

• The difference between a 32-bit or 64-bit machine.

• The configuration variable: EnableDOS. This configuration variable has two values; Yes and No.

Basically, the value of EnableDOS indicates which version of the utility should be used when the user does not specify the full path to the utility. This variable is particularly critical for use on a 32-bit machine to execute the utility tasks.

Full Path to Utility Not SpecifiedIf the full path to a utility isn't specified:

• On a 32-bit machine:

- If EnableDOS = Yes, the DOS-based version will be used.

- If EnableDOS = No, the Windows-based version will be used.

- If EnableDOS = No, and if there is no equivalent Windows-based version of the utility, the DOS-based version with a full path defined can be used (see below).

• On a 64-bit machine (which does not support DOS):

The configuration variable will be ignored because the Windows-based version of the utility is the only one that can be used.

Full Path to Utility SpecifiedIf the full path to a utility is specified, the following conditions apply:

• On a 32-bit machine with a full path defined for a DOS-based version:

- If EnableDOS = Yes or No, the DOS-based version will be used.

• On a 32-bit machine with a full path defined for a Windows-based version:

- If EnableDOS = Yes or No, the Windows-based version will be used.


Fourth Shift Release 7.50 Utilities Quick Reference

• On a 64-bit machine with a full path defined for a DOS-based version:

- The system will create an error and not permit the process to continue.


Fourth Shift Release 7.50 Fourth Shift Utilities

Fourth Shift UtilitiesThis section contains information on supplemental utilities.

AAC2STD—Average Actual to Standard Costing ConversionExtreme care as to timing and procedure should be taken when changing from an average actual costing system to a standard costing system. Costing changes can significantly impact inventory valuation, business margins and profitability.

The AAC2STD conversion process includes the following phases:

• updates the system costing method on the CCFG (Costing Configuration) screen to be Cost Method = S (standard)

• deletes average actual costing features, including the CCAN (Cost Control Action) screen and CSTU (Actual Cost Update) task

• deletes any existing cost action messages CSQ, CST, CSY and CSZ that appeared on the CCAN screen

The CSTUM and CSTUP batch source codes are not deleted from the GLSC (G/L Source Code Maintenance) screen since G/L batches with these batch source codes remain in the system.

Costs are not recalculated during the conversion process. The existing inventory value (Cost Type 0) from the average actual costing system is the beginning cost point for standard costing calculations. The existing inventory value is revalued when the CROV (Cost Roll-Over) and CROL (Cost Roll-Up) tasks are run after converting to a standard costing system. Running the CROV and CROL tasks update ITMC item cost records and G/L inventory accounts balances. WIP values are not recalculated during the conversion process.

Parameters are not required when the AAC2STD utility is used.

Pre-conversion TasksProcess Existing Orders1. Use the MOMT or POMT screens to close all open orders that are complete.

2. Run the CSTU task in update mode to update all orders to a cost status 8 or 9.

3. Run the OVAR task to change the order status to 6.

4. Print an Inventory Valuation Report using the INVR task, if the Management Reports Module is installed.

This Inventory Valuation Report represents on-hand inventory values with average actual costs.

Create System Backup1. Perform a system backup of your system.

2. Label this backup: Pre-Standard Costing System Backup.

Conversion TasksRun Conversion Program1. Stop your database server.

The AAC2STD utility must be run in single-user mode.



2. From a DOS command prompt, go to the MFGSYS\SYSTEM directory on the drive where your system is installed.

3. Type: AAC2STD -C[file] substituting the name and path to your Fourth Shift configuration file for [file].

4. Press Enter.

The AAC2STD utility processes. The message "Process Completed Successfully" is displayed at the prompt when the AAC2STD utility has successfully completed.

Review Conversion ResultsReview the INSTALL.HIS file to verify that no errors were encountered during the conversion processing.

- The INSTALL.HIS file is created in the MFGSYS directory by default.

Verify Conversion Results1. Sign onto your system.

2. Verify that the configuration information at the top of the CCFG screen indicates Standard Costing.

3. Verify that the CCAN and CSTU tasks are not listed on the PRCM module menu.

Post-conversion TasksCreate System Backup1. Perform a system backup of your new Standard Costing system.

2. Label this backup: Standard Costing System Initial Backup.

Review Cost Type Information1. Sign onto your system.

2. Go to the CNFC (Cost Type Setup) screen.

3. Review the cost description for Cost Type 0.

4. Change the cost description for Cost Type 0.

For example, use STD COST to reflect your standard costing system.

5. Print an Inventory Valuation Report using the INVR task, i the Management Reports Module is installed.

This Inventory Valuation Report represents on-hand inventory values after the conversion.

6. Review the two Inventory Valuation reports (prior to and after AAC2STD conversion process).

The inventory values should match in both reports.

Evaluation of Item Cost RecordsEstablish an evaluation cost type, if desired. Use the evaluation cost type to perform a cost roll in order to evaluate how converting from an average actual to a standard costing system will change the inventory value and inventory accounts balances.


2. Enter an evaluation cost type and cost description.

For example, enter Cost Type 9 with an "evaluation" description.

3. Use the CROV task to copy the inventory cost (Cost Type 0) to the evaluation cost type (for example, Cost Type 9).



4. Use the CROL (Cost Roll-Up) task to roll the costs for the evaluation cost type.

5. Use the COMP (Cost Comparison Report) task to compare the evaluation costs (Cost Type 9) to the inventory costs (Cost Type 0).

6. Compare the previously printed Inventory Valuation Report to the Cost Comparison Report to review the financial impact of a cost roll for a standard costing system.

Update Item Cost Records (Optional)After assessing the financial impact of a cost roll when converting from an average actual costing system to a standard costing system, your company's Chief Financial Officer or financial controller must decide when to update the item cost records. Updating the item cost records can be done at anytime after converting to a standard costing system. After deciding to update item cost records, use the following instructions:

1. Use the CROV task to copy the inventory cost (Cost Type 0) to another cost type (for example, Cost Type 9).

2. Use the CROL (Cost Roll-Up) task to roll the costs for the copy cost type (Cost Type 9).

3. Use the COMP (Cost Comparison Report) task to compare the new costs (Cost Type 9) to the inventory costs (Cost Type 0).

4. Use the CROV task to exchange the new cost (Cost Type 9) and the inventory value (Cost Type 0) when verification is complete.

Cost changes for those items with inventory automatically create financial transactions to update the general ledger.

5. Run the GLMQ (G/L Module Communication) and GLAU (G/L Account Update) tasks to update the G/L account balances.

6. Print the Inventory Valuation Report using the INVR task, if the Management Reports Module is installed.

This Inventory Valuation Report represents on-hand inventory after changing costs.

7. Use the two Inventory Valuation reports (prior to and after cost changes) to assess the impact of the cost changes.

The inventory valuation totals should reconcile to the G/L Inventory Accounts balance.

Review Costing Configuration1. Go to the CCFG (Costing Configuration) screen.

2. Review the costing options selected and update if necessary.

See “Setting Up the Module” in the Product Costing online manual for more information on using your standard costing system.



ARCREORG—Archive ReorganizationSome Fourth Shift transactions produce multiple, interdependent archive records for one transaction. The G/L Distribution screen used after entering cash receipts on the ARCD (A/R Cash Deposits) screen is one example. In a multi-user configuration, the transactions are not necessarily recorded contiguously in the ARCHIVE.FIL file.

The ARCREORG utility is used to reorganize the ARCHIVE.FIL file so that interdependent archive records are contiguous. The ARCHIVE.FIL file can then be used for recovery purposes. The ARCHIVE.FIL file, prior to reorganization, is saved as ARCHIVE.SAV as part of the ARCREORG process.

Interdependent archive records include a flag identifying where the transaction belongs in a sequence. The ARCREORG utility uses this flag to reorganize the ARCHIVE.FIL file. The flags are:

For instructions on using ARCREORG during a system recovery process, contact Customer Support Services for further information and an additional utility (ARCBEXE). ARCBEXE uses the reorganized archive file to create a series of files that are then processed by the RCVR batch task.

Flag Description

F first

M middle

L last

B both first and last



CFG2DOS/CFG2CMD—Configuration Variable ConversionThis utility enables you to use configuration variables in commands and allows connectivity applications to use the current configuration file values. For example, use the AuxDataFiles configuration variable rather than a specific drive/directory location for a report generated by a task.

Note: There are two versions to this utility: the DOS-based version (CFG2DOS) is only for use on a 32-bit machine. It is located in the root of your mapped Fourth Shift drive (for example: M:\) and the Windows-based version (CFG2CMD) is located in the M:\mfgsys\system directory.

See the Enable DOS Configuration Variable section in this manual for additional information on DOS- and Windows-based utilities.

Before you use the utility from a Command prompt or within a batch file, you must explicitly set an environment variable that identifies the name and location of the Fourth Shift configuration (FS.CFG) file. The utility uses this FSCFG environment variable to locate the configuration file that contains the variable you want to use.

C:\SET FSCFG=M:\MFGSYS\FS.CFG

If running the utility from a batch task, the machines' environmental variable needs to have the appropriate drive value for FSCFG defined first.

Several parameters are available to assist you in using this utility. The parameters available include:

This utility uses the last location in the list when multiple locations are associated with a configuration variable.

The following table lists several examples of how you can use the utility to complete commands using configuration variable values.

These instructions assume your system is installed on drive M: using the standard system configuration. Substitute different drive/directory identifiers, if necessary.

To use the CFG2CMD utility from a command prompt window:

Parameter Description

$variable$ Configuration variable keyword; this variable must be listed in the configuration file specified by the FSCFG environment variable

/D Debug mode; this mode completes the conversion of the configuration variable but does not complete the command execution

Desired Result Type:

Delete all *.LOG files after a system backup

CFG2DOS DEL $AuxLogFiles$\*.LOG

Rename your MODCOMSL file at the end of the month

CFG2CMD REN $ArchiveFile$\MODCOMSL.FIL MODCOMSL.JAN



1. From the M:\mfgsys\system directory, type:CFG2CMD command $variable$\filenameThen press Enter.

2. Substitute the path and name of your configuration file if necessary.

3. Any valid command can be used for command and any configuration variable defined in the configuration file can be specified for $variable$.

To use the CFG2DOS utility from a command prompt window:

1. From the root directory of the mapped drive, type:CFG2DOS command $variable$\filenameThen press Enter.

2. Substitute the path and name of your configuration file if necessary.

3. Any valid command can be used for command and any configuration variable defined in the configuration file can be specified for $variable$.

Either utility can be used as a BSET task to perform the same activities.

Note: If CFG2DOS is used in a BSET task, the full path must be defined.



CHOOSE2—Selection Window ConfigurationThe CHOOSE2 utility enables you to create and use a set of instructions and data files with a connectivity application. You can create user-defined windows with data from an external data file and include additional menus based on the selection from the first window. For example, you can create a menu from a data file that lists a series of transportation methods. Once a transportation method is selected, a second window opens listing the types of options that a carrier provides such as priority or second day.

Note: This utility is available only when the CSTM Module is installed.

The CHOOSE2 utility is normally accessed using the PROG (Fourth Shift Program Execution) task within the system. See the CIM Customizer manual for additional information on defining CIM Customizer applications.

Note: There are two versions to this utility: a DOS-based version for use only on a 32-bit machine located in the M:\mfgsys\e directory (where M: represents the mapped drive), and the Windows-based version is located in the M:\mfgsys\system directory.

See the Enable DOS Configuration Variable section in this document for additional information on DOS- and Windows-based utilities.

The following table lists several examples of how you can use the CHOOSE2 utility.

Several types of values are used in the data file for the CHOOSE2 utility, which enables you to specify what size your window should be, what information should be displayed and what action is needed once a selection is made.

CHOOSE2: Window DefinitionThe directives available for defining the attributes of the window include:

Desired Result Type:

Use instructions provided in the SERVICE.LST file. CHOOSE2 SERVICE.LST

Use the SERVICE.LST file and display any debug messages as needed. CHOOSE2 SERVICE.LST /d

Directives Description

; Comment line symbol

.Title=text Displays as the title at the top of the window; text is centered automatically

.TopRow=number Identifies the row location where you want the window to display on the screen; for example, use .TopRow=1 to create the window on the first row of the screen

.LeftCol=number Identifies the column location where you want the window to display on the screen; for example, use .LeftCol=1 to create a window in the first column of the screen

.MaxRows=number Identifies the maximum number of lines which display in the window; the maxi-mum number of lines available is 25

.Label=text Displays in black on the second row of the window; this text can be used to label the columns in your window

.End Identifies the end of the data file; any lines listed after this directive are ignored



CHOOSE2: Processing Control DirectivesSeveral types of directives are used to define the actions needed to display the windows, complete processing once a selection is entered and identify supplemental files.

Note: Processing control directives are case-sensitive.

The directives available include:

The {macroname}, {popupname} and {filename} values must be identified based on the type of value specified because similar syntax is used to specify the name of each type.

The following directives are used to group each type of value.

Value Description Example

{macroname}=values Macros can identify keystrokes, literal data values and other macros

{m1}={home}BILL{f1}

{popupname}=input,output,label,default

Data entry windows are defined based on the size of the data entry field displayed, the number of characters returned, the label dis-played above the entry field and the default value displayed in the field when the data entry window opens; spaces are not permit-ted between values

{p1}=3,3,User Id,AAA

{filename}=location+filename

Supplemental data files, identified by location and filename, needed for additional selection windows

{file1}=c:\fsuser\item.lst

Start Directive End Directive Description

.Macros .EndMacros Macros identifying keystrokes or literal data entries are listed between these directives

.Pop_Ups .EndPop_Ups Data entry windows which allow user input are defined between these directives

.Files .EndFiles Supplemental files needed are listed between these directives



CHOOSE2: Selection ItemsThe lines which display on the selection window are listed in the data file without any directives. Any lines entered without a comment symbol are included in the scrolling area of the window.

The information displayed and returned to the calling application are based on the following symbols:

Note: Macro, pop-up and filename values can be incorporated into the return text value. When the item is selected from the window, the related operations are executed. For example, if you select an option which includes a pop-up operation, the pop-up window is displayed when you select the item on the window.

The example would look similar to the following:

Overnight#Overnight -- {p1}

CHOOSE2: Available KeysKeys specified as part of a macro can include literal keyboard characters such as a Function Code or special keys such as Tab. Special keys are entered in braces. For example, to specify Tab, enter {TAB}.

Symbol Description Example

menu text=return text

Both the menu and return text are displayed on the selection window; the "=" symbol is displayed as a space on the window.

• If no return text is listed, the menu text item is displayed on the window but cannot be selected and returned to the calling application

Crate=CR

menu text#return text

Only the return text is displayed on the selection win-dow.

• If no return text is listed, the menu text item is displayed on the window but cannot be selected and returned to the calling application

Crate#CR

Keys Key Value

ALT+BACKSPACE {@BS}

ALT+ENTER {@CR}

ALT+Function key {@F1}, {@F2}, {@F3}, etc

ALT+TAB {@Tab}

BACKSPACE {BS}

BACKTAB {Btab} or {*Tab}

CTRL+BREAK {^Break}

CTRL+DELETE {^Del}



CTRL+DOWN {^Dn}

CTRL+END {Ênd}

CTRL+ENTER {^CR}

CTRL+Function key {^F1}, {^F2}, {^F3}, etc

CTRL+HOME {^Home}

CTRL+INSERT {Îns}

CTRL+LEFT {^Lt}

CTRL+PAGE DOWN {^PgDn}

CTRL+PAGE UP {^PgUp}

CTRL+PRINTSCREEN {^PrtSc}

CTRL+RIGHT {^Rt}

CTRL+UP {Ûp}

CURSOR LEFT {Lt}

CURSOR RIGHT {Rt}

DELETE {Del}

END {End}

ESC {Esc} or {Escape}

ENTER {CR}

Function keys {F1}, {F2}, {F3}, etc

HOME {Home}

INSERT {Ins}

PAGE DOWN {PgDn}

PAGE UP {PgUp}

SCROLL DOWN {Dn}

SCROLL UP {Up}

SHIFT-Function key {*F1}, {*F2}, {*F3}, etc

SPACEBAR {Sp} or {Space}

TAB {Tab}

Keys Key Value



CHOOSE2: Sample ApplicationThe following data file is used to identify a CHOOSE2 application which displays a list of transportation methods. Values are returned based on the item selected. In this example, most items return descriptive text once the item is selected. One selection opens another data entry window to request additional information.

The data file used looks similar to the following:

; SERVICE.LST; CHOOSE2 data file for selecting transortation service;.Title=DELIVERY OPTIONS.TopRow=10.LeftCol=25.MaxRows=8.Label=SERVICE TRLT;.pop_ups {p1}=2,2,Enter AM or PM,PM.endpop_ups;.files {file1}=c:\fsuser\jtruck.ls.endfiles;OVERNIGHT/NEXT DAY 1#OVERNIGHT -- {p1}STANDARD MAIL 2#STD MAIL SVCUPS GROUND 2#UPS-GROUNDJOHN'S TRUCKING 2#J. TRUCKING {file1}

.end

The window defined in the data file looks similar to the following:

If the first item is selected, an additional data entry window opens automatically. The window looks similar to the following:

*OVERNIGHT/NEXT DAYEnter AM or PMPM

SERVICE TRLT

OVERNIGHT/NEXT DAY 1

STANDARD MAIL 2

UPS GROUND 2

JOHN'S TRUCKING 2



FS_TABLE—Verification TableThe FS_TABLE utility enables you to return the contents of a CDF file to a screen in the system. Specific data can be returned based on predefined key sequences. For example, create a list of all company-specific valid units of measure. Verify that the user entry is a valid unit of measure and return an error message and key sequence to accept the information.


The FS_TABLE utility is normally accessed using the PROG (Fourth Shift Program Execution) task within the system. See the CIM Customizer User Guide for additional information on defining CIM Customizer applications.



FS_TABLE: ParametersThe available parameters for the FS_TABLE utility include:

Note: The parameters must be entered in the order listed above. If a specific value is not needed, use a null value. Parameters must be separated by commas.

For example, to use the FS_TABLE utility to search for the string "EA" as the second field in the file STD_UM.TXT, your entries would look similar to the following:

01 PROG FS_TABLE EA, 2, $AuxDataFiles$\STD_UM.TXT


string Identifies the value which you wish to search for in the data file. This value is case-sensitive. The string value is usually identified as a parameter in a CIM Customizer appli-cation. Required.

field Identifies the location of the value in a string of data values in the file; default = 1

valuefile Identifies the data file used for performing the search for the string value. Required.

controlfile Identifies a supplemental file used for messages or key information; default = valuefile

prefix Identifies an alternate processing method for a data file. For example, two directives could be specified, such as: 1.YesMsg and 2.YesMsg. The directive used is based on the prefix entered

/d Display debug information during processing

; Identifies a comment line in a data file



FS_TABLE: Value FileThe valuefile is an ASCII data file which can contain lists of values, directives and comments. The values entered can be used as the comparison values for the string parameter entered. The following directives are available.

A sample of a valuefile used to identify valid units of measure could look similar to the following:

; Unit of Measure verification table;; Format of file: Description, CodeBox, BXBottle, BTBundle, BNCarton, CACase, CSCrate, CREach, EALiters, LTMeters, MtPackage. MK;; Keys and messages based on whether UM is valid.YesKeys={cr}.NoKeys={esc}.NoMsg="INVALID UM ENTERED".NoBeep=yes

File Directives Description Examples

.YesKeys=keys keystrokes returned if the string parameter is located; default = none

.YesKeys={cr}

.YesMsg=text text message displayed if the string parameter is located; default = none

.YesMsg="VALID UM ENTERED"

.YesBeep=yes/no generate a message "beep" sound if the string param-eter is located; default = no

.YesBeep=yes

.NoKeys=keys keystrokes returned if the string parameter is not located; default = none

.NoKeys={esc}

.NoMsg=text text message displayed if the string parameter is not located; default = none

.NoMsg="INVALID UM ENTERED"

.NoBeep=yes/no generate a message "beep" sound if the string param-eter is not located; default = no

.NoBeep=yes



FS_TABLE: KeysThe keys specified in the valuefile can include literal keyboard characters such as a Function Code or special keys such as Tab. Special keys are entered in braces. For example, to specify Tab, enter {TAB}.

The following table lists the special key values available for use with the FS_TABLE utility:

Keys Key Value


BACKSPACE {BS} or {@BS}

BACKTAB {BTab}

CTRL+BREAK {^Break}

CTRL+END {Ênd}

CTRL+ENTER {^CR}


CTRL+HOME {^Home}



CURSOR LEFT {Lt}

CURSOR RIGHT {Rt}

DELETE {Del}

END {End}


ENTER {CR} or {@CR}


HOME {Home}

INSERT {Ins}

PAGE DOWN {PgDn}

PAGE UP {PgUp}

SCROLL DOWN {Dn}

SCROLL UP {Up}

SHIFT+Function key {*F1}, {*F2}, {*F3}, etc


TAB {Tab}



FSLICENS—Fourth Shift Workstation License InstallationAn initial set of workstations are installed with your system to allow several users to access the system concurrently. You can purchase additional workstation licenses to increase the number of users able to access the system.

These instructions assume your system is installed on drive M: using the standard system configuration. Substitute drive identifiers if necessary.

FSLICENS: Review Total Workstation Licenses InstalledUse the following instructions to view the number of workstation licenses currently installed for your database.

1. Go to the root directory on the drive where your system is installed. In a standard configuration, this is the M: directory.

2. Type: FSLICENS -R -C M:\mfgsys\fs.cfgThen press Enter.

The following message is displayed:

FSLICENS: WORKSTATION LICENSE COUNT IS xx.CONFIGURATION VARIABLE MAXUSERS IS xx.

FSLICENS: SQL Server Systems1. Copy the key file (obtained from Fourth Shift Support Services) to the root of the mapped

drive.

2. From a command line prompt, go to the mapped drive.

3. Type: M:\FSLICENS then press Enter.

The system prompt returns to the screen when the process is complete. The following message is displayed.:

FSLICENS: WORKSTATION LICENSE COUNT CHANGED FROM xx TO yy.CONFIGURATION VARIABLE MAXUSERS CHANGED FROM xx TO yy.MODULE ACCESS KEY SUCCESSFULLY INSTALLED

The number of users able to access the system is now updated in the database.

4. Go to the Control Panel group, then select the Services icon.

5. Select each of the following services and click Stop:

- Fourth Shift Lockserver

- MSSqlServer

- FIN XX

- MAIN XX

6. Select each of the services listed in step 5 and click Start to restart them individually.



FSVBUFF.exeThis utility is used with CIM Customizer routines to provide a way to capture the contents of the current screen to a file. It can be run as a step in a batch process to write the current screen's contents to a file. This file can then be read later to know what Fourth Shift was displaying when the user started the batch process.

FSVBUFF is a DOS program that writes the contents of the DOS video buffer to the file. It writes two bytes for each character - the actual character and its DOS attribute byte.

Arguments are:

• /dDirectoryName, the directory to create the file in. Default is the mfgsys directory.

• /fFileName, the name for the file. Default is FSSCREEN.BIN.

Note: See the Enable DOS Configuration Variable section in this document for additional information on DOS- and Windows-based utilities.

FSSCREEN.exeThis utility is used with CIM Customizer routines to provide a way to capture the contents of the current screen to a file. It can be run as a step in a batch process to write the current screen's contents to a file. This file can then be read later to know what Fourth Shift was displaying when the user started the batch process.

FSSCREEN.exe is a Windows program that writes the screen contents as an XML file. There is an XML element for each field on the screen, with information about its current state.

Arguments are:

• /dDirectoryName, the directory to create the file in. Default is the UserDir fs.cfg variable.

• /fFileName, the name for the file. Default is FSSCREEN.XML.

Note: See the Enable DOS Configuration Variable section in this document for additional information on DOS- and Windows-based utilities.



KBD—Keyboard EntryThe KBD utility enables you to define sequences of keystrokes and allows conditional processing based on whether a specific file exists. For example, use the KBD utility to transport to another screen and display information for a specific item before beginning the next step in a connectivity application.




Several parameters are available to assist you in specifying information. The available parameters for the KBD utility include:

Parameters

Special Key ValuesThe keys specified can include literal keyboard characters such as a Function Code or special keys such as Tab. Special keys are entered in braces. For example, to specify Tab, enter {TAB}.

Note: If you are running the KBD utility from a Windows NT or 2000 workstation, substitute the single caret (^) with a double caret (^^) in the following key values. This is required to accommodate operating system rules in Windows NT and 2000.

The following table list the special key values available for use with the KBD utility.


keys Keys to execute before any keys specified by the /E or /N parameters

/Ekeys If the filename specified exists, execute the keys specified

/Nkeys If the filename specified does not exist, execute the keys specified

/keys Keys to execute after completing the /E and /N keys

@@filename Filename checked before executing the /E and /N parameters

@@@@filename Filename checked before executing keys and contains the keys which should be executed; overrides the /E parameter

/D Debug mode; displays troubleshooting information for identifying problems

Keys Key Value

ALT+BACKSPACE {@BS}

ALT+ENTER {@CR}


ALT+TAB {@Tab}

BACKSPACE {BS}




BACKTAB {Btab} or {*Tab}

CTRL+BREAK {^Break}

CTRL+DELETE {^Del}

CTRL+DOWN {^Dn}

CTRL+END {Ênd}

CTRL+ENTER {^CR}


CTRL+HOME {^Home}

CTRL+INSERT {Îns}

CTRL+LEFT {^Lt}



CTRL+PRINTSCREEN {^PrtSc}

CTRL+RIGHT {^Rt}

CTRL+UP {Ûp}

CURSOR LEFT {Lt}

CURSOR RIGHT {Rt}

DELETE {Del}

END {End}


ENTER {CR}


HOME {Home}

INSERT {Ins}

PAGE DOWN {PgDn}

PAGE UP {PgUp}

SCROLL DOWN {Dn}

SCROLL UP {Up}

SHIFT-Function key {*F1}, {*F2}, {*F3}, etc


TAB {Tab}

Keys Key Value


ExamplesThe following table lists several examples of how you can use the parameters to identify information and execute keystrokes. These examples would be entered as parameters for the PROG (Fourth Shift Program Execution) task.

See the CIM Customizer manual for more information on defining CIM Customizer applications.

MAKEPATH—Fourth Shift Security UpdateUse the Makepath utility to update your PATH.FIL file to reflect your current security. This utility is used automatically during module installation and when recommended by Fourth Shift Customer Support to update your PATH.FIL file to correct errors.


1. Type: CD \MFGSYS\E then press Enter.

2. Type: MAKEPATH then press Enter.

After the MAKEPATH utility has finished, you are returned to the system prompt.

Desired Action Type

From the current screen, transport to the BILL screen KBD {HOME}BILL{ESC}

Transport to the BILL screen and display Item = 19-FRAME KBD {HOME}BILL{ESC}19-FRAME{Cr}

Verify if the BATCHUPD.FIL file exists; if the file exists, exe-cute Process Id = UPD

KBD @@$AuxDataFiles$\BATCH-UPD.FIL /EBEXE{Esc} /UPD{Cr}

Continue a batch process by going to the next Process Id = DY2 once a previous batch process is completed

KBD {f1}DY2{Cr}Note: This must be the

last line in the batch process.



PARAM—Parameter DisplayThe CIM Customizer (CSTM) Module provides the ability to "cut" information from a Fourth Shift screen and pass the information to an external application.

The PARAM utility analyzes data being captured by the "cut" defined on the CACF (CIM Customizer Configuration) screen. The PARAM utility shows you what information is being cut and passed to your application. In this way, you can verify that the correct parameters are being passed to your application.


1. Sign onto the system.

2. Go to the CIM Customizer Configuration Detail screen and substitute the PARAM utility for your application's executable.

Note: There are two versions to this utility: a DOS-based version for use only on a 32-bit machine located in the M:\fs_apps directory (where M: represents the mapped drive), and the Windows-based version is located in the M:\mfgsys\system directory.


Note: Specify both the location and the filename.

3. Go to the BEXE (Batch Process Execution) screen and execute the batch process used to call your external application.

A message similar to the following is displayed:

PARAMETER DISPLAY UTILITY

0102

Parameter values are listed in the order the parameters were entered on the CIM Customizer Record Information window.

4. Press any key to refresh your screen.



PIPEDOS—Pipe to DOS from Microsoft WindowsThe PIPEDOS.EXE utility enables you open applications in separate windows. The PIPEDOS.EXE utility can be accessed from the command line in a DOS prompt window, by specifying the information in the Parameters field on the BSET (Batch Process Setup) screen within the system or as an external application defined on the CIM Customizer Record Information window.

Note: This DOS-based version is usable only on a 32-bit machine. It is located in the M:\fs_apps directory or M:\mfgsys\e (where M: represents the mapped drive).


Parameters passed to the PIPEDOS.EXE utility specify the application you wish to access or reactivate.

Several parameters are available to assist you in identifying the application information. Parameter entries are not case-sensitive. The available parameters for the PIPEDOS utility included:

You must create a unique identifier for the application you wish to access using a combination of the /tTaskName, /wWindowText and /eExeName parameters.

Note: Parameters must be enclosed in double quote marks (" ") if a space is needed in the parameter value.

General ExamplesThe following examples include ways that the CIM Customizer Utilities for Microsoft Windows could be used.

Defining External Application AccessExternal applications can be defined using the CIM Customizer Record Information window accessed from the CACF screen. The PIPEDOS.EXE utility is entered in the File Spec field and


/tTaskName Identifies the task name associated with a specific Microsoft Windows application currently running in the background. This is the description displayed in the Task List window.

/eExeName Identifies the location and filename of the application you wish to access and any associated data files.This parameter is required if the task is not currently running in the background.

/wWindowText Identifies the title of a window which was already started and is now running in the background.

/nNewWindowText Specifies the title to display on the window when the PIPEDOS utility accesses the application.

/dDefaultDir Sets the default directory to use when the application is running.

/sSize Identifies how the window should be displayed when accessed. Options include I = iconized, M = maximized, N = normal; default is N (normal)

/P Indicates that the program should wait until the requested task has completed before continuing.



the parameters are entered in the Parameters field. Screen cuts, map variables and configuration variable keywords are supported.

These examples assume you are familiar with the CSTM Module and using the CIM Customizer Record Information window. See the CIM Customizer manual for more information on external application definitions if needed.

PIPEDOS: Example 1—DOS Based ApplicationYou can access a DOS application (C:\WORK\TEST.EXE), pass the name of a data file C:\DATA\DATA.FIL as a parameter, set the default drive to C:\DATA, and name the DOS window "Sample DOS Window".

To access the application:

1. Open a DOS prompt window.

2. Go to the directory where the PIPEDOS.EXE utility is located.

3. Type: PIPEDOS "/eC:\WORK\TEST.EXE C:\DATA\DATA.FIL" "/nSample DOS Window" /dC:\DATA

4. Press Enter.

The application is accessed and the information you requested is displayed in another window.

PIPEDOS: Example 2—Access the SHOP CALENDAR WindowThe external application definition includes the following information and assumptions:

• The PIPEDOS.EXE utility is located in the directory defined by the WinProgFiles configuration variable.

• The location of SHOPCAL.EXE is unique. In a standard configuration, this location can be specified using the SystemDir configuration variable and would look similar to the following: /e$SystemDir$\SHOPCAL.EXE

The CIM Customizer Record Information window example uses the following field entries:

PIPEDOS: Example 3—Engineering Drawing DisplayYou can use an external application to review item-related engineering drawings from the POMT (Purchase Order) screen. The drawings are stored as *.PCX files and the filenames are defined by a mapping of the Item field. The Item is determined by where the line marker is positioned on the POMT screen. The engineering drawings are located in a directory defined by a user-defined configuration variable Eng_Drawings. The definition includes the following information and assumptions:

• The /e parameter contains required spaces and therefore needs to be passed as a single parameter in double quotation marks ("").

• A user-supplied DOS application for viewing engineering drawings is accessed. The application has a Microsoft Windows *.PIF file already defined called PCXVIEW.PIF.

Field Entry

Description Shop Calendar

File Spec $WinProgFiles$\PIPEDOS.EXE

Parameters “/e$SystemDir$\SHOPCAL.EXE”



• DOS prompt windows may be named by either the PIPEDOS utility or within the *.PIF file that defines the DOS application being called but not both. The /n%m parameter makes the window name the same as the drawing file name.

• The %m parameter passes the mapped value of the screen cut which contains the Item field where the line marker is positioned.

• The /d$Eng_Drawings$ configuration variable keyword sets the default directory to the location of the engineering drawings.

The CIM Customizer Record Information window example looks similar to the following:

Other Sample ApplicationsSome examples of ways to use the CSTM Windows Utilities together with the functionality of the CSTM Module include:

• Access a customer-related Microsoft Excel worksheet in a separate window using a user-defined key combination.

After reviewing the spreadsheet, minimize the Excel window into an icon and return to using Fourth Shift. You can return to reviewing the spreadsheet at any time by restoring from the icon.

• Execute a database query in a separate window.

For example, determine what normal, active items have no standard price. After reviewing the information, you can return to the system to enter the missing standard prices as needed while the query is displayed in another window.

• Activate a CIM Customizer menu from a specific screen.

Each item on the menu could access a Microsoft Windows application.

Field Entry

Description Engineering Drawing (PCX)

File Spec $WinProgFiles$\PIPEDOS.EXE

Parameters "/epcxview.pif %m.pcx" /n%m /d$Eng_Drawings$

Row 1

Col 6

Length 15



SETCFG—Set Configuration VariableThe SETCFG utility can set FS.CFG configuration variables to a specific date. The configuration variable can be referenced in a BSET parameter line to automatically use this date. This eliminates the need to edit the date in a BSET parameter line every time you run a batch task.

Note: There are two versions to this utility: a DOS-based version for use only on a 32-bit machine located in the M:\fs_apps directory (where M: represents the mapped drive), and the Windows-based version is located in the M:\mfgsys\system directory.

Note that the DOS-based version may not work properly when applied to a Windows Server 2008 R2 environment due to enhanced security changes.


Important: In an environment running a Windows Server 2008 operating system, the user running a BEXE with this utility needs to have read/write permissions to the FS.CFG file to successfully change the configuration variable values.

Setting the Configuration Variable1. Make sure all Fourth Shift users are logged out of the system.

2. Add configuration variable(s) to the FS.CFG to store the required date(s). Some systems may require that the variable use an underscore instead of a dash.

- Configuration Variable Examples:

DT-TODAY={TODAY}

DT-MINUS10={TODAY}

DT-PLUS10={TODAY}

3. Execute the SETCFG utility one time per day. Use of this utility will change the configuration variables in the FS.CFG file to the appropriate date.

Execution examples for using the DOS-based version:

- PROG M:\fs_apps\SETCFG /0 DT-TODAY={TODAY}

- PROG M:\fs_apps\SETCFG /0 DT-MINUS10={TODAY-10}

- PROG M:\fs_apps\SETCFG /0 DT-PLUS10={TODAY+10}

Note: The /N switch where N determines the date format. All calculated dates are per number of calendar days; i.e., one week = 7 days. Shop Calendar is not considered as part of the calculation.

- 0 = MMDDYY

- 1 = DDMMYY

- 2 = YYMMDD

For execution of the Windows-based version, substitute the path to M:\mfgsys\system.

Using this functionality:

The configuration variable for the date may be entered in the BSET parameter line in place if a date parameter. Bracket the variable with a $ symbol at the beginning and end where the date parameter would normally be entered.



Execution examples:.

SeqNum Task Parameters

10 SHPL F$DT-TODAY$ T$DT-T0DAY$ B000000 EZZZZZZ D

15 SHPL F$DT-MINUS10$ T$DT-TODAY$ B000000 EZZZZZZ D



STD2AAC—Standard to Average Actual Costing ConversionThe STD2AAC conversion process includes the following phases:

• updates the system costing method on the CCFG (Costing Configuration) screen to be Cost Method = A (average actual)

• adds average actual costing features, including the CCAN (Cost Control Action) screen and CSTU (Actual Cost Update) task

• adds the CSTUM and CSTUP batch source codes to the GLSC (G/L Source Code Maintenance) screen

• updates the manufacturing and purchase orders and creates cost action messages to be reviewed on the CCAN screen

Costs are not recalculated during the conversion process. Action messages for order lines with a Ln# Sta = 5 are generated and these messages can be reviewed after the conversion using the CCAN screen. Order lines that are not at a Ln# Sta = 5 are not changed. The average actual costing process begins once the lines are changed to Ln# Sta = 5.

Conversion ParametersSeveral parameters are available when you use the STD2AAC utility to convert your costing system. The parameters are used to configure your average actual costing system, as defined on the CCFG (Costing Configuration) screen. Changes are permitted on the CCFG screen after the conversion, also.

Note: The -C parameter, which identifies the name and location of the Fourth Shift configuration file, is a required parameter. All other parameters are optional.

Parameter OptionsParameters available with the STD2AAC utility include:

Parameter Description Values Default

-C name and location of Fourth Shift configuration (FS.CFG) file

M:\MFGSYS\FS.CFG

n/a

-TU upper tolerance percent 9999.99 105.00

-TL lower tolerance percent 9999.99 95.00

-UM user id to respond to manufacturing order cost exception messages

XXX MMM

-UP user id to respond to purchase order cost exception messages

XXX PPP



Numeric values entered are verified based on the Date and Number Format specified on the CNFG (System Installation Setup) screen.

Values Entered on CCFG ScreenDuring the STD2AAC conversion, parameter values are entered automatically for the CCFG screen into specified fields. The values may be modified on the CCFG screen after the STD2AAC conversion is completed. The fields include:

• Evaluation Cost Type—identifies the cost type specified on the ITMC screen that is used to evaluate actual costs before average actual costs are updated. Default cost type 0 (inventory value) is used.

• Lower Tolerance Percent—is the percentage used to determine the lower range of cost tolerance that is not considered out of tolerance in an average actual costing system. For example, if 5 percent under the evaluation cost is considered within tolerance, enter a lower tolerance of 95. Entry is up to 9999.99.

• Upper Tolerance Percent—is the percentage used to determine the upper range of cost tolerance that is not considered out of tolerance in an average actual costing system. For example, if 5 percent over the evaluation cost is considered within tolerance, enter a upper tolerance of 105. Entry is up to 9999.99.

• User Id to Receive Cost Exceptions for MO/PO—identifies the valid user identifications for the cost accountant assigned to respond to manufacturing and purchase order cost exception action messages. The cost exception action messages display on the CCAN (Cost Control Action) screen for the cost accountant identified in the Acct field.

STD2AAC Command Examples

Pre-conversion TasksProcess Existing Orders1. Use the MOMT or POMT screens to close all open orders possible.

2. Run the OVAR task to process orders and generate any standard cost variances and change the order status for closed and completed orders.

3. Run the PLNG task to update MRP planning information.

Determine Command ParametersDetermine the necessary parameters to use with the STD2AAC command for your system.

- The default parameter value is used if a parameter is not specified.

Create System Backup1. Perform a system backup of your system.

2. Label this backup: Pre-Average Actual Costing System Backup.

Command Description

STD2AAC -CM:\MFGSYS\FS.CFG -TUx -TLx -UMx - UPx

where "X" is your determined parameter value

STD2AAC -CM:\MFGSYS\FS.CFG uses all standard parameters

STD2AAC -CM:\MFGSYS\FS.CFG -UMAAA - UPBBB uses all default parameters



ConversionRun Conversion Program1. Verify that there are no user connections to the Fourth Shift system from any source.

This includes connections to Fourth Shift databases from Fourth Shift applications with a GUI, as well as ODBC and FSTI connections.

Note: If you use ODBC server, it must be stopped as well.

2. From a Command Prompt, go to the system directory, such as M:\mfgsys\system.

3. Run STD2AAC, specifying the configuration file for the system you want to update.

For example, type: STD2AAC -s-cM:\mfgsys\fs.cfg.

The STD2AAC utility processes then displays the following message in the Command Prompt window: Process Completed Successfully.

Note: If this message is not displayed, verify that the configuration file name and path are correct and try again.

Review Conversion ResultsReview the INSTALL.HIS file to verify that no errors were encountered during the conversion processing.

- The INSTALL.HIS file is created in the MFGSYS directory by default.

Verify Conversion Results1. Sign onto your system.

2. Verify that the configuration information at the top of the CCFG screen indicates Average Actual Costing.

Post-conversion TasksCreate System Backup1. Perform a system backup of your new Average Actual Costing system.

2. Label this backup: Average Actual Costing System Initial Backup.

Assign Screen SecurityAssign security access for the CCAN (Cost Control Action) screen and CSTU (Actual Cost Update) task.

- The CCAN and CSTU screens are available only in an average actual costing system.

Review Cost Type Information1. Sign onto your system.


3. Establish a Cost Type B (budget) cost type, if desired.

4. Enter a cost description for Cost Type B, for example: Budget Cost.

5. Review the cost description for Cost Type 0.

6. Change the cost description for Cost Type 0.

For example use AVG COST to reflect your average actual costing system.



Update Item Cost Records1. Go to the ITMC screen.

2. Use the ITMC screen to update item cost records for Cost Type B for all items.

3. Go to the CROV (Cost Roll Over) task.

4. Use the CROV task to roll costs into the Cost Type B item cost records, if desired.

5. Review and update your Cost Type 0 item costs.

The Cost Type 0 values are the beginning average cost for an item and are used in calculating average actual costs by item.

Review Costing Configuration1. Go to the CCFG (Costing Configuration) screen.

2. Review the additional fields in the lower section of the screen.

3. Review the costing options selected and update if necessary.

See “Setting Up the Module” in the Product Costing online manual for more information on using your average actual costing system.


Documents

Utilities and Tools Fourth Shift Release 7worthen.xdatasync.com/support/PrintDoc/UtilitiesTools.pdf · Fourth Shift Release 7.50 Utilities Quick Reference Utilities and Tools 5 Utilities