DMS - BADIs: Read Characteristic values

Hello,
we want to implement a characteristic-check in the Document BADI DOCUMENT_STATUS01~AFTER_CHANGE_STATUS.
Therefore we need to read the chacteristic values of the default class.
If the user enters i.e. some characteristic values in the CV02N an changes the Document Status (without saving between), the new characteristic values cannot be accessed via BAPI_DOCUMENT_GETDETAIL2 (getclassification=x).
Is there an other way to get the characteristic values in the Document BADIs ?
Best regards,
Stefan.

Hello Pelaez,
thanks, we read the buffer with the the function module CLFM_GET_INTERNAL_TABLES.
If the buffer is empty, we get the characteristic values with the BAPI_DOCUMENT_GETDETAIL2.
Stefan.

Similar Messages

  • Error when reading chars values when restricting time chars in Query

    Hi all,
    since a few days I am not able to restrict time characteristics in queries on a particular Multiporvider. I can restrict the time chars with variables but not with fixed values.
    I am getting the following error:
    Reading Characteristic Values -> Programm Error in class SAPMSSY1 -> Uncaught exception.
    The problem exists only on one particular multi provider, but when checking the MP it indicates no errors.
    Anyone experienced something similiar? I am appreciating your help.
    Thomas

    actually it is a problem associated with SAP GUI 7.0.
    A solution to this problem is
    Just replace the file wdbspres.dll with in the following location
    C:\Program Files\SAP\FrontEnd\SapGui.
    You can search for this file on google and download it.
    we also had faced this problem earlier...but after replacing the wdbspres.dll...it worked..
    i hope this helps you.
    pls assign points if this answer is of some help

  • Bad reading of thermocouple on SCXI-1102

    Hi,
    Some of the thermocouple plugged in the SCXI-1102 give bad reading(unusual value). There is maybe an issue with the use of grounded and non-grounded thermocouple? Is the system need to be calibrated?
    Thanks.

    Hello gperron,
    When you say some thermocouples give bad values, does this mean that you have some that give the correct value?  If so, try switching the ones that give you a correct reading with the ones that are giving a bad reading.  If the bad readings follow the thermocouples, you can conclude that those thermocouples are bad.  Are you using the built-in cold junction compensation on the SCXI-1303 to make sure you are getting the most accurate readings?
    In general, thermocouples are floating sources and you measure them differentially with a bias resistor connected between the negative terminal and ground.  Page 3-4 of the 1102 User Manual describes connecting signals to the 1102.  The 1303 Installation Guide describes how to replace bias resistors, if needed.   
    Thanks,
    Laura

  • Variable reading other's characteristic value.

    Hi gurus,
    do you know, how can I make a variable (characteristic value variable) that reads other characteristic's value?
    i.e. I have 0CALMONTH in columns and a structure with 3 restricted key figures - I need to show KF value for 1st, 15th and last day of 0CALMONTH.
    Regards,
    Dorota

    Hi Dorota,
    What I have got from your query is.
    Take an input for 0CALMONTH from user.
    And then display Key figures restricted by 1st Day of the month entered by user, 15th daysand then last day of the month.
    If this is what your requirement is then you can achieve it by restricting the three key figures with variable.
    The variable should be defined with processing type as Customer Exit.
    Please refer the below link for more info:
    Problem while deriving 1st Calendar day of the fiscal period
    Regards
    Shubh Karan

  • Easy DMS Search - Characteristic Value Format

    Hi,
    I am having an issue when conducting a document search using classification with a date characteristic.  More specifically, when BAPI_DOCUMENT_GETLIST2 is called, the characteristic value is formatted as DD.MM.YYYY.  When the user setting format is MM/DD/YYYY, the search does not yield any results.  Does anyone know where EasyDMS derives the format it uses when calling the BAPI and how this may be changed?
    Thanks,
    Adam

    You may extract the info using vs studio 2005, by referring the EasyDMSExplorer.tlb file supplied in EasyDMS Installtion. See  wiki http://wiki.sdn.sap.com/wiki/x/cAHEB for example.

  • DMS - Inconsistent characteristic value assignment

    Dear experts,
    I've some DMS documents with an 'Inconsistent characteristic value assignment': two values for a single-value characteristic.
    I want to correct those documents, but I don't to change AUSP directly. I've tried BAPI_DOCUMENT_CHANGE2, but without results.
    Thanks in advance for any help.
    Regards,
    sb.

    Thanks Charlie.
    Yes, this is for PR release strategy. I have checked OMGQCK, there is no inconsitency related to char value assignment. But when I tried to assign char values in SAPL0ME2, there is hard error C1821.
    I also tried to delete the char from the class but the error is still there. Any ideas?
    Thanks
    JM

  • Batch Classification Characteristic Values in MIGO...

    Hi,
    Can we update Batch Classification Characteristic Values in MIGO...
    Batch is also created while doing MIGO. I have no issues in creating Batch.
    Thanks in advance...

    Hi.
      You can use the CACL_VALUE_CHANGE badi.
    Regards.

  • How to fulfill the virtual characteristic value into report

    Hi Experts,
          I am working on one reporting requirement that needs to add reference date (virtual characteristic) field to report.
          I have added reference date field to query and able to display the field in report.But I am not able to display reference date field runtime data in to report output.
        Could someone please help me on this how to display this virtual characteristic values into report.where the runtime variable values are stored.How to fill the data etc.
    Thanks in advance.
    Best Regards,
    Hari.
    Edited by: k hari on Jan 29, 2008 6:22 AM
    Edited by: k hari on Jan 29, 2008 6:24 AM

    You can achieve this using Customer Exit or BADI. Check the folllowing link.
    http://help.sap.com/saphelp_nw70/helpdata/en/ac/ef1f43daac9a448f0150a02e3a7aba/content.htm
    If you are using BADI
    You can create Virtual CHAR in BADI using transaction SE19
    In this transaction you can create a new or display the existing BADI.
    There you can see two tabs
    The Attribute Tab we need to give the name of the Multiprovider on which the query with the virtual char is getting executed.
    The Inerface Tab has three following sections. Need to write the ABAP code for all the three.
    Define : Defind all the characteristics and virtual char that will be used for populating virtual char
    Initialize : Initialize them
    Compute : Here you will have to write the logic for populating the virtual char.
    Once the logic is written then you can use this char in your query .
    Hope this helps.

  • Conversion of Characteristic Values to SIDs is taking long time

    Hi Experts,
        Cube load is taking more than 7 hrs to complete for 6 million records. Max time is at Conversion of Characteristic Values to SIDs. Cube consists of 500 fields. Load is from DSO to Cube. DSO has 10 fileds with no SID flag check for activation. Remaining fields in the CUBE are pouplated looking in to other DSO's. Start and End routines are executing very fast. How to fasten Conversion of Characteristic Values to SIDs step.  I need to load 15 million records daily as part of delta. any suggestions.
    Thanks
    Sunil

    Hi Sunil,
    Go through the below link, it will be useful
    http://aq33.com/business-warehouse/Articles-05269.html
    Regards,
    Marasa.

  • Performance - Conversion of characteristic values to SID

    Greetings:
    Yesterday I load 556.000 record into an infocube.
    No transformations of any kind. Direct assign for every infoobject. Very simple
    It lasted 1 h 30m to complete the loading.
    It started loading  7 datapackage of 50.000 records each.
    I realized that 3 of those datapackage (#2, #4 and #7) lasted from 41:47min to 41:59min in the "Conversion of characteristic values to SID" task. The other 5 lasted ... seconds.
    Any idea of that could be going on during this conversion?
    I don't understant why some datapackages last so long and other don't.
    Does anybody has any idea about this?
    Thanks in regards.
    Guillermo

    Hi Daniel,
    The SID generation is based upon the Dimension Table and Master data.
    If you see the dimension table can be build with different types like:
    one to many
    many to one
    many to many
    one to one
    So, if the dimension's for that datapacket data is many to many then it has to get all the relations and then it has to assign an SID.
    If it is one to one then there will be no more work to be done by the system to assign the SID's
    Hope you understood the back-end process.
    With Regards,
    Ravi Kanth.

  • Conversion of Characteristic Values to SIDs. Load Very slow

    Hi Experts,
                     We have a slow load issue when loading from a Write-Optimized DSO into an InfoCube. 8 millon recs in 10 hours.
    We check the start, end, and rules routines and every is ok but for all the package the load was very slow in the Conversion of Characteristic Values to SIDs.
    Can any help me with this?
    Thanks a lot,
    Alejandro

    Hi,
    It is because the SIDs Generation upon Activation flag is unchecked at DSO level .
    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 .
    Also load your master data first and activate it before loading it to cube.
    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.

  • 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

  • Issue in Custome FM of Characteristic Value

    Hi All,
    I have created Custom FM for possible values of  Characteristic.
    Its working fine in all transaction except CU60.
    In Cu60 Transaction if user click on F4 for characteristic value My custom help popup is coming.  when user select any of the value its populating in table maintenance. But Issue the issue is when user is saving those value those value are not saving in table maintenance.
    Please tell me if I need to do any addition stuff.
    I have created FM using below SAP Doc.
    Function Module for Checking Values
    In this field, you can enter the name of a function module for checking characteristic values entered by the user. The function module can be created in any function group.
    The following restrictions apply:
    The function module must use the standardized interface.
    The function module name cannot have more than 27 characters.
    This allows names to be inferred for further function modules: for the possible entries on the value assignment screen, and for copying language-dependent value descriptions:
    Function module for possible entries
    <function module for value check> + suffix "_F4"
    Function module for language-dependent value descriptions
    <function module for value check> + suffix "_DC"
    Interface for Function Module for Checking Values
    Import Parameters:
    CHARACT_NO LIKE CABN-ATINN  Internal characteristic number
    CHARACT LIKE CABN-ATNAM  Characteristic name
    VALUE LIKE CAWN-ATWRT  Value to be checked
    Exceptions:
    NOT_FOUND   Value not found
    Interface for Function Module for Possible Entries
    Import Parameters:
    CHARACT_NO LIKE CABN-ATINN  Internal characteristic number
    CHARACT LIKE CABN-ATNAM  Characteristic name
    DISPLAY   Display values only,
       if DISPLAY = 'X'
    ADDITIONAL_VALUES LIKE CABN-ATSON Additional values allowed
       if ADDITIONAL_VALUES = 'X'
       (if you want the possible
       entries dialog box to contain an
       additional line for entry)
    MULTIPLE_VALUES LIKE RCTMV-ATLIS Multiple values allowed
    LANGUAGE LIKE SY-LANGU  Language indicator
    DISPLAY_WITH_LANGUAGE   Display value with description
    Tables
    VALUES LIKE RCTVALUES  Selected values
       When you call this table, it
       contains existing values.
       Deleted values have status 'D'
       in the table.
       New values have status 'I'
       in the table.
    The function module must also let you display and select values using the possible entries pushbutton. To display possible entries, you can use function modules in function group SHL3, such as HELP_VALUES_GET_WITH_TABLE_EXT. The content is described in the function module documentation.
    Interface for Function Module for Language-Dependent Value Descriptions
    Import parameters
    CHARACT_NO LIKE CABN-ATINN  Internal characteristic number
    CHARACT LIKE CABN-ATNAM  Characteristic name
    VALUE LIKE CAWN-ATWRT  Value to be checked
    LANGUAGE LIKE SY-LANGU  System language
    Exceptions
    NOT_FOUND   Value not found
    If you use this function module after the function module for checking values, the language-dependent description of the value is copied to the value assignment screen.
    Note
    Please note that the program code must be based on the predefined interfaces. If your program is not based on these interfaces, the program may terminate with a short dump.
    Please note also that the function module cannot take into account any restrictions on allowed values that are due to inheritance or object dependencies, because the function can only read data that is already saved to database tables. The function cannot read current user entries.

    I  have Created two FM Function Module for Checking Values  and Function Module for Possible Entries

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

Maybe you are looking for