Let us see today about the Option codes in VMS
We will look at how vehicle record data is built
Step 1 : To figure out what options are needed to define the vehicle
A. Examples are exterior color, engine, transmission, model, and trim package.
B. There is no limit to the number of options that could be created to define the vehicle.
Step 2 : To figure out the possible values for each option
A. Example, the choices for exterior color can be red, blue, green, yellow and black;
The choice for trim can be LX, EX, and ZX.
These examples have multiple values for each option. But it’s just as acceptable
to define a unique option for RED, a unique option for BLUE, so forth and so on.
Step 3 : To create a characteristic for every option through tcode CT04
A. Every characteristic must have a unique name.
B. Using Exterior Colour, acceptable names are: EXT_COLOUR, or
COLOUR, or 1234AHG, or etc
To define the data type
A. Majority of characteristics will be either type CHAR (character) or NUM (numeric).
B. Once the data type is defined, the input parameters need to be defined.
C. For CHAR, this is the max length of the value key.
D. For NUM, this is the max number of integers
Warning: once the data type is set, it can’t be changed.
Step 4: To defines the possible values inside the characteristic
A. It’s the combination of characteristic and value that define the vehicle record
so that step 1 and 2 are much important.
B. If this characteristic (Exterior colour) has multiple values (red, blue, green, etc.),
then each possible colour would be listed as a unique value
C. If the characteristic has single value (e.g. COLOUR_RED), then only one colour
would be listed as a value.
Entering values in the characteristic
1. Each line for value has two fields: the key and the description.
2. The key must be unique for the characteristic
3. Its length must be less than or equal to the max length defined in the header.
4. For CHAR, the key can be alphanumeric
5. for NUM, the key must be numeric
Example : OY6 could be the key for red, A4R could be the key for blue, etc.
Defining all the option codes is a big chunk of work, but this is only the first of several additional steps needed to build the master data.
We will look at how vehicle record data is built
Step 1 : To figure out what options are needed to define the vehicle
A. Examples are exterior color, engine, transmission, model, and trim package.
B. There is no limit to the number of options that could be created to define the vehicle.
Step 2 : To figure out the possible values for each option
A. Example, the choices for exterior color can be red, blue, green, yellow and black;
The choice for trim can be LX, EX, and ZX.
These examples have multiple values for each option. But it’s just as acceptable
to define a unique option for RED, a unique option for BLUE, so forth and so on.
Step 3 : To create a characteristic for every option through tcode CT04
A. Every characteristic must have a unique name.
B. Using Exterior Colour, acceptable names are: EXT_COLOUR, or
COLOUR, or 1234AHG, or etc
To define the data type
A. Majority of characteristics will be either type CHAR (character) or NUM (numeric).
B. Once the data type is defined, the input parameters need to be defined.
C. For CHAR, this is the max length of the value key.
D. For NUM, this is the max number of integers
Warning: once the data type is set, it can’t be changed.
Step 4: To defines the possible values inside the characteristic
A. It’s the combination of characteristic and value that define the vehicle record
so that step 1 and 2 are much important.
B. If this characteristic (Exterior colour) has multiple values (red, blue, green, etc.),
then each possible colour would be listed as a unique value
C. If the characteristic has single value (e.g. COLOUR_RED), then only one colour
would be listed as a value.
Entering values in the characteristic
1. Each line for value has two fields: the key and the description.
2. The key must be unique for the characteristic
3. Its length must be less than or equal to the max length defined in the header.
4. For CHAR, the key can be alphanumeric
5. for NUM, the key must be numeric
Example : OY6 could be the key for red, A4R could be the key for blue, etc.
Defining all the option codes is a big chunk of work, but this is only the first of several additional steps needed to build the master data.
No comments:
Post a Comment