Frequently Asked Questions

Labels can be produced in both the Shipping solution and the Handheld solution-- what are the options for creating shipping labels, BOL's, and ASN's?

We have two methods for handling the creation of shipping labels and BOL's. The first is the SYSPRO based Shipping Solution and the second is our Handheld Solution. Both solutions can process an order, collect carton and pallet information, produce customer labels, and generate a BOL. Both solutions store the shipment information in the SYSPRO database in tables and the EDI ASN export knows how to read those tables to produce the required ASN's.

The SYSPRO based solution is great if all the cartons/pallets pass by fixed locations where a SYSPRO workstation can be set to collect the required information and produce the labels.

The Handheld solution is great if you need a more portable solution and/or wish to use the other warehousing functions the handheld solution can provide (receiving, transfer, stock take, WIP, etc.).

Of course the two solutions can work side by side where both mechanisms are desirable for different shipping methods. For example, we have customers who use the SYSPRO based shipping for small packages to take advantage of the Fedex/UPS/USPS labeling and scale interfaces and then use the handheld solution for larger palletized shipments. Of course, both solutions can do both types of shipments.

When a handheld device is initially configured, what scan code should be sent by the device at the end of a scan?

The scanner should only send either a "CR" or a "TAB" at the end of a scan.

Does the Handheld solution require that SYSPRO be running under SQL or can it run under C-ISAM?

The Handheld solution will work with either SYSPRO application database, SQL or C-ISAM.

Is there a way to run an exception report for a trading partner?

Some 810's are not transmitting for Lowe's.

What is the best way to confirm if ALL 810's transmitted?

One option is to write a report using the ArTrnSummary and EDIAcknowledgement tables keying on the invoice number. The EDIacknowledgement table has a date / time stamp of when the document was processed. It also will show when the acknowledgement was received.

I have a few questions regarding setting up handhelds to our network to get them to work with Syspro and Cadacus. How do most companies set up the handhelds on their network? Do they put them on the domain or just on the same network? And how do they connect with everything else?

Generally companies don't bother to connect the handhelds to the domain. They get connected to the WiFi so that they can access the network but that's about it. This is one of the reasons we use the IP address of the SYSPRO app server in the settings so we don't have to worry about name translations.

The only real requirement of the handhelds on the network is 1) having access to the Internet, and 2) being able to see port 1991 on the SYSPRO application server. Of course for diagnostics and support it's good for them to be able to access the network in general.

What versions of SYSPRO do Cadacus licenses work with?

Licenses issued by Cadacus will work across all supported versions of SYSPRO.

Other than the annual new license, when must a Cadacus license be changed?

If SYSPRO user counts change or company names change, a matching Cadacus license must be generated from the updated SYSPRO license.

More...

The main SYSPRO license, either for SQL or C-ISAM, is considered the "master", or "core" license for the main company. Cadacus licenses must have a precise match to whatever license is set for the main company in the SYSPRO license. Extra spaces, punctuation, or case mismatches matter when it comes to a precise match.

If a user is attempting to test using a company that is not included in the main SYSPRO license, like "Test Company 1" for example, then an updated license from SYSPRO that includes "Test Company 1" should be requested by the user to SYSPRO. After the user receives an updated license from SYSPRO, the user should send that updated license to Cadacus and request a matching Cadacus license.

What are the shorthand instructions for importing a Cadacus license?

Login to SYSPRO as an administrator, press Ctrl+R, run EDIREG, click "Import Cadacus SFS Licenses", browse/select the new Cadacus license file, then finish the prompts. For more detailed instructions, go here.

In terms of "licensed users", how does SYSPRO's licensing work?

SYSPRO uses a "concurrent license" approach-- no more than X users are allowed in the system at any one time.

What capability exists to identify "Dangerous Goods" to the carrier?

The following options may be used to identify Dangerous Goods items. Please note these options are available for FedEx, only, at this time.

Are licenses locked to a user/unit or can licenses float among several units/users?

The handhelds are licenses by "Active Unit". The "Unit" part refers to the mobile computer or Windows computer on which the software is installed. The "Active" part means that anywhere the software is installed that performs production transactions on a regular basis requires a license. A unit that is solely used for testing, training, or has the software installed as a backup to another unit does not need to licensed.

Also, the Handheld solution licensing is by device, not user or company. One device can be used with multiple companies on the same SYSPRO server.

o We're looking at the Motorolo MC9190-G, any better choices? How about the MC9200-G?

9190 – 256 ram/1gb rom – a/b/g wireless

