Runtime error in extractor enhancement

Hi,
I need to enhance the extractor 0WBS_ELEMT_ATTR with an additional field. The field is a Z field from the table PRPS.
Now PRPS is a base table for the extractor for this extractor, so simply adding this field into the append structure should suffice.
However, when I do this the extractor gives the following runtime error:
Syntax error in program "SAPLPSBW "
Component called ZZSO already exists.
The error is in the function call "e_fname".
I have found that the same Z field is used in another structure CNCI_PRPS. Could this be leading to the error?
Please let me know if any of you have any insights as to why this problem might be occurring.
TIA,
Amrita

Hi,
In my case the problem was caused because the same ZZ Field was used in two structures.
One for ECC and one for BI. This was causing some interference.
To solve this I changed the field name in my extract structure to ZZZSO and populated it via a CMOD routine.
Hope this helps.
Amrita

Similar Messages

CREATE_OBJECT_CLASS_NOT_FOUND runtime error during extractor checking

Hi Gurus,
I had to modify a generic data source based on a database view. I had to add a field for extraction. Since this field was available in the tables on which the view was built but not used in the view, I modified the view to to include the field. Then, I modified the extract structure to include the newly added field.
Now, when I try to check the extractor in RSA3 (extract checker), I end up getting a runtime error with details as below.
Runtime Errors                    CREATE_OBJECT_CLASS_NOT_FOUND
Except.                    CX_SY_CREATE_OBJECT_ERROR
Date and Time                    3/6/2012     5:46:07
     Short text
          CREATE OBJECT: The class "\CLASS=ZCL_IM_CLC" was not found.
     What happened?
          Error in the ABAP Application Program
          The current ABAP program "CL_EXIT_MASTER================CP" 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_CREATE_OBJECT_ERROR', was not
           caught in
          procedure "INSTANTIATE_IMP_CLASS" "(METHOD)", nor was it propagated by a
           RAISING clause.
          Since the caller of the procedure could not have anticipated that the
          exception would occur, the current program is terminated.
          The reason for the exception is:
          The dynamically specified class "\CLASS=ZCL_IM_CLC" at CREATE OBJECT neither
           exists as
          local, nor as global class in the system, or is overshadowed by a local
          data type of the same name.
     Missing RAISING Clause in Interface
          Program                    CL_EXIT_MASTER================CP
          Include                    CL_EXIT_MASTER================CM002
          Row                    1
          Module type                    (METHOD)
          Module Name                    INSTANTIATE_IMP_CLASS
     Trigger Location of Exception
          Program                    CL_EXIT_MASTER================CP
          Include                    CL_EXIT_MASTER================CM002
          Row                    15
          Module type                    (METHOD)
          Module Name                    INSTANTIATE_IMP_CLASS
     Source Code Extract
     Line          SourceCde
     1          METHOD instantiate_imp_class .
     2
     3            DATA: abs_type_classname TYPE string,
     4                  imp_obj            TYPE imp_obj_type.
     5
     6          *   Look for objects that have been created for this class
     7            READ TABLE imp_obj_tab INTO imp_obj
     8                WITH TABLE KEY imp_name    = imp_name
     9                               calling_obj = caller.
     10            IF sy-subrc = 0.
     11              instance = imp_obj-obj.
     12            ELSE.
     13              CONCATENATE '\CLASS=' imp_class INTO abs_type_classname.
     14          ***** dynamic object creation     *******************************
     >>>>>              CREATE OBJECT instance TYPE (abs_type_classname).
     16          ******************************************************************
     17              imp_obj-imp_name    = imp_name.
     18              imp_obj-calling_obj = caller.
     19              imp_obj-obj         = instance.
     20              INSERT imp_obj INTO TABLE imp_obj_tab.
     21            ENDIF.
     22          ENDMETHOD.
Can anybody please help me solve this issue?

Hi Ajay,
Please check the following threads for your issue::
System Exception
Exception              CX_SY_CREATE_OBJECT_ERROR
Why is CREATE_OBJECT_CLASS_NOT_FOUND ?
Dump CREATE_OBJECT_CLASS_NOT_FOUND with BADI in MM_MATBEL archiving object
Regards,
Arpit

Runtime error in enhancement spot-' mereq_topline does not exists.'

Hi all,
I have implemented an implicit enhancement spot in ME53n.
When i applied break point in enhancement spot and control goes to ebhancement spot in debugging mode, i got purchse requisition number in mereq_topline.
When i tried to use this structure value in code i get runtime error-
' mereq_topline does not exists.'
Can you please guide how to resolve this runtime error.
thanks.
Edited by: Sanjay_lnt on Sep 20, 2010 8:52 AM

