Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SPRO: how do I transport node text?

Former Member
0 Likes
1,955

I've edited and existing structure in S_IMG_EXTENSION: added a node with two IMG-operations. Everything is just fine in the development system, the problem arose while moving changes to the QA system: node itself and both its IMG-subnodes were transported successfully, but the node text reads "Node text not found". Subnodes, at the same time, look and work just fine.

So, the question is: what do I do to transport the node text from the development system to QA and production? Thank you.

I've edited and existing structure in S_IMG_EXTENSION: added a node with two IMG-operations. Everything is just fine in the development system, the problem arose while moving changes to the QA system: node itself and both its IMG-subnodes were transported successfully, but the node text reads "Node text not found". Subnodes, at the same time, look and work just fine.

So, the question is: what do I do to transport the node text from the development system to QA and production? Thank you.

3 REPLIES 3
Read only

kiran_k8
Active Contributor
0 Likes
1,144

Alex,

May this is what you are looking for

K.Kiran.

Read only

Former Member
0 Likes
1,144

I've already checked the note 204433 as suggested: it's valid for 4.6 only, which is not my case. So, unfortunately, this is not a solution. Still thanks for looking into this.

P.S. My SAP_BASIS version is 731, SAP_APPL is 606.

Read only

Former Member
0 Likes
1,144

The whole issue turned out to be a languages problem. I've added my node to the "Production" structure which has German as original language, while I log in in Russian.

So, I've recreated the node having logged in in German, it has got transported to QA successfully, but I'm still not sure how this should be handled correctly in the future.