CALL_FUNCTION_CONFLICT_LENG
Hi gurus,
I got short dump CALL_FUNCTION_CONFLICT_LENG .
could you please suggest me how to rectify this problem?
Please find the below runtime error details.
Runtime Error CALL_FUNCTION_CONFLICT_LENG
Exception CX_SY_DYN_CALL_ILLEGAL_TYPE
Occurred on 15.12.2008 at 12:00:23
Type conflict when calling a function module (field length).
What happened?
Error in ABAP application program.
The current ABAP program "SAPLZDELVCONF" had to be terminated because one of
the
statements could not be executed.
This is probably due to an error in the ABAP program.
A function module was called incorrectly.
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 is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE',
was neither
caught nor passed along using a RAISING clause, in the procedure
"ZIDOC_INPUT_ZDELVCONF" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The call to the function module "BAPI_OUTB_DELIVERY_CONFIRM_DEC" is incorrect:
In the function module interface, you can specify only
fields of a specific type and length under "HEADER_CONTROL".
Although the currently specified field
"V_BAPIOBDLVHDRCTRLCON" is the correct type, its length is incorrect.
How to correct the error
The exception must either be prevented, caught within the procedure
"ZIDOC_INPUT_ZDELVCONF"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
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:
"CALL_FUNCTION_CONFLICT_LENG" CX_SY_DYN_CALL_ILLEGAL_TYPEC
"SAPLZDELVCONF" or "LZDELVCONFU01"
"ZIDOC_INPUT_ZDELVCONF"
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.
If the error occurs in the program SAPCNVE, it could be for any of
the following reasons:
1. The field <INPUT> conflicts with a function module called
"..._INPUT" or the field <OUTPUT> with "..._OUTPUT".
This is probably due to an error in the definition of the
function module interface. For the relevant
parameters, you should not specify any reference field.
2. The field <INPUT> conflicts with a function module called
"..._OUTPUT".
It may be that the GPA mechanism was used to read a value from the
SAP memory with an incorrect length. The
material number conversion MATN1, for example, expects
a material number 18 characters long in ABAP/4 internal terms. If,
instead, MAT contains a value only 1 character long, the program
terminates.
To view the current contents of the SAP memory, go into "Debugging"
and select Goto -> System -> System areas. View area SMEM.
A GPA value may be the wrong length for any of the following reasons:
a) The user master record contains a value with an incorrect length.
b) In the current transaction, an incorrect parameter ID was
chosen for the field with this conversion.
c) In one of the screens for a previously executed transaction, a
field was assigned an incorrect parameter ID.
d) In a previously executed ABAP/4 program, a
SET-PARAMETER statement has a value with an incorrect length, e.g.
SET PARAMETER ID 'MAT' FIELD '1'.
System environment
SAP Release.............. "620"
Application server....... "efcuxp01"
Network address.......... "10.94.10.43"
Operating system......... "HP-UX"
Release.................. "B.11.23"
Hardware type............ "ia64"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 23
Short dump setting....... "full"
Database server.......... "efcuxp1t"
Database type............ "ORACLE"
Database name............ "P60"
Database owner........... "SAPR3"
Terminal................. " "
Character set............ "C"
SAP kernel............... "640"
Created on............... "Oct 26 2008 20:48:43"
Created in............... "HP-UX B.11.23 U ia64"
Database version......... "OCI_920 "
Patch level.............. "257"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "HP-UX B.11"
User, transaction...
Client.............. 100
User................ "BATCHUSER"
Language key........ "E"
Transaction......... " "
Program............. "SAPLZDELVCONF"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLZDELVCONF" in
"ZIDOC_INPUT_ZDELVCONF".
The main program was "RBDAPP01 ".
The termination occurred in line 167 of the source code of the (Include)
program "LZDELVCONFU01"
of the source code of program "LZDELVCONFU01" (when calling the editor 1670).
The program "SAPLZDELVCONF" was started as a background job.
Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_TYPE"
occurred in the
procedure "ZIDOC_INPUT_ZDELVCONF" "(FUNCTION)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLZDELVCONF ". Its source code starts in
line 5
of the (Include) program "LZDELVCONF$01 ".
Source code extract
001370 l_bapiobdlvitemctrlcon.
001380 l_bapiobdlvitemctrlcon-deliv_numb = v_delv_no.
001390 APPEND l_bapiobdlvitemctrlcon TO t_bapiobdlvitemctrlcon.
001400 ENDCASE.
001410 ENDLOOP.
001420 ENDLOOP. "End loop at idoc_contrl.
001430
001440 * Populate Picking Qty into delv item line, those belong item
001450 * category 'KBN'
001460 IF NOT t_vbpok IS INITIAL.
001470 * Call FM to update picking QTY
001480 CALL FUNCTION 'SD_DELIVERY_UPDATE_PICKING'
001490 EXPORTING
001500 vbkok_wa = l_vbkok
001510 * SYNCHRON = ' '
001520 * NO_MESSAGES_UPDATE = ' '
001530 * NICHT_SPERREN = ' '
001540 * AUFRUFER_T = ' '
001550 * IF_ERROR_MESSAGES_SEND = 'X'
001560 TABLES
001570 vbpok_tab = t_vbpok
001580 prot = t_prot.
001590 * Check Picking QTY successfully update
001600 IF t_prot IS INITIAL.
001610 * Commit
001620 COMMIT WORK.
001630 ENDIF.
001640 ENDIF.
001650
001660 * Call FM to confirm Delivery
> CALL FUNCTION 'BAPI_OUTB_DELIVERY_CONFIRM_DEC'
00168 0 EXPORTING
001690 header_data = v_bapiobdlvhdrcon
001700 header_control = v_bapiobdlvhdrctrlcon
001710 delivery = v_delv_no
001720 TABLES
001730 item_data = t_bapiobdlvitemcon
001740 item_control = t_bapiobdlvitemctrlcon
001750 return = t_bapiret2.
001760 IF t_bapiret2[] IS INITIAL.
001770 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
001780 IMPORTING
001790 return = l_bapiret2.
001800 IF l_bapiret2 IS INITIAL.
001810
001820
001830 *{ INSERT D60K962623 T.Jain
001840 * Update LIKP-VLSTK as blank in database table.
001850
001860
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 1
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM
SY-TITLE Inbound Processing of IDocs Ready for Transfer
SY-MSGTY SY-MSGID
SY-MSGNO 000 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
7 FUNCTION ZIDOC_INPUT_ZDELVCONF
SAPLZDELVCONF
LZDELVCONFU01 167
6 FORM IDOCS_PASS_TO_APPLICATION
SAPLBD20
LBD20F0A 367
5 FORM IDOCS_PROCESS
SAPLBD20
LBD20F0B 68
4 FUNCTION IDOC_INPUT
SAPLBD20
LBD20U05 240
3 FUNCTION IDOC_START_INBOUND
SAPLEDIR
LEDIRU02 163
2 FUNCTION APPLICATION_IDOC_POST_IMMEDIAT
SAPLBD12
LBD12U04 37
1 EVENT START-OF-SELECTION
RBDAPP01
RBDAPP01 327
Chosen variables
7 FUNCTION ZIDOC_INPUT_ZDELVCONF
SAPLZDELVCONF
LZDELVCONFU01 167
INPUT_METHOD
0
0
2
0
MASS_PROCESSING X
0
0
5
8
APPLICATION_VARIABLE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
000000000000000
000000000000000
222222222222222
000000000000000
CALL_TRANSACTION_DONE
0
0
2
0
DOCUMENT_NUMBER
0000000000
0000000000
2222222222
0000000000
IN_UPDATE_TASK
0
0
2
0
WORKFLOW_RESULT
00000
00000
22222
00000
EDI_TEXT[] Table[initial]
EDI_TEXT_LINES[] Table[initial]
IDOC_CONTRL[] Table IT_96[1x1084]
IDOC_DATA[] Table IT_97[113x2122]
IDOC_STATUS[] Table IT_105[0x788]
RETURN_VARIABLES[] Table IT_106[0x204]
SERIALIZATION_INFO[] Table IT_107[0x430]
T_BAPISDH1X
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
00000000000000000000
00000000000000000000
22222222222222222222
00000000000000000000
T_PROT Table[initial]
V_STO
0000000000
0000000000
2222222222
0000000000
T_VBPOK Table[initial]
%_ARCHIVE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
000000000000000
000000000000000
222222222222222
000000000000000
SY-ONCOM S
0
0
5
3
I_EMSEG[] Table[initial]
V_DELV_NO 0720010737
0000000000
0000000000
3333333333
0720010737
I_IMSEG 00000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
3333333333333322222222222222222222222222
0000000000000000000000000000000000000000
... + 40 #
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222220222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 #### #### #### 00000 0
0000000000000000000000000000000000000000
0000C000000C000000C000000000000000000000
2000022200002220000222222222222233333232
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 000000000
000000000000000
000000000000000
222222333333333
000000000000000
V_BAPIOBDLVHDRCTRLCON 0720010737
0000000000000000000000000000000
0000000000000000000000000000000
3333333333222222222222222222222
0720010737000000000000000000000
I_IMSEG[] Table[initial]
V_BAPIOBDLVHDRCON 0720010737######## ####
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
3333333333000000002222220000222222222222
0720010737000C000C000000000C000000000000
... + 40 00
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222223322
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000
0000000000000000000000000
2222222222222222222222222
0000000000000000000000000
I_IMKPF 0000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
3333333333333333222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 0
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222322222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
00
00
22
00
T_BAPIOBDLVITEMCTRLCON Table IT_109[55x42]
I_EMSEG 00000000000000##000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
3333333333333300333333333333222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 00
000000000000000
000000000000000
222222222222233
000000000000000
T_BAPIOBDLVITEMCON Table IT_108[55x440]
I_EMKPF 000000000000000000 ##
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222333333333333333333222222222200
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
000000000000000
000000000000000
222222222222222
000000000000000
T_BAPIRET2 Table[initial]
SYST-REPID SAPLZDELVCONF
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454544454444222222222222222222222222222
310CA45C63FE6000000000000000000000000000
6 FORM IDOCS_PASS_TO_APPLICATION
SAPLBD20
LBD20F0A 367
SY-XFORM CONVERSION_EXIT
000000000000000000000000000000
000000000000000000000000000000
444545544454545222222222222222
3FE65239FEF5894000000000000000
SY-REPID SAPLBD20
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454443322222222222222222222222222222222
310C242000000000000000000000000000000000
SY-MSGID
00000000000000000000
00000000000000000000
22222222222222222222
00000000000000000000
C_WF_RESULT_OK 0
00000
00000
32222
00000
SPACE
0
0
2
0
SY-MSGNO 000
000
000
333
000
SY-MSGV1
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000
0000000000
2222222222
0000000000
SY-MSGV2
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000
0000000000
2222222222
0000000000
SY-MSGV3
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000
0000000000
2222222222
0000000000
SY-MSGV4
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000
0000000000
2222222222
0000000000
PI_INPUT_METHOD
0
0
2
0
EDIFCT
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
000000000000000000
000000000000000000
222222222222222222
000000000000000000
PIF_EVENT_INFO-FUNCNAME ZIDOC_INPUT_ZDELVCONF
000000000000000000000000000000
000000000000000000000000000000
544445445555544454444222222222
A94F3F9E054FA45C63FE6000000000
C_WF_PAR_APPL_OBJECTS Appl_Objects
00000000000000000000000000000000
00000000000000000000000000000000
47765466667722222222222222222222
100CFF2A534300000000000000000000
C_WF_PAR_CREATED_OBJECTS Appl_Objects
00000000000000000000000000000000
00000000000000000000000000000000
47765466667722222222222222222222
100CFF2A534300000000000000000000
PI_MASS_PROCESSING X
0
0
5
8
SY-XPROG SAPCNVE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
PE_APPLICATION_VARIABLE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
000000000000000
000000000000000
222222222222222
000000000000000
PE_CALL_TRANSACTION_DONE
0
0
2
0
PE_IN_UPDATE_TASK
0
0
2
0
%_ARCHIVE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
000000000000000
000000000000000
222222222222222
000000000000000
PE_WORKFLOW_RESULT
00000
00000
22222
00000
SYST-SUBRC 0
0000
0000
PXT_IDOC_CONTROL[] Table IT_96[1x1084]
C_WF_PAR_APPL_OBJ_TYPE Appl_Object_Type
00000000000000000000000000000000
00000000000000000000000000000000
47765466667557762222222222222222
100CFF2A534F49050000000000000000
PXT_IDOC_DATA[] Table IT_97[113x2122]
T_APPL_IDOC_STATUS[] Table IT_105[0x788]
PET_RETURN_VARIABLES[] Table IT_106[0x204]
T_SERIALIZATION_INFO[] Table IT_107[0x430]
5 FORM IDOCS_PROCESS
SAPLBD20
LBD20F0B 68
PIT_IDOC_STATUS 000000001561906062IB1 0
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
3333333333333333334432222222222222222223
0000000015619060629210000000000000000000
... + 40 42
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
3322222222222222222222222222222222222222
4200000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... +
Hi,
Try to use SO_CONVERT_OBJECT_TO_FAX.
Reward If UsefuL
Similar Messages
-
Hi Friends,
For the last few weeks we have been receiving the same runtime errors when I perform the daily checks
SAPBATCH - CALL_FUNCTION_CONFLICT_LENG
SAPBATCH - CALL_FUNCTION_UC_STRUCT
Please help me if any one have idea and is this something we need to be concerned about?
Best Regards,
VinodSorry for the delay in response...I'm sure that program is sap batch only..please find the first page of two dumps.
Dump(1):
Runtime Error CALL_FUNCTION_CONFLICT_LENG
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
Date and Time 02.06.2008 04:53:15
ShrtText
Type conflict when calling a function module (field length).
What happened?
Error in ABAP application program.
The current ABAP program "/SDF/SAPLRI_SQLSERVER" had to be terminated because one of the statements could not be executed.
This is probably due to an error in the ABAP program.
A function module was called incorrectly.
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.
is especially useful if you want to keep a particular message.
Dump(2) First page:
Runtime Error CALL_FUNCTION_UC_STRUCT
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
Date and Time 02.06.2008 04:53:14
ShrtText:
A type conflict occurred when structure parameters were passed in the.
What happened?
Error in ABAP application program.
The current ABAP program "/SDF/SAPLRI_SQLSERVER" 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.
is especially useful if you want to keep a particular message.
Please let me know if required further information.
Best Regards,
Vinod -
Bapi in a badi, error call_function_conflict_leng
Hi, i'm using the bapi BAPI_REL_CREATERELATION in the badi IF_EX_ECM_UPDATE~CHANGE_IN_UPDATE. But there is an rutime error that doesnt continue, that is call_function_conflict_leng.
Did anyone have this error.
plz help me,
regards,
Diegocalling a BAPI in a BADI, which will be hit on a online process... my money doesnt go on this process.
-
CALL_FUNCTION_CONFLICT_LENG error
Hi freinds
i m getting run time error CALL_FUNCTION_CONFLICT_LENG
while using the call function CALL FUNCTION 'SAVE_TEXT'
pls help me by sending sample code
regardsHi,
Check this sample code...
REPORT Z_TEST_SAVE_TEXT .
TABLES:MAKT.
DATA: IT_LINSS TYPE STANDARD TABLE OF TLINE WITH HEADER LINE,
IT_TDHEAD TYPE THEAD .
CALL FUNCTION 'READ_TEXT'
EXPORTING
* CLIENT = SY-MANDT
ID = '0002'
LANGUAGE = 'E'
NAME = '0000000241'
OBJECT = 'VBBK'
TABLES
LINES = IT_LINSS
* EXCEPTIONS
* ID = 1
* LANGUAGE = 2
* NAME = 3
* NOT_FOUND = 4
* OBJECT = 5
* REFERENCE_CHECK = 6
* WRONG_ACCESS_TO_ARCHIVE = 7
* OTHERS = 8
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IT_LINSS-TDLINE = 'ADDITIONAL TEXT'.
APPEND IT_LINSS.
IT_TDHEAD-TDNAME = '0000000241'.
IT_TDHEAD-TDID = '0002'.
IT_TDHEAD-TDSPRAS ='E'.
IT_TDHEAD-TDOBJECT = 'VBBK'.
*APPEND IT_TDHEAD.
CALL FUNCTION 'SAVE_TEXT'
EXPORTING
* CLIENT = SY-MANDT
HEADER = IT_TDHEAD
SAVEMODE_DIRECT = 'X'
TABLES
LINES = IT_LINSS
EXCEPTIONS
ID = 1
LANGUAGE = 2
NAME = 3
OBJECT = 4
OTHERS = 5
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Regards
vijay -
CALL_FUNCTION_CONFLICT_LENG Dump error
Dear gurus
Please help me..
my problem is located on the links below
[REPORT ERROR|http://www.geocities.com/saadnisarahmedkhatib/ABAP/Report.zip]
Regards
SaadDear Gurus
I have re-attached my smart forms and my tables details on the link below
[Report Error|http://www.geocities.com/saadnisarahmedkhatib/ABAP/Report.zip]
Regards
Saad -
Run-time error "PXA_NO_SHARED_MEMORY" occurred
Hi All,
My production system is running fine. And when i check SM21 I saw a lot of error message Run-time error "PXA_NO_SHARED_MEMORY" occurred and Run-time error "SYSTEM_NO_ROLL" occurred. However I can't see any error in ST22. I had read sap note 307976. And dont know when I restart the SAP services is it will be fine?
trc file: "dev_w0", trc level: 1, release: "640"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, M
B
B Mon Feb 22 08:13:29 2010
B create_con (con_name=R/3)
B Loading DB library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll' ...
B Library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll' loaded
B Version of 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll' is "640.00", patchlevel (0.58)
B New connection 0 created
M sysno 00
M sid PRD
M systemid 560 (PC with Windows NT)
M relno 6400
M patchlevel 0
M patchno 58
M intno 20020600
M make: multithreaded, ASCII
M pid 2440
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 2440) [dpxxdisp.c 1160]
I MtxInit: -2 0 0
M DpSysAdmExtCreate: ABAP is active
M DpShMCreate: sizeof(wp_adm) 11592 (828)
M DpShMCreate: sizeof(tm_adm) 2219848 (11044)
M DpShMCreate: sizeof(wp_ca_adm) 18000 (60)
M DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
M DpShMCreate: sizeof(comm_adm) 192000 (384)
M DpShMCreate: sizeof(vmc_adm) 0 (320)
M DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
M DpShMCreate: SHM_DP_ADM_KEY (addr: 047D0040, size: 2510384)
M DpShMCreate: allocated sys_adm at 047D0040
M DpShMCreate: allocated wp_adm at 047D17A8
M DpShMCreate: allocated tm_adm_list at 047D44F0
M DpShMCreate: allocated tm_adm at 047D4518
M DpShMCreate: allocated wp_ca_adm at 049F2460
M DpShMCreate: allocated appc_ca_adm at 049F6AB0
M DpShMCreate: allocated comm_adm_list at 049F8220
M DpShMCreate: allocated comm_adm at 049F8238
M DpShMCreate: allocated vmc_adm_list at 04A27038
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 04A27060
M DpShMCreate: allocated wall_adm at 04A27068
X EmInit: MmSetImplementation( 2 ).
X <ES> client 0 initializing ....
X Using implementation flat
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M
M Mon Feb 22 08:13:30 2010
M calling db_connect ...
C Thank You for using the SLOLEDB-interface
C Using dynamic link library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll'
C dbmssslib.dll patch info
C patchlevel 0
C patchno 58
C patchcomment MSSQL: Workaround for SQL2005 change in RpcNexecInsert (814383)
C np:(local) connection used on PKG-PRD
C CopyLocalParameters: dbuser is 'prd'
C
C Mon Feb 22 08:13:31 2010
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: MARS property was not set.
C Provider Release:08.50.1022
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: MARS property was not set.
C
C Mon Feb 22 08:13:42 2010
C Cache sizes: header 52 bytes, 20000 names (26720000 bytes), 1000 dynamic statements (5432000 bytes), total 32152052 bytes
C Using shared procedure name cache PKG-PRD_PRDPRD_PRD_MEM initialized by another process.
C Connected to db server : [PKG-PRD] server_used : [np:(local)], dbname: PRD, dbuser: prd
C pn_id:PKG-PRD_PRDPRD_PRD
C Not using MARS (on sql 8.0)
B Connection 0 opened (DBSL handle 0)
B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost
B 000 000 R/3 000000000 ACTIVE NO YES NO 000 255 255 20100222 081330 PKG-PRD
C The IRow interface is supported by this OLEDB provider
M db_connect o.k.
I
I Mon Feb 22 08:14:02 2010
I MtxInit: 0 0 0
M SHM_PRES_BUF (addr: 09E50040, size: 4400128)
M SHM_ROLL_AREA (addr: 12510040, size: 262144000)
M SHM_PAGING_AREA (addr: 617B0040, size: 113246208)
M SHM_ROLL_ADM (addr: 0A290040, size: 2616690)
M SHM_PAGING_ADM (addr: 0A510040, size: 525344)
M ThCreateNoBuffer allocated 320144 bytes for 1000 entries at 0A5A0040
M ThCreateNoBuffer index size: 3000 elems
M ThCreateVBAdm allocated 7424 bytes (50 server) at 0A5F0040
X EmInit: MmSetImplementation( 2 ).
X <ES> client 0 initializing ....
X Using implementation flat
X ES initialized.
B db_con_shm_ini: WP_ID = 0, WP_CNT = 14
B dbtbxbuf: Buffer TABL (addr: 103500C8, size: 30000128, end: 11FEC4C8)
B dbtbxbuf: Buffer TABLP (addr: 0E5200C8, size: 10240000, end: 0EEE40C8)
B dbexpbuf: Buffer EIBUF (addr: 0EF000D0, size: 4194304, end: 0F3000D0)
B dbexpbuf: Buffer ESM (addr: 0F3100D0, size: 4194304, end: 0F7100D0)
B dbexpbuf: Buffer CUA (addr: 0F7200D0, size: 3072000, end: 0FA0E0D0)
B dbexpbuf: Buffer OTR (addr: 0FA100D0, size: 4194304, end: 0FE100D0)
M rdisp/reinitialize_code_page -> 0
M icm/accept_remote_trace_level -> 0
M rdisp/no_hooks_for_sqlbreak -> 0
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: MARS property was not set.
S *** init spool environment
S initialize debug system
T Stack direction is downwards.
T debug control: prepare exclude for printer trace
T new memory block 120D8040
S spool kernel/ddic check: Ok
S using table TSP02FX for frontend printing
S 1 spool work process(es) found
S frontend print via spool service enabled
S printer list size is 150
S printer type list size is 50
S queue size (profile) = 300
S hostspool list size = 3000
S option list size is 30
S found processing queue enabled
S found spool memory service RSPO-RCLOCKS at 121F0098
S doing lock recovery
S setting server cache root
S found spool memory service RSPO-SERVERCACHE at 121F03E0
S using messages for server info
S size of spec char cache entry: 165020 bytes (timeout 100 sec)
S size of open spool request entry: 1152 bytes
S immediate print option for implicitely closed spool requests is disabled
A
A -PXA--
A PXA INITIALIZATION
A PXA: Fragment Size too small: 107 MB, reducing # of fragments
A System page size: 4kb, admin_size: 13396kb.
A Attached to PXA (address 21F30040, size 440000K)
A abap/pxa = shared protect gen_remote
A PXA INITIALIZATION FINISHED
A -PXA--
A
C The IRow interface is supported by this OLEDB provider
B dbtran INFO (init_connection '<DEFAULT>' [MSSQL:640.00]):
B max_blocking_factor = 50, max_in_blocking_factor = 255,
B min_blocking_factor = 5, min_in_blocking_factor = 10,
B prefer_union_all = 1, prefer_union_for_select_all = 0,
B prefer_fix_blocking = 0, prefer_in_itab_opt = 0,
B convert AVG = 1, alias table FUPD = 0,
B escape_as_literal = 0, opt GE LE to BETWEEN = 0,
B select * =0x00, character encoding =SBCS / []:X,
B use_hints = abap->1, dbif->0x1, upto->0, rule_in->0,
B rule_fae->0, concat_fae->0, concat_fae_or->0
A
A Mon Feb 22 08:14:03 2010
A ABAP ShmAdm attached (addr=53EC5000 leng=20955136 end=552C1000)
A >> Shm MMADM area (addr=5422D180 leng=134720 end=5424DFC0)
A >> Shm MMDAT area (addr=5424F000 leng=17244160 end=552C1000)
A RFC Destination> destination pkg-prd_PRD_00 host pkg-prd system PRD systnr 0 (pkg-prd_PRD_00)
A RFC Options> H=pkg-prd,S=00
A RFC FRFC> fallback activ but this is not a central instance.
A
A RFC rfc/signon_error_log = -1
A RFC rfc/dump_connection_info = 0
A RFC rfc/dump_client_info = 0
A RFC rfc/cp_convert/ignore_error = 1
A RFC rfc/cp_convert/conversion_char = 23
A RFC rfc/wan_compress/threshold = 251
A RFC rfc/recorder_pcs not set, use defaule value: 1
A RFC rfc/delta_trc_level not set, use default value: 0
A RFC rfc/no_uuid_check not set, use default value: 0
A RFC abap/SIGCHILD_default not set, use default value: 0
A RFC Method> initialize RemObjDriver for ABAP Objects
A Hotpackage version: 49
M ThrCreateShObjects allocated 14604 bytes at 0FFD0040
N
N Mon Feb 22 08:14:05 2010
N SsfSapSecin: putenv(SECUDIR=D:\usr\sap\PRD\DVEBMGS00\sec): ok
N
N =================================================
N === SSF INITIALIZATION:
N ===...SSF Security Toolkit name SAPSECULIB .
N ===...SSF trace level is 0 .
N ===...SSF library is D:\usr\sap\PRD\SYS\exe\run\sapsecu.dll .
N ===...SSF hash algorithm is SHA1 .
N ===...SSF symmetric encryption algorithm is DES-CBC .
N ===...sucessfully completed.
N =================================================
N MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
N MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
W =================================================
W === ipl_Init() called
W ITSP Running against db release 620!
W ITSP Disable Kernel Web GUI functionality
W === ipl_Init() returns 2, ITSPE_DISABLED: Service is disabled (sapparam)
W =================================================
E
E Mon Feb 22 08:14:39 2010
E Replication is disabled
C
C Mon Feb 22 08:15:00 2010
C sloledb.cpp [DoDbcc,line 2930]: Error/Message: (err 2571, sev 0), User 'prd' does not have permission to run DBCC CACHEPROFILE.
C Procname: [No proc]
C
C Mon Feb 22 08:15:01 2010
C statement rerun with user dbo was successful, you can ignore the preceeding message
C
C Mon Feb 22 08:16:27 2010
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: MARS property was not set.
S
S Mon Feb 22 08:19:23 2010
S found spool memory service RSPO-ACTIONS at 121F4C68
A
A Mon Feb 22 08:19:55 2010
A TH VERBOSE LEVEL FULL
M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c 12304]
C Rollback Work (0)
A
A Mon Feb 22 08:19:59 2010
A Mon Feb 22 08:19:59 2010
A
A ABAP/4 Program /SDF/SAPLRI_SQLSERVER .
A Source /SDF/LRI_SQLSERVERU02 Line 264.
A Error Code CALL_FUNCTION_CONFLICT_LENG.
A Module $Id: //bas/640_REL/src/krn/runt/abfunc.c#14 $ SAP.
A Function FuncParams Line 2906.
C Rollback Work (0)
C
C Mon Feb 22 08:20:00 2010
C sloledb.cpp [DoDbcc,line 2930]: Error/Message: (err 2571, sev 0), User 'prd' does not have permission to run DBCC loginfo.
C Procname: [No proc]
C
C Mon Feb 22 08:20:01 2010
C statement rerun with user dbo was successful, you can ignore the preceeding message
C
C Mon Feb 22 08:20:07 2010
C sloledb.cpp [ParamStmtExec,line 12251]: Error/Message: (err 50000, sev 0), Table not found.
C Procname: [##Y3PKG_PRDprd00000024400000003365081342]
C ParamStmtExec failed. HR 80040e14 DBSL retcode 99. stmt: [sap_get_table_size_info 'syscomments', 'prd', 'PRD'
C /* R3:CL_SQL_RESULT_SET=============CP:234 T: */
C ]
C Conn_i:2 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 222194
C dbdsmss: DBSL99 SQL50000
C Table not found.
B ***LOG BY2=> sql error 50000 performing FET [dbds#3 @ 592] [dbds 0592 ]
B ***LOG BY0=> Table not found. [dbds#3 @ 592] [dbds 0592 ]
B ***LOG BY1=> sql error 50000 [dbacds#2 @ 1187] [dbacds 1187 ]
B
B Mon Feb 22 08:26:10 2010
B dbmyclu : info : my major identification is 3232261128, minor one 0.
B dbmyclu : info : Time Reference is 1.12.2001 00:00:00h GMT.
B dbmyclu : info : my uuid is 31B87DDDE43B904B955F2E6B45F604BE.
B dbmyclu : info : current optimistic cluster level: 3
B dbmyclu : info : pessimistic reads set to 2.
N login/password_change_for_SSO : 1 -> 1
B
B Mon Feb 22 08:32:54 2010
B table logging switched off for all clients
M
M Mon Feb 22 08:45:50 2010
M PfHIndInitialize: memory=<60720150>, header=<60720150>, records=<60720180>
S
S Mon Feb 22 08:55:52 2010
S handle memory type is RSTSPROMMM
M
M Mon Feb 22 09:18:08 2010
M *** ERROR => NiProcMsg: rc=-104 (NIEROUT_SNC_FAILURE) from router [nibuf.c 423]
M *** ERROR => MsIAttachEx: NiBufConnect to /H/192.168.100.7/S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001/sapmsOSS failed (rc=NIEROUT_SNC_FAILURE) [msxxi.c 633]
M *** ERROR => LgIAttach: MsAttach (rc=NIEROUT_SNC_FAILURE) [lgxx.c 2984]
M *** ERROR => LgIGroup: LgIAttach(rc=-101) [lgxx.c 3504]
A TH VERBOSE LEVEL FULL
M
M Mon Feb 22 09:18:28 2010
M *** ERROR => NiProcMsg: rc=-104 (NIEROUT_SNC_FAILURE) from router [nibuf.c 423]
M *** ERROR => MsIAttachEx: NiBufConnect to /H/192.168.100.7/S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001/sapmsOSS failed (rc=NIEROUT_SNC_FAILURE) [msxxi.c 633]
M *** ERROR => LgIAttach: MsAttach (rc=NIEROUT_SNC_FAILURE) [lgxx.c 2984]
M *** ERROR => LgIGroup: LgIAttach(rc=-101) [lgxx.c 3504]
A TH VERBOSE LEVEL FULL
C
C Mon Feb 22 10:01:09 2010
C Rollback Work (0)
A
A Mon Feb 22 10:18:24 2010
A TH VERBOSE LEVEL FULL
M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c 12304]
C Rollback Work (0)
A
A Mon Feb 22 10:18:26 2010
A Mon Feb 22 10:18:26 2010
A
A ABAP/4 Program /SDF/SAPLRI_SQLSERVER .
A Source /SDF/LRI_SQLSERVERU02 Line 264.
A Error Code CALL_FUNCTION_CONFLICT_LENG.
A Module $Id: //bas/640_REL/src/krn/runt/abfunc.c#14 $ SAP.
A Function FuncParams Line 2906.
C Rollback Work (0)
C sloledb.cpp [DoDbcc,line 2930]: Error/Message: (err 2571, sev 0), User 'prd' does not have permission to run DBCC loginfo.
C Procname: [No proc]
C statement rerun with user dbo was successful, you can ignore the preceeding message
C
C Mon Feb 22 10:18:29 2010
C sloledb.cpp [ParamStmtExec,line 12251]: Error/Message: (err 50000, sev 0), Table not found.
C Procname: [##Y3PKG_PRDprd00000024400000012657081342]
C ParamStmtExec failed. HR 80040e14 DBSL retcode 99. stmt: [sap_get_table_size_info 'syscomments', 'prd', 'PRD'
C /* R3:CL_SQL_RESULT_SET=============CP:234 T: */
C ]
C Conn_i:2 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 222194
C dbdsmss: DBSL99 SQL50000
C Table not found.
B ***LOG BY2=> sql error 50000 performing FET [dbds#3 @ 592] [dbds 0592 ]
B ***LOG BY0=> Table not found. [dbds#3 @ 592] [dbds 0592 ]
B ***LOG BY1=> sql error 50000 [dbacds#2 @ 1187] [dbacds 1187 ]
Could anybody advice me on this
Regards,
ZulHi,
I hope 440000 will not the cause,
this might occur due to many reasons,
1. make sure you have all the components(Applications,OSlevel,DBlevel) are at same level in entire the landscape.
2. you can observe the evenlogs at OSlevel to get the error information pointing to. Also check for the dumps/logs(work direcotry).
3. if not, can open SAP message.
regards
Nagaraju -
Purchase Order Description Text
Hi All,
I am trying to display a POD text but it is cutting off, can anyone help to write the purchase order description text. Currently it can only display only 130 characters.
gv_repid = sy-repid.
SELECT SINGLE ebeln INTO i_tab-ebeln FROM ekpo WHERE matnr = i_tab-matnr.
line_id = 'BEST'.
line_name = i_tab-matnr.
line_lang = sy-langu.
line_object = 'MATERIAL'.
CALL FUNCTION 'READ_TEXT'
EXPORTING
id = line_id
language = line_lang
name = line_name
object = line_object
TABLES
lines = i_tabs
EXCEPTIONS
id = 1
language = 2
name = 3
not_found = 4
object = 5
reference_check = 6
wrong_access_to_archive = 7
OTHERS = 8.
IF sy-subrc <> 0.
ENDIF.
LOOP AT i_tabs.
CONDENSE i_tabs-tdline.
CONCATENATE i_tab-text i_tabs-tdline INTO i_tab-text SEPARATED BY space.
MODIFY i_tab TRANSPORTING text.
ENDLOOP.
Regards,
FredHi
This is my code:
FORM reading_text.
Begin of i_tab occurs 0,
text(150) type c
end of i_tab.
gv_repid = sy-repid.
SELECT ebeln INTO i_tab-ebeln FROM ekpo WHERE matnr = i_tab-matnr.
EXIT.
ENDSELECT.
line_id = 'BEST'.
line_name = i_tab-matnr.
line_lang = sy-langu.
line_object = 'MATERIAL'.
ALL FUNCTION 'READ_TEXT'
EXPORTING
id = line_id
language = line_lang
name = line_name
object = line_object
TABLES
lines = i_tabs
EXCEPTIONS
id = 1
language = 2
name = 3
not_found = 4
object = 5
reference_check = 6
wrong_access_to_archive = 7
OTHERS = 8.
IF sy-subrc <> 0.
ENDIF.
LOOP AT i_tabs.
CONDENSE i_tabs-tdline.
CONCATENATE i_tab-text i_tabs-tdline INTO i_tab-text(150) SEPARATED BY space.
MODIFY i_tab TRANSPORTING text.
ENDLOOP.
CALL FUNCTION 'SAVE_TEXT'
EXPORTING
header = i_tab-text
TABLES
lines = i_tabs.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
It's giving me a dump:call_function_conflict_leng
There are other fields in an internal table.
Regards,
Fred
Edited by: Fred Mogaadile on Sep 26, 2008 6:17 AM
Edited by: Fred Mogaadile on Sep 26, 2008 6:19 AM -
Mapping a field from input help screen(Using POV) to user screen
I have used the Function module 'DYNP_VALUES_UPDATE', to get the value from Description field in the search help.Now its throwing a runtime error mentioned below.
Runtime errors: CALL_FUNCTION_CONFLICT_LENG
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE.
Short text: Type conflict when calling a function module
the function module was called incorrectly.
Below is the code i implemented.
ws_dynpfields-fieldname = wc_scrfld.
ws_dynpfields-stepl = tc_1017-current_line.
ws_dynpfields-fieldvalue = ws_hssr-text.
APPEND ws_dynpfields TO wt_dynpfields.
CALL FUNCTION 'DYNP_VALUES_UPDATE'
EXPORTING
dyname = 'sapmzapp01'
dynumb = '1008'
TABLES
dynpfields = wt_dynpfields
EXCEPTIONS
invalid_abapworkarea = 1
invalid_dynprofield = 2
invalid_dynproname = 3
invalid_dynpronummer = 4
invalid_request = 5
no_fielddescription = 6
undefind_error = 7
OTHERS = 8.
IF sy-subrc <> 0.
MESSAGE e800(zmdb_mda_supplier).
ENDIF.
The above code is in screen USER COMMAND OF 1017(POV-input help screen).
wt_dynpfields is the internal table.
and its fields are fieldname,stepl and fieldvalue
ws_dynpfields is the workarea of the internal table.
wc_scrfld-Constant with value zbut0000qnnyxa-ztfldg6h7np'(the description field name of the screen 1008 where i want the description value to get in automatically after selecting from input help)
ws_hssr-text= The Work area containing the value 'eg ORDER'.
kindly get back immediately....Hi,
This function works only after POV.
So ensure that it is written in that module:
like AT SELECTION-SCREEN ON VALUE-REQUEST FOR f_name.
Hope it will guide you.
Jogdand M B -
Workflow: step specific tab
Hello Gurus,
I need to display two tables in a work item and to handle that I have created a custom screen. I am calling my screen in Work Item Display tab in workflow. Now when is use the demo screen provided by SAP (program SAPLSWL0 and screen 0100) it works fine. It shows an empty screen because data is not available but it at least shows a blank screen. I have coped that screen into a custom program and screen as a starting point. When I provide this custom program and screen number I get a short dump when trying to display the work item. I get below exceptions:
"CALL_FUNCTION_CONFLICT_LENG"
"CX_SY_DYN_CALL_ILLEGAL_TYPE"
I don't know why I am getting this dump because I am using SAP code and it works if I provide SAP program and screen. Can anyone provide example of how to add a custom tab in work item display? Has anyone encountered similar issue while adding a custom tab in work item? Any help would be appreciated.
Thanks,
Rutul ThakkarFound solution
-
HI experts ,
I have smartforms for Stock Report. and respective selection screen in se38. while executing its shows Below runtime error.
Runtime Errors CALL_FUNCTION_CONFLICT_LENG
Exceptn CX_SY_DYN_CALL_ILLEGAL_TYPE
Date and Time 07.07.2007 16:15:34
ShrtText
Type conflict when calling a function module (field length).
What happened?
Error in ABAP application program.
The current ABAP program "ZSTOCK_TR" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
A function module was called incorrectly.
Error analysis
An exception occurred. This exception will be dealt with in more detail
below. The exception, assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was
not caught, which
led to a runtime error. The reason for this exception is:
The call to the function module "/1BCDWB/SF00000017" is incorrect:
In the function module interface, you can specify only
fields of a specific type and length under "GT_STRUCT".
Although the currently specified field
"GT_STRUCT2" is the correct type, its length is incorrect.
Source Code Extract
Line SourceCde
304
305 SELECT stceg into ITAB0-stceg FROM kna1 WHERE KUNNR = VKUNNR.
306 APPEND ITAB0.
307 ENDSELECT.
308
309 select vgbel from lips into itab0-ponum where vbeln in vbeln.
310 append itab0.
311 endselect.
312 DATA : LINES TYPE STANDARD TABLE OF TLINE WITH HEADER LINE.
313
314 ***************************************************************
315
316 CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
317 EXPORTING
318 FORMNAME = 'Z_STOCK_TR'
319 * VARIANT = ' '
320 * DIRECT_CALL = ' '
321 IMPORTING
322 FM_NAME = gv_fname
323 * EXCEPTIONS
324 * NO_FORM = 1
325 * NO_FUNCTION_MODULE = 2
326 * OTHERS = 3
327 .
328 IF SY-SUBRC <> 0.
329 * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
330 * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
331 ENDIF.
332
333
>334 CALL FUNCTION gv_fname
335 exporting
336 * ARCHIVE_INDEX =
337 * ARCHIVE_INDEX_TAB =
338 * ARCHIVE_PARAMETERS =
339 * CONTROL_PARAMETERS =
340 * MAIL_APPL_OBJ =
341 * MAIL_RECIPIENT =
342 * MAIL_SENDER =
343 * OUTPUT_OPTIONS =
344 * USER_SETTINGS = 'X'
345 plant = plant
346 * vbeln = exc_inv
347 * srdoc = srdoc-low
348 * vexdat = vexdat
349 * vrdoc = vrdoc
350 * ptotal = ptotal
351 * line1 = line1
352 * fkwert = fkwert
353 * ikwert = ikwert
Plz help. Thanks alot.
Khan.Hi
I think u have not called Function module properly
check this sample code
Tables : sflight.
Data : fm_name TYPE rs38l_fnam.
*data : Begin of it_flttab occurs 0,
* carrid type sflight-carrid,
* connid type sflight-connid,
* fldate type sflight-fldate,
* seatsmax type sflight-seatsmax,
* seatsocc type sflight-seatsocc,
* End of it_flttab.
data : it_flttab like table of sflight.
Data : g_salary type i .
* it_flttab type standard table of ty_flt.
g_salary = 1000.
select carrid connid fldate seatsmax seatsocc from sflight into
corresponding fields of table it_flttab.
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
EXPORTING
formname = 'ZTACA_SMFORM2'
* VARIANT = ' '
* DIRECT_CALL = ' '
IMPORTING
FM_NAME = fm_name
EXCEPTIONS
NO_FORM = 1
NO_FUNCTION_MODULE = 2
OTHERS = 3
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
call function fm_name
Exporting
salary = g_salary
TABLES
it_flttab = it_flttab
EXCEPTIONS
FORMATTING_ERROR = 1
INTERNAL_ERROR = 2
SEND_ERROR = 3
USER_CANCELED = 4
OTHERS = 5 .
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
<b>2nd code</b>
TABLES: MKPF.
DATA: FM_NAME TYPE RS38L_FNAM.
DATA: BEGIN OF INT_MKPF OCCURS 0.
INCLUDE STRUCTURE MKPF.
DATA: END OF INT_MKPF.
SELECT-OPTIONS S_MBLNR FOR MKPF-MBLNR MEMORY ID 001.
SELECT * FROM MKPF WHERE MBLNR IN S_MBLNR.
MOVE-CORRESPONDING MKPF TO INT_MKPF.
APPEND INT_MKPF.
ENDSELECT.
* At the end of your program.
* Passing data to SMARTFORMS
call function 'SSF_FUNCTION_MODULE_NAME'
exporting
formname = 'ZSMARTFORM'
* VARIANT = ' '
* DIRECT_CALL = ' '
IMPORTING
FM_NAME = FM_NAME
EXCEPTIONS
NO_FORM = 1
NO_FUNCTION_MODULE = 2
OTHERS = 3.
if sy-subrc <> 0.
WRITE: / 'ERROR 1'.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function FM_NAME
* EXPORTING
* ARCHIVE_INDEX =
* ARCHIVE_INDEX_TAB =
* ARCHIVE_PARAMETERS =
* CONTROL_PARAMETERS =
* MAIL_APPL_OBJ =
* MAIL_RECIPIENT =
* MAIL_SENDER =
* OUTPUT_OPTIONS =
* USER_SETTINGS = 'X'
* IMPORTING
* DOCUMENT_OUTPUT_INFO =
* JOB_OUTPUT_INFO =
* JOB_OUTPUT_OPTIONS =
TABLES
GS_MKPF = INT_MKPF
EXCEPTIONS
FORMATTING_ERROR = 1
INTERNAL_ERROR = 2
SEND_ERROR = 3
USER_CANCELED = 4
OTHERS = 5.
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
Reward all helpfull answers
Regards
Pavan -
Prob with "BAPI_USER_CREATE"
Hello all,
I'm am getting dump while calling FM BAPI_USER_CREATE in ECC 6.0. Parameter 'password' lenght is 8 charectors in itab & 40 char lenght in FM. Still getting dump If passing 8 char value parameter passing to 40 char parameter.
If i called same FM 4.6c then its working fine. In 4.6c, lenght of "password" parameter lenght is 8 char in FM & same length in my itab.
CALL FUNCTION 'BAPI_USER_CREATE'
DESTINATION rfc
EXPORTING
username = itab-bname
logondata = wa_data
password = itab-password
address = wa_addr
TABLES
return = itab2.
" <Dump is>
Runtime Errors CALL_FUNCTION_CONFLICT_LENG
Exception CX_SY_DYN_CALL_ILLEGAL_TYPE
Date and Time 04/03/2009 02:18:34
Short text
Type conflict when calling a function module (field length).
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was
not caught in
procedure "DATA_CREATION" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
The call to the function module "BAPI_USER_CREATE" is incorrect:
In the function module interface, you can specify only
fields of a specific type and length under "PASSWORD".
Although the currently specified field
"itab-PASSWORD" is the correct type, its length is incorrect.
Is there any problem with the fm in ecc 6.0.
Plz help on this.
Regards.Hi,
Please check again.
The password type should be declared as bapipwd.
And as I saw the length is of 8 char.
not of 40 char.
use like that.
DATA: BEGIN OF itab OCCURS 0 ,
bname LIKE BAPIBNAME-BAPIBNAME,
password(8) like BAPIPWD,
class LIKE usr02-class,
END OF itab.
Thanks. -
Hi Experts,
I am facing the following error after doing VA01 i.e creation of sales order and while selecting the order from the list it is showing me the run time error.
Runtime Errors CALL_FUNCTION_CONFLICT_LENG
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
Date and Time 24.07.2008 15:32:41
Short text
Type conflict when calling a function module (field length).
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPFV45C" had to be terminated because it
come across a statement that unfortunately cannot be executed.
A function module was called incorrectly.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_T
not caught in
procedure "VBAP_KOPIEREN_PRUEFEN" "(FORM)", nor was it propagated b
clause.
Since the caller of the procedure could not have anticipated that t
exception would occur, the current program is terminated.
The reason for the exception is:
The call to the function module "CO_DB_HEADER_READ" is incorrect:
In the function module interface, you can specify only
fields of a specific type and length under "CAUFVWA".
Although the currently specified field
"LS_CAUFV" is the correct type, its length is incorrect.
Thanx In Advance,
RipelRipal,
i think you have some user exit for va* transaction might be this creating a problem.
Amit. -
0ASSET_ATTR master data load error
Hi all,
I got an error when i was loading the master data for Asset number.
The error message in BI side is: u201CThe error occurred in Extractoru201D.
When tried to check the data in the RSA3 extract checker their it was giving me short dump with error message as
*Runtime Errors CALL_FUNCTION_CONFLICT_LENG
Exception CX_SY_DYN_CALL_ILLEGAL_TYPE*
Short text: Type conflict when calling a function module (field length).
What happened?
Error in the ABAP Application Program, The current ABAP program "GP4A36CIW2A4S3VKUAJL657AX3F" had to be terminated because it has come across a statement that unfortunately cannot be executed.
A function module was called incorrectly.
*Error analysis: *
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was not caught in procedure "EXTRACTOR_FETCH" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated. The reason for the exception is:
The call to the function module "ARBW_BIW_GET_MASTER_DATA" is incorrect:
In the function module interface, you can specify only fields of a specific type and length under "E_T_BIW_ASSET". Although the currently specified field " " is the correct type, its length is incorrect.
Thanks & Regards
PrabhakarThanks KK !!!!!!!!!!
Issue got resolved.
ASSIGNED POINTS.
Thanks & Regards
Prabhakar -
Error 6 in FM RSS_Program_Generate in RSA3 tcode
Hello,
In RSA3 we are trying to look at hierarchies and we get an error.
'Error 6 in FM RSS_Program_Generate '
Report RSA1HCAT does show the hierarchies for all the other extractors except for Equipment hierarchy.
We are trying to load equipment hierarchies is there any hierarchy settings that have to performed on the BW side.
Get the following dump when we run report RSA1HCAT for equipment hierarchy extractor.
CALL_FUNCTION_CONFLICT_LENG
Type conflict when calling a function module (field length).
An exception occurred. This exception is dealt with in more de
. The exception, which is assigned to the class 'CX_SY_DYN_CAL
was neither
caught nor passed along using a RAISING clause, in the procedu
"DISPLAY_HIERARCHY_TRANSF_TREE" "(FORM)"
Since the caller of the procedure could not have expected this
to occur, the running program was terminated.
The reason for the exception is:
The call to the function module "PMEX_HIERARCHY_TRANSFER_EQUI"
>>>>> CALL FUNCTION L_S_HIEBAS-FHTRANSFER
88 EXPORTING
89 I_S_HIEBAS = L_S_HIEBAS
90 I_S_HIEFLAG = L_S_HIEFLAG
91 I_S_HIERSEL = L_S_HIERSEL
92 TABLES
93 I_T_LANGU = G_T_LANGU
94 E_T_HIETEXT = L_T_HIETEXT
95 E_T_HIENODE = L_T_HIENODE
96 E_T_FOLDERT = L_T_FOLDERT
97 E_T_HIEINTV = L_T_HIEINTV
98 EXCEPTIONS
99 INVALID_CHABASNM_HCLASS = 1
100 INVALID_HIERARCHY_FLAG = 2
101 INVALID_HIERARCHY_SELECT = 3
102 FUNCTION_NOT_SUPPORTED = 4
103 ROUTINE_NOT_SUPPORTED = 5
104 LANGU_NOT_SUPPORTED = 6
105 HIERARCHY_TAB_NOT_FOUND = 7
106 APPLICATION_ERROR = 8
In the function module interface, you can specify only
fields of a specific type and length under "E_T_HIENODE".
Although the currently specified field
"L_T_HIENODE" is the correct type, its length is incorrect.
Appreciate your help.
Thanks
Message was edited by:
KK'Error 6 in FM RSS_Program_Generate '
This means that occurs an error 6 in your code and this error is LANGU_NOT_SUPPORTED
Check if the hierarchy you selected is not created in your language and try another languages....
Regards -
Creating the spool request for the internal table data
Hi..
I am little confused with the function module used for creating the spool request.
well...I am practicing the ALV report and sending the that report to the spool.
I ve used the FM SLVC_TABLE_PS_TO_SPOOL.
this is the way i defined the internal table.
Data:
begin of imat occurs 0,
matnr like marav-matnr,
maktx like marav-maktx,
matkl like marav-matkl,
ntgew like marav-ntgew,
gewei like marav-gewei,
end of imat.
data i_lines type sy-tfill
and i declared..
describe table imat lines i_lines.
then i given the value for i_file_length as i_lines in the export paramet of the FM SLVC_TABLE_PS_TO_SPOOL.
CALL FUNCTION 'SLVC_TABLE_PS_TO_SPOOL'
EXPORTING
i_file_length = i_lines
IMPORTING
E_SPOOLID = spoolid
tables
it_textdata = imat
when i executed it shows the list and wen going back it shows the runtime error as
CALL_FUNCTION_CONFLICT_LENG - Type conflict when calling a function module (field length).
please provide me some solutions.
thanks in advance.
etienne.Hi satyajit,
Thanks for your response....but the fields in my internal table "IMAT" is not compatible with the structure LVC_S_1022 as it has it componenrt - LINE.
so how can i define my internal table IMAT as type lvc_s_1022 as you suggested.
thanks in advance.
etienne.
Maybe you are looking for
-
Home Hub 3 reporting muliple SSID
Hopefully someone can help to save me having to contact BT (un)help desk! I'm having problems getting my laptop to talk with my HP printer wirelessly; the printer IS connected to my network - HP printer setup software confirms this but then the lapto
-
Reinstalling CS3 Master Collection on Vista x64
CS3 has worked fine for me up until I did some major Windows updates (mainly for MS Office 2007) on 4/29/09. Premiere Pro gave me the "Sorry, a serious error has occurred that requires Premiere to be shut down. We will attempt to save your current p
-
Role of a Support Guy in SAP HR
Hello, kindly explain, what is the role of a supportGuy in SAP HR.
-
'notes' has disappeared on my iMac, how do i re-install it?
I have 'Notes' on my MacBook Pro (10.8.3) my iPhone 5S (6.1.4) and my iPad (6.1.3) but not on my intel iMac (10.7.5). Can anyone explain where it has gone to and how I get it back? Thanks
-
Automator - Creating a service - to Copy and Paste Folders
I keep trying to create an Automator service to copy a set of folders and paste them in a location where I have right clicked, but I can not make it happen. Can someone please help me or point me in the right direction of some information. Thank you