BI-IP change characteristic value in FOX

Hello Guys,
i want to change the characteristic value in FOX.
Therefore the FOX runs through all char combinations to identify the highest
number for the char test.
This step works fine, but i cant write the value for maxloop in the cube.
If i try, only the old row is deleted, but i dont get a new row with the calculated value for maxloop.
the code looks like this:
DATA LOOP TYPE test.
DATA MINLOOP TYPE test.
DATA MAXLOOP TYPE test.
MINLOOP = 00000.
MAXLOOP = 00000.
FOREACH LOOP.
MINLOOP = LOOP.
IF MINLOOP > MAXLOOP.
MAXLOOP = MINLOOP.
ENDIF.
ENDFOR.
MAXLOOP = MAXLOOP + 00001.
{Amount, EUR, #, #, 00200, 00000000, #, 2007, #, #, #, #, #, #, #} =
{Amount, EUR, #, #, maxloop, 00000000, #, 2007, #, #, #, #, #, #, #}.
Any suggestions what is wrong here?
Regards
T. Mekler

Hi,
You have written
{Amount, EUR, #, #, 00200, 00000000, #, 2007, #, #, #, #, #, #, #} =
{Amount, EUR, #, #, maxloop, 00000000, #, 2007, #, #, #, #, #, #, #}.
But as per the statement  MAXLOOP = MAXLOOP + 00001 the MAXLOOP conatins a new figure. Obviously there will not be any record in the cube for this value of MAXLOOP.
You are assigning this to the record with MAXLOOP = 00200, so system is assigning zero to  0AMOUNT for the record that is having MAXLOOP=00200 value.
Make the below corrections and test again:
DATA NEWLOOP type test.
NEWLOOP = MAXLOOP + 00001.
{Amount, EUR, #, #, NEWLOOP, 00000000, #, 2007, #, #, #, #, #, #, #} =
{Amount, EUR, #, #, MAXLOOP, 00000000, #, 2007, #, #, #, #, #, #, #}.
Regards,
Deepti

Similar Messages

  • Hi. i used Function module to change Characteristic values of a sales order

    hi. i used Function module to change Characteristic values of a sales order..
    but sales order's Characteristic values didn't change.
    And the Function module doesn't occur any log message.
    please tell me wrong code, and how to solve this problem.
    if i have wrong method, what data can i pass to change the characteristic values
    DATA: LT_E1CUVAL    TYPE TABLE OF E1CUVAL.
      DATA: WA_E1CUVAL    TYPE E1CUVAL.
      DATA: LS_CFG_HEAD   LIKE CUXT_CUCFG_S,
            LS_INSTANCES  LIKE CUXT_CUINS_S,
            LS_VALUES     LIKE CUXT_CUVAL_S,
            LS_E1CUCFG    LIKE E1CUCFG,
            LS_E1CUINS    LIKE E1CUINS,
            LS_E1CUVAL    LIKE E1CUVAL,
            LS_PROFILE    LIKE E1CUCOM,
            LS_VBAP       LIKE VBAP,
            L_CUOBJ       LIKE INOB-CUOBJ,
            L_ATINN       LIKE CABN-ATINN.
      DATA: LT_INSTANCES  LIKE CUXT_CUINS_S OCCURS 0,
            LT_PART_OF    LIKE CUXT_CUPRT_S OCCURS 0,
            LT_VALUES     LIKE CUXT_CUVAL_S OCCURS 0,
            LT_VAR_KEYS   LIKE CUXT_CUVK_S  OCCURS 0,
            LT_KSML       LIKE KSML         OCCURS 0 WITH HEADER LINE,
            BEGIN OF LT_CLINT OCCURS 0,
              CLINT  LIKE KSSK-CLINT,
            END OF LT_CLINT.
      DATA: LT_CUIB       LIKE CUIB_CUOBJ_S OCCURS 0 WITH HEADER LINE.
      DATA: E_ROOT_INSTANCE           TYPE     CUXT_INSTANCE_NO.
      DATA: EV_ROOT_PERSIST_ID     TYPE     IBEXTINST_DATA-EXT_INST_ID.
      DATA: EV_CFG_HAS_CHANGED     TYPE     XFELD.
      DATA: EV_HANDLE_APPL_LOG     TYPE     BALLOGHNDL.
      DATA: L_CUOBJ_NEW           TYPE CUOBJ.
      DATA: L_OWNER               TYPE IBXX_BUSINESS_OBJECT.
      REFRESH LT_E1CUVAL.
      CLEAR LS_VBAP.
      SELECT SINGLE CUOBJ INTO CORRESPONDING FIELDS OF LS_VBAP
                                FROM VBAP WHERE VBELN = I_VBELN
                                            AND POSNR = I_POSNR.
      IF SY-SUBRC <> 0.
        RAISE INSTANCE_NOT_FOUND.
      ENDIF.
      REFRESH LT_CUIB. CLEAR LT_CUIB.
      LT_CUIB-INSTANCE = LS_VBAP-CUOBJ.
      APPEND LT_CUIB.
      CALL FUNCTION 'CUCB_INITIALIZER'
        EXPORTING
          IT_INSTANCES = LT_CUIB[].
      CALL FUNCTION 'CUXI_GET_SINGLE_CONFIGURATION'
        EXPORTING
          I_ROOT_INSTANCE              = LS_VBAP-CUOBJ
        IMPORTING
          E_CFG_HEAD                   = LS_CFG_HEAD
          ES_PROFILE                   = LS_PROFILE
          ET_RETURN                    = ET_RETURN
        TABLES
          E_TAB_INSTANCES              = LT_INSTANCES
          E_TAB_PART_OF                = LT_PART_OF
          E_TAB_VALUES                 = LT_VALUES
          E_TAB_VAR_KEYS               = LT_VAR_KEYS
        EXCEPTIONS
          INVALID_INSTANCE             = 1
          NO_ROOT_INSTANCE             = 2
          INSTANCE_IS_A_CLASSIFICATION = 3
          INTERNAL_ERROR               = 4
          NO_PROFILE_FOUND             = 5
          INVALID_DATA                 = 6
          OTHERS                       = 7.
      IF SY-SUBRC <> 0.
        CASE SY-SUBRC.
          WHEN 1.
            RAISE INSTANCE_NOT_FOUND.
          WHEN 3.
            RAISE INSTANCE_IS_A_CLASSIFICATION.
          WHEN OTHERS.
            RAISE INVALID_DATA.
        ENDCASE.
      ELSE.
        LOOP AT LT_VALUES INTO LS_VALUES.
          IF    LS_VALUES-CHARC = 'SAP_MILLCA_PACKAGING'
             OR LS_VALUES-CHARC = 'PD_CA_PACKING_DM'.
            LS_VALUES-VALUE = '7100010'. "This is test data
            MODIFY LT_VALUES FROM LS_VALUES.
          ELSE.
            DELETE LT_VALUES WHERE CHARC = LS_VALUES-CHARC.
          ENDIF.
          CLEAR LS_VALUES.
        ENDLOOP.
      ENDIF.
    &#50689;&#50629;&#51221;&#48372; &#53945;&#49457; &#48320;&#44221;
      CALL FUNCTION 'CUXI_SET_SINGLE_CONFIGURATION'
        EXPORTING
          I_CFG_HEADER                        = LS_CFG_HEAD
          I_ROOT_INSTANCE                     = LS_VBAP-CUOBJ
        I_PLANT                             =
        I_STRUCTURE_EXPLOSION_DATE          =
        I_STRUCTURE_EXPLOSION_APPL_ID       =
        I_LOGSYS                            =
          IS_PROFILE                          = LS_PROFILE
        IV_ONLY_SINGLE_LEVEL                =
        IV_HANDLE_APPL_LOG                  =
        IV_OBJECT_APPL_LOG                  = 'CIF'
        IV_SUBOBJECT_APPL_LOG               = 'T_CNFG'
        IMPORTING
          E_ROOT_INSTANCE                     = E_ROOT_INSTANCE
          EV_ROOT_PERSIST_ID                  = EV_ROOT_PERSIST_ID
          EV_CFG_HAS_CHANGED                  = EV_CFG_HAS_CHANGED
          EV_HANDLE_APPL_LOG                  = EV_HANDLE_APPL_LOG
          ET_RETURN                           = ET_RETURN
        TABLES
          I_TAB_INSTANCES                     = LT_INSTANCES
          I_TAB_PART_OF                       = LT_PART_OF
          I_TAB_VALUES                        = LT_VALUES
          I_TAB_VAR_KEYS                      = LT_VAR_KEYS
        I_TAB_BLOB                          =
        EXCEPTIONS
          NO_CONFIGURATION_DATA               = 1
          NO_ROOT_INSTANCE                    = 2
          INVALID_INSTANCE                    = 3
          INSTANCE_IS_A_CLASSIFICATION        = 4
          INTERNAL_ERROR                      = 5
          NO_PROFILE_FOUND                    = 6
          INVALID_DATA                        = 7
          OTHERS                              = 8
      IF SY-SUBRC <> 0.
        CASE SY-SUBRC.
          WHEN 1.
            RAISE NO_CONFIGURATION_DATA.
          WHEN 3.
            RAISE NO_ROOT_INSTANCE.
          WHEN 3.
            RAISE INVALID_INSTANCE .
          WHEN 3.
            RAISE INSTANCE_IS_A_CLASSIFICATION.
          WHEN 3.
            RAISE INTERNAL_ERROR.
          WHEN OTHERS.
            RAISE INVALID_DATA.
        ENDCASE.
      ENDIF.
      COMMIT WORK.
    save configuration with next commit
      CLEAR: LS_INSTANCES.
      READ TABLE LT_INSTANCES INTO LS_INSTANCES INDEX 1.
    L_OWNER-OBJECT_TYPE = LS_INSTANCES-OBJ_TYPE.
      L_OWNER-OBJECT_TYPE = 'PVS_POSVAR'.
      L_OWNER-OBJECT_KEY  = LS_INSTANCES-OBJ_KEY.
      CALL FUNCTION 'CUCB_CONFIGURATION_TO_DB'
        EXPORTING
          ROOT_INSTANCE         = LS_VBAP-CUOBJ
          ROOT_OBJECT           = L_OWNER
        IMPORTING
          NEW_INSTANCE          = L_CUOBJ_NEW
        EXCEPTIONS
          INVALID_INSTANCE      = 1
          INVALID_ROOT_INSTANCE = 2
          NO_CHANGES            = 3
          OTHERS                = 4.
      IF SY-SUBRC > 1 AND SY-SUBRC <> 3.
        CLEAR LS_VBAP-CUOBJ.
        RAISE INTERNAL_ERROR.
      ELSEIF SY-SUBRC = 1.
        LS_VBAP-CUOBJ = L_CUOBJ_NEW.
      ENDIF.
    What's wrong?
    help me to solve this problem.
    Thanks a lot.

    <b>SD_SALES_DOCUMENT_READ</b> Reads sales document header and business data: tables VBAK, VBKD and VBPA (Sold-to (AG), Payer (RG) and Ship-to (WE) parties)
    <b>SD_SALES_DOCUMENT_READ_POS</b> Reads sales document header and item material: tables VBAK, VBAP-MATNR
    <b>SD_DOCUMENT_PARTNER_READ</b> partner information including address. Calls SD_PARTNER_READ
    <b>SD_PARTNER_READ</b> all the partners information and addresses
    <b>SD_DETERMINE_CONTRACT_TYPE</b>
    In: at least VBAK-VBELN
    Exceptions: NO CONTRACT | SERVICE_CONTRACT | QUANTITY_CONTRACT
    <b>SD_SALES_DOCUMENT_COPY</b>
    <b>RV_ORDER_FLOW_INFORMATION</b> Reads sales document flow of sales document after delivery and billing
    SD_SALES_DOCUMENT_SAVE create Sales Doc from the copied document
    SD_SALES_DOCUMENT_ENQUEUE to dequeue use DEQUEUE_EVVBAKE
    RV_DELIVERY_PRINT_VIEW Data provision for delivery note printing
    SD_PACKING_PRINT_VIEW
    SD_DELIVERY_VIEW Data collection for printing
    called from RV_DELIVERY_PRINT_VIEW, SD_PACKING_PRINT_VIEW
    RV_BILLING_PRINT_VIEW Data Provision for Billing Document Print
    regards
    vinod

  • CT04 - Changing characteristic Value Check procedure

    Hi,
    I want to change the value check validation for a an existing material characteristic from from the allowed values list to a chaeck table.  I intende on on using the 'Other Value Check'  button in the Values tab of CT04, but unfortunately this button is greyed out.
    I would like to know if it is possible to start using a check table for an existing material characteriestic, and if so how?
    Thanks,
    Roy

    Hi Roy,
    The only way I've managed to do this was to delete and re-create the characteristic. It gets complicated as SAP wants you to remove all entries for the characteristic before deleting it which means you need someone able to do the LSMWs to remove then re-load the data once you've re-created the characteristic.
    Regards,
    John

  • Change characteristic values in SO via BAPI_SALESORDER_CHANGEBOS

    Hi Experts,
    Now, I would like to update the characteristic values of configuration in sales order via BAPI : BAPI_SALESORDER_CHANGEBOS. But, I can't find right way to execute this BAPI. I tried so many times and no data changed. I wonder that i didn't specify the correct import parameters.
    Is anyone can help me? Thanks for your kindly support in advance.
    Best Regards,
    Ryan

    Hi Ryan,
        I had a similar kind of requirment, to change the characteristic values in a sales contract, where I used, BAPISDORDER_GETDETAILEDLIST to get the details of the agreement line iteam and after sorting the necessary vales then used BAPI: BAPI_CUSTOMERCONTRACT_CHANGE to change the customer agreement line item.
    In your case as well you can use the BAPISDORDER_GETDETAILEDLIST to get the details, based on this you write logic to hold the necessary change value and finally, use BAPI: BAPI_SALESORDER_CHANGE to updated the changes in the sales order.
    Hope this helps.
    Regards
    Raj

  • Change Characteristic values in Material class Classification

    Hi,
    Is there any standard program to change Characteristic vaules in Material Classification?
    Thanks,
    Shiva

    Thanks for your help.
    Points will be awarded.
    Shiva

  • Lock characteristic value for configurable material in Sales Order

    Is there a setting in SAP which can prevent user changing characteristic value for configurable material in Sales Order after production order created for this Sales Order? Currently, it can only works when first delivery create for this Sales Order.
    Thanks a lot.

    Hi,,
    in the characteristic goto additional data tab,
    you have a field called not ready for input.
    you select this when the value in this characteristic come by calculation based on the previous selection.
    that field will be greyed out.
    OR
    u can even select the no display check box,
    by selecting this u cant see the characteristic in the list,, it will give u a popup before leaving the screen.
    for this the char has to be a required field.
    OR
    if any of this is not working then may be u can try out with authorization management.
    thanks

  • BI-IP: Change of characteristic value in ABAP EXIT planning function

    Hi
    I have created a planning function of the type EXIT with reference data without blocks. In method IF_RSPLFA_SRVTYPE_IMP_EXEC_REF~EXECUTE I am going to implement my code.
    Now, one of the purposes is to update the VALIDTO of an existing record. Is it possible to modify the characteristic values directly in C_TH_DATA (thus allowing me to just update the date directly on the record) or can I only append records?
    Cheers!
    /Karsten

    Hi Larse,
    Yes you can change directly your value in a record withou appending a new one,but still it will create 2 records in the delta buffer ready to be save to the cube.
    Reagrds,
    Eitan.

  • How to change the variable value in fox formula?

    Hi All,
        Please help me achieve this scenario,
             in the variable selection screen , i wil give some i/p like, calyear(0calyear) = 2008.
          In planing function using FOX formula, i must be able change the variable value to 2009.
      Will it be possible to achieve this, can we change a variable value using FOX formula, if possible
    please let me knw how to achieve this.
    Thanks n Regards,
    Priya.

    Hi Priyadarshini,
    i dont know what is your requirement exactly.If you can give a better explanation of ur requirement we can help you. But to answer your question yes we can get new values for the variable in the planning function.
    for this you need to couple the planning function together with the planning filter in a planning sequence. This planning filter should have the variable that you wanted to change. In the WAD when you want to call this planning sequence there is an option to call variable screen. If you enable this, it will pop up the variable screen to get this value again.
    Guess this was helpful.
    Regards.
    Shafi.

  • How to change the characteristic value in a item of sales order by FM?

    Hi experts,
    I guess the FM BAPI_SALESORDER_CHANGE can implement my requirement. But I have made many testing program, that's all failed. I don't know which part is not correct. So could you give a very simple sample to me? Just change the characteristic value in a item of sales order, not do any change for other parts. Thanks in advanced.
    Regrads

    Hi Birendra,
    Thanks for you explain. I follow your guide to wirte abap program. But related characteristic value still not changed in SO main screen. could you give me some suggestion? Thanks a lot!
    type-pools: IBCO2,
                IBXX.
    data: l_CUOBJ type CUOBJ_VA,
          l_ibase type IBCO2_IBASE_REC,
          l_CONFIGURATION type IBCO2_INSTANCE_TAB2,
          w_CONFIGURATION type IBCO2_INSTANCE_REC2,
          l_ROOT_OBJECT type IBXX_BUSINESS_OBJECT.
    data: t_IBCO2_VALUE_TAB type IBCO2_VALUE_TAB,
          w_IBCO2_VALUE_REC type IBCO2_VALUE_REC.
    select single CUOBJ
      into l_CUOBJ
      from VBAP
      where VBELN = '0020030609'
        and POSNR = '000020'.
      CALL FUNCTION 'CUCB_GET_CONFIGURATION'
        EXPORTING
          INSTANCE                           = l_CUOBJ
        IS_BUSINESS_OBJECT                 =
        IV_MOMENT                          =
        IV_WITH_DB_INSTANCE                =
       IMPORTING
         IBASE                              = l_ibase
         CONFIGURATION                      = l_CONFIGURATION
        EO_CBASE_REF                       =
      EXCEPTIONS
        INVALID_INPUT                      = 1
        INVALID_INSTANCE                   = 2
        INSTANCE_IS_A_CLASSIFICATION       = 3
        OTHERS                             = 4
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    loop at l_CONFIGURATION into w_CONFIGURATION.
      l_ROOT_OBJECT = w_CONFIGURATION-OWNER.
    t_IBCO2_VALUE_TAB[] = w_CONFIGURATION-values[].
      read table w_CONFIGURATION-values into w_IBCO2_VALUE_REC with key ATINN = '0000000222'.
      w_IBCO2_VALUE_REC-ATWRT = 'TMP'.
      modify w_CONFIGURATION-values from w_IBCO2_VALUE_REC index sy-tabix.
      modify l_CONFIGURATION from w_CONFIGURATION index 1.
      clear: w_CONFIGURATION.
    endloop.
    CALL FUNCTION 'CUCB_SET_CONFIGURATION'
      EXPORTING
        ROOT_INSTANCE                      = l_CUOBJ
      IS_CBASE_HEADER                    =
      CHANGING
        CONFIGURATION                      = l_CONFIGURATION
    EXCEPTIONS
      INVALID_INPUT                      = 1
      INVALID_INSTANCE                   = 2
      INSTANCE_IS_A_CLASSIFICATION       = 3
      OTHERS                             = 4
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    CALL FUNCTION 'CUCB_CONFIGURATION_TO_DB'
      EXPORTING
        ROOT_INSTANCE                       = l_CUOBJ
        ROOT_OBJECT                         = l_ROOT_OBJECT
      FORCE_NEW_INSTANCE                  =
      IV_WITHOUT_COMMIT_UPDATE            = ' '
      IV_MATERIAL                         =
      IV_LOCATION                         =
      IV_TECHS                            =
    IMPORTING
      NEW_INSTANCE                        =
    TABLES
      EXP_NEW_NESTED_CUOBJS               =
    EXCEPTIONS
      INVALID_INSTANCE                    = 1
      INVALID_ROOT_INSTANCE               = 2
      NO_CHANGES                          = 3
      ALREADY_REGISTERED_FOR_UPDATE       = 4
      INSTANCE_IS_A_CLASSIFICATION        = 5
      OTHERS                              = 6
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.

  • Generate change documents for characteristic value changes in material master

    Hello,
    I am currently using material class (class type: 001) and assign some characteristics to material master. I am going to create a query/custom report to track all changes in the characteristic values in that material master. However, I could not find any change document in CDHDR table.
    I have activated "Change Docs" parameter in class type 001 customizing as described in SAP note: 65124 Classification Change Documents as follow:
    Is it possible to generate change documents for characteristic values in material master?
    Regards,
    Julian

    Hi Rajen,
    Thanks for your reply. It seems that I missed one more step in the customizing. Once the multiple object is activated, I need to activate the change document parameter for each assigned object.
    Thread closed.
    Regards,
    Julian

  • Retail : Mass characteristic value change

    Hi,
    I manage characteristic values in the material master data (MM41/MM42/MM43) but I did not find a way to change these values in mass (MM46).
    Does someone has an idea ?
    Best regards,
    ML

    Hi,
    Pls put in MM forums and get the reply immly.
    Anil

  • Change Column Value based on Characteristic in Rows

    I am not sure it is possible.
    We have product prices at different levels of customer hierarchy.
    Channel > Division > Region > Market
    One Region can have multiple Markets.  Each market can have different Rates.  But the Region will have a different Rate which many not be the average rate of all market (assigned as part of master data)
    I have a column for Product Price.  So when a Report is run at Market Level it should use Market Rate.  If Market is Removed and Region is dragged into the report it should use Region Rate for Product Price.
    Product Price is Restricted by Rate Type value to determine which Rate is used.
    Is there a way to dynamically determine the define the column value based on the characteristic value in the ROWS.
    Thanks

    Hi,
    For every CHAR like Market/Region there will be some key. For example Maket1 = 11 and Market2 = 22. If that key is a number then you may create replacement path variable on that and convert the same in numbers then you may create various CKF (for various rate type) and put "If" condtion and check for those replacement path CKF and use the apprpriate one.
    You need to write some tricky formula at CKF levels. This is one of the way to achieve that.
    I hope it will help.
    Thanks,
    S

  • Changing DATE as a Characteristic value of batch with BAPI_OBJCL_CHANGE

    Hello,
    Could you give advice for using BAPI_OBJCL_CHANGE?
    I decided to use BAPI_OBJCL_CHANGE to update Batch characteristic value.
    I could update CHAR field but could not DATE.
    I set like below :
      - Characteristic name (e.g. Z10001) to CHARACT of ALLOCVALUESNUMNEW(Tables)
      - DATE(e.g. 20081211) to VALUE_FROM of ALLOCVALUESNUMNEW(Tables).
    But it does not work.
    Of course, I executed BAPI_TRANSACTION_COMMIT after the FM done.
    I found the value of VALUE_FROM is missing when debugging.
    Thanks in advance.
    Takeru Miyagawa

    Hello,
    you said :
    - DATE(e.g. 20081211) to VALUE_FROM of ALLOCVALUESNUMNEW(Tables).
    Data type of field VALUE_FROM is FLTP. How do you fill this field ? by MOVE ?
    You should not use MOVE, you should use :
    DATA:
    wlv_date              TYPE d,
    wls_ALLOCVALUESNUMNEW TYPE BAPI1003_ALLOC_VALUES_NUM.
               CALL FUNCTION 'CTCV_CONVERT_DATE_TO_FLOAT'
                             EXPORTING date          = wlv_date
                             IMPORTING   float       = wls_ALLOCVALUESNUMNEW-VALUE_FROM.
    - I found the value of VALUE_FROM is missing when debugging.
    Can you show us your code ?
    Cordialement,
    Chaouki.

  • Slow dataload into Infocube- Conversion of Characteristic values to SIDs

    Hi All,
    we are facing a slow delta load issue when loading from a DSO into an InfoCube ( approx 150,000 recs).
    After checking the monitor found that
    - The Conversion of Characteristic values to SIDs is taking time
    - The Start Routine time is real quick ( in secs)
    The underlying DSO is hugh and there is no SIDs Generation upon Activation flag set for it
    Master data is loaded first and than we are loading the transaction data.
    i've tried refreshing the stats of the Cube, Reduce the size of the data package,
    Deletion of Indexes than Loading and recreation of Indexes, no joy at all.
    Any comments and recommendations are much appreciated.
    Thanks,
    Natalie

    Hi Natalie,
    The problem for your slow delta load from DSO to cube is because the SIDs Generation upon Activation flag is unchecked at DSO level .
    Becasue of which your activation is faster but your loading from DSO to cube will be slower as you only mentioned that SIDs are being generated .
    One recommendation will be to switch on the property of the DSO SIDs Generation upon Activation flag .
    Are there any secondary indexes also in DSO ?
    You can try deleting them also during loading the data from DSO to cube .
    I guess your change log table is also huge in this case . If possible we can think of deleting the log table also . Then for the new records let it get filled .
    Hope the above reply was helpful.
    Regards,
    Ashutosh Singh .
    Edited by: DEADLOCKS on Apr 21, 2011 5:08 PM

  • Characteristic value '5000000000 ' of characteristic 0MATERIAL is not MATN1

    Dear Experts,
                          I am getting one error message while extraction,when executing the DTP .the messge is :
    "Characteristic value '5000000000 ' of characteristic 0MATERIAL is not MATN1 -converted"     BRAIN     68          @3R@
    what is the meaning of this messege ,Request you to plese suggest me reagarding the same .thanks in advance .

    Hi Bhullar,
    Have you maintained material length as 18 at ECC and BW sides.
    at bw side info object 0material conversion routine as MATN1. seems like you may be maintained as ALPHA. if your using as ALPHA conversion routine then at transfer rules for MATERIAL you can pass output data by suing FM - CONVERSION_EXIT_ALPHA_INPUT.
    or if possible then change conversion routine to MATN1 for material(info obj) at data source level or info object maintenance(RSD1) level.
    Thanks

Maybe you are looking for