9200 – 512 ram/2gb rom – a/b/g/n wireless

o There are also 28 key, 43 key, 53 key, 53-vtkey, 53-3270 key, 53-5250 key, etc.. devices, do you have a preferred keypad selection?

o There are many model numbers for short range/long range, any issues noted between the two that you can think of?

o Also there are different OS versions, which one do you recommend, windows mobile 6.5, CE6.5, CE7.0, Windows embedded 6.5, etc.

o Do you support both 1D and 2D barcodes? The devices that are 2D also support 1D backwards compatible.

The MC9190 was the top of the line until the 9200 came along. Either one will work great. The choice of keypad is completely up to you and depends on if you have numeric or alphanumeric stock codes. Unless you have a mainframe you have no need for the emulation keypads. Similar answer for short/long range. It depends on your warehouse and how you plan on using the funds. As for OS, I would recommend the latest OS. We have worked with all of them, but Windows Mobile/Embedded is easier to administer. Both 2d and 1d barcodes are supported. Operating systems supported are here .

Hopefully you are working with a reputable dealer who can help with the selection of the units and configuration. Our recommendation for a reputable dealer in handheld device/scanner hardware is here.

Other compatible devices: Intermec (by Honeywell) CK3x.

We are not on the latest version of Solutions for SYSPRO-- is it possible to take one program out of a newer release and install just that one program on an older release?

Loading an individual program into a system can be risky.

Depending on how up-to-date the rest of the EDI/Shipping solution is it could go fine or there be major data/program incompatibilities. SQL systems tend to mask some of the data incompatibilities and are easier to update than CISAM systems.

This is one of the reasons we recommend a simple test environment to load the program(s) and test. In the absence of a testbed we recommend waiting for the next full release.

In any case, we strongly recommend having a proven backup/restore and test plan.

When the Handhelds are configured to perform various validations against the input scanned data, such as serial number verification, for example, the scanners initially were scanning and processing the data very quickly. However, gradually, scanner processing time is slowing down. We have done timings on the round trips to the server from the handheld and we don't think that is the issue. What are some suggestions for how to maximize the the speed of the handheld devices?

One quick fix is to either delete the CHS-Shipping.sdf file from the \Data folder or to choose Actions->Remove->All from the Shipping Solution's menu. This will clear ALL shipments out of the local database so only do this when there are no active shipments in the handheld.

You can also do Actions->Remove->Posted(or Completed) to just remove the old shipments.

There are also these settings on the Options 1 tab of the handheld settings.

The first one controls how often to ask the operator to automatically clean the database. The second one says how old a shipment needs to be to be cleaned out. In the example above, every other day when the operator goes into the system, he will be asked if the database should be cleaned. If he replies "yes" to the prompt, then all posted shipments more then a day old will be removed.

This keeps the database small and fast.

When a shipment is canceled in the shipping system, does the UPS label get canceled and does UPS get that information? "Loop Billing" involves sending statements and charging for labels created but never picked-up, so it needs to be clear how canceled shipments affect labels.

If a shipment is canceled BEFORE the end-of-day (EOD), then the label will not get transmitted to UPS. If it is canceled after EOD then, yes, it will get transmitted. We are not aware of a procedure with UPS to cancel a label after EOD.

How can I get the date in the GS segment of a 997 to be in the format of YYYYMMDD. Currently the date is exporting as YYMMDD. I don't see any options in the 997 configuration pages for dates.

The format of all dates in the system is controlled by the version number of the document. If the version is 004010 or higher CCYYMMDD is used. Below that YYMMDD is used. The only exception is the ISA segment that always uses YYMMDD.

Is it possible to update a sales order using a "replace 850" (purpose code = "05")?

Here are the steps we used:

1. We imported the original 850,

2. We used a "replace 850" that should change the delivery date and should delete one of two items in the original sales order.

Instead, the system seems to interpret the "05" code as a "cancel" and it cancels the original sales order.

We need to be able to replace the sales order with the new purchase order if the sales order is less than status 8.

This can be accomplished by first cancelling the original sales order before creating a new one.

" Bartender " barcode-printing software is a popular choice, but what about " Wasp " barcode software? What makes Bartender different? Both Bartender and Wasp pull information from a databse.

You may use whatever software you wish. The feature of Bartender that we recommend is the Commander system. This is a service that runs on the server which takes a control file output by the labeling system and calls Bartender to produce the label. Any software that can read a CSV formatted file or similar can work with the shipping solution on the workstation. Only server based systems can work with the Handheld Solution. Even for the shipping solution, a server based solution has advantages in speed, configuration and manageability. We do not have enough experience with Wasp to know its full capabilities.

