Launchpad text transport issue

[Former Member]

Hello Experts,

My client is on EHP6.I have created a launchpad by copying from standard ESS(Menu) launchpad. I have saved this Launchpad with the Namespace 'Z' and respective  TR's(Customizing & Workbench) got generated for this Launchpad. Now when i transported these TR's into Quality, No text is appearing for the applications and launchpad(Description in language English doesn't exists). Can you please let me know how to transport the text. Please see the screenshots attached.

I tried to run the report APB_LPD_SHOW_TEXT_KEYS and i can see the missing entries(Texts created by customer) in Qulaity system.

Then i tried to follow this procedure

"

If you have not yet transported the launchpad, you first have to include the texts in a workbench transport request.

This means the texts are stored as General Texts (TX) with the prefix "LP*LECD0000008".

2. In the Easy Access menu, choose Tools -> ABAP Workbench -> Utilities -> Translation -> Short and Long Texts (SE63).

3. You then choose Translation -> ABAP Objects -> LongTexts (Documentation).

You branch to the dialog box Object Type Selection.

4. Expand the node C6 F1 Help and double-click on TX   General Texts.

5. To select the text, enter "LP*LECD0000008*" in the field Object Name and "999999" as the Translation Area.

"

When i try to search the object name For ex 'LP*LECD0000009000000' or LP**, i am not getting any object related to this. Can you please guide how to go ahead on this and add the concerned objects in the transport request.

Thanks & Regards

Sahil Kohli

[siddharthrajora · Accepted solution]

to fix the issue you need to implement the corrections of note 1786881.

After this., you need to transport the launchpad again to get the missing texts in your  system.

The problem is that the transport key R3TR LPDC .... contains at the

end a '%'. At this reason no texts are found and so no texts are

transported. The same issue occurs in the translation what is described

in the note.

so apply the note from where you originate the transport

[Former Member · Accepted solution]

Hi Siddharth,

Thanks for your response.

This note(1786881) is having the dependency on the note 1768132 & 1680522 . Should i only implement the corrections for all these notes or implement complete note? Also please tell in case of launchpad transport, which TR should be moved first(Workbench or customizing)?

Regards

Sahil Kohli

[siddharthrajora · Accepted solution]

You need to implement all the notes, there was a bug to resolved it apply all pre reqs notes etc

[Former Member · Accepted solution]

Hi Siddharth,

We implemented the manual corrections & the notes in development client but issue still remains the same. Please suggest.

Thanks & Regards

Sahil Kohli

[siddharthrajora · Accepted solution]

what error you get now? Did you follow the steps?

[Former Member · Accepted solution]

Hi Sahil,

We have the same issue as well! We are on EHP6. Even after implementing 3 notes and creating fresh transport requests (workbench and customizing) and moving to it to QA. We have the same issue.

1) 1768132

2) 1680522

3) 1786881

Siddharth - Any thoughts?

[siddharthrajora · Accepted solution]

you need to apply note 1714746 and 1702081. as well

If you want to correct this problem for existing launchpads, execute the

program APB_LPD_RESET_CV_ADAPTED for the affected launchpads.

and ensure correct namespace is given ie Z and package name

[Former Member · Accepted solution]

Thanks Siddharth. 1702081 is released in German. Do you have the english version?

Do you want me to execute the report APB_LPD_RESET_CV_ADAPTED in QA where the launchpad is broken? And is this report alternative to the applying the above notes or have to this in addition to these notes.

[siddharthrajora · Accepted solution]

Its a new note, but you can apply it even it its in DE, here is the sympton

Symptom
When you transport a launchpad, the system issues error message TO 142:
'SAP object DOCT L... cannot be assigned to package &3'.

Other terms
Floorplan Manager, FPM, FPM navigation, report launchpad, LPD_CUST

Reason and Prerequisites
The system issues this error message if the namespace of the launchpad
texts does not match the namespace of the package that used.

Solution
When you create the launchpad, you must ensure that you enter the
correct namespace. To solve the problem for existing launchpads, proceed
as follows:

Copy the affected launchpad to a different role or instance. Delete the
launchpad. Copy the launchpad back to the previous role or instance.
Enter the correct namespace in the creation dialog box.

If the package begins with Z, the namespace is Z. Do not use the
namespace /0CUST/ under any circumstances. If you do, the system will
issue error message TO 142 again during the transport process.

[Former Member · Accepted solution]

Thanks Siddharth! But we don't have the above Symptom. Or where do we look for this issue?

Do you still think we should implement this note?

Symptom

When you transport a launchpad, the system issues error message TO 142:

'SAP object DOCT L... cannot be assigned to package &3'.

[siddharthrajora · Accepted solution]

yes i know, but there are many bugs, so apply the note and please test again and let us know if you have further issues

[Former Member · Accepted solution]

Hi Siddharth,

As per our BASIS team, Out of two notes mentioned only 1714746 can be applied the second one(1702081) is obsolete as all the ECC systems are already running on SAPKB73104.

We have applied this note(1714746 ), but the issue is still the same 😞

The difference i can see now is when i save my new launchpad in Dev client, apart from Customizing and Workbench request, it gives a pop up for one more workbench request (APB_LPD_TRANSLOG). Please see the below screenshots.

Appreciate your help on this.

Thanks & Regards

Sahil Kohli

[siddharthrajora · Accepted solution]

after creating this, still no successful transport of texts?

what is the package name and namespace used, this is critical

[Former Member · Accepted solution]

Hi Siddharth,

Yes, still the same issue"Description in language English doesn't exists". I am using the below values. In the namespace, I have given the value 'Z'. Where do i need to specify Package name?

Thanks & Regards

Sahil Kohli

[former_member87990]

I am having the same issue. Was there a solution found for this ever?    

[Former Member]

hi siddharth ,

Can you make process in a simple way in transporting this launchpad without creating any difficulty,as this lengthy process is creating confusion , suggest you to give solution for this transport issue as simple as that like general transport , as initially we have faced lot of problems  in doing this.