Regenerate sourcing dynpro

[Former Member]

Hi,

I would like to regenerate the sourcing dynpros but when i execute program BBP_DYNPROS_GENERATE and put either SAPLBBP_PDH_SOS or SAPLBBP_PDH_SOS_UI_ITS no screens are shown. Does anyone knows which program can i use in order to be able to see the relevant sourcing screens.

Regards,

Gigi

Message was edited by:

Goithoma Magdeline Maletsoa

[Former Member]

Good Day,

I've send message to SAP for further assitance. I will rely to the forum once i got the reply.

Regards,

Gigi

[Former Member]

Hi

Oh sure.. Any time. Waiting for your response eagerly. )

Regards

- Atul

[Former Member]

Hi

What is the exact requirement ? which SRM version you are using ?

<u>Meanwhile, Refer to follwoing OSS Notes which might help -></u>

785616 Displaying history at item level of a purchase order 

592137 Advance development: Vendor lists in sourcing tree 

647717 Descriptions with special characters in the sourcing screen 

635120 Scrolling in vendor list of the source of supply screen 

627769 Wrong display of order values (SAPLBBP_PDH_SOS_UI_ITS/1000)

Hope this will help.

Please reward suitable points.

Regards

- Atul

[Former Member]

Hi,

Why do you want to regenerate the screens for Sourcing?

BR,

Disha.

Pls reward points for useful answers.

[Former Member]

Hi Disha,

I need to regenerate them because they have been deleted as per note 632982. So i can't recover them.Therefore am encoutering an error in R/3 when distributing GOA as those one of those screens are utilised in MODULE CUSTSCR1_HEAD_SET_DATA OUTPUT.

Rgs,

Maggie

[Former Member]

Hi

Since it is quite old note. You can verify whether the sceens 0301 and others are still avialable in your system, by doing the following steps.

<b>It's related to the Transacation - SE51.</b>

<b>Put the progame name as 'SAPLBBP_SOCO_UI_ITS'. </b> and in the screen don't enter anything and Press F4 Key.

<u> In my system, I am having the following screens attached with thsi program - 'SAPLBBP_SOCO_UI_ITS'.</u>

-------------------------------------------------------------------
Program -> SAPLBBP_SOCO_UI_ITS                                          
-------------------------------------------------------------------
Screen No              Screen Description
-------------------------------------------------------------------     
  10 Grouping Information (Worklist & Search)                     
  20 Work Area for Subitems                                       
 100 Tab strip buttons (worklist/search)                          
 200 Work Area                                                    
 300 List of Shopping Cart Items                                  
1000 Main Screen for Sourcing Cockpit (Worklist and Work Area)    
1100 Worklist                                                     
2000 Main Screen for Search for Shopping Cart Items               
2100 Find                                                         
3000 Main Screen for Source of Supply Proposal                    
4000 Main Screen for Creation of Follow-On Objects                
4100 Preview of Follow-On Document(s)                             
5000 Main Screen for Shopping Cart     

Also, Log on to Transaction - SE80 and put the service name as <b>BBPSOCO01</b>

<u>Specially regenerate the mentioned screen templates -

0301, 0201, 0021, 0011</u>

<b>Regenerate the complete the service, by right click on the left hand side of the main service node and selct Pubish -> Complete Service.</b>

Hope this will help.

Please reward suitable points.

Regards

- Atul

[Former Member]

Hi Atul,

In my system it is exactly like in your side. In that case regeneration is not necessary, but my worry is R/3 is using screen 0201 and 0301, which them gibes me a short dump when distributing GOA,maybe i should change 201 to 200 and 301 to 300.

Regards,

Maggie

[Ramki]

Hi

The given note also mentions how to regenerate.

If you have a transport request created while deleting the screens, then do this:

1) Release the transport request

2) Goto Souricng screen. The screens will be automatically generated.

Pl let me know, if you still have problem.

Best regards

Ramki

[Former Member]

Hi

Please paste the detailed short dump details here by <b>using transaction - ST22</b>

at the earliest.

Hope this will help.

Please reward suitable points.

Regards

- Atul

[Former Member]

Hi Atul,

See Dump Below.

Error analysis

IIm Programm "SAPLXM06" wurde versucht, das Dynpro 0201 zu verwenden.Dieses Dynpro existiert nicht.

