cancel
Showing results for 
Search instead for 
Did you mean: 

Transport of a Transform failed with returned code 12

former_member316405
Participant
0 Kudos

Hi Experts,

I'm kind of new to SAP BW. I made changes to a Transform in my development system and the changes are working well in Development.But when I'm trying to move the transform to Testing system the transport is failing with returned code 12.I tried this several times and still getting the same error.

The datasource is CRM datasource and moving the data to a DSO.Please check the detail error below and please let me know how can I fix this.Also please let me know the process to move changes to an individual objects like transforms,datasources and DTPS.Thanks in Advance.

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member183519
Contributor
0 Kudos

Hi Niranjan,

Yes, as suggested by suhas, if RC=12 then basis team comes in the picture.

Let me know one thing, is the flow which u are created is already present in QUA/ your are transporting it first time to QUA ?

Also, many times , perticularly for CRM DS the process of replcating DS is not like BI, there are some tools(vary from project to project/company) which are doing that things for us.

So is there any thing like in your case ?

Regards,

Hitesh

former_member316405
Participant
0 Kudos

Hi Hitesh,

The flow already present in QA.I'm transporting the changes made to the transformation.

Thanks,

Niranjan

former_member183519
Contributor
0 Kudos

Hello Niranjan,

I guess problem is with replication.

Can u try to replicate DS in QUA, and then ask basis to re-import TR?

let us know what happend after this ?

Regards,

Hitesh

former_member185132
Active Contributor
0 Kudos

An RC of 12 in a TR usually indicates that the problem is with the transport mechanism, not the contents of the TR itself. It even says this in one of the message popups in the TR log.

So please check with your Basis team on this.

RamanKorrapati
Active Contributor
0 Kudos

Please send more details about error.

Above screen, try to expand + symbols and see the exact error information.

in your transformations have you used any material conversion?

former_member316405
Participant
0 Kudos

Hi Ramanjaneyulu,

Thanks for replying to my post.

I'm not using any material conversion in the transformation.0MATERIAL is directly mapped with the source field.Please help me.

bhavinvyas
Active Contributor
0 Kudos

Hi Niranjan,

Go to Transaction - OMSL

add Length = 18

Leave template as Blank

Tick the check box for Leading Zeros.

Save.

Now re-import the Transport.

Hope it Helps.

Thanks,

Bhavin Vyas

former_member316405
Participant
0 Kudos

Hi Bhavin,

Thanks for replying. I will try that in my development system.When moving a transformation into Testing system can I move only that object or Should I include in other objects like Datasource,DTP and DSOs? How will the system know that this transformation belongs to a particular DSO if I just transport the transformation? Please help me understand this.

Many Thanks!

RamanKorrapati
Active Contributor
0 Kudos

please exapnd + symbol and share more information about error.

Please explore more about BW and transports.

There are plenty of docs/pdfs and discussion about transports, please find and understand it.

Please use google serach key as "Step by step procedure to transport SAP BI/BW :.

former_member316405
Participant
0 Kudos

Please check the attached Transport error report.

RamanKorrapati
Active Contributor
0 Kudos

In future , please share information on open/readable format instead of zip.

Coming to error:

Before transporting, have you tested your load at bw dev system?

is your transformations are active at bw dev system?

Your transformation have lot of formula/routines. so please do the test at dev system and check it.

if issues exist there then rectify it.

Later collect into new transport request and import to Qua.

former_member316405
Participant
0 Kudos

Sure! Yes I've tested it in my Dev system and all the objects in the dataflow are active.

bhavinvyas
Active Contributor
0 Kudos

Hi Niranjan,

If it was working in development then this setting was already there in Dev. Please check OMSL setting in Dev First.

If it is there then please check the same in BW prod.

Thanks,

Bhavin Vyas