Problems in transporting a Software Component Version (SWCV)

[Former Member]

HI,

We have developed a SWCV in Mobile 7.1 DOE (System development).RFC destination is our own development.

We transported the SWCV to our System Test.

The problem is that the RFC destination is blank.

We have created the RFC destination (System Test) but we can not change the SWCV to introduce each Data Object your RFC Destination.

Once created RFC Destination We transported the SWCV again and RFC Destination remains blank.

Any Idea?

Maria Elena

[Former Member]

OK

Best regards

[former_member196472]

Hi,

Backend destination is system as well as client specific. So destination is not being copied while transporting SWCV. Further,

if two or more clients are present in a system, we have to set the destination for SCV in each and every client. So you can set RFC destination of SCV at target system as mentioned by Dhana and Ramanath.

Regards,

Ashish.

[Former Member]

Hi,

RFC Destination is something very specific between 2 systems. So during transport of SWCV, we do not copy the RFC destination. (Because this RFC might not hold good in the target system).

Once the SWCV reaches the target system, you can either maintain the RFC destination using the portal as mentioned by Dhana above, or else you can go to SDOE_WB transaction and change the RFC destination of the SWCV.

Note: You dont have to mark this for all the data objects in that SWCV. Maintaining it at the SWCV level is enough.

Regards,

Ramanath.

[Former Member]

Hi,

The RFC destinations will not be copied while transporting SCV.

In target system you can do a configuration in Netweaver mobile admin portal.

Go to Portal->Configuration->Backend Configuration

configure BACKEND_DESTINATION for your SCV.

Regards,

Dhana