transport request ended up with status RC-8

[Former Member]

Hi Every Body

There was a new field created at source system side and new infoobject at BW side. All this was done in DEV system. Then i had transported this changes to QA system. But here i missed one step in the transporting the changes. And that is the reason my Transport ended up with status RC-8 and thus i was not able to see my new Object on QA system. I missed replicating the Data Source b4 transporting the request.

Then to resolve this. I first replicated the Data Source and retransported the request. This time i was able to see the new object in QA but my request still ended up with status RC-8. Now my Q is will i be able to move the same Transport request to PRD system or i will have to create another Transport Request with transfer sturcture?

I would appreciate for a quick reply, bcoz its quite urgent. got to move the changes to PRD by tomorrow

Thanks a lot in advance

Rohini

[Former Member · Accepted solution]

Hi,

Can I know what was the exact error in the transport aside from RC-8

Regards,

Jkyle

[Former Member · Accepted solution]

The error it gives after the transport :

Mapping between data source and source system is inconsistent.

Field ZXXX will not be delivered from data source in source system.

Reference to transfer structure not available. No activation possible.

Thanks

Rohini

[Former Member · Accepted solution]

Hi,

It looks like its searching for a field not found in BW. But according to you. after replication, the field is already visible in BW. Is it active?

Where did you see that its visible already? You should be able to see that at RSA1->Modeling->Source Systems-><double click your source system name>->at the right panel, click find and look for your field. It should exist there with a negative red mark (Unmapped).

Did you see that?

Ensure also that the field in question in the error is the one you see there. I am saying this because we might mistakenly identify the wrong field for the error...

--Jkyle

[Former Member · Accepted solution]

Hi Jkyle

Thanks for getting back with reply so fast.

I can see my new infoobject, in my ODS and now i have deleted my provious data and reloaded the data successfully and it is getting uploaded daily through porcess chain.

But my Q is even after all my transport made successfully my transport is endding up with RC-8. I can understand why i got this error when the transported was made for the first time(because i missed replicating data source b4 transpoting the changes). But now after retransporting the request it is still ending up with status RC-8. So now can i tarnsport the same transport request to PRD or i will have create new transport request in DEV and then move it to QA and then in PRD?

Thansk & Regards,

Rohini

[Former Member · Accepted solution]

Hi Rohini,

Yes you can use that old transport request to transport to live. Just always be sure you <b>REPLICATE FIRST</b> prior transporting BW objects specially transfer rules.

Hope I get points then...

Best Regards,

--Jkyle

[tom_francis2 · Accepted solution]

For me, it just seems safer to create a new BW request including the datasource from the transport connection.

Afterwards when going to production, use both of the requests. (old + new).

kr,

Tom

[Former Member · Accepted solution]

Thanks!!! Jkyle

U will surely get points. Because u came up with reply very fast.but got to wait till it is transported successfully.

Thanks a lot again

Rohini

[Former Member · Accepted solution]

Hi Jkyle

Now Tom's reply has scrard me,is it required to create new TR# or old one with status RC-8 will do in Production?

Regards,

Rohini

[Former Member · Accepted solution]

Hi Rohini,

