End routine field not populated

Hi,
I have made the following end routine in order to populate the field YNEGOCIO with two characters.
I´m uploading data from DSO 0FIAR_O03 to customized DSO.  When i activate this DSO i don´t see the field YNEGOCIO populated but the strange thing is that when i make a debbugg to the end routine,  the result package-YNEGOCIO at the end of routine IS POPULATED with the correct values.
Can anybody help me with this?
LOOP AT RESULT_PACKAGE INTO e_s_result.
**Recover characters 14,15 from YNEGOCIO.
CLEAR lv_negocio.
           SELECT SINGLE
             /BIC/YYKEY
            FROM /BIC/AYSDLASPV00
            INTO lv_key
                WHERE
                  /BIC/YYVALUE EQ e_s_result-GL_ACCOUNT.
            IF sy-subrc EQ 0.
              MOVE lv_key+13(2) TO lv_negocio.
            ENDIF.
      LOOP AT gt_inv_gl9_doc INTO gs_inv_gl8_doc
        WHERE ac_doc_no = e_s_result-ac_doc_no.
* Calculate Importe Aplicado
        MOVE e_s_result to aux_s_result.
         aux_s_result-record = v_count + 1.
        IF aux_s_result-DEB_CRE_DC IS NOT INITIAL.
          aux_s_result-PROFIT_CTR = gs_inv_gl8_doc-profit_ctr.
          aux_s_result-USERNAME = gs_inv_gl8_doc-USERNAME.
          aux_s_result-deb_cre_dc = gs_inv_gl8_doc-DEB_CRE_DC.
          aux_s_result-/BIC/YI_WRBTR = gs_inv_gl8_doc-DEB_CRE_DC *
            aux_s_result-/BIC/YI_WRBTR / aux_s_result-DEB_CRE_DC.
          aux_s_result-/BIC/YNEGOCIO = lv_negocio.
          APPEND aux_s_result to e_t_result.
        ENDIF.
      endloop.
    endloop.
    REFRESH RESULT_PACKAGE.
    MOVE e_t_result[] TO RESULT_PACKAGE[].
Regards,
Diego

hi,
   check your changelog table and see data over there, i guess this situation generally happens when you do delta laod , itmight happening bcoz of two image are created which might be cancelling each other when request gets actiavted in DSO and also see for 0recordmode value.
hope it helps
regards
laksh

Similar Messages

  • End Routine is NOT modifying the DSO with new data after load into that DSO

    Hi all,
      I am creating an End Routine for DSO to populate a field ZFCMP_FLG (to store 'Y' ) with lookup from another DSO ZMDS_D01. This new field shows blank instead of 'Y', after activating the DSO. The RESULT_PACKAGE record is populated with 'Y' for ZFCMP_FLG  while debugging that End Routine and why it is NOT writing the modified records into DSO, please ? It is a Characteristic InfoObject with length 1 to store 'Y'. The following is some part of the code:
    DATA: wa_fcmp_flag   TYPE c VALUE 'Y'.
    LOOP AT RESULT_PACKAGE ASSIGNING <RESULT_FIELDS>.
        READ TABLE it_zmds_d01 INTO wa_zmds_d01 WITH KEY
                    /BIC/ZAUFNR    = <RESULT_FIELDS>-CS_ORDER
                    NOTIFICATN     = <RESULT_FIELDS>-NOTIFICATN  BINARY SEARCH.
         IF sy-subrc = 0.
           <RESULT_FIELDS>-/BIC/ZFCMP_FLG = wa_fcmp_flg.
        ENDIF.
    ENDLOOP.
    Thanks,
    Venkat.

    hi...
    Since you are using Field symbol to loop the internal Table there is no need to use the MODIFY Statement in the loop.
    So your code is correct only.
    But here you have to check the status of READ TABLE command in the debug mode.
    it may be failing that's why the RESULT_PACKAGE is not getting modified.
    Plz check it.
    Note: You may need to SORT the Int Table since you are using BINARY SEARCH. check below.
    DATA: wa_fcmp_flag   TYPE c VALUE 'Y'.
    Sort it_zmds_d01 by  /BIC/ZAUFNR    NOTIFICATN  .
    LOOP AT RESULT_PACKAGE ASSIGNING <RESULT_FIELDS>.
        READ TABLE it_zmds_d01 INTO wa_zmds_d01 WITH KEY
                    /BIC/ZAUFNR    = <RESULT_FIELDS>-CS_ORDER
                    NOTIFICATN     = <RESULT_FIELDS>-NOTIFICATN  BINARY SEARCH.
         IF sy-subrc = 0.
           <RESULT_FIELDS>-/BIC/ZFCMP_FLG = wa_fcmp_flg.
        ENDIF.
    ENDLOOP.

  • 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

  • Fields not populated in cube

    hi experts,
                       i have one problem i have sales item,and header dso's which i have loaded the data using flat files.when am trying to load to cube some of the fields of header is not  getting populated.when i am loading only header data that time it is showing the data in cube.when i am loading item data also that time some of the fields of header are not populating in cube.i have tried by taking two seperate cubes for header and item and tried to  loading data to multiprovider. but same issue came.for ur reference i am providing screen shots of that. this is multi provider screen shot in this u can observe that division ,region and some fields are not populating data. in local sand box i have done this please help me to resolve this issue.
    header  cube screen shot before loading to multiprovider.
    item cube screen shot before loading to multiprovider.
    regards
    jaswanthi

    How are you "loading" to a MultiProvider? A MultiProvider is merely a "view" on 1 or more InfoProviders, nothing gets loaded in it.
    The screen shot of your MultiProvider shows data of your items InfoCube only... have you filtered on the InfoProvider field? If not, try and filter on your header InfoCube and see whether it shows any data. If not, then there's something wrong with your mappings in the MultiProvider definition.
    It's perfectly normal to have empty fields if you're combining 2 InfoProviders into 1 MultiProvider. If that's not what you want, you should consider an InfoSet (which "joins" data) or model it so that when you're sending item data to a new InfoCube, you "look up" the missing header data in your header data DSO and add it.

  • Fields not populating

    Hi Experts,
    I have enhanced 0fi_gl_4 extractor. appropriate data is coming into the extractor. But when I load the ODS the enhanced fields are not populating.
    Can anyone help please.
    Thanks in advance
    Yvone

    Hi,
    The issue has to be one of the areas below. Heres a checklist-
    Source system:
    RSA3 check. New fields pulling the correct data?
    BW:
    1. Replication of DataSource - done?
    2. Transfer Structure & Transfer Rules in place for the new fields?
    3. InfoObjects the above fileds are being mapped to are the correct type, in the correct InfoSource & Data Target? All activated?
    4. Update rule that maps these new InfoObjects. Acivated? Has the specific mappings for the new infoObjects been checked and validated?
    Hope this helps
    Sandeep

  • SQ01 query, one field not populating in first line, pushing data to next line

    Good day all
    I have worked with queries for some time and have never encountered this error
    I have a few table joins (FAGLFLEXA, BKPF, BSEG, EKKN, SKAT and EKPO), every thing works and displays correctly, except for the one field
    EKKN (ABLAD) - Unload Point.
    For some reason, when I test the query, it displays correctly with one entry, but as soon as you run the test for more entries, for some reason, the first Unloading point on the report is empty and the value reflects on the next line.  If you display the physical documents where the data pulls from, you can clearly see that the entire report pushes down the field to the next line.
    For example
    Physical SAP Document GL and or PO:
    Year     Per     Do     Document No     Profit     Account     Short Text     Merch     Amount in Grp     Segm     Posted on     Unload Point
    2014     001     XF     40000000000     ABCD     86100       Text              ACD       72799.60             11          20140106      24/59/68
    2014     001     XD     40000000001     ABCC     86100       Text              ACC       18755.50             11          20140108      26/00/48
    SQ01 report (with one line)
    Year     Per     Do     Document No     Profit     Account     Short Text     Merch     Amount in Grp     Segm     Posted on     Unload Point
    2014     001     XF     40000000000     ABCD     86100       Text              ACD       72799.60             11          20140106      24/59/68
    SQ01 report (with more lines)
    Year     Per     Do     Document No     Profit     Account     Short Text     Merch     Amount in Grp     Segm     Posted on     Unload Point
    2014     001     XF     40000000000     ABCD     86100       Text              ACD       72799.60             11          20140106      2014     001     XD     40000000001     ABCC     86100       Text              ACC       18755.50             11          20140108      24/59/68

    I found the error!  The query was written in a certain format.  For example it had many fields which was used to populate the data from different tables.  The error occured because of the sequence.  The query had to bring in a field but it had to derive it from a purchase order, but the purchase order check was after the said field therefor, when it looked at the Purchase Order, it found the field and populated it, but only on the second line.  In the first line it couldnt find the Purchase order yet (as EKKO was lower down), so it didnt populate it yet....
    SIGH

  • New COPA Value field not populating in BW

    We created a NEW value field (VV0056) in SAP COPA that is NOT pulling manual journal entries into BW (document types AB and SA). All other value fields are pulling in all document types and balance to SAP u2013 itu2019s this new one that is not.  We do not have any restrictions on selection of data coming into BW.
    The manual journal entry is in our CE1* table in R/3.
    We are still 3.x data loading in our BW 7 system.
    Any ideas on what to look for?  Your input is greatly appreciated.
    Renee Mercede

    Hi Renee
    The new fields that has been added must be either in the COPA table or the corresponding datasource.
    If it is added in the table
    1) You need to enhance the corresponding datasource with a z-field that wiill represent the field added in the table.
    2) This field will have to be populated through an ABAP routine.
    3) Check the populated field values in RSA3.
    4) Replicate the datasource in BW.
    5) Create infoobject for the enhanced field.
    6) Add infoobject in the corresponding BW data targets.
    7) Change transformations / UR's - TR's.
    8) Extract data.
    If it is added in the datasource - which means you know from which base table this field needs to be populated.
    Carry out steps (2) to (8) from above.
    Cheers
    Umesh

  • Custom idoc segment fields not populated

    Way back in 1999 someone create a custom Idoc type with custom Idoc segments in it.  Unfortunately, they forgot to release one of the segments.
    Recently a change was request to add new fields to this custom segment.  In order to get the fields transported the segment had to be released.
    All worked fine in Dev and the new Idoc segments were populated as expected.  However when the idoc segment was moved to the test system all visually appears to be fine but when the idoc is created (status 50) the new fields are not popultated. 
    In 40B the start of the inbound process was IDOC_INBOUND_DATA.  Does anyone know what the new starting point is in 4.7??
    I beleive the error is actually that SData is not reading all the input values and stopping right where the old fields end in teh custom segment.
    Thanks,
    Anthony

    additionally,
    SAP will not allow us to release the basic idoc type because it was released in 40B.  It also will not allow us to cancel the release since we are now in 620.  So, unless anyone has input for this I think the only solution will be to create a successor IDoc type and change our apps to use the new IDoc type with it's enhancements.

  • Field not populating in update rule

    Hi Gurus,
                  I have created an update rule and i assigned some characteristic to the KF in my rule when i load data to test this update rule some fields are not getting populated can any one tell me what will be the reason? the mapping is correct for these fields.
    waiting for reply
    ravi

    Hi Ravi,
                I think you must check your code exactly.It might be that there is some problem there.Also,Make sure that your mapping is perfect for these fields and also check whether everything is availabale in activated version.
    Regards,
    Amar

  • CRM fields not populating in BPS layout for opportunity Planning 0crm_order

    Hello Support,                                                                               
    We are using SAP CRM 5.0 SP09 with BW 7.0 SP 09.                                                                               
    When creating an opportunity in CRM, the product data ( quantity ,
    values) are not appearing in Planning tab( SEM-BPS Layout) .                                                                               
    Kindly let us know what needs to be done to resolve this issue.    
    Thanks and regards,                                                
    Rajiv Jain

    In your CRM system, check your mapping from CRM to BW are correct.
    You can do this in transaction SPRO. Menu path 'SAP Implementation Guide --> Integration with other mySAP components --> SEM --> Change mapping between CRM fields and InfoObjects'. Select planning application 'OPP' and click on 'Mapping table - system entries' on the left.
    In here you should see the mapping from the InfoObject to the CRM field (eg. Infoobject 0CRM_EXPREV uses structure CRM_BW_OPPT_H and field name EXP_REVENUE).
    In order for the value to be passed to planning you must tick the 'Empty' checkbox on.
    Regards,
    Adrian

  • SRM Invoice and Confirmation fields not populated in Standard content DSO

    We are implementing an extended classic SRM Scenario in our company, along with SAP recommended standard solution for BI. While activating the PO DSO (0SRPO_D1) confirmation quantity (SR_CFQBU) and amount (SR_CFVOC) along with Invoice quantity (SR_IVQBU) and amount (SR_IVVOC) are not getting populated.  Is there a recommended solution to correct this scenario?

    This problem has been solved by implementing OSS Note 1343257

  • External Reference field not populating via CRM_ORDER_MAINTAIN

    Hi ,
    I am using the FM CRM_ORDER_MAINTAIN and wanted to add EXTERNAL REFERENCE Field in existing Complain Order(Transaction :CRMD_ORDER). I am passing the following parameter to add the Reference. But it is not updating the
    with the follwoing Reference number. Could you please help on this.
      ls_ext_ref-REFERENCE_TYPE           = 'Z002'.
      ls_ext_ref-REFERENCE_NUMBER      = '12345678'.
      ls_ext_ref-REFERENCE_TYPE_T        = 'SOCS Number'.
    ls_ext_ref-REFERENCE_MODE           = 'A'.
      ls_Ext_ref-handle                                = '0000000001'.
      ls_ext_ref-ref_guid          = gs_orderadm_h-guid.
      ls_ext_ref-ref_kind          = gc_object_ref_kind-orderadm_h.
      INSERT ls_ext_ref INTO TABLE gt_ext_ref.
      ls_input_field-ref_guid    = gs_orderadm_h-guid.
      ls_input_field-ref_kind    = gc_object_ref_kind-orderadm_h.
      ls_input_field-objectname  = gc_object_name-ext_ref.
      ls_input_field-LOGICAL_KEY = '0000000001'.
      ls_input_field_names-fieldname = 'REFERENCE_TYPE_T'.
      INSERT ls_input_field_names INTO TABLE ls_input_field-field_names.
      ls_input_field_names-fieldname = 'REFERENCE_TYPE'.
      INSERT ls_input_field_names INTO TABLE ls_input_field-field_names.
      ls_input_field_names-fieldname = 'REFERENCE_NUMBER'.
      INSERT ls_input_field_names INTO TABLE ls_input_field-field_names.
      INSERT ls_input_field  INTO TABLE  gt_input_fields.
    CALL FUNCTION 'CRM_ORDER_MAINTAIN'
        EXPORTING
        ct_orderadm_h   = gt_orderadm_h
         it_ext_ref           = gt_ext_ref
       CHANGING
          ct_input_fields = gt_input_fields.
    Get guids
      LOOP AT gt_orderadm_h INTO gs_orderadm_h.
        INSERT gs_orderadm_h-guid INTO TABLE gt_obj_guids.
      ENDLOOP.
      CALL FUNCTION 'CRM_ORDER_SAVE'
        EXPORTING
          IT_OBJECTS_TO_SAVE = gt_obj_guids
        EXCEPTIONS
          DOCUMENT_NOT_SAVED = 1
          OTHERS             = 2.

    Hi,
    For external reference field
    Use Crm_order_read funtion module to read the details.
    get the details  of sales  lt_sales and create same structure of sales and pass the value.
    IF lt_sales IS NOT INITIAL.
        CLEAR ls_sales.
        READ TABLE lt_sales INTO ls_sales INDEX 1.
        IF sy-subrc = 0.
          ls_sales-po_number_sold  = ls_orderadm_h-object_id. """" Ticket no
          MODIFY lt_sales FROM ls_sales INDEX 1.
        ENDIF.
        CLEAR ls_sales.
        CLEAR ls_sales1.
        READ TABLE lt_sales INTO ls_sales INDEX 1.
        IF sy-subrc = 0.
          MOVE-CORRESPONDING  ls_sales TO ls_sales1.
          ls_sales1-ref_handle    = 1.
          ls_sales1-ref_guid      = lv_hguid .                          ls_sales1-ref_kind      = 'A' .
          h2_ls_sales1-po_number_sold = ls_sales-po_number_sold.  "" this is external reference no field._h2
          INSERT ls_sales1 INTO TABLE lt_sales1.
        ENDIF.
        " Input Fields
        ls_input_field-ref_handle =  1.
        ls_input_field-ref_kind   = 'A' .                  "A
        ls_input_field-ref_guid   = lv_hguid.                   "External System GUID Assignment."
        ls_input_field-objectname = sales.                   "SALES
        ls_input_field_names-fieldname = PO_NUMBER_SOLD.
        INSERT ls_input_field_names INTO TABLE ls_input_field-field_names.
        ls_input_field_names-fieldname = PO_DATE_SOLD.
        INSERT ls_input_field_names INTO TABLE ls_input_field-field_names.
        INSERT ls_input_field  INTO TABLE  it_input_fields.
      ENDIF.
    Pass lt_sales1 to crm_order_maintain and crm_order_save.

  • Amount field is not populating properly

    Expert's,
    Here is an issue where one of the amount field not populating properly.For some opportunities the amount field will be just displyed as'0' but for some opprtunities the amount field is displaying as'$0'.The data we are pulling is from CRM.
    Thanks in advance.
    vasu.

    Hi,
    looks like extenstion of your last thread
    did you already have a look in data in cube?just to make sure,try to display cube's data using List cube transaction .Take this amount field,corresponding Currency Key,and you rmost impotant characteristics...and check whether all records are having entry in 'currency' column?

  • 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

  • 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

Maybe you are looking for