Transport Print Workbench Languages translations across clients

[Former Member]

Hi,

I am having a strange problem.

I have created an application form (EFRM) in Spanish (ES) and maintained translations in Gallego (GL) and Catalan (CA) in the development client.

I am unable to move it to the testing client using SCC1. (EN and ES move successfully to the testing client, GL and CA do not).

I have maintained all the language dependent components in all 4 languages i.e sap script, text elements and application forms, however i am unable to transport to the testing client.

Your time and effort to help me out is appreciated.

Thanks in advance,

Averil Lobo

[nils_buerckel · Accepted solution]

Hi Averil,

can you please check SAP note 45548 ?

Best regards,

Nils Buerckel

SAP AG

[Former Member]

Thanks Nils,

Firstly, I have gone through the note 45548 you suggested and it talks about controlling the transport of language dependent objects my modifying the file /usr/sap/trans/bin/TPPARAM which i believe will be generated by the STMS transaction (Transport Management System.

The problem is no such file is created in the system.

Secondly, since the translation in maintained in the development client and cannot be transported to the testing client the issue seems to be while using transaction SCC1.

So I tried debugging SCC1 and have analysed the tables referenced (Customizing and Object Specific) and found that the T002C is being reference to generate the language vector. The languages installed are German, English and Spanish and hence the language vector DES.

My question is can someone confirm if translations of language dependent objects can only be transported for installed lanaguages. (In my case DES)?

Thanks once again for your time and effort!

Regards,

Averil Lobo.

[nils_buerckel]

Hi Averil,

can you please use report RSCPINST (see SAP note 42305) to define the mentioned languages and retry.

Best regards,

Nils Buerckel

[Former Member]

Hi Nils,

I checked the installed languages by Report RSCPINST but here the language GL (Gallegan) is already installaled.

As I mentioned earlier the table T002C is validated during transaction SCC1.

As of now I have found a work-around so that I dont need to use the GL language forms. However, I am still looking to the resolution of this issue.

Thanks again for your time.

Regards

Averil Lobo