Corrected in v6.5. The shipping process in SBT is halted if a SOC kit is
shipped and a subsequent item has a zero cost and a zero price.
Workaround - Enter the actual cost for the item or a token one cent.
Problems defining SOC as a custom application in SBT
installing SBT Pro v6.0 you must install SBT service pack 3. This can be
downloaded from the SBT web site. After installing service pack 3,
follow the instructions on page 13 in the SOC Users Guide with
the following changes.
Under Part Two replace steps 1
- 4 with:
1. Select Start
2. Select Run
3. Enter the path to the SBT program
4. Type sbtinstw
5. Select OK to start the installation
6. At the Warning Message - select Proceed
sure the WorkShop v6.0A or greater is in the CD drive from which you are
performing this installation. You will need the CD to be present
starting on Step 7.
steps. Please feel free to contact Tech Support with any questions.
Corrected in v6.5A - SOC v6.0A and v6.0B are not active on the SBT Pro
6.0 menu. Solution - SBT Pro6 requires that any new
modules added to the system now be contained in a separate subdirectory. Create a subdirectory, called SC, in the Pro v6.0 directory. Copy the four SC files
(SC.add, SC.FPT, sc.FXP, sc_hook.FXP) from the Pro6 directory to the SC
When viewing the directory the SC folder should appear on the same level
with AP, AR, GL, etc. Be sure to copy, not move, the SC files, they need
be in the root directory as well as in the SC folder.
Corrected in v6.5A -
An error occurs if a new sales order
is created by copying an old one and then a line item is immediately
the new sales order after the copy process and before
doing any editing.
The hooks for
the SOC in Build 708 of SBT Pro Series 5.0 are not functional. TIW has
included a modified SOPOST.FXP on the CD containing the WorkShop v3.2B
release. This file can be found under WS32SOC\SBT50MOD. It may be used to
replace your unmodified SOPOST.FXP. We have also included a file called CHANGE.TXT
which has the code instructions to make the changes yourself in the event you have made
modifications to your SOPOST file and cannot use the one we supply.
The SOC does
not support SBT Pro Series multi currency. WorkShop v3.2B and
greater contains the enhancements required to support multi
The link to a
kit/configuration is broken if you delete a line item from an order that is being COPIED
to a new sales order and SBT is forced to renumber the line items and one or more of those
renumbered line items is a kit or is configurable. An easy work
around is to copy the order to a new sales order, save, then delete the line item. You may
field fix the problem if you wish since the line renumbering takes place in the SBT code.
Change the code to resynch the line number with the kit/configuration in the SALESMTL and
SALESCFG tables during the copy process. A correction will be made by TIW in a future
Build 707 of
SBT Pro Series 5.0 is missing some updated hooks for the TIW SOC. SBT has posted
a patch for the SOPOST.PRG on the web that may be downloaded at
(No longer available 08/30/10) Please note that your reseller will need to download
this patch as this is in a reserved section of the SBT home page.
Under some conditions allocations are
being incorrectly maintained in SBT when the SOC kitting functions is used. The problem
affects both the 16 bit and 32 bit SOC products. The problem occurs under the following
- Sales orders are shipped using the batch method.
- There is insufficient inventory or any one component to meet all the demand - or - the
sales orders are partially shipped.
This has been corrected in WorkShop v3.2A and greater. A field fix is can be done by adding a single line of code to the SOC hook in the
SBT soshpp.prg as follows:
(15) File: soshpp.prg Main program 1 TIW addition
* Check for payment records
IF a_tmpf1->sotype = "$"
*-- Skip to next record in temporary file
IF a_tmpf1->shipqty <> 0
<----- (Add this line here)
DO sc_hook WITH
* If anything shipped for this line
If a_tmpf1->shipqty <> 0
allocation balances - A good portion of incorrect
allocations are automatically corrected when an order is closed.
TIW Development developed an utility to correct any remaining allocation balances.
The name of the file is SOUTIL2.FXP, size
2K, dated 10/01/99. Copy the file to the WorkShop program directory.
Start WorkShop and go to the access FoxPro command line. Type in DO
SOUTIL2. When it is done you are returned to the command line. Type Exit
and leave. Note: This utility does not work
Problem occurs when you enter a
sales order that has two or more line items that contain kits. The kits are configured and
use the same generic item number. The configuration is different for each kit. When the
pick list for the sales order is printed the like item numbers are summed and only the
components for the first kit are listed.
The SOC places
the requirements for each kit into the SBT memo field. When the SBT pick list is printed
and the like item numbers are summed, only the first memo field is printed. TIW is working
with SBT to add an option to the pick list report that allows you to print the line items
individually rather than summed. For the present, the
Net Trial Requirements
report in the BOM Module may be used if a pick list is required. Run the report for the
kit item number with the same configuration. Set the Requirements option
to Gross. This will produce a list that can be used in place of the pick
You ship an order for two
kits. The kit contains five total components. On the Sale Order>Print
Transactions Report>Customer POs report you notice that the Open Qty
is correctly showing two but the Shipped Qty is showing ten.
This particular report displays the
sum of the number of kits shipped times the sum of the number of components that make up
the kits ( 2 x 5 = 10). It is a function of this report and your actual inventory
transactions are correct. TIW has determined that the SBT report contains a logic error.
SBT has corrected the issue.