Runtime Error - In PO creation

Hi friends,
Pls advise how to resolve this runtime error issue mentioned below...which Im getting in PO creation and at the time of releasing the same but getting the error as background express document.
Note(FYI):No enhancement has been developed and its a normal process only.
************Runtime error
Report outputRuntime Errors POSTING_ILLEGAL_STATEMENT
Statement "CALL SCREEN" is not allowed in this form.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLKKBL" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
There is probably an error in the program
"SAPLKKBL".
This program is triggered in the update task. There, the
following ABAP/4 statements are not allowed:
CALL SCREEN
CALL DIALOG
CALL TRANSACTION
SUBMIT
How to correct the error
Probably the only way to eliminate the error is to correct the program
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:
"POSTING_ILLEGAL_STATEMENT" " "
"SAPLKKBL" or "LKKBLU01"
"K_KKB_LIST_DISPLAY"
Information on where terminated
Termination occurred in the ABAP program "SAPLKKBL" - in "K_KKB_LIST_DISPLAY".
The main program was "RSM13000 ".
In the source code you have the termination point in line 441
of the (Include) program "LKKBLU01".
The program "SAPLKKBL" was started in the update system.
438 if gt_stack-is_layout-detail_only is initial.
439 if gt_stack-is_layout-suppress_dynpro is initial.
440 if i_screen_start_line eq 0.
call screen 500.
442 sy-pagno = g_sypagno. "wegen Dynpro 200 Spoolinfo bei F8+Druck
443 else.
Pls reply.
thanks & regards
sankar.
Edited by: sankar babu on May 23, 2008 12:05 PM
Edited by: sankar babu on May 23, 2008 12:05 PM

Hi
Check with Abapers, it transaction is calling some screen 500, which is not compatible with the Form output.
Regards
Rahul

Similar Messages

Runtime errors during RFQ creation

Hello experts,
I am trying to create a RFQ for my client. I have provided all necessary information needs to create a RFQ but when I try to execute, I get Runtime error "DYNPRO_NOT_FOUND"
Can anyone tell me how can I solve this problem. I belive this error related to ABAP program.
Regards,
Atul Kumbhani

Raf,
Termination occurred in the ABAP program "SAPLXM06" - in "EXIT_SAPLEINM_013".
The main program was "SAPMM06E ".
In the source code you have the termination point in line 10
of the (Include) program "MM06EO0C_CUSTSCR1_HEAD_SET_DAT".
Regards,
Atul Kumbhani

Runtime Error during Asset Creation (AS01)

Hello Everyone !
I have been trying to CREATE ASSET for a long time but unfortunatly land up on ..... RUNTIME ERROR. I used all the possible ways to get it solved but i am stuck. Error analysis says The ASSERT Condition was violated.
Hope you guys would help me out and push my knowledge further. Answers would be highly appreciated.
Srinivas

Hi Srinivas
Please go through T-cd:ST22 and check the dump content first, especially, u2018Error analysisu2019, u2018How to correct the erroru2019 of the runtime error long text may give you some hints to solve the problem.
Regards
George

Runtime error while saving the billing document after creation

hi friends ,
while saving the billing document after creation , the fallowing discriptive runtime error has come.
Run time errors -
SAPSQL_INVALID_TABLENAME
Except. -
CX_SY_DYNAMIC_OSQL_SEMANTICS

Dear Unnam,
There may be several reasons...
1. If u have enhanced the tcode with some z tables,and that might not be moved properly to prod or not active in data dictonary.
2. u may not be entering proper data to the input fields.
3. please check if u have added any z tables to the std tcode.I am exepcting this prob.u may not moved the table or enhancement properly to prod server,
Please check it...
Thanks N Regards
SettyKY

PR Creation in CN22 - Runtime Error u201CSAPSQL_ARRAY_INSERT_DUPRECu201D