Specifically, when is it recommended to install the following Cadacus downloads?

EDI Tranlation File

Transoft ODBC UDD File

Cadacus WCF Service

Cacacus Support System

What criteria do we recommend using for installing these Cadacus downloads:

EDI Translation File - It is not normally needed, although it does not hurt to install the latest download; however, DO install this download if the existing translation file is out of date and a new document is needed to setup for EDI that is not in the current translation file.

Transoft ODBC UDD File - Install this download if SYSPRO is C-ISAM based and the ODBC programs are used to access the data outside of SYSPRO

WCF Service – This download is used with the Cadacus Handheld Solution and is rarely changed and consequently is rarely needed after the initial Handheld installation.

Support System – If this is currently being used, then the latest download should be installed.

After installing the 8/1/2012 release of the Cadacus Shipping Solution, the dispatch notes are not showing up in the sales order query. Suggestions?

The 8/1/2012 release of the shipping solution has switched to using the SYSPRO business objects for most work involving the creation of dispatch notes. We have noticed one problem with the dispatch notes not showing up in the sales order query which we are working on resolving. The cancellation of dispatch notes requires an updated business object that hopefully will be in 6.1 SP1 port 27. Due to the error in the dispatch note, cancellation of dispatches will not be supported in any earlier SYSPRO versions.

We are looking into why the dispatch note business object is not updating the Sales orders.

Client wants to default the "Purchase Order Check" settings to Warning. When the default is set to "Warn if duplicate PO number found" the Warning radial button is not highlighted the next time you go in to run an import, it's still set to Yes. Is there a corresponding setting in Sales Orders that is set, or needs to be set to change this? The only thing I found was the in SO Set Up > General 1 > Validation of duplicate customer p/order numbers. But even when I select Warn under By Customer or By Company, the Warning is not defaulted on the process imports window.

Any ideas on why the default isn't changing?

The setting you are referring to is only used when the 850 import is called from the Input Sort program, not if you run the import directly. There is no setting at this time to allow a global change to the default purchase order setting.

I used the EDI Backup/Restore module today, having it also backup my Data/Work folders...

Since it only backed up "C-ISAM data", one wonders whether a "Restore" will restore do something magic for the SQL Companies I have?

The function is a backup only and does not backup any of the SQL data. SQL data must be backed up for another means and restores are done by hand.

What does Cadacus recommend?

Cadacus Solutions for SYSPRO recommends the following:

"SYSPRO 7 Update 1"

For more information on upgrades, please see the alerts here.

And if so, how do Cadacus Solutions work with UCC-128?

The more specific question is this, "Can the Shipping Solution produce serialized container barcode labels?" and the answer is "yes".

UCC-128 is a barcode format, not a specific barcode entity (this is commonly confused). The Serialized Shipment Container Code or SSCC-18 is a specific serial number applied in barcode form (using the UCC-128 format) to a label attached to a pallet or package. The serial number and the information about the package or pallet is then transmitted via the EDI 856 document to the customer.

That’s the long answer. The short answer is “YES”.

Or are the licensed restricted per company?

We generally provide licenses for all companies that we know about based on the information you sent to us when you initially licensed the handhelds. If you need to use your handhelds with multiple companies that are not registered with Cadacus, please send us your SYSPRO company XML license file and we will be happy to generate licenses for all the companies.

What devices are supported?

Please go here, for the latest supported handheld/tablet devices.

To keep the handhelds optimized for efficiency, I need to clear locally stored data periodically. How do I do this with the Handheld Solution?

Periodically, stored data may be removed from the Handheld devices by the following:

1. Select the "Shipping" button on the Handheld main menu

2. Select Actions > Remove

3. Select one of the options (Posted, Completed, Saved, New, All)

Also, to maintain a minimum of stored data on the handhelds on an ongoing basis, we recommend setting the appropriate cleanse "day" options in the "Options 1" tab under the Handheld Configurations in the Cross-Reference to "Request data cleanse" and "Clean posted entries". Both options should be set to at least "1". Click here to see the detailed documentation.

Another option related to data storage is to insert SD cards into the handhelds and move the local handheld database files to the SD cards. Step-by-step instructions for doing that are here.

We have a number of Handhelds setup-- some communicate with the Cadacus WCF Service, and some do not. What are the recommended troubleshooting steps?

This section has been moved to here.