Infopackage routine error

HI experts
My datasource is an external datasource. I want to load only those records with the field 'FECULMOD' like sysdate
To do this I have written an ABAP routine in my Infopackage with the code below:
<i>DATA: va_maxdat LIKE /BIC/ADSPX_0100-/BIC/TDPXMOD.
data: l_idx like sy-tabix.
read table l_t_range with key
     fieldname = 'FECULMOD'.
l_idx = sy-tabix.
SELECT SINGLE /BIC/TDPXMOD
INTO va_maxdat
FROM /BIC/ADSPX_0100
WHERE /BIC/CHPXTDATM = 'MARG_ART'.
l_t_range-SIGN = 'I'.
l_t_range-OPTION = 'GT'.
l_t_range-LOW = va_maxdat.
APPEND l_t_range.
modify l_t_range index l_idx.
p_subrc = 0.</i>
My SELECT instruction returns values less than sysdate.
When I execute my IP, I got a dump with this message:
For the field FECULMOD, any selection with SIGN 'I', OPTION 'GT' is not autorised
Can anybody help me please.
Thank

Hi Eric,
you need to specify a upper limit ( high value of 9991231) and use BT as the option. That is what is possible in an infopackage. There is no option available to select for <, >, <=, >=, *. It is only = or bt for a specific value or a range.
regards
Siggi

