Start/End routine code to delete last 5 characters

Hi All,
          I have a field 15 CHAR in length in my data source. The first 10 characters are always numbers followed by a hyphen(-) and 4 more numbers.
I want to store this into my DSO as a 10 character field containing just the first 10 numbers and drop the last 5 characters. Can anyone suggest me the routine for this?
Thanks!
Missy

Hi Missy,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/609eea32-455e-2c10-c08a-c23adf8c934e?quicklink=index&overridelayout=true
Have a look to above docs link.
I hope, it will help you alot!!!
Thanks,
Ajay

Similar Messages

  • End Routine Code not Working after Support Pack Upgrade

    Hi BI Community,
    We have recently upgraded to SPS17 (BW SP19) for our production system and the code deriving the values of several attributes in the end routine of the transformation for one InfoObject (as info provider) does not work anymore. We have been trying to identify the root cause but the fact is that we did not change anything to the InfoObject and its transformation and this used to work fine. The strange thing is that when we debugged the code we could see the value of the aforementioned attributes was derived correctly but the value is just not updated to the InfoObject where we still see the old values for these attributes.
    We have a similar InfoObject with the same end routine code in the transformation and it is working fine. We are out of idea what could have caused this during the SP upgrade.
    Thanks in advance for your feedback.
    Regards,
    Peter

    Cannot say what might have caused it but one check you can perform.
    Open your transformation in change mode and you can see a button next to create end routine button, titled ' Update Behavior of End Routine Change', click on that and say all fields.
    Hope it helps...
    Regards,
    Ashish

  • Finding the simulation mode in start/end routine

    Hi ,
    I am also updating some other tables in my transformation apart from the actual target infoprovider data.
    But I would like to update those other tables only when the DTP is actually run and don't want to update when DTP is run in simulation mode.
    Is there any way in the start/end routine to find whether the DTP execution is simulation or Real?
    Regards,
    Ramesh

    Hi,
    This is not possible in the start routine as this check is done even before reaching the start routine by using the method :
    if_rsbk_dtp_maintain~set_simulation
    -Vikram

  • Primitive APAB editor in start/end routines in transformations

    When editing or viewing ABAP code in BI transformations, for example in a start routine, the editor that opens is very primitive compared to the normal SE38 editor. Some of the limitations include:
    The editor window doesn't cover the whole screen with seemingly no way to increase its size.
    The syntax check doesn't show on which line syntax errors are located.
    There is no option to perform a extended program check.
    There is no way to insert break-points (other than with the ABAP keyword of course)
    These limitations are present regardless of whether i choose the new front-end editor, the old front-end editor or the back-end editor. We're running SAP Netweaver 2004s.
    It is of course possible to create a program in SE38 and copy-paste your start routine code to see the code using the "real" editor, but this is very tiresome and time consuming. Is there a way to make this editor look and behave like the normal editor? I have looked through the setting options an searched SDN without finding a way.

    Hi,
    This is just the settings you need to change to open the start,end, and characteristics routine using the old editor you are comfortable with. No need to go to se38 and check copy the program.
    Go to se38->Utilities->settings->abap editor->editor tab->select the old abap editor.
    To specifically put break point in transformations (start routine..end routine..)..goto transformation (RSA1) and then display the transformation.
    Then goto extra (menu)->generated program. search for start_routine (method now) and put break point in the desired place.
    Then from the DTP enable all 4 break points..in tranformation (this will come when u cange it to debug mode simulation). And u can debug the transformation.
    The new editor is a good handy one. But take some time to get acquented to it. After you may start liking it :).
    Cheers,
    -J

  • Check if a DSO has been lookup by other DSO/cube in start/end routine

    I have to support on of the client system which I am not part of the development.
    I found one DSO has been schedule to load data in daily process chain but it is not update to any target.
    Is it possible to check if this DSO has been using in the staging  i.e look up the reference field by other cube/DSO in start or end routine ?

    Hi,
    Possible by invoking respective field into code part.
    I think not much stuff required in this regard.
    Thanks - RK

  • Thumbrule for Start/End Routines Usage

    Friends,
                 Is there any thumb rule to decide when to use start or end routine in BW 7 in transformations ?  Can anybody provide a scenario for demonstration .. from performing simple lookups on different DSOs to get descriptions vs any other specific scenarios..   Is there any scenario in which only start or only end routine can be performed.. ?
    Any thoughts would be great..?
    thanks,
    Sunil

    Start routine is totally concerned with source data , where you need to write logic for source_package.
    Start routine will execute before transformation execution.
    Executes packageby package.
    loop at source_package into source-feilds.
    End routine works on target structure  and we have lo write logic on result_package.
    Genarally dso lookups are concerned with end routines.
    loop at result_package into result-feilds.
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/609eea32-455e-2c10-c08a-c23adf8c934e
    http://forums.sdn.sap.com/thread.jspa?threadID=1963087
    Regards,
    rvc

  • Start & End Routines in BI 7  Transformations

    Hi,
    In Transformations from DSO1-->DSO2
    In Start Routine for all entries in Source Package i read some fields from DSO3 and filled an iternal table
    And  in end routine i read the iternal table and filled the result package/fields
    In the mapping i haven't mapped any thing to the fields to which i intended to fill using routines
    When i executed data load those fields are not populated with any value
    But if i debug the transformation...results are updating in all fields in the  result package.......
    Do i need to make any setting or mappings to the fields which i want to update using end routine
    Thanks

    HI,
    For support pack 16 and above you get one more button besides End Routine (once end routine is created).
    This button is to update behaviour of fields in End Routines. You get two options once you select this button. One needs to make selection of proper option as it is mandatory.
    The default setting for the pushbutton is that only the fields with active rules are updated in the transformation. With this selection, fields populated in End routine wont be updated in the data target if no active rule exists for them in Transformation.
    Alternatively, you can define that all the fields should always be updated by selecting 2nd radio button. As a result, fields filled in the end routine are not lost if there is no other active rule.
    So in your case if you are in SP 15 or lower, then you will have to map the fields.
    Go through this article it gives the above explanation along with screenshots.
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/30d35342-1fe3-2c10-70ba-ad0da83d23bd
    Hope this helps.
    Thanks,
    Rahul

  • Start routine code for deleting records in different language

    Hello,
    can someone please specify the exact code to be used in start routine, and whre exactly it needs to be pasted?
    this code is needed for master data notifaction type which is loaded for both languages German and English.
    german records are to be avoided.
    thanks,

    Ciao Claudio,
    this issue about languages selection is an old situation...
    The problem is that language selection is not possible, even if you have this field checked for selection !!!
    Look at OSS Note 324684...
    "If a field of a DataSource - typically with field name 'LANGU' or 'SPRAS' - is assigned to InfoObject '0langu', the field is not provided in the selection fields although the field actually can be selected. In this case, all languages of the language vector active in the BW System are requested by the source system but the language selection cannot be defined in the Scheduler.
    A precondition is that the language field of the DataSource in the source system is maintained as selection field. This setting is done in Transaction RSA6 (or RSO2 for customer developments)."
    Bye,
    Roberto

  • Start - end routine modeling

    Hello experts,
    I have a fairly large source package 3 million lines. From that one line that starts with a specific patern for example date* has the date of the file.
    I need that date in order to use it at the transformation.
    The problem is that i cannot know in which package the system will find that date.
    So even if i find it with abap at the start routine, the packages before that will not have that date which i need.
    Any thoughts?
    Thanks
    Yannis

    Hi Yannis,
    here's an idea that allows you to stay in BW.
    1) Load your file into a new DSO or new InfoObject. In the start routine you delete all lines except the one of the 3 million that you need first.
    2)Then as a second step you load the same file into your main target and you use a lookup into the new DSO to get the date you are after.
    If you use the same datasource for both you can even use the same PSA. Use a Process Chain to make sure step 1 is executed before step 2 is started.
    Best,
    Ralf

  • End routine to fill 0PROFIT_CTR

    Hi experts,
    i am uploading data from DSO TO INFO CUBE. where some of the customers are assigned to PROFIT CENTER in ECC which is coming to DSO and INFO CUBE perfectly, but most of the customers are not assigned to PROFIT CENTER but assigned to SALES DISTRICT.
    so whenever the PROFIT CENTER is blank I need to fill the SALES DISTRICT values for the PROFIT CENTER.
    from DSO to CUBE profit center is direct mapping, so i want to write a end routine to fill the values of PROFIT CENTER where PROFIT CENTER is Blank.
    here is the default code in the end routine
    TYPES:
          BEGIN OF _ty_s_TG_1,
    *      InfoObject: 0FISCPER Fiscal year / period.
            FISCPER           TYPE /BI0/OIFISCPER,
    *      InfoObject: 0FISCVARNT Fiscal year variant.
            FISCVARNT           TYPE /BI0/OIFISCVARNT,
    *      InfoObject: 0LOC_CURRCY Local currency.
            LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
    *      InfoObject: 0DOC_CURRCY Document currency.
            DOC_CURRCY           TYPE /BI0/OIDOC_CURRCY,
    *      InfoObject: 0CLEAR_DATE Clearing date.
            CLEAR_DATE           TYPE /BI0/OICLEAR_DATE,
    *      InfoObject: 0AC_DOC_TYP Document type.
            AC_DOC_TYP           TYPE /BI0/OIAC_DOC_TYP,
    *      InfoObject: 0DOC_DATE Document Date.
            DOC_DATE           TYPE /BI0/OIDOC_DATE,
    *      InfoObject: 0POST_KEY Posting key.
            POST_KEY           TYPE /BI0/OIPOST_KEY,
    *      InfoObject: 0COMP_CODE Company code.
            COMP_CODE           TYPE /BI0/OICOMP_CODE,
    *      InfoObject: 0GL_ACCOUNT G/L Account.
            GL_ACCOUNT           TYPE /BI0/OIGL_ACCOUNT,
    *      InfoObject: 0C_CTR_AREA Credit Control Area.
            C_CTR_AREA           TYPE /BI0/OIC_CTR_AREA,
    *      InfoObject: 0DUNN_AREA Dunning Area.
            DUNN_AREA           TYPE /BI0/OIDUNN_AREA,
    *      InfoObject: 0LAST_DUNN Date of last dunning notice.
            LAST_DUNN           TYPE /BI0/OILAST_DUNN,
    *      InfoObject: 0DUNN_BLOCK Dunning block.
            DUNN_BLOCK           TYPE /BI0/OIDUNN_BLOCK,
    *      InfoObject: 0DUNN_LEVEL Dunning level.
            DUNN_LEVEL           TYPE /BI0/OIDUNN_LEVEL,
    *      InfoObject: 0DUNN_KEY Dunning key.
            DUNN_KEY           TYPE /BI0/OIDUNN_KEY,
    *      InfoObject: 0NETDUEDATE Due date for net payment.
            NETDUEDATE           TYPE /BI0/OINETDUEDATE,
    *      InfoObject: 0REASON_CDE Difference Reason for Payments.
            REASON_CDE           TYPE /BI0/OIREASON_CDE,
    *      InfoObject: 0DSCT_DATE1 Due date for cash discount 1.
            DSCT_DATE1           TYPE /BI0/OIDSCT_DATE1,
    *      InfoObject: 0DSCT_DATE2 Due date for cash discount 2.
            DSCT_DATE2           TYPE /BI0/OIDSCT_DATE2,
    *      InfoObject: 0SP_GL_IND Special General Ledger Indicator.
            SP_GL_IND           TYPE /BI0/OISP_GL_IND,
    *      InfoObject: 0BLINE_DATE Baseline Date For Due Date Calculation.
            BLINE_DATE           TYPE /BI0/OIBLINE_DATE,
    *      InfoObject: 0PYMT_METH Payment method.
            PYMT_METH           TYPE /BI0/OIPYMT_METH,
    *      InfoObject: 0PMNT_BLOCK Payment block key.
            PMNT_BLOCK           TYPE /BI0/OIPMNT_BLOCK,
    *      InfoObject: 0PMNTTRMS Terms of Payment Key.
            PMNTTRMS           TYPE /BI0/OIPMNTTRMS,
    *      InfoObject: 0CHRT_ACCTS Chart of accounts.
            CHRT_ACCTS           TYPE /BI0/OICHRT_ACCTS,
    *      InfoObject: 0ACCT_TYPE Account type.
            ACCT_TYPE           TYPE /BI0/OIACCT_TYPE,
    *      InfoObject: 0COUNTRY Country Key.
            COUNTRY           TYPE /BI0/OICOUNTRY,
    *      InfoObject: 0DEBITOR Customer Number.
            DEBITOR           TYPE /BI0/OIDEBITOR,
    *      InfoObject: 0FI_DOCSTAT Item Status.
            FI_DOCSTAT           TYPE /BI0/OIFI_DOCSTAT,
    *      InfoObject: 0FI_SUBSID Account Number of the Branch.
            FI_SUBSID           TYPE /BI0/OIFI_SUBSID,
    *      InfoObject: 0PSTNG_DATE Posting date in the document.
            PSTNG_DATE           TYPE /BI0/OIPSTNG_DATE,
    *      InfoObject: 0DEB_CRE_LC Amount in Local Currency with +/- Signs.
            DEB_CRE_LC           TYPE /BI0/OIDEB_CRE_LC,
    *      InfoObject: 0DISC_BASE Amount eligible for cash discount in docum
    *ent currency.
            DISC_BASE           TYPE /BI0/OIDISC_BASE,
    *      InfoObject: 0DSC_AMT_LC Cash discount amount in local currency.
            DSC_AMT_LC           TYPE /BI0/OIDSC_AMT_LC,
    *      InfoObject: 0DEB_CRE_DC Foreign currency amount with signs (+/-).
            DEB_CRE_DC           TYPE /BI0/OIDEB_CRE_DC,
    *      InfoObject: 0DSC_AMT_DC Cash discount amount in document currency
            DSC_AMT_DC           TYPE /BI0/OIDSC_AMT_DC,
    *      InfoObject: 0CREDIT_DC Credit amount in foreign currency.
            CREDIT_DC           TYPE /BI0/OICREDIT_DC,
    *      InfoObject: 0CREDIT_LC Credit amount in local currency.
            CREDIT_LC           TYPE /BI0/OICREDIT_LC,
    *      InfoObject: 0DEBIT_DC Debit amount in foreign currency.
            DEBIT_DC           TYPE /BI0/OIDEBIT_DC,
    *      InfoObject: 0DEBIT_LC Debit amount in local currency.
            DEBIT_LC           TYPE /BI0/OIDEBIT_LC,
    *      InfoObject: 0NETTAKEN Net period used.
            NETTAKEN           TYPE /BI0/OINETTAKEN,
    *      InfoObject: 0INT_CALC_1 Interest Calculation Numerator Days 1 (Ag
    *reed).
            INT_CALC_1           TYPE /BI0/OIINT_CALC_1,
    *      InfoObject: 0INT_CALC_2 Interest calculation numerator days 2 (ag
    *reed).
            INT_CALC_2           TYPE /BI0/OIINT_CALC_2,
    *      InfoObject: 0INT_CALC_N Interest Calculation Numerator Net (Agree
    *d).
            INT_CALC_N           TYPE /BI0/OIINT_CALC_N,
    *      InfoObject: 0INT_CALCT1 Interest Calculation Numerator Days 1 (Re
    *alized).
            INT_CALCT1           TYPE /BI0/OIINT_CALCT1,
    *      InfoObject: 0INT_CALCT2 Interest Calculation Numerator Days 2 (Re
    *alized).
            INT_CALCT2           TYPE /BI0/OIINT_CALCT2,
    *      InfoObject: 0INT_CALCTN Interest Calculation Numerator Net (Reali
    *zed).
            INT_CALCTN           TYPE /BI0/OIINT_CALCTN,
    *      InfoObject: ZPART_FUN Partner Function.
            /BIC/ZPART_FUN           TYPE /BIC/OIZPART_FUN,
    *      InfoObject: ZAC_CLERK Accounting Clerk.
            /BIC/ZAC_CLERK           TYPE /BIC/OIZAC_CLERK,
    *      InfoObject: 0PROFIT_CTR Profit Center.
            PROFIT_CTR           TYPE /BI0/OIPROFIT_CTR,
    *      InfoObject: 0SALES_DIST Sales District.
            SALES_DIST           TYPE /BI0/OISALES_DIST,
    *      InfoObject: 0SALES_OFF Sales Office.
            SALES_OFF           TYPE /BI0/OISALES_OFF,
    *      InfoObject: 0SALES_GRP Sales group.
            SALES_GRP           TYPE /BI0/OISALES_GRP,
    *      InfoObject: 0RATING Rating.
            RATING           TYPE /BI0/OIRATING,
    *      InfoObject: 0CO_AREA Controlling area.
            CO_AREA           TYPE /BI0/OICO_AREA,
    *      InfoObject: ZAM_INSUR Amount Insured.
            /BIC/ZAM_INSUR           TYPE /BIC/OIZAM_INSUR,
    *      InfoObject: 0CURRENCY Currency key.
            CURRENCY           TYPE /BI0/OICURRENCY,
    *      InfoObject: 0CRED_LIMIT Customer's Credit Limit.
            CRED_LIMIT           TYPE /BI0/OICRED_LIMIT,
    *      InfoObject: 0RISK_CATEG Credit Management: Risk Class for New Cus
    *tomer.
            RISK_CATEG           TYPE /BI0/OIRISK_CATEG,
    *      InfoObject: 0CLR_DOC_NO Clearing Document Number.
            CLR_DOC_NO           TYPE /BI0/OICLR_DOC_NO,
    *      InfoObject: 0REF_DOC_NO Reference document number.
            REF_DOC_NO           TYPE /BI0/OIREF_DOC_NO,
    *      InfoObject: 0INV_DOC_NO Invoice Number.
            INV_DOC_NO           TYPE /BI0/OIINV_DOC_NO,
    *      InfoObject: 0DOC_NUMBER Sales document.
            DOC_NUMBER           TYPE /BI0/OIDOC_NUMBER,
    *      Field: RECORD.
            RECORD           TYPE RSARECORD,
          END   OF _ty_s_TG_1.
        TYPES:
          _ty_t_TG_1        TYPE STANDARD TABLE OF _ty_s_TG_1
                            WITH NON-UNIQUE DEFAULT KEY.
    *$*$ 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
          new_record__end_routine
            IMPORTING
              source_segid             type rstran_segid
              source_record            type sytabix
            EXPORTING
              record_new               type sytabix.
        METHODS
          end_routine
            IMPORTING
              request                  type rsrequest
              datapackid               type rsdatapid
            EXPORTING
              monitor                  type rstr_ty_t_monitors
            CHANGING
              RESULT_PACKAGE              type _ty_t_TG_1
            RAISING
              cx_rsrout_abort.
        METHODS
          inverse_end_routine
            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
    Pleae provide me the end routine code.
    regards
    venuscm
    Edited by: venugopal vadlamudi on Sep 7, 2010 1:14 PM
    Edited by: venugopal vadlamudi on Sep 7, 2010 1:15 PM

    hi experts,
    i have written the end routine
    if not RESULT_PACKAGE is INITIAL.
      LOOP AT RESULT_PACKAGE ASSIGNING <RESULT_FIELDS>.
        IF <RESULT_FIELDS>-PROFIT_CTR IS INITIAL .
          <RESULT_FIELDS>-PROFIT_CTR = <RESULT_FIELDS>-SALES_DIST.
          MODIFY RESULT_PACKAGE FROM <RESULT_FIELDS>.
        ENDIF.
      ENDLOOP.
    endif.
    but while doing DTP from DSO to CUBE it is giving following error.
    Characteristic value '1000 ' of characteristic 0PROFIT_CTR is not ALPHA -converted.
    0PROFIT_CTR info object is ALPHA Converted while 0SALES_DISTRICT is not.
    pl provide me the solution
    regards
    venuscm
    Edited by: venugopal vadlamudi on Sep 7, 2010 2:55 PM

  • How to delete data from a DSO using start or end routine

    Is it possible to delete records from a DSO in the start or end routine.
    My example:  I have order 123, item 10, sched line 1.  This gets loaded into the DSO.
    Next day I have order 123, item 10, sched line 2 coming in.
    I want to delete the first one (with sched line 1) from the DSO and load the second one (with sched line 2).
    Can code be put in the start or end routine to do this?

    unless I can do it within the start routine I don't want to have to create new records.
    In the start routine I am comparing records coming in with what are already in the DSO.  If there is a match on order and item and the sched line is different, then I want to delete the record from the DSO and load the new one.  Is there code that I can put in a start routine to accomplish this?

  • Delete code in End Routine.

    Hi Experts,
    I have to write a delete code in end routine. I giving it below. Kindly correct for mistakes.
    Delete data_package where zquantity = 0 and zorder = 0.
    I find after putting this code it tells that Data_Package is not available.
    What to put then?
    Kindly help me.
    Thanks in advance,
    With Kind Regards,
    Kannan

    Hi
    There is no Data_package in end routine. you can use that only in start routine.
    Use Result_package in end routine.
    Thanks
    Jay.

  • How to add new records in Start routine or end routine.

    Hi All,
            My requirement is to transfer data from one DSO to anothe DSO. But while transfering a single record frorm DSO1 i want to add 7 records to DSO2 for each record in DSO1 with slight change in data( with a different key). I want to do it in start routine or end routine. How can i do it. If you have any ABAP code for this then please send.
    Regards
    Amlan

    you can use this code, replace the fields where i have marked with <>.
    DATA : WA_RESULT_PACKAGE TYPE DSO2,
           WA_RESULT_PACKAGE1 LIKE WA_RESULT_PACKAGE.
    DATA : IT_RESULT_PACKAGE LIKE TABLE OF WA_RESULT_PACKAGE.
    DATA : DATE1 TYPE SY-DATUM.
    DATA : DAYDIFF TYPE i.
    DATA : RECORD_NO type rsarecord.
    SORT RESULT_PACKAGE BY <KEY FIELDS> "specify the key fields here
    RECORD_NO = 1.
    LOOP AT RESULT_PACKAGE INTO WA_RESULT_PACKAGE.
         IF WA_RESULT_PACKAGE_1-<KEYFIELDS> NE WA_RESULT_PACKAGE-<KEYFIELDS>.
              WA_RESULT_PACKAGE_1 = WA_RESULT_PACKAGE.
              DAYDIFF = WA_RESULT_PACKAGE-ENDDATE - WA_RESULT_PACKAGE-STARTDATE.
                   WHILE DAYDIFF NE 0.
                        DATE1 = WA_RESULT_PACKAGE-STARTDATE + DAYDIFF.
                        MOVE DATE1 TO WA_RESULT_PACKAGE-<KEYFIELDDATE>.
                        MOVE RECORD_NO TO WA_RESULT_PACKAGE-RECORD.
                        APPEND WA_RESULT_PACKAGE INTO IT_RESULT_PACKAGE.
                        DAYDIFF = DAYDIFF - 1.
                        RECORD_NO = RECORD_NO + 1.
                        CLEAR DATE1.
                   ENDWHILE.
              CLEAR DAYDIFF.
         ENDIF.
    ENDLOOP.
    DELETE RESULT_PACKAGE[].
    RESULT_PACKAGE[] = IT_RESULT_PACKAGE[].
    Reg Point 3.
    The Key figures will then show up in the report aggregated.Hope that is fine with you.
    Note:
    Before loading data, in DTP set the semantic key with the key field of the DSO1.This brings all the similar data w.r.t the key fields from the PSA together in a single package.
    rgds, Ghuru

  • What are start and end routines in BI 7.0..

    Hi,
    Can you please explain and give me a sample code ?
    thanks

    Hi,
    depending on your data flow you have to use the routines .
    Start routines - start routines:
    It is used to perform preliminary calculations.if you have any modifications required before the actual transformation is done, then you must write those routines in the start routine of 7.0.
    End routines - new:
    You can use an end routine to postprocess data after transformation on a package-by-package basis.
    Expert routine - update routine :
    You can use the expert routine if there are not sufficient functions to perform a transformation. The expert routine should be used as an interim solution until the necessary functions are available in the standard routine. You can use this to program the transformation yourself without using the available rule types. If you have already created transformation rules, the system deletes them once you have created an expert routine.
    Also Check the below link for detail info.
    Routine in Transformation.
    Reg
    Pra

  • Start And End Routine !

    Hi All,
                  In BI 7 we have a start routine and end routine. In end routine we delete all the transformed records that need not be updated to the infocube. Which we can also do it in the start routine. In that case Y do we need a End routine.
    Regards.

    Hi,
    1. Start Routine : whenever you create a start routine, the system will automatically give you some predefined data declaration like structure of the type of your source. In start routine you can declare a local data declaration and Global data declaration also. I will give one example.
    Suppose you are creating Start routine for transformation from Datasource to DSO. Then when you create start routine the System will provide you a structure of your datasource. By using this structure it will also define an internal table which will be used as changing parameter of a method of a class. It is this changing parameter where you have to do all sorts of manipulation. The changing parameter is both export as well as import parameter. This changing parameter will contain data in the package wise.
    In start routine you can also read some database table and store that data into an internal table and this internal table data can then be read in the field level routine. In this case it acts as a substitute of master data look up in the field level transformation.
    2. End routine : The end routine is also same as start routine, the only difference is that here the system will provide you with a structure of the target not the source. and rest is all same as start routine.
    assign points if it helps
    Thanks & Regards
    santo

Maybe you are looking for