Archive

Posts Tagged ‘Syteline’

Google Insights for Search – Web Search Interest: syteline – Worldwide, 2004 – present

March 3rd, 2010 No comments

image 

Google Insights for Search – Web Search Interest: syteline – Worldwide, 2004 – present

Looks like Syteline is fading slowly in the past 5 years.  The pick up in early this year may be related to the ad campaign Infor recently run.  Hope they really do something, no just sit there simply claim themselves as third biggest ERP software firm. 

Categories: Application Tags: , ,

Dynamic change color on a row of grid, based on some cell value

January 21st, 2010 2 comments

This is considered by some people as Holy Grail of Syteline Form Personalization.

Here is what we want to do.  In “Time Phased Inventory” form, we want to change the color to yellow for those rows that is PO.

First, we need to create a new form script method, called SetPOColor()

Sub SetPOColor()
Dim i as Integer
Dim j as Integer
Dim sReference As String
Dim sRef3 As String
Dim sRef4 As String
Dim oSupDem As IWSIDOCollection

oSupDem = ThisForm.PrimaryIDOCollection.GetSubCollection(“SLSupDems”, -1)
j = oSupDem.GetNumEntries

‘    MsgBox(“j = ” + CStr(j))

For i = 1 To j

sReference = ThisForm.Components(“SLSupDemsGrid”).GetGridValueByColumnName(i, “SLSupDemsReferenceSubGridCol”)

sRef3 = Mid(sReference, 1, 3)
sRef4 = Mid(sReference, 1, 4)
If sRef3 = “PO ” Or sRef4 = “XPO ” Then
ThisForm.Components(“SLSupDemsGrid”).SetGridRowColColor(i, 0, “255,255,0”, “”)
End If
Next i
ThisForm.Components(“SLSupDemsGrid”).ForceRepaint
End Sub

Secondly, we create a new event handler for event “StdObjectSelectCurrentCompleted”, to call the above form script method SetPOColor().

Done.  Now here we are:

Convert a String to a Date / Time in VB

February 4th, 2009 No comments

Use CDate to convert a string to a date/time.

Dim d1 As Date
Dim d2 As Date
Dim d3 As Date

d1 = CDate("August 12, 2004")
d2 = CDate("2:07:30 PM")
d3 = CDate("August 12, 2004 2:07:30 PM")

Print d1  ' prints 8/12/2004
Print d2  ' prints 2:07:30 PM
Print d3  ' prints 8/12/2004 2:07:30 PM

Today’s Date

January 24th, 2009 No comments

It is very often that you need to get current date/time in your development.

T-SQL

To get today date without time as string variable use following script:

Select CONVERT( CHAR(8), GetDate(), 112)

To get datetime variable of today date without time use following script:

Select CAST( CONVERT( CHAR(8), GetDate(), 112) AS DATETIME)

VB

System.DateTime.Now.ToString(“yyyyMMddhhmmss”)

Now()

To initiate a date field as today’s date in Syteline form, need to use CURDATE().

How to block “PO Box” being entered into Customer Ship To Address

January 23rd, 2009 No comments

Problem:

Many business would not allow product shipped to a “PO Box” address.  So would like to block any “PO Box” address being entered into any ship to address.

Solution:

1)      Enter design mode of “Customer Ship Tos” Form.

2)      We are going to first create a script.  Go to “Menu -> Edit -> Script”, a Script window should open.  Click “New”, enter Script Name called “NoPOBox”, then click OK.

NoPOBox1

Put in the following script:

Option Explicit On

Option Strict On

Imports System

Imports Microsoft.VisualBasic

Imports Mongoose.IDO.Protocol

Imports Mongoose.Scripting

Namespace SyteLine.GlobalScripts

Public class NoPOBox

Inherits GlobalScript

Sub Main()

Dim strValue As String

Dim logicYN as boolean

Dim logicYN1 as boolean

Dim logicYN2 as boolean

Dim logicYN3 as boolean

Dim logicYN4 as boolean

strValue = GetParameter(0).ToUpper()

logicYN = strValue like “*PO BOX*”

logicYN1 = strValue like “*P.O BOX*”

logicYN2 = strValue like “*P.O.BOX*”

logicYN3 = strValue like “*PO. BOX*”

logicYN4 = strValue like “*P.O. BOX*”

If logicYN or logicYN1 or logicYN2 or logicYN3 or logicYN4

ReturnValue = “1”

else

ReturnValue = “0”

end if

End Sub

End Class

End Namespace

Then “OK” to save the Script, and “Done” to close the Script window.

3)      Create a Validator.

While we are still in the design mode of “Ship Tos” Form, from menu, go to “Edit -> Validator”.  A “Validator” window open, click “New”.  In the “Validator Properties” window, enter “NoPOBox” as name, “Run Script” as type.  Select “NoPOBox” as script name from the pull-down list, that is the script we just created in step 2).

NoPOBox2

Then, create Error Message: “PO Box Is Not Valid Address”.

NoPOBox3

Click OK all the way back, we now have created a validator called “NoPOBox”, and we can apply it to the fields that we want to validate.

4)      Apply validator

NoPOBox4

Click to enter PV(Addr_1), that means property value of Addr_1, as parameters.

NoPOBox5

5) Now save the change and exit out of design mode, we should be able to see the validation is working:

NoPOBox6

Cut Over Plan

December 23rd, 2008 No comments

Syteline system cut over will be the biggest milestone of your implementation project.  Careful planning would be essential to your project success.

Section A – Initial Setup

