Removing ABAP dump when JDBC is down in RFC- JDBC- RFC scenario
Hi All,
I need help to build one scenario.
I am working on RFC->XI->JDBC->XI->RFC scenario. It is working fine.
But problem is that whenever JDBC server is down RFC is giving ABAP dump in SAP. How can i Remove ABAP dump in SAP and give information to RFC that "JDBC is out of order"
Is it possible to implement without BPM, then How?
If not possible then what could be the steps of BPM?
Thanks & Regards
Rohan,
1.Recive Step should open the Synch - Asynch Bridge
2. Block Step --> Send Synchronous inside this step with an Exception Hanler.
3. Now in the exception ahndler step, do the necessary error handling requirement.
4. Send Step --> closes Synch Asynch bridge.
My question is what data do you want to send back to the RFC if the DB is down? This data should be populated inside the exception handling block and then this data should be mapped to the corresponding RFC response and used in the step 4.
Regards,
Bhavesh
Similar Messages
-
ABAP Dump when calling Function Module Starting New Task
Hi all. I have a tricky situation now, I am doing a POC on parallel processing.
I am getting an ABAP dump on the following Call Function line which is in class lcl_steer_114numc (See below for full program):
METHOD start.
CALL FUNCTION 'Z_ZZCLS_STEER_114NUMC'
STARTING NEW TASK me->id
CALLING me->finish ON END OF TASK.
ENDMETHOD. "start
However I get the following ABAP dump:
Short text
Statement "CALL FUNCTION .. DESTINATION/STARTING NEW TASK/IN BACKGROUND TASK"
The function module only contains a wait statement to simulate parallel processing. It is strange that it dumps here, because when I change the FM call to another call that has been triggered successfully from other classes, it still produces the same ABAP dump.
The background of the Proof Of Concept is to see if I can get an event to trigger the next process that depends on the outcome of the previous process. Parallel processes are run in the start methods by calling RFC.
<Garbled code removed>
Moderator Message: Please post relevant portions of the code only.
Edited by: Suhas Saha on Jul 17, 2011 1:17 PMWell, the thing is I did manage to run 3 other Function Modules asynchronously succeesfully prior to that function call, with the same exact function call syntax. Further more, I have tried editing it with your suggestion but I get the exact same dump.
The complete function group can be downloaded here (slinkee file):
https://docs.google.com/leaf?id=0B3sua1Bw4XK4ZmFhNzcwMTgtYzQ0Mi00NzQ4LTg5YTMtNDNlNWUxYTM2NTg3&hl=en_US
The complete program can be downloaded here (slinkee file):
https://docs.google.com/leaf?id=0B3sua1Bw4XK4YWJmNjU3ODYtODRmMy00Nzg2LThkNTUtZjNkNDRhZGQ3MTUw&hl=en_US
The complete ST22 dump can be found here:
https://docs.google.com/leaf?id=0B3sua1Bw4XK4ZDU1YmFkZDAtOTU5MS00ZTgwLWFlZTktNWZhMDUxMzJlZWNl&hl=en_US
Basically I ST22 gives me the following:
Runtime Errors RPERF_ILLEGAL_STATEMENT
Date and Time 17.07.2011 05:29:54
|Short text |
| Statement "CALL FUNCTION .. DESTINATION/STARTING NEW TASK/IN BACKGROUND TASK" |
|What happened? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "Z_ZZB1_CLOSE_PERIOD_TEST2" had to be terminated |
| because it has |
| come across a statement that unfortunately cannot be executed. |
And it explains it here (but is not helpful / relevant at all) as I ran the program from SE38.
|Error analysis |
| There is probably an error in the program |
| "Z_ZZB1_CLOSE_PERIOD_TEST2". |
| The program was probably called in a conversion exit |
| or in a field exit. These are implemented by |
| function modules called CONVERSION_EXIT_xxxxx_INPUT/OUTPUT or |
| USER_EXIT_xxxxx_INPUT. |
| Conversion exits are triggered during screen field transports or |
| WRITE statements, field exits during field transports from the |
| screen to the ABAP/4 program. |
| In this connection, the following ABAP/4 statements are not allowed: |
| |
I hope you try to download the slinkee files and you will notice the call function I performed was no different than the other call function RFC calls that really are working. -
ABAP dump when running an ALV report in a portal
Hi,
I have an ABAP report created in SAP R/3 4.7. Am using the ALV function module REUSE_ALV_GRID_DISPLAY to display the output. The programs runs correctly when run in R/3 using the SAP GUI.
When the report is run in the portal, I get a runtime error 'MESSAGE_TYPE_X'.
Please let me know if anybody has faced such issues.
I checked the OSS note 702732 which talks about increasing the threshold value of the start parameter. But this is not agreed by the BASIS team.
Thanks,
Best regards,
Ajith
The ST22 error log is as follows:
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
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
Short text of error message:
Data volume (84.550.400 bytes) is too large. (abap/alvgrid/size_nodod_mb
Technical information about the message:
Diagnosis
You tried to send a data record to the front-end that contains
84.550.400 bytes. However, the data volume is restricted to
52.428.800 bytes.
System Response
The running application program was terminated with a runtime
error.
Procedure
Restrict the data selection if possible or contact your system
administrator.
Procedure for System Administration
You can set the maximum size of these data volumes using the kernel
parameter 'abap/alvgrid/size_nodod_mb' (in megabytes).
Message classe...... "S>"
Number.............. 890
Variable 1.......... "84.550.400"
Variable 2.......... "52.428.800"
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"MESSAGE_TYPE_X" C
"SAPLAWRT" or "LAWRTU22"
"ITS_CHECK_ALV_DATA_SIZE"
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.
Information on where terminated
The termination occurred in the ABAP program "SAPLAWRT" in
"ITS_CHECK_ALV_DATA_SIZE".
The main program was "Z_BW_RECON_INV_RPT ".
The termination occurred in line 25 of the source code of the (Include)
program "LAWRTU22"
of the source code of program "LAWRTU22" (when calling the editor 250).
Source code extract
000010 FUNCTION ITS_CHECK_ALV_DATA_SIZE.
000020 *"
000030 ""Lokale Schnittstelle:
000040 *" IMPORTING
000050 *" REFERENCE(DATA_TABLE) TYPE TABLE
000060 *"
000070
000080 data n type i.
000090 data currsize type i.
000100 statics maxsize type i.
000110 data par_value(56).
000120 if maxsize is initial.
000130 sy-subrc = 0.
000140 CALL 'C_SAPGPARAM' ID 'NAME' FIELD 'abap/alvgrid/size_nodod_MB'
000150 id 'VALUE' field par_value.
000160 if sy-subrc ne 0.
000170 maxsize = 52428800. " Default 50 MB
000180 else.
000190 maxsize = 1048576 * par_value.
000200 endif.
000210 endif.
000220 describe table data_table lines n.
000230 currsize = sy-tfill * sy-tleng.
000240 if currsize gt maxsize.
> message x890(s>) with currsize maxsize.
000260 endif.
000270 ENDFUNCTION.HI,
This is a Memory problem.
System is allocated with a Max Memory of 50 MB,(see the dump code, in the last it is hardcoded in the std code)
The data of your report is coming around 83 MB.
Restrict your selection criteria of the Object and run the same report and see. it will work.
Regards,
Anji -
Dear gurus:
I just faced an annoying problem when executing DTP in t-code RSA1. It appears an ABAP dump here. The ABAP dump is briefly shown below. And I found that it seems to be an authorization problem, because when I use a new account which has SAP_ALL authorization, then it works. So it may lack of some authorizations, but it's hard to figure it out. T-code su53 cannot check it properly. Need your help and thanks a lot.
Runtime Errors MESSAGE_TYPE_X
Date and Time 2007.06.20 11:17:30
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Invalid program status
Long text of error message:
Technical information about the message:
Message class....... "RSBK"
Number.............. 299
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "Hai Wei,
This dump is due missing of OCX files while installing SAP GUI Front end just find out the exact files and copy and paste them in the Front end files files then ur prob will be solved.......
If in case any issues let me know.
Regards
Madhavi -
ABAP dump when user login in to PRD system
Hi Experts,
From today morning our users are facing one severe issue.The users when ever they login into the system the ABAP dump is occuring like "Database inconsistency: Start transaction SICK ",when i execute the SICK t-code it is showing errors.
SAP System Check
no application server offers an VB service
Severe problems were detected during initial system check.
Please, do not use that system before fixing these problems.
our go live was before one month only,now we are facing this issue.our kernel release is 740 and DB sybase ASE 15.7.0.1010. please suggest us what can we do.
regards,
Patan Thavaheer.|15.05.2014 Active parameters 12:47:40 |
|Parameter Name |Parameter value Parameter Value - Continued |
|login/disable_multi_gui_login |1 |
|rdisp/wp_no_enq |1 |
|login/no_automatic_user_sapstar |0 |
|SAPSYSTEMNAME |XXX |
|SAPGLOBALHOST |XXXXXX |
|SAPSYSTEM |00 |
|INSTANCE_NAME |DVEBMGS00 |
|DIR_CT_RUN |$(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64 |
|DIR_EXECUTABLE |$(DIR_INSTANCE)\exe |
|DIR_PROFILE |\\XXXXXX\sapmnt\XXX\SYS\profile |
|_PF |$(DIR_PROFILE)\XXX_DVEBMGS00_XXXXXX |
|SETENV_00 |PATH=$(DIR_EXECUTABLE);%PATH% |
|Start_Program_00 |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) |
|_CPARG0 |list:$(DIR_GLOBAL)/syb/NTAMD64/cpe_sybjdbc.lst |
|_CPARG1 |source:$(DIR_GLOBAL)/syb/NTAMD64 |
|Start_Program_01 |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0) $(_CPARG1) |
|Start_Program_02 |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) |
|_CPARG2 |list:$(DIR_GLOBAL)/syb/NTAMD64/cpe_sybodbc.lst |
|_CPARG3 |source:$(DIR_GLOBAL)/syb/NTAMD64/sybodbc |
|Start_Program_03 |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG2) $(_CPARG3) |
|_CPARG4 |list:$(DIR_CT_RUN)/sapcrypto.lst |
|Start_Program_04 |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG4) |
|SAPJVM_VERSION |6.1.048 |
|DIR_SAPJVM |$(DIR_EXECUTABLE)$(DIR_SEP)sapjvm_6 |
|jstartup/vm/home |$(DIR_SAPJVM) |
|Start_Program_05 |immediate $(DIR_CT_RUN)\strdbs.cmd XXX |
|sec/libsapsecu |$(ssl/ssl_lib) |
|ssf/ssfapi_lib |$(ssl/ssl_lib) |
|rdisp/wp_no_dia |10 |
|rdisp/wp_no_btc |3 |
|_DW |$(DIR_EXECUTABLE)\disp+work$(FT_EXE) |
|Start_Program_06 |local $(_DW) pf=$(_PF) |
|_IG |$(DIR_EXECUTABLE)\igswd$(FT_EXE) |
|Start_Program_07 |local $(_IG) -mode=profile pf=$(_PF) |
|rdisp/wp_no_vb |1 |
|rdisp/wp_no_vb2 |1 |
|rdisp/wp_no_spo |1 |
|ssl/ssl_lib |$(DIR_EXECUTABLE)$(DIR_SEP)$(FT_DLL_PREFIX)sapcrypto$(FT_DLL) |
|SETENV_01 |SECUDIR=$(DIR_INSTANCE)/sec | -
ABAP Dump when running S_ALR_87100205 (RFHABU00N)
Hi,
We are implementing New GL for a company code in Turkey. When I trying to run the report RFHABU00N for non-leading ledger, I am getting an abap dump because the program is not able to report the output for non-leading ledger documents. The report outputs correct information when executed for the leading ledger.
has any one else faced this issue in the past and if so how was it resolved.
We are currently on SAP ECC 6.04.
Thanks,
NitinHi,
What is the dump message exactly? Anyway, for execution of this report for non-leading ledger, please, consult the following notes:
1883338 - RFHABU00N Long runtimes and termination
1965855 - RFHABU00/RFHABU00N: General Ledger View
1965562 - SAPDBBRF: Fiscal year not correctly delimited for non-leading ledgers
1939154 - RFHABU00N: Documents from non-leading ledgers ignored
Regards,
Eli -
Hi Getting Abap dump when in RRP3 when deactivating the DP Planning area
Hi
We are using the Consumption group by this releasing Forecast to SNP at Customer level also along with product and location level,i am doing in dev only,
Issue :I have deactivated the DP Planning area(because of some modification) then activated/Initialized the DP Planning area, After that when I see in the RRP3 for the product it is getting Abap dump,CVCs now it is available also, Please let me know how to correct itKKK,
I doubt that the event of deactivating/reactivating the DP PA is the cause of your ABAP dumps in //RRP3. More likely the problem is related to a LC inconsistency, or a userexit.
Run all of your LC consistency checks, they are easy to do and quick to run. And, like any other dump, read the messages in the dumps to find out what went wrong.
Best Regards,
DB49 -
ABAP Dump when using Shift Related Confirmations in CO11N
Dear SAP Gurus,
We have activated business function LOG_PP_SRN_CONF for doing shift
related confirmations using T Code CO11N.
On entering the production order and operation number in CO11N, the
system proposes the actual data. Then we select the shift number.
If we try to change the selected shift again, the system gives an ABAP
dump - "OBJECTS_OBJREF_NOT_ASSIGNED" and exits the program.
Please suggest some SAP Note or other solution for the problem.
Thanks!
With Regards,
NitinDear Prasobh,
Thanks for the quick reply.
I have checked the OSS Note - 1359966 as mentioned by you.
However, there are 2 things which make me feel that the note is not relevant to my scenario -
1. The note says that the confirmation profile for CO11N includes the detail area "0240-Quantities: Subdivided Quantities". I'm not using this detail area in my confirmation profile. Instead, I'm using the detail area "0200-Quantities: yield/scrap/rework/reason".
2. System may issue termination message COCF 000 when single-screen entry for the confirmation (CO11N) is called by another application such as the order information system (COOIS). However, I'm getting this dump when i run the T Code CO11N directly. Further, I don't get the termination message at all.
Please suggest.
With Regards,
Nitin -
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 -
ABAP DUMP WHEN Executing GANTT CHART IN CN41N TCODE
Hi,
we are getting the following error while trying to display gantt chart in CN41N Tcode.
A calculation field is defined too small.
The current ABAP program "FCNGR000" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
caught in
procedure "GET_WORKAREA" "(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:
A value generated during processing is too large for the
field "ALL_OBJ-VDAUER" of the program "FCNGR000".
any suggestion.please.
nazi.Should be rather obvious? The domain for VDAUER is Dec 10,1. The dump would suggest that you've getting a value for VDAUER that's more than 10 digits long?
-
ABAP Dump when executing tcode CATS_APPR_LITE for multiple selection.
Dear Members,
Issue:
When executing tcode CATS_APPR_LITE for Time Approval from the remote R/3 by selecting multiple selections and click on Approve, if you get a dump saying CALL_FUNCTION_REMOTE_ERROR
Analysis:
If there is an SAP Note applied in 1368487 and at CALL FUNCTION CATS_CHECK _PTEXDIR FM getting the dump because in source system for this function module Remote Enabled Module option is not checked.
To resolve this correction note 1430042 has to be applied.
Regards
DurgaDear Members,
Issue:
When executing tcode CATS_APPR_LITE for Time Approval from the remote R/3 by selecting multiple selections and click on Approve, if you get a dump saying CALL_FUNCTION_REMOTE_ERROR
Analysis:
If there is an SAP Note applied in 1368487 and at CALL FUNCTION CATS_CHECK _PTEXDIR FM getting the dump because in source system for this function module Remote Enabled Module option is not checked.
To resolve this correction note 1430042 has to be applied.
Regards
Durga -
ABAP Dump when selecting Calendar Field for selection in Working Time reports
Hi Team,
Out client gets a weird issue, when he selects date from selection he gets dump, this is happening only in his system, If he tries from his same user id from different machine, he is not getting the error.
Dump details below
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Thanks ~ PriyaHi Krishnan,
this issue is most likely related to some missing\unregistered components in SAPGUI folder. There are a few ways to solve this kind of errors:
1. In order to check it, ask your client to go to 'C:\Program Files (x86)\SAP\SapSetup\Errors\' path and open an .xml file, which is the error report file that contains error log created during SAPGUI client installation. The erroneous modules can be registered by using regsvr32 command via command line. (Make sure you have Administrator rights while doing this.)
2. If previous step did not help, run SAP Logon, goto Options->System Information->'Check SAP GUI Installation' and run the report.It will open an xml file with the errors report.
3. If none of steps helped, then reinstall SAPGUI client. You need to run installation under Administrator user rights.
BR -
Urgent: ABAP Dump when using ME9F
Hi All,
I am using ME9F transaction to re-print POs. I get a short dump stating error "MOVE_TO_LIT_NOTALLOWED_NODATA". This just started happend after we applied the support packs. We are using custom SAP Script form.
Did anyone ever experience this problem before with ME9F or anywhere else.
Any ideas/suggestions will be greatly appreciated.
Thanks in advance.Check out oSS # 354101
FYI
ME9E: short dump for releases with web releases
Symptom
If messages of JIT delivery schedules and forecast delivery schedules are issued with web release functions in Transactions ME9E, a short dump is generated, if print-dependent data is updated.
Additional key words
ME9E, short dump, MOVE_TO_LIT_NOTALLOWED_NODATA, ME_PRINT_PO, print-dependent data
Cause and prerequisites
For function module ME_PRINT_PO, the transfer of parameter DOC is carried out as a reference. As a result, you cannot change internal tables which are transferred with this parameter.
Solution
Set indicator 'Call by value' for parameter DOC of function module ME_PRINT_PO. As a result, the parameter is copied and can be changed.
Source code corrections
Hope thisll give you idea!!
<b>P.S award the points.</b>
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise" -
ABAP Dump - Graphical Layout Editor
Hi...I get an ABAP Dump when I try to start the Graphical Layout Editor (to modify a screen layout). Here are a few lines from the dump:
<b>&INCLUDE INCL_INSTALLATION_ERROR
What happened?
The current program had to be terminated because of an error when installing the R/3 System. The program had already requested 789763632 bytes from the operating system with 'malloc' when the operating system reported after a further memory request that there was no more memory space available.
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.
Set the system profile parameters
- abap/heap_area_dia
- abap/heap_area_nondia to a maximum of 789763632. Then reduce the value by 10.000.000 to be on the safe side.
Then restart the SAP System.
</b>
<u>Here's what I know so far:</u>
<i>- I can logon to SAP but can NOT start Graphical Layout Editor from my machine using my user account.
- Other people can logon to SAP but can NOT start Graphical Layout Editor from my machine using their user accounts.
- I can logon to SAP and start Graphical Layout Editor from a DIFFERENT machine using my own user account.
- Other people can logon to SAP and start Graphical Layout Editor from a DIFFERENT machine using their own account.</i>
I have access to more than one SAP systems (different SAP instances) and I have tested the following:
<i>- I can logon to a different SAP system/server (from this same machine) and start the Graphical Layout Editor without error.
- Other people can logon to a different SAP system/server (from this same machine) and start the Graphical Layout Editor without error.</i>
The problem is not likely with low memory on my machine because I have 2 GB RAM whereas these other computers I've tested only have 512 MB or 1 GB memory. I don't see how the problem could be with the SAP server when other people are able to start the Graphical Layout Editor from their machines and even I can start it from their machines. The problem can't be with the SAPGUI files on my machine because I can start the Graphical Layout Editor using a different SAP system/server. I am completely stumped. Any ideas??I have already done the following:
- Uninstall SAP GUI using the "Add Remove Programs" & reinstall it
- Uninstall SAP GUI using the option provided by SAPGUI setup & reinstall it
- Uninstall SAP GUI using the option provided by SAPGUI setup & rename the folder "C:\Program Files\SAP" then install it again.
- Upgrade from SAPGUI v6.40 to v7.10. I'm now using v7.10
Don't forget that I <b><u>am</u></b> able to start the Graphical Layout Editor for a different SAP server using this same SAPGUI from this same computer. I don't think the problem is with SAPGUI but I appreciate your response. -
Dear All Gurrus
i am facing an Abap Dump when user send cheque Printing .other document printing are Ok .please see this error
Runtime errors LOAD_PROGRAM_NOT_FOUND
Occurred on 04.06.2007 at 16:18:50
Program " " not found.
What happened?
There are several possible reasons for the error:
or
The current ABAP program had to be terminated because the
ABAP processor detected an internal system error.
The current ABAP program "SAPLF028" had to be terminated because the ABAP
processor discovered an invalid system state.
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
On account of a branch in the program
(CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
or a transaction call, another ABAP/4 program
is to be loaded, namely " ".
However, program " " does not exist in the library.
Possible reasons:
a) Wrong program name specified in an external PERFORM or
SUBMIT or, when defining a new transaction, a new
dialog module or a new function module.
b) Transport error
b) Transport error
How to correct the error
Check the last transports to the R/3 System.
Are changes currently being made to the program "SAPLF028"?
Has the correct program been entered in table TSTC for Transaction "FBZ4 "?
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:
"LOAD_PROGRAM_NOT_FOUND" C
"SAPLF028" or "LF028U06"
"PAYMENT_FORM_PRINT"
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....... "PKSAPT10"
Network address.......... "184.208.96.235"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "PKSAPT10"
Database type............ "MSSQL"
Database name............ "T10"
Database owner........... "t10"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Oct 29 2006 23:44:46"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "155"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 210
User................ "AGHAZNAVI"
Language key........ "E"
Transaction......... "FBZ4 "
Program............. "SAPLF028"
Screen.............. "SAPMF05A 0700"
Screen line......... 43
Information on where terminated
The termination occurred in the ABAP program "SAPLF028" in
"PAYMENT_FORM_PRINT".
The main program was "SAPMF05A ".
The termination occurred in line 332 of the source code of the (Include)
program "LF028U06"
of the source code of program "LF028U06" (when calling the editor 3320).
Source code extract
003020 IF sy-subrc NE 0 "bei nicht in PAYR vorhandenen o.
003030 AND payr-vblnr EQ reguh-vblnr. "durch FCH7 (Scheck neu drucken)
003040 opayf-pstap = 0. "in Auftrag gegebene Schecks wird
003050 ELSE. "der Stapel mitgegeben, sonst die
003060 CLEAR payr. "Restart-Schecknummer aus PAYR
003070 ENDIF.
003080
003090 IF t042z-formi IS INITIAL. "alte Zahlungsträger (nur Scheck)
003100 SUBMIT (t042z-progn) WITH zw_laufd = reguh-laufd
003110 WITH zw_laufi = reguh-laufi
003120 WITH zw_zbukr = reguh-zbukr
003130 WITH zw_xvorl = space
003140 WITH sel_zawe = i_opayf-rzawe
003150 WITH par_zdru = 'X'
003160 WITH par_priz = i_opayf-ppriz
003170 WITH par_zfor = i_opayf-pzfor
003180 WITH par_avis = i_opayf-pavis
003190 WITH par_pria = i_opayf-ppria
003200 WITH par_stap = i_opayf-pstap
003210 WITH par_rchk = payr-chect
003220 WITH par_begl = space
003230 WITH sel_hbki = reguh-hbkid
003240 WITH sel_hkti = reguh-hktid
003250 WITH par_anzp = par_anzp
003260 WITH par_fill = i_opayf-pfill
003270 WITH par_espr = i_opayf-pespr
003280 WITH par_isoc = i_opayf-pisoc
003290 WITH par_sofo = i_opayf-psofo
003300 WITH par_novo = i_opayf-xnovo
003310 AND RETURN.
ELSE. "neue Zahlungsträger (z.Zt. nur OFX)
003330 CALL FUNCTION 'PAYMENT_MEDIUM_ONLINE'
003340 EXPORTING
003350 im_formi = t042z-formi
003360 im_reguh = reguh
003370 im_opayf = i_opayf
003380 TABLES
003390 tb_regup = xregup.
003400 ENDIF.
003410
003420 ENDFUNCTION.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 4 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 UAN
SY-UCOMM BU
SY-TITLE Payment with Printout: Display Overview
SY-MSGTY I SY-MSGID F5
SY-MSGNO 312 SY-MSGV1 1500000011
SY-MSGV2 KOPK SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
4 FUNCTION PAYMENT_FORM_PRINT
SAPLF028
LF028U06 332
3 FORM FCODE_BEARBEITUNG
SAPMF05A
MF05AFF0_FCODE_BEARBEITUNG 2333
2 FORM FUSSZEILE_VERARBEITEN
SAPMF05A
MF05AFF0_FUSSZEILE_VERARBEITEN 148
1 MODULE (PAI) FUSSZEILE_BEARBEITEN
SAPMF05A
MF05AI00_FUSSZEILE_BEARBEITEN 46
Chosen variables
4 FUNCTION PAYMENT_FORM_PRINT
SAPLF028
LF028U06 332
I_CC_CURR PKR
54522
0B200
I_OPAYF KOPKLOCL 0002 XCCIT
4454444422222222222222222222233332254445
BF0BCF3C00000000000000000000000020083394
... + 40 IH X 0001000005
4422522222222222333333333322222222222222
9800800000000000000100000500000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 00000000000000
2222222222222222222222233333333333333
0000000000000000000000000000000000000
I_REPRI
2
0
I_VBLNR 1500000011
3333333333
1500000011
I_WWERT 20070604
33333333
20070604
REGUH-LAUFI 00001*
333332
00001A
<%_TABLE_LFA1> ???
REGUH-ZBUKR KOPK
4454
BF0B
I_OPAYF-RZAWE C
4
3
I_OPAYF-PPRIZ LOCL
4444
CF3C
I_OPAYF-PZFOR
2222222222222222
0000000000000000
I_OPAYF-PAVIS
2
0
I_OPAYF-PPRIA
2222
0000
I_OPAYF-PSTAP 0002
3333
0002
PAYR-CHECT
2222222222222
0000000000000
REGUH-HBKID CITIH
44544
39498
REGUH-HKTID CTOLH
45444
34FC8
PAR_ANZP 0
3
0
I_OPAYF-PFILL
2
0
I_OPAYF-PESPR
2
0
I_OPAYF-PISOC
2
0
I_OPAYF-PSOFO X
5
8
I_OPAYF-XNOVO
2
0
%_PRINT 000
2222333222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 0 ########
2222222222320000000022222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160 0 ####
222222222222223222222222222222220000
000000000000000000000000000000000000
KNBK-KOINH
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
22222222222222222222
00000000000000000000
T042Z-FORMI
222222222222222222222222222222
000000000000000000000000000000
<%_TABLE_T012> ???
REGUH 2007060400001* KOPK0001000005
2223333333333333224454333333333322222222
0002007060400001A0BF0B000100000500000000
... + 40 1500000011 PKR LHP1Co
2222222222222222223333333333254522445346
000000000000000000150000001100B200C8013F
... + 80 mpany Supreme Gas Ind. Pvt. Ltd
6766722222222577766624672466225772247622
D01E90000000035025D5071309E4E0064E0C4400
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 Lahore
222466676222222
000C18F25000000
SYST-REPID SAPLF028
5454433322222222222222222222222222222222
310C602800000000000000000000000000000000
T042I-HBKID CITIH
44544
39498
XREGUP[] Table IT_1065[1x1184]
3 FORM FCODE_BEARBEITUNG
SAPMF05A
MF05AFF0_FCODE_BEARBEITUNG 2333
%_SPACE
2
0
RC 0
0000
0000
SYST-REPID SAPMF05A
5454433422222222222222222222222222222222
310D605100000000000000000000000000000000
SY-REPID SAPMF05A
5454433422222222222222222222222222222222
310D605100000000000000000000000000000000
VORSCHL_GRIRG
222
000
XBKPF-BELNR 1500000011
3333333333
1500000011
%_DUMMY$$
2222
0000
VAKTAB
222222222222222222222222222222
000000000000000000000000000000
XBKPF-BUKRS KOPK
4454
BF0B
VORSCHL_GITYP
22
00
XBKPF-GJAHR 2007
3333
2007
C_INFO_LINK 100
333
100
BKPF 210KOPK15000000112007KZ20070604200706040
3334454333333333333334533333333333333333
210BF0B15000000112007BA20070604200706040
... + 40 620070604161846000000000000000020070604A
3333333333333333333333333333333333333334
6200706041618460000000000000000200706041
... + 80 GHAZNAVI FBZ4
4445445422244532222222222222222222222222
781AE16900062A40000000000000000000000000
... + 120 12345
2222222333332222222222222222222222222222
0000000123450000000000000000000000000000
... + 160 0000 PKR ###
2223333222222222222222222222222254522000
000000000000000000000000000000000B200000
... + 200 ## ##### ####### RFBU
0022222000002200000002544522222222222222
0C000000000C00000000C0262500000000000000
... + 240
222222222222222
000000000000000
BSEG 210KOPK15000000112007002 000000000000000
3334454333333333333333332333333333333333
210BF0B150000001120070020000000000000000
... + 40 0 25K SLHP1 ##########
3222222222233422254453222222220001000000
0000000000025B0003C80100000000000000C000
... + 80 ##################PKR #################
1000000000000010005452200000000000000000
000C000000C000000C0B200000000C000000C000
... + 120 #######################################
0000000000000000000000000000000000000002
000C000000C000000C000000C000000C000000C0
... + 160 000 ###############################
2223332220000000000000000000000000000000
000000000000000C0000C000000C000000C00000
... + 200 ##0000000020070427
0033333333333333332222222222222222222222
0C00000000200704270000000000000000000000
... + 240
222222222222222
000000000000000
SY-SUBRC 4
0000
4000
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
SAPOS-GITYP
22
00
T001-WAERS PKR
54522
0B200
SAPOS-GRICD
22
00
OPAYF KOPKLOCL 0002 XCCIT
4454444422222222222222222222233332254445
BF0BCF3C00000000000000000000000020083394
... + 40 IH X 0001000005
4422522222222222333333333322222222222222
9800800000000000000100000500000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 00000000000000
2222222222222222222222233333333333333
0000000000000000000000000000000000000
SAPOS-GRIRG
222
000
RF05A-KOATX
222222222222
000000000000
BKPF-WWERT 20070604
33333333
20070604
SY-XFORM CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
SY-MSGID F5
43222222222222222222
65000000000000000000
ANL_HKONT
2222222222
0000000000
T001W
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 #
222222222222220
000000000000000
SPACE
2
0
SY-MSGNO 312
333Specification of form is missing in pmnt method C for comp.code KOPK
In the include program RFFORI01 the query "SELECT * FROM t042z WHERE land1 EQ t001-land1 AND zlsch IN sel_zawe AND progn EQ sy-repid" is returning a null value for progn. This null value is passed to "003100 SUBMIT (t042z-progn) WITH zw_laufd = reguh-laufd" (Refer to the short dump).
Refer to IMG for adding specification of form.
Regards,
Khalid Mustafa
Development Consultant Netweaver-ABAP
Maybe you are looking for
-
Does anybody have a problem with ios7
I have a ipad 2 , now with ios7 . My problems started when I updated first the wallpaper size that was solved sort of . Now may ipad is slower to respond and my apps keep crashing also at times i cant even get my e-mail ! I am tempted to go back
-
Error using Richfaces Drag and Drop support in JSF 1.1 application
Iam using rich faces drag n drop support in my JSF application . The jsp works as expected but I get this weird exception while navigating through my pages. Scenario : User logs into the application , from the home page ---> when the user click on a
-
I just bought mac last night.... Trying to import movies from my sony handycam to my mac, and for the past 20 hours it has said, "Optimizing Video" with no progress bar moving.... What is wrong? Does the video camera need to be converted first? If so
-
CMR - how to deal with no child records
Hi, I have developed a number of CMP EJBs, created relationships, mapped and deployed OK using WSAD v5 + DB2 backend. When I call findByPrimaryKey on the parent in the one to many, everything works unless there are no child records. The server genera
-
AD Group Provisioining to User
Hi All, I am working on AD automatic provisioning using GTC flat file.I have done prepopulation of necessary attributes like Resource Name,Organization Unit etc.In the next form I need to supply AD Group Values. In the forums/blogs I found some infor