Error in TP Abap Objects Programs to MiniWAS 6.20

Hello,
I have install the MiniWAS 6.20 to my pc and I am trying to transport the ABAP OBJECTS programs by following the instractions. Unfortunately, the tp ended with error code 8 and the message is:
Program S_ITAB_ACCESS: Syntax error in line 000060
You cannot specify the component 'TABLE_LINE' fora generic line type in the current statement. allo
Can someone tell me what to do in order to complete this transport?
Thanks in advance

You can ignore this message, S_ITAB_ACCESS has a syntax error (you can check in se38).
In 46C the syntax was a little bit different:
when you paste this code to a 46C system, the syntax check will be ok.
In higher release it won't be ok. So if you copy it to a customer namerange eg ZS_ITAB_ACCESS and modify like this, it will be ok.
Since you cannot change program S_ITAB_ACCESS, there is not much you can do with the transport.
*      READ TABLE tab WITH TABLE KEY table_line = key
    READ TABLE tab WITH KEY table_line = key
Incho

Similar Messages

  • Re : select-options in abap-objects program

    Dear friends,
                      I want to give select-options in abap-objects program. How to give that.
                                 Thanking You
    with regards,
    Mani

    In the transaction SE24, enter your class name, click modify.
    in the tab named "Types" you have to declare two types. By example, if you want to receive one select-options that in your program that uses this class is declared like:
    " P_SAKNR FOR SKAT-SAKNR".
    you've got to declare two types in the class:
    a- TYPES:  begin of E_S_SAKNR,
                          sign(1),
                          option(2),
                          low(10),
                          high(10),
                      end of E_S_SAKNR.
    b - TYPES E_T_SAKNR type standard table of E_S_SAKNR.
    so, in the class method that you want to receive P_SAKNR as importing parameter. You got to do this:
    method TEST importing ET_SAKNR type E_T_SAKNR.
    now, in the implementation of this method you should be able to use ET_SAKNR as the same way as you usually use a parameter or a select-option. You could use it in a select with the operator IN by example..

  • Error in the ABAP Application Program

    Dear All
    While Incoming invoice posting ( MIRO). When i put amount in Unpl. Del. Csts field system give following  Error
    Error in the ABAP Application Program
    The current ABAP program "SAPLMRMK" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    Error analysis
        When changing or deleting one or more lines of the internal table
        "\FUNCTION-POOL=MR1M\DATA=YDRSEG[1]-CO" or when inserting in the table
         "\FUNCTION-POOL=MR1M\DATA=YDRSEG[1]-CO", 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
         "\FUNCTION-POOL=MR1M\DATA=YDRSEG[1]-CO"
           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
         "\FUNCTION-POOL=MR1M\DATA=YDRSEG[1]-CO".
        3. "TO idx" for specifying the end index when deleting a line
           area from or inserting a line area into the table
    Pls help to resolve above issue
    Regards,
    Vipin

    Hi,
    have you checked transaction SM13?
    if so, what information have you got there?
    Best regards.
    Edited by: Pablo Casamayor on Sep 30, 2011 3:33 PM

  • ABAP Object program flow

    Hi all,
    I'm starting to play with ABAP Object, and am very comfortable with OO features (coming from Java).
    Currently, I am hesitating on the way to code my program flow. Let me explain:
    Is it common practice to manage the screens flow within methods (with SET SCREEN etc.)?
    I would think that this is kind of bad, since it requires local classes, and is simply kind of weird (to someone coming from Java anyway). Is continuing to handle this via MODULES and such still a good way to go?
    Thanks for any enlightenment you can bring me.

    Hello,
    First, I din't mentioned that you said JAVA is better. I just said the things what u can do in JAVA u can achieve and there is a way in ABAP also. I tihnk u misunderstood my statements. :)..no hard feelings...
    Ok.
    BADI's are kind of Exits. To make it in a simple statement SAP has provided us with a way to enhance the business process.
    For example, assume that a business process goes thru step 1, step 2 and so on. Inbetween step1 and step2 you want to do something. For this SAP has provided some standard interface, which will get the information about the business process in step1 in to it. You can make use of that and customize according to your requirement.
    Send me you mail ID I will forward good document on BADI's.
    Regs,
    Venkat Ramanan N

  • Error in ABAP Objects program - SAP BI

    Dear All,
    While trying to update infoobject /BIC/ZGROSSPRI in an ODS in BI through an update routine, a syntax error is thrown when I am trying to define a variable of type tys_TG_1-/BIC/ZGROSSPRI. How is it possible to define a variable of type target field(Infoobject) ?
    For instance,
    DATA: VALUE TYPE tys_TG_1-/BIC/ZGROSSPRI.
    The error is :
    E:Field "_ty_s_TG_1-/BIC/ZGROSSPRI" is unknown. It is neither in one of the
    specified tables nor defined by a "DATA" statement. "DATA" statement.
    tys_TG_1-/BIC/ZGROSSPRI is already defined in the Class section as below
    TYPES:
    BEGIN OF tys_TG_1,
    InfoObject: ZGROSSPRI Gross Price in Statistical Currency.
    /BIC/ZGROSSPRI TYPE /BIC/OIZGROSSPRI,
    END OF tys_TG_1.
    Moderator message: please use a more meaningful subject line next time!
    Edited by: Thomas Zloch on Apr 10, 2010 7:03 PM

    Hi,
    Please use :
    DATA: VALUE TYPE /BIC/OIZGROSSPRI.
    -Vikram

  • Getting Dump error for WD ABAP URL, program CX_WDR_ADAPTER_EXCEPTION======C

    Hi SAP WD gurus,
    Getting the below bump error while launcing the WD ABAP URL on browser.
    Please help to resolve this.
    The following error text was processed in system SD1 : An exception occurred that was not caught.
    The error occurred on the application server isvsapsrmidev_SD1_01 and in the work process 9 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: RAISE_FOR of program CX_WDR_ADAPTER_EXCEPTION======CP
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C0STANDARD==============CP
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C7STANDARD==============CP
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C7STANDARD==============CP
    Regards,
    Vinod
    Edited by: Vinod Malagi on Jan 9, 2012 7:11 AM

    Hello,
    did you get this fixed? We are experiencing the same issue after just doing the EhP5 upgrade in our first system.
    Thanks,
    Ingrid Funken

  • Error while activating DataStore Object

    Hi Experts,
    I am using standard DataStore Object(0FIGL_O02), but while scheduling the laod for it its giving me error:
    "DataStore 0FIGL_O02 built incorrectly; cannot update request REQU_432B1OBKPHR2X8JKALGN0UZLE(617)"
    My DataStore Object is active, but when i am trying to actiavte it again its going for dump but all the other ODS are working fine, does anyone faced the same problem?
    Below is the dump:
    Error in the ABAP Application Program
    The current ABAP program "SAPLRSDG_MDOB" had to be terminated becau
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
      "CL_RSTRAN_TRFN================CP " in include
      "CL_RSTRAN_TRFN================CU " in
    line 159:
    "Implementation missing for method "GET_INFO_VERS". "GET_INFO_VERS"
    Message was edited by: SAP BI

    Are you using transformations/DTP to load the DSO??
    I am not sure if this helps
    Note 961556 - DataStore (activation): Columns are initialized without rule
    Note 974833 - DataStore (activation): Columns initialized without rule
    Hope it Helps
    Chetan
    @CP..

  • Keep getting this error when I run a program   UC_OBJECTS_NOT_CONVERTIBLE

    I created a project via CMOD for a modification to a BW extractor.  It is pretty simple coding but when I try and execute the extractor via RSA3 I get the following error.  I've attached the code as well and it is something with line 17.  can you please help
    Short text
        Data objects in Unicode programs cannot be converted.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLXRSA" had to be terminated because
        come across a statement that unfortunately cannot be executed.
    Error analysis
        The statement
           "MOVE src TO dst"
        requires that the operands "dst" and "src" are convertible.
        Since this statement is in a Unicode program, the special conver
        rules for Unicode programs apply.
        In this case, these rules were violated.
    Trigger Location of Runtime Error
        Program                                 SAPLXRSA
        Include                                 ZXRSAU01
        Row                                     17
        Module type                             (FUNCTION)
        Module Name                             EXIT_SAPLRSAP_001
    Source Code Extract
    Line  SourceCde
        1 *&----
        2 *&  Include           ZXRSAU01
        3 *&----
        4
        5 TABLES: VTTK.
        6 DATA: L_MCCOMVTTS LIKE MCCOMVTTS,
        7       L_TABIX LIKE SY-TABIX.
        8
        9
       10
       11 CASE I_DATASOURCE.
       12
       13  WHEN '2LIS_08TRTLP'.
       14
       15 *FIND TDLNR & VSART IN THE SHIPMENT HEADER TABLE
       16
    >>>>>  LOOP AT C_T_DATA INTO L_MCCOMVTTS.
       18   L_TABIX = SY-tabix.
       19   SELECT SINGLE * FROM VTTK WHERE TKNUM = L_MCCOMVTTS-TKNUM.
       20
       21 *FILL FIELDS WITH DATA FROM VTTK(SHIPMENT HEADER TABLE)
       22   IF SY-SUBRC = 0.
       23    L_MCCOMVTTS-Z_TDLNR = VTTK-TDLNR.
       24    L_MCCOMVTTS-Z_VSART = VTTK-VSART.
       25    MODIFY C_T_DATA FROM L_MCCOMVTTS INDEX L_TABIX.
       26   ENDIF.
       27  ENDLOOP.
       28 ENDCASE.

    ra you sure the
    table C_T_DATA and the work area L_MCCOMVTTS have the smae fileds with same data element .
    i think somewhere ther is adifference that why systerm is umable to populate the table data in to work area..
    <b>i have observed that C_T_DATA is not defined any format..
    Make sure u have the same structure for the work area as well</b>
    Please Close this thread.. when u r problem ise solved
    Reward if Helpful
    Regards
    Naresh Reddy K
    Message was edited by:
            Naresh Reddy

  • Dump error while executing this unicode program.....

    Hi,
         I got a program for 'Production Order Quantity Change Daily Checklist' ,but while executing i got the dump error from the following program stating tat,
      The current statement is only defined for character-type data objects.
    Error in the ABAP Application Program
    The current ABAP program "ZPROD" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    For the statement
       "READ DATASET ... INTO f"
    only character-type data objects are supported at the argument position
    "f".
    In this case. the operand "f" has the non-character-type "u". The
    current program is a Unicode program. In the Unicode context, the type
    'X' or structures containing not only character-type components are
    regarded as non-character-type.
    Program:
    REPORT ZPPORDER LINE-SIZE 180 NO STANDARD PAGE HEADING
                    LINE-COUNT 058(001).
    TABLES: AUFK,  "Order master data
            AFKO,  "Order header data PP orders
            RESB,  "Reservation/dependent requirements
            MAST,  "Material to BOM Link
            STKO,  "BOM Header
            STPO.  "BOM item
    DATA: BEGIN OF WA,
             AUART      TYPE AUFK-AUART,
             AUFNR      TYPE AUFK-AUFNR,
             AEDAT      TYPE AUFK-AEDAT,
             AENAM      TYPE AUFK-AENAM,
             WERKS      TYPE AUFK-WERKS,
             PLNBEZ     TYPE AFKO-PLNBEZ,
             GAMNG      TYPE AFKO-GAMNG,
             GASMG      TYPE AFKO-GASMG,
             MATNR      TYPE RESB-MATNR,
             POSNR      TYPE RESB-POSNR,
             BDMNG      TYPE RESB-BDMNG,
             BMENG      TYPE STKO-BMENG,
             MENGE      TYPE STPO-MENGE,
          END OF WA,
          ITAB  LIKE SORTED   TABLE OF WA WITH NON-UNIQUE KEY AUFNR POSNR.
    DATA: BEGIN OF ITAB2 OCCURS 0.
          INCLUDE STRUCTURE WA.
    DATA: END OF ITAB2.
    DATA: BEGIN OF ITAB_AUFK OCCURS 0,
          AUART  LIKE AUFK-AUART,
          AUFNR  LIKE AUFK-AUFNR,
          POSNR  LIKE RESB-POSNR,
          AEDAT  LIKE AUFK-AEDAT,
          AENAM  LIKE AUFK-AENAM,
          WERKS  LIKE AUFK-WERKS,
          PLNBEZ LIKE AFKO-PLNBEZ,
          GAMNG(7) TYPE P DECIMALS 0,
          GASMG(7) TYPE P DECIMALS 0,
          MATNR  LIKE RESB-MATNR,
          BDMNG(7) TYPE P DECIMALS 0,
          BMENG(7) TYPE P DECIMALS 0,
          MENGE(7) TYPE P DECIMALS 3.
    DATA: END OF ITAB_AUFK.
    DATA: FDATE LIKE SY-DATUM,
          LDATE LIKE SY-DATUM.
    DATA: X_AUFNR LIKE AFKO-AUFNR,
          X_MENGE(7) TYPE P DECIMALS 0,
          X_ERR(3).
    DATA: W_DATASET1(500) VALUE '/usr/sap/trans/data/'.
    SELECT-OPTIONS T_WERKS  FOR  AUFK-WERKS OBLIGATORY.
    SELECT-OPTIONS T_AUFNR  FOR  AUFK-AUFNR.
    SELECT-OPTIONS T_AEDAT  FOR  AUFK-AEDAT.
    PARAMETERS     PDATA    LIKE W_DATASET1.
    CONCATENATE W_DATASET1 PDATA INTO W_DATASET1.
    PERFORM F_COLLECT_DATA.
    FORM F_COLLECT_DATA.
    OPEN DATASET W_DATASET1 FOR INPUT IN TEXT MODE encoding default.
      DO.
         IF sy-subrc <> 0.
            EXIT.
         ENDIF.
         READ DATASET W_DATASET1 INTO WA.
         APPEND WA TO ITAB2.
      ENDDO.
    CLOSE DATASET W_DATASET1.
    SELECT  AAUFNR  AAUART AAEDAT AAENAM A~WERKS
            BPLNBEZ BGAMNG B~GASMG
            CMATNR  CBDMNG C~POSNR
         INTO CORRESPONDING FIELDS OF TABLE ITAB
         FROM          ( AUFK AS A
              INNER JOIN AFKO AS B ON BAUFNR  = AAUFNR
              INNER JOIN RESB AS C ON CAUFNR  = AAUFNR )
         WHERE A~AEDAT IN T_AEDAT
           AND A~WERKS IN T_WERKS.
         LOOP AT ITAB INTO WA.
            CLEAR MAST.
            SELECT SINGLE * FROM MAST WHERE MATNR = WA-PLNBEZ
                                        AND WERKS = WA-WERKS.
            CLEAR STKO.
            SELECT SINGLE * FROM STKO WHERE STLNR = MAST-STLNR
                                        AND STLAL = MAST-STLAL.
            CLEAR STPO.
            SELECT SINGLE * FROM STPO WHERE STLNR = MAST-STLNR
                                        AND POSNR = WA-POSNR.
            WA-BMENG = STKO-BMENG.
            WA-MENGE = STPO-MENGE.
            MODIFY ITAB FROM WA.
            AT NEW AUFNR.
               SKIP.
            ENDAT.
            LOOP AT ITAB2 WHERE AUFNR = WA-AUFNR
                            AND POSNR = WA-POSNR.
                IF ITAB2-GAMNG <> WA-GAMNG OR
                   ITAB2-GASMG <> WA-GASMG OR
                   ITAB2-BDMNG <> WA-BDMNG.
                   CLEAR X_MENGE.
                   IF ITAB2-BMENG <> 0.
                      X_MENGE = ITAB2-GAMNG / ITAB2-BMENG * ITAB2-MENGE.
                   ENDIF.
                   CLEAR X_ERR.
                   IF ITAB2-BDMNG <> X_MENGE.
                      X_ERR = 'Err'.
                   ENDIF.
                   FORMAT COLOR COL_TOTAL.
                   WRITE: / ITAB2-AUART  UNDER 'Type',
                            ITAB2-AUFNR  UNDER 'Prod Order',
                            ITAB2-AEDAT  UNDER 'Last Chg Dt',
                            ITAB2-AENAM  UNDER 'Last Chg by',
                            ITAB2-WERKS  UNDER 'Plant',
                            ITAB2-PLNBEZ UNDER 'Material',
                       (10) ITAB2-GAMNG  UNDER 'Order Qty' DECIMALS 0,
                       (10) ITAB2-GASMG  UNDER 'Scrap Qty' DECIMALS 0,
                            ITAB2-POSNR  UNDER 'Item',
                            ITAB2-MATNR  UNDER 'Component Req',
                       (10) ITAB2-BDMNG  UNDER 'Req Qty' DECIMALS 0,
                            X_MENGE      UNDER 'BOM Qty' COLOR COL_TOTAL,
                            ITAB2-BMENG  UNDER 'BOM Base',
                            ITAB2-MENGE  UNDER 'BOM Comp',
                            X_ERR        UNDER 'Rmks' COLOR COL_TOTAL.
                   CLEAR X_MENGE.
                   IF WA-BMENG <> 0.
                      X_MENGE = WA-GAMNG / WA-BMENG * WA-MENGE.
                   ENDIF.
                   CLEAR X_ERR.
                   IF WA-BDMNG <> X_MENGE.
                      X_ERR = 'Err'.
                   ENDIF.
                   FORMAT COLOR OFF.
                   WRITE: / WA-AUART  UNDER 'Type',
                            WA-AUFNR  UNDER 'Prod Order',
                            WA-AEDAT  UNDER 'Last Chg Dt',
                            WA-AENAM  UNDER 'Last Chg by',
                            WA-WERKS  UNDER 'Plant',
                            WA-PLNBEZ UNDER 'Material',
                       (10) WA-GAMNG  UNDER 'Order Qty' DECIMALS 0,
                       (10) WA-GASMG  UNDER 'Scrap Qty' DECIMALS 0,
                            WA-POSNR  UNDER 'Item',
                            WA-MATNR  UNDER 'Component Req',
                       (10) WA-BDMNG  UNDER 'Req Qty' DECIMALS 0,
                            X_MENGE   UNDER 'BOM Qty' COLOR COL_TOTAL,
                            WA-BMENG  UNDER 'BOM Base',
                            WA-MENGE  UNDER 'BOM Comp',
                            X_ERR     UNDER 'Rmks' COLOR COL_TOTAL.
                 ENDIF.
            ENDLOOP.
         ENDLOOP.
       LOOP AT ITAB2.
            LOOP AT ITAB INTO WA WHERE AUFNR = ITAB2-AUFNR
                                   AND POSNR = ITAB2-POSNR.
                 DELETE ITAB2.
            ENDLOOP.
            SELECT SINGLE * FROM AUFK WHERE AUFNR = ITAB2-AUFNR.
            IF SY-SUBRC <> 0.
                 DELETE ITAB2.
            ENDIF.
       ENDLOOP.
       OPEN DATASET W_DATASET1 FOR OUTPUT IN TEXT MODE encoding default.
            LOOP AT ITAB  INTO WA.
               TRANSFER WA TO W_DATASET1.
            ENDLOOP.
            LOOP AT ITAB2 INTO WA.
               TRANSFER WA TO W_DATASET1.
            ENDLOOP.
       CLOSE DATASET W_DATASET1.
    ENDFORM.
    TOP-OF-PAGE.
        FORMAT COLOR COL_TOTAL.
        WRITE: / SY-DATUM, SY-UZEIT, SY-REPID, SY-UNAME,
             50 'Daily Qty Changed Checklist for Production Order',
            120 SY-PAGNO.
        SKIP.
        WRITE: / 'Plant ', T_WERKS-LOW.
        WRITE:   ' Last Change Date ', T_AEDAT-LOW, ' to ', T_AEDAT-HIGH.
        SKIP.
        WRITE: /1  'Type',
                6  'Prod Order',
                17 'Last Chg Dt',
                29 'Last Chg by',
                42 'Plant',
                49 'Material',
                69 'Order Qty',
                83 'Scrap Qty',
                99 'Item',
               105 'Component Req',
               121 'Req Qty',
               135 'BOM Qty',
               149 'BOM Base',
               163 'BOM Comp',
               178 'Rmks'.
         ULINE.
         WRITE: / 'Previous data :- '.
         FORMAT COLOR OFF.
         WRITE: / 'Current data :- '.
    INITIALIZATION.
       LDATE = SY-DATUM.
       LDATE  = LDATE - 1.
       FDATE = LDATE.
       MOVE:   FDATE         TO  T_AEDAT-LOW.
       APPEND T_AEDAT.
       PDATA = 'AE001'.
    So,give me any suggestions where to customize r do rectify the error.This will be useful for me.
    Advance Thnx..

    *REPORT  ZPROD.
    REPORT ZPPORDER LINE-SIZE 180 NO STANDARD PAGE HEADING
                    LINE-COUNT 058(001).
    TABLES: AUFK,  "Order master data
            AFKO,  "Order header data PP orders
            RESB,  "Reservation/dependent requirements
            MAST,  "Material to BOM Link
            STKO,  "BOM Header
            STPO.  "BOM item
    DATA: BEGIN OF WA,
             AUART      TYPE AUFK-AUART,
             AUFNR      TYPE AUFK-AUFNR,
             AEDAT      TYPE AUFK-AEDAT,
             AENAM      TYPE AUFK-AENAM,
             WERKS      TYPE AUFK-WERKS,
             PLNBEZ     TYPE AFKO-PLNBEZ,
             GAMNG      TYPE AFKO-GAMNG,
             GASMG      TYPE AFKO-GASMG,
             MATNR      TYPE RESB-MATNR,
             POSNR      TYPE RESB-POSNR,
             BDMNG      TYPE RESB-BDMNG,
             BMENG      TYPE STKO-BMENG,
             MENGE      TYPE STPO-MENGE,
          END OF WA,
          ITAB  LIKE SORTED   TABLE OF WA WITH NON-UNIQUE KEY AUFNR POSNR.
    DATA: BEGIN OF ITAB2 OCCURS 0.
          INCLUDE STRUCTURE WA.
    DATA: END OF ITAB2.
    DATA: BEGIN OF ITAB_AUFK OCCURS 0,
          AUART  LIKE AUFK-AUART,
          AUFNR  LIKE AUFK-AUFNR,
          POSNR  LIKE RESB-POSNR,
          AEDAT  LIKE AUFK-AEDAT,
          AENAM  LIKE AUFK-AENAM,
          WERKS  LIKE AUFK-WERKS,
          PLNBEZ LIKE AFKO-PLNBEZ,
          GAMNG(7) TYPE P DECIMALS 0,
          GASMG(7) TYPE P DECIMALS 0,
          MATNR  LIKE RESB-MATNR,
          BDMNG(7) TYPE P DECIMALS 0,
          BMENG(7) TYPE P DECIMALS 0,
          MENGE(7) TYPE P DECIMALS 3.
    DATA: END OF ITAB_AUFK.
    DATA: FDATE LIKE SY-DATUM,
          LDATE LIKE SY-DATUM.
    DATA: X_AUFNR LIKE AFKO-AUFNR,
          X_MENGE(7) TYPE P DECIMALS 0,
          X_ERR(3).
    DATA: W_DATASET1(500) VALUE '/usr/sap/trans/data/'.
    SELECT-OPTIONS T_WERKS  FOR  AUFK-WERKS OBLIGATORY.
    SELECT-OPTIONS T_AUFNR  FOR  AUFK-AUFNR.
    SELECT-OPTIONS T_AEDAT  FOR  AUFK-AEDAT.
    PARAMETERS     PDATA    LIKE W_DATASET1.
    CONCATENATE W_DATASET1 PDATA INTO W_DATASET1.
    PERFORM F_COLLECT_DATA.
    FORM F_COLLECT_DATA.
    OPEN DATASET W_DATASET1 FOR INPUT IN TEXT MODE encoding default.
      DO.
         IF sy-subrc <> 0.
            EXIT.
         ENDIF.
         READ DATASET W_DATASET1 INTO WA.
         APPEND WA TO ITAB2.
      ENDDO.
    CLOSE DATASET W_DATASET1.
    SELECT  AAUFNR  AAUART AAEDAT AAENAM A~WERKS
            BPLNBEZ BGAMNG B~GASMG
            CMATNR  CBDMNG C~POSNR
         INTO CORRESPONDING FIELDS OF TABLE ITAB
         FROM          ( AUFK AS A
              INNER JOIN AFKO AS B ON BAUFNR  = AAUFNR
              INNER JOIN RESB AS C ON CAUFNR  = AAUFNR )
         WHERE A~AEDAT IN T_AEDAT
           AND A~WERKS IN T_WERKS.
         LOOP AT ITAB INTO WA.
            CLEAR MAST.
            SELECT SINGLE * FROM MAST WHERE MATNR = WA-PLNBEZ
                                        AND WERKS = WA-WERKS.
            CLEAR STKO.
            SELECT SINGLE * FROM STKO WHERE STLNR = MAST-STLNR
                                        AND STLAL = MAST-STLAL.
            CLEAR STPO.
            SELECT SINGLE * FROM STPO WHERE STLNR = MAST-STLNR
                                        AND POSNR = WA-POSNR.
            WA-BMENG = STKO-BMENG.
            WA-MENGE = STPO-MENGE.
            MODIFY ITAB FROM WA.
            AT NEW AUFNR.
               SKIP.
            ENDAT.
            LOOP AT ITAB2 WHERE AUFNR = WA-AUFNR
                            AND POSNR = WA-POSNR.
                IF ITAB2-GAMNG <> WA-GAMNG OR
                   ITAB2-GASMG <> WA-GASMG OR
                   ITAB2-BDMNG <> WA-BDMNG.
                   CLEAR X_MENGE.
                   IF ITAB2-BMENG <> 0.
                      X_MENGE = ITAB2-GAMNG / ITAB2-BMENG * ITAB2-MENGE.
                   ENDIF.
                   CLEAR X_ERR.
                   IF ITAB2-BDMNG <> X_MENGE.
                      X_ERR = 'Err'.
                   ENDIF.
                   FORMAT COLOR COL_TOTAL.
                   WRITE: / ITAB2-AUART  UNDER 'Type',
                            ITAB2-AUFNR  UNDER 'Prod Order',
                            ITAB2-AEDAT  UNDER 'Last Chg Dt',
                            ITAB2-AENAM  UNDER 'Last Chg by',
                            ITAB2-WERKS  UNDER 'Plant',
                            ITAB2-PLNBEZ UNDER 'Material',
                       (10) ITAB2-GAMNG  UNDER 'Order Qty' DECIMALS 0,
                       (10) ITAB2-GASMG  UNDER 'Scrap Qty' DECIMALS 0,
                            ITAB2-POSNR  UNDER 'Item',
                            ITAB2-MATNR  UNDER 'Component Req',
                       (10) ITAB2-BDMNG  UNDER 'Req Qty' DECIMALS 0,
                            X_MENGE      UNDER 'BOM Qty' COLOR COL_TOTAL,
                            ITAB2-BMENG  UNDER 'BOM Base',
                            ITAB2-MENGE  UNDER 'BOM Comp',
                            X_ERR        UNDER 'Rmks' COLOR COL_TOTAL.
                   CLEAR X_MENGE.
                   IF WA-BMENG <> 0.
                      X_MENGE = WA-GAMNG / WA-BMENG * WA-MENGE.
                   ENDIF.
                   CLEAR X_ERR.
                   IF WA-BDMNG <> X_MENGE.
                      X_ERR = 'Err'.
                   ENDIF.
                   FORMAT COLOR OFF.
                   WRITE: / WA-AUART  UNDER 'Type',
                            WA-AUFNR  UNDER 'Prod Order',
                            WA-AEDAT  UNDER 'Last Chg Dt',
                            WA-AENAM  UNDER 'Last Chg by',
                            WA-WERKS  UNDER 'Plant',
                            WA-PLNBEZ UNDER 'Material',
                       (10) WA-GAMNG  UNDER 'Order Qty' DECIMALS 0,
                       (10) WA-GASMG  UNDER 'Scrap Qty' DECIMALS 0,
                            WA-POSNR  UNDER 'Item',
                            WA-MATNR  UNDER 'Component Req',
                       (10) WA-BDMNG  UNDER 'Req Qty' DECIMALS 0,
                            X_MENGE   UNDER 'BOM Qty' COLOR COL_TOTAL,
                            WA-BMENG  UNDER 'BOM Base',
                            WA-MENGE  UNDER 'BOM Comp',
                            X_ERR     UNDER 'Rmks' COLOR COL_TOTAL.
                 ENDIF.
            ENDLOOP.
         ENDLOOP.
       LOOP AT ITAB2.
            LOOP AT ITAB INTO WA WHERE AUFNR = ITAB2-AUFNR
                                   AND POSNR = ITAB2-POSNR.
                 DELETE ITAB2.
            ENDLOOP.
            SELECT SINGLE * FROM AUFK WHERE AUFNR = ITAB2-AUFNR.
            IF SY-SUBRC <> 0.
                 DELETE ITAB2.
            ENDIF.
       ENDLOOP.
       OPEN DATASET W_DATASET1 FOR OUTPUT IN TEXT MODE encoding default.
            LOOP AT ITAB  INTO WA.
               TRANSFER WA TO W_DATASET1.
            ENDLOOP.
            LOOP AT ITAB2 INTO WA.
               TRANSFER WA TO W_DATASET1.
            ENDLOOP.
       CLOSE DATASET W_DATASET1.
    ENDFORM.
    TOP-OF-PAGE.
        FORMAT COLOR COL_TOTAL.
        WRITE: / SY-DATUM, SY-UZEIT, SY-REPID, SY-UNAME,
             50 'Daily Qty Changed Checklist for Production Order',
            120 SY-PAGNO.
        SKIP.
        WRITE: / 'Plant ', T_WERKS-LOW.
        WRITE:   ' Last Change Date ', T_AEDAT-LOW, ' to ', T_AEDAT-HIGH.
        SKIP.
        WRITE: /1  'Type',
                6  'Prod Order',
                17 'Last Chg Dt',
                29 'Last Chg by',
                42 'Plant',
                49 'Material',
                69 'Order Qty',
                83 'Scrap Qty',
                99 'Item',
               105 'Component Req',
               121 'Req Qty',
               135 'BOM Qty',
               149 'BOM Base',
               163 'BOM Comp',
               178 'Rmks'.
         ULINE.
         WRITE: / 'Previous data :- '.
         FORMAT COLOR OFF.
         WRITE: / 'Current data :- '.
    INITIALIZATION.
       LDATE = SY-DATUM.
       LDATE  = LDATE - 1.
       FDATE = LDATE.
       MOVE:   FDATE         TO  T_AEDAT-LOW.
       APPEND T_AEDAT.
       PDATA = 'AE001'.

  • Dump Error in ES55 Connection Object

    Dear Experts,
    I am getting the error when I am saving the connection object.
    Error in the ABAP Application Program
    The current ABAP program "CL_EEWA_RFC_CONTAINER_LOCATIONCP" had to betTerminated. because it has come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "CL_EEWA_RCI_COMMON============CP " in include
    "CL_EEWA_RCI_COMMON============CM003 " in line 145:
    "The data object "LS_EQUI" does not have a component called "LOGIKNR_WA"
    It seems, I am missing some config settings.
    Please help me to close this issue.
    Thanks
    Aswin

    Hi Aswin
    The problem is not caused by the number ranges, but an inconsistency between the Data Dictionary and the code.
    The code for method GET_SERVLOC_BY_CONTAINER of class CL_EEWA_RCI_COMMON (in the shortdump as CL_EEWA_RCI_COMMON============CM003), selects information from view V_EQUI_WASTE and tries to populate an internal structure using the fieldname LOGIKNR_WA of the view.
    Please check the view V_EQUI_WASTE contains an append called EEWA_EQUI_WASTE (transaction SE11, the append should be at the bottom of tab "View Flds." (probably not). Afterwards check if append view EEWA_EQUI_WASTE exists (again use transaction SE11).
    If EEWA_EQUI_WASTE is missing altogether or if the view V_EQUI_WASTE doesn't contain the APPEND, there was a problem with the SAP installation or an upgrade. Please check with Basis and SAP to get this fixed.
    Are you by any chance using waste management? Or are you a stock standard power company?
    I wouldn't expect this code to be called, when you don't use waste management, so there might be some customising someone (ab)used: IMG: SAP Utilities: Waste Management.
    Yep
    Jürgen

  • Re : select-options in abap objects

    Dear friends,
    I want to give select-options in abap-objects program. How to give that.
    Thanking You
    with regards,
    Mani

    HI Mani,
    It's common mix ABAP Procedural with ABAP Objects in the same program.
    You should use the same way used in ABAP procedural program as Marco Cerdelli sad.
    But inside ABAP OBJECTS classes you can't use is these statement type.
    Don't forget to close this thread and all yours previous when your question be answered ! In case of doubt read the [rules of engagement|https://forums.sdn.sap.com/].
    Best Regards.
    Marcelo Ramos

  • Major global classes used in abap objects

    Hi,
    I am new to the abap objects and till now i am to understand that the role of the global classes are important in the abap object program. I had tried to search on the net but i was not able to get the desired result.
    I want to know which are the major global classes which are used in the ABAP objects.
    Plzz provide me guidelines for it.

    Ricx,
       It depends on your requirement.
    For alv's we use these global classes. For Webdynpro related alv we use different global classes.
    CL_GUI_ALV_GRID (List Viewer)
    CL_GUI_ALV_GRID_BASE (Basis Class for ALV grid)
    CL_GUI_ALV_TREE (ALV Tree Control)
    CL_GUI_ALV_TREE_SIMPLE (Simple ALV Tree)
    CL_ALV_TABLE_CREATE (Dynamic Creation of ALV Data Table)
    CL_ALV_TREE_BASE (Basis Class ALV Tree Control)
    CL_CK_ALVTREE_NKEY_2_OBJECT (Converter Node Key Object)
    CL_ALV_EVENT_DATA (Changing Data Container for Events)
    CL_ALV_EVENT_TOOLBAR_SET (ALV Context menu)
    Regards,
    Arun.

  • ABAP Objects and Upgrade

    Hi,
    I would like to discuss pro and cons of using ABAP Objects for custom development related to upgrades. For example, it seems to be an advantage to encapsulate standard functionality. Through encapsulation the calling programs do not have to care about whether or not the underlying functionality has been changed. Reuse makes it possible to adapt affected areas centrally without having to make changes in various places. However, I saw a thread in this forum regarding older ABAP Objects programming which was obsolete after an upgrade. Even if it seems good that obsolete statements are detected and can be exchanged, it is additional upgrade work which would have been avoided if the code had not been written in ABAP Objects.
    Please share you pros and cons regarding this subject.
    Thanks!

    J@Y - it's a good link to an interesting discussion.  But it's 5 years old...  ABAP Objects has moved on since then.  ( Also, (moderator hat on) please refrain from just posting links without at least giving an indication of what the links are about ).
    To the original poster.  I think it is VERY unlikely that statements that are allowed now in an OO environment will be disallowed in future.  I've been working in Objects since 46C, and have been careful to observe the warnings, and also quick to adopt the new syntax and reject the obsolete (even before it became necessary).  The only remedial work I've had to do in ten years, is on a few classes, where the constructor wasn't calling the super constructor.  And that was easily identified and remedied.
    My experience has been, in those last ten years, that properly written object oriented code leads to developments that are much easier and quicker to maintain - and therefore, a lot cheaper.  And that's the bottom line.
    matt

  • ABAP objects design patterns

    hi all,
        can any one send me the Design patterns used for ABAP objects programming in ABAP. eg mvc and sample code which uses the design patterns
    cheers
    senthil

    Of course that program is not an object design pattern
    (Its just a little ABAP Objects syntax demo that I wrote  years ago
    I don't know about a list of OO design patterns implemented in ABAP Objects.
    A very simple one, a Singleton might look like this:
    <b>* cl_singleton: Eager Variant
    CLASS cl_singleton DEFINITION FINAL
                                  CREATE PRIVATE.
      PUBLIC SECTION.
        CLASS-METHODS: class_constructor,
                       get_singleton RETURNING VALUE(singleton)
                                               TYPE REF TO cl_singleton.
      PRIVATE SECTION.
        CLASS-DATA singleton TYPE REF TO cl_singleton.
    ENDCLASS.
    CLASS cl_singleton IMPLEMENTATION.
      METHOD class_constructor.
        CREATE OBJECT singleton.
      ENDMETHOD.
      METHOD get_singleton.
        singleton = cl_singleton=>singleton.
      ENDMETHOD.
    ENDCLASS.
    cl_singleton: Lazy Variant
    CLASS cl_singleton DEFINITION FINAL
                                  CREATE PRIVATE.
      PUBLIC SECTION.
        CLASS-METHODS get_singleton RETURNING VALUE(singleton)
                                              TYPE REF TO cl_singleton.
      PRIVATE SECTION.
        CLASS-DATA singleton TYPE REF TO cl_singleton.
    ENDCLASS.
    CLASS cl_singleton IMPLEMENTATION.
      METHOD get_singleton.
        IF cl_singleton=>singleton IS INITIAL.
          CREATE OBJECT cl_singleton=>singleton.
        ENDIF.
        singleton = cl_singleton=>singleton.
      ENDMETHOD.
    ENDCLASS.</b>

  • How to use LDB PNP with ABAP objects in a program

    Hello,
    I am wondering if anybody has used the HR logical database(LDB) PNP with user defined ABAP objects in a program? I am using the FM- <b>LDB_PROCESS</b> but its not working. Also assigning PNP in the attributes section of the program -- so that I can use predefined fields from the LDB and then invoking the FM doesn't work -- throwing 'Logical database already active' error.
    I suppose even with the ABAP objects and the new FM -- I should still be able to utilize the pre-defined fields of the PNP database -- and also the built in authorizations. I cannot use GET PERNR and REJECT as they give errors. I understand that the use of HR-macros (RP-PROVIDE-FROM-LAST and et al.) are not allowed as they use the table work area -- which is not allowed in ABAP-OOPS.
    I would really appreciate if anyone could show me some insight regarding this. Thank you.
    Kshitij R. Devre

    Hi Kshitij
    It would be really good if we could use both together. But as I know, it is not possible. "GET pernr." is an event-like loop statement and so cannot be used in OO context. And I guess, the same restriction holds for the "LDB_PROCESS" since it uses LDB-specific processing.
    What I suggest you is to use standard and BAPI functions.
    Sorry for giving bad news...
    *--Serdar

Maybe you are looking for

  • How to set up text alerts for contacts

    How do you set up ring tones for contacts? Besides going to contacts.  I know in the S4 there was a setting under contacts to make text tones different for each contact.  How do you set it up? Thanks

  • Why is type matter not showing as black?

    Just loaded Pages 08 but when Typing all wording appears white out of purple - Why?

  • HT201320 How do I set up my iCloud email account on an OLD iPhone w/ OS4.X?

    Hey everyone, My iPhone 4S got stolen, and I don't qualify for an upgrade for one more month.  So I've reverted to my old 3G iPhone.  The rep at ATT told me NOT to upgrade the OS - that it would make this thing run slower than molasses.  SO, I've onl

  • How to use getEquipmentStatusCondition() ?

    Hi, I would like to use the function getEquipmentStatusCondition to filter mly equipment list. But, during the process an exception is launch. After debug, i've seen it is at this point (in the UIHelperImpl.java): if (parent == null) { ---> size = ((

  • FIFO valuation with stock transfer

    Hello I would like to include stock transfer movements between 2 plants within the same company code in my FIFO valuation. The price to be used in the receiving plant shall be the std price from the delivering plant. Unfortunately I don't have succes