Step Form Purpose Owner(s) Due Date Scope

(Task Size – Small (<1Day) Medium (<1wk)

Large >1wk)

A1 Groups Specify groups who are allowed access to the SyteLine ERP system.
A2 Group Authorizations (Linked) Allows the system administrator to set up different levels of access for every group within the SyteLine ERP system.
A3 Users Specify users who are allowed access to the SyteLine ERP system.
A4 User Authorizations (Linked) Allows the system administrator to set up different levels of access for every user within the SyteLine ERP system.
A5 General Parameters Lets you set the parameters used throughout the system. Small
A6 Countries (Optional) Set up country codes used throughout the system. Small (add as needed)
A7 Prov/States Set up province/state abbreviations used throughout the system. Small
A8a Currency Codes (Optional) Maintains currency codes used throughout the system. Small
A8b Currency Conversion Parameter Form (Optional) Small
A8c Currency Rates (Optional) Small
A9 Language Ids (Optional) Identify the language used in a string table in the forms database. Small – English is the only supported lanugage

Section B – General Ledger Setup

Step Form Purpose Owner(s) Due Date Scope

(Task Size – Small (<1Day) Medium (<1wk)

Large >1wk)

B1 Accounting Periods Maintains the accounting periods used by the General Ledger to post transactions. Small
B2 Account Number Formatting Allow you to change the General Ledger account number or to respecify the section of the account number to use as the sub-account (or whether to use a sub-account at all). Small
B3 Unit Codes Used to view, enter, budget, and report financial information by reporting unit, at the account/sub-account level.  Sub-accounts are not recommended. Small
B4 Departments Maintains a list of all departments referenced by work center and employee records.  Departments are also linked to Unit code 1 for financial reporting. Small
B5 Chart of Accounts Defines account numbers, which will be used throughout the SyteLine ERP system to record, track, and report costs. Small
B6 Chart of Account Allocations (Optional) Routinely distributes an expense among more than one account according to percentages you define. Small
B7 Statistical Accounts (Optional) Used in financial statements to compare important non-financial data to related financial data for measuring such things as productivity and controlling costs Small
B8 Budgets and Plans (Optional) Worksheet used to create budgets and plans for each individual account, accounting period, and fiscal year.

Section C – General Financial Setup

Step Form Purpose Owner(s) Due Date Scope

(Task Size – Small (<1Day) Medium (<1wk)

Large >1wk)

C1 Bank Reconciliations Keeps a transaction history against all the bank checking accounts your company uses.  Also used to define the GL Cash account used when processing payment transactions. Small
C2 Bank Addresses (Linked) Maintains address information for the banks your company uses. Small
C3 Ship Via Codes Used to identify the delivery methods available to ship merchandise. Small
C4 Billing Terms Codes Maintains billing terms used by both customers and vendors. Small
C5 Tax Parameters Defines global (applying to both tax systems) switches and dates, and to set optional tax data printing options. Small
C6 Tax System Assign a numerical code to the tax system (ex. 1 = State). Small
C7 Tax Jurisdiction (Optional) Assign a code to the tax jurisdiction (ex. CO = Colorado). Used only if reporting tax by Jurisdiction. Small
C8 Tax Codes Used to specify the percentage of tax to charge to a customer and the GL Account to which the tax is to be posted. Small
C9 Product Codes Allow you to group similar types of items and assign price markups, discounts, GL accounts, tolerance factors, and selection criteria for reports of those groups.  Used to group items for financial purposes using reporting units, and to group for general reporting. Small
C10 Fixed Asset Depreciation Tables (Optional) Used to define custom depreciation methods.  Standard depreciation schedules are already built into the system and can only be viewed by displaying help. Small
C11 Bonus Depreciation Codes (Optional) Used to define additional depreciation. Small
C12 Fixed Asset Parameters Establishes titles for up to three depreciation schedules.  The only one that will be used to post financial transactions is Book. Small
C13 Fixed Class Codes Enter the identifier for the GL account class being established in the system. It is a user-defined code. Small
C14 Fixed Assets Maintains all identifying and descriptive information unique to an asset. Small
C15 Fixed Asset Depreciation Used to define the method in which SyteLine ERP calculates depreciation for each active asset. Small
C16 Fixed Asset Costs Maintains a comprehensive history of all costs accumulated for an asset. All costs will be used for depreciation purposes, except type “Repair.” Small
C17 Project Default Parameters Used to enter the GL account numbers that SyteLine ERP will use. Small
C18 Project Types Used to enter all the codes that classify the project types. Small

Section D – Accounts Payable Setup

Step Form Purpose Owner(s) Due Date Scope

(Task Size – Small (<1Day) Medium (<1wk)

Large >1wk)

D1 Accounts Payable Parameters Define aging buckets, specify the accounts to use in the GL, and provide 1099 information. Small
D2 Payment Hold Reason Code Explains why you put the current vendor on payment hold. Small
D3 Recurring Vouchers (Optional) Allow you to generate monthly vouchers for transactions in which the vendor and amount are always the same. Small

Section E – Accounts Receivable Setup

Step Form Purpose Scope

(Task Size – Small (<1Day) Medium (<1wk)

Large >1wk)