Sanjay,
try to delete the enhancement and recreate it
Thanks
Bala Duvvuri

LBWR gets runtime error display backup data

We are getting a runtime error "IMPORT_WRONG_END_POS" in program RMBWV3RE when we try to "dispay the data in the backup table" for logistics extractor 2LIS_46_SCL.
We have enhanced the extract structure several times since we did our initial LBWR customizing. Could it be that there is backup data still in the LBWR queue that is in the old format? Can we delete the backup queue?
Regards,
Mike Wagner

Francisco,
I check and those notes have already been applied to our system.
I did find a blog "A Safety Belt for Logistics Extraction Queues" by Bernd Sieger which is dedicated to LBWR.
/people/bernd.sieger/blog/2007/05/07/a-safety-belt-for-logistics-extraction-queues
Bernd gave me a couple of hints on how to fix the problem. I ended up writing an ABAP program to delete the contents of the queue for my logistics extractor 2LIS_46_SCL.
After clearing old records, the data display work fine now.
Regards,
Mike Wagner

WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR " Screen: Illegal message"

Hi Experts,
While deleting a sales order giving run time error. PFB runtime error details.
If you know any OSS message, please let m know. I tried, but there is no luck.
Short text
    Screen: Illegal message
What happened?
    The current screen processing action was terminated since a situation
    occurred where the application could not continue.
    This is probably due to an error in the ABAP program or in the current
    screen.
What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator.
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
Error analysis
    The program attempted to issue a " " message during "Exit Command" processing.
    This is an illegal operation.
    The program was terminated.
    Screen name.............. "SAPMV45A"
    Screen number............ 4001
How to correct the error
    The program must be modified to correct the error.
    The modification must be made in "Exit Command" processing.
    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)".
Source Code Extract
Line SourceCde
    1 *---------------------------------------------------------------------*
    2 *       FORM YVBEP_LESEN                                              *
    3 *---------------------------------------------------------------------*
    4 *       Lesen der Tabelle YVBEP (nicht sortiert)                      *
    5 *---------------------------------------------------------------------*
    6 FORM YVBEP_LESEN USING US_POSNR
    7                        US_ETENR
    8               CHANGING CH_TABIX.
    9
   10   YVBEP = SPACE.
   11   YVBEP-MANDT = VBAK-MANDT.
   12   YVBEP-VBELN = VBAK-VBELN.
   13   YVBEP-POSNR = US_POSNR.
   14   YVBEP-ETENR = US_ETENR.
   15   READ TABLE YVBEP.
   16   IF SY-SUBRC > 0.
   17     MESSAGE E506 WITH US_POSNR US_ETENR.
   18   ENDIF.
>>>>>   CH_TABIX = SY-TABIX.
   20
   21 ENDFORM.
Could you please help on this issue.
Thanks
Srinu

Hi Srinu,
it looks like you got the error message Schedule line &1 &2 is missing in table YVBEP while deleting the sales order.
It seems, that there are no SAP notes regarding this issue. Do you have this issue with all orders or with a single order?
If only a single order causes this issue, maybe something was wrong during an update.
If you get this error for many orders, then custom code (modification, enhancement, user exit in MV45AFZZ, ...) may be the reason for it.
If you have no custom code in module pool SAPMV45A, then contact SAP for this issue.
Regards,
Klaus

Runtime error in MIRO while using User/Screen exit

Hello,
I have implemented an exit in ABAP for MIRO which when transported to Quality server through runtime error.
I have used EXIT (SMOD) : LFDCB001 which contains FM -> EXIT_SAPLFDCB_001 and include -> ZXM08U31. In this exit I have written my code to disable Inv. Party field. This field exist in Details Tab in Miro Transaction.
Location of the field: MIRO -> Details (tab) -> Inv. Party (Field)
Code written in include ZXM08U31 is:
LOOP AT SCREEN.
IF screen-name = 'INVFO-LIFRE'.
    screen-input = 0.
    MODIFY SCREEN.
ENDIF.
ENDLOOP.
This exit is assigned to a project in CMOD and I tested the same in Development system. It is working perfectly.
Now I transported the TR (Includes program ZXM08U31 and Customer enhancement projects ZMIRO). Now when I run MIRO in quality server it triggers the my logic and then through runtime error.
Runtime error says:
Short text
    Dynpro does not exist
