Difference between revisions of "Price Group Import Guide"

Revision as of 13:38, 10 January 2019

General Data Import Notes

Refer to the Data Import General Information page for information and guidance on general import timeline, formatting import templates, as well as how to ensure you are using the most current template information for data imports.

Price Group Import Notes

The Price Group Import is used to create new price group records, update existing records, or delete unwanted records. The import can create either customer pricing or vendor pricing controls. Vendor pricing groups are not as common.

Timing and Preparation

Customer Price Groups should be set up after all Item Master setup, including Item Master imports, has been completed, and all customer organizations have been imported.

Pricing controls should be in place during parallel testing so that order pricing and special customer pricing can be reviewed and adjusted as needed.

General Notes

The Price Group Import can update either the Customer Pricing or the Vendor Pricing(Costing) screen. Adjustments to the pricing setup can easily be made by re-importing the same file after making changes. The import works to update existing records, as well as deleting unwanted records if the 'DeleteOnly' column is checked and there is an exact match.

There are four types of pricing models that can be defined. The pricing model code is required for the first column of the import file, labelled PGRP.

GG - Group/Group - Pricing Group name (Gold, Tier 1, Preferred, etc.) plus the Item Price Group name (from the ITEMGRP rule)
GI - Group/Item - Pricing Group name (Gold, Tier 1, Preferred, etc.) plus the Item number
EG - Entity/Group - Organization number (customer or vendor) plus the Item Price Group name (from the ITEMGRP rule)
EI - Entity/Item - Organization number (customer or vendor) plus the item number

An item may fall into more than one pricing model. Adjutant will always choose the lowest price when an item has multiple matching pricing controls.

Price Group File Data Scrubbing

Every customer's data will have different issues that need addressing. Some of the issues will not make themselves visible until after the data has been imported and is in use during parallel testing. This is why it is critically important to perform an early import, and keep accurate notes on issues that need to be addressed on a supplemental import, or for a complete re-import.

This file is generally built from various sources of customer supplied data, so there is rarely a need for scrubbing customer data, except when item codes or vendor numbers are changed from the customer's legacy system.

Price Group Import Screen (PRICEIMP)

Menu Location: Transaction>>Importers/Exporters>>Purchase and Sales Orders>>Price Group Import

Item File Name/Browse: Use the Browse button to locate and select the completed Price Group import template file (in XLS format).

Export Template: Generates a blank Price Group template file

Map Fields: Fields must be mapped prior to importing. If no changes have been made to the column headings, the mapping screen should show all green, and you can click OK to continue. If any of the Input Field Name columns on the left are red, single-click on the line on the left column, and then double-click the desired mapped field in the right column to complete the mapping. Repeat for any red lines on the left that should be mapped. If there are additional columns in the source file that should NOT be mapped, they can be left unmapped (displayed in red). Mandatory fields will require that they be mapped before clicking OK.

Special Customer Entered Pricing: Checking this box sets the 'Customer Entered Pricing' flag in the Customer Pricing screen for all imported records.

Customer Pricing: Select this radio button to update the Customer Pricing screen

Vendor Costing: Select this radio button to update the Vendor Pricing screen

Price Group File Definitions

Required fields are indicated with an *

*f1 - PGrp - Pricing matrix code. Valid entries are GG, GI, EG, and EI. See above for detailed explanation.

*f2 - EntCode - Pricing Group name for GG and GI matrix setups. Organization number (customer or vendor) for EG and EI matrix setups.

*f3 - ItemCode - Item Group name for GG and EG matrix setups. Item number for GI and EI matrix setups.

f4 - Factor - Factor type. Defines how the factor amount entry is used to calculate pricing. Valid entries are 'F' (Fixed Price), 'P' (Percentage), 'M' (Margin), and 'D' (Dollars). Percentage and Fixed Price are the most common factor types.

*f5 - RateCode - Enter 'R' (Regular) for all records, unless directed otherwise. Other available entries are 'D' (Double-Time), 'O' (Overtime), and 'T' (Triple-Time) for labor options, which are no longer priced through this program.

*f6 - Origin - Enter 'P' (Price) to use the item list price as the origin amount. Enter 'C' (Cost) to use the item base cost.

*f7 - FacAmt - Factor Amount value. Enter the fixed price dollar amount or the percentage value to use for calculating the discount (for Price origin) or markup (for Cost origin). Allows 3 decimals.

*f8 - StkStatus - Item stocking status filter. The most common entry is 'B' (Both stock and non-stock). Other filters are 'S' (Stock) and 'N' (Non-stock).

f9 - StartQty - Starting quantity (low) count used to define different price breaks based on order quantity.

f10 - EndQty - Ending quantity (high) count used to define different price breaks based on order quantity.

f11 - Sale - Enter 'Y' to check the Sale box for the associated pricing record. Sale start and end dates should be defined in the following fields, if 'Y' is entered.

f12 - SaleStart - Sale starting date in MM/DD/YY format

f13 - SaleEnd - Saled ending date in MM/DD/YY format

f14 - Unit - Unit of measure used with the fixed price factor type

f15 - DeleteOnly - Enter 'Y' to delete the associated pricing record

f16 - StartVal - Starting dollar value (low) count used to define different price breaks based on order value.

f17 - EndVal - Ending dollar value (high) count used to define different price breaks based on order value.

Price Group Additional Steps

There are no additional steps needed after the import.

Price Group Reconciliation

Reconciling imported data should begin with spot-checking several records field-by-field for complete data import. Pick records from the source file that have the most data columns filled in. Verify that all source file data fields imported correctly and display as expected.

Price Group Database Tables

PRICEGROUP - All imported records are stored in the table. The EGROUP value holds the Entity or Group name. The IGROUP holds the Item Price Group or Item number. The IKEY shows the associated item number. The ENTID shows the associated organization ID.

@@ Line 1: / Line 1: @@
-==General Import Template File Notes==
+==General Data Import Notes==
-*Template files are typically generated from their respective Import screen using an 'Export Template' button.
+Refer to the [[Data Import General Information]] page for information and guidance on general import timeline, formatting import templates, as well as how to ensure you are using the most current template information for data imports.
-*Using the 'Export Template' button from an updated system will help ensure that you are using the most up-to-date import file, and will help avoid errors.
-*Templates generally (but not in all cases) contain 3 rows of header information.
-**The first row is generally labelled with f1 through f## and is used to give a consistent column id to each data column. Do not remove this row unless instructed.
-**The second row is labelled with the column data/field name. The values in this row are used for the file mapping screen. Editing these values is generally not needed and may make the field mapping process difficult.
-**The third row (if present) is labelled either with the same values from row 2, or with more detailed field descriptions.  The third row is available to create a customer-friendly name for the associated data column.
-***The third row should be removed from the source file prior to importing.  It will cause errors since it will be treated as the first import record on the file.
-*Import files MUST always be saved as 'Microsoft Excel 5.0/95 Workbook (*.xls)' format until further notice. The import screens will generate errors if the file type is not correct.
-*It is a good idea to perform a Mapping Table Import using a current source list before beginning on any imports.  Without a current mapping table, the quality of imports can be compromised. The Mapping Table Import only needs to be run once on a newly set up Adjutant system.  It does not need to be run before each import.
-**Export a current list from the Mapping Table Import screen from an updated system (or contact your Implementation Consultant for an updated file).
-**Perform a Mapping Table Import on the target system with the XLS file from the step above.