E1 Accounts Receivable Parameters Used to enter the default parameter values SyteLine ERP applies throughout Accounts Receivable. Small
E2 Salesperson Classifications (Optional) Used to create sales force classifications by region, division, locality, area, and so on. Small
E3 Salespersons (Optional) Maintains the list of valid salespersons that can be entered for each order header. It is recommended to setup a salesman for either salesman reporting and/or commissions reason. Small
E4 End User Type Used to classify customers and customer orders and to overwrite Sales, Sales Discounts, Accounts Receivable, and COGS accounts based on the specified end user type.
E5 Distribution Accounts Defines distribution accounts for a grouping of items. Small
E6 Finance Charges (Optional) Used to enter amounts charged to the customer for their overdue balances.
E7 Dunning Report (Optional) Use Crystal Reports to modify the report output format, adding your company address, a salutation, and introductory and closing text.
E8a Credit Hold Reason Codes Used to define codes used to explain why various customers have been placed on credit hold. Small
E8b Customer Credit Limits Set credit limits for repeat customers $500k (AZ, Roland DG…) for all others $100k Small
E8C Customer Billing Terms Define customer specific terms Small
Customize Invoice modify the invoice output format, adding your company address, a salutation, and introductory and closing text. Medium
Order Verification modify the form output format, adding your company address, a salutation, and introductory and closing text. Medium
Packing Slip modify the form output format, adding your company address, a salutation, and introductory and closing text. Medium
ProForma Invoice modify the form output format, adding your company address, a salutation, and introductory and closing text. Make sure Commodity Codes Print Medium

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Backup Database before entering Section F (note Parameter forms can be entered, no master data just static data)

Section F – Inventory Setup

Step Form Purpose Owner(s) Due Date Scope

(Task Size – Small (<1Day) Medium (<1wk)

Large >1wk)

F1 Inventory Parameters Used to set parameters in your inventory system for use throughout the entire SyteLine ERP system. Small
F2 Units of Measure Used to maintain all units of measure that can be associated with an item. Med
F3 Unit of Measure Conversions Maintains valid mathematical relationships between units of measure. Large
F4 Family Codes (Optional) Allow you to classify groups of items for planning purposes.
F5 Warehouses Maintains all warehouses used in the system. Small
F6 Locations Maintains the list of valid places for inventory. Small
F7 Obsolete/Slow Reason Codes Used to explain why you are designating an item as obsolete or slow-moving inventory. Small (Use blank, do not put GL accts, let product code define)
F8 Commodity Codes (Optional) Used to identify various commodities. Small (figure out how to get them to display)
F9 Items Used to maintain a list of all items bought, manufactured, and/or sold. Large
F9 Items Lead Times and ABC Set long lead critical items (LEDs, substrates) ABC Code A and then use 3days as generic for all remaining items ABC Code C, custom machined parts 3wks ABC Code B Large
F9b Items-Mfg Name/PN Enable User Defined Fields in Item Master for this purpose Med
F10 Item Stockroom Locations (Linked) Used to create a record of every location where an item is to be kept. Small (If we use one stock location)
F11 Item Costs (Linked) Tracks costs associated with items entered on the Item Maintenance screen. Large
F12 Item Pricing (Linked) Maintains pricing and pricing options, which can be associated with items. Medium
F13 Item/Warehouse Adds an item to warehouses in addition to the default warehouse.
F14 Lots Maintains information about lots and their locations. Small (Use lots to track Feature BOM items or SN???)
F15 Item Lot Locations Maintains information about all lot-tracked items and their locations.
F16 Transfer Order Parameters (Optional) Used to set parameters for transfer orders.
F17 Misc. Receipt Reason Codes Used to track the entry of  Miscellaneous Receipt transactions. Small (Use blank, do not put GL accts, let product code define)
F18 Misc. Issue Reason Codes Used to track the entry of Miscellaneous Issue transactions. Small (Use blank, do not put GL accts, let product code define)
F19 Inv. Adjustment Reason Codes Use to explain why a quantity adjustment to inventory is needed. Small (Use blank, do not put GL accts, let product code define)
F20 Transfer Loss Reason Codes Used to explain quantity adjustments to inventory due to transfer losses. Small (Use blank, do not put GL accts, let product code define)
F21 Reservations for Item (Optional) Used to reserve an item.

Section G – Purchasing Setup

Step Form Purpose Owner(s) Due Date Scope

(Task Size – Small (<1Day) Medium (<1wk)

Large >1wk)

G1 Purchasing Parameters Enters default values for use throughout Purchasing. Small
G2 Vendor Categories(Optional) Used to add categories to assign to your vendors for financial grouping purposes.
G3 Vendors Maintains a record for all vendors with whom your company deals. Medium (must use AP address)
G4 Drop Ship To(Optional) Used to identify a drop ship address different from the address that appears on the Vendors form. Enter as needed
G5 Vendor/Item Cross Reference Used to associate items with Vendors; allows the setup of vendor part number to your part number and history. Large
G6 Vendor/Item Pricing Used to create vendor specific pricing and quantity price breaks, date sensitive Enter as required for open and new orders
G7 Vendor Letter of Credit(Optional) Used to document letters of credit (LCRs) from your banks to vendors who require them.
G8 Purchase Order Requisition Codes Used to define codes to track the entry of requisitions.

Section H – Sales/Order Entry Setup

Step Form Purpose Scope

(Task Size – Small (<1Day) Medium (<1wk)

Large >1wk)

