SytelineMaster

This solution contains two options on processing returned items for rework, incorporating the returned item and costs into rework jobs for SL-ERP versions prior to SL8.

With the release of SL8 , job orders can be flagged rework josb by checking a Rework flag on the job order. This will allow recursive materials to be added to the job so the same material can be both the end item and a job material on the Rework job.

Resolution

Versions Prior to SyteLine 8 – Option 1:

1. Go to Job Orders and reopen the job by changing job status from "Complete" to "Released"

( For SL-ERP go to Production – Job Orders )
(For Symix go to Modules – Shop Floor Control – Job Orders)
2. Withdraw material returned by customer from inventory to the Job using a reversing job transaction.
NOTE: See solution 2003Syteline4586 for instructions on how to do a reversing job transaction.
3. Add Job Operation 999 (or some other operation number out of normal sequence on job) as the last Job Operation.
( SL-ERP and Symix go to View – Job Operations)
4. Post all materials and labor for rework process to the 999 operation.
(SL-ERP and Symix select Activities | Job Transactions for entry of labor transactions.)
( Select Activities | Job Transaction Posting to post labor to job.)
(Select Activities | Job Material Transactions to enter and post material issues to rework. )
5. Move reworked item into inventory and complete the job.

Note: If the original job is not in status of "History" and is in "Complete" status you can use this process.

Versions Prior to SyteLine 8 – Option 2

1. Create a new released job for the returned item that must be reworked.
(In SL-ERP go to Production | Job orders.)
( In Symix go to Modules | Shop Floor Control | Job Orders)
2. Enter a Miscellaneous Issue to remove the returned item from inventory with a reason code "REWORK". Your inventory quantities will be doubled for the item if this is not done since the return was received into inventory and the rework job is also received into inventory.
( SL-ERP , select Material | Inventory- Activities | Stockroom Activities | Miscellaneous Stockroom Issue.)
( Symix, select Modules | Material | Inventory | Activities | Stockroom Activities | Miscellaneous Stockroom Issue.)
3. Issue a material to the job that is not in the Item Master records which will be used to represent the returned item. You cannot add the parent item to the Job. This would be a recursive Bill of Material which is not valid in Symix/SL-ERP. Using an item not in the Item Master (for example, "rework-xxx" where xxx is the parent item) eliminates the recursive error message and allows you to enter an account numbers and costs associated with the returned item.
(SL-ERP and Symix, select Activities | Job Material Transactions.)
4. The Job BOM can be modified to account for the additional labor and materials required to complete the rework using Job Operations and Job Materials screens.

Note: If original job has been changed to "History" status, you will need to use this suggestion.

SyteLine 8

1. Enter a job for item to be reworked

2. Check the rework job flag on the job order header. This flags the job as a rework job.

3 Add a job material to the job that is the same as the job end item.

