Distribution, Manufacturing, and Internet Modules

[jernst]

I set 3 different price levels for my items: C, R, T.  I want to import these with cost for a large amount of items.  I thought I could import into IM.Price but I can't seem to get it to work.

Here's my layout:

Price_Code_Rec  Assign 1 (for Item Pricing)

Price_Code Replace 24 (skip this field because its blank)

PC_Cust_Prc_Lvl Assign C (I will assign this for each level. Run the import 3 separate times)

Item_Number Replace 1

Im_Cust_Prc_Lvl Replace 25 (skip this field because its blank)

Division_No Replace 26 (skip this field because its blank)

Customer_No Replace 27 (skip this field because its blank)

PC_Method Assign 5 (for Price Override)

Disc_Markup1 Replace 4 (Price of Item)

Break_Qty1 RunAssign (max quantity, always entered as 99999)

When I run the import only Price_Code_Rec and Break_Qty are written.

Any ideas where I am going wrong?

[JimPetrie]

How did you configure the records tab?  You need to tell the import job how to distinguish between the three different types of pricing records you could be creating.

[jernst]

I planned on running this job 3 separate times and assigning this record each time so I didn't think I needed to configure the records tab.

[jernst]

Not sure if it will make things easier in helping me to get this job to work but this is what I need to import:

Item_Number - Item Code (Imported in from file)

IM_Cust_Prc_Lvl - Price Level (C, R, T) - I can run this as 3 separate jobs and assign this if needed.

Im_Method (Cost Override) - pretty sure this value should be "O"

Disc_MkUp_Prcr1 (This will be the cost I import in)

There are other values that are required, but I want to leave all those fields blank.  Currently, we manually enter these levels for each item.  You can image 3 levels for each item number is a daunting task and time consuming.

[Heather]

I do not believe that the fact that you are assigning a 1 to the Price_Code_Rec field is enough to tell VI what you are importing.  Nor does the fact that you are importing a value into IM_Cust_Prc_Lvl.  Follow Jim's advice and set up the records tab.

I see no need to do three imports.  Put all your records in one file, include the price level, and do just one import.

[jernst]

The records tab is where I get confused.  What do I set up in the records tab?

I tried leaving the records tab as what they defaulted to when starting the import job but no luck.

[JimPetrie · Accepted solution]

Step #1: Determine which pricing method you are creating (price code, item price or item/customer price record).

Step #2: Add a field to your source data that identifies each record as being one of those three types (1 = price code, 2 = item price, 3 = item/customer price).  For the purposes of this example let's say it's the 2nd column of your source data that contains this 1,2,3 designator.

Step #3: On the records tab, pick Record Type "Price Code Record".  Uncheck the box for "Perform Logic Only".  In the fields that appear tell it to look at Field 2 of your data, Start 1 Length 1 and asssign if the value =1.

Step #4: Repeat for the other two record types.

[BShockley]

You have to tell the import job which type of record you are importing.

The easiest way to find out your record type is to manually enter special pricing and then import the data into Excel or create a Crystal Report to show you what data is in each field.