Syntax error in Transfer routine

Hai all,
           I am trying to write a routine for an object in the datasource trasnfer structure. I am getting a error. The code and the error as as follows.
DATA: l_s_errorlog TYPE rssm_s_errorlog_int.
SELECT SINGLE * FROM /BI0/PCOMP_CODE
    WHERE COMP_CODE     = TRAN_STRUCTURE-BUKRS AND
          OBJVERS       = 'A'.
  IF SY-SUBRC           = 0.
     RESULT = /BI0/PCOMP_CODE-CHRT_ACCTS.
  ENDIF.
returncode <> 0 means skip this record
  RETURNCODE = 0.
abort <> 0 means skip whole data package !!!
  ABORT = 0.
The error message I am getting is
"E:A target area must be declared either explicitly with an INTO clause or implicitly with a TABLES statement."
            The cursor is going to the line " SELECT SINGLE *.....". 
         I guess its pointing where the mistake is. It says the target must be specified. But I already specified the target.
I appreciate any kind of help.
Thanks a lot.

Hi,
You didn't provide a INTO class for the select statement.
DATA : BEGIN OF LCL_COMPCODE.
DATA : INCLUDE STRUCTURE /BI0/PCOMP_CODE.
DATA : END OF LCL_COMPCODE.
SELECT SINGLE * FROM /BI0/PCOMP_CODE
WHERE COMP_CODE = TRAN_STRUCTURE-BUKRS AND
OBJVERS = 'A'
INTO LCL_COMPCODE.
Loop at the LCL_COMPCODE to retrieve the data.
Thank you
Arun