4. Issue the Material to the job. (This recursive job material cannot be flagged as backflushed and must be issued to the job using the Job Material Transactions form. If the material is serial tracked, the serial number status must be "In Inventory" so that it can be issued to the rework job. Once this material is issued to the job, the serial number status is "out of inventory". This serial number can then be used to move the end item back into inventory when the rework job is complete.

5. Continue processing the job adding additional material and labor as needed.

6. Perform a Job finish to move the end item to inventory.

Additional information concerning this new functionality:

MRP and APS planning will ignore any rework jobs with no defined routing\ bom structure and will not use the current bom structure for the end item on the rework job. Rework job end items are treated as planned receipts. Components that are same as job end item are not processed as a material requirement.

The Copy Routing/BOM utility will not create sub jobs if the "from" job is flagged as a rework job. Rework check boxes have been added to the Copy Routing/BOM utility for the From and To jobs.

The Job Pick list does not allow auto issue materials for rework jobs. This gives the user more control on issuing materials to the rework job.

Data collection allows the processing of recursive material on rework jobs.

The Job Split Utility sets the new job flag for rework job on the split job the same as the original job rework flag.

The Job Merge utility requires both jobs to have same setting for the rework job flag.

Rework jobs for lot and serial tracked items are supported.

No changes for Costing were implemented. The Rework Job WIP Cost is equal to the Job Cost less the recursive material cost. Standard Costed items will generate variances.

SOLUTION #1 – This is to be used if you are UPGRADING from a previous SL7.0x version, and applying a Service Pack.  This is NOT to be used if you are ONLY applying a Service Pack to the same SL7 version.

Before you begin the upgrade, please review your Client Configuration Names go to Start>Programs>MAPICS>Tools>Client Configuration Manager. The Syteline Client Configuration names will be listed on the left.  Each Syteline Client Configuration consists of xxxx_app and xxxx_forms ( see your Syteline Client Configuration Manager for the names of your databases)
**Always make a back up of your xxx_app and xxx_forms database prior to executing any Service Pack or Upgrade so that you have a restore point to go back to if you run into problems.
In this example the Syteline Client Configuration name prior to applying the Service Pack is called "Live". This Syteline ‘Live’ Configuration consists of Live_App and Live_Forms databases.
1. Uninstall your current version of SL7.0x
2. Install the new version of SL7.0x
3. To prepare for FormSync create a SQL backup of Live_forms database and restore the back up as the name temp_forms
4. Execute the SyteLine Configuration Wizard on the Utility Server and create a new temporary Client Configuration called "SP#Temp". (for example if you are installing SP09 for SL 7.03 then the naming convention of the configuration would be named ‘SP09Temp‘). This new configuration will consists of Live_app and temp_forms databases respectively.
5. Run the Upgrade – to affect all configurations.
6. Apply the Service Pack to the "SP#Temp" configuration, but do NOT apply the Service Pack to "Live".
7. So far Live_app and temp_forms have been upgraded and service packed, but Live_forms has only been upgraded, not Service Packed.
8. At this point you have a choice. You can either create a brand new Forms database and use the SyteLine Configuration Wizard to connect that forms db to the SP#Temp configuration, or you can proceed with the upgraded SP#Temp configuration as it is. In theory they should both now contain all the new Vendor level forms and objects. If you want to avoid any doubts of getting only the latest vendor versions of objects however, the safest option would be to create a brand new forms db.
Now you are ready to run FormSync.
Select the SOURCE: SP#Temp configuration (temp_forms db or brand new forms db)
Select the TARGET: Live configuration (live_forms db)
Click Synchronize.
EXAMPLE: SL 8.00.00 apply Service Pack 10
Source = SL8.00.10 forms database created after SP10 was applied to the Database Server (new forms database)
Target = SL8.00.00 – This is the live forms database that you have all our customizations located in (old forms database)
Notice, you NEVER apply the service pack to the "Live" configuration and therefore the live_forms database was never service packed in this process. FormSync applied the changes to Live_forms database. You can now run the "Live" configuration at the new service pack level.
To Verify the version of a Syteline Database
There is a table named ProductVersion that is updated when the Service Pack is applied. Open each database (app and forms) and select Tables, on the right hand window find the ProductVersion table. Right click on the ProductVersion table and select Open Table>Return all Rows. The version listed should match the service pack level you just installed.

Note

See Related Primus:
Form Sync Utility – Newest Version
FAQ – Form Sync
Form Sync Utility Configurations on two Servers

In Formsync under OPTIONS there are settings for handling form customizations and then a different setting for Global objects. It is important when doing a formsync to consider the options chosen for Global objects. Global objects include any scripts used on a form, PropertyClassExtentions, ComponentClasses, Validators, Variables and Strings. If you have made a change to any of these global objects they can affect more than just one form, so the choice to either keep or remove customizations in any global objects is VERY important. Wherever possible try to avoid making changes to standard SL scripts. Scripts can NOT be merged by formsync. You either have to accept the Vendor changes (and thereby remove all your customizations to the script) or you keep your version of the script and lose all the bug fixes that went into the vendor version of the script. As a rule, changing standard Global objects in Syteline is not recommended. If you must change a global object, then rather create a NEW global object with a copy of the original, and make changes to that. For instance, instead of making changes to the standard script named ‘EnableDisable’, rather copy the script, make your changes and name it ‘EnableDisable_mycompanyname’. Often you can accomplish the same things through Events and inline scripts or Events calling a custom stored procedure from a form using the SP! method.

Form Sync when Forms databases reside on two separate SQL Servers
Click Here for details:

If you ever need to change the site name in Syteline, here are steps you should follow,

1) Backup all your database.

2) Log off all users.

3) Run the “Change Site” utility.

4)  If Intranet Licensing has been implemented in this site, after running the Change Site Utility,  the Intranet License option on the Site’s Entities form must be reselected.

5) Regenerate replication triggers should also be ran if  replication had been enabled for the site.

If you have hundreds users, manually rebuilding the User/Module Authorization will be painful.  The below query will copy over the User/Module Authorization from source DB to target DB.  Just run it against your target DB.