H1 Order Entry Parameters Used to set default values for customer order entry. Small
H2 Price Codes A user defined code applying to customers or items.
H3 Price Matrix Allow you to associate a specific Price Code with a corresponding Customer and Item to form a price matrix.
H4 Price Formulas Used to enter a pricing formula from which to calculate the necessary unit prices.
H5 Commissions Table Maintenance Contains commission percentage information for each salesperson.  Before this is done, you must first set the labels from the Activities>set labels.  Basically, input salesman as the first and commission for the second.  This will input the labels used when inputting the commission rates and salesman.
H6 Customer Letters of Credit(Optional) A document from a bank stating that the bank will insure the customer’s payment.
H7 Customer Type(Optional) Using them allows you to sort reports by customer type.
H8 Customers Stores all the relevant information for storing basic customer data and tracking what customers buy from the company, as well as what customers owe. Small (active customers only)
H9 Customer Item Cross Reference Track and control information about items bought by specific customers, customer specific items, and customer specific pricing. Enter as new orders come in
H10 Item Pricing Maintains pricing and pricing options, which can be used with items.
H11 CO Returns Reason Codes Used to define codes used to track adjustments to inventory for customer order returns.
H12 RMA Parameters Used to set default values for RMA functions.
H13 Problem Codes Codes used to track and report problems at the order level.
H14 Evaluation Codes Codes used to track and report RMAs at the line item, or individual material, level.
H15 Disposition Codes Used to enter codes at the line item, or individual material, level, which you will use to track and report what happens to material after it has been returned.

Section I – Manufacturing Setup

Step Form Purpose Owner(s) Due Date Scope

(Task Size – Small (<1Day) Medium (<1wk)

Large >1wk)

I1 Shop Floor Control Parameters Sets up default policies for scheduling jobs, What-If jobs, and estimate jobs in SyteLine ERP. Small
I2 Shift Codes Maintains codes that identify particular shifts. Small
I3 Holidays Used to enter all dates the entire shop floor is not in operation. Small
I4 Resources Defines resources that perform work on the shop floor. A resource is a non-specific person, machine, or other tool used in at least one step of the manufacturing process. Small
I5 Resource Groups Used to organize resources that can perform the same function. Small
I6 Work Centers For viewing and maintaining information about the work centers in the SyteLine ERP system. Small
I7 Current Operations Maintains routing requirements and costing information for an item. Large
I8 Current Materials Maintains material requirements, costs, and reference information for an item. Large
I9 Planning Parameters Enables features and options used throughout the MRP and APS planning functions. Small
I10 Planning Horizon Calendar Used to enter starting dates for MRP, APS, and master planning horizontal display periods. Small (use monthly buckets)
I11 Forecast Used to enter a prediction of requirements for an item.
I12 Exception Message Priority Used to filter out messages considered less important when generating the Exceptions Report.
I13 ECN Reason Codes Defines codes used to explain why an engineering change is needed.
I14 ECN Priority Codes Defines codes that establish priority for suggested ECNs.
I15 ECN Distribution Codes Used to create distribution lists to add to the ECN.

Section J – Human Resources / Payroll Setup

Step Form Purpose Owner(s) Due Date Scope

(Task Size – Small (<1Day) Medium (<1wk)

Large >1wk)

J1 Human Resource Parameters Used to enter the frequency with which each employee should be reviewed. Small
J2 Position Classification Used to enter information classifying the employee’s position. Small – Sales only
J8 Employees Stores all the information necessary for processing and tracking employee payroll, wages, taxes and deductions, and so on. Small – Sales only
J10 Companies Used to enter basic information about the company and its CEO.
J11 Divisions Used to enter information about the divisions within the company.

K – Beginning Balances

Step Form Purpose Owner(s) Due Date Scope

(Task Size – Small (<1Day) Medium (<1wk)

Large >1wk)

K1 Inventory Large
K2 AR
K3 AP
K4 Customer Orders
K5 Purchase Orders
K6 Ledger Balances
K7 Open Jobs

L –Action Items

Step Form Purpose Owner(s) Due Date Scope

(Task Size – Small (<1Day) Medium (<1wk)

Large >1wk)

L1 Order and setup for printed checks Medium
L1 Setup and Test Foreign Currency Customers
L3 Projects Module
L4 Write Syteline Work Instructions for Mfg Large
L5 Remove obsolete parts from P&V Large
L6 Background Ques – e.g., Run MRP nightly or weekly
L7 Backup Plan Syteline data Small
Test and Setup Customer Profiles – to email invoices etc directly to customer and accounting
Setup financial statements
Phase 1 Preparation

Cost Roll Ups

Roll Current to Standard

Large
Journal Entries – Purge all “Dist” Journals  IC, PO, SF

How to use the Query Form

September 23rd, 2008 No comments

The “Query” function in Syteline allows you to use multiple selection criteria to query transaction.  The example below show you how to query manual transactions for inventory account in a given date range.

Open the “GL posted transaction query” form.ScreenShot001

Click “Additional Criteria” tab.
ScreenShot002
In the first pull down list, select “Account”.  In second pull down list, select “=”.  Put in an account#, or select from pull down list in the last field, then click the “Add” button.

ScreenShot003Select “Posted from”, let it “=” to General.  That means we will only select transactions that is posted from “General Journal”, instead of normal inventory transactions that are posted from “IC Journal”.  Then click the “Add” button.

Repeat the similar process for “Transaction date”, to give a date range.  Once finished entering all the criteria, click the “Refesh” button.  Transaction data should shows up.

ScreenShot004Right click on left-upper corner of the grid, from the menu, select “To Excel”, you will then be able to export the data to Excel.

The similar query process will work on all the “Query” form.

Categories: Application Tags: , , , , ,

How to Write Procedure

August 23rd, 2008 No comments

The Definition of Procedures

