topic Re: Error in BAPI in Application Development and Automation Discussions

Error in BAPI

Former Member — Thu, 05 Mar 2009 08:04:31 GMT

Hi Experts,

We are creating articles in mm42 in IS retail through BDC (which we inherited from ECC5.0) which also have an bapi BAPI_MATERIAL_GETCHARMERCHHIER for addition of characteristic values. while uploading the Tab separated TXT file. It is giving runtime error CONVT_NO_NUMBER on creation of 12th article. The dump analysis says

Runtime Errors CONVT_NO_NUMBER

Date and Time 03.03.2009 19:27:38

Short text

| Unable to interpret "*0" as a number.

Thanks and regards,

Amit

Re: Error in BAPI

former_member632729 — Thu, 05 Mar 2009 08:06:54 GMT

Hi Dude,

Before Calling BAPI .. use the conversion rotine. for Data and Time.. And then Pass those values to BAPI..

Re: Error in BAPI

Former Member — Thu, 05 Mar 2009 08:31:34 GMT

Here is complete dump error

Runtime Errors CONVT_NO_NUMBER

Date and Time 03.03.2009 19:27:38

Short text

Unable to interpret "*0" as a number.

What happened?

Error in the ABAP Application Program

The current ABAP program "Y_MM_SINGLEART_BDC_COPY" had to be terminated because

it has

come across a statement that unfortunately cannot be executed.

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 that is explained in detail below.

This exception cannot be caught in the context of the current statement.

The reason for the exception is:

The program attempted to interpret the value "*0" as a number, but

since the value contravenes the rules for correct number formats,

this was not possible.

How to correct the error

Whole numbers are represented in ABAP as a sequence of numbers, possibly

with an algebraic sign.

The following are the possibilities for the representation of floating

point numbers:

[algebraic sign][mantissa]E[algebraic sign][exponent]

[algebraic sign][whole number part].[fraction part]

For example, -12E+34, +12E-34, 12E34, 12.34

If the error occurred in your own ABAP program or in an SAP

program you modified, try to remove 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:

"CONVT_NO_NUMBER" " "

"Y_MM_SINGLEART_BDC_COPY" or "Y_MM_SINGLEART_BDC_COPY"

"ADD_CHAR"

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)".

Information on where terminated

Termination occurred in the ABAP program "Y_MM_SINGLEART_BDC_COPY" - in

"ADD_CHAR".

The main program was "Y_MM_SINGLEART_BDC_COPY ".

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

of the (Include) program "Y_MM_SINGLEART_BDC_COPY".

Source Code Extract

Line

SourceCde

893	wa_tab1-zatwrt = wa_main-mwert1.
894	APPEND wa_tab1 TO tab1.
895	CLEAR wa_tab1.
896
897	wa_tab1-zatwrt = wa_main-mwert2.
898	APPEND wa_tab1 TO tab1.
899	CLEAR wa_tab1.
900
901	wa_tab1-zatwrt = wa_main-mwert3.
902	APPEND wa_tab1 TO tab1.
903	CLEAR wa_tab1.
904
905	wa_tab1-zatwrt = wa_main-mwert4.
906	APPEND wa_tab1 TO tab1.
907	CLEAR wa_tab1.
908
909	wa_tab1-zatwrt = wa_main-mwert5.
910	APPEND wa_tab1 TO tab1.
911	CLEAR wa_tab1.
912
913	wa_tab1-zatwrt = wa_main-mwert6.
914	APPEND wa_tab1 TO tab1.
915	CLEAR wa_tab1.
916
917	DESCRIBE TABLE i_characterstic LINES count.
918
919	CLEAR: wa_tab2, wa_tab1.
920
921	DO count TIMES.
922	READ TABLE tab2 INDEX n INTO wa_tab2.
>>>>>	MOVE wa_tab2 TO wa_final-atnam.
924
925	READ TABLE tab1 INDEX n INTO wa_tab1.
926	MOVE wa_tab1 TO wa_final-atwrt.
927
928	APPEND wa_final TO tab_final.
929	CLEAR wa_final.
930
931	n = n + 1.
932
933	ENDDO.
934
935	i_header-material = zmatnr_final.
936	i_header-matl_type = wa_main-mtart.
937	i_header-matl_group = wa_main-matkl.
938	i_header-matl_cat = wa_main-attyp.
939	i_header-char_prof = z_wghier-clas1.
940	i_header-basic_view = 'X'.
941
942	i_char-material = zmatnr_final.

Re: Error in BAPI

Former Member — Thu, 05 Mar 2009 08:37:14 GMT


> Short text                                                                                
> Unable to interpret "*0" as a number.
>

Doesn't that answer your question ? *0 is definitely not a number so it will give an error.

regards,

Advait

Re: Error in BAPI

Former Member — Thu, 05 Mar 2009 08:52:24 GMT

Thanks Advait,

But how to rectify it?

rgrds,

amit

Re: Error in BAPI

Former Member — Thu, 05 Mar 2009 08:56:48 GMT

Hi,

Fill all the fields of the workarea and then append it in internal table once at the end only dont append each field separately.

Cheers,

Surinder

Re: Error in BAPI

Former Member — Thu, 05 Mar 2009 09:50:46 GMT

Hi Amit,

You need to check your source file and see which record has a * it and rectify the record in the file and reload it.

regards,

Advait

Re: Error in BAPI

Former Member — Thu, 05 Mar 2009 10:14:25 GMT

Hi Amit,

Dont understand what kind f tables your tab1 and tab2 are.... however ensure wa_tab2 is not longer than your wa_final-atnam.. even if these tables contain only one field you should have used the field name while moving data... hope u solve your problem and correct ur code

READ TABLE tab2 INDEX n INTO wa_tab2.

MOVE wa_tab2 TO wa_final-atnam.

924

925 READ TABLE tab1 INDEX n INTO wa_tab1.

926 MOVE wa_tab1 TO wa_final-atwrt.

927

928 APPEND wa_final TO tab_final.

929 CLEAR wa_final.

Re: Error in BAPI

Former Member — Fri, 06 Mar 2009 12:06:45 GMT

The problem is resolved.

The internal tables were not getting cleared properly.

rgrds,

Amit