Similar Messages

  • Start routine errors while activating transformations 2LIS_13_VDITM

    Hi Friends,
    I have an error while activating transformation for Cube: 0SD_C03
    Transformation Z2LIS_13_VDITM
    The start routine error is like this->
    Start Routine: Syntax error in routine
    Rule (target: 0SUBTOT_1S, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0SUBTOT_2S, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0SUBTOT_3S, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0SUBTOT_4S, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0SUBTOT_5S, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0SUBTOT_6S, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0QUANT_B, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0DOC_ITEMS, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0NET_VAL_S, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0COST_VAL_S, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0GR_WT_KG, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0NT_WT_KG, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0VOLUME_CDM, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0BP_GRP, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0CP_CATEG, group: 01 Standard Group): Syntax error in routine
    S:RSTRAN:552 38 0CRM_PROD 01 Standard Group 0MATERIAL
    Rule (target: 0DEB_CRED, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0PROD_CATEG, group: 01 Standard Group): Syntax error in routine
    Key rule 43 (target field: 0VERSION): Initial update set
    pls guys if some one can suggest me to solve this i would be very greateful
    Bala
    Edited by: bala dondeti on Jun 20, 2011 12:32 PM
    Edited by: bala dondeti on Jun 20, 2011 12:43 PM

    Thanks for the info Umesh,
    Just to be sure - I should simply change "SOURCE_PACKAGE" to "DATA_PACKAGE" in the code of the start routine? "Source_Package" is present in two places in that code:
    METHODS
          start_routine
            IMPORTING
              request                  type rsrequest
              datapackid               type rsdatapid
            EXPORTING
              monitor                  type rstr_ty_t_monitors
            CHANGING
              SOURCE_PACKAGE              type tyt_SC_1
            RAISING
              cx_rsrout_abort.
    and then after that in:
    Migrated update rule call
      Perform routine_9998
      TABLES
        SOURCE_PACKAGE
      CHANGING
        l_abort.
    Or should I revert to the 3.5 version? (as a side note, that Data Source (2LIS_13_VDITM) has been activated in 7.0 version by default, when I replicated data sources in BW).
    Praveen, as to your remarks, I have the datasource 2LIS_13_VDITM (in version 7.0) active, along with the appropriate Infosource. Transformation between the DataSource and InfoSource is active, and only the transformation between the InforSource and the Cube poses problems.
    BR,
    Alek

  • Am getting Routine error  R6034. I can not open iTunes.  Windows Vista Home  64 bit

    For the  first time,am getting a routine error R6034. Do not let open my iTunes, and possible lost all my contents. Why is this happening, is it nothing  secure on the Internet no more even our music? Please  I appreaciate any good help. I tried to redownload am stil the same  message. During reinstallation.."Service Apple mobile device failed to start. Verify that you have sufficient privileges. Options   ABORT,RETRY,OR IGNORE. That is what am getting.

    Go to Control Panel > Add or Remove Programs (Win XP) or Programs and Features (later)
    Remove all of these items in the following order:
    iTunes
    Apple Software Update
    Apple Mobile Device Support (if this won't uninstall move on to the next item)
    Bonjour
    Apple Application Support
    Reboot, download iTunes, then reinstall, either using an account with administrative rights, or right-clicking the downloaded installer and selecting Run as Administrator.
    The uninstall and reinstall process will preserve your iTunes library and settings, but ideally you would back up the library and your other important personal documents and data on a regular basis. See this user tip for a suggested technique.
    Please note:
    Some users may need to follow all the steps in whichever of the following support documents applies to their system. These include some additional manual file and folder deletions not mentioned above.
    HT1925: Removing and Reinstalling iTunes for Windows XP
    HT1923: Removing and reinstalling iTunes for Windows Vista, Windows 7, or Windows 8
    tt2

  • Error in Infopackage- retrieve error data

    Hello experts,
    During execution of infopackage to extract data from ECC i had this error : "Error in codepage mapping for source system" read some thread i understand there was some idoc in error therefore i found the problem in BD87 in source system and i have processed my idocs correctly.
    NOW: i have again in the log my infopackage in error and after this execution i have many other executions correct so the delta extraction, after that problem, contunue in right way.
    My question is: how can i manage the data that went in error? the infopackage with error extract 2400 record where are these record?how can i retrieve these records?
    thanks
    kind regards
    Boris

    Hi,
    After you processed your Idocs in BD87, your subsequent loads went successful. So, now there is no Idocs problem as such.
    For your missing records, run a  Repair Full load by specifying the data selection. Then it will bring all the missed records.
    Regards,
    Suman

  • Overflow in EXCEL title line routine - Error while posting FI document

    Hi All -
       We are getting an "Overflow in EXCEL title line routine" error message while posting SAP FI document thru FB01 transaction code. We are getting this error message while entering the coding block, can anyone please explain how this error message is coming and how to rectify it.
    Thanks in advance.
    Rds,
    K

    Hi,
    Thanks for the reply.
    The interesting part is, it is a standard message and there is no message class ZKV available in the system.  We have gone live only six months back and not done a single enhancement in HR module till now.
    As far as FICO is concerned, we have an internal control that we will not enhance any of the FI transactions in view of data accuracy and integrity.  We don't have enhancements running in FI & CO modules also.
    I am sure that it is a standard message.  This message is arising out of the function module 'AC_DOCUMENT_CREATE' called internally in the program associated with posting run transaction.
    Please hint, what could be the problem.
    Regards,
    Hema

  • COM routine error in Background job.

    Hello All,
    During background process of a job, we found a "Error for COM routine using application program (return code 40.301)" for a CVC. It caused a backgroung job to fail.
    Could you please throw light, why this error comes only for this CVC ( as had the same instance before for the same CVC ) & how to fix it ?
    Reagrds
    Rahul Chitte

    HI Rahul,
    COM routine errors are generally related to LC errors. There are a number of possible causes for it, the CVC was created when a macro was running or it was deleted from MPOS but not from LC etc etc.,
    Solution to this is go /n/sapapo/msdp_admin --> Go to your planning area --> Double Click --> Look for Extras in Menu --> Go to Consistency check and do a time series consistency check.
    Remember to click Check for Live Cache Anchor and leave 'Repair' unselected.
    This will return what is the error. Once you see the error, you can go back and select the 'Repair' Also and then execute again. This should resolve the problem.
    Hope this is helpful.
    Thanks
    Mani Suresh

  • COM routine error code descriptions in SAP APO - transaction /SAPAPO/OM10

    I had recently encountered a  COM error in SCM APO and wasted a lot of time trying to figure out what the error code actually meant.
    If you ever have this issue, you can use transaction /SAPAPO/OM10 to resolve any COM routine error message.
    You can also check the message class /SAPAPO/OM_TS and possibly some other /SAPAPO/OM* message classes as well. This is where the error message descriptions are coming from.
    Hope this helps.

    Hello Gabor,
    -> As you know, you could use the transaction /n/sapapo/om10 to Display Meaning of COM Return Code.
    -> In case you got a COM error in SCM APO => to avoid a spending a lot of time trying to figure out what the error code actually meant, please, open the OSS message to the component BC-DB-LCA to get the liveCache application support from SAP on this issue.
    Thank you and best regards, Natalia Khlopina

  • COM ROUTINE ERROR

    Hi Any one can explain the reason for Com Routine Error 40.075.
    Description:
    Error for COM routine using application program (return code 40.075)
    All input time series to which you can distribute are fixed
    And Please provide the solution also.
    Thanks and Regards,
    RAVI SAGAR CHENNU

    Procedure
    Remove at least one of the fixings of the aggregated time series
    objects.
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    You have fixed information in your planning area, which is causing the
    issue to occurs.
    So in tscube, if you try and load data into a key figure which has
    at least one value fixed, the load will fail, if your selection criteria
    in tscube overlaps with the aggregate level of the fixing. The reason is
    because, tscube does the data set in one shot for the selection criteria
    If your cube is a backup cube and you already have the fixing
    information in it, you can use macro to unfix the fixing information in
    the planning area, then use tscube to load.
    Before executing the TSCUBE,you can schedule this macro job and then
    execute the TSCUBE.while defining the macro you can check whether
    the keyfigure value is fixed or not using the macro function
    IS_FIXED(). If it's fixed then please unfix the cell.
    You have fixed information in your planning area, which is causing the
    issue to occurs.
    To run the macro considering fixings, please, update your macro. Change
    the Row properties and flag the "Adjust Fixings" information for each
    row.
    Also please find the below notes related to fixings:
    1599645
    687074 Macros: General notes on fixing with macros
    643517 Macrobuilder: Fixing key figures with a macro
    Even that these notes do not apply because of the SP, information is
    relevant.
    Also, please, take a look at the online documentation:
    http://help.sap.com/saphelp_scm50/helpdata/en/92/cd15426bf3dd2ce10000000
    a1550b0/frameset.htm

  • Start routine error ....,

    Hi
    i written start routine in transformations. it showing some error. please suggest correct way.
    TYPES : begin of fs_pctr,
                  profit_ctr type /BIC/PZPRFTCTR-/BIC/ZPRFTCTR,
                 end of fs_pctr.
    DATA : it_pctr type standard table of fs_pctr,
                wa_pctr like line of it_pctr.
    select /BIC/ZPRFTCTR from /BIC/PZPRFTCTR into table it_pctr where objvers  = 'A'.
    loop at source_package assigning <source_fields>.
    read table it_pctr with key profit_ctr = <source_fields>-/BIC/ZPRFTCTR.
       if sy-subrc ne 0.
        delete source_package.
       endif.
    endloop.
    Error: E:In the OO context either an INTO or an ASSIGNING specification or the         
    addition "TRANSPORTING NO FIELDS" must be used. addition "TRANSPORTING          
    NO FIELDS" must be used.
    waiting for suggestions.
    Regrds
    swetha

    Hi,
    you can work around with the code as below... this would be much faster as you are deleting transaction data based on some master. so looping master is lesser and deleting transaction in that is faster.
    Declaration
    - internal table is correct but for work area declare as under
    data wa_pctr type fs_pctr.
    after select statement
    loop at it_pctr into wa_Pctr.
    delete source_package where /bic/zprftctr = wa_pctr-profit_ctr
    endloop.
    Hope this helps.
    Regards
    Raj

  • Correct ABAP Logic in Transformations-Start or Field Routine Error

    Hi
    I have written this code in start routine to split the data record into 2 if  bic/zdte_trm is not initial.
    But i am getting below error please correct me where i was wrong
    LOOP AT SOURCE_PACKAGE ASSIGNING <source_fields>.
          IF NOT <source_fields>-/bic/zdte_trm = ' '.
    * append a new record to source_package with this field initialised
            CLEAR wa_source.
            MOVE <source_fields> TO wa_source.
            CLEAR wa_source-/bic/zdte_trm.
            APPEND wa_source TO SOURCE_PACKAGE.
          ENDIF.
        ENDLOOP.
    At a LOOP over an internal table, the table is not allowed to be changed 
      in the loop tail as a whole.                                            
    SORT, MOVE, REFRESH, CLEAR are, for example, not allowed.

    Hi Saurov,
    Thanks for all the help.....
    The code is working fine but
    I got a strange issue while using this code
    DSO Data (Exisiting Data )
    Emp ID---Start Date--End Date
    1-----01/01/2008----
    Data from source system
    Emp ID---Start Date--End Date
    1-----01/01/2008----01/05/2008
    The code is spliting that record into 2 records
    1-----01/01/2008----
    1-----01/01/2008----01/05/2008
    and in source system in can see total 3 records
    1-------01/01/2008   (Exisisting Record)
    1-------01/01/2008   (New)
    1-----01/01/2008----01/05/2008 (New)
    The key fields in DSO is Emp Id and End Date
    Please,please update me how to resolve this issue

  • ABAP Logic in Transformations-Start or Field Routine Error

    Hi,
    Below is the field routine in transformations that will calculacte No of Years between 2 dates (Source Field & System Date)
    It is showing me no systex Error but when i started data load ,Load is failing due to below mentioned error
    Routine:
    IF NOT SOURCE_FIELDS-/BIC/ZCYB_DOB IS INITIAL.
    CALL FUNCTION 'FIMA_DAYS_AND_MONTHS_AND_YEARS'
    EXPORTING
    I_DATE_FROM = SOURCE_FIELDS-/BIC/ZCYB_DOB
    I_KEY_DAY_FROM = 00
    I_DATE_TO = SYST-DATUM
    I_KEY_DAY_TO = 00
    I_FLAG_SEPERATE = 'X'
    IMPORTING
    E_YEARS = RESULT.
    ENDIF.
    Error:
    The exception CX_STATIC_CHECK is neither caught nor is it declared in
    the RAISING clause of "EXECUTE".
    Please update me where i was doing wrong
    Thanks

    It must have something to do with your input variables - I ran this FM locally using my DOB and today's date and it worked fine.
    make sure your input date types are in the correct format for the FM.

  • End routine error upon trying to transport

    Hello folks,
    Getting a RC 8 upon trying to transport an end routine piece to our QA environment.
    No syntax error upon trying to check the code in the end routine. The custom infoobject that i m trying to populate in this code is set to 'Initial' in the transformational rules. Plz can you share any clues there. This transformation is attached to an Infocube.
    Here is the code:
    data: v_fiscper(3) type n.
      loop at RESULT_PACKAGE assigning <result_fields>.
        clear v_fiscper.
        v_fiscper = <result_fields>-fiscper+4(3).
        case v_fiscper.
          when '001' or '002' or '003'.
           concatenate 'Q1,' <result_fields>-fiscyear
               into <result_fields>-/bic/zfiscqtr.
          when '004' or '005' or '006'.
           concatenate 'Q2,' <result_fields>-fiscyear
               into <result_fields>-/bic/zfiscqtr.
          when '007' or '008' or '009'.
           concatenate 'Q3,' <result_fields>-fiscyear
               into <result_fields>-/bic/zfiscqtr.
          when '010' or '011' or '012'.
           concatenate 'Q4,' <result_fields>-fiscyear
               into <result_fields>-/bic/zfiscqtr.
        endcase.
      endloop.
    Appreciate help on this one.
    Cheers !!

    How is InofObject zfiscqtr implemented?
    Additional:
    Try to use RSA1 transport connection.
    Select your transformation, cube and so on and collect all necessary objects.
    Regards
    Andreas
    Edited by: Andreas Schindler on Nov 26, 2009 10:24 AM

  • Start routine error - infosource 2LIS_13_VDITM

    Hello,
    During the activation of the standard InfoCube 0SD_C03 (Sales: Overview), I have encountered a problem in a transformation between the infosource 2LIS_13_VDITM and the afrementioned Cube (this transformation has been transferred during the activation of Business Content).
    The transformation is inactive after the installation (other dataflow structures, for other datasources attached to this Cube have been automatically activated). When I try to active it, an error message appers, informing that:
    a) Initial update has been set for some of the key rules (e.g. for target field 0VERSION) - but that is a minor obstacle; the bigger problem is that
    b) there is a syntax error in the start routine for this transformation
    Checking that start routine results with the following error:
    E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter
    "SOURCE_PACKAGE" is incompatible with the formal parameter
    "DATA_PACKAGE".
    Since I'm not an ABAPer, that info is a bit vague to me.
    I have tried to find an answer in the forums but with no success. So if anyone could provide a solution this problem or point me to a thread where it has been answered, I would be very grateful.
    I can provide more details should those be needed.
    Best Regards,
    Alek

    Thanks for the info Umesh,
    Just to be sure - I should simply change "SOURCE_PACKAGE" to "DATA_PACKAGE" in the code of the start routine? "Source_Package" is present in two places in that code:
    METHODS
          start_routine
            IMPORTING
              request                  type rsrequest
              datapackid               type rsdatapid
            EXPORTING
              monitor                  type rstr_ty_t_monitors
            CHANGING
              SOURCE_PACKAGE              type tyt_SC_1
            RAISING
              cx_rsrout_abort.
    and then after that in:
    Migrated update rule call
      Perform routine_9998
      TABLES
        SOURCE_PACKAGE
      CHANGING
        l_abort.
    Or should I revert to the 3.5 version? (as a side note, that Data Source (2LIS_13_VDITM) has been activated in 7.0 version by default, when I replicated data sources in BW).
    Praveen, as to your remarks, I have the datasource 2LIS_13_VDITM (in version 7.0) active, along with the appropriate Infosource. Transformation between the DataSource and InfoSource is active, and only the transformation between the InforSource and the Cube poses problems.
    BR,
    Alek

  • 0CO_REPLINE infoobject ABAP routine error

    Hi experts,
    I am facing a problem while activating a transformation for the cube 0CCA_C11. I installed the flow in 3.5 and wen i was migrating the flow, i first migrated the update rule. At that time, the transformation is giving me " syntax error in the routine" for the infoobject 0CO_REPLINE.
    The eroor message is given below:
    *E:The type "_TY_S_SC_1_FULL" is unknown, but there is a type with the similar name "_TY_S_TG_1_FULL". "_TY_S_TG_1_FULL".*
    I have appended part of the routine:
    CLASS lcl_transform IMPLEMENTATION.
      METHOD compute_0CO_REPLINE.
      IMPORTING
        request     type rsrequest
        datapackid  type rsdatapid
        SOURCE_FIELDS-CO_AREA TYPE /BI0/OICO_AREA
        SOURCE_FIELDS-CO_DOC_NO TYPE /BI0/OICO_DOC_NO
        SOURCE_FIELDS-CO_ITEM_NO TYPE /BI0/OICO_ITEM_NO
        SOURCE_FIELDS-FISCVARNT TYPE /BI0/OIFISCVARNT
        SOURCE_FIELDS-FISCPER TYPE /BI0/OIFISCPER
        SOURCE_FIELDS-COSTCENTER TYPE /BI0/OICOSTCENTER
        SOURCE_FIELDS-ACTTYPE TYPE /BI0/OIACTTYPE
        SOURCE_FIELDS-VTYPE TYPE /BI0/OIVTYPE
        SOURCE_FIELDS-VTDETAIL TYPE /BI0/OIVTDETAIL
        SOURCE_FIELDS-VTSTAT TYPE /BI0/OIVTSTAT
        SOURCE_FIELDS-METYPE TYPE /BI0/OIMETYPE
        SOURCE_FIELDS-VERSION TYPE /BI0/OIVERSION
        SOURCE_FIELDS-VALUATION TYPE /BI0/OIVALUATION
        SOURCE_FIELDS-COSTELMNT TYPE /BI0/OICOSTELMNT
        SOURCE_FIELDS-DB_CR_IND TYPE /BI0/OIDB_CR_IND
        SOURCE_FIELDS-PIOBJSV TYPE /BI0/OIPIOBJSV
        SOURCE_FIELDS-PIOVALUE TYPE /BI0/OIPIOVALUE
        SOURCE_FIELDS-PART_CCTR TYPE /BI0/OIPART_CCTR
        SOURCE_FIELDS-PART_ACTTY TYPE /BI0/OIPART_ACTTY
        SOURCE_FIELDS-PART_COORD TYPE /BI0/OIPART_COORD
        SOURCE_FIELDS-PART_WBSEL TYPE /BI0/OIPART_WBSEL
        SOURCE_FIELDS-PART_ABCPR TYPE /BI0/OIPART_ABCPR
        SOURCE_FIELDS-AMOUNT TYPE /BI0/OIAMOUNT
        SOURCE_FIELDS-AMOUNTFX TYPE /BI0/OIAMOUNTFX
        SOURCE_FIELDS-AMOUNTVR TYPE /BI0/OIAMOUNTVR
        SOURCE_FIELDS-QUANTITY TYPE /BI0/OIQUANTITY
        SOURCE_FIELDS-QUANTITYFX TYPE /BI0/OIQUANTITYFX
        SOURCE_FIELDS-QUANTITYVR TYPE /BI0/OIQUANTITYVR
        SOURCE_FIELDS-CURRENCY TYPE /BI0/OICURRENCY
        SOURCE_FIELDS-CURTYPE TYPE /BI0/OICURTYPE
        SOURCE_FIELDS-UNIT TYPE /BI0/OIUNIT
        SOURCE_FIELDS-AUXACCTYPE TYPE /BI0/OIAUXACCTYPE
        SOURCE_FIELDS-AUXACCVAL TYPE /BI0/OIAUXACCVAL
        SOURCE_FIELDS-COMP_CODE TYPE /BI0/OICOMP_CODE
        SOURCE_FIELDS-BUS_AREA TYPE /BI0/OIBUS_AREA
        SOURCE_FIELDS-FUNC_AREA TYPE /BI0/OIFUNC_AREA
        SOURCE_FIELDS-PCOMP_CODE TYPE /BI0/OIPCOMP_CODE
        SOURCE_FIELDS-PFUNC_AREA TYPE /BI0/OIPFUNC_AREA
        SOURCE_FIELDS-CHRT_ACCTS TYPE /BI0/OICHRT_ACCTS
        SOURCE_FIELDS-GL_ACCOUNT TYPE /BI0/OIGL_ACCOUNT
        SOURCE_FIELDS-CREDITOR TYPE /BI0/OICREDITOR
        SOURCE_FIELDS-DEBITOR TYPE /BI0/OIDEBITOR
        SOURCE_FIELDS-PLANT TYPE /BI0/OIPLANT
        SOURCE_FIELDS-MATERIAL TYPE /BI0/OIMATERIAL
        SOURCE_FIELDS-EMPLOYEE TYPE /BI0/OIEMPLOYEE
        SOURCE_FIELDS-NOTIFICATN TYPE /BI0/OINOTIFICATN
        SOURCE_FIELDS-CO_ITEM_TX TYPE /BI0/OICO_ITEM_TX
        SOURCE_FIELDS-DOC_DATE TYPE /BI0/OIDOC_DATE
        SOURCE_FIELDS-PSTNG_DATE TYPE /BI0/OIPSTNG_DATE
        SOURCE_FIELDS-RECORDMODE TYPE RODMUPDMOD
        SOURCE_FIELDS-CORRTYPE TYPE /BI0/OICORRTYPE
        SOURCE_FIELDS-CCTR_IBV TYPE /BI0/OICCTR_IBV
        SOURCE_FIELDS-FM_AREA TYPE /BI0/OIFM_AREA
        SOURCE_FIELDS-FUND TYPE /BI0/OIFUND
        SOURCE_FIELDS-GRANT_NBR TYPE /BI0/OIGRANT_NBR
        SOURCE_FIELDS-PFUND TYPE /BI0/OIPFUND
        SOURCE_FIELDS-PGRANT_NBR TYPE /BI0/OIPGRANT_NBR
        SOURCE_FIELDS-PU_BDGTID TYPE /BI0/OIPU_BDGTID
        SOURCE_FIELDS-PBDGTID TYPE /BI0/OIPBDGTID
       EXPORTING
         RESULT type tys_TG_1-CO_REPLINE
        DATA:
          MONITOR_REC    TYPE rsmonitor.
    $$ begin of routine - insert your code only below this line        -
      Data:
        COMM_STRUCTURE   type tys_SC_1_full,
        l_subrc          type sy-tabix,
        l_abort          type sy-tabix,
        ls_monitor       TYPE rsmonitor,
        ls_monitor_recno TYPE rsmonitors.
      data:
        l_monitor        type standard table of rsmonitor.
      REFRESH:
        MONITOR.

    How have you solved? I have also error for 0vtype.
    Thanks!

  • Infopackage routine for changing  file name

    Hi Everyone,
                               I have to load flat files from application server directories. I get these files from different locations and they are saved in own (location) folders by a script). I would like to run these file from infopackage through process chain. the problem is that these files have changing names. The format is like this
    Canada_co3300.csv
    I can write a routine is my infopackage but  "co3300" keeps changing as it represents different companies code in that particular location (Canada).
      I have a routine
    data: F1 type string value 'D:\usr\sap\FLAT_FILES\Inbound\Cayman\Canada_<b>co3300</b>_',
    F2 type string '.csv'.
    concatenate f1 f2 into p_filename.
      How can I get a variable <b>co</b>---- in my routine so my infopackage can read the file if <b>co</b> has different value like co2000. Thanks In advance.
    Regards,
    Asad

    Hi Saugata,
                           My flat file name has a naming convention based on company code in application server folder, so I get files with name
                                               Canadaco<b>3000</b>.csv  or
                                               Canadaco<b>2000</b>.csv or
                                               Canadaco<b>4000</b>.csv or something else <b>(co</b> number keeps changing)
    So My file name keeps changing all the time. I would like my infopackage to read these files automatically thorugh a routine or logical file name. I have tried both, but donot know how to configure this scenerio thorugh my infopackage. Please give me steps to use that table you mentioned. Thanks .

Maybe you are looking for