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.

Similar Messages

  • 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

  • Syntax Error in Routine while Activating Transformation

    Dear All,
    I am activating whole scenario for 0SD_C03. we have made transformation for 2lis_11_vaitm, during installation we get below errors:
    - Rule (target: 0SUBTOT_1S, group: 01 Standard Group): Syntax error in routine
    -Rule (target: 0NET_VAL_S, group: 01 Standard Group): Syntax error in routine
    -Rule (target: 0PROD_CATEG, group: 01 Standard Group): Syntax error in routine
    I really appreciate your any input for this.
    Thanks & Regards,
    Darshan

    Hi,
    I hope there is inbalance in between SOURCE Datapackage and Target Datapackage. So in the start routines pls check it and it not found then add in DATA_PACKAGE...
    Check with ABAPer
    under ,
    TYPES:
          BEGIN OF tys_TG_1_full,
            SUBTOT_1S           TYPE /BI0/OISUBTOT_1S,
    and also you can fin dsimilar kind of threads in SDN.
    Re: Syntax Error in Routine while Activating Transformation
    Re: Issue while creating Transformation from Update rule.
    Re: 0IC_C03 activation of Transformation rule ends with ERROR
    Re: Error in activation of transformation
    Thanks
    Reddy

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

  • Syntax Error while activating 2LIS_04_P_ARBPL Transformation

    Dear all,
    While activating  2LIS_04_P_ARBPL Transformation activation , I am facing following  error while checking in Routine
    E:Field "COMM_STRUCTURE-TGTPROCCAP" is unknown. It is neither in one of
    the specified tables nor defined by a "DATA" statement. "DATA"
    statement.
    please help me out for this
    Edited by: tjoshi1982 on May 19, 2011 7:11 PM

    Following are error that comes after checking routine
    0TGTPROCCAP     -
        E:Field "COMM_STRUCTURE-TGTPROCCAP" is unknown. It is neither in one of
    the specified tables nor defined by a "DATA" statement. "DATA" statement.
    0TGTSETPCAP      -
    E:Field "COMM_STRUCTURE-TGTPROCCAP" is unknown. It is neither in one of
    the specified tables nor defined by a "DATA" statement. "DATA"statement.
    0TGTTEARCAP    -
    E:Field "COMM_STRUCTURE-TGTPROCCAP" is unknown. It is neither in one of
    the specified tables nor defined by a "DATA" statement. "DATA" statement.
    please tell me what to do next,as  i already tried to assign source field

  • 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

    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

  • Data Source 0HR_PA_0 Syntax Error in the start routine while activating

    Hi All,
    I have migrated the Business content for the data source 0HR_PA_0
    While activating the transformation-2 there is errors like:
    Start Routine: Syntax error in routine
    Rule (target: 0HDCNT_LAST, group: 01 Standard Group): Syntax error in routine
    Rule (target: 0AGE_KYF, group: 01 Standard Group): Syntax error in routine
    .................... etc
    I need help to resolve this issue.
    Thanks & Regards,
    Savitha

    Hello Jurgita,
    When Data Source was migrated the codes related to COMM_STRUCTURE was missing in the start routinue.
    Following codes (in bold) with regard to COMM_STRUCTURE added and then got activated
    4.     *--
    5.         COMM_STRUCTURE   type tys_sc_1__rule_25,
    6.         l_subrc          type sy-tabix,
    7.         l_abort          type sy-tabix,
    8.         ls_monitor       TYPE rsmonitor,
    9.         ls_monitor_recno TYPE rsmonitors.
    10.     
    11.       REFRESH:
    12.         MONITOR.
    13.     
    14.     * Runtime attributs
    15.         SOURCE_SYSTEM  = p_r_request->get_logsys( ).
    16.         move-corresponding SOURCE_FIELDS to COMM_STRUCTURE.
    17.     
    18.     *  Migrated update rule call
    19.       Perform routine_0011
    20.       using
    21.         COMM_STRUCTURE
    22.       CHANGING
    Regards,
    Savitha
    Edited by: Savitha  Ravi on Jun 19, 2009 6:34 AM

  • 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

  • Getting syntax error while executing keyfigure routine BI 7.0

    Hello,
    I am writing a very simple keyfigure routine to calculate sales revune using sales quantity and sales price, I am getting error as follows
    - I am in 'Rules Details' screen and I have selected 'Routine' as the rule type. I enter the following code in routine
         RESULT = SOURCE_FIELDS_RULE-/BIC/IO_VB_QU *
         SOURCE_FIELDS_RULE-/BIC/IO_VB_PRC .
    - I hit the check button on the routine page, it says no syntax errors
    - Now I am back in the 'Rules Details' page and I hit the 'Check' button it gives me the following error
    Rule(target IO_VB_REV, group: Standard Group): Syntax error in routine
    Please tell me what is wrong. what should i check

    Hi Vaibhav,
    Here are the details
    - I am loading data from flatfile to an Infocube with 3 keyfigures: IO_VB_PRC (Sales Price) , IO_VB_QU (Sales Quantity), IO_VB_REV (Sales Revune). Getting values for IO_VB_QU and IO_Vb_PRC from flatfile and calculating for IO_VB_REV using routine
    - I created Transformations, and under  Rule Group: Standard Group box I see 'X' sign against 'IO_VB_REV' field, meaning not mapped to any datasource 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.
    - I specify 'USD' as the Conversion Type and then click on check button it initially gives me 'Incorrect Input'  written in an information message box and then error that Syntax error in routine
    Let me know what is that I am missing
    Thanks for helping

  • Transport Error. Sintax error in routine.

    Hi all,
    I'm facing an error and I would like to receive some help.
    I'm trying to transport a transformation of BI7.0 from development to quality environment and I'm receiving this error:
    Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (activation mode)
    Transformation 0375K6W8L81KCGPGVDUBF7P9Y1O9AZEL deleted in version M of DDIC
    Activation of Transformation type object
    Transformation 0375K6W8L81KCGPGVDUBF7P9Y1O9AZEL
    Rule (target: ZIMPPRESU, group: 01 Grupo estándar): Syntax error in routine
    Transformation  : Rule 13 could not be imported
    I've checked the routine and no sintax errors are found. It works perfectly in dev.
    I found a similar post in sdn:
    And I followed the steps I found in it. I recollected the tranformation objects in the transport connection and no objects were missing.
    In RSLOGSYSMAP table I have one record and the ONLYNEW field is empty. I don't know if it's ok or not but it's not the first time I have transported this transformation.
    Can anyone help me in resolving this issue?
    Thanks, points will be assigned.

    hi,
    We faced a similar problem last week...
    Check the routine first ...There might not be a syntax error but maybe you are using the routine to fetch data from someother ODS or infocube or using an infoobject which might not have been transported...
    In our case, we were fetching data from another ODS using this routine and had not transported that ODS, thats why we faced this problem...
    Some object required for the routine to work fine, has not been transported, thats why its showing this error......
    Regards,

  • Routine's Error After Migration BW to BI

    *HI,*
    *I have migrated 2lis_13_vditm data source from bw to bi and now issue is when i try to activate transformation it is showing error*
    "RULE(TARGET 0SUBTOT_1S,GROUP 01 STANDARD GROUP): SYNTAX ERROR IN ROUTINE". ***
    " ERROR WHEN I CHECK FOR SYNTAX CONSISTENCY "* it is showing**
    *E:THE DATA OBJECT "AOMM_STRUCTURE" DOES NOT HAVE A COMPONENT CALLED*
    *"NETVAL_IN"*

    Make sure you have the latest SP for CR 2008  installed;
    https://smpdl.sap-ag.de/~sapidp/012002523100009038092009E/cr2008win_sp2.exe
    Ensure you are deploying SP 2 runtime;
    MSM
    https://smpdl.sap-ag.de/~sapidp/012002523100009159092009E/cr2008sp2_mm.zip
    MSI
    https://smpdl.sap-ag.de/~sapidp/012002523100009159002009E/cr2008sp2_redistinstall.zip
    If that does not help;
    1) Do these reports work in the designer?
    2) What database are you using and what is the connection type?
    3) Compare the dlls loading on the systems where this app works (environment which has both Crystal Reports 10 and Crystal Reports 12 in GAC) and a system that is giving you the error. Use the [Modules|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] utility.
    4) Open the reports in the designer and look at the properties in the Database menu -> Set Datasource Location. Check to see if there are any differences between the two reports.
    5) If there is a subreport in the report that causes the issue, remove it and see if the report works without the subreport.
    Ludek

  • Error in transporting the Transformation to Quality system

    Hi All,
    I am trying to transport the transformation which has field level routine as well as start and end routine.
    I have basically ehanced the standard routine and it works perfectly fine in dev server . I have even loaded the data and generated reports on this cube.
    Now i am trying to transport it to Quality system. It throws up some "syntax error in routine" error. Very strange.
    All my routine in Dev is working but during transport ther is some issue.
    i saw some post on same but they are suggesting to regenerate a new transformation. For me this will be a nightmare as there are so many routnies at field level and as end routine.
    Kindly suggest how can i rectify this error.
    Note:- I had generated this transformation via old update rules with Migration function.
    Thanks & Regards,
    Anup

    Hi Anindya,
    Below is my source code for one field level routine in transformation.
    FORM routine_0080
      TABLES
       p_monitor         STRUCTURE rsmonitor
      USING
        COMM_STRUCTURE TYPE _ty_s_sc_1__rule_52
      CHANGING
        RESULT         TYPE _ty_s_tg_1_full-srvclen
        RETURNCODE     LIKE sy-subrc
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
    * init variables
    * fill the internal table "MONITOR", to make monitor entries
      DATA: ultimo LIKE sy-datum.
      IF g_record_no <> RECORD_NO.
        g_record_no = RECORD_NO.
        CLEAR: employee_wa, person_wa.
        CLEAR: employee_md, person_md.
      ENDIF.
      PERFORM read_md_employee
              USING    COMM_STRUCTURE-employee
                       COMM_STRUCTURE-calday
                       RECORD_NO
                       RECORD_ALL
                       SOURCE_SYSTEM
              CHANGING employee_wa
                       RETURNCODE.
      employee_md = employee_wa.
      PERFORM calculate_ultimo
              USING COMM_STRUCTURE-calday+0(6)
                     RECORD_NO
                     RECORD_ALL
                     SOURCE_SYSTEM
              CHANGING ultimo
                       RETURNCODE.
      IF NOT employee_md-entrydate IS INITIAL.
        RESULT = ultimo+0(4) - employee_md-entrydate+0(4).
        IF ultimo+4(4) LT employee_md-entrydate+4(4).
          RESULT = RESULT - 1.
        ENDIF.
      ENDIF.
    * result value of the routine
    * if the returncode is not equal zero, the result will not be updated
      RETURNCODE = 0.
    * if abort is not equal zero, the update process will be canceled
      ABORT = 0.
      p_monitor[] = MONITOR[].
      CLEAR:
        MONITOR[].
    CLASS lcl_transform IMPLEMENTATION.
      METHOD compute_0AGE_RANGE.
    *   IMPORTING
    *     request     type rsrequest
    *     datapackid  type rsdatapid
    *     SOURCE_FIELDS-CALDAY TYPE /BI0/OICALDAY
    *     SOURCE_FIELDS-EMPLOYEE TYPE /BI0/OIEMPLOYEE
    *    EXPORTING
    *      RESULT type _ty_s_TG_1-AGE_RANGE
        DATA:
          MONITOR_REC    TYPE rsmonitor.
    *$*$ begin of routine - insert your code only below this line        *-*
      Data:
        COMM_STRUCTURE   type _ty_s_SC_1__RULE_20,
        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.
    * Runtime attributs
        SOURCE_SYSTEM  = p_r_request->get_logsys( ).
        MOVE-CORRESPONDING SOURCE_FIELDS to COMM_STRUCTURE.
    *  Migrated update rule call
      Perform routine_0070
      TABLES
        l_monitor
      USING
        COMM_STRUCTURE
      CHANGING
        RESULT
        l_subrc
        l_abort.
    *-- Convert Messages in Transformation format
        LOOP AT l_monitor INTO ls_monitor.
          move-CORRESPONDING ls_monitor to MONITOR_REC.
          append monitor_rec to MONITOR.
        ENDLOOP.
        IF l_subrc <> 0.
          RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
        ENDIF.
        IF l_abort <> 0.
          RAISE EXCEPTION TYPE CX_RSROUT_ABORT.
        ENDIF.
    I am not able to change the code which are marked with " * ". Where can i change the code here?
    Regards,
    Anup

  • Error in BI at Transformation after migration from BW Rule (target :ZDTAPAK

    Hello Gurus,
    I have migrated datasource from BW to BI. The update rule from BW  against transformation in BI has routine.
    I see an error messgae in "Transformation Display"(screen). error msg is
      Rule (target :ZDTAPAKID, group:01 standard Group): syntax error in routine
      Rule (target :ZRECNM, group:01 standard Group): syntax error in routine
      Rule (target :ZRECORDID, group:01 standard Group): syntax error in routine
    Rule (target :ZREQUID, group:01 standard Group): syntax error in routine
    when I double click on field/ Rule Name : ZDTAPAKID,ZRECNM,ZRECORDID & ZREQUID on all the four   field / rule name and go to Rule Details  and against Rule Type : Routine , go to Display Rule  and land in Rule Details .
    There is see routine isa defined, when I  check the syntax of routine I get following error .
    E:Field "G_S_MINFO-DATAPAKID" is unknown. It is neither in one of the
    specified tables nor defined by a "DATA" statement. "DATA" statement
    Note: I get same error for all the 4 fields/rule name  when I try to check the syntax ZDTAPAKID,ZRECNM,ZRECORDID & ZREQUID
    can any one please guide me?
    Thank you
    Ashwaq

    hi check note Note 1052648 - Migrating transfer rules and update rules for BW7.x
    otherwise try to declare the fields in your generated coding
    for example
    TYPE-POOLS: RSSM.
    DATA :
    G_S_MINFO TYPE RSSM_S_MINFO,
    ZDTAPAKID TYPE RSDATAPID,
    ZRECNM TYPE rssm_s_minfo-requnr,
    ZREQUID TYPE RSREQUEST.
    Bye
    Boujema

  • 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

Maybe you are looking for