Error analysis
    The system attempted to use dynpro 0400 in program "SAPLXM08".
    This dynpro does not exist.
I agree that screen 400 does not exists in program for MIRO but it does not exists in development system as well. So if the runtime error is valid in QEC server then why not in DEV server. And when it can run successfully in DEV server why cant it run in QEC server.
Hope I have explained all the things in detail.
Please provide me the solution since user can bombard anytime for the MIRO dump everytime in QEC.
Regards,
Harjeet Grover

Hi Harjeet,
Reason of your Dump is that the enhancement "LFDCB001" which you used contains one Function module exit "EXIT_SAPLFDCB_001" and another one screen exit in calling screen "SAPLFDCB" number 0150.
So when you activate your project these above mentioned both components were activated.
So when you execute transaction SAP looks for called screen "SAPLXM08" No-0400 but as you havn't created and program go for DUMP.
Solution - Just Create called screen "SAPLXM08" No-0400 and activate.
Thanks,
Vijay

Runtime Error in Test Client after Transport

Hello SDNers,
I did enhancements to standard SAP component ICCMP_BP_SEARCH in developement system in client XXX of system SSS.
I wanted to test the functionality in client YYY so used SCC1 transaction to transport from client XXX to client YYY.
But when i tried to test the application, it resulted in runtime error.
I had kinda identified the problem while debugging, in the class CL_CHTMLB_CONFIG_UTILITY method CREATE_UI_ELEMENT, it is not taking my Z class references rather it still referring to starndard classes.
My Z classes are created for IMPL class, CTXT class and CN00 class.
If any one has suggestions your help would be appreciated
Thanks in advance.
Best Regards,
Srikanth

Srikanth,
Is the definition of the enhancement set defined properly for your test client. This table does not transport and you have to maintain it manually in each client. The view is BSPWDV_EHSET_ASG for SM30. Client is not the first field in the table, so you have to edit this view in each client.
Take care,
Stephen

Runtime error in CRMD_SALES_MASS transaction

Hi Gurus,
I have to enhance the transaction CRMD_SALES_MASS to add few custom fields to it.
I am trying to execute the transaction but I keep getting a runtime error in a standard Function Module CRM_SALESORDER_MASS_SELECT that is meant for the MASS Transaction. I have gone through many notes but I could not find anything which is relevant. Please help me with this! Please find the below dump if it can help.
Runtime Errors         CREATE_DATA_UNKNOWN_TYPE
Except.                CX_SY_CREATE_DATA_ERROR
Date and Time          09.12.2010 05:11:12
Short text
    CREATE DATA: The specified type "CRMT_SALESORD_MASSUPDATE_ITEM
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLCRM_SALES_MASS_UPDATE" had to be terminated
     because it has
    come across a statement that unfortunately cannot be executed.

Hi Nisha,
Thanks for the reply.
I got to know the issue with the function module before I saw the reply. It has something to do with the type that is used in CREATE DATA statement. The statement at line 51 should have been as below
CREATE DATA ls_selecttable_ref type (tabname-name).
but the type mentioned tabname in standard FM is a structure of type MASSTABLESTAB.
Now I have another question. If we are to implement MASS transaction for Service contracts in CRM how are we supposed to do it? I am talking about SAP GUI and not the WebUI here.
Regards,
Mahesh

Runtime error while activating LO Datasource in Source System

Hi Gurus,
I have followed the below steps to activate the SD related LO extractor in ECC
1. RSA5 --> Select all the 2LIS_11,12&13 data source and activate
2. LBWE --> Choose the 2LIS_11,12&13 data source and activate.
Upon execution of the second step , the system return me the following runtime error
Runtime Errors         DDIC_TYPE_INCONSISTENCY
Date and Time          07.07.2011 10:14:29
Short text
     Inconsistency in the Dictionary for the structure "MCQALSB".
What happened?
     Error in the SAP kernel.
     The current ABAP "SAPLMCEX" program had to be terminated because the
     ABAP processor detected an internal system error.
Error analysis
     There is an internal system error.
     eliminated with ABAP/4.
Trigger Location of Runtime Error
     Program                                 SAPLMCEX
     Include                                 LMCEX$04
     Row                                     26
With this error i cant proceed to activate any of the LO data source
Please help
Thanks in advance

The table MCQALSB need to be activated in SE11 and LBWE works fine

BAPI Runtime Error DBIF_RSQL_INVALID_REQUEST with module "KONV_BEARBEITEN"

