Dump in va02.
My user getting message : Bcd_field_overflow in saplv61a program
include LV61AU02
in PRICING_COMPLETE
FUCTION MODULE
.My client is using SAP R/3 4.6 version.
Plz suggest some note.
thanks in advance..
gorika
Check the value of each condition type that system would calculate. Probably for one of the condition types the value i.e rate X quantity is too big and the field is not able to hold the value. It may not be quantity and could be weight or volume depending on the configuration of the condition type. Try to reduce the quantity or price and check the scenario again.
If you are using a routine for calculation then you need to check the code or remove the routine in pricing procedure and test the scenario.
Regards,
GSL.
Similar Messages
-
Dump in VA02 changing conditions / SWEC with VERKBELEG and BUS2032
Hi,
Iu2019m Working on SAP 4.6c
I create a subtype object from BUS2032 to have new events which I have place in Tcode SWEC using VERKBELEG and BUS2032 and my new event on CHANGE mode, additionally I restricted the condition using this field restrictions and the condition editor including the next sentence:
&VBAK_LIFSK_OLD& EQ &VBAK_LIFSK_NEW& or
&VBAK_LIFSK_OLD& NE 02 and
&VBAK_LIFSK_NEW& EQ 02
This condition is Ok but when I call the Tcode VA02 to change the conditions in one position I got a dump and a popup telling me that the modification was not done, if I check SM13 to see the dump, I can see a conversion error from blank into a number in a SAP program and this is the error.
I think there's a SAP NOTE to solve this issue but I couldn't find it.
Any suggestion?
Thanks a lot
Felipe.Hi Mr Arghadip
Mysteriously there is a connection between Workflow and this error and thereu2019s a dump generated by this, Iu2019m sending you the dump analysis for you to see, but the most important thing is that I did apply the Workflow u201CNote 570711 - SWEB: Typing when evaluating field restrictionsu201D and the issue was solved.
Thanks a lot for your help....
This is our system: R/3 release 4.6C, Las patch applied SAPKB46C43,
Dump analisys:
Function module RV_MESSAGE_UPDATE
Status Update was terminated
Report
Line
Error text
00 671: ABAP/4 processor: CONVT_NO_NUMBER
ABAP Short Dump (button)
u2026
ABAP runtime errors CONVT_NO_NUMBER
What happened?
The current ABAP/4 program "SAPLSWEB " had to be terminated because
one of the statements could not be executed.
Error analysis
The program attempted to interpret the value " " as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
CODE ERROR:
002770 FORM cdpos_convert_value USING p_cdpos_value TYPE cdpos-value_new
002780 CHANGING p_value TYPE any.
002790 " "
002800 " for conversion of VALUE_OLD and VALUE_NEW, this should be almost the"
002810 " same implementation as LSCD2F01 form EDIT_CDPOS_NEW "
002820 " "
002830 *- begin of local data
002840 DATA: l_dec TYPE i.
002850 DATA: l_type TYPE c.
002860 DATA: l_float type f.
002870 *- end of local data
002880
002890 DESCRIBE FIELD p_value DECIMALS l_dec TYPE l_type.
002900
002910 CASE l_type.
002920 WHEN 'P'.
> l_float = p_cdpos_value.
002940 IF l_dec > 0.
002950 l_float = l_float / ( 10 ** l_dec ).
002960 ENDIF.
002970 * move the value
002980 p_value = l_float.
002990 WHEN OTHERS.
003000 * move the value
003010 p_value = p_cdpos_value.
003020 ENDCASE.
003030
003040 ENDFORM. " cdpos_convert_value
Edited by: FelipeUribe on Apr 23, 2010 6:40 PM -
While saving the delivery no in VA02 dump error showing (Arithmatic overflo
Hi,
while saving the delivery no in VA02, one dump error getting displayed.
Arithmatic over flow occurs.
Can any one can say how to rectify the program to avoid dump error
The below lines are showing in dump.
Waiting for quick response.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
caught in
procedure "USEREXIT_SAVE_DOCUMENT_PREPARE" "(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:
An overflow was discovered in an ongoing arithmetical operation with
operands of type P. Possible causes are:
1. The result field of type P is too small for the result.
2. The result or a intermediate result has more than 31 decimal places.
How to correct the error
The result field must be enlarged, if this is still possible. It may
also be possible to break up the current process into subprocesses so
that only smaller values occur.
There may already be a solution to the error in the SAP notes system.
If you have access to the SAP notes system first try searching with the
following keywords:
"COMPUTE_BCD_OVERFLOW"
"BCD_FIELD_OVERFLOW" (Until release 4.0a, this runtime error occurred at this
position)
"SAPMV50A" or "ZSDI_MV50AFZ1_CRPC_CALC_4QA"
"USEREXIT_SAVE_DOCUMENT_PREPARE" ***----
Information on where terminated
Termination occurred in the ABAP program "SAPMV50A" - in
"USEREXIT_SAVE_DOCUMENT_PREPARE".
The main program was "SAPMV50A ".
In the source code you have the termination point in line 666
of the (Include) program "ZSDI_MV50AFZ1_CRPC_CALC_4QA".
The termination is caused because exception "CX_SY_ARITHMETIC_OVERFLOW"
occurred in
procedure "USEREXIT_SAVE_DOCUMENT_PREPARE" "(FORM)", but it was neither handled
locally nor declared
in the RAISING clause of its signature.
The procedure is in program "SAPMV50A "; its source code begins in line
208 of the (Include program "MV50AFZ1 ".
657 ADD: xvbap-brgew TO l_w_tot_list_vals-brgew,
658 xvbap-zzlogpoint TO l_w_tot_list_vals-zlogpoint,
659 xvbap-zztotgrossvalue TO
660 l_w_tot_list_vals-totgrossvalue.
661
662
663 l_w_tot_list_vals-gewei = xvbap-gewei.
664
665 IF NOT xvbap-pstyv IN zzt_free.
>>>>> ADD xvbap-volum TO l_w_tot_list_vals-volum.
667 ELSE.
668 ADD xvbap-volum TO l_w_tot_list_vals-volum_f.
669 ENDIF.
670 ADD 1 TO l_w_tot_list_vals-zw_nbitem.
Best Regards,
BDP
Edited by: Bansidhar Padhy on Jan 26, 2010 8:24 AMADD xvbap-volum TO l_w_tot_list_vals-volum.
Declare l_w_tot_list_vals-volum as "like vbap-volum" or (preferably) "type volum_ap".
If you're using a packed decimal, you've done something like.... volum(5) type p decimals 2, which is a great way to get an overflow...if you use packed decimals in a program...declare <field> type p decimals <n> without a length attribute, so that SAP can use the full 8 bytes for the calculation.....the put it into a alpha field for display, if needed.... -
Dump when navigating to "text" tab in VA02
Hello,
I am getting dump "Exception condition "CNTL_ERROR" raised" for certain Sales order in VA02 while navigating to Text tab.
I tried Note 316243, the error does not come for that paticular session. Once the system is logged in again, it results in dump. Please suggest a solution. We use SAP 4.6C.
Thanks,
JK.Maybe an error in text customizing (VOTX, VOTXN)
Please also check note 189963. -
Dump run time error "dbif_rsql_sql_error"
Hi guru's,
I have a genric data source with function module which feeds data to a genric ods in bw.
But at time of data upload i see quality status in manage of ods green saying (0 of 0 records extracted) but it asks me to check dump in st22 which is as follows
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Occurred on 21.11.2006 at 23:57:48
An SQL error occurred when accessing a table.
What happened?
What can you do?
Make a note of the actions and input which 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_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"ZL3_BW_SALES_ORDER_ITEM" "(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:
How to correct the error
The exception must either be prevented, caught within the procedure
"ZL3_BW_SALES_ORDER_ITEM"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-01555: snapshot too old: rollback segment
number 222 with name "_SYSSMU222$" too small"
Internal call code.........: "[RSQL/FTCH/VBAP ]"
Please check the entries in the system log (Transaction SM21).
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:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"SAPLZL3_BW_VARIANT" or "LZL3_BW_VARIANTU03"
"ZL3_BW_SALES_ORDER_ITEM"
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....... "wieap053"
Network address.......... "10.50.197.53"
Operating system......... "HP-UX"
Release.................. "B.11.23"
Hardware type............ "ia64"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "wieap007"
Database type............ "ORACLE"
Database name............ "P00"
Database owner........... "SAPR3"
Character set............ "en_US.iso88591"
SAP kernel............... "640"
Created on............... "May 21 2006 20:37:10"
Created in............... "HP-UX B.11.23 U ia64"
Database version......... "OCI_920 "
Patch level.............. "129"
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.............. 001
User................ "RFC_P92"
Language key........ "E"
Transaction......... " "
Program............. "SAPLZL3_BW_VARIANT"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where termination occurred
The termination occurred in the ABAP program "SAPLZL3_BW_VARIANT" in
"ZL3_BW_SALES_ORDER_ITEM".
The main program was "SBIE0001 ".
The termination occurred in line 240 of the source code of the (Include)
program "LZL3_BW_VARIANTU03"
of the source code of program "LZL3_BW_VARIANTU03" (when calling the editor
2400).
The program "SAPLZL3_BW_VARIANT" was started as a background job.
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "ZL3_BW_SALES_ORDER_ITEM" "(FUNCTION)" but was not handled locally,
not declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLZL3_BW_VARIANT ". Its source code starts
in line 5
of the (Include) program "LZL3_BW_VARIANT$03 ".
Source code extract
002100 a~werks
002110 c~edatu
002120 a~aedat
002130 a~erdat
002140 FROM ( vbap AS a
002150 INNER JOIN vbak AS b
002160 ON a~vbeln = b~vbeln
002170 AND b~vbtyp = 'W' "C0006-R2
002180 INNER JOIN vbep AS c
002190 ON a~vbeln = c~vbeln
002200 AND a~posnr = c~posnr
002210 AND c~etenr = '1' )
002220 WHERE a~vbeln IN
002230 ( SELECT objectid
002240 FROM cdhdr
002250 WHERE objectclas = 'VERKBELEG'
002260 * AND tcode = 'VA02'
002270 AND udate IN l_r_aedat )
002280 OR a~erdat IN l_r_aedat.
002290
002300 ENDIF. "Full or Delta ?
002310 ENDIF. "First data package ?
002320
002330 * Fetch records into e_t_data
002340
002350 FETCH NEXT CURSOR s_cursor
002360 INTO CORRESPONDING FIELDS
002370 OF TABLE l_t_data
002380 PACKAGE SIZE s_s_if-maxsize.
002390
> IF sy-subrc <> 0.
00241 0
002420 CLOSE CURSOR s_cursor.
002430
002440 ** Do not insert the upload date in the timestamp table when testing on
002450 ** the R/3 system
002460 * IF SY-TCODE <> 'RSA3'
002470 * AND SY-TCODE <> 'RSO2'
002480 * AND SY-TCODE <> 'SE37'
002490 * AND I_READ_ONLY IS INITIAL.
002500 *
002510 * ls_zl3_bw_timest-upload_date = sy-datum.
002520 * ls_zl3_bw_timest-oltpsource = s_s_if-dsource.
002530 *
002540 * INSERT INTO zl3_bw_timest VALUES ls_zl3_bw_timest.
002550 *
002560 * ENDIF.
002570
002580 RAISE no_more_data.
002590 ENDIF.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 1
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 Data extraction using SUBMIT_JOB as batch process
SY-MSGTY E SY-MSGID BM
SY-MSGNO 026 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
9 FUNCTION ZL3_BW_SALES_ORDER_ITEM
SAPLZL3_BW_VARIANT
LZL3_BW_VARIANTU03 240
8 FUNCTION RSA3_GET_DATA_SIMPLE
SAPLRSA3
LRSA3U06 74
7 FORM EXTRACTOR_FETCH
%_T002T1
??? 0
6 FORM EXTRACT_EAPI_INTO_QUEUE
%_T002T1
??? 0
5 FUNCTION RSC1_DELTA_BIW_GET
SAPLRSC1
LRSC1U03 390
4 FORM DATA_TRANSFER
GP3Z7WZZ1QZLIWHNBB8PBL5TTS7
GP3Z7WZZ1QZLIWHNBB8PBL5TTS7 128
3 FUNCTION RSAP_DATA_TRANSFER
SAPLRSAP
LRSAPU06 137
2 FUNCTION RSAP_PERFORM_EXTRACTION
SAPLRSAP
LRSAPU19 135
1 EVENT START-OF-SELECTION
SBIE0001
SBIE0001 60
Chosen variables
9 FUNCTION ZL3_BW_SALES_ORDER_ITEM
SAPLZL3_BW_VARIANT
LZL3_BW_VARIANTU03 240
I_DSOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
I_INITFLAG
2
0
I_MAXSIZE 050000
333333
050000
I_READ_ONLY
2
0
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
E_T_DATA[] Table IT_1937[0x103]
I_T_FIELDS[] Table IT_1917[13x30]
I_T_SELECT[] Table IT_1916[1x123]
<%_TABLE_CDHDR> ???
%_DUMMY$$
2222
0000
SY-REPID SAPLZL3_BW_VARIANT
5454543545554544452222222222222222222222
310CAC3F27F61291E40000000000000000000000
SYST-REPID SAPLZL3_BW_VARIANT
5454543545554544452222222222222222222222
310CAC3F27F61291E40000000000000000000000
<%_TABLE_ZL3_VARIANT_CONF> ???
L_R_AEDAT[] Table IT_1938[1x19]
%_SPACE
2
0
S_S_IF-MAXSIZE 050000
333333
050000
S_CURSOR 20
0001
0004
L_T_DATA[] Table IT_1939[0x111]
SY-SUBRC 0
0000
0000
SY-UZEIT 220930
333333
220930
L_T_DATA 00000000000000 ##
2222222222333333333333332222222222222200
0000000000000000000000000000000000000000
... + 40 ######
0000002222222222222222222222222222222222
00000C0000000000000000000000000000000000
... + 80 000000000000000000000000
2222222333333333333333333333333
0000000000000000000000000000000
%_PRINT 001SBIE0001_RFC
2222333544433335544222222222222222222222
000000132950001F263000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 X8 ###A###PX_PAPER DRF
2222222225320004000555545452222222222454
000000000880000100008F010520000000000426
... + 120 C_P92 LIST1S
4553322222222222222222222222222222445535
3F09200000000000000000000000000000C93413
... + 160 TEXT 1 5D 2 ###Y
545522222222323422222222222222320015
4584000000001054000000000000002000E9
L_T_DATA-AEDAT 00000000
33333333
00000000
8 FUNCTION RSA3_GET_DATA_SIMPLE
SAPLRSA3
LRSA3U06 74
I_CHABASNM
222222222222222222222222222222
000000000000000000000000000000
I_DATAPAKID 000000
333333
000000
I_INITFLAG
2
0
I_ISOURCE
222222222222222222222222222222
000000000000000000000000000000
I_MAXSIZE 000000
333333
000000
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
I_RLOGSYS
2222222222
0000000000
I_UPDMODE
22
00
E_T_DATA[] Table IT_1937[0x103]
I_T_FIELDS[] Table[initial]
I_T_SELECT[] Table[initial]
SY ########################################
0000000000000000000000000000000000000000
000100000001000100000000000A000000000000
... + 40 ###############A#######P################
0000000000000004000000050000000000000001
0001000000010001000100000000000000000003
... + 80 ###################g####################
0000000000000000000600000000000000000000
0000000000000000000700000000000000000000
... + 120 #######################################T
0000000000000000000000000000000000010005
0000000000000000000000000000000000060004
... + 160 ################ u############# E0X X1
0000000000000001270000000000000222435253
00000000000000E0050020000C0000C000508081
... + 200 000 ####__S 001
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000010
... + 240 80
222223322222222
000008000000000
S_S_IF_SIMPLE-T_FIELDS Table IT_1917[13x30]
S_S_IF_SIMPLE-T_SELECT Table IT_1916[1x123]
G_T_FIELDS Table[initial]
%_DUMMY$$
2222
0000
G_S_RODCHABAS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
22222222222222
00000000000000
SY-REPID SAPLRSA3
5454554322222222222222222222222222222222
310C231300000000000000000000000000000000
RSAL_S_LOGPARMS-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
G_T_LANGU Table[initial]
E_T_DATA 00000000000000 ##
2222222222333333333333332222222222222200
0000000000000000000000000000000000000000
... + 40 ######
0000002222222222222222222222222222222222
00000C0000000000000000000000000000000000
... + 80 0000000000000000
22222223333333333333333
00000000000000000000000
S_S_IF_SIMPLE-INITFLAG
2
0
S_FNAME ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
S_S_IF_SIMPLE-DSOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
SY-XFORM CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
SY-XPROG SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
S_S_IF_SIMPLE-MAXSIZE 050000
333333
050000
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
S_S_IF_SIMPLE-REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
%_PRINT 001SBIE0001_RFC
2222333544433335544222222222222222222222
000000132950001F263000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 X8 ###A###PX_PAPER DRF
2222222225320004000555545452222222222454
000000000880000100008F010520000000000426
... + 120 C_P92 LIST1S
4553322222222222222222222222222222445535
3F09200000000000000000000000000000C93413
... + 160 TEXT 1 5D 2 ###Y
545522222222323422222222222222320015
4584000000001054000000000000002000E9
G_S_INTERFACE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 000000 000000
2222222222333333222333333
0000000000000000000000000
SYST-REPID SAPLRSA3
5454554322222222222222222222222222222222
310C231300000000000000000000000000000000
7 FORM EXTRACTOR_FETCH
%_T002T1
??? 0
SYST-REPID %_T002T1
2553335322222222222222222222222222222222
5F40024100000000000000000000000000000000
E_T_DATA Table IT_1937[0x103]
SY-SUBRC 0
0000
0000
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
SY-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGNO 026
333
026
%_DUMMY$$
2222
0000
SY-REPID %_T002T1
2553335322222222222222222222222222222222
5F40024100000000000000000000000000000000
6 FORM EXTRACT_EAPI_INTO_QUEUE
%_T002T1
??? 0
G_TABIX 1
0000
0001
SY ########################################
0000000000000000000000000000000000000000
000100000001000100000000000A000000000000
... + 40 ###############A#######P################
0000000000000004000000050000000000000001
0001000000010001000100000000000000000003
... + 80 ###################g####################
0000000000000000000600000000000000000000
0000000000000000000700000000000000000000
... + 120 #######################################T
0000000000000000000000000000000000010005
0000000000000000000000000000000000060004
... + 160 ################ u############# E0X X1
0000000000000001270000000000000222435253
00000000000000E0050020000C0000C000508081
... + 200 000 ####__S 001
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000010
... + 240 80
222223322222222
000008000000000
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
L_T_DATA Table IT_1937[0x103]
C_SUBRC 0
0000
0000
I_OSOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
5 FUNCTION RSC1_DELTA_BIW_GET
SAPLRSC1
LRSC1U03 390
I_CHABASNM
222222222222222222222222222222
000000000000000000000000000000
I_DATAPAKID 000000
333333
000000
I_INITFLAG
2
0
I_ISOURCE
222222222222222222222222222222
000000000000000000000000000000
I_MAXSIZE 000000
333333
000000
I_PRIVATE_MODE
2222
0000
I_READ_ONLY
2
0
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
I_RLOGSYS
2222222222
0000000000
I_UPDMODE
22
00
E_T_DATA[] Table IT_1926[0x103]
I_T_FIELDS[] Table[initial]
I_T_SELECT[] Table[initial]
SBIWA_C_FLAG_OFF
2
0
L_PROGNAME
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
L_FUNCTION /BIC/QIZL3_BW_SALES_ORD__10001
244425454354555444554545533333
F293F19AC3F27F31C53FF24FF10001
L_T_QRFCRCV Table IT_1936[1x56]
L_SUBRC 0
0000
0000
S_READ_ONLY
2
0
L_DELTA_TYPE E
4222
5000
RSAOT_C_DELTA-OWN E
4222
5000
SYST-REPID SAPLRSC1
5454554322222222222222222222222222222222
310C233100000000000000000000000000000000
RSAOT_C_DELTA-ALE A
4222
1000
L_NO_MORE_DATA
2
0
L_UPDMODE D
42
40
SBIWA_C_UPDMODE_DELTA D
42
40
RSAL_SAVE_SUBRC 0
0000
0000
L_POOLNAME %_T002T1
2553335322222222222222222222222222222222
5F40024100000000000000000000000000000000
S_S_ROIS-ISOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
G_FLAG_INTERFACE_INITIALIZED X
5
8
<%_TABLE_ROOSPRMSC> ???
%_SPACE
2
0
SYST ########################################
0000000000000000000000000000000000000000
000100000001000100000000000A000000000000
... + 40 ###############A#######P################
0000000000000004000000050000000000000001
0001000000010001000100000000000000000003
... + 80 ###################g####################
0000000000000000000600000000000000000000
0000000000000000000700000000000000000000
... + 120 #######################################T
0000000000000000000000000000000000010005
0000000000000000000000000000000000060004
... + 160 ################ u############# E0X X1
0000000000000001270000000000000222435253
00000000000000E0050020000C0000C000508081
... + 200 000 ####__S 001
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000010
... + 240 80
222223322222222
000008000000000
SBIW_C_TRUE X
5
8
SY-REPID SAPLRSC1
5454554322222222222222222222222222222222
310C233100000000000000000000000000000000
QS_NOSENDS NOSENDS
44544452
EF35E430
4 FORM DATA_TRANSFER
GP3Z7WZZ1QZLIWHNBB8PBL5TTS7
GP3Z7WZZ1QZLIWHNBB8PBL5TTS7 128
SY-SUBRC 0
0000
0000
SY-REPID GP3Z7WZZ1QZLIWHNBB8PBL5TTS7
4535355535544544443544355532222222222222
703A77AA11AC978E22802C544370000000000000
SPACE
2
0
SYST-REPID GP3Z7WZZ1QZLIWHNBB8PBL5TTS7
4535355535544544443544355532222222222222
703A77AA11AC978E22802C544370000000000000
%_DUMMY$$
2222
0000
P_S_REQUEST-UPDMODE D
42
40
SBIWA_C_UPDMODE_DELTA D
42
40
SBIWA_C_UPDMODE_REPEAT R
52
20
SRSC_C_UPDMODE_INITSIMU S
52
30
SBIWA_C_UPDMODE_DELTAINIT C
42
30
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
L_FNAME RSC1_DELTA_BIW_GET
554354445454455445222222222222
2331F45C41F297F754000000000000
P_S_REQUEST-REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
RODKYF
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
22222222
00000000
L_T_ZL3_SALES Table IT_1926[0x103]
ROISGEN ZL3_BW_SALES_ORDER_ITEM PHD00
5435455544455454455454422222225443322222
AC3F27F31C53FF2452F945D00000000840000000
... + 40 PBW82 T /B
5453322222522222222222222222222222222224
02782000004000000000000000000000000000F2
... + 80 IC/CCPB0000000766 3Z7WZZ1QZLIW
4424454333333333322222222222353555355445
93F33020000000766000000000003A77AA11AC97
... + 120 HNBB8PBL5TTS7
4444354435553222222222222222222222222222
8E22802C54437000000000000000000000000000
... + 160 RFC_P92
2222222222222222222222222222222225445533
000000000000000000000000000000000263F092
... + 200 20060322161543 000000000
2222233333333333333222222222222333333333
0000020060322161543000000000000000000000
... + 240 00000
33333
00000
ROIST
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222
0000000000000000000000000000000
%_PRINT 001SBIE0001_RFC
2222333544433335544222222222222222222222
000000132950001F263000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 X8 ###A###PX_PAPER DRF
2222222225320004000555545452222222222454
000000000880000100008F010520000000000426
... + 120 C_P92 LIST1S
4553322222222222222222222222222222445535
3F09200000000000000000000000000000C93413
... + 160 TEXT 1 5D 2 ###Y
545522222222323422222222222222320015
4584000000001054000000000000002000E9
3 FUNCTION RSAP_DATA_TRANSFER
SAPLRSAP
LRSAPU06 137
I_ISOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
I_S_REQUEST REQU_43VWUSBH207E5H8W64KGNKSPNDZL3_BW_SA
5455533555544333434353344445544543545554
2515F436753282075588764B7EB30E4AC3F27F31
... + 40 LES_ORDER_ITEM 20061121210928RFC_B
4455454455454422222223333333333333354454
C53FF2452F945D000000020061121210928263F2
... + 80 W PHD00 PBW82 000000D T X
5222222544332222254533222223333334252252
7000000084000000002782000000000004040080
... + 120 X
5
8
I_T_SELECT Table IT_57[0x123]
RODIOBJCMP 0000
2222222222222222222222222222223333222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
22222222222222
00000000000000
L_S_LOGPARMS-MSGV3
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
RODCHA
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222Tell your basis guys
"ORA-01555: snapshot too old: rollback segment"
ie the job took too long for the current settings you have for rollbacks
They will adjust the settings -
Run Time Error when go to sales order change tcode :va02
Hi All,
I am functional guy and i am facing the following situation
1.System is allowing to create the sales order through VA01 and also saved it
2.When i want to see the same sales order throug Va02 i am getting runtime errorAttach at least a download of the dump (ST22) or post to your post, as you clearly didn't give enough information to get correct answers. (Asking Good Questions in the SCN Discussion Spaces will help you get Good Answers and similar documents.)
Regards,
Raymond -
Dumps while using output types
Hi,
We are to create a PO by giving a output type ZPO2 in the sales order. For this we have configured in NACE the ZPO2 output type with medium as 8 (special function). In NACE we have given the Z program name and the form name (Perform in the Z program).
Now when we give the output type in the sales order and then while debugging we find that the Z program and the form given in NACE is called.
But however when we check the sales order again in TCode VA02 there is a popup mentioning that the update was terminated. In ST22 there are 2 dumps.
1) One with the error DYNPRO_SEND_IN_BACKGROUND and the description in the dump is
The current ABAP program "RSNAST00" had to be terminated because one of the statements could not be executed.
The termination occurred in line 910 of the source code of the (Include) program "RSNAST00"
2) The other dump mentions Too many parameters specified with PERFORM.
In a subroutine call, there were more parameters than in the routine definition.
Error in ABAP application program.
The current ABAP program "RSNAST00" had to be terminated because one of the statements could not be executed.
The termination occurred in line 910 of the source code of the (Include) program "RSNAST00"
In both the cases the termination occurs on:
NAST = TEMP_NAST
Please help me understand what is wrong and how can it be rectified.
Thanks
MickHi Mick James,
About First Error..
Check out there is an Enhancement Point there in program RSNAST00
ENHANCEMENT-POINT OBJEKT_SPERREN SPOTS ES_RSNAST00 STATIC
Check the code in this Enhancement Point...
You must be executing some objects or FMs etc which can not be run in Background because it require SAP GUI
And another You must be passing more parameters in Subroutine while calling it ... Check out the defination of Subroutine and number of parameters you are passing...
Hope it will solve your problem..
Thanks & Regards
ilesh 24x7
ilesh Nandaniya -
Add a new line item in VA01/VA02 using user exits.
Hi Experts,
I have a problem regarding adding of line items in VA01/VA02. I was able to add a line item but my problem is, there is no validation for the added line. I want SAP to validate it before posting it to database. I'm using USEREXIT_SAVE_DOCUMENT_PREPARE for this one.
I also found out from other threads, that adding line items in XVBAP is not advisable since no checking will be done after USEREXIT_SAVE_DOCUMENT_PREPARE.
I'm thinking if I can use FM DYNP_VALUES_UPDATE on one of the user exits to add a line item in VA01/VA02 and let SAP do the checking and validation. This way, I'm sure that the added line is correct and data integrity will be maintained.
Do you have any comments/suggestions about this?
Thanks a lot,
Arman.Hi,
I am trying to do this as well but I don't get it working...
I am able to add records to XVBAP, but those never show up in my sales order.
I have found that I should also add records to XVBEP, XKOMV and XKOMP before it will be working, but when I add something to XVBEP I do get a dump on SAVE.
I would like to ask people that managed to get this working to post the code as an example here.
Thanks and best regards,
Marnix -
ABAP DUMP when I do a document flow
Hi Experts-
In transaction VA02, once inside the document, when I do a document flow, I am receiving ABAP run-time error message.
However, when I do document from the initial screen of VA02, I am able to see the document flow.
I have checked the OSS notes, but do not find any existing note related to this.
Any thoughts?
Cheers,
SyedHi:
The best way to deal with this (if you have not ABAP experience) is to get a ABAPer to look at it with you. You can check transaction ST22, there you will find the details of the dump. when you double-click on your report (dump) and scroll down, you will see some numbers on the left of the page then there will be an interrupt in the sequence and an arrow -
> will be seen, this would be the point where the dump occurred. Hopefully this will give some clue to what is happening.
Regards
please reward if helpful
Aaon -
Hi,
I need a solution for the short dump which i'm getting at the time of accessing the XD02/XD03 transaction for only one particular customer number.
Interestingly the same customer number was useful in that transaction a week before and i was able to add that customer as my shipto in my sales order with all its addresses appearing. Now no details of that customer is appearing and when i double click on shipto field (at VA02) or given the same number at XD02/XD03 transaction, an short dump arises.
It says this...
Program "SAPLSZA1" tried to use screen 0000.
The screen does not exist.
Source code extract
000010 * ABAP-System Include for all programs
000020 constants SPACE value ' ' %_predefined.
000030
000040 * SYST-Felder als SY-Felder ansprechbar machen.
000050 tables: SYST,
000060 sy %%internal%%.
000070 *
000080
000090 tables RSJOBINFO. "for SUBMIT .. VIA JOB ..
000100
000110 data: begin of common part %_SYS%%,
000120 SCREEN type SCREEN,
000130 %_PRINT type PRI_PARAMS,
000140 %_ARCHIVE type ARC_PARAMS,
000150 end of common part.
000160 *
000170 data: %_VIASELSCR type X value '04' %_predefined.
000180
000190 system-exit.
000200 perform (SY-XFORM) in program (SY-XPROG).
000210
000220 * Nach Laden des Dynpros
000230 module %_CTL_INIT output.
000240 perform %_CTL_INIT in program SAPMSSYD using SY-REPID if found.
> endmodule.
000260
000270 * Nach DCO
000280 module %_CTL_OUTPUT output.
000290 perform %_CTL_OUTPUT in program SAPMSSYD using SY-REPID if found.
000300 endmodule.
000310
000320 * Vor DCI
000330 module %_CTL_INPUT input.
000340 perform %_CTL_INPUT in program SAPMSSYD using SY-REPID if found.
000350 endmodule.
000360
000370 * Vor at exit-Modul (wenn vorhanden)
000380 module %_CTL_AT_EXIT input.
000390 perform %_CTL_AT_EXIT in program SAPMSSYD using SY-REPID if found.
000400 endmodule.
000410
000420 * Erstes Modul in PAI
000430 module %_CTL_PAI input.
000440 perform %_CTL_PAI in program SAPMSSYD using SY-REPID if found.
I have also got a message in the "How to correct the error" column to search for some OSS note for this issue. I tried and not able to find the exact one. The search criteria proposed for the OSS note was
"DYNPRO_NOT_FOUND" C
"SAPLSZA1" or "<SYSINI>"
"%_CTL_INIT"
This dump appears only for one customer number and all the other numbers are working fine at XD02/XD03. Please help me with your valuable solutions.Hi Ravi,
Thanks again.
I performed the steps suggested by you and found the following implementations were available.
<u>For CUSTOMER_ADD_DATA Badi</u>:
1. FM_CUSTOMER_ADD_DATA - Implementation of CUSTOMER_ADD_DATA by Public Sector
2. ZCUSTOMER_ADD_DATA - For adding custom field in the Customer Master
<u>For CUSTOMER_ADD_DATA_BI Badi</u>:
1. FM_CUSTOMER_ADD_D_BI - IS-PS: Additional Data for Customers (Batch-Input and ALE)
<u>For CUSTOMER_ADD_DATA_CS Badi</u>:
1. FM_CUSTOMER_ADD_D_CS - Implementation of CUSTOMER_ADD_DATA_CS by Public Sector
2. ZCUST_ADD_DATA_CS - Adding custom field to the customer master
Now shall i just give these names and deactivate in Se19. Sorry it might be silly but i really haven't worked on badi's. Hope deactivating it will not cause any surprising behaviour in the transaction.
Please let me know your comments. -
Dump occured in standard program SAPMV45A (order creation)
hi,
In order creation, a dump is occured in standard program SAPMV45A. Because of in FM "Pricing_Dialog_Tabstrips" is incorrect and TAXI_TABSTRIP_C and TAXI_TABSTRIP_ITEM" specified here is a different field type.This is standard program we can not change field type. Kindly provide any OSS notes for this or any other solution.
STANDARD PROGAM - SAPMV45A
INCLUDE PROGRAM - MV45AF0F_FCODE_PKO4
ERROR - Runtime Error CALL_FUNCTION_CONFLICT_TYPE has occurred
Kindly help me, Its very uigent
thanks in advance.hi
Please note SAP redesigned the condition screen and it's
underlaying logic completely starting with release 4.6A.
Hence you should not use the function codes PKON and KKON any longer.
Furthermore screen 6201 and all includes stored in program pool SAPMV61A
are not used by the standard any more. The new condition sub-screen
is placed in program pool SAPLV69A and triggered by function
codes KKO1 (= jump into header condition screen) or PKO1 (= jump into
item condition screen). Further details you can find in the SAP
note 360942.
So, In release 470 & above , function code PKON to display the conditions in a
sales order via VA01, VA02 and VA03 may lead this short dump. To avoid
this short dump, I recommend you to use the function code PK01 instead
Hope this helps
Paul Quinn -
DELETE SD DOCUMENT (VA02)- ILLEGAL MESSAGE
Hi all
i have a strange problem
it's occurs when i delete an sd document in va02.
the dump is DYNPRO_MSG_IN_HELP.
The situation is:
in the save_document_prepare the are some controlls. one sends an error message.
Now when I save the document, the message starts and I am not able to save the document.
Instead, if I try to delete the document, at the message the program dumps.
do Any one know why?
Bye
enzoWell I find a trick.
I was not able to solve the dump,
but when I enter in the delete process the system fill the variable
ereignis
with 'DELETED', so at the beginning of save_document_prepare I put a
check ereigins ne 'DELETED'.
so the user exit does not performed in delete process.
Regards
enzo -
Lock ups and dumping psyical memory!!!
Hi i have just installed a new pc most of the stuff im useing is from my old computer so i know they work fine im running a:
P4 3GHZ Prescot 800MHz, HT-Enabled
865PE Neo2-P
512 DDR-400 Twin moss
ATI Radeon 9000 pro
PSU-400
XP Pro
My computer locks up alot when running intense games (games have worked before no problem) i also get a error saying dumping pysical memory, i have looked about and tried to solve this myself, i found that someone was haveing the exact same problem as me and he fixed it by turning the FSB down as his memory wasnt compatable with his motherboard if doing that works how do i do it ?
Many thanks JonathanFlappa, Your memory " clock" is fine and there is no need to "underclock it" as long as you did not mess with the Bios.
I had the same problems. I could not even get thru a Clean install of windows as it would Blue Screen
1- are you running in " Dual Channel Mode"?
2- If so is your memory a " match Set"?
some times memory even thought it has the same markings is not matched . Dual channel sets are matched and made to run together in "Dual Channel Mode"{
( Even though I had the same manufacturer memory my set would not run in Dual Channel without " Blue Screening" I bought a Matched Set of Kingston Valueram and have not had a problem since
3- If it is not a matched set, pull one stick out and run it for a while , if it still bluescreens try the other stick
4- raise your memory voltage to 2.7 or 2.8 ( which ever is the lowest that it runs stable)
5- If all this does not work , run MEMTEST to see if there is a problem with both sticks
6- you are running a Bios Version that supports the " Prescott Microcode" right?
Let us know what your findings are
Good Luck
Dave -
Report J_1IEWT_CERT getting cancelled, generating ABAP dump!
A long running report J_1IEWT_CERT in background mode is getting cancelled after running for a while and generating the following dump :
Error analysis
When changing or deleting one or more lines of the internal table
"\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]" or when inserting in the table
"\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]", 0 was used as
the line index. An index less than or equal to zero is not
allowed.
The error can occur when using the following options:
1. "INDEX idx" for specifying the line number in the table
"\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]"
where you want to change, insert or delete.
2. "FROM idx" for specifying the start index when deleting a line
area from or inserting a line area into the table
"\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
3. "TO idx" for specifying the end index when deleting a line
area from or inserting a line area into the table
"\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
At the time of the termination, the table contained 17008 lines.
How to correct the error
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:
"TABLE_INVALID_INDEX" " "
"J_1IEWT_CERT" or "J_1IEWT_CERT_F01"
"FILTER_DATA"
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".
Tried searching for some SAP Notes to fix the issue, no success as of now, Please help me out...Have you checked these notes ?
363107 Short dump occurs during TDS certificate printing.
803806 Error while genrating TDS certificate 03.01.2005
1066049 J1INCERT - Error while generating TDS certificate
Regards,
Subhash -
Short dump 'Table does not exist in database'
Hello All,
When a report is executing it is going to short dump by saying 'Table does not exist in database'. As per the short dump analysis this issue is happening because of the following Native SQL statement statement :
Program : %_T050N0 (This is a dynamic program generating by SAP )
Form Name : DYN_LIC_SEL_TOT
exec sql performing LOOP_MOVE_WRITE_ISAP.
select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty into :dcat-lplate, :dcat-matnr,
:dcat-werks, :dcat-charg, :dcat-holdflag,
:dcat-qty from ZLICENSE_R2 where itm_num = :p_matnr and
model_lot = :p_charg
endexec.
As per the customer this issue occurring since they migrated the SAP back-end data base from Oralce to DB6. Here I felt that ZLICENSE_R2 is not migrated from the Oracle to DB6. But as per the BASIS Team, even this table was not maintained in Oracle also. If the table was not maintained in the Oracle, this issue should have been there even before migration also.
Following is the short dump details:
Short text
Table does not exist in database.
What happened?
The table or view name used does not
exist in the database.
The error occurred in the current database connection "DEFAULT".
What can you do?
Check the spelling of the table names in your report.
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.
The exception, which is assigned to class 'CX_SY_NATIVE_SQL_ERROR', was not
caught in
procedure "DYN_LIC_SEL_TOT" "(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:
Triggering SQL statement: "select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty from ZLICENSE_R2 where itm_num = ? and model_lot = ? "
Database error code: "-204"
Could you please let me know what might be the reason for this issue.
Many Thanks in Advance.Transaction SE11, input ZLICENSE_R2 for table name, and display the table. Did the table display? If not, that is the main problem.
If the table displays, go to menu item Utilities -> Database Object -> Database Utility
In the resulting screen, under the "Status" fields, you should see text "Exists in the database." If you don't, then the table exists in the dictionary, but doesn't exist in the database system. Click the "Create database table" button and then you should be able to run the program.
You may need basis team's help to carryout some of these actions.
Maybe you are looking for
-
Hi, We have couple of MSAD users in a native group which has admin rights to Essbase server as well as Shared Services in 11.1.2.1. Can login to EAS but when we expand the Essbase servers we get "Error 1051293: Login fails due to invalid login creden
-
Authentication Web Services for Java applications
Hi All, We are building Java based SAP applications for mobile devices such as Blackberry, iPhone etc. The applications are browser based (thin client) to be deployed on SAP Netweaver WAS and would interface with SAP backends such as SAP ECC, SAP BW
-
i've got an error in generating maskfile. i used the command : maskgen cref <Directory>\filename.jca it shows an error message i.e :Package 0xa0:0x00:0x00:0x00:0x62:0x01:0x01 1.0 imported by applet is missing can any body knows how to use makgen in t
-
Hi, I have migrated from a 10.4.11 -> 10.5.3 server. I've found a lot of database errors in the log: Jun 11 23:40:04 headlines ctl_cyrusdb[1782]: checkpointing cyrus databases Jun 11 23:40:04 headlines ctl_cyrusdb[1782]: DBERROR db4: /var/imap/tls_se
-
I am new to Java and have a project where I need to change some info in a DB2 table. I keep getting the following run time error. LRAM-BRIO-T2/BRIOT is not a valid database name. It seems to be dropping the last part of the database name. Am I missin