Archives

Archive by SytelineMaster

In the SyteLine database you will find Temporary tables that start with: tt_* tmp_* tmp_snapshot_* tmp_staging_* There are others that end with: _ii _dd _all. The first six are various forms of permanent "temporary" tables, used for temporary processing of data. The *_all tables are used to remove the requirement that another site must be […]

Jul 6th, 2014 | Filed under Application, Development

Below are some sample ways of constructing email body in Syteline event system. BODY( SUBSTITUTE(“We have a new customer. Please see customer number {0} for customer: {1}.”, FP(“custNum”), FP(“custName”) ) ) This uses the common SUBSTITUTE function and use object property as parameter value. BODY( IF( P(“POCost”) > 10000, GC(StdApprovalMessageBody), GC(StdRejectionMessageBody) ) ) Notice the […]

May 24th, 2014 | Filed under Development

Sometimes a user will accidentally type in a wrong number in the starting check number in A/P check printing and posting. If that check number is higher than the last check number used, the system will prompt to void all the check numbers in between. If that prompt is answered "ok", this will result in […]

Apr 27th, 2014 | Filed under Application, Implementation, Progress, SQL

Syteline multi-site supports centralized AR payment process.  Here are the basic set-up steps 1.  Site Groups Create a site group that contains all sites that will be sharing cross-site A/R Payments NOTE:  All sites within the group must have the same domestic currency 2.  Replication Rules Set up Replication Rule for category A/R for each […]

Apr 26th, 2014 | Filed under Application, Implementation

To repair an item that you have received through a return material authorization (RMA), you create a rework job order (or estimate job order). The rework order’s bill of material includes the item as the end item and as a component. This recursive BOM structure is allowed only on a bill of material for a […]

Apr 9th, 2014 | Filed under Application, Implementation

 Order Types The ORDTYPE field in the ORDER table distinguishes different types of orders. The value in this field affects the database data you need to retrieve for various APS functions. 10 reserved by the Scheduler to identify planned manufacturing orders 50 supply delivery (reserved for internal use) 100 released, scheduled work order 200 customer […]

Apr 8th, 2014 | Filed under Application, Implementation
Tags:

ITEM MAINTENANCE WINDOW – GENERAL TAB   Cost Type: item.cost Cost Method: item.cost-method (Standard) Unit Cost: item.unit-cost Current Unit Cost: item.cur-u-cost Notes: The Cost Type can be either Actual or Standard with the stored value being "A" or "S". The Cost Method and the associated field values can be (L)IFO, (F)IFO, (A)verage, (S)pecific, (C)Standard. The […]

Apr 3rd, 2014 | Filed under Application, Implementation

Under the BackgroundColor property, use this expression =IIF(RunningValue(Fields!grn_num.Value,countDistinct,Nothing) mod 2,"Silver","Transparent")

Feb 25th, 2014 | Filed under Development

In general Scheduler should be run first as input to the APS Planning run.  The reason for this is based upon the fact that the Scheduler is in charge of Released Jobs by default and if there are any new Release Jobs since the last planning run, you want the Scheduler to have scheduled them.  […]

Feb 20th, 2014 | Filed under Application, Implementation

If someone accidentally closes a job that was in process, all of the costs that were in WIP will be written off to the item’s inventory adjustment account if actual-costed or to variance accounts if standard-costed and the WIP buckets on the job will be cleared. These WIP-clearing entries will be written to the SF […]

Feb 12th, 2014 | Filed under Application, Implementation