from your description (but correct me if I'm wrong...), it seems that by now you didn't transport a request with a valid returncode!

So, before deciding if it's better to transport the old one or to create a new CR, it would be better to execute a final CR that ends with a successfull RC and then...it's up to you !

Bye,

Roberto

[Former Member · Accepted solution]

Hi Roberto

Yes you are right Tramsport request is not yet moved to production system. There were some other issue's so could not move it.

You want me to create new CR but making no change? And then i would not require to move old transport request?

Please get back ASAP and with clear steps to create new CR.

Regards,

Rohini

[Former Member · Accepted solution]

Hi Rohini,

Whats the catch if transport failed to Production? Correct me if I am wrong but the <i>data sources</i> you are transporting does not exist yet in <b>BW PROD</b> right? So no one is using it for live purposes, so whose affected with it?

--Jkyle

[Former Member · Accepted solution]

Hi Rohini,

if you don't like to run a risk, good sense require to transport everything (if not damaging !!!) you needed to reach a correct situation...that is, transport everything in your PRD as you already did from DEV, in the same sequence !

Bur the question is why you are facing these transport problem...I'm not clear about your actual situation in BW...even if you replicated, even if you see your new field in transfer structure (and in transfer rules?), you have still failed RC ???

[Former Member · Accepted solution]

Hi Jkyle

Data Source is already there in PRD system.

There some enhancement made in data source and that is what i want to transport.

Regards,

Rohini

[Former Member · Accepted solution]

Hi Roberto

There reason of the RC-8 is

"There was a new field created at source system side and new infoobject at BW side. All this was done in DEV system. Then i had transported this changes to QA system. But here i missed one step in the transporting the changes. And that is the reason my Transport ended up with status RC-8 and thus i was not able to see my new Object on QA system. I missed replicating the Data Source b4 transporting the request.

Then to resolve this. I first replicated the Data Source and retransported the request. This time i was able to see the new object in QA but my request still ended up with status RC-8. Now my Q is will i be able to move the same Transport request to PRD system or i will have to create another Transport Request with transfer sturcture?"

i hope now every thng is clear, if not let me know.

I didnt understand your solution.

Regards,

Rohini

[Former Member · Accepted solution]

Hi Rohini,

Ok, thanks for the clarification.

But how sure are you that only the <b>REPLICATION</b> is the culprit?

The error message may mean more than just missing fields. How did you collect your objects for transport by the way? Did you manually create them? There is an automatic way to do it and i hope you used that RSA1->Transport Connection to ensure that no needed objects are missed.

--Jkyle

[Former Member · Accepted solution]

Let me explain all the steps i performed.

Objective is to add new field in the source system and BW system. Prereuisite is that custom field ZZ has been enhanced in the EBP Transaction data table and it is populated with the use of EBP BADI's. To enable reporting on the custom fields enhancement is required in the source system (EBP) and analytics system(BW).

Steps taken to move TR to QA system

1.Moved Transport Request(TR) of source system.

2.Moved TR of BW.

3. Replicated the Data Source.

4.Transport ended with status RC-8 and folowwing erro mesg

" Mapping between Data source(DS) and source system (SS) is inconsistent

field ZZ will nt be delivered from DS in SS.

Reference to transfer sturture not available. No activation possible. "

As a result of this error i was not able to see the new field ZZ in BW QA.

Now to rectify the error

1. Transported TR's of SS.

2. Replicated the DS.

3. Transported TR's of BW.

Now i was able to see the new field ZZ in BW QA system. But transported still ended up with status RC-8 and same error mesg.

So now my question is do i need to create new TR to move the chanegs to BW PRD or moving of same TR will not have any issue? Pls come up with single solution, that will be easy for me to follow.

Thansk & Regards,

Rohini

[somnathkumar · Accepted solution]

You got a RC8 in your second transport in the BW side. Just because you are able to see the field in BW does not solve the issue. You must investigate and take a corrective step and send a third transport on the BW side which should be transported without errors.

Once this is done, you should import all the 3 requests (2error and 1 correct) in the same sequence into production.

So the procedure should be, get the transport correct in BW, import all SS requests into prod, replicate datasources, import all BW requests into prod, activate transfer structure with RS_TRANSTRU_ACTIVATE_ALL.

[Former Member · Accepted solution]

Thanks Somnath

The third tranport shuld be realted to what all BW object? And what do you think is the possible cause of this error's.

And activating of transfer sturcture is last step?

Regards,

Rohini

[somnathkumar · Accepted solution]

1. You have said that the datasource is replicated in BW QA, check to see whether the field in visible in BW.

2. In Dev, under infosources, right-click on the transfer rule and choose 'Change Transfer rule'. Make some small chage (maybe delete and add the same field back again) so that when you activate it, it prompts for a transport request. Assign to a transport request. This should collect all the necessary objects for the transport.

Yes, successful activation of the transfer structure is the last step. After this just verify once again that the mapping is there.

[Former Member · Accepted solution]

Thanks you Somnath

Yes the new field is visible in BW QA system.And also data is getting uploaded succesfully in the ODS which has this new field. And this new field also have value in it.Can see that new field in the report also.

Got one last question

i will have to transport the old TR's(which ended up with error) also alsong with this new TR?

Will surely give u points.

Regards,

Rohini

[Former Member · Accepted solution]

Rohini,

as already said, if you don't like to run a risk, good sense require to transport everything you needed to reach a correct situation in your QA...that is, transport EVERY CR (correct and not) in your PRD as you already did from DEV, in the same sequence !

Bye,

Roberto

[somnathkumar · Accepted solution]

Hi Rohini,

Roberto is right. The practice in all projects is to transport all the request through all the systems in the same order. This way we can be 100% sure that all the systems are in sync.

This way even if there were 9 error requests, and one correct request in the end. When you transport all 10 in one go into production, you will not get any transport errors.

'All's well that ends well'.

[Former Member · Accepted solution]

Thanks to one and all for the prompt reply. This actually increases the trust in the forum.

I have at present rewarded equal points to every one, but u cn expect more points later.

Thanks once again

Rohini

[Former Member · Accepted solution]

Hi Rohini,

Kindly inform us any development on this matter. If it was solved, kindly share it to us.

--Jkyle

[Former Member · Accepted solution]

Hi Jkyle

I will surely update you once it is transported. But i can update only by Monday, because transport to prd is made only on Fri-Sun.

Thansk & Regards,

Rohini

[Former Member · Accepted solution]

Hi Guys (who took part in this post)

Thanks a lot for your quick response and solving my queries and for giving all possible correct solution.

Finally my CR is transported successfully tp production system wih absolutly no error's.

I had created a new CR with Transfer struct, but it was not required. My CR which ended up with RC-8 was moved successfully with no error.

Regards,

Rohini

Thanks once again. It was prd issue, so was bit scared.

[Former Member · Accepted solution]

Hi guys

I have also incresed the award points.

Thanks

Rohini

[Former Member]

Hi Rohini,

Sorry to interrupt.

What Roberto wants to know is, ok, for the first time u missed replication step and got RC-8 error.

But then second time u 'did' replicate in QA, and checked your objects in QA, and retransported the original request.. did you get the same error again? Why?.. maybe the problem is somewhere else..

Regards,

Vikrant.