We, are on ECC6.0 since December 2007.
We have implemented all core modules including PS.
In our business, purchase requisitions get generated in 3 ways.
1) Manual generation of PR using Transaction Code ME51n
2) Network PR using transaction code CN22
3) MRP PR.
Last month we have activated version management functionality for purchase requisition. After version management activation, we have noticed a very peculiar problem which is explained below.
Problem Description:
Step 1 - Certain number of materials (say u2018nu2019) are attached to a particular network (using t_code CN22) & system has generated a PR with u2018nu2019 number of line items. This activity is done before activation version management.
Step 2 u2013 After activating version management, if a new material is attached to the same network, ideally system should add a line item in the existing PR. But, in our case, system is generating a Runtime Errors u201CSAPSQL_ARRAY_INSERT_DUPRECu201D. (Document is attached for your study)
Our Analysis:
1) When we try to attach a new material to network (say item No. 30), entry of item no. 30 for this particular PR already exists in table u2018EREVu2019 even when the material attachment is not saved.
2) To avoid this error we have applied SAP Note No. 0001370641, 1382900, 1381754, 1388921.1309689, but still the error is appearing in CN22 while adding material code for PR creation in already created networks.
Requesting you to suggest a solution.

Hi,
If you are using some badi or exit, check the process by de activating the same.
If same results are coming, then check OSS notes applicability in your case. (e.g. 148828, 193580 etc)
Other wise take help from OSS message, since this problem mainly occures due to program error.
Regards,
Manoj

Runtime Error during Creation of Asset (AS01)

Hello Everyone !
I have been trying to CREATE ASSET for a long time but unfortunatly land up on ..... RUNTIME ERROR. I used all the possible ways to get it solved but i am stuck. Error analysis says The ASSERT Condition was violated.
Hope you guys would help me out and push my knowledge further. Answers would be highly appreciated.
Srinivas.

Hi Srinivas,
I found more information about your issue. These are notes that have been given by SAP in regards to the "ASSERTION_FAILED" runtime error in AS01 or also AS91.
931764    Runtime error ASSERTION_FAILED
989402    Expand/Collapse All events in planning hang t
951191    AA 908, AA 698, AA 475, incorrect ANLC values
932560    ITAB_DUPLICATE_KEY runtime error
971300    AA610 for fixed asset creation, change or recalculation
988238 FAQ New depreciation calculation
949802 AS91: Dump ASSERTION_FAILED in CF_FAA_CFG_TRANSACTION
Please be aware of note 988238 which is a composite note with many erros in FI-AA when in ECC 6.0 It advices to:
"Implement the following notes or import at least Support Package 6 for the components EA-APPL and SAP_APPL (available as of October 2006)."
Check also note 949802.
I hope this helps.
Best Regards,
Vanessa.

Runtime Error while creation of rule for IU elimination

Hi,
Following runtime error occuring while creating a rule under IU elimination method.
Error analysis
A RAISE statement in the program "CL_UC_SINGLESELCOND_FACTORY===CP" raised the
     exception
condition "NOT_FOUND".
Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
   For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
Trigger Location of Runtime Error
    Program                                 CL_UC_SINGLESELCOND_FACTORY===CP
    Include                                 CL_UC_SINGLESELCOND_FACTORY===CM001
    Row                                     33
    Module type                             (METHOD)
    Module Name                             IF_UC_CUST_FACTORY~GET_INSTANCE_BY_GUID
Please advice...
Edited by: VNK on Nov 25, 2008 11:18 AM

Hi,
please check SAP note 859500:
- implement all relevant notes
- send a message to SAP support for checking and solving the GUID inconsistencies.
best regards
Thomas

Runtime Error in CRM_EVENT_PUBLISH_OW while Sales Order Creation

Hi,
I am getting run time error when I try to copy the sales order from Existing one and Save it. ( in WEB UI)
I am getting this error in the Function Module : CRM_EVENT_PUBLISH_OW
Code Extract :
IF ( iv_obj_name IS INITIAL ) OR
    ( iv_guid_hi IS INITIAL ) OR
    ( iv_kind_hi IS INITIAL ) OR
    ( iv_event IS INITIAL ).
-- Fehlerhafte oder unvollständige Parameterübergabe bei Aufruf &1 ---*
   MESSAGE x028(crm_ssc) WITH 'FU CRM_EVENT_PUBLISH_OW'.