Similar Messages

  • Error while transporting Transformation: Syntax error in Start Routine

    Hi Everyone,
    I'm facing a strange problem during transporting one of the Business Content cubes from Dev. to Quality.
    I'd activated the DSO 'Purchase Order Items (0PUR_O01)' and its entire data flow from the 4 datasources 2LIS_02_CGR, 2LIS_02_SCN, 2LIS_02_SGR, and 2LIS_02_ITM from BC. Then I migrated the Transfer/Update rules to transformations and the DataSources to BI7 DataSource. So far so good. The migration was successful and all the objects were activated.
    Now when I transport the same to Quality, the import fails with return code 8 and the error message says:
    'Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Activation Mode)'
    'Start Routine: Syntax error in routine'
    I verified that the transformation where the error orrured was the one from InfoSource Z2LIS_02_ITM to DSO 0PUR_O01. I went and checked the start routine and it did indeed have a syntax error:
    'In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter SOURCE_PACKAGE" is incompatible with the formal parameter DATA_PACKAGE". '
    But when I check in the Dev. system, there is no syntax error for the same routine. Later, I tried to transport only the said transformation by re-activating it in Dev, and again I got the same error.
    I have no idea why I'm getting a syntax error in the start routine when there are non in the Dev. system. Also none of the coding is customised, it was only the BC code, migrated to a transformation.
    Any suggestions on the steps I could take to transport the transformation to my quality system?
    Thanks,
    Ram

    Hi Ajay, Shanthi, svu and Ray
    I do indeed have a start routine in my transformation and it was migrated from a 3.x update rule to a BI 7 transformation routine.
    The migration was successful and the Start Routine has NO syntax errors in the start routine in the Dev. system. I only encounter the error while transporting it to the Quality system. I cannot modify the code in the Quality system because it is non-changelable and there is no point in trying to change the code in Dev. because there are no errors over there.
    I've also made sure that I've transported all the necessary objects required by the transformations to quality. The routine does not perform a lookup, it simply deletes some records from the data package based on the processkey value (which is itself present in the data package).

  • Syntax error in Start Routine routine 9998 in transformation

    Hi Guyz,
    I am getting the below error while doinf the syntax check in start routine in one of the transformation in BW production after the failed TR movement
    E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter
    "SOURCE_PACKAGE" is incompatible with the formal parameter
    "DATA_PACKAGE".
    but for the same transformation in quality its showing  no syntax errors found.
    its an odd behaviour.
    please guide with ur expertise.
    cheerz,
    raps.

    Hi,
    Check the note 1052648. it says that:
    Start routine:
               In the start routine, all the fields from the source are always available.
    During the migration, a type '_ty_t_SC_1_full' is generated in '2nd part global'. Since Note 1325124, this type has been adjusted when the field list is changed. In the past, a change to the field list caused syntax errors of the type:
    For update rules:
                        E: For PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter "SOURCE_PACKAGE" is not compatible with the formal parameter "DATA_PACKAGE".
    For transfer rules:
                        E:For PERFORM or CALL FUNCTION "STARTROUTINE", the actual parameter "SOURCE_PACKAGE" is not compatible with the formal parameter "DATAPAK".
               If this error continues to occur, go to the solution section to correct it.
               Solution:
               This error should now be automatically corrected with Note 1325124. Access the incorrect start routine in change mode. The type '_ty_s_SC_1_full' is then automatically adjusted to the source structure. If this does not work, you should use the tool 'RSTRAN_MIGRATION_CHECK' (described in Note 1369395) to check and possibly repair the transformation in question.
               If this error still occurs, you can correct it manually as follows:
               Copy the field list of the type     '_ty_s_SC_1' from the 'private section' of the CLASS lcl_transform DEFINITION (you can find this when you scroll up in the routine editor of the start routine) to the type '_ty_s_SC_1_full' of '2nd part global'.
    Regards,
    Anil Kumar Sharma .P

  • Syntax error in Transformation routine

    Hi Folks,
    We are In SP 17.
    I have migrated standard 0bpartner_attr transfer rules to a transformation with syntax errors.
    I have a routine for a gender, Valid From and Valid To its giving the following erorr.
    E:Field "TRAN_STRUCTURE-VALID_FROM" is unknown. It is neither in one of
    the specified tables nor defined by a "DATA" statement. "DATA"
    statement.
    the following is the routine code for Gender.
    PROGRAM trans_routine.
          CLASS routine DEFINITION
    CLASS lcl_transform DEFINITION.
      PUBLIC SECTION.
    Attributs
        DATA:
          p_check_master_data_exist
                TYPE RSODSOCHECKONLY READ-ONLY,
    *-    Instance for getting request runtime attributs;
        Available information: Refer to methods of
        interface 'if_rsbk_request_admintab_view'
          p_r_request
                TYPE REF TO if_rsbk_request_admintab_view READ-ONLY.
      PRIVATE SECTION.
        TYPE-POOLS: rsd, rstr.
      Rule specific types
        TYPES:
          BEGIN OF tys_SC_1,
         Field: XSEXM Male.
            XSEXM           TYPE C LENGTH 1,
         Field: XSEXF Female.
            XSEXF           TYPE C LENGTH 1,
         Field: XSEXU Unknown.
            XSEXU           TYPE C LENGTH 1,
         Field: RECORD.
            RECORD           TYPE RSARECORD,
          END   OF tys_SC_1.
        TYPES:
          BEGIN OF tys_TG_1,
         InfoObject: 0GENDER Gender.
            GENDER           TYPE /BI0/OIGENDER,
          END   OF tys_TG_1.
    $$ begin of global - insert your declaration only below this line  -
    ... "insert your code here
    $$ end of global - insert your declaration only before this line   -
        METHODS
          compute_0GENDER
            IMPORTING
              request                  type rsrequest
              datapackid               type rsdatapid
              SOURCE_FIELDS              type tys_SC_1
            EXPORTING
              RESULT                   type tys_TG_1-GENDER
              monitor                  type rstr_ty_t_monitor
            RAISING
              cx_rsrout_abort
              cx_rsrout_skip_record
              cx_rsrout_skip_val.
        METHODS
          invert_0GENDER
            IMPORTING
              i_th_fields_outbound         TYPE rstran_t_field_inv
              i_r_selset_outbound          TYPE REF TO cl_rsmds_set
              i_is_main_selection          TYPE rs_bool
              i_r_selset_outbound_complete TYPE REF TO cl_rsmds_set
              i_r_universe_inbound         TYPE REF TO cl_rsmds_universe
            CHANGING
              c_th_fields_inbound          TYPE rstran_t_field_inv
              c_r_selset_inbound           TYPE REF TO cl_rsmds_set
              c_exact                      TYPE rs_bool.
    ENDCLASS.                    "routine DEFINITION
    $$ begin of 2nd part global - insert your code only below this line  *
    $$ end of rule type
        TYPES:
          BEGIN OF tys_TG_1_full,
         InfoObject: 0BPARTNER Business Partner.
            BPARTNER           TYPE /BI0/OIBPARTNER,
         InfoObject: 0BP_ACTITL1 First Academic Title.
            BP_ACTITL1           TYPE /BI0/OIBP_ACTITL1,
         InfoObject: 0BP_ACTITL2 Second Academic Title.
            BP_ACTITL2           TYPE /BI0/OIBP_ACTITL2,
         InfoObject: 0BP_BTHNAME BP: Person's Name at Birth.
            BP_BTHNAME           TYPE /BI0/OIBP_BTHNAME,
         InfoObject: 0BP_CAT Business Partner Category.
            BP_CAT           TYPE /BI0/OIBP_CAT,
         InfoObject: 0BP_CONS Business Partner (Consolidated/Cleansing).
            BP_CONS           TYPE /BI0/OIBP_CONS,
         InfoObject: 0BP_CONTACT BP: Contact Permission.
            BP_CONTACT           TYPE /BI0/OIBP_CONTACT,
         InfoObject: 0BP_EXTERN BP Number in External System.
            BP_EXTERN           TYPE /BI0/OIBP_EXTERN,
         InfoObject: 0BP_FSTNAME BP: Person's First Name.
            BP_FSTNAME           TYPE /BI0/OIBP_FSTNAME,
         InfoObject: 0BP_GROUP Business Partner Grouping.
            BP_GROUP           TYPE /BI0/OIBP_GROUP,
         InfoObject: 0BP_GRPNAM1 BP: Name 1 (Group).
            BP_GRPNAM1           TYPE /BI0/OIBP_GRPNAM1,
         InfoObject: 0BP_GRPNAM2 BP: Name 2 (Group).
            BP_GRPNAM2           TYPE /BI0/OIBP_GRPNAM2,
         InfoObject: 0BP_GRPTYPE BP: Group Type.
            BP_GRPTYPE           TYPE /BI0/OIBP_GRPTYPE,
         InfoObject: 0BP_LSTNAME BP: Person's Surname.
            BP_LSTNAME           TYPE /BI0/OIBP_LSTNAME,
         InfoObject: 0BP_MAR_STA BP: Marital Status.
            BP_MAR_STA           TYPE /BI0/OIBP_MAR_STA,
         InfoObject: 0BP_MDLNAME BP: Person's Middle Name or Second First
    *Name.
            BP_MDLNAME           TYPE /BI0/OIBP_MDLNAME,
         InfoObject: 0BP_SECNAME BP: Person's Second Surname.
            BP_SECNAME           TYPE /BI0/OIBP_SECNAME,
         InfoObject: 0CHANGEDBY Changed by.
            CHANGEDBY           TYPE /BI0/OICHANGEDBY,
         InfoObject: 0CH_AT Time of Last Change.
            CH_AT           TYPE /BI0/OICH_AT,
         InfoObject: 0CH_ON Last changed on.
            CH_ON           TYPE /BI0/OICH_ON,
         InfoObject: 0CREATEDBY Name of person who created the object.
            CREATEDBY           TYPE /BI0/OICREATEDBY,
         InfoObject: 0CREATEDON Date on which the record was created.
            CREATEDON           TYPE /BI0/OICREATEDON,
         InfoObject: 0CREA_TIME Time Created.
            CREA_TIME           TYPE /BI0/OICREA_TIME,
         InfoObject: 0GENDER Gender.
            GENDER           TYPE /BI0/OIGENDER,
         InfoObject: 0LEGALFORM Legal Status of Organization.
            LEGALFORM           TYPE /BI0/OILEGALFORM,
         InfoObject: 0NAME_ORG1 BP: Organization Name 1.
            NAME_ORG1           TYPE /BI0/OINAME_ORG1,
         InfoObject: 0NAME_ORG2 BP: Organization Name 2.
            NAME_ORG2           TYPE /BI0/OINAME_ORG2,
         InfoObject: 0NAME_ORG3 BP: Organization Name 3.
            NAME_ORG3           TYPE /BI0/OINAME_ORG3,
         InfoObject: 0NAME_ORG4 BP: Organization Name 4.
            NAME_ORG4           TYPE /BI0/OINAME_ORG4,
         InfoObject: 0NATION Nationality.
            NATION           TYPE /BI0/OINATION,
         InfoObject: 0TITLE_SPPL Name Supplement, for example, Noble Title
            TITLE_SPPL           TYPE /BI0/OITITLE_SPPL,
         InfoObject: 0BP_TYPE Partner:Partner Type.
            BP_TYPE           TYPE /BI0/OIBP_TYPE,
         InfoObject: 0GN_PAR_SSY Source System of a Partner.
            GN_PAR_SSY           TYPE /BI0/OIGN_PAR_SSY,
         InfoObject: 0LOGSYS Source System.
            LOGSYS           TYPE RSDLOGSYS,
         InfoObject: 0RECORDMODE BW Delta Process: Record Mode.
            RECORDMODE           TYPE RODMUPDMOD,
         InfoObject: 0BP_GUID GUID of Business Partner.
            BP_GUID           TYPE /BI0/OIBP_GUID,
         InfoObject: 0BPDATEFROM GP Attributes Valid from.
            BPDATEFROM           TYPE /BI0/OIBPDATEFROM,
         InfoObject: 0BPDATETO GP Attributes Valid to.
            BPDATETO           TYPE /BI0/OIBPDATETO,
         Field: RECORD Data record number.
            RECORD           TYPE RSARECORD,
          END   OF tys_TG_1_full.
    Additional declaration for transfer rule interface
      DATA:
        g_t_errorlog TYPE rssm_t_errorlog_int,
        RECORD_ALL   LIKE SY-TABIX.
    global definitions from transfer rules
    DATA: gs_cob_pro TYPE rsd_s_cob_pro,
          gt_viobj   TYPE rsd_t_viobj,
          gs_viobj   TYPE rsd_s_viobj.
    DATA:   l_s_errorlog TYPE rssm_s_errorlog_int,
            l_text TYPE string.
    FORM compute_BPDATEFROM
       CHANGING
        RESULT         TYPE tys_TG_1_full-BPDATEFROM
        RETURNCODE     LIKE sy-subrc
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
      INCLUDE rs_bct_bupa_form_valid_from.
    ENDFORM.                    "BPDATEFROM
    FORM compute_BPDATETO
       CHANGING
        RESULT         TYPE tys_TG_1_full-BPDATETO
        RETURNCODE     LIKE sy-subrc
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
      INCLUDE rs_bct_bupa_form_valid_to.
    ENDFORM.                    "BPDATETO
    FORM compute_GENDER
       CHANGING
        RESULT         TYPE tys_TG_1_full-GENDER
        RETURNCODE     LIKE sy-subrc
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
    INCLUDE rs_bct_bupa_form_gender.
    ENDFORM.                    "GENDER
    FORM compute_GN_PAR_SSY
       CHANGING
        RESULT         TYPE tys_TG_1_full-GN_PAR_SSY
        RETURNCODE     LIKE sy-subrc
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
    INCLUDE rs_bct_bupa_form_gn_par_ssy.
    ENDFORM.                    "GN_PAR_SSY
    $$ end of 2nd part global - insert your code only before this line   *
          CLASS routine IMPLEMENTATION
    CLASS lcl_transform IMPLEMENTATION.
      METHOD compute_0GENDER.
      IMPORTING
        request     type rsrequest
        datapackid  type rsdatapid
        SOURCE_FIELDS-XSEXM TYPE C LENGTH 000001
        SOURCE_FIELDS-XSEXF TYPE C LENGTH 000001
        SOURCE_FIELDS-XSEXU TYPE C LENGTH 000001
       EXPORTING
         RESULT type tys_TG_1-GENDER
        DATA:
          MONITOR_REC    TYPE rsmonitor.
    *$*$ begin of routine - insert your code only below this line        *-*
      Data:
        l_s_error_log    type rssm_s_errorlog_int,
        l_subrc          type sy-tabix,
        l_abort          type sy-tabix,
        ls_monitor       TYPE rsmonitor,
        ls_monitor_recno TYPE rsmonitors.
    REFRESH:
      monitor,
      monitor_recno.
    Migrated transfer rule call
      Perform compute_GENDER
        CHANGING
          RESULT
          l_subrc
          l_abort.
    *-- Convert Messages in Transformation format
        LOOP AT G_T_ERRORLOG INTO l_s_error_log.
          move-CORRESPONDING l_s_error_log to MONITOR_REC.
          append monitor_rec to MONITOR.
        ENDLOOP.
        IF l_subrc <> 0.
          RAISE EXCEPTION TYPE cx_rsrout_skip_val.
        ENDIF.
        IF l_abort <> 0.
          RAISE EXCEPTION TYPE CX_RSROUT_ABORT.
        ENDIF.
    $$ end of routine - insert your code only before this line         -
      ENDMETHOD.                    "compute_0GENDER
          Method invert_0GENDER
          This subroutine needs to be implemented only for direct access
          (for better performance) and for the Report/Report Interface
          (drill through).
          The inverse routine should transform a projection and
          a selection for the target to a projection and a selection
          for the source, respectively.
          If the implementation remains empty all fields are filled and
          all values are selected.
      METHOD invert_0GENDER.
    $$ begin of inverse routine - insert your code only below this line-
    ... "insert your code here
    $$ end of inverse routine - insert your code only before this line -
      ENDMETHOD.                    "invert_0GENDER
    ENDCLASS.                    "routine IMPLEMENTATION
    let me know how to correct the above code.
    thanks

    Hi,
    the field tran_structure is no more available. The name changed to source_fields. Additionally there is no datapak available. It is now source_fields_table. You might need to use field symbols to access the fields.
    regards
    Siggi

  • Errors in Transfer Routine for 0MATERIAL_ATTR

    I created a transfer routine on the 0Material_attr upload that needs to populate an attribute called Z_CPFX.
    Problem is, I need to look at the material number, material group, and the Material Description, and then populate the result based on what I find.
    I am new to using ABAP in these routines, so any help would be appreciated.  I will award points.
    The error I keep getting is E:Field "TRAN_STRUCTURE-MATNR" unknown.
    Could somebody take a look at my ABAP and advise what I'm doing wrong?
    Thank you.
    Ken
    $$ begin of routine - insert your code only below this line        -
    DATA: l_s_errorlog TYPE rssm_s_errorlog_int.
      DATA:   X_DESCRIPTION TYPE TABLE OF /BI0/TMATERIAL.       " KC01
        select  *
              into CORRESPONDING FIELDS of Table X_DESCRIPTION
             from /BI0/TMATERIAL
            where tran_structure-matnr = /BI0/TMATERIAL-matnr.
      IF MATKL between 765 and 770.
        RESULT = 'MAPOO'.
      ELSEIF MATNR(1) = 'X'.
        RESULT = 'MAPOO'.
      ELSEIF MATNR(1) <> 'X'.
        AND (MATKL = '750'
              OR MATKL = '751'
              or MATKL = '755'
        RESULT = 'MAPWK'.
      ELSEIF
        (MATKL = '756'
        or MATKL = '760'
        or MATKL = '761'
        and X_DESCRIPTION-TXTMD co 'renew'.
        RESULT = 'MAPRK'.
      ELSEIF
      (MATKL = '756'
      or MATKL = '760'
      or MATKL = '761'
      and X_DESCRIPTION-TXTMD !co 'renew'.
        RESULT = 'MAPMM'.
      ELSE.
        RESULT = space.
      ENDIF.
    returncode <> 0 means skip this record
      RETURNCODE = 0.
    abort <> 0 means skip whole data package !!!
      ABORT = 0.
    $$ end of routine - insert your code only before this line         -
    ENDFORM.

    Hi Kenneth,
    /BI0/TMATERIAL is the text table for 0material. If you are trying to get all the data from text table, please correct your select statement as below (text table does not contain the attributes. you might need to chenge the selection table to its attribute tables):
    select *
    into CORRESPONDING FIELDS of Table X_DESCRIPTION
    from /BI0/TMATERIAL
    where tran_structure-matnr = /BI0/TMATERIAL-MATERIAL.
    I also see that some of your syntaxes are wrong:
    eg: IF MATKL between 765 and 770. ==>
    IF( ( MATKL > 765 ) and ( MATKL < 770 ) ).
    Please look into the syntaxes of other statements as well.

  • Syntax error in start routine

    Dear All,
    I have activated the infocube 0sd_c03 with grouping "in data flow before" and the infocube is activated with datasources
    2LIS_11_VAITM
    2LIS_11_VAHDR
    2LIS_12_VCITM
    2LIS_12_VCHDR
    2LIS_13_VDITM
    2LIS_13_VDHDR in 3.x where as
    TRCS 2LIS_13_VDITM -> CUBE 0SD_C03 in transformation with DTP.
    when I activate the transformation I get error as mentioned below:
    Start Routine: Syntax error in routine and in the start routine when I check the details of the error is
                      E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter
                               "SOURCE_PACKAGE" is incompatible with the formal parameter
                                   "DATA_PACKAGE".
    If source pakage is replaced by data package the system message is data_package is not available.
    What do I do to resolve this issue.
    KS

    hi,
    There is a structral diffrence between SOURCE_PACKAGE and DATA_PACKAGE
    so you need to change tys_SC_1_full
    go through the below links for similar problem
    Re: 0IC_C03: 2LIS_03_BF Transformation Start Routine Activation error
    Re: 2LIS_03_BF transformation problem

  • Syntax error in Update Routine

    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 defining a variable of type  tys_TG_1-/BIC/ZGROSSPRI.
    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.
    Below given is the code which I am using for the same. Kindly advise how to correct this error.
    Moderator message - Please respect the 2,500 character maximum when posting. Post only the relevant portions of code
    Edited by: Suneeth Sebastian on Apr 7, 2010 4:11 PM
    Edited by: Rob Burbank on Apr 7, 2010 1:19 PM

    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.

  • Syntax error in Transfer strcutre activation

    Friends,
    Unable to activate SD Master Data DataSource
    When we tried to activate master data datasource transfer structure we are facing following error,
    Syntax error in GP_ERR_RSAPTM2, row 24 (-> long text)
    Message no. RG102
    Diagnosis
    The type "WITH" is unknown.
    please help us in this regard with your inputs
    Thanks in advance,
    Soujanya

    Hi Soujanya,
    please check OSS note #755677. This is the only problem known to us in this area. If this does not succeed, please create a customer problem message.
      Cheers
         SAP NetWeaver BI Organisation

  • Undue Syntax error in transformation routine

    Hi,
    A routine is reported to be incorrect (error RSTRAN 523)  during the check of the transformation. However, a check on the source code in the editor returns no errors.
    I've implemented the oss note 980548, but I still face the problem.
    Do you have any idea of how to solve this issue ?
    Thanks in advance !
    Dieu

    Hi Dieu,
    I had a problem related to a Transfer Roule for the selection of the same filed in Start Routine and single filed routine.
    Check if you are obtaining two InfoObjects from the same field and check the corresponding routines.
    Ciao.
    Riccardo.

  • Syntax error during transport on valid transfer routines

    Dear All,
    We have some routines in a tranfer structure that are valid and working just fine in DEV.  But when we transport them to QA we get the following error message :-
    Start of the after-import method for object type R3TR ISTS (Activation Mode)                
    Transfer structure 6DB_V_BW_EPISODE_AD activated under the name 6DB_V_BW_EPISODE_AD         
    It is not necessary to copy dependent objects for transfer structure 6DB_V_BW_EPISODE_AD    
    Syntax error in transfer routine for InfoObject OPEN_DAT                                    
    Activating Transfer Rules 6DB_V_BW_EPISODE_AD ...                                           
    47 Transfer Rule(s) of the transfer structure 6DB_V_BW_EPISODE_AD removed from control table
    53 InfoObject(s) of the transfer structure 6DB_V_BW_EPISODE_AD removed from control table   
    Formulas have been saved                                                                    
    Syntax error in transfer routine for InfoObject OPEN_DAT
    If we remove all the routines the activation works just fine even though our routines are valid and working just fine in DEV.
    Can anyone explain this as this is becoming quite urgent now ?
    Thanks in advance.
    Craig

    Hi Oliver
    I work with Craig. In response to your question, what he means is that all objects independantly have been transported ok, apart from the transfer rules. If you look at the table RSTSRULES you will see a column called CONVROUT_L.
    In our Dev system this field contains the BW generated rule code. Eg.
    45GEGC5I66GA9Z5G4KFDDRIK4 against the Transfer structure. When the after import process runs, it uses the contents of this table together with the contents of the RSAABAP table which contains the code and creates the transfer rule program.
    In RSAABAP we have the following code for CODEID '45GEGC5I66GA9Z5G4KFDDRIK4'
    DATA: l_s_errorlog TYPE rssm_s_errorlog_int.
    CHECK NOT &TS&-opened_date IS INITIAL.
    IF &TS&-opened_date < '19000101'.
    &RS& = '19900101'.
    ELSEIF &TS&-opened_date > '29990101'.
    &RS& = '19900101'.
    ELSE.
    &RS& = &TS&-opened_date.
    ENDIF.
    returncode <> 0 means skip this record
    &RE& = 0.
    abort <> 0 means skip whole data package !!!
    &AB& = 0.
    In our QA system the column is blank because of the wierd Syntax problem when generating the program, therefore the transfer rules dont get activated.
    As you can see there is no problem with the ABAP.
    Regards
    Mark

  • Syntax error  while executing Key Figure routine

    Hello,
    I am posting my question again, as I have not got any solution. Please help it will be really appreciated. Here's the description
    I am loading data from flatfile to an Infocube with 3 keyfigures: Sales Price , Sales Quantity, Sales Revune. Getting values for Sales Price and Salea Quantity  from flatfile and calculating for Sales Revunue IO_VB_REV using routine
    - I created Transformations, and under Rule Group: Standard Group box I have not mapped IO_VB_REV  any datasource field and see 'X' sign against the field.
    - In rules detail screen, I add two source fields of Rule , IO_VB_QU and IO_VB_PRC. I see IO_VB_REV already added under 'Target fields of Rule' section
    - I then add the only following line to routine
    RESULT = SOURCE_FIELDS_RULE-/BIC/IO_VB_QU * SOURCE_FIELDS_RULE-/BIC/IO_VB_PRC .
    - Clicking on check button it gives no syntax error message. I save and exit back to Rule Details page.
    - For IO_VB_REV field If I select any of 2 options i.e. Fixed Unit or No conversion it gives me a dump. So I select 'from conversion' option. In that case I enter USD against 'Conversion Type' field. It gives me information box popup with 'Incorrect Input Message'
    - When check button hit on 'Rule Details' page, it gives me error message ' Syntax error in routine '
    Why is it giving me syntax error, inspite of the fact that I get 'no syntax error' message on routine page. Also why am I getting short dumps on changing Conversion Type

    Hi Olivier,
    I really thank you for ur efforts in helping me solving this problem. Below is complete description of KF defined,
    1. Created InfoObjects for Sales Quantity, Sales Price, Sales Revunue
    Definition of <b>Sales Quantity</b>
    Name: IO_VB_QU
    Type/Data Type : Quantity
    Data Type: QUAN - Quantity field, points to unit field with format UN
    Currency / unit of measure
    Unit / Currency: 0UNIT
    Definition of <b>Sales Price</b>
    Name: IO_VB_PRC
    Type/Data Type : Amount
    Data Type: CURR - Currency field, stored as DEC
    Currency / unit of measure
    Fixed Currency: USD
    Definition of <b>Sales Revunue</b>
    Name: IO_VB_REV
    Type/Data Type : Amount
    Data Type: CURR - Currency field, stored as DEC
    Currency / unit of measure
    Fixed Currency: USD
    2. As the data is being read from flatfile, created DataSource with fields for Sales ID, Sales Price, Sales Quantity. As I am reading unit for quantity from file (has values EA,BOX,CSE), I have a corresponding field UNIT in DataSource. No field for Sales Revunue.
    3. I use 'Create Transformation' functionality to automatically create transformations.
    4. Rule Details page of each of 3 KFs has following values
    <b>Rule Details page of Sales Quantity</b>
    Rule Type: Direct Assignment
    Aggregation : Summation
    Target Unit: 0UNIT
    Unit: from Source
    Source Unit: UNIT
    Source Fields of Rule: /BIC/IO_VB_QU, UNIT
    Target Fields of Rule: 0UNIT, IO_VB_QU
    <b>Rule Details page of Sales Price</b>
    Rule Type: Direct Assignment
    Aggregation : Maximum
    Fixed Target Currency : USD
    Currency: No Conversion
    Source Fields of Rule: /BIC/IO_VB_PRC
    Target Fields of Rule:  IO_VB_PRC
    <b>Rule Details page of Sales Revunue</b>
    Rule Type: Routine   
    Aggregation : Summation
    Fixed Target Currency : USD
    Currency: from Conversion
    Conversion Type: ??????.....(I entered USD it gives me Incorrect Input message)
    Source Fields of Rule: /BIC/IO_VB_PRC, /BIC/IO_VB_QU, UNIT
    Target Fields of Rule:  IO_VB_REV
    I have this line is the routine 
    RESULT = SOURCE_FIELDS_RULE-/BIC/IO_VB_QU *   SOURCE_FIELDS_RULE-/BIC/IO_VB_PRC.
    Let me know if u need any other info......
    I really appreciate u trying  to help me
    Vidya

  • ABAP SYNTAX ERROR IN STANDARD SAP TRANSFORMATION

    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".

    Hi,
    Please check routine if any for 0CO_REPLINE and also expert routine.
    Regards,
    Rema.

  • 0LOGSYS transfer routine error transporting DEV- QA

    Hello!
    I need to transport several business content infocubes and loading flow(migrated from 3x to in 7.0) from DEV to QA.
    In QA I've imported also infoobject 0LOGSYS and his transfer routine. But it appears iinactive. When I display the transfer routine from characteristic 0LOGSYS, is missing this part of code::
      IF RESULT IS INITIAL     and
         IOBJ_NAME = '0LOGSYS'.
    fill source system
        RESULT = SOURCE_SYSTEM.
    What can I do ?  In DEV, the code is ok. Can I modify it manually ? Other what must I do in DEV to repair it?
    Thanks a lot !

    I need to activate the object 0LOGSYS from Business Content again ? or manually with change and also change and save the routine?
    In STMS I have:
    Start of the after-import method RS_IOBJ AFTERIMPORT for object type IOBJ
    Syntax error Incorrect statement :Expression missing . in row 20 position 0
    Characteristic 0LOGSYS: Error when activating or checking the transfer routine
    This infoobject, 0LOGSYS is also attribute for others infoobjects and I have also errors like:
    Attribute 0LOGSYS from characteristic 0BUS_AREA is not actively available.
    I've imported also a data source 3x migrated to 7.0 with the transformation and an infocube, and I have error:
    Start of the after-import method RS_RSDS AFTERIIMPORT for object type RSDS
    Soource system DEV does not exist
    Start of the after-import method RS_TRFN_AFTER_IMPORT  fot object type TRFN
    No rule exists.
    Source RSDS mysource DEV does not exist
    AND SUMMARy:
    Object  IOBJ 0logsys imported with errors
    Thanks!

  • Start Routine: Syntax error in routine 2LIS_03_BF Transformations

    Hi experts,
    I enhanced the 2lis_03_bf data source, and replicated the data source in bw system, i have mapped the transformations and when i try to activate the transformations it is giving the below error.
    Start Routine: Syntax error in routine
    when i check the start routine it is giving the  below error message.
    E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter
    "SOURCE_PACKAGE" is incompatible with the formal parameter
    "DATA_PACKAGE".
    please provide me the solution.
    Regards
    venuscm

    Hi Venu,
    This seems to me like you have earlier migrated the update rules to transformations. We did the same earlier and faced issues whenever we add new fields/infoobjects. The error message was different, if i remember correctly.
    We had to add the new field/infoobject added, to the structure '_ty_s_*****' that exists at the top of the start routine code. This was one disadvantage of migration of rules.

  • Syntax error in routine

    Hi Gurus,
        I have added new fields in ODS  and Cube.While activating transformation I am getting the following error : 'Start routine:Syntax error in routine'Please let me know how to trouble shoot the same.
    Regards
    Hasini

    Hi Pallavi,
    Pls gothroug the Routine:
    MONITOR_RECNO.
    Runtime attributs
        SOURCE_SYSTEM  = p_r_request->get_logsys( ).
    Migrated update rule call
      Perform routine_9998
      TABLES
        SOURCE_PACKAGE
      CHANGING
        l_abort.
    *-- Convert Messages in Transformation format
        LOOP AT MONITOR_RECNO INTO ls_monitor_recno.
          move-CORRESPONDING ls_monitor_recno to MONITOR_REC.
          append monitor_rec to MONITOR.
        ENDLOOP.
        LOOP AT MONITOR INTO ls_monitor.
          move-CORRESPONDING ls_monitor to MONITOR_REC.
          append monitor_rec to MONITOR.
        ENDLOOP.
        IF l_abort <> 0.
          RAISE EXCEPTION TYPE CX_RSROUT_ABORT.
        ENDIF.
    $$ end of routine - insert your code only before this line         -
      ENDMETHOD.                    "start_routine
          Method inverse_start_routine
    E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter
    SOURCE_PACKAGE" is incompatible with the formal parameter
    "DATA_PACKAGE".
    Regards
    Hasini

Maybe you are looking for

  • Mail - Forwarding attachments manually and with rules - how do I keep my attachments?

    I have the latest updates of Lion on by MacBookPro (late 2010 model). I use mail to receive mail from my business account (Exchange account) and my personal account (IMAP account). Up until this summer, everything was working peachy with the system.

  • How do I create a song in key of Ab Minor

    Is it possible to create a song in garageband in Aflat minor? If so, how? Thanks Kate

  • Screen Refresh

    So in the most basic (first exercise) jsp, it works fine, but; if I open another instance of IE and then return to the �localhost�page (*.jsp) clicking the submit button causes the page to refresh to default values. It also takes 10-15 seconds for th

  • Should Fuse for OS X be on my new Retina iMac?

    After migrating files, folders, setting and apps from my old 2009 iMac (currently running OS X 10.10 Yosemite) to my new Retina iMac (27", Retina 5K, OS X Yosemite) I notice that there is a Fuse for OS X (Oxyfuse) preference pane in the System Prefer

  • Print tiff format

    Hi guys, I'm trying to print a tiff format image, I can print gif formats, but if the image is tiff, it doesnt print, on my researchs I saw that is not so simple as I'd like it to be, so if anyone here has done it before, print tiff images, pls send