Get problem when input vendor classification data on R3 with CTBW

[Former Member]

We are using vendor classification application and the datasource is 1CL_OVEN001 and there are quite a few characteristic name added already. Now we want to add a new classification data called ZQ_SIC_CODE with transaction CTBW on R3.

Run CTBW on R3 (there is only one line for BASIS DataSource with a value of 0VENDOR_ATTR for 1st column)

-> Select this line, double click Characteristic, can see some Characteristic names with the datasource 1CL_OVEN001

-> Click New Entries button to try to add ZQ_SIC_CODE, click the keyword list button for 1st row/1st column for DataSource, there is only one 1CL_OVEN001 listed, but find the enter button is dimmed, double click on this value, still can't bring in this value to a new line, maybe it's security restriction for our user id? Then we try 2nd column for Characteristic Name which is a required field by pasting ZQ_SIC_CODE into it, then hit Enter, but get red error msg saying "Characteristic has multiple values", what does that mean and how to resolve the problems to add ZQ_SIC_CODE into the classification application?

Thanks

[Former Member]

VENKAT/KEVIN,

Did you guys had a chance to fix this "characteristic has multiple values ".Iam trying to create a data source to get the classifications for a minority indicator charactersitic which has multiple values.

Pls update the thread with ur findings

Thanks

Jagadish

[Former Member]

Hi Jagadish,

The characteristics have been changed from Multiple Values to Single value ones and successfully created the DataSource.

Thanks.

[Former Member]

Hello Kevin,

How did you fix your "Characteristic has multiple values" problem, please?

Thanks.

[Former Member]

Hi there you cannot have multiple values the characteristic names to be single value. There are SAP Notes on this and you can check on whether the characteristic is multi value using R3 transaction CT04

Kevin SAP Note 306046 is almost like an overview with regards to CTBW: Details below:

Symptom

You can classify objects in the R/3 System via the classification system. The required classes are created with respect to a class type. Characteristics are assigned to a class. If an object is classified, values can be assigned to the characteristics (valuation). Since the classifying characteristics of every customer can be maintained individually, it is impossible to deliver a DataSource that is standardized in a way that would meet the requirements of all customers. For this reason, an option was developed to generate DataSources for characteristics which should be used as attributes of an InfoObject in BW.

!! No Delta Procedure is possible for Release 2.0B!!

Additional key words

Generic article, retail, generic article variant, article, characteristics

Cause and prerequisites

Solution

1. OLTP: Maintain DataSources for classification data (menu path in Customizing, Transaction: 'SBIW'

Business Information Warehouse -> Customer-Defined DataSources -> Cross-application components -> Classification system -> Maintain DataSources for Classification Data)

Approach:

1.1 Enter a basis DataSource which you want to enhance, for example, 0MATERIAL_ATTR

1.2 Choose the client, the class type and the object table from which classification data should be copied for examlpe, 100, 026, MARAT

1.3 Select the DataSource that you would like to assign characteristics to and select Characteristics in navigation.

1.4 With the key 'New Entries' enter the characteristics you want to assign.

1.5 You can enter a line item number if you would like to define a sequence within the characteristics.

1.6 Choose the key 'DataSource' to generate the DataSource. At the same time the characteristic DataSource is generated for characteristics of the type CHAR. A prefix "1CL_..." is assigned for the DataSource names.

2. BW: Creating InfoObjects to include the characteristics from OLTP

So that the characteristics can be included and stored with their characteristic values in BW, a corresponding InfoObject must be defined for every characteristic first.

The InfoObjects must have the same technical attributes as the corresponding characteristics in the OLTP system.

The flag 'With texts' must be set, so that an InfoSource for texts is generated for this InfoObject in the system.

The InfoObject is displayed in the InfoSource tree under the specified application component, for example, IS-R-IO, master data IS-R'.

3. BW: Extending the master data InfoSource, for example, 0Material

The attributes of the master data InfoSource 0Material must be extended by the two InfoObjects.

Activate the InfoObject!

!So that you can expand later in the query via the classifying characteristic also, select the attributes in the InfoObject as navigation attributes.

The same also applies to the Cube in which the characteristic is used.

4. Metadata upload

Perform a metadata upload so that the DataSources created in the OLTP are also available in BW.

5. BW: Supplying the attributes of the InfoSource for example, 0Material

Procedure

5.1 Access the transfer rules

5.2 Choose #DataSource'

5.3 Select new DataSource for attibutes

5.4 Assign the newly created InfoObjects created to the corresponding fields.

5.5 Delete unnecessary fields from the transfer structure

5.6 Save and activate

6. BW: Text DataSources for the characteristic texts

The characteristics or InfoSources which were created at point 2 must be supplied with the corresponding characteristic texts. As the flag 'With texts' was set for both InfoObjects, they both appear in the source tree of the application component specified under master data InfoSource.

Procedure

6.1 Access the transfer rules

6.2 Choose 'DataSource'

6.3 Select a new DataSource for attibutes

6.4 Assign the newly created InfoObjects to the corresponding fields

6.5 Delete unnecessary fields from the transfer structure

6.6 Save and activate

Message was edited by:

Niten Shah

[Former Member]

The Multi value note is 535370, details below:

SAP Note 535370

Symptom

Interval-value and multiple-value characteristics cannot be extracted.

Other terms

CTBW, CL_CHECK_ENTRY_110, CL_CHECK_ATNAM.

Reason and Prerequisites

A class type with several object types may have object hierarchies. All characteristics for non-leaf objects then generally have multiple values. Currently, an object hierarchy is implemented for material and batch. A material, which a batch is created for, inherits the value range on the batch. That is, if the characteristics of the material were single values before, they turn into multiple values during this inheritance. However, multiple values as well as interval-value characteristics cannot be extracted.

Solution

As part of this modification, the error messages are changed into warning messages. During the extraction, only one (the first) value is transferred. The modification is not implemented in the standard system.

Implement the corrections described in the note. Refer here to the related note 350296.

Caution: The long texts of messages CLBW017 and CLBW024 must be changed manually.

To change the long text of messages CLBW017 or CLBW024 manually, go to transaction SM31

 Table/view: T100

 Press the "Maintain" button

 Confirm the next information message with ENTER

 Message class: CLBW

 Press the "Change" button

 On the "Messages" tab, position the cursor on row 017 (for CLBW017) or on row 024 (for CLBW024)

 Press the "Long text" button located on the menu bar

 Under the heading "SYSTEM_RESPONSE", delete the old text and enter the following new one(s):

 for CLBW017: "During the extraction of interval-value characteristics, only one value is transferred."

 for CLBW024: " During the extraction of multiple-value characteristics, only one value is transferred."

 Save the long text.