The Category Price Plan Import enables the creation of a CSV file for importing one or more CPP plans. The Import will add the Category Pricing plan but will not auto-assign it to customers. Updates will not be supported by the system, but you can add new categories to an existing plan provided the correct plan name (ID) is listed in the CSV file and the category does not already exist in the plan.
The following settings are required:
NewSystem Option 2083 ‘Category Pricing Plan Import’must be set toYesto enable access to the import utility.
Security Bit 1175 ‘Access Category Pricing Plan Import’must be set toYesfor each user that has the authority to import CPP Plans.
Import file requirements:
The file must be in a Comma Delimited (CSV) file format. The expected columns are:
Import Fields
Required?
Description
Plan Name
Required
Plan Description
Required
If left blank, the import will default to the plan name.
Required if using a price method of markup or markdown percent.
Category Price
Optional
Required if using a price method that requires a price such as a method *.
Category Expiry Date
Optional
mm/dd/yy format.
Price Code
Optional
Required when using price methodG- The price code where you specify which cost or price field you want the price method to calculate from. If left blank, the system will use the cost present in MIC Cost used in the calculations. Available options are: Blank12345ACMLR.
Category Start Date
Optional
mm/dd/yy format.
Notes:
All records listed in the CSV file for the same plan name must have the same values for the fields marked with an asterisk (*) above, which are CPP plan header fields. If any records with the same plan name follow a different value, the system will ignore that value and add the plan to the first value listed.
Subplans must already exist in CPP to be linked.
You can only have one level of Subplans.
The Subplan Category Name must match the existing subplan name.
The file can contain a header row that will not import. Set the option‘File Contains Header Row?’ toYif a header already exists.
Place the file inC:\3apps\tempbefore starting the import process.
One file can import multiple plans if all category records have the appropriate assigned plan name.
In theImport CSV Filefield, use the drop-down to select the file to import (preloaded into C:\3apps\temp). See the Setting the import path section of this article to learn how to do this.
In theFile Contains a Header Row?field, use the drop-down to indicate whether the file includes a header row.
SelectOKto import the file.
After importing the file, a‘Processing Complete’dialog displays the number of Records Read and Successful Updates. It also lists errors encountered if any lines could not be updated.
Note:Referring to the screenshot above, the file included a header record, thus showing a difference in the Records Read and Successful Updates fields. Also, the records that are not updated will report to the 3log.log file.
Important: Always test with a small plan first to make sure the data fields in the file are correct.
Once the plan is imported, link it to the correct customer in Eagle Customer Maintenance (MCR).
Category Pricing Plan (CPP) can import existing CPP plan changes by removing and replacing the existing plan with the new updated CSV file.
When the import begins processing the CSV file, it checks if the Plan Name matches an existing plan name in Eagle. If a match is found the import shows a prompt with a warning that the plan(s) already exist. You can select Yes, No, or Cancel to complete the import.
Select Yes to remove the existing plan along with all the detail records and then import the new file for replacement.
Select NO to process the import file, it imports only categories that did not previously exist in the existing plan on file. Any category matching a record in the existing plan will not update and will report the line as a record not added, already on file.
Select Cancel to exit with no import.
Note: If there are multiple plan names in one CSV Import file, the warning only comes up once with the first plan name match.
Additional Notes:
If importing a subplan, you must list a price method (such as 1). CPP usually uses the subplans pricing, but the import requires a price method. Also, if you add a subplan manually in CPP, you must select a price method to add the subplan. Once added, the price method field will be blank as the system uses the subplan pricing.
If the entire plan imports but some records have an issue, you have two ways to correct them:
Display the imported file in CPP and manually correct or add any record that did not import.
Display and delete the plan in Eagle CPP, fix the problematic records on the import file, and reimport the entire plan.
Mode 2 CPP Imports,
When using type S and category SKU, the import will recognize the SKU entered in the category SKU, even if the shadow number is different. Always use the SKU number in this field.
CPP imports do not support setting the flag to ‘Apply to Cores Only.’ Imports will default Core’s Only flag to N. Note about long SKUs in mode 2:
All SKUs longer than 14 characters, when added to IMU, will have a shadow number different than the actual SKU number.
All SKUs that are 14 characters and under, will have the shadow number same as the SKU when added to the inventory. But if a delete is done and a SKU is re-added to inventory, then a SKU with 14 characters or less will have a different shadow number than the actual SKU.
Setting the import path
You can set the Import path when importing a CPP CSV file.
To access this feature:
Launch the Category Pricing Plan (CPP) under the Misc Menu.
Select CPP Import.
Select the Set Import File button to set the Import file and path.
Select the file to import using the Windows browse function.
Browse to the directory to import the file and select Open.
The Import file path is displayed beside the Import File.