AW: AW: AW: Costom Object : Not getting Generated Properly, Metho d in Test Run Working,When called from Task giving short Dump
Schmidinger, Heinz (Unaxis IT BZ)
heinz.schmidinger at unaxis.com
Mon May 17 06:10:28 EDT 2004
it seems to me taht Element Y_POCO of BO BUS2105 is not a number, but =
it
shoud.
The problem raises if WI-Container should be moved to WF-Container.
Bets will be to check the object-result of the step.
-----Urspr=FCngliche Nachricht-----
Von: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]Im Auftrag von
Praveen Johri
Gesendet am: Montag, 17. Mai 2004 11:31
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: AW: AW: Costom Object : Not getting Generated Properly,
Method in Test Run Working,When called from Task giving short Dump
Ok here it is,
Runtime Errors CONVT_NO_NUMBER
Occurred on 05/17/2004 at 07:31:58
------------------------------------------------------------------------=
----
--------------
Unable to interpret "BOBUS2105 Y_POCO" as a number.
--------------
What happened?
--------------
Error in ABAP application program.
The current ABAP program "SAPLSWP1 " had to be terminated because one =
of
the
statements could not be executed.
This is probably due to an error in the ABAP program.
----------------
What can you do?
----------------
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and =
administer
termination messages, especially those beyond their normal deletion
date.
--------------
Error analysis
--------------
An exception occurred. This exception will be dealt with in more 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 "BOBUS2105 Y_POCO" as a
number,
but
since the value contravenes the rules for correct number formats,
this was not possible.
------------------------
How to correct the error
------------------------
Integers are represented in ABAP using a sequence of digits and, in =
some
cases, a preceding sign.
The system offers the following options for displaying floating point
numbers:
[sign][mantissa]E[sign][exponent]
[sign][whole number part].[fractional part]
e.g. -12E+34, +12E-34, 12E34, 12.34
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
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,
use the following search criteria:
------------------------------------------------------------------------=
"CONVT_NO_NUMBER" C
"SAPLSWP1 " or "LSWP1U56 "
"SWP_CALLBACK_WI_DONE"
------------------------------------------------------------------------=
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 or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
------------------
System environment
------------------
SAP Release.............. "620"
Application server....... "cscgd01"
Network address.......... "192.168.254.55"
Operating system......... "SunOS"
Release.................. "5.8"
Hardware type............ "sun4u"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 5
Short dump setting....... "full"
Database server.......... "cscgd01"
Database type............ "ORACLE"
Database name............ "E12"
Database owner........... "SAPR3"
Character set............ "en_US"
SAP kernel............... "620"
Created on............... "Jan 18 2004 22:58:53"
Created in............... "SunOS 5.8 Generic_108528-07 sun4u"
Database version......... "OCI_817_64 "
Patch level.............. "1283"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.*.*, ORACLE 9.2.0.*.*"
SAP database version..... "620"
Operating system......... "SunOS 5.8, SunOS 5.9"
--------------------
User, transaction...
--------------------
Client.............. 500
User................ "WF-BATCH"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSWP1 "
Screen.............. "SAPMSSY1 3004"
Row of screen....... 2
Information about program making the Remote Function Call (RFC):
System.............. "E12"
Database Release.... 620
Kernel Release...... 620
Connection type: 3 (2 =3D R/2, 3 =3D R/3, E =3D External, R =3D =
Reg.external)
Call type: "S-T-C0A8FE3703D140A84E4A2B71" (S =3D Synchronous, a/A =3D
Asynchronous,
T =3D Transaction)
Client.............. 500
User................ "WF-BATCH"
Transaction......... " (Program: SAPLERFC)"
Function module..... "ARFC_DEST_SHIP"
Call destination.... "WORKFLOW_LOCAL_500"
Source server....... "cscgd01_E12_00"
Source IP address... "192.168.254.55"
Additional RFC logon information:
Trusted Relation....." "
Logon return code....0
Trusted return code..0
Note: Prior to Release 4.0, there was less information available on RFC
calling programs.
-----------------------------------------
Information on where termination occurred
-----------------------------------------
The termination occurred in the ABAP program "SAPLSWP1 " in
"SWP_CALLBACK_WI_DONE".
The main program was "SAPMSSY1 ".
The termination occurred in line 207 of the source code of the =
(Include)
program "LSWP1U56 "
of the source code of program "LSWP1U56 " (when calling the editor =
2070).
-------------------
Source code extract
-------------------
001770 RAISE EXCEPTION TYPE =
cx_swf_run_wim_ignore_callback.
001780 * --->no log<---
001790 ENDIF.
001800 WHEN wi_status_cancelled.
001810 * avoid processing behind cancelled work item
001820 CALL METHOD l_cb_wi_handle->set_cb_done_to_db
001830 EXPORTING
001840 im_cb_done =3D 'X'.
001850 CALL METHOD l_cb_wi_handle->free( ).
001860 RAISE EXCEPTION TYPE =
cx_swf_run_wim_ignore_callback.
001870 * --->no log<---
001880 ENDCASE.
001890 ENDIF.
001900
001910
*--------------------------------------------------------------------*
001920 * begin of note 711722
001930 * the call of SWP_WI_RETURNCODE_GET must take place here!
001940 * get wi return code
001950 CALL FUNCTION 'SWP_WI_RETURNCODE_GET'
001960 EXPORTING
001970 wi_abap_container =3D wi_container_handle
001980 IMPORTING
001990 ex_exception =3D main_exception
002000 CHANGING
002010 wf =3D wf
002020 calling_back_wi =3D ls_calling_back_wi.
002030 * end of note 711722
002040
*--------------------------------------------------------------------*
002050
002060 * do import binding: dataflow from wi to wf-abap_container
-----> IF wf-abap_container <> wi_container_handle AND " if no
start_node
002080 l_cb_wi_handle->m_sww_wihead-wi_stat =3D
002090
*--------------------------------------------------------------------*
002100 * begin of note 711722
002110 * don't execute the binding if the callback has been triggered =
by
002120 * an administrator or a control step!
002130 * swfco_wi_status_completed.
002140 swfco_wi_status_completed AND
002150 ls_calling_back_wi-returncode <>
swfco_wi_rc_wi_obsolete.
002160 * end of note 711722
002170
*--------------------------------------------------------------------*
002180 CALL FUNCTION 'SWP_BINDING_EXECUTE'
002190 EXPORTING
002200 node_id =3D =
ls_calling_back_wi-node_id
002210 parforeach_index =3D =
ls_calling_back_wi-node_p_ind
002220 binding_type =3D binding_wf_to_wi
002230 dataflow_direction =3D 'I'
002240 error_text =3D 'vom Workitem zum
Workflow'(005)
002250 diagnose_message =3D $swp_cont_wi_wf
002260 IMPORTING
-------------------------
Contents of system fields
-------------------------
SY field contents..................... SY field
contents.....................
-------- ----------------------------- --------
-----------------------------
SY-SUBRC 0 SY-INDEX 1
SY-TABIX 0 SY-DBCNT 2
SY-FDPOS 1 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM SY-TITLE CPIC and RFC Control
SY-MSGTY E SY-MSGID WD
SY-MSGNO 327 SY-MSGV1 WS95000024
SY-MSGV2 0000 SY-MSGV3
SY-MSGV4
---------------------
Active calls / events
---------------------
No.... Type........ Name..........................
Program
Include Line
Class
-----------------------------------------------------
12 FUNCTION SWP_CALLBACK_WI_DONE
SAPLSWP1
LSWP1U56 207
11 METHOD IF_SWF_RUN_WIM_INTERNAL~EXECUTE_CALLBACK
CL_SWF_RUN_WIM_LOCAL=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DCP
CL_SWF_RUN_WIM_LOCAL=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DCM04A =
41
CL_SWF_RUN_WIM_LOCAL
10 FUNCTION SWW_WI_COMP_EVT_RECEIVE_INTERN
SAPLSWWA
LSWWAU61 187
9 FUNCTION SWW_WI_COMP_EVENT_RECEIVE
SAPLSWWA
LSWWAU32 76
8 FORM SWW_WI_COMP_EVENT_RECEIVE
SAPLSWWA
LSWWAV32 33
7 FORM XAB_RUN_DRIVER
SAPMSSY1
SAPMSSY1 254
6 FUNCTION RFC_RUN_XAB_DRIVER
SAPLSXAB
LSXABU01 9
5 FUNCTION ARFC_EXECUTE
SAPLERFC
LERFCU01 59
4 FUNCTION ARFC_DEST_SHIP
SAPLERFC
LERFCU02 229
3 FORM ARFC_DEST_SHIP
SAPLERFC
LERFCV02 28
2 FORM REMOTE_FUNCTION_CALL
SAPMSSY1
SAPMSSY1 69
1 MODULE (PBO) %_RFC_START
SAPMSSY1
SAPMSSY1 30
----------------
Chosen variables
----------------
------------------------------------------------------------------------=
----
--------------
12 FUNCTION SWP_CALLBACK_WI_DONE
SAPLSWP1
LSWP1U56 207
------------------------------------------------------------------------=
----
--------------
CALLED_IN_BACKGROUND X
5
8
CONTROL_WAIT_FOR_ENQ 00
33
00
DEBUG_FLAG
2
0
DO_COMMIT X
5
8
DO_SYNC_WI_CHAIN X
5
8
NO_CALLBACK_ON_COMPLETION
2
0
-----------------------
End of runtime analysis
-----------------------
Thanks & Regards
Praveen Johri
SAP Practice
Extn : 2597
Ph : 91-0120-2582323
Fax : 91-0120-2582322
Computer Science Corporation India Ltd.
------------------------------------------------------------------------=
----
------------
This is a PRIVATE message. If you are not the intended recipient, =
please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit =
written
agreement or government initiative expressly permitting the use of =
e-mail
for such purpose.
------------------------------------------------------------------------=
----
------------
=20
"Schmidinger, =20
Heinz (Unaxis IT To:
SAP-WUG at MITVMA.MIT.EDU
BZ)" cc: =20
<heinz.schmiding Subject: AW: AW: Costom
Object : Not getting Generated Properly, Method in Test Run
er Working,When called from =
Task
giving short Dump
@unaxis.com> =20
Sent by: SAP =20
Workflow =20
<Owner-SAP-WUG =20
=20
=20
05/17/2004 02:20 =20
PM =20
Please respond =20
to "SAP Workflow =20
Users' Group" =20
=20
=20
listserver doesn't accept attachments.
-----Urspr=FCngliche Nachricht-----
Von: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]Im Auftrag von
Praveen Johri
Gesendet am: Montag, 17. Mai 2004 10:48
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: AW: Costom Object : Not getting Generated Properly, Method
in Test Run Working,When called from Task giving short Dump
its giving
* do import binding: dataflow from wi to wf-abap_container
-----> IF wf-abap_container <> wi_container_handle AND " if no
start_node
in FM SWP_CALLBACK_WI_DONE
the ST22 dump is attached for ur reference
(See attached file: Dump.zip)
Thanks & Regards
Praveen Johri
SAP Practice
Extn : 2597
Ph : 91-0120-2582323
Fax : 91-0120-2582322
Computer Science Corporation India Ltd.
------------------------------------------------------------------------=
----
------------
This is a PRIVATE message. If you are not the intended recipient, =
please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit =
written
agreement or government initiative expressly permitting the use of =
e-mail
for such purpose.
------------------------------------------------------------------------=
----
------------
"Schmidinger,
Heinz (Unaxis IT To:
SAP-WUG at MITVMA.MIT.EDU
BZ)" cc:
<heinz.schmiding Subject: AW: Costom =
Object :
Not getting Generated Properly,Method in Test Run
er Working,When called from
Task
giving short Dump
@unaxis.com>
Sent by: SAP
Workflow
<Owner-SAP-WUG
05/17/2004 01:48
PM
Please respond
to "SAP Workflow
Users' Group"
Look into the short-dump, which field is raising die conversion-error.
Probaly you have filled it not numeric.
-----Urspr=FCngliche Nachricht-----
Von: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]Im Auftrag von
Praveen Johri
Gesendet am: Montag, 17. Mai 2004 09:56
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Costom Object : Not getting Generated Properly,Method in Test
Run Working,When called from Task giving short Dump
Hi Guys,
Something more to feed to ur thought process.
I m using Custom object for bus2105.I changed a few lines of code in =
it.
when trying to generate , it says object could not be =
generated......but
while checking it shows no syntax errors as i save it and change to =
display
mode and then try to generate or when i save it and come out of =
transaction
and then generate it it gets generated.When i instantiate the object =
the
method runs fine. But when i call it from task it gives me short dump =
with
CONVRT_NO_NUMBER error in SAP code. Initially the task is a background =
task
so in ST22 the user is WF-BATCH but while changing the processing type =
to
foreground the problem persist, Method is a synchronous type method.
I reverted back the changes, in mehtod then also it is not working
......prior o these changes method was working from task also.
Help me understand what is happening and why???..............more
importantly how to correct it.
Thanks & Regards
Praveen Johri
SAP Practice
Extn : 2597
Ph : 91-0120-2582323
Fax : 91-0120-2582322
Computer Science Corporation India Ltd.
------------------------------------------------------------------------=
----
------------
This is a PRIVATE message. If you are not the intended recipient, =
please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit =
written
agreement or government initiative expressly permitting the use of =
e-mail
for such purpose.
------------------------------------------------------------------------=
----
------------
More information about the SAP-WUG
mailing list