Procedures represent the documentation of business process.  Their purpose is to document all business processes, strategies, and principles and their related information.  In terms of ISO 9000, procedures represent the Level B/Tier 2 of the Quality System.  Procedures should be written in a detailed manner.  They should cover the ‘5 – Ws’, what, where, when, why, and who.  A common rule of content to adopt is 90% specific and 10% general.

Getting Started

Getting organized to begin the process of procedure writing requires several administration steps.  The first step is to determine what kind of procedure system do you require.  This can be determined by reviewing your current procedure situation.

  • Do procedures exist?
  • Are these procedures current?
  • Is there a common procedure?
  • Are or will the current procedures required for a regulatory certification?
  • Review current situation
  • Determine required control
  • Pick a procedure format
  • Start a procedure log
  • Educate procedure writers

Getting Started

The answers to these questions will assist in determining the level of control required manage your procedures.

The next steps are to select the proper procedure format for your system and develop a procedure log to establish procedure requirements. There is no one standard procedure format.  Selecting a procedure format is a matter of reviewing possible styles and selecting the one suited best to meet your requirements.  If a certification, like ISO 9000, is factor a specific procedure format or content may be required.  . Check with you registrar for recommendations.  Establishing a procedure log through the course of the implementation will allow written procedures to be documented and tracked.  Establishing this log prior to the business pilot will allow you to determine the scope of procedure writing required for your implementation.  Some of the most common elements of a procedure log are procedure numbers, titles, revision level, functional area, person responsible, approval responsibilities, and related dates.

Once the procedure system and format have been established, the next step is to select and educate procedure writers.  Often the best people to write the procedures are the ones responsible for the tasks.  The selected procedure writers should be given proper education on what is expected and to review the selected procedure format and content.  Practicing flowcharting business processes is an excellent way to begin the process and to develop proper technique.  Flowcharting helps to understand the level required and where additional or smaller procedures are needed.  After completing the flowchart, the procedures can then be easily written in the specified format or in a draft fashion for a clerical person to input for review.  The final step is to review, approve, and distribute the finished procedures.


Procedure for writing a procedure

1.0 Purpose

1.01     The purpose of this procedure is to detail the requirements necessary                  in documenting a procedure

2.0 Scope

2.01     All procedures must be prepared on standard format paper.

2.02     All procedures must have as a minimum the following:

  • title
  • procedure number
  • issue number
  • date
  • page number
  • purpose
  • scope
  • responsibility
  • definition
  • procedure itself
  • references

2.03     The decision, as to whether or not a written procedure is necessary,                          should be taken on the basis that if the absence of such a procedure                                could adversely affect the quality of work being performed, then a                          procedure is necessary.

2.04     The language used in a procedure should be specific enough to avoid                 ambiguity and general enough to ensure it is practical.

2.05     Documentation Control controls the issue of the procedure numbers                               and the procedure log.

3.0 Responsibility

3.01     Primary responsibility for the adherence to the requirements of this                           procedure shall rest with the originator, with contributing                                          responsibility from the appropriate Function Head.

4.0 Definitions

4.01     Function Head.

The Function Head is defined as the manager for the area in which                                the procedure will be performed.

4.02     Originator.

The preparation and writing of a procedure shall be undertaken by                          personnel familiar with the function to be controlled.  The person(s)                                so defined shall be the originator of the procedure.

4.03     Controlled Document.

Authorized copies of procedures, which are produced on the colored                 pro-forma paper, shall be classified as controlled documents.

Authorized copies of procedures, which are not on colored pre-                          printed paper, shall be classified as uncontrolled documents, i.e.                                 photocopies.

5.0 Procedure

5.01     The Originator will prepare a draft procedure.

5.02     The Originator will then forward the draft procedure to all                                        departments affected by the procedure for their comments.

5.03     Departments are normally given two weeks to respond with their                             comments.  (Originators should specify in a covering memo, the                          deadline for comments and circulation list.)

5.04     Comments are taken into account and the procedure modified if                               necessary.  The Project Leader will arbitrate on any disagreements.

5.05     The Originator signs and dates the document under the Approval                            Section.

5.06     Document Control issues official copies of the procedure.

6.0 Reference Documents

6.01     The references shall identify all procedures, operating instruction,                                   and documents referred to within the procedure, which are not part                                of the procedure itself.

Sample Procedure Format

Title
Originator Procedure Title Issue Number
Approval Procedure Number Issue Date

1.0 Purpose

Objective of the procedure.

2.0 Scope

To what activities the procedure applies.

3.0 Responsibility

Who is responsible for implementation?

4.0 Definitions

Terms or words not readily understood.

5.0 Procedure

Step by step instructions of each activity stating:

  • What is done?
  • By whom?
  • When, where, and possibly why?

6.0 Reference Documents

Any other documents or referred to activities.

CRP Planning

July 23rd, 2008 No comments

Categories: Implementation Tags: , ,

CRP Script

July 2nd, 2008 No comments

