Creation of a Classification Datasource and its related Dataflow

[Former Member]

Summary:

The objective of this document is to explain how to create a classification Datasource and the related dataflow .

Classification and its Purpose:

Classification is the process of assigning objects to classes and characteristic values to these objects. It is the means by which an object is classified based on its properties. Classification concept provides us with the flexibility to keep track of various features that are assigned to an object. Also these characteristics can be used across multiple classes and hence multiple objects. And using the same characteristics different values can be assigned to different objects.

Purpose

When you are managing a large number of objects, you must be able to group these objects according to particular features. This enables a proper and easy way to manage various objects and its features.

The basic use for SAP's classification module is to "classify" master data objects so that you can find them more easily later. For example, you can classify several materials as being black, so that later on you can search for all the black materials.

Why  there is no Standard Classification Datasource?

We  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 not possible 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.

Step By Step to Create Classification Dataflow:

1.      1. Go to transaction CTBW in R/3 or ECC Source system.

2.      2. Create the new entry for the new classification datasource:

a.       Specify the Datasource, which will be related to the master data which we are extending, in this case we are extending Vendor Master Data. 

b.      Select the client from which we will extract the data, although this will be defined as cross client extractor but we need to select one client so that extractor can read the information

c.       Select the class type, object table and Datasource type from the dropdown to match the master data.

       

3.    3.  Once entry is maintained for the datasource, select the datasource line and click on Characteristics in left side of the screen

        

  4. Then select new entries option and add all the required Characteristics

       

     

        Enter the Characteristic name and other entries will default correctly.

5.      5.  After entering characteristics, save and generate datasources.     

           

        The necessary master data attributes (Characteristic datasource) will automatically get generated.    

        The maintenance status ‘N’ indicates datasource has been created and after datasource generation the status will change to ‘R’.

    

       If there is any change in characteristic then we need to reset the status to ‘N’ before regeneration.

6.       6. After that test the new Classification datasource as well as generated Characteristic Datasource using RSA3.

       

7.      7.  Now Replicate the datasources in SAP BW system, In BI 7 system we will get the option to replicate the datasource as 7.x or 3.x, It will be advantageous 

              to replicate it as 3.x datasource as it will allow to automatically create metadata that will perform all the steps  to automatically generate infoobjects and 

              connect them to the master data attribute datasources through transfer rules.

8.       8. After replicating datasource run transaction CTBW_META and enter the source system name and the classification datasource name which we have 

              created.

       

          We can extend the existing datasource or we can keep it as a separate datasource and then later merge at Infoobject level. The later method is preferable

          as it will not modify the original datasources.

          In the lower part of screen provide the new infosource name and enter the infoobject that we are extending (e.g. 0Vendor in this case) and then press 

          continue.

9.       9.  In next screen we can provide Infoobject technical name, description and Infoobject Catalog , these infoobjects will be created automatically in BW 

              system.

    

         Press execute button on top, system will generates all the Infoobjects .

       10.  Now add new Infoobjects in original Infoobject in this case it is 0Vendor and then create  update rule to connect the new Infosource to the infoobject

              0Vendor.

Limitation:

The BW system cannot manage multiple values for a characteristic of an InfoObject. Therefore, when creating DataSources for classifications (transaction CTBW), you cannot use multiple-value characteristics.

Solution:

Use one of the below solution as per the requirement:

1.       Notes 350296 and 535370 describe modifications that make it possible to use multiple-value characteristics. These changes downgrade the corresponding errors to warnings. The BW system is still unable able to process multiple values. Consequently, the extractor always delivers the first value that is found.

2.       If you want to load multiple values in BW, you can create additional single-value characteristics in the classification system. You can then extract the additional values in additional attributes that are based on the additional characteristics

3.       Another solution would be to leave the modeling in the classification system unchanged and to modify the extractor so that the additional values are extracted. These values must then be assigned several attributes in BW.

Refrences:

Note 306046 - Characters of classifctn - attributes in BW

Note 1002105 - CTBW: Extracting multiple-value characteristics