Skip to Content

Transport of datasource, infosource etc. for classification data

Hello All

I am an old ABAP programmer who has just started to work with BW.

My first task is to enhance an old DataSource for classification data. The changes worked fine in our Development system, but transport to the QA system is a problem.

I enhanced the definition of the DataSource in SBIW/CTBW and generated the DataSource/extraction structure.

The fieldname in the extraction structure is generated with a number suffix. As example one of the old fields is called DC_DCKALV050 where 050 is the suffix.

On the BW side this suffix is also used when the DataSource is linked to an infosource and it seems everything is works in our development system (maybe I don't describe this in the right way but please remember this is all new to me).

When I want to move it all to the QA environment I follow an old procedure made by an external consultant. According to this procedure I must NOT transport the definition of the infosource from BW development to BW QA, but I have already transported the definition of the DataSource on the R/3 side.

The problem is now that the infosource link to a fieldname with suffix 49, but the fieldname in the DataSource/extraction structure has suffix 50.

My guess is that this inconsistency will be fixed if i transport the infosource also ?

Is it normal procedure to transport the infosources or must I maintain the infosources in every system (DEV,QA,PRD) ?

Best regards

Thomas Madsen Nielsen

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jun 02, 2005 at 09:19 AM

    Hi Thomas,

    after you transported the R/3 stuff (datasource), did you replicate the datasource? This needs to be done before the BW transport.


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 02, 2005 at 10:04 AM


    InfoSources normally get transported but I think your issue is about the following (and please forgive me if I'm wrong ;-):

    In BW you can link an InfoSource to any source system you have available.

    What I see in many projects is that they use BW-DVL for testing as well, and to get good quality data they connect BW-DVL to R/3-QA.

    So you had to transport the (modified) extractor for R/3, but for the InfoSource it was not necessary.

    Siggi is right that you need to replicate the datasource in BW, and then of course for the right source system. Goto tr. RSA1 -> Source systems and look up your datasource for the correct source system. Don't forget to re-activate the transfer rules afterwards. When you now start loading the new field should come in (check if it's in the transferstructure, tab DataSource/Trans.structure).

    Hope this helps!



    Add a comment
    10|10000 characters needed characters exceeded

    • Hello again

      Thanks for your reply.

      I have now spoken with a colleague who can remember why we didn't transport infosources in the past.

      In SBIW/CTBW we can now give the DataSource a number for Position of characteristic in structure. In older versions of the plugin this number was missing, and the fields could be placed in the different order in DEV and QA and get different suffix.

      Because of this the procedure was made: Do NOT transport the infosources (The infosources was developed 3 times (DEV,QA,PRD).

      With the new field it should be safe to transport everything.

      Best regards

      Thomas Madsen Nielsen

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.