Response 9x Manifest_CPS.doc ____________________________________________________________________________________ CoLinear Systems, Inc. 1 of 23 update: 07/19/2011 Support email: [email protected]http://support.colinear.com/doc Response Manifest Interface using CPS MANIFEST Software (Harveysoft) o You must be on at least Response 8x build #3043 to configure CPS Manifest software to work with Response o Nov 2007: This CPS Optional AVM module is NOT Supported by Response at this time Per CPS NEW for November, 2007, the Address Verification Module (AVM) - With Harvey Software's CPS you can have address verification three ways with CPS! You can use the Standard CPS City, State and ZIP verification that has saved shippers money for over 10 years now. CPS shippers that use Endicia Internet Postage can use Endicia Address Verification. Or, you get CASS level address certification and automatic residential and commercial service correction by adding the optional Address Verification Module (AVM). CPS gives you unequalled choices to help get your packages to the right location at the right price. PART I: The files you need and what to do with them: Download the CPS.zip file using the link here: http://support.colinear.com/doc/Optional%20Modules/Manifest_cps.zip the zip file contains: Manifest_General.doc Manifest_CPS.doc (THIS document) Manifest_ODBC_Interface.doc Manifest_CPS_ratebot_cls.doc Cpsr4w.sql Cpsdivision.vd7 (for multi-company users only) (the are no .imm or .spe files for the Harvey interface, it is 100% ODBC) 1. Manifest_General.doc Read over this. It applies to ALL manifest options. 2. Manifest_CPS.doc (THIS document) To simplify the information in Manifest_General.doc, this will help you with what you need to enter in R4W for your Harvey Manifest product. You should still review all info in 'manifest_general .doc' for information not included here. 3. Manifest_ODBC_Interface.doc
23
Embed
Response Manifest Interface using CPS MANIFEST Software ...
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Response Manifest Interface using CPS MANIFEST Software
(Harveysoft)
o You must be on at least Response 8x build #3043 to configure CPS Manifest
software to work with Response o Nov 2007: This CPS Optional AVM module is NOT Supported by Response at this
time Per CPS NEW for November, 2007, the Address Verification Module (AVM) - With Harvey Software's CPS you can have address verification three ways with CPS! You can use the Standard CPS City, State and ZIP verification that has saved shippers money for over 10 years now. CPS shippers that use Endicia Internet Postage can use Endicia Address Verification. Or, you get CASS level address certification and automatic residential and commercial service correction by adding the optional Address Verification Module (AVM). CPS gives you unequalled choices to help get your packages to the right location at the right price.
You will need to set up an ODBC Source for Harvey. You will be using ODBC to move
information to Harvey from Response and From Harvey back to Response tables. You
must review this document for more information
4. Cpsdivision.vd7 only used for true multi-company users who ALSO SHARE a single
CPS manifest station between all companies. If you’re not, skip to #5: This is a special case, and will be considered a billable project. This is because a special cpsr4w SQL view and trigger must be created for the companie(s) they want to share the manifest. We will remove mimport/mexport.int from the 00x folders so their mimport/mexport point to r4w_primary, create special cpsr4w view in r4w_primary (with custom SQL). This also requires setting sysfile.x10 in each division to a separate division indicator of A, B, C, D, etc. This cannot be deployed "unattended", contact [email protected] for more information.
This puts the trigger on the MIMPORT table. A "trigger" is function of a MS SQL
database. It can execute on record creation, change or delete. In this case when the
record is created, if mimport.shipper_comment not equal blank, the trigger
executes. Information on MS SQL triggers is beyond the scope of this document.
To install the trigger on MIMPORT, do the following:
copy cpsdivision.vd7 to \r4w\data and double-click on it. (see Q&A at end of this
document IF you need to uninstall this trigger)
*! see more at step 10, page 14… For the mapping back to Response, map
CUSTID to MIMPORT.SHIPPER_COMMENT.
The trigger will parse this information out to shipto_id and division_id and
remove the data from shipper_comment. Shipto_id and Division_id should NOT
be mapped to directly in this setup.
5. Memo for those who are not a multi-company or are using separate manifest
installations for each company:
MIMPORT.int and MEXPORT.int in your \r4w\001\ folder need to point to
R4W_001 if it exists. They should by default already do this.
If you are NOT multi-company, DO NOT map the DIVISION_ID (R4W) to
DEPARTMENT (CPS) on the write tab for the ODBC setup. CPS documents
that you can use/customize the department field to track which department you
are shipping with. Colinear documents that you use this field for multi-division
setup. (repeated on page 14)
6. CPSR4W.SQL
To create a SQL view you will need later at CPS setup, do this only one time:
Get your *CPSR4W.sql file from the CPSR4W.zip. You can also download from
here: http://support.colinear.com/download/cpsr4w.sql , copy this to your
\r4w\data folder. Open the file and copy/past the text into the Response Query
Executor and execute. This will create the ODBC interface view (the SQL
A. If you are NOT a multi-division company, DO NOT map the DIVISION_ID (R4W) to
DEPARTMENT (CPS) on the write tab for the ODBC setup. CPS documents that you
can use/customize the department field to track which department you are shipping with.
Colinear documents that you use this field for multi-division setup.
B. All users: Do not map the PHONE field on the read tab for the ODBC setup. By
default, if the field is populated, it will print on the UPS labels. I doubt that customers
will appreciate their phone # on their ship label.
C: All users: Under the "Advanced" setting in the "read" setup for CPS, select the
checkbox which says "use first record found if multiples" or something along similar.
Without this option on you will have trouble getting CPS to see “second” shipments on
an order even though the second MEXPORT record is created. Configuring CPS to the "use first record if multiple" check box. maybe all the magic you need. Without explaining all the technical details, that setting isn't about suppressing multiple shiptos or second shipment on an order. It's about suppressing a smoke and mirror effect the coding in our CPS_R4W view might cause. This is due to the way we're linking several other tables into the CPS_R4W view after we find the mexport record. Mexport is the key piece driving the VIEW, but then Response finds pieces of data from other tables like lpicktrn, picbatch, shipto, etc to make all the magic work. Sometimes those create a mirror effect in the view and CPS will "see" two and balk. This is more likely to happen when a second shipment is created. So that's the reason behind using the checkbox. It's not suppressing legitimate mexport data from a backorder shipment or multiple shiptos. Those are layman's terms as Scott explained to me. I hope this makes sense for you because tech support staff typically cannot decipher the actual code in the SQL view. Bottom line is, that setting alone may resolve your issues with the backorders, without having to keep your mexport table purged
10. The Write Tab is configured differently. The Data Source Name is the NAME you
defined and may not be the exact name in the picture below. You must be able to Select
our TABLE “MIMPORT” as the source table for CPS Write Tab. The fieldnames here
are different so you must be careful to map them across exactly as indicated below and
only those fields as noted.
If you are NOT multi-company, DO NOT map the DIVISION_ID (R4W) to
DEPARTMENT (CPS) on the write tab for the ODBC setup. CPS documents that
you can use/customize the department field to track which department you are
shipping with. Colinear documents that you use this field for multi-division setup