Skip to Content
author's profile photo Former Member
Former Member

Classification Datasource (CTBW) - Different characteristic onfig. in R/3

I generated a material classification datasource (1CL_*) in development with CTBW transaction and then include it in a transport and move it to quality. But we are facing the issue that on R/3 side the master data team did not define the characteristics (CT04 transaction) exactly in the same way in all environments (specifically I am talking about different lengths u2013 for example a characteristic being 30 chars in Dev/ Qal and 10 in Prod). The MD team said that this is not transportable in R/3 since it is considered master data u2013 so, it is manual configuration in each environment.

How is this 'flexibility' managed in BI?. Is the generation of the datasource using CTBW transaction something that should be done in each environment? If the response is yes, the issue is the system should have to open for modifications (customizing). And this is something that will need to be done (open system, regenerate CTBW) everytime they decide to change a characteristic definition.

Also, this is not something that they can replicate in dev, since it is not allowed by the system to shorten the length of the characteristic (only to expand it). So, even if we want to replicate the case in dev., regenerate the datasource and transport, it is not possible. And also, how to avoid this being done directly in production at any time (since R/3 standard gives this flexibility when considering this as master data)?.

Did anyone have / hear any similar scenario?. Thanks!

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Apr 17, 2009 at 08:53 AM

    Claudia,

    you're right. Definitions of characteristics are master data not customizing.

    Characteristics use internal keys. The same characteristic probably will have different internal keys in different clients. Transporting characteristics so probably would create inconsistencies in the target client. The intended method is distribution via ALE. See please message type CHRMAS.

    If you take care that characteristics used in CTBW are available in all relevant clients and they are defined in the same way (that's necessary because fields in generated extract structure depend on these definitions) you won't need to generate such datasources again in quality or production system.

    Regards,

    Rolf

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Claudia,

      I had understood that you're looking for a way how to align characteristics in the different systems.

      You're right. If you need different definitions of characteristics you will have to generate the datsources again.

      The demand to have different definitions for the same characteristic used in CTBW datasources is very unusual. How can you guarantee quality, if already tested objects are changed again when they are transferred to production?

      I would recommend to use identical characteristic defintions. If you need deviating defintions, additional characteristics should be created therefore.

      Regards,

      Rolf

  • author's profile photo Former Member
    Former Member
    Posted on Apr 16, 2009 at 08:44 AM

    Claudia,

    Talk of BI trying to keep up with changes from config teams !!

    Unfortunately, there isn't much that can be done from my experience.

    After you exported the charactersitic datasources (1CL*) into QA, I reckon you should have to change the client name in CTBW and regenerate the datasource.

    For fixing the issue in DEV, if the data is not huge, you can clear out the charactersitic values from the respective materials. Try using transaction CL03N to find materials for the relevant char and then changing the values.

    Following this cleansing exercise, config teams need to sync the QA environment into Dev.

    Alternatively, if you can manage to get the system 'open' for customizing with help from ever-resourceful basis colleagues, then try and generate the char datasources in QA. 'Normally' there is no deviation from QA onwards, so you may not have to do this in PRD.

    All the best!

    Regards,

    Ashu

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 29, 2010 at 04:34 PM

    Hi Claudia,

    I am new to generating the classification data source and I am facing the same issue that you faced regarding the definition of the characteristics in the CT04 transaction and the generated extract structure.

    The Definition in the QUality and Dev seem to be consistent for us, but the Production environment has diffenrent lengths for the characteristics, due to which the transaported data source is not working.

    Our basis resource opened the client for changes, but i was unable to re-generate the data source.

    Can you please tell me how can i re-generate the existing data source so that it re-generates itself by looking at the characteristics definition in PROD environment.

    If you could give me a step by step procedure,i'd really appreciate it.

    Thanks

    Netra.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.