V8 to Prism (V8ToPrism.exe)
This topic explains how to migrate a Retail Pro 8 system to Prism 1.14.7 or 2.0 using the following process and tools:
- Export data from Retail Pro 8 Main using V8ToPrism.exe
- Import the data into a new Prism subsidiary using ExportImportResources.exe.
The data that is exported from Retail Pro 8 includes:
- Sales documents (excluding customer, layaway, and special orders)
- Supporting dictionary data
Download V8ToPrism.exe and ExportImportResources.exe
The V8ToPrism.exe and ExportImportResources.exe programs are available on the "Prism Downloads" page of my.retailpro.com.
For importing data into default empty Prism Subsidiary 1 (for a different subsidiary, the steps will be slightly different):
Step 1 - Prepare Data for Export
a) Replicate all data from remotes to the RP8 main.
b) Use a tool like DVS.exe to clean data.
c) Run Reconstruct after the data is clean.
d) Make a backup of the data and history files.
Step 2 - Export Data from RP 8
a) Launch V8ToPrism.exe. Set the path to RP8 history and datafiles
b) Click the Prism button to access Prism settings. Click Prepare Subsidiary 1.
c) Change the Subsidiary No and Subsidiary Name.
d) Click Read Lists. Click Read Data.
e) Click OK to return to the main screen. Click Process. The RP8 data is exported as a set of .csv files to the …\V8ToPrism\Prism folder.
Step 3 - Import Data into Prism
a) Use the right-click "Run as Administrator" option to launch ExportImportResources.exe. Click the "RIL to Prism replication CSV tool" button.
b) Navigate to the .csv files. Clear the Zip checkbox. Select the files and click Open.
c) Click Import. When the process is finished, click OK.
Step 4 - Finish Steps
a) (optional) Go back to the V8ToPrism.exe tool and click "Finish Subsidiary 1."
b) In Prism, configure Subsidiary settings for currency, country, price levels, etc.
c) Do a full PI to verify quantities.
Considerations before you begin
Does V8ToPrism.exe have access to the Prism system?
To ensure RP8 data is exported successfully, the utility requires certain information about the Prism server into which the data will be imported and instructions for handling certain differences in database formats, fields and program logic. Ideally, the Prism server into which the files will be imported is on the same machine as the RP8 Main and V8ToPrism.exe (or available via a mapped network drive). If the tool has access to Prism, information about the Prism server can be pulled directly from Prism. If the tool does not have access to the Prism system, the user must obtain the information from the Prism system and then edit the V8ToPrism.ini file.
As a workaround, if the RP8 and Prism systems do not have a connection available, you can copy the v8ToPrism.exe tool to the Prism system, run it to collect the needed Prism data (using the Read Lists and Read Data buttons), and then copy the V8toPrism.ini file and the tool back to the Retail Pro 8 system. You can then run the tool and process out using the information contained in the v8ToPrism.ini file.
Does the Prism system have existing subsidiaries?
The import can only be run once and only into a NEW subsidiary that you specify when configuring the V8toPrism.exe tool (you must specify the import subsidiary BEFORE exporting the V8 data). Ideally, the Prism system is new and does not have any data in any existing subsidiaries. In such a case, the data can be imported the default empty Subsidiary 1. However, this may not always be the case; therefore, the tool enables you to specify the subsidiary number into which the data will be imported. The subsidiary must be new (i.e., never had data entered). During the export process, the tool checks if the sub you are trying to use exists in Prism. If the subsidiary number is being used, a message explains that the sub number is already taken.
There may be data differences due to different technologies
Because of underlying differences in technology between Retail Pro 8 and Retail Pro Prism, the export/import process may result in minor differences in data between the two systems. Additionally, given the differences in the way tenders are handled on transactions, tender totals may be different for historical sales transactions brought in from Retail Pro 8. These differences are typically a result of a ‘penny rounding' issues. This same ‘penny rounding' issue can also result in stored gift card balances being off. These are known issues and will not be addressed further.
Prepare Data for Export
Prepare Retail Pro 8 data for export by doing the following:
1. Replicate all data from remotes to the Retail Pro 8 Main.
2. Clean the Retail Pro 8 data. Cleaning the data will reduce the number of records and enable export to go faster. Cleaning will also ensure that the limited set of records being exported do not have any conflicting SIDs or other problems. You can use the Retail Pro 8 tool DVS.exe to help with the cleaning.
3. Run the Retail Pro 8 tool Reconstruct.exe to recreate any indexes that may have changed.
4. Backup the data and history files that will be exported.
Replicate all Data to Retail Pro 8 Main
Using the Retail Pro 8 polling programs, replicate all data to the Retail Pro 8 Main station before running the V8ToPrism.exe tool.
1. Process out at Remotes: The data typically includes receipts for the day's sales, vouchers for merchandise received, slips for merchandise transfers, plus any sales orders and customers added or changed that day.
2. Run Exchange at Remotes: The stations send the prepared data files and pick up any waiting files.
3. Process in at Main: The Main station processes in the data it has just received. This updates inventory, history, customers, and other data.
Clean Retail Pro 8 Data
Before exporting Retail Pro 8 data, make sure it is "clean." Refer to the following checklist to help you clean the data before export. You can use the DVS.exe tool to help with the data cleaning. Complete for each Retail Pro 8 Main.
1. How many years of data will be migrated from Retail Pro 8 to Prism? Limit the data cleaning process to this amount of data. Two years or less will take less time to clean, less time to import into Prism. More than 2 years - will take longer to clean, longer to import into Prism and increase size of Prism database.
2. What inventory fields are being used to define an item? Item definition is needed for data cleaning purposes.
3. What inventory fields are being used to define a style? Style definition is needed for data cleaning purposes.
4. If there are multiple Retail Pro 8 Main stations, are there inventory items that exist across all Mains? Items shared across multiple RP 8 Main stations must have the same UPC. If yes, do they have the same UPCs? If no, assign the same UPCs and regenerate SIDs based on UPC. If yes, regenerate SIDs based on UPC.
5. Are UPCs reused by different inventory items? Prism will not allow the import of items (whether active or inactive) with the same UPC code. If yes, obtain a list and decide how it should be handled. Option 1: Match all history to the current Inventory Item's UPC. Option 2: Delete the UPC from all historical documents. Option 3: Change the UPC code and regenerate SIDS based on UPC.
6. Are there inventory items that have been entered into the system multiple times (with differing definitions) that are really the same item? If yes, get a list from the retailer. Then systematically correct store qty, delete "extra" items and synchronize history for each error
7. Is Item Number being used for barcode generation and item lookup? If yes, what approach should be taken in Prism? Option 1: Plan to use UPC for Prism lookup. Option 2: Plan to use ALU for Prism lookup. With either option, you will need to recreate tag designs in Prism to include UPC or ALU.
8. Do department codes need to be reorganized/restructured/merged? If so, obtain requirements and do it in Retail Pro 8.
9. Are there any pending/held documents? These documents cannot be imported into Prism. If yes, you will need to discard or update those documents.
10. Are there customer records that have been entered into the system multiple times (with differing definitions) that are really the same customer? If yes, use DVS Customer Revision to merge these customers in Retail Pro 8.
11. Are there any duplicate documents (same Document #, Document Type, Store/Station, Date/Time?) It is much easier fix duplicate documents in Retail Pro 8. If yes, assign new SID to duplicate documents and inactivate.
Use DVS Tool to clean data
Retail Pro 8 users can use the DVS.exe tool to perform some of the data cleaning. DVS includes tools for selectively removing unneeded customer records and resolving conflicting SIDs
DVS.exe is launched from the Tools menu on the Retail Pro 8 main screen.
Purge unneeded Customers
DVS can assist you in maintaining your customer database by purging selected customer records from your Retail Pro customer file. Using the filter provided, you can select customers for deletion based on their entries in any field(s), including Last Sale Date, Info 1 and Info 2, and the eight user-defined fields.
To access options for purging customers, in DVS, select Maintenance > Purge Customers.
SIDS and SID discrepancies
Each inventory item, style, customer, and document can be identified by its own unique SID. Each can also be described by the entries recorded in its identifying data fields. These identifying fields make up the definition for that item, style, customer, or document. For example, item definitions always include Item #, DCS, VC, style description field(s), Attribute, and Size; a document defini¬tion is made up of several fields (document #, document type, date, time, store, and station).
There should always be a one-to-one correspondence between a SID and its definition. Each item definition should occur just once in inventory and should have just one SID. Each Item SID should be assigned to just one inventory row. Each time an item is listed on a document, the same Item SID and definition from inventory should be recorded on the document. A similar one-to-one relationship should exist between styles and Style SIDs, between customers and Customer SIDs, and between documents and Document SIDs. Any deviation from this one-to-one relationship constitutes a discrepancy that should be resolved to ensure accurate reporting.
DVS can locate and resolve numerous types of discrepancies. For example, it can identify duplicated documents (duplicate document SIDs) or can spotlight a Style SID that is associated with different definitions in inventory and history.
Click the Advanced button to access options for dealing with SIDS and SID discrepancies
Reconstruct.exe is used to validate Retail Pro data files, to repair some types of data corruption, to rebuild file indexes, and to perform other file reconstruction procedures. It's a good idea to run Reconstruct.exe to make sure the RP 8 indexes are up to date.
To launch the tool, from the Retail Pro 8 Tools menu, select Reconstruct.
Backup Retail Pro 8 Data
As a final preparation step, make a complete backup of your Retail Pro 8 History and Data files before beginning the export. Copy the files in the \Retail\RPro folder to a secure location in the cloud or to removable media (e.g., attached disk storage).
Export Data using V8ToPrism.exe
The V8ToPrism.exe tool needs certain information about the Prism system into which data will be imported. If there is a connection with the Prism system, the data can be pulled. If there is no connection, the V8ToPrism.ini file must be edited to enter the information. The following steps assume there is a connection to the Prism system and that data will be imported into the empty default Sub 1 of a new Prism system.
1. At the Retail Pro 8 Main, launch V8ToPrism.exe.
2. Enter path to the RP8 data and history files (Default=C:\Retail\RPro
3. Click the Prism button to define Prism settings. Click Prepare Subsidiary 1.
4. Change Subsidiary No from 2 to 1.
5. Change Subsidiary Name from Sub2 to Sub1 or whatever name you want to use for Sub 1. A prompt asks if you want to change the SBS SID as well. Click Yes.
6. Click Read Lists.
7. Click Read Data.
8. Click OK to return to the main screen. Click Process. The RP8 data is processed out for SBS 1.
Obtain the V8ToPrism.exe tool from Retail Pro Technical Support. Copy the tool to the Retail Pro 8 Main.
Double-click the V8ToPrism.exe file. The V8ToPrism.ini file is created automatically the first time you launch the tool.
Path to RP 8 data and history files
The main screen of the V8ToPrism.exe tool has fields for entering the path to the RP8 data and history files that you want to export. By default, these files are saved to the …\Retail\Rpro folder (e.g., C:\Retail\Rpro).
About the Data and History files
The files stored in the "Path to Data" and "Path to History" are the sales, inventory, customers, etc., that will be exported by the V8toPrism.exe tool. For each data class-subclass combination, there is a dedicated file. For example, subclasses in the inventory data class include data files such as INVN.DAT, MULTI.DAT, and PRICE.DAT. The document history files are stored in a similar set of files except there is a separate file for each month for each doc type. These have names such as SA######.DAT, PO######.DAT, SO######.DAT, ME######.DAT, RC######.DAT, TO######.DAT where ###### is the month and year.
Older document .DAT file are often archived. Make sure all the Retail Pro 8 data and history files for export are in the specified path.
Prepare Subsidiary 1
You must enter information about the Prism system into which the RP8 data will be imported. This information is needed to resolve differences in the RP 8 and Prism data structures. If the V8ToPrism.exe tool has a connection to the Prism system (e.g., if both are on the same machine), information about the Prism system can be pulled. If a connection to the Prism system is not available, the V8ToPrism.ini file must be edited. (Note: Some options are only available in the V8ToPrism.ini file.)
When a user first accesses the "Get Data from Prism" screen, a few default settings are entered, but most fields are blank. The default Db Name and Db Type are entered. The Subsidiary No is set to "2" (more on this later), the Subsidiary Name is set to Sub2 and a random Subsidiary SID is assigned. The default Country Code and Currency Code are set to USA and USD, respectively.
Click Prepare Subsidiary 1. The tool reaches out to the Prism system and changes the default SBS 001 to SBS 002 and makes a few other behind-the-scenes changes that are needed. This frees up SBS 001 in Prism so the data can be imported into SBS 001.
You will see a confirmation when it is finished. Click OK.
Next, on the "Get Data from Prism" screen, change Subsidiary No from 2 to 1. Change Subsidiary Name from Sub2 to Sub1 or whatever name you want to use for Sub 1. A prompt asks if you want to change the SBS SID as well. Click Yes.
Note: The preceding instructions assume the target Prism is a new system. If the Prism system has a single existing subsidiary with data entered, that data is most likely in Sub 1, so leaving the Subsidiary No at "2" is the right choice. If the Prism system has existing subsidiaries (e.g., 001 and 002), set the Subsidiary No to the next available SBS number. The utility will bring the data into the database and create the chosen SBS with all required system information (fulfilling the requirement that the data import be into a NEW subsidiary).
If the tool is being run is on the same machine as the Prism system, click Read Lists to fill in the lists of Country Codes and Currency Codes, etc. Once the lists are filled in, select the desired values from the dropdowns. [Note: These are global values in the database; not subsidiary-specific values.]
After selecting the desired Country Code and Currency Code, click Read Data. When you click Read Data, the tool checks if the subsidiary is being used. If data is found in the subsidiary, a message is displayed. In such a case, you should edit the SBS No setting to use the next available subsidiary number.
Process Out Data
After entering the path to the RP8 data and history files and configuring the Prism and Preferences screens, click the Process button on the main screen. When you click Process, the RP8 data is converted to a set of files in .csv format in the …\V8ToPrism\Prism folder.
1. Click OK on the "Get Data from Prism" screen to return to the V8ToPrism main screen.
2. Click Process. The RP8 data is exported as a set of .csv files to the \v8ToPrism\Prism folder.
3. Copy the exported .csv files to a location (e.g., the local drive) that can be accessed by the machine that will do the import. The exported .csv files can be imported into an Oracle DB or MySQL DB.
History Documents that Reference Deleted Items, Vendors or Departments
In certain situations, the history files exported from RP8 may include documents with items that were later deleted from Inventory (e.g., using Clean House). For such a document item to be imported into Prism, an item needs to be added to the Prism database that has this deleted item's item number and UID (unique ID, the RP8 SID). In this situation, the utility will create a basic Inventory item (set to Inactive status) using the item information on the history document. This basic information includes UPC, Description 1 and Description 2. Deleted items that are recreated in this situation will not have ALU, Description 3, or Description 4 information.
In a similar manner, if the Vendor or Department for an item on a history document has been deleted, the utility will create a basic Vendor or Department record using the information on the history document.
Prism Screen Settings
Refer to the following table for information about the settings on the Prism screen:
|Prism Db Name||
Database name. Default = rpsods
|Prism Db Type||Select a database type from the dropdown: Oracle or MySQL. (0=Oracle; 1=MySQL)
Note: If you select MySQL as the Prism Db Type, be sure to also enter the hostname of the Prism MySQL Server in the Prism Db Name field.
|Subsidiary No||The default Subsidiary No is "2" because the Prism install creates a default SBS 001 and users might enter data in SBS 001 and/or create additional subsidiaries. Consider any existing subsidiaries and whether the data in those subsidiaries needs to be preserved. For example, if Prism has SBS 001 and 002 and you want to keep the existing data, set Subsidiary_No=3. This will preserve data in Prism Sub 1 and Sub 2 and create a new Sub 3 for the RP8 data.
If you change the tool's Subsidiary_No=1 the data import will overwrite data entered in the Prism SBS 001.
Default = 2
|Subsidiary SID||The Subsidiary SID of the subsidiary into which the RP8 data will be put. This data will be filled in/updated when the user clicks the Read Data button.|
|Subsidiary Name||The Subsidiary Name of the subsidiary into which the RP 8 data will be put.|
|Controller SID||Unique system ID for the controller record. Used to reference the CONTROLLER table.|
|Tenant SID||Unique system ID for the tenant record. Used to reference the TENANT table.|
|Country Code||By default, USA is the only Country Code available. Click Read Lists and then select a Country Code from the dropdown (e.g. FRA for France).|
|Country SID||Unique system ID for the country. Used to reference the COUNTRY table.|
|Country Name||Country name. When you click Read Data, the tool will update the Country Name field based on the selected Country Code.|
|Currency Code||Select a Currency code from the dropdown (e.g. USD, JPY).|
|Currency SID||Unique system identifier for the currency. Used to reference the CURRENCY table.|
|Currency Name||Currency name (e.g. US Dollar, Japanese Yen).|
|Season SID||Unique system identifier for the currently active Season. Used to reference the SEASON table.|
|Active Price Level SID||Unique system identifier for the currently active price level. Used to reference the PRICE_LVL table. Data for this field is not pulled from Prism. The data will be filled in when the user clicks the Process button.|
|Active Store SID||Unique system identifier for the currently active Store. Used to reference the STORE table. Data for this field is not pulled from Prism. The data will be filled in when the user clicks the Process button.|
Click the Preferences button on the main screen to customize how price levels, stores and tax areas are displayed. This enables these to be displayed in a manner familiar to users.
When you modify a format, the "Example" area will dynamically update to show how the new formatting will appear. The maximum number of characters allowed for each field is shown on the far right.
Example: Format Price Level Name: %0:s-%1:s
|%||Indicates the start of a new formatting instructions|
|0||Indicates which parameter of the Price Level Name value is being referenced by the formatting instruction (using zero-based numbering).|
|:s||Displays the parameter string being referenced. In the example, both the first and second parameters (0 and 1 using zero-based numbering) display the string "1."|
Import Data into Prism
Use the ExportImportResources.exe tool to import the .csv files into Prism at the root authority. Obtain the ExportImportResources.exe tool from Retail Pro Technical Support. The ExportImportResources.exe tool must be on the Prism machine into which data will be imported.
1. Navigate to the …\PrismTools\ImportExport folder. Use the right-click "Run as Administrator" option to launch ExportImportResources.exe
2. Click the RIL to Prism replication CSV tool button.
3. In the Import File area of the tool, click the ellipses.
4. Navigate to the location of the .csv files. Clear the Zip checkbox. Select the files and click Open.
5. Click Import. In the text box, you will see the data being imported. When the process is finished, click OK.
Wrap-up (Finish Prism, Verify Configuration)
After the import is finished, there are a few tasks remaining:
1. (optional) Return to the V8ToPrism.exe too. Click the Prism button to access Prism settings. Click "Finish Subsidiary 1."
2. Launch Prism and verify/update configuration settings.
3. (recommended) Perform a Physical Inventory to verify inventory quantities.
Finish Subsidiary 1
After the import, return to the V8ToPrism.exe tool. Click the Prism button to access Prism settings. Click Finish Subsidiary 1. This configures some preferences in Prism Admin Console. Alternatively, you can manually edit the settings in Admin Console.
Verify/Configure Prism Subsidiary Settings
Since the tool will be importing into a new Prism subsidiary, you must configure certain settings for the subsidiary after the import (e.g., assign country, currency, price levels and tax settings.
1. Navigate to the Admin Console > Node Selection.
2. Click the pencil icon for the subsidiary.
3. Edit the Country, Price Level and Base Currency.
4. Click Save & Exit.
Where inventory quantities are concerned, it is possible to see minor differences in on hand quantities. If this is encountered, it is recommended to perform a physical inventory within Retail Pro Prism.We recommend completing a physical inventory in Prism after the import.
Appendix: V8ToPrism.ini File
The RP8 Export utility exports data from RP8 according to the instructions in the V8ToPrism.ini file. This section reviews section-by-section the information found in the V8ToPrism.ini file. Note: Blank lines are added to this document to separate out the sections of the .ini file.
Some sections of the .ini file start with "Desc0=0:None, 1: …, 2: …, " . These lines are not used by the tool itself; they are labels to provide the user with information. The lines help the user know the available entries for the field. An example is the [Store_Field_Source] which shows the user the RP8 Store Header field assigned to each Prism Store Address field.
This section sets the Prism database name and type. For Oracle, the Db_Name is the name entry in the tnsnames.ora file (default=RProODS).
|Db_name||The name of the database. Default = RPSODS|
|Db_Type||0 = Oracle
1 = MySQL
Note: This section is not currently used.
This section has general system preferences.
|PrefNow||The preference now is to override the timestamp it puts on the records. This value is for advanced users and should left at the default of 0.|
|Text_File_Limit||Text_File_Limit is a limit on the size of some of the exported .csv files. The .csv files that are controlled by this parameter will have the name format FileName_#.csv. Examples are Inventory and Document:
As the tool is creating the files, if the file size reaches the Text_File_Limit, the tool will close the file and create a new one with the next number. It will then continue to export the data into this new file. It will continue until it has exported all the data. The number of files will be controlled by the total size of the data, and the size limit of the files. If the tool needs to export 100 MB of data and the Text_File_Limit is 1 MB, the tool will export 100 files.
|DataPath||DataPath is the path to the main data files in V8. This will be where you find files such as Invn.data and Price.dat. This will usually be something like C:\Retail\RPro|
|HistoryPath||HistoryPath is the path to the history files. Examples of files found in this path:
The HistoryPath is usually C:\Retail\RPro (the same as the DataPath).
|Subsidiary_Export||Subsidiary_Export controls if the tool will export the subsidiary information. If you are transferring (exporting from V8 and importing into Prism) into an existing subsidiary, you do not want to export subsidiary information. Instead, you will use the information that is already in Prism.
If you are transferring .csv files to a new Subsidiary, you will need to export the subsidiary information so it can be imported into the Prism database.
|Subsidiary_Number||The number of the subsidiary into which the V8 data is being transferred.|
|Subsidiary_Name||The name of the subsidiary into which the V8 data is being transferred.|
|Ws_No||The V8 workstation from which preferences are pulled. Default=1|
The SID section is the collection of SIDs needed to export the data. This is all the SIDs that need to be collected from the Prism system to export the data. The one exception is Currency_SID, which is in the [CURRENCY] section. All the fields in this section are SIDS, except for the Country_Code field (the Country_Code is used to extract the Country_SID from the Prism database).
|Subsidiary||Subsidiary SID is the SID of either an existing Subsidiary to which the data is being transferred, or the SID of a new subsidiary to create.|
|Controller||Generated by Prism when Prism is installed.|
|Tenant||Generated by Prism when Prism is installed.|
|Country_Code||The country to be used by Prism|
|Country||The SID corresponding to the Country_Code|
|SID||This is the SID for the base currency used by Prism. Export controls whether the currency information is exported to Prism. At this time, Prism contains all the known currencies so no currency should be transferred from V8 to Prism; therefore this field should be set to 0.|
|Code||Code is the currency code as defined by Prism. This is used to look up the currency SID in the Prism database.|
|Name||This is contained in the Prism database and is the actual name Prism uses for the base currency.|
|Decimals||The number of decimals used with the base currency.|
|Rounding||0 = No rounding used; 1 = Rounding used.|
The Season section has the Season SID.
|SID||The SID for the season used by Prism. The tool uses the SID for the ‘None' season.|
This section contains the SIDs of the active price level and the active store. The data is collected as the tool exports the data from the V8 database. It will be available after the data has been exported.
This section controls the creation of employees. When an employee record is created, it also creates child customer record. This record requires a customer ID.
|CustIdPref||The customer ID with its prefix. The prefix is added to the beginning of the employee number to create the customer number. An example using the prefix 99999 would be 99999001|
The address type section controls the creation of the address type table entry. This will be the entry for all address types used in transferring the data from V8 to Prism.
|SID||The SID of the address type.|
|Name||The default name is "Home"|
Some Prism fields are not available in V8. These fields could be left blank, or they can be generated by the V8-to-Prism tool. To give some flexibility in the generation of these fields, a way has been made to control this process.
- Static text: e.g. "This is a test." The text will be entered into the field for every relevant record in the database.
- Substitution fields: These have the format "%#:s" where the number (#) sign is an actual number. Examples are "%0:s" and "%2:s". The # is replaced by data from the V8 database. The field used depends on the table being used to create the data. For example, when exporting the price level table, Field0 is the subsidiary number and Field1 is the price level code, also a number. Let's say data is being exported into Subsidiary 5. The tool is exporting the price level record with a price level code of 9. If you have the format string Sub:%0:s-PrcCd:%1s, the actual field will contain "Sub:5-PrcCd:9"
|Price_Lvl_Name||Used when transferring the price level table. Field0 is the Subsidiary number and Field1 is the Price Level Code.|
|Store_Code_Local||Store information. Field0 is for the Subsidiary number and Field1 is for the Store Code.|
|Store_Code_Global||Store information. Field0 is for the Subsidiary number and Field1 is for the Store Code.|
|Store_Name||This field is handled differently than the other fields. This field controls the default store name field if it is chosen by the store field source for store name.|
|Alt_Tax_Area_Name||Alt_Tax_Area_Name is for transferring tax information. Tax code is handled separately. This takes the single v8 TAX_AREA table and creates three Prism tables: TAX_AREA, TAX_RULE and TAX. Field 0 is Subsidiary No, Field 1 is Tax Area Name, Field 2 is Tax Code Number, Field 3 is Tax Code. Alt-Tax_Area_Name is a maximum of 10 characters, so it defaults to field 3.|
Store_Field_Source, Inven_Field_Source, Customer_Field_Source, Invoice_Item_Field_Source
There are several sections that control the source of the fields being transferred from RP8 to Prism. Some of them have default values. Some of them default to 0, which will make those fields blank in Prism. The reason why this was done was that there are fields in RP8 that do not have a direct counterpart in Prism. This allows us to control which RP8 field is mapped to a Prism field.
Each type has a set of entries to control where the data is being stored in Prism. For each entry, there is a list of possible RP8 source fields from which the data is obtained. Each type is discussed in the following sections.
Note that each section lines that with the label "Desc#". Example, Desc0 or Desc2. These labels are there for information when editing the data. These lines are not used by the utility itself. They help users to know what sources are available while editing the entries.
Store_Field_Soure controls the fields that are transferred while the STORE table is being exported. The entries are labeled with where in Prism the field is. Name is the store name. Like other Source Control fields, an entry of 0 will make the Prism field blank. A value of 1 in the Name field means the utility will get the entry from the store name formatting field (described earlier).
In the V8 data, the primary use of the store information fields is to print the store information on receipts and reports. The user can put store information in any of the six available Prism store information header fields. For example, the user might put the Street Name in header field 1 and the address (e.g. 123 Main St) in header field 2. Alternatively, the user might put a message in header field 0, (e.g. "Thank you for shopping with us") and then put the store name in header field 1.
You can configure the Store Name and other information in Prism after the import.
Desc0=0None, 1:Default, 2:Hdr1, 3:Hdr2
Desc1=4:Hdr3, 5:Hdr4, 6:Hdr5, 7:Hdr6
The Inven_Field_Source section is to control the Inventory UDF fields. There are four that are read from the RP8 data. These are UDF fields 1 to 4. You can decide where to put these in the Prism data
Desc0=0:None, 1:Udf1, 2:Udf2, 3:Udf3, 4:Udf4
For creating the customer table, there are 20 possible source fields. The first two are UDF date field 1 and 2. Next are the rest of the UDF fields, Udf3 to Udf8. These correspond to a value of 3 to 8. Then there are 12 auxiliary fields. The auxiliary fields correspond to values of 9 through 20.
Desc1=1:UdfDt1, 2:UdfDt2, 3:Udf3, 4:Udf4, 5:Udf5
Desc2=6:Udf6, 7:Udf7, 8:Udf8, 9:Aux1, 10:Aux2
Desc3=11:Aux8, 12:Aux4, 13:Aux5, 14:Aux6, 15:Aux7
Desc4=16:Aux8, 17:Aux9, 18:Aux10, 19:Aux11, 20:Aux12
There is the invoice item source field control. In Prism, the fields are Note 1 to Note 10. In V8, the fields are UdfDt, which has a value of 1. Then there is UdfStr, which is a value of 2. Finally, there are Udf1 to Udf8. These correspond to values of 3 to 10.
Desc2=3:Udf1, 4:Udf2, 5:Udf3, 6:Aux4
Desc3=7:Udf5, 8:Udf6, 9:Udf7, 10:Udf8