How to correct the error

Probably the only way to eliminate the error is to correct the program.

You may able to find an interim solution to the problem in the SAP note system. If you have access to the note system yourself, please use the following search criteria:

"SAPMM06E" "DYNPRO_NOT_FOUND"

If you cannot solve the problem yourself, please send the following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

-

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant

part.

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, you can either use the "PRINT" command in the editor

[Ramki]

Hi Gigi

1) System should have automatically generated the screens when you launch Carryout sourcing screens. First release the transport requests for SOCO screens, if any, and then launch the sourcing screens. Did you do that ?

2) Try this, if the above did not work:

A) start the report RSSCRPINT001

supply Program name -> SAPLBBP_SOCO_UI_ITS

Dynpro number -> 0301

Language -> EN

B) start the transaction SE80 (Object Navigator)

choose "Function Group" BBP_SOCO_UI_ITS

drill-down to "Screens"

choose screen (=dynpro) "0301"

activate the dynpro (CTRL + F3)

C) Repeat A& B above for the others screens - 0011, 0021, 0201- if necessary

Best regards

Ramki

[Former Member]

Hi

<b>Have you referred to OSS Note - 672960 ?</b>

<u>Here are the key points.</u>

<b>If you define fields for the first time, the system generates a screen for the display. If you create or delete fields, the screen must be regenerated. To do this, start report BBP_DYNPROS_GENERATE, change the proposed program to SAPLBBP_PDH_CUF and execute the report. Select the checkbox for the screens with the descriptions BBP_PDS_HCF for the table-like fields at the header and/or with the description BBP_PDS_ICF for the table-like fields at the item. You can use the 'Copy' button to enforce a regeneration of the screens.</b>

Hope this will help.

Please reward suitable points.

Regards

- Atul

[Former Member]

Hi Atul,

The attached note is for user defined fields. Since i didn't define any fields or changed screens.It doesn't help me much. And again, when i execute program SAPLBBP_PDH_CUF , i can only see screen 0510 without description.

Rgs,

Gigi

[yann_bouillut]

Hi,

This report doesn't exist...

I guess you mean BBP_DYNPROS_GENERATE

Kind regards,

Yann

[Former Member]

Hi Yann,

Yes, i mean BBP_DYNPROS_GENERATE.

Regards,

Gigi

[yann_bouillut]

Hi,

Did you try to restart the server ?

Kind regards,

Yann

[Former Member]

Hi Yann,

Do you mean that if i restart the server deleted screens will be back? Because what i need is to regenerate screens.

Regards,

Gigi

[yann_bouillut]

Hi Gigi,

Extract from OSS note 600410 :

"Two different paths are provided for the change of the generated screens.

a) A generated screen is deleted and regenerate automatically during the next call of the correponding transaction.

IMPORTANT !!!

During the deletion of the screen, the development system demands a transport request.

The best thing to do is to create a new transport request and to release it immediately. If the transport request is not released, the program prevents the regeneration of the screen and the transaction is terminated with an error message.

It is very important that the system is set up in such a way that exactly this screen is blocked in the transport request (object LIMU DYNP), not the entire function group.

If the changes which caused the regeneration of the screen (for example, the changes of the strucutre of the list) have not been transported yet, the transport of the transport request may lead to the deletion of the screen error. That is, delete the changes first and then the deletion. If this sequence is not possible, better use the second method for the generation of the screens.

b) Carry out report BBP_DYNPROS_GENERATE. Enter the name of search program SAPLBBP_PDH_SEARCH.Carry out this report.You see a table with all generated screens for the search results.Select the checkbox for the screens to be regenerated.Click the 'Copy' pushbutton.Then you do not need to delete the screen, it is overwritten.

IMPORTANT !!!

Remember the following: The selected screens are generated here (during the next call of the corresponding transaction), however, only in the development system. If you also need the regeneration in the production system, carry out the report there as well and do the same.

Consider that you have to activate the generated screesn after the implementation of Note 632691 and the generation of the screens with the translated texts.

"

Please confirm That you have proceed the same way .

Kind regards,

Yann

[Former Member]

Hi Yann,

I did try option 2 but i unfortunately i couldn't see any screen for sourcing.And I did ignore some of the notes as am on SRM server 5.5, SP 07, and most of the notes are below.

Rgs,

Gigi