cancel
Showing results for 
Search instead for 
Did you mean: 

WebDynpro Error while creating a Purchase Order in SRM 7.0

Former Member
0 Kudos

Hello Friends,

I need help.

We are on SRM 7.0 with support pack 8.0 and we are getting the below error wile clicking on Shopping cart or Purchase Order link in Portal.

Any idea on how to resolve this error.

Thanks

Jyothi.

http://sapsrm.erpcx.com:8000/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif/

ASSERTION_FAILED

The ASSERT condition was violated.

Method: ADD_EVENT_TO_QUEUE of program CL_FPM========================CP

Method: IF_FPM~RAISE_EVENT of program CL_FPM========================CP

Method: SET_CREATE_BUTTON_ACTIVE of program /1BCWDY/0FJM4718F184UKVHA34J==CP

Method: IF_COMPONENTCONTROLLER~SET_CREATE_BUTTON_ACTIVE of program /1BCWDY/0FJM4718F184UKVHA34J==CP

Method: RESET_SCREEN of program /1BCWDY/0FJM4718F184UKVHA34J==CP

Method: IF_V_PRSEL~RESET_SCREEN of program /1BCWDY/0FJM4718F184UKVHA34J==CP

Method: WDDOMODIFYVIEW of program /1BCWDY/0FJM4718F184UKVHA34J==CP

Method: IF_WDR_VIEW_DELEGATE~WD_DO_MODIFY_VIEW of program /1BCWDY/0FJM4718F184UKVHA34J==CP

Method: DO_MODIFY_VIEW of program CL_WDR_DELEGATING_VIEW========CP

Method: MODIFY_VIEW of program CL_WDR_VIEW===================CP

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello, we are running into the exact same issue.  Has anyone come up with how they fixed this issue?

Former Member
0 Kudos
Former Member
0 Kudos

Hi Jyothi,

We are SRM 7.0 SP06 and having exactly the same problem. Could you tell me what you did to solve the problem? Thanks

Tiffany.

Former Member
0 Kudos

Guys can you please share solution for this issue. Thanks

thomas_jung
Developer Advocate
Developer Advocate
0 Kudos

There isn't enough information here to comment on the true root cause of the error. An assert condition just means that something went wrong, but doesn't tell you what. You should check transaction ST22. There should be a short dump with more details about the error. Often the area of code near where the assertion was thrown will show you the condition the logic was testing upon.

Former Member
0 Kudos

Here is what I see:

Error analysis |

The following checkpoint group was used: "No checkpoint group specified"

If in the ASSERT statement the addition FIELDS was used, you can find

the content of the first 8 specified fields in the following overview:

" (not used) "

" (not used) "

" (not used) "

" (not used) "

" (not used) "

" (not used) "

" (not used) "

" (not used) "

-


-


How to correct the error

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

-

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"ASSERTION_FAILED" " "

"CL_FPM========================CP" or "CL_FPM========================CM004"

"ADD_EVENT_TO_QUEUE"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

|

thomas_jung
Developer Advocate
Developer Advocate
0 Kudos

This section of the short dump is fairly meaningless. You probably want to post the section with the source code that triggered the dump.

If you are having problems with the troubleshooting and this is an unmodified standard SAP application; perhaps you should just open a support ticket and assistance from SAP.