PO output in SRM

[Former Member]

Hi chaps,

We are running ECV. I'm getting an error, 'unable to interpret C1 as a number'. When I click on Preview Output for a PO. Anyone come across this error and knows what it means??

Regards

TV

[Former Member]

Hi

<b>Which SRM version are you using ? Could you please paste complete ST22 - dump details in next reply... ?</b>

<i>When this error is happening.. ?</i>

<u>Meanwhile, please go through the following SAP OSS Notes -></u>

<u>Note 1107999 Purchase Order not updated correctly</u>

<b>Note 1036361 ShoppingCart appl.dumps:Unable to interpret "OP" as a number</b>

Note 447854 EBP, Catalog (OCI): Short dump when value >= 1,000.00

Note 1044100 'CONVT_NO_NUMBER' program termination in conditions

Do let me know.

Regards

- Atul

[Former Member]

Atul,

SRM Extended Classic Version 5.0.

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_BBP_PD_ABORT

Date and Time 26.11.2007 12:18:06

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_BBP_PD_ABORT

Date and Time 26.11.2007 12:18:06

Short text

An exception occurred that was not caught.

What happened?

The exception 'CX_BBP_PD_ABORT' was raised, but it was not caught anywhere

along the call hierarchy.

Since exceptions represent error situations and this error was not

adequately responded to, the running ABAP program 'SAPLBBP_PDH' has to be

terminated.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

An exception occurred which is explained in detail below.

The exception, which is assigned to class 'CX_BBP_PD_ABORT', was not caught and

therefore caused a runtime error.

The reason for the exception is:

Übernehmen

to correct the error

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:

"UNCAUGHT_EXCEPTION" "CX_BBP_PD_ABORT"

"SAPLBBP_PDH" or "LBBP_PDHU08"

"BBP_PD_ABORT"

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.

System environment

SAP-Release 700

User and Transaction

Client.............. 400

User................ "SPHILBIN"

Language Key........ "E"

Transaction......... "BBP_POC_EDIT "

Program............. "SAPLBBP_PDH"

Screen.............. "SAPLBBP_PO_UI_ITS 1000"

Screen Line......... 4

Information on where terminated

Termination occurred in the ABAP program "SAPLBBP_PDH" - in "

The main program was "SAPLBBP_PO_UI_ITS ".

In the source code you have the termination point in line 73

of the (Include) program "LBBP_PDHU08".

Rgds

TV

[Former Member]

This is the error in SRM:

Error when processing your request

What has happened?

The URL https://ofcomlcys008.extra.ofcom.local:/sap/bc/gui/sap/its/bbp_poc/~flNUQVRFPTE3NTgxLjAwNy4wNC4wOQ== was not called due to an error.

Note

The following error text was processed in the system SR3 : Unable to interpret C1 as a number.

The error occurred on the application server OFCOMLCYS008_SR3_00 and in the work process 1 .

The termination type was: RABAX_STATE

The ABAP call stack was:

Form: %WI10_BODY of program /1BCDWB/SAPLSF00000004

Form: %WI10 of program /1BCDWB/SAPLSF00000004

Form: CALLBACK of program SAPLSTXBC

Form: PROCESS_TEXT_WINDOW of program SAPLSTXBC

Form: PROCESS_NON_MAIN of program SAPLSTXBC

Form: PROCESS_WIN_BEFORE_MAIN of program SAPLSTXBC

Function: SSFCOMP_PROCESS_DOCUMENT of program SAPLSTXBC

Function: /1BCDWB/SF00000004 of program /1BCDWB/SAPLSF00000004

Function: BBP_OUTPUT_PO_PREVIEW_SMART of program SAPLBBP_OUTPUT

Form: PREVIEW_PO of program SAPLBBP_PO_APP

What can I do?

If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SR3 in transaction ST22.

If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server OFCOMLCYS008_SR3_00 in transaction SM21.

If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server OFCOMLCYS008_SR3_00 . In some situations, you may also need to analyze the trace files of other work processes.

If you do not yet have a user ID, contact your system administrator.

Error code: ICF-IE-https -c: 400 -u: AHANCOX -l: E -s: SR3 -i: OFCOMLCYS008_SR3_00 -w: 1 -d: 20071128 -t: 100152 -v: RABAX_STATE -e: CONVT_NO_NUMBER

[Former Member]

Hi

<u>Which SRM version are you using ? Seems like a sure shot missing SAP OSS Note (Due to SAP bug).</u>

<u><b>Please go through this -></b></u>

Note 895932 - Dump after applying note 895171

Note 895171 - Unsynchronized follow-on document indicator in extended PO

Note 858570 - Error CONVT_NO_NUMBER in Purchase Orders

Note 906151 - Follow on correction for note 895171

Note 1023130 - Finally Invoice indicator can not be cleared

<u>Do let me know. Hope this will definitely help.</u>

Regards

- Atul

[Former Member]

Thanks Atul,

where can I find the final_entry indicator 'X' as mentioned in note 895171?

[Former Member]

Hi

<b>Implement the SAP OSS Note using SNOTE transaction .. the correction instruction given in note 895171</b>

<u><b>Please go through this -></b></u>

<u>Related OSS Note -></u>

Note 794467 - Update of pricing document in change version fails

<u>Program ID Object Type Object Name Program ID Object Type Object Name

LIMU REPS LBBP_PDIGPF14 R3TR FUGR BBP_PDIGP </u>

* note 895171
* adding logic to ignore changes related to the follow-on indicator
* that is being set int he backend system but not synchronized in SRM
  IF w_itmigp-final_entry EQ gc_to_set AND   " BE value X transformed
     old_itmigp-final_entry IS INITIAL AND   " SRM DB value
     new_itmigp-final_entry EQ c_on.         " SRM thinks it's the user update
   new_itmigp-final_entry = gc_off.    " in fact there is really no change from SRM side
  ENDIF.
  IF w_itmigp-final_inv EQ gc_to_set AND     " same logic for invoicing
     old_itmigp-final_inv IS INITIAL AND
     new_itmigp-final_inv EQ c_on.
   new_itmigp-final_inv = gc_off.
  ENDIF.

* something changed ?

<u>Do let me know. Hope this will definitely help.</u>

Regards

- Atul