Hi Experts
I am trying to create a sales order using BAPI FM BAPI_SALESORDER_CREATEFROMDAT1. After executing the program it shows in output screen that the sales order created and also displays the newly created sales order number. But when I want to check the order from VA03 it shows Express document "Update was terminated" received by author AAA, where AAA is login name.
I also analysis the sort dump for which the update process was terminated. I give the error details
Runtime Errors         DBIF_RSQL_INVALID_REQUES
Error analysis
    An invalid request was made to the SAP database interface in a statement
     in which the table "KONV " was accessed.
Below are the module name and report from where the error is coming.
Function Module name RV_SALES_DOCUMENT_ADD
Program Name SAPLV45U
Include LV45UF0K
Row 26
Source code from Rruntime Error
Line SourceCde
1 *****************************************************************
    2 * Unterroutinen RV-Auftragsabwicklung alphabetisch sortiert:
    3 * ----------------------------------------------------------
    4 * Buchstabe K:
    5 *
    6 *****************************************************************
    7
    8 *----------------------------------------------------------------
    9 *       FORM KONV_BEARBEITEN
   10 *----------------------------------------------------------------
   11 FORM KONV_BEARBEITEN.
   12
   13   CHECK: FKONV_GEAENDERT NE SPACE OR
   14          VORGANG = CHARH.
   15
   16   IF VORGANG NE 'H'.
   17     DELETE FROM KONV WHERE KNUMV = VBAK-KNUMV.
   18 ENHANCEMENT-POINT KONV_BEARBEITEN_10 SPOTS ES_SAPLV45U.
   19   ENDIF.
   20
   21   LOOP AT FXKOMV.
   22     FXKOMV-MANDT = VBAK-MANDT.
   23     FXKOMV-KNUMV = VBAK-KNUMV.
   24     MODIFY FXKOMV.
   25   ENDLOOP.
>>>>>   INSERT KONV FROM TABLE FXKOMV.
   27   IF SY-SUBRC NE 0.
   28     MESSAGE A100 WITH
   29   ENDIF.
   30
   31 ENHANCEMENT-POINT KONV
   32 ENDFORM.
   33 *eject
Below is my source code.
*& Report Z_BAPI_SALESORDER
REPORT z_bapi_salesorder.
* Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
* Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr.
SELECTION-SCREEN END OF LINE.
SKIP 1.
* Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE dzmengc OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapiitemin OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapireturn1    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapisdhedu
                         WITH HEADER LINE.
* Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
* Start-of-selection.
START-OF-SELECTION.
* Header data
* Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
* Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
* Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
* Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
* Partner data
* Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
* Ship to
partner-partn_role = 'WB'.
partner-partn_numb = p_ship.
APPEND partner.
* ITEM DATA
itemx-updateflag = 'I'.
* Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
* Material
item-material = p_matnr.
itemx-material = 'X'.
* Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
* Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
*   Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
*   Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
    EXPORTING
      order_header_in           = header
*     WITHOUT_COMMIT            = ' '
*     CONVERT_PARVW_AUART       = ' '
   IMPORTING
     salesdocument              = v_vbeln
*     SOLD_TO_PARTY             =
*     SHIP_TO_PARTY             =
*     BILLING_PARTY             =
*     RETURN                    =
    TABLES
      order_items_in            = item
      order_partners            = partner
*     ORDER_ITEMS_OUT           =
*     ORDER_CFGS_REF            =
*     ORDER_CFGS_INST           =
*     ORDER_CFGS_PART_OF        =
*     ORDER_CFGS_VALUE          =
*     ORDER_CCARD               =
*     ORDER_CFGS_BLOB           =
     order_schedule_ex          = lt_schedules_in
* Check the return table.
IF v_vbeln <> space.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'Document ', v_vbeln, ' created'.
ELSE.
    WRITE: / 'Error in creating document'.
ENDIF.
I am unable to trace the exact reason. Please help and thanks in advance.
Edited by: Joy Banerjee on Oct 12, 2009 7:47 AM

Hi Prashant,
Set the profile parameter abap/buffersize value to maximum.Get the virtual memory increased.
If it doesn't work, see in transaction db02 if there is sufficient tablespace.
Let me knoe the status of tablespaces.
Regards,
Sabita

Runtime error in excise tax