ENDIF.
Please help me, how can I solve this runtime error.
Thanks,
Sandeep

Hi,
    The Event Publish itself might not be responsible for the error. Whenever you make a change in the order, the change is "published" in order to check if the change is acceptable to other objects of the order. You will have to analyze what might be possibly affected when you made the change or have to do a lot of debugging....
Regards,
Arun Prakash

Runtime error in sales order creation

Hai,When I am trying to create sales order one run time error is occured.The error is CALL_TRANSACTION_NOT_FOUND TRANSACTION "%_GS" IS UNKNOWN.TRANSACTION "%_GS" IS NOT LISTED IN TABLE OF T.CODES.CURRENT ABAP PROGRAMME HAD TO BE TERMINATED BECAUSE ONE OF THE STATEMENT COULD NOT BE EXICUTED.THE CURRENT ABAP/4 SAPMV80Z PROGRAMME USES CALL TRANSCTION TO CALL THE TRANSACTION"%_GS".TABLE TSTC CONTAINS NO ENTRY FOR"%_GS".THIS COULD BE DUE TO PROGRAMME ERROR.

Hi,
Did you call the correct transaction?
Non-Catchable Exceptions
Cause: Transaction is unknown
Runtime Error: CALL_TRANSACTION_NOT_FOUND
More info
http://www.s001.org/ABAP-Hlp/abapcall_transaction.htm
Cheers
Wiparat

Runtime error in Field catalog creation

when i try to create the field catalog using the following code.
am getting *'Field Symbol Is not assigned' Runtime error.*
Please give me idea how to resolve this issue.
data: wa_field type slis_fieldcat_alv,
        t_field type slis_t_fieldcat_alv.
LOOP AT t_role INTO wa_role.
    wa_field-col_pos = count1.
    wa_field-fieldname = wa_role-agr_name.
    wa_field-datatype = 'CHAR'.
    wa_field-ref_fieldname = 'AGR_NAME'.
    wa_field-ref_tabname = 'AGR_1251'.
    APPEND wa_field TO t_field.
    count1 = count1 + 1.
ENDLOOP.
Suitable Answers rewarded with maximum points....
it's Urgent...
Give me Quick Reply.

Error is having following short text.
Field symbol has not yet been assigned.
Error analysis
    You attempted to access an unassigned field symbol
    (data segment 92).
This error may occur for any of the following reasons:
    - You address a typed field symbol before it is set using ASSIGN
    - You address a field symbol that points to a line in an internal table
      that has been deleted
    - You address a field symbol that had previously been reset using
      UNASSIGN, or that pointed to a local field that no longer exists
    - You address a global function interface parameter, even
      though the relevant function module is not active,
      that is it is not in the list of active calls. You can get the list
      of active calls from the this short dump.
Please tell me how to correct this error.
It is very Urgent..

Runtime Error - POSTING_ILLEGAL_STATEMENT

Hi friends,
Pls advise how to resolve this runtime error issue mentioned below...which Im getting in PO creation and at the time of releasing the same but getting the error as background express document.
Note(FYI):No enhancement has been developed and its a normal process only.
************Runtime error
Report outputRuntime Errors         POSTING_ILLEGAL_STATEMENT
Statement "CALL SCREEN" is not allowed in this form.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLKKBL" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
There is probably an error in the program
"SAPLKKBL".
This program is triggered in the update task. There, the
following ABAP/4 statements are not allowed:
- CALL SCREEN
- CALL DIALOG
- CALL TRANSACTION
- SUBMIT
How to correct the error
Probably the only way to eliminate the error is to correct the program
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:
"POSTING_ILLEGAL_STATEMENT" " "
"SAPLKKBL" or "LKKBLU01"
"K_KKB_LIST_DISPLAY"
Information on where terminated
Termination occurred in the ABAP program "SAPLKKBL" - in "K_KKB_LIST_DISPLAY".
The main program was "RSM13000 ".
In the source code you have the termination point in line 441
of the (Include) program "LKKBLU01".
The program "SAPLKKBL" was started in the update system.
438 if gt_stack-is_layout-detail_only is initial.
439    if gt_stack-is_layout-suppress_dynpro is initial.
440      if i_screen_start_line eq 0.
>>>>>        call screen 500.
442        sy-pagno = g_sypagno. "wegen Dynpro 200 Spoolinfo bei F8+Druck
443      else.
Pls reply.
thanks & regards
sankar.
Edited by: sankar babu on May 23, 2008 12:04 PM

Hi All,
The error is related to the ABAP coding of the particular program. The program related to sales and billing.
The error you get must be the user own output screen.
Please refer to the SAP Note for further analysis and solution.
http://service.sap.com/sap/support/notes/1472777

I loaded actions into my PSE 10, then when I restarted my PC (windows 7) and PSE 10 I got a Runtime Error (Microsoft Visual C Runtime Library)

I loaded actions into my PSE 10, then when I restarted my PC (windows 7) and PSE 10 I got a Runtime Error (Microsoft Visual C Runtime Library)

Are these actions you put into the C:\ProgramData\Adobe\Photoshop Elements\10.0\Photo Creations\photo effects folder?
If so, did you delete both the
ThumbDatabase.db3 in C:\ProgramData\Adobe\Photoshop Elements\10.0
and
MediaDatabase.db3 in C:\ProgramData\Adobe\Photoshop Elements\10.0\Locale\en_us
after installing the actions?
Then let the pse 10 editor run for about 10 to 20 minutes to rebuild the effects database.

Getting a runtime error DATA_INCONS_IN_EXIT_MANAGEM

Hi All,
I am getting a runtime error "Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" raised. when I tried to implement a BADI given in the tutorial.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d0456c54-0901-0010-f0b3-cd765fb99702
When I debuged and found that there is no entry i.e Inetrface was not found in table in table "SXS_INTER"
I have created the BADI using the Enhancement spot not the Classic BADI creation.
Kindly provide a good solution
Regards
Paul

Hi Paul Paul,
i am also getting same error when implementing BADI, if you get any solution from somewhere, kindly forward it to me.
thanks
Shahid Rais

Runtime Error while creating FINANCIAL STATEMENT VERSION

Hi Experts,
The major concern of the problem is related with the new creation of FINANCIAL STATEMENT VERSION.
(SPRO --> IMG --> Financial Accounting --> General Ledger Accounting --> Business Transactinons --> Closing > Document> Define Financial Statement Versions.)
My quries is that is it possiable to maintain more then one FSV for the same company code or for same chart of account.
If yes then we are trying to do it . But the problem reflect, be the indication that we can`t maintain more then one code.
Its giving an runtime error
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
Date and Time          15.03.2008 18:36:04
Short text
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLFAGL_FSV" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
      in
procedure "FSV_TEXTS_CONVERT" "(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:
     If you use an ABAP/4 Open SQL array insert to insert a record in
     the database and that record already exists with the same key,
     this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
     situation, processing does not terminate, but SY-SUBRC is set to 4.)
We are trying Its giving an abap dump
Rest the technicall aspect that is comming in ABAP Dump i am not
getting.....so pls inquire according to yourself.
Kind Regards,
Sudhanshu

Hello
Logically speaking, a company code can have more than one FSV as long as they share the same chart of accounts.
When COA is common, the FSV pattern can be designed seperatly to serve the purpose of varied reporting.
The dump you are getting is a temporary snag. Take a screen shot from SM54 after you execute the report and pass it to BASIS for analysis. They would fix that.
Reg
assign points if useful

Runtime Errors in Portal

Hi,
When I click on the menu in Portal (assume it as material creation), it display a screen with some runtime errors.
- Unable to start the application. Contact help desk # xxxxxxxxxxxxx .
My question is from where do we get these runtime errors. Where could we see the list of runtime error in portal.
Thanks.

Hi,
This is related to iviews and backend system configuration.
Please check the configuration related to the iviews.
If it does not solve your problem, please explain more briefly
Regards,
Bala.

Runtime Error - In PO creation

Similar Messages

Maybe you are looking for