insert  modulemembers (objecttype, objectname, modulename, originalmodulename, modulememberspec)
select objecttype, objectname, modulename, originalmodulename, modulememberspec
from [Your_Source_DB_name].[dbo].[modulemembers]
where objectname like ‘OS_%’

If you are a Syteline administrator, you will often need to refresh your Test/Training database with update-to-date Production database.

The most common way for copying DBs in SQL server is to use the backup/restore function.

1) Bring down all Infor service.

2) Backup your Syteline production database.

In SQL management studio, right click database name, task-> backup.

3) Restore it to Test/Training DB.

In SQL management studio, right click database name, task-> restore –> database.

Select source from device, give it the backup file location and file name.

Click Option.  Select the “Overwrite the existing database” option.  Provide the restore to DB

4) Once the restore process is done, right click on your Test/Training database name, go “Property –> File”.  Make sure the database owner is sa.  If it is not, change it to sa.

5) Run the below command to your Test/Training database.

ALTER DATABASE dbname SET TRUSTWORTHY ON

6) Bring back all Infor service.

7) Login to your Test/Training Syteline system.  Go to Site/Entities form, change the “Database Name” and “Form Database Name” to correct name.  Since this is a copy of your production database, it carries that Production DB name over, and you will need to change them to correct Test/Training DB name.

8) In a multi-site environment, there are a few more steps need to be completed.  First, if you are using intranet licensing, you may have problem login, even with sa account.  Need to do the following in SQL.

1.  Temporarily disable any replication for the Site Admin category in the database to prevent any later updates from replicating over to the production database. This is generally only an issue if the test, pilot, or development database is housed on the same server as production, but I would strongly recommend disabling replication under any circumstances to avoid any possible unexpected issues.

To disable replication for Site Admin, run the following in SQL against the database that has been copied over:

update rep_rule set disable_repl = 1 where category = ‘Site Admin’

2. With replication disabled in step 1, now update the site record to temporarily disable intranet licensing, which should allow the ‘sa’ user to login without error. To disable intranet licensing, run the following query in SQL:

update site set IntranetLicensing = 0

9) Now, you should be able to login with sa account.  Complete the above step 7) to update the DB name.  This need to be done for all sites.

10) If the Site name is differ between your production and pilot environment, you need to run the “Change Site Name” utility to correct the site name.

11) Finally, regen Replication Trigger.

12) Once all the updates are finished, replication triggers are regenerated,  you should be able to return to the Sites/Entities form and re-enable Intranet Licensing for all sites, and then do the same for Disable Replication in the Replication Rules form.

13) Update the license

Done.

Overview

There are four lead time fields in the Syteline item master: fixed, variable, paperwork and dock-to-stock. The fixed, paperwork and dock-to-stock leads are expressed in days and the variable is expressed in hours (run time per piece). For purchased items, they must be manually entered. For manufactured, they can be either manually entered or you can use the Lead Time Processor utility which populates the fixed and variable fields using the times in the item’s current routing .
In general, purchased and transferred items will have a fixed lead time and perhaps a paperwork and dock-to-stock but no variable. Manufactured items will typically have a fixed, variable and perhaps a paperwork but not a dock-to-stock. The following is an explanation of what functions in the system use lead times and how they are used. It is broken down by manufactured vs purchased items.
NOTE: All calculations of dates involving item master lead times are done using manufacturing days (M-days), not calendar days. For example, when the system deducts 10 days from an end date to arrive at a start date, it is actually counting back 10 M-days

Manufactured Items

The lead times for manufactured items are used to estimate job start dates and material requirement dates, which are essentially the same thing. That is, you need the material at the start of the job. The calculation used for manufactured items to arrive at a projected start date is the following. The .499 is added before the integer function (which rounds) is used so that it always rounds up to the next full day.
start date = end date – fixed lead – integer((var lead * qty / hrs per day) + .499)
The following functions use this calculation:
1) Job Creation
When you manually add a job, you must enter either the start or end date. Whichever you enter, the system arrives at the other using this calculation. When you use a system feature which creates a job, the end date defaults from the source record’s due date and the start is calculated using this formula.
Manually add a job
Firm a PLN to job from the MRP Detail Display
Firm MPS to job from the MPS screen
Add a production schedule release
X-ref and create a job from CO line item
X-ref and create an estimate job from an estimate line
X-ref and create job from a transfer order line item
X-ref and create job from project resource
2) MRP passing requirements
When a parent item has a PLN or and MPS receipt, the system passes it to the materials in the item’s current BOM to create PPLN and PMPS requirements for the materials. The date assigned to those requirements is calculated with the above formula using the MPS or PLN due date as the “end date”.
This calculation is also used to pass job requirements to the job’s BOM if the MRP parameter “Use Dynamic Lead Time” is No (or not checked). In that case, the item master lead times are deducted via the formula from the job’s “MRP End” date.
3) MRP Order Action report
The order action report reads through all planned orders and prints those that need to be released. The report deducts the item’s lead time from the planned order due date using the following calculation which differs from the one given above in that paperwork lead and dock-to-stock are both also deducted. The report prints the PLN if the resulting “Release Date” is less than the “Ending Date” entered on the option screen. The paperwork lead is included since that is time before the start of the job which must be accounted for when releasing planned orders. The dock-to-stock is included since the report uses the same calculation for purchased and manufactured items but while have no impact since it should be zero for manufactured items.
release date = PLN due date – fixed lead –
integer((var lead * PLN qty / avg hrs per day) + .499) –
dock-to-stock lead – paperwork lead.

Purchased Items

For purchased items, the lead times are used to either calculate a PO release date when starting from a due date or to calculate a PO due date when starting with release date. The specific functions which use lead times for purchased items in one way or another are the following:
1) MRP Order Action report to calculate Release Date
Used as described above for manufactured items. The variable lead is used in the calculation but will typically be zero for purchased items.
2) Firming a PLN from MRP
When you firm a planned order from the MRP detail display, the system deducts the item’s dock-to-stock lead time from the PLN due date to arrive at the PO line (or PO requisition line) due date. The PLN due date is the date you need to issue the material to the job so the dock-to-stock must be deducted from that date for the PO due date.
3) X-ref and create PO from a job material
Same logic as item 2 applies here. The dock-to-stock is deducted from the operation’s start date if not blank or the job’s start date if the operation’s is blank.
4) “Matl Chk FWD Sched” algorithm
Enabling the “Matl Chk FWD Sched” SFC parameter causes the scheduling routine to potentially move out the start date of operations if it determines that purchased, non-stocked materials cannot be available by the desired start date. If the material is not tied to a PO line item, determines when it can be available by adding the item’s lead times to the current date. (i.e. when can we have the material if ordered today?). If an item/vendor cross reference records exists for the item, the system uses the lead time from the number one ranked vendor. Otherwise, it uses item master lead times.
5) Calculating a “Release Date” displayed on reports
A handful of purchasing reports deduct the item’s fixed and paperwork lead times from the PO line due date and print the result in a “Release Date” column. The dock-to-stock is not deducted since it is assumed that it was already deducted from the true need date when arriving at the PO line due date. The reports which show this are the following:
PO Status
Purchase Requirements (if status is planned)
PO Requisition by Buyer
6) Calculating due date when manually adding PO
If you manually add a PO (or requisition) line and an item/vendor cross reference record exists for the item and the PO vendor, the default due date is calculated by adding the item vendor record’s lead time to the date listed below:
Regular PO line: adds item vendor lead to PO order date
Blanket PO release: adds item vendor lead to Rel Date entered
PO requisition: adds item vendor lead to Req Date
NOTE: Unlike the item master lead time field, the item vendor cross reference lead time should be expressed in calendar days, not manufacturing days. When used as described in this point and point 4 above, the item vendor lead is simply added to the one date to arrive at the other. That is, it does not count M-days as do the functions which utilize the item master lead times.
Transferred Items
For the item with a source of Transferred, the fixed and variable lead time fields are not used by the cross-site functionality. When the MRP module passes planned orders (PLNs) for a transferred item to the item’s supply site to become a TPLN requirement in that site, date assigned to that requirement is the due date of the PLN minus the Transit Time in the Inter-Site Parameter record. Also, when you firm the PLN into a transfer order the Transit time is also used for setting the line’s Schd Ship Date. The Schd Rcvd Date is set to the PLN’s due date and the Transit Time is deducted from the date to arrive at the Schd Ship Date.
However, the Order Action report does use the item master lead time to calculate the Release Date for PLNs. That release date is then used to determine if the PLN will display in the “Transfer Orders to be Firmed” section of the report. For that reason, it may be best to set the item master fixed lead time equal to the transit time from the item’s ship site for all transferred items.

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

Section B – General Ledger Setup

Section C – General Financial Setup

Section D – Accounts Payable Setup

Section E – Accounts Receivable Setup

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

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

Section F – Inventory Setup

Section G – Purchasing Setup

Section H – Sales/Order Entry Setup

Section I – Manufacturing Setup

Section J – Human Resources / Payroll Setup

K – Beginning Balances

L –Action Items

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

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 – 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