hi
i am getting runtime error while doing googs receipt with tax code(without tax not getting error).please see this error.
Runtime Errors         MESSAGE_TYPE_X
Date and Time          27.08.2008 20:32:45
Short dump has not been completely stored (too big)
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:
Balance in transaction currency
Long text of error message:
Diagnosis
A balance has occurred in transaction currency 'INR' with the
following details:
Exchange rate '00', amount '             8.00-' and currency key
'INR'.
The data in the transaction currency were transferred from the
calling application.
System Response
Your data cannot be processed in FI.
Procedure
The error is probably in the calling application.
Technical information about the message:
Message class....... "F5"
Number.............. 702
Variable 1.......... 00
Variable 2.......... " 8.00-"
Variable 3.......... "INR"
Variable 4.......... " "
Trigger Location of Runtime Error
Program                                 SAPLMBWL
Include                                 LMBWLU21
Row                                     59
Module type                             (FUNCTION)
Module Name                             MB_POST_GOODS_MOVEMENT
Source Code Extract
Line
SourceCde
29
   when a goods movement for an inbound or outbound delivery is posted
30
   directly from VL31N/ VL01N, XBLNR is not yet known when we call
31
   CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
32
   BKPF as well. There is no other way to forward XBLNR to FI as not
33
   every document is posted by MB_CREATE -> a new function module in
34
   MBWL for transferring the information, called by FI, meant to load
35
   the complete function group for all MBxx postings when this isn't
36
   required (Performance). Would be the better way to transport the
37
   information after switching off MBxx in later release.
38
   corresponding IMPORT ... FROM MEMORY ... can be found in
39
   AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
40
l_mem_id = 'MKPF-XBLNR'.                                   " 641365
41
EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
42
ENDIF.
43
IF xmkpf-xabln IS INITIAL.                               "note 434093
44
CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
45
ENDIF.                                                   "note 434093
46
47
ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
48
49
ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
50
CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
51
EXCEPTIONS
52
error_message = 4.
53
As soon as we have started to put things into UPDATE TASK, we must
54
ensure that errors definitely terminate the transaction.
55
MESSAGE A is not sufficient because it can be catched from
56
external callers which COMMIT WORK afterwards, resulting in
57
incomplete updates. Read note 385830 for the full story.
58
IF NOT sy-subrc IS INITIAL.
>>>>>
MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
60
sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
61
    MESSAGE A263.
62
ENDIF.
63
Optische Archivierung
64
Spaete Erfassung mit Barcode
65
Redesign of barcode handling -> note 780365
66
PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
67
xmkpf-mjahr
68
barcode.
69
70
MOVE-CORRESPONDING xmkpf TO emkpf.
71
CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
72
EXCEPTIONS
73
error_message = 4.
74
MOVE-CORRESPONDING xmkpf TO emkpf.
75
CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
76
EXCEPTIONS
77
error_message = 4.
78
IF NOT sy-subrc IS INITIAL.

Hi,
Please check the following notes
Note 1242773 - Getting short dump when doing GR for combined requisitions
Note 1047059 - Run time error in migo/Goods receipt
Regards,
Jigar

Getting ABAP runtime error while doing MIGO-GR against PO.

Hi,
Getting ABAP runtime error message while doing GR against PO.
47 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
48
49 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
50    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
51         EXCEPTIONS
52           error_message = 4.
53 * As soon as we have started to put things into UPDATE TASK, we must
54 * ensure that errors definitely terminate the transaction.
55 * MESSAGE A is not sufficient because it can be catched from
56 * external callers which COMMIT WORK afterwards, resulting in
57 * incomplete updates. Read note 385830 for the full story.
58    IF NOT sy-subrc IS INITIAL.
>>       MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
60                  sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
61 *     MESSAGE A263.
62    ENDIF.
63 * Optische Archivierung
64 * Spaete Erfassung mit Barcode
65 * Redesign of barcode handling -> note 780365
66   PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
67                                          xmkpf-mjahr
68                                          barcode.
69
70   MOVE-CORRESPONDING xmkpf TO emkpf.
71   CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
72     EXCEPTIONS
73       error_message = 4.
74    MOVE-CORRESPONDING xmkpf TO emkpf.
75    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
76         EXCEPTIONS
77           error_message = 4.
78    IF NOT sy-subrc IS INITIAL.
Any pointers
Code Formatted by: Alvaro Tejada Galindo on Jan 14, 2010 6:00 PM

Hi ,
Any inputs
for this error
No RFC destination is defined for SAP Global Trade Services
Regards
Ashu

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

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

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

Runtime error in extractor enhancement

Similar Messages

Maybe you are looking for