cancel
Showing results for 
Search instead for 
Did you mean: 

Webdynpro debug

Former Member
0 Kudos

Hi,

does anybody know how to debug webdynpro? we are working with SRM and MDM, but as there is a bug in webdynpro, we need to find the root cause and remove it.

Thank you very much for your help.

Katarina

Accepted Solutions (1)

Accepted Solutions (1)

dean_hinson2
Active Contributor
0 Kudos

I think this is what you want...

In SE38...or SE80, go to menu bar option Utilities(M) --> Settings. Click tab Abap Editor then sub-tab Debugging. Make sure the New Debugger and Session Breakpoints Active Immed is checked.

Then in the program, use the External Breakpoint ( Stop Sign with the little world in the upper right).

See if that helps...

Regards, Dean.

Former Member
0 Kudos

could you please tell me which program should be used in se38?

thank you

katarina

dean_hinson2
Active Contributor
0 Kudos

What program are you getting the bug in? Are you getting a short dump? Then use that program.

BTW, if this is not home grown, did you check OSS? Just a thought.

Regards, Dean.

Former Member
0 Kudos

which OSS number you mean? need to check then...

dean_hinson2
Active Contributor
0 Kudos

Katarina,

I do not know the OSS note that you might need to apply. Did you search OSS for the particular problem you are encountering? Are you getting short dumps? What ever you are noticing should help you with determing how to search the OSS note database.

Regards, Dean.

Former Member
0 Kudos

So far, I have found one OSS note: 1238078 Obtain catalog information from cross catalog search agent. It is about: SRM does not import the catalog information from BBP_OCI_AGENT search service as part of the OCI. This leads to loss of catalog information in item data in SRM.

I suppose this might be the correct OSS note. It relates to Package SAPKA70018. We are using SAPKA70017. Do you think that implementing of this OSS would help to solve the issue? Another thing is, that once we want to transfer the chosen item to shopping cart, there is an error message which appears: Function parameter "ET_CATALOG_ID" is unknown. I have not seen this before and am not sure whether this relates to the OSS note or not. I could not find any similar issue on SAP Forum neither. Can you advise?

thank you very much for all valuable information

Katarina

Former Member
0 Kudos

We implemented OSS note 1238078 - Obtain catalog information from cross catalog search agent and performed testing in Development and Quality and it helped to solved the issue with the unknown function module. However, the problem with the pricing still remains. How to find the root cause? We still see more prices in one catalog item if we want to choose from the catalog.

thank you for any hints.

katarina

dean_hinson2
Active Contributor
0 Kudos

Sorry for not replying sooner, I have been very busy. Glad the OSS Note worked. Could there be another OSS Note for your other problem? I really don't understand the pricing issue, so if you could provide a little more detail, it would help.

Regards, Dean.

Former Member
0 Kudos

Dean,

The pricing issue is following:

We are using integrated (internal) catalogs, so the Purchasor uploads catalogs via MDM Import Manager. I have already raised another question which relates to MDM upload problem, but so far there is no satisfiable answer. Please see my question: SRM MDM Import Manager - price upload.

To summarize: once the Purchasor uploads new prices (valid for 2009), we see in our integrated catalog two prices (the old and the new one). When we choose the new one, the old price is transferred to SC. Basically, we think that it is a webdynpro bug, but do not know how to remove it. We contacted SAP via message as well, but they replied following: This issue is an enhancement request as the #Filter# option on the

qualified display is not saved as part of the Saved Name search. It is

working the same way in Data Manager, but the default view includes the

filter checked and therefore it seems to worked differently.

The standard SRM-MDM Catalog uses namedsearch just for search but not

for filtering any values (price etc).

This is not acceptable for us, as we think the problem is somewhere else but we are unable to find the root cause. If you have any hints or tips, please share. Thank you very much.

Katarina

dean_hinson2
Active Contributor
0 Kudos

Katarina,

We are currently not using MDM (wish we were), so I do not think I can help further on this particualr issue. However, did you search OSS for MDM and price/pricing?

I wish I was more familar with MDM. Also, you might want to look at the data upload. It could be a data issue.

I wish you the best in getting this resolved.

Regards, Dean.

Answers (0)