CRP – INVENTORY CONTROL

  • Set up parameter files
  • Determine item structure for Item Master.  Determine what will be inventory items and non-inventory items.
  • Determine structure for Product Codes/Distribution Accounts.
  • Set up master files
    • Item Master
      • Purchasing information
      • Manufacturing information
      • Costing information
      • Engineering information
      • Sales information
    • Product Codes/Distribution Accounts
    • Warehouse Master
    • Stock Locations
      • Nettable/non-nettable
      • Temporary/permanent
    • Reason Codes for miscellaneous inventory transactions
    • Set up Customer/Item and Vendor/Item Cross References
    • Determine valid item/stockroom locations for each inventory item & ranking
    • Determine use of lot tracking and/or serial tracking
    • Determine use of item reservations
      • Procedures to be considered and tested, including how-to, responsibility, frequency, reporting requirements:
        • Item maintenance, including BOMs
        • Product Code/Distribution Accounts maintenance
        • Warehouse orders and transfers
        • Use of miscellaneous inventory transactions
        • Cycle count
        • Physical inventory
        • Periodic procedures and utilities
          • Rebalance utilities
          • Cost roll-ups
          • Roll current unit cost to standard unit cost
          • Delete transactions/locations/lots/serial numbers
          • Set item PTD and YTD totals to zero
  • Determine reports and/or documentation to be used for all procedures – SyteLine and internal
  • Establish guidelines for retention of documents and reports – printing hard copies or printing to the terminal

CRP – BOM

  • Set up master files
    • Work Centers – scheduling & costing information
    • Machine Master
    • Maintenance schedules
    • Cells
    • Create current routings and bills of material for manufactured items
    • Perform BOM utilities to create standard routing/BOM
      • Low Level Processor
      • BOM Cost Roll-up
      • Roll Current Unit Cost to Standard Unit Cost
  • Procedures to be considered and tested, including how-to, responsibility, frequency, reporting requirements:
    • BOM maintenance
    • Periodic procedures and utilities
      • Cost roll-ups
      • Roll current unit cost to standard unit cost
      • Delete utilities
      • Substitutions
  • Determine reports and/or documentation to be used for all procedures – SyteLine and internal
  • Establish guidelines for retention of documents and reports – printing hard copies or printing to the terminal


CRP – ENGINEERING CHANGE NOTICES

  • Set up codes
    • Priority Codes
    • Reason Codes
    • Distribution Codes
  • Procedures to be considered and tested, including how-to, responsibility, frequency, reporting requirements:
    • Use of Engineering Change Notices for items, estimates, and/or jobs
      • Guidelines for use
      • Requests
      • Flow of documentation through system
      • Changes to
      • Revision tracking
      • Approval
  • Determine reports and/or documentation to be used for all procedures – SyteLine and internal
  • Establish guidelines for retention of documents and reports – printing hard copies or printing to the terminal


CRP – ORDER ENTRY

  • Set up parameter files
  • Set up master files, creating examples of each possible type of record or situation that may occur
    • Customer Master
    • Ship-To Addresses
    • Salesperson Master
    • Billing Terms
    • Ship Via Codes
    • Shipping Return Reason Codes
    • Customer Hold Reason Codes
    • Set up Customer/Item cross-references
    • Determine use of Drop Ship To’s
    • Tax codes
      • Determine requirements for reporting on sales tax collected
      • Establish required tax codes
      • Establish procedures for assessing sales tax on orders
      • Pricing
        • Review requirements
        • Establish pricing by some combination of available methods
        • Determine procedures for price changes
        • Determine procedures for exceptions to existing pricing
        • Determine procedures for new item pricing and/or modifications to items
  • Procedures to be considered and tested, including how-to, responsibility, frequency, reporting requirements
    • Customer Order Entry – steps
      • Create order
      • Print Order Verification
      • Verify on-hand, available to ship
      • Print Order Pick List
      • Ship items
      • Print Packing Slip
      • Print Bill of Lading
      • Invoice order
      • Close order after invoicing
    • Customer Order Entry – types of orders to consider
      • Regular/blanket in stock
      • Regular/blanket manufacture to order
      • Regular/blanket conversions
      • Regular/blanket spare parts
      • Regular/blanket services
      • Other

CRP – ORDER ENTRY (contd.)

  • Changes to existing orders
  • Managing back orders – completing/not completing
  • Expediting orders
  • Progressive billing – use and management
  • Stopping/re-releasing orders
  • Order cancellations
  • Shipping return procedures
    • Use of RMAs to manage
    • Flow of documentation through the system
    • Notification to shipping department and customer service/accounting          for credit to customer
    • Perform shipping return
    • Inspection of returned goods and return/not return to inventory
    • Generation and control of credit memos
    • Un-ship (prior to invoicing)
    • Use of credit holds and credit limits
      • Compliance and exceptions
      • Changes to credit limit
    • Order Inquiry handling by customer service
    • Reserving inventory for orders
    • Adjustments to price after invoicing
    • Commissions
      • Use of SyteLine commission structure or external
      • Management of calculation
      • Adjustments to
      • Payment through AP or Payroll
    • Routine utilities and procedures
      • Closing orders
      • Purge Customer Order Audit Trail
      • Rebalance Customer Order/Posted Balance
      • Balance History
      • Period/Year end Procedures
      • Delete and purge transactions
  • Determine reports and/or documentation to be used at each step – SyteLine and internal
  • Establish guidelines for retention of documents and reports – printing hard copies or printing to the terminal

CRP – PURCHASING

  • Set up parameter files
  • Set up master files, creating examples of each possible type of record or situation that may occur
    • Vendor Master and remit to vendors
    • Billing Terms
    • Ship Via Codes
    • Drop Ship To’s
    • Receiving Return Reason Codes
    • Set up Vendor/Item cross-references
    • Determine use of Drop Ship To’s
      • Procedures to be considered and tested, including how-to, responsibility, frequency, reporting requirements
        • Purchase Requisitions – if and for what items
        • Purchase Order Entry – steps
          • Create purchase order
          • Verify cost
          • Print Purchase Order
          • Print purchasing Receiving List
          • Receive items
          • Close order after vouchering (AP)
    • Purchase Order Entry – types to consider
      • Regular/blanket for inventory stock items
      • Regular/blanket for non-inventory items
      • Regular/blanket Customer Orders – cross-reference or not
      • Regular for Job Orders – cross-reference or not
      • Regular for inter-company purchases
    • Lot/serial controls on purchases
    • Expediting Purchase Orders
    • Canceling Purchase Orders
    • Managing back orders – completing/not completing
    • Receiving returns
      • Use of RMAs to manage
      • Flow of documentation through the system
        • Notification to receiving department and accounting for credit from vendor
      • Perform receiving return
    • Un-receive (prior to vouchering)
    • Use of PO Change Orders
      • Determine use of Vendor Communications Log

CRP – PURCHASING (contd.)

  • Routine utilities and procedures
    • Closing Purchase Orders
    • Closing Change Orders
      • Review and update Purchased Current Unit Cost if vouchered cost does not equal received cost
      • Purge Purchase Order Audit Trail
      • Rebalance items
      • Delete utilities
      • Determine reports and documentation to be used – SyteLine and internal
        • Determine how purchasing requirements will be determined – Purchase Requirements Report or MRP
        • Determine if tax codes are to be used for purchasing
          • Establish tax codes as required
          • Establish procedures for assessing use tax
          • Determine reporting requirements for use tax on purchases

CRP – ACCOUNTS PAYABLE

  • Set up parameter files
  • Set up master files, creating examples of each possible type of record or situation that may occur
    • Vendor Master and remit to vendors
    • Salesperson Master
    • Billing Terms
    • Ship Via Codes
    • State Master
    • Vendor Payment Hold Reason Codes
    • Bank Codes
    • Set up Vendor/Item Cross-references
    • Establish tax codes as required
      • Establish procedures for assessing use tax
      • Determine reporting requirements for use tax on purchases
  • Procedures to be considered and tested, including how-to, responsibility, frequency, reporting requirements
    • Vouchering
      • From purchasing
      • Manually through Vouchers & Adjustments
      • Generating recurring vouchers
      • Distributing manual and recurring vouchers
    • Voucher Adjustments
      • From purchasing returns
      • Manually through Vouchers & Adjustments
      • Distributing voucher adjustments
    • Payment processing
      • Manual check posting
      • Generation of standard checks
      • Manual addition of standard checks
      • Selection of check distributions
      • Check printing and posting
    • Void checks prior to posting and after posting
    • Putting vendors and/or vouchers on hold
    • Use of Vendor Communications Log
    • Routine utilities and procedures
      • Year end procedure
      • Delete transactions
      • Deactivate posted transactions
      • Generate currency gains/losses
      • Purge Vendor Master Audit Trail

CRP – ACCOUNTS PAYABLE (contd.)

  • Determine reports and documentation to be used – SyteLine and internal
    • Establish procedures for retention of documents and reports – printing hard copies or printing to the terminal

Accounts Payable Cut-Over Procedures:

  • Order checks
  • Set up recurring vouchers
  • Enter all AP open vouchers at cut-over date into Vouchers & Adjustments (this includes those items vouchered in the existing system – i.e. already recorded in general ledger on the existing system)
  • Enter all AP open payments, if any, such as an un-applied deposit on a vendor’s account at cut-over date into Payments
  • Post Vouchers & Adjustments and Payments files to AP Distribution Journal
  • Purge AP Dist. of all transactions
  • Print AP Aging.  Verify vendor balances to AP Aging on existing system.
  • Enter outstanding checks into Bank Reconciliation file

CRP – ACCOUNTS RECEIVABLE

  • Set up parameter files
  • Set up master files, creating examples of each possible type of record or situation that may occur
    • Customer Master
    • Ship-To Addresses
    • Salesperson Master
    • Billing Terms
    • Ship Via Codes
    • Bank Codes
    • Establish tax codes as required
      • Determine requirements for reporting on sales tax collected
      • Establish procedures for assessing sales tax on orders
  • Procedures to be considered and tested, including how-to, responsibility, frequency, reporting requirements
    • Invoices, debit memos, and credit memos
      • Generate from Order Entry
      • Price Adjustments generated in Order Entry
      • Create and print from Accounts Receivable
        • Uses for AR invoices, debits, and credits
        • Distributing AR invoices, debits, and credits
      • Invoice posting
      • Transactions review
    • Payments
      • Distributions to invoices
      • Prepayments tied to Customer Orders
      • Open payments
      • Non-AR payments
      • Payment posting
      • Re-application of open payments
      • Re-application of open credits and debits
    • Add bank deposits to Bank Reconciliation file
    • Process finance charges
    • Review posted transactions for open transactions
    • Collections, statements, dunning letters
    • Use of Customer Communications Log

CRP – ACCOUNTS RECEIVABLE (contd.)

  • Routine utilities and procedures
    • Rebalance Customer Order/Posted Balance
    • Balance History
    • Period/Year end Procedures
    • Delete and purge transactions
    • Deactivate Posted Transactions
    • Purge Customer Audit Trail
    • Generate Currency Gains/Losses
    • Determine reports and/or documentation to be used – SyteLine and internal
      • Establish procedures for retention of documents and reports – printing hard copies or printing to the terminal

Accounts Receivable Cut-Over Procedures:

  • Order invoices and statements
  • Enter all AR open invoices at cut-over date into Invoices, Debits, & Credits screen (this includes those items invoiced in the existing system – i.e. already recorded in general ledger on the existing system)
  • Enter all AR open payments, if any, such as an un-applied deposit on a customer’s account at cut-over date into Payments
  • Post Invoices, Debits & Credits and Payments files to AR Distribution Journal
  • Purge AR Dist. of all transactions
  • Print AR Aging.  Verify customer balances to AR Aging on existing system.
  • Enter deposits in transit into Bank Reconciliation file

CRP – GENERAL LEDGER

  • Establish Chart of Accounts
  • Set up parameter files
  • Determine financial reporting requirements
  • Determine use of Budgets and Plans
  • Set up accounting periods
    • Procedures to be considered and tested, including how-to, responsibility, frequency, reporting requirements
      • Posting journals
      • Standard entries and recurring journals for those entries
      • Correcting journal entries
      • Creation and generation of financial statements
      • Using Bank Reconciliation
      • Periodic procedures and utilities
        • Updating accounting period
        • Maintaining budgets and plans
        • Maintaining chart of accounts
        • Year-end closing
    • Account analysis
    • Determine reports and/or documentation to be used – SyteLine and internal
      • Establish procedures for retention of documents and reports – printing hard copies or printing to the terminal

General Ledger Cut-Over Procedures:

  • Enter accounting periods for current year and other years, as applicable
  • Enter net monthly GL account balances into a Balances journal for the current YTD and prior year, if applicable (this includes those items posted in the existing system – i.e. already recorded in general ledger on the existing system)
  • Load budgets and plans
  • Post Balances journal
  • Reconcile posted GL balances to current system

CRP – PRODUCTION PLANNING/CONTROL

  • Set up parameter files
  • Set up master files
    • Shop Calendars
    • Holidays
    • Employees
  • Procedures to be considered and tested, including how-to, responsibility, frequency, reporting requirements
    • Determine how manufacturing requirements will be determined – Purchase Requirements Report or MRP
    • Job cycle – steps
      • Create job and copy item routing/BOM
      • Modify job routing/BOM
      • Release job
      • Job paperwork and dispatch list
      • Post transactions through backflushing or transaction entry
      • Lot controlled items on jobs
      • Job analysis
      • Close job
      • Lot/serial tracking finished goods
    • Job cycle – types
      • Manufacture to stock
      • Manufacture cross-referenced to Customer Order
    • Production schedule cycle – steps
      • Create production schedule and copy item routing/BOM
      • Modify PS routing/BOM
      • Set up PS releases
      • Paperwork and dispatch
      • Issue material to floorstock locations as appropriate
      • Report production to work centers
      • Report complete production
      • Run end of period costing procedure
      • Review variances
    • Modifying job/production schedule routing/BOM
    • Determine use of backflushing and/or manual reporting
    • Cross-referencing Purchase Orders
    • Job splitting
    • Job merging
    • Stopping  jobs/production schedules
    • Canceling jobs/production schedules

CRP – SCHEDULING/CAPACITY PLANNING

  • Set up parameter files
  • Set up master files
    • Departments
    • Shop Calendars
    • Holidays
    • Work Centers – Scheduling & Costing
    • Cells
    • Machine
    • Machine Maintenance
    • Determine scheduling methods – finite/infinite, backward/forward, move, queue
    • Determine scheduling method for each Work Center
    • Determine how to use scheduling priorities
      • Procedures to be considered and tested, including how-to, responsibility, frequency, reporting requirements
        • Use outputs to review Work Center capacity
          • Analyze job schedules and production schedules in terms of load on Work Center capacity
    • Use global priority setting and scheduling methods
    • Use individual priority setting and scheduling methods

CRP – COSTING

  • Determine costing method(s) to be used
  • Set up parameter files
    • Procedures to be considered and tested, including how-to, responsibility, frequency, reporting requirements
      • Determine cost type & method by item
      • Overhead rates
        • Basis – material, labor, machine
        • Valuation
        • Changes
        • Routine evaluation
    • Work Center costing
      • Labor and machine rates
      • Efficiency
      • Crew size
      • Period based accounts setup
      • Changes at Work Center
      • Changes to Job/Production Schedule routing
      • Routine evaluation
    • Employee Labor Rates
      • Valuation determination
      • Changes
      • Routine evaluation
    • Determine Current Unit Cost for purchased and manufactured items
    • Roll Current Unit Cost to Standard Unit Cost for standard cost items
    • Costing method changes to existing items, new items
    • Item cost reviews (cost comparison)
    • Product Code account determinations
    • Maintenance of BOM costs
      • Review of and utilities to update
      • Scrap factor determination
    • Purchase costing review
      • Differences in Purchase Order Plan Cost and Item Cost
      • Update of Purchased Current Unit Cost for vouchered cost
      • Freight cost analysis
    • Capitalization of landed costs
    • Job cost analysis
    • Period based costing analysis
    • Review of material transactions

CRP – COSTING (contd.)

  • Review of journal entries
    • Purchasing variances
    • Non-inventory item costs
    • Job costing variances
    • Period based costing variances
    • Sales and cost of sales
    • General Ledger analysis
      • Budget vs. Actual
      • Current vs. Prior Year
      • Departments

CRP – MRP

  • MRP Logic – methodology
  • Forecasting – data requirements
  • MPS – schedule, controls
  • Rough Cut Capacity Planning – capabilities, process
  • MRP Detail Information – ownership
  • MRP “Firm” Planned Orders – process, paperwork
  • Exception Messages – priority, control, paperwork
  • Regeneration vs. Net Change – when, how, who