Eclipse PDW

The following control maintenance records belong to the EPDW (Eclipse Product Data Warehouse) category. Review and complete these records if you use the Product Data Warehouse companion product.

Allow Duplicates In PDW Description

Indicate whether to allow duplicate descriptions in PDW. If set to No, the system recognizes duplicate description words and removes them. If set to Yes, then the system keeps all descriptions. The default is No.

Allow Price Line Change To PDW Items In Excluded Lines In SOE

Indicate whether, for a nonstock imported from the Product Data Warehouse (PDW) into a price line that excludes manual creation of nonstocks, to allow the user to change the price line assigned to that product. More:

Options	Yes - Users can change products within sales order entry that are part of price lines that are flagged to exclude nonstocks. No - Users cannot change products within sales order entry that are part of price lines that are flagged to exclude nonstocks.
Outcome of setting this control record	Determines if a user can update pricing information for nonstocks in pricelines that are flagged to exclude nonstocks.
Default Value(s)	No
Dependencies	This record is active only when the manual creation of nonstocks is excluded from a price line by selecting the Exclude option in the Nonstock section of the Price Line Maintenance window.
Action if set to Null	Same as if set to No.
Additional Information	None

Allow Price Sheet Per Qty And UOM To Change On PDW Price Update

Indicate whether, when doing a batch price update, the system changes the price per unit of measure and price per unit of measure quantity on the product price sheet in the Product file to match the UOM data in the PDW. The default is N. More:

For example, in Eclipse you have a product's price per unit of measure set to ea and the price per unit of measure quantity set to 1, but in the PDW the product's price per unit of measure is set to C and the price per unit of measure quantity is 100.

Y - The system changes the price per unit of measure and the price per unit of measure quantity on the Eclipse product price sheet to match the UOM data in the PDW.

Note: For any Eclipse products that the system updates because this record is set to Y, you will need to manually adjust the average cost unit of measure for the branch on the Branch Costs screen and any UOM-specific sell matrix cells.

N - The pricing unit of measure on the Eclipse price sheet does not change when the corresponding PDW information changes. When running the batch price update, the system divides the PDW price/cost by the price per unit of measure quantity and then uses that amount to update the price/cost on the Eclipse product price sheet.

Note: Select this option to retain Release 7 functionality.

Disable Branch Specific Product Authorization In PDW Search

Indicate if you want to turn off the product authorization check at the branch level during a PDW Search. Set this control maintenance record to Yes if you find the system PDW searches taking an inordinate amount of time. By skipping the branch-specific product authorization, the system can search product records more quickly and keep your daily work more efficient.

Disable PDW Catalog

Suspends PDW functions except to administrative users. Used by PDW administrators for maintenance or troubleshooting, this control maintenance records essentially turns the PDW catalog off, suspending functions until maintenance, such as running a PDW index routine, is complete. Setting this control maintenance record to Yes keeps mass calls to the database from inhibiting any maintenance routines. Users currently in PDW sessions when this control maintenance record is set to Yes can complete their current work, but will not be able to open any new sessions. PDW Administrative users are set in the PDW Administrator User ID control maintenance record (see below).

Note: This control maintenance record impacts all Web Order Entry. Those WOE applications will not return any data from the PDW catalog while this option is set to Yes.

Display PDW Products In WOE

Indicate whether the system displays Product Data Warehouse (PDW) products in web order entry product searches. PDW is a companion product that can store millions of product records. More:

Options	Yes - Displays PDW items in web order entry. No - Does not display PDW items in web order entry.
Outcome of setting this control record	Determines if products in your PDW catalog are included in product searches conducted through your web order entry site. You might choose to not offer your PDW catalog products for sale over the web, as these are typically products that you do not stock, but can order.
Default Value(s)	No
Action if set to Null	Same as if set to No.
Additional Information	You can override this record at the customer level in the Display PDW Products field on the B2B/WOE Remote Order Entry Parameters window in Customer Maintenance. For more information, see Entering B2B/WOE Remote Order Entry Parameters.

Enable PDW Effective Dates

Set this control maintenance record to Yes if you want to use a data identifier in the Effective Date field when importing PDW maps and let Eclipse update your price sheet effective dates for PDW. More:

Enable PDW Effective Dates	Yes - Lets Eclipse update your price sheet effective dates for PDW. No - Processes using the most current pricing stored in PDW and loading it to the Last Effective Date value in the Price Line or Product Price Sheet. This is the backward compatible option.
Enable Batch Update to Update Pricing on Future Eff Dates	Yes - Allows the system to fetch future effective dates as valid dates to update pricing. No - Keeps the system from updating future effective dates.
Outcome of setting this control record	Allows the system to keep effective dates updated automatically. You can use this option to load true manufacturer pricing effective dates which is often necessary to avoid end-of-month rebate claim issues.
Default Value(s)	No
Action if set to Null	Same as if set to No.
Additional Information	Use this option in conjunction with PDW Historical Price Sheet Number Of Months control maintenance records if you need to take historical data into consideration.

Ignore Products In PDW Sync With Status

Enter the product statuses in your primary product file the system should ignore when syncing the Product Data Warehouse (PDW). More:

Options	Any product status, such as Temp, Delete, and Purge.
Outcome of setting this control record	When you use the PDW/Eclipse Product File Sync Utility to connect records in the PDW catalog with records in Eclipse, the system ignores products with the statuses you indicate in this record.
Default Value(s)	None
Action if set to Null	The system uses products with all statuses when you perform a sync.
Additional Information	We recommend entering the Delete and Purge statuses, as these are products you have chosen to remove from your product file.

Local Path For PDW FTP Files

Indicate the directory path where the system downloads the Product Data Warehouse (PDW) FTP file. For more information, see Using FTP Requests to Update PDW.

Minimum % Variance To Include On Batch Update Report

Enter a minimum percentage threshold to control how the Batch Update Report includes products with price variances. For example, if a user enters a value of 10% then only product price updates with a price variance of 10% or greater would display on the report.

Enter a whole number or number with one decimal place. For 10% enter 10. For 2.5% enter 2.5. The default is 0.0%.

PDW Administrator User ID

Enter the user or message group to notify of Product Data Warehouse (PDW) updates and errors. More:

Options	Any user ID or message group.
Outcome of setting this control record	Notifies the user or message group regarding updates
Default Value(s)	None
Dependencies	To assign a message group, you must be authorized to see the message group type to which the message group is assigned. For more information, see the Valid Message Group Types control maintenance record.
Action if set to Null	No message is sent when there are PDW updates or PDW error occur.
Additional Information	None

PDW Historical Price Sheet Number Of Months

Enter the number of months (greater than zero) for which to copy and store PDW effective dates for products in a given price line. When new products are created from PDW or when items are updated through the PDW Batch update process, the system checks this control maintenance record to see how much historical information to keep. If set to yes, you must also select the Enable Historical Price Lines check box in Price Line Maintenance.

PDW Image Path

PDW Product Template

Enter the product set up to use as a template whenever you export product data from the PDW Catalog to create a product in the Eclipse Product file. More:

When a PDW metadata item mapped to a field in the Eclipse product record does not contain a value, the system populates the field in the Eclipse product record with the corresponding value from the default template. If you leave this control maintenance record blank and a PDW metadata item does not contain a value, the system leaves the corresponding field in the product record blank.

PDW Reserved Source Names

Enter the names of any source-specific data load routines, which cannot be used as import map names. For example, I2, IDW, or PM are reserved source names in Eclipse.

Setting WOE, PDW Image Priorities, IMG

Should Lower Level PDW Price Sheets Look To Tilde

Indicate if you want the system to use the default (~ tilde) price sheet settings for all lower-level PDW price sheets. The system would then retrieve all information in the price field setting defined in the map, plus the basis field settings defined in the default price sheet.

For sites with a large number of branch and territory pricing, this feature helps to easily maintain pricing basis fields which are common to all price sheets, such as LIST. By using this feature, the system uses a three-level hierarchy check to determine a PDW price:

Use PDW Price Export Map With Blank Discount Class As Override

Indicate if you want the system to find a default PDW Price Export map with an empty Discount Class to use as an override. By default, if a specific export map is not found, the system uses the *Default* map. The system first calculates pricing using the PDW Price Sheet specified by the price line, then the price sheet, and then the discount class. If nothing matches, the system uses the *Default* price map.

Eclipse PDW (Product Data Warehouse)