Hi Florian,
Can you provide some more details? What is the product and have you done it for ESH_COCKPIT modeler?
Best regards,
Luke
Hi Luke!
I am using SAP ECC 60 SP8 5 on NW 702 SP5. When modelling in ESH_COCKPIT a new software component is a transport request assignment is created and the Software component is part of a transport request. This can even be seen in SE10 when looking at the transport request.
When creating a new Search Template or when enhancing an existing one this is not happening and therefore all modelling needs to be redone in the other systems and clients.
Regards
/Florian
Hi Florian,
The process for transporting TREX modeling configuration is different from the standard SAP transaport mechanism. Transports are performed the standard way, but setup of the system is required first. TREX transports, unlike standard transports, create a copy of the entire software component in the transport and do not refer to a backend table. In order to transport the manual correction instructions in SAP note 1483890 need to be implemented.
It is important to note that the RFC connection must be created in the target client. For example, RFC connection ES_APPL_ECQ_000_ECQ100_TRANS would be created in client ECQ/100. This is because the transport goes to client 000 of the target system and needs the RFC connection to move to the target client.
Once the system is setup the transports can be moved as per any other transport request.
Best regards,
Luke
Hi Luke!
Thank you for your reply.
I have implemented note 1483890 (even though it is stated that it only is required until NW 702 SP5 and we use SP7) and created a new software component and a new search template and released and transported it. The transport is looking fine and I do not get any warnings. When opening ESH_COCKPIT in the target system the newly created software component is not showing up there.
Regards
/Florian
Hi Florian,
What do you mean "I have implemented note 1483890"? It is not a corrective note - it is informative and you must read and follow the instructions in the note before doing any transport of your transport request.
Best regards,
Luke
Hi Luke!
I think it is both. It both contains a correction instruction and information about setting up the RFC connection and the message class. Nevertheless I wanted to say that I created the RFC destination but not the correction instruction (since the correction instruction is not relevant). I created the SW component after setting up the RFC connection.
Regards
/Florian
Hi Florian,
The note is a bit dubious, so please make sure you read my comments. I tried to summarize it a bit better than the note, because if you don't get it exactly right then it won't work. Make sure you create the right RFCs in the appropriate systems and clients. The transport goes into client 000 of the target system so an RFC needs to exist between client 000 and your target client. I hope I'm not being patronizing - I' m just trying to be clear since SAP made this process weirdly different from other transports!
Best regards,
Luke
Hi Luke!
Thank you for your efforts.
that is exactly what I did. I created the RFC destination in Quality system (target system) and then created a SW component, released the transport and imported it to quality system.
Regards
/Florian
Hi Alice,
I recommend you open an OSS message, since SAP will be able to help you.
Best regards,
Luke
Hi Luke!
that is what I did. Thanks for your help.
/Florian
No problem - let us know what SAP say.
Best regards,
Luke
Hi Luke!
finally some answers and help rom SAP.
There was some corruption i one of our ESH* tables. Additionally the roles described in the OSS note are not correct and needs some additional authorizations.
Thanks for your help.
/Florian
