What is meant by characteristic  values

hi
what is meant by characteristic  values
i have seen some tables like AUSP, these r for characteristic values.
can any one explain me that

Hi,
Characteristic value variables are parameters for a query. You set these variables in the query definition, and they are filled with values when you execute the query. They act as placeholders for characteristic values, and are processed using any processing type.
In some cases, it is possible to use variables for texts, as well as for characteristic values.
If you specify a variable as a characteristic value, for example, you do not have to give a text for the characteristic value straight away. Instead, you are able to fill the text field dynamically, according to the characteristic that you used for the variable when you inserted the query into the workbook. Define a text variable with automatic replacement for this.
Use
You need to use a variable for characteristic values, if you want to specify one or more characteristic values that you do not want to be included permanently in the query definition. A characteristic value variable is the placeholder for either a single value, an interval, or a set of selection options. With selection options, it is possible to make several restrictions, meaning that you are able to combine single values and intervals (7 and 3 to 19 and 43, for example). Characteristic value variables for intervals and selection options are available with the processing type Manual entry / Proposed value and Customer Exit.
Thanks,
Khushbu.

Similar Messages

  • What to set authorization on characteristic value

    HI team I want to set a authorization on characteristic value, to be displayed in Bex report depending on user accessing that report
    Say : I have one report which show data about company code. I want to set authorization on characteristic value of Company code , for eg for USER 1 - he should see ony C001 and C002, and USER2 should see C003 , C004 etc.
    Please guide me in step by step approch ....
    Which authorization objetc should be used.
    Regards
    Ashutosh D

    Hi,
    First step towards authorization is to make your InfoObject (Company Code) as authorization relevant in the tab Business Explorer.
    Once this is done, create Analysis Authorizations in transaction RSECADMIN with the following variables.
    0TCAACTVT - *( or you can give the activities to be restricted)
    0TCAIPROV - *
    0TCAVALID - *
    0COMP_CODE - C001 & C002
    Now assign the analysis auth in the role under the Auth object S_RS_AUTH.
    Now assign this role for user1.
    Similarly create another Analysis auth for company code C003 & C004 and assign that role to user2
    Regards,
    Gaurav

  • What is meant by cost element

    hi
    what is meant by cost element

    HI.
    Differentiation of Cost Elements
    Use
    In call management, it is necessary to differentiate cost elements further for the settlement of orders in profitability analysis. Both the costs incurred and the sales deductions are classified according to their source, and assigned to the appropriate cost elements. For example, the following costs are differentiated:
    Sales costs
    Warranty costs
    Good will costs
    Sales deductions due to warranty
    Sales deductions due to good will
    The differentiation of costs and sales deductions enables you to assess more accurately the profitability of your products.
    Integration
    The differentiation of cost elements is only of use if the service orders are settled in profitability analysis.
    Prerequisites
    Resource-related billing must be performed for service orders.
    You must have defined the accounting indicator in Customizing for Plant Maintenance.
    When you create a service order, you define the accounting indicator in the header, under administrative data. Currently it is only possible to have one accounting indicator per order.
    Once the order is released, the accounting indicator can no longer be changed in the order header.
    Features
    When actual postings are made for a service order, the system creates CO single records and a CO totals record. When doing this, it copies the accounting indicator defined in the order header, and enters it in the origin of the totals or single records.
    In addition to the variance class and the cost element, the accounting indicator is a further characteristic of the PA transfer structure.
    The transfer of the accounting indicator to the origin also makes it possible during the settlement of a service order in profitability analysis, to navigate more specifically in the PA transfer structure. The costs and sales deductions for warranty, good will, and sales are entered in the respective value fields.
    Reward all helpfull answers.
    Regards.
    Jay

  • What is meant by referential integrity

    hi
    what is meant by referential integrity

    Hi,
    Referential integrity is the property that guarantees that values from one column depend on values from another column. This property is enforced through integrity constraints.
    If you set this flag a check for referential integrity is performed for this InfoObject, against the master data table or ODS object. The InfoObject is checked for valid characteristic values.
    It is used when v r doing Flexi update...
    Prerequisites for checking for referential integrity:
    Data is updated flexibly
    You have activated error handling in the BW scheduler (Tab page Update)
    On the Update tab page in the BW scheduler, you have selected the option Always update data, even when no master data exists for the data.
    send ur id, i will send u screen shot of ref.integrity
    regards
    reena

  • Populate Batch characteristic values in create sales order BAPI

    Can anybody help me in populating the batch characteristic values using BAPI_SALESORDER_CREATEFROMDAT2?
    I have checked the related notes provided by SAP, like, 567348 but it will be great if someone can send some code snippet on this.

      Subramanian, Brad and Raja.
      Thanks for your suggestions its were useful, with
      these i can resolve my problem.
       !!! Best Regards !!!
    Raja
      I used the se37 to test bapis, is more easy and fast !!
      and you can save data like variant, and you can simulate the real execution without write any code abap,
    and re-process the times that you need,
    when you know what fields you need you write your abap code faster.
       Thanks !!!
    Message was edited by: Noemi Huerta

  • 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

  • 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

  • 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

  • Copy BOM Component Characteristic value in material PR created by MRP Run

    Dear Gurus,
    My requirement is I have materials like thread to maintain color characteristic i have create class - color- class type is 023 , now i want user should able to maintain characteristic value in BOM component (thread) of semifinish material.  FG , SFG  are not having any characteristic.
    Now in PR and PO we can maintain characteristic value in Material Data --->Configuration tab , Configuration tab will come only when there is tick in material is configurable at material basic data 2 view of thread and in CU41 I have to maintain material for class type 300 - Variant , then in class assignment i have select class type 300 and 023 both and maintain class , both are having same characteristic please make me correct if i am doing wrong process, if i am not maintaining class assignment 300 in CU41, in manual PO system not allowing to enter characteristic value in configuration tab . so i maintain both class assignment 300 and 023.
      Now for manual PR and PO system showing configuration tab and from PO configuration tab characteristic value is coming in MIGO automatically but when i am running MRP for finish material the auto PR generated by system for material thread is not showing configuration tab in Material Data of PR. I have maintain characteristic value in BOM --->Extra--->Batch Classification. Please guide me how to archive this.
    Thanks & Regards
    Akshay.

    Akshay kukde,
    Still i am unable to understand the reason for maintaining a characterstic value for a batch through BOM, I hope you are not changing BOM for every purchase order ?
    can you explain what you expect by maintaing this one value for batch characterstic?
    you can have many other simple option like
    1) Create a material with colour included in it ex, Thread_red, Thread _green etc and use them in BOM
    2) Use text in BOM to hold this discription for colour
    3) Use batch management, class 023 in material master classification , defalut value for colour, purchase order will be created and while doing GR you can change in colur if its different then default you set earlier.
    Akshay kukde wrote:
    if i am creating PR Manually -ME51N , system showing configuration tab , where i can maintain characteristic value , which then reflecting in PO and from PO to MIGO
    The above scenario I have tried by maintaining class type 023 and same characteristic in material Master. but result is same for auto generate PR by MRP- configuration tab is missing.
    My requirement in this case is characteristic value should flow from BOM to PR generated by MRP.
    when you manualy create PR you Thread material is consider to be a configurable material and thats why you are able to input configuration value, otherwise as soon as you put this configurable material inside a BOM of normal materila it loost its configuration feature, if you want you can create your parent material also as configurable material, assign same class to it and create configuration profile and take MRP run this time you will get PR with configuration tab as your thread get configuration derived from parent.
    Hope above details may help you.
    Check and reply, also mark replies helpful if it helps you.
    Thanks
    Ritesh

  • Characteristic Value Assignment in Sales order

    Hi Pals,
    I am using the Variant configuration scenario in the sales order. My problem is, when ever i try creating a new sales order and enter a material, it suppose to display the Characteristic Value Assignment screen but for me it is showing the "Display Characteristic Values" Screen. Because of this i am unable to enter the data at the sales order level. what might be the problem for this case.
    Kindly help me out in this issue.
    Thanks & Regards,
    Srinivas.D

    Dear,
    I hope the following link will help u in giving a good understanding of Characteristic values
    help.sap.com/printdocu/core/Print46c/en/data/pdf/CACLCHR/CACLCHR.pdf
    Regards,
    R.brahmankar

  • Copy characteristic value(class 023 ) from the material master to the batch

    Dear All,
    Is there a way to copy the characteristic value (class 123) from material master to the batch master automatically once we create a batch of that material
    I tried to create a dependency, but didnu2019t know what to write in the dependency editor
    Please advise

    I dont know if its possible in standard,  you can try and create a reference batch, and use the below user exit I found in SAP library :
    Set Up Customer Exit for Determining Source Batch
    You can use function module exit EXIT_SAPLV01Z_011 in SAP enhancement SAPLV1ZN when assigning characteristic values to batches. You use this to specify a reference batch when creating a new batch with the central function module VB_CREATE_BATCH.
    Further notes
    The reference batch must always be specified completely. This means the reference material, source batch and reference plant details must have been entered if the batch is determined at plant level.
    All batch master data is copied. If the batch is classified in this enhancement, the values assigned to the corresponding characteristics are copied.
    In the exit, you can use a communication structure with the application data for the respective business transaction (for example, plant or material type). If you require further information, you must obtain it yourself in one of the user exits (such as time, user name, or date, for example).

  • Characteristic values in BAPI_SALESORDER_CHANGE

    Hi,
    I want to add new configurable item in existing sales order with charactersitic values.
    Iam using bapi BAPI_SALESORDER_CHANGE.
    Iam now able to insert configurable item in existing sales order.
    But the characteristic values are not getting stored.
    Latest code is attached. What else is missing for storing characteristic values ?
    select maximum item number in sales order
    SELECT MAX( POSNR ) FROM VBAP CLIENT SPECIFIED
    INTO MAX_POSNR
    WHERE MANDT = SY-MANDT AND
    VBELN = I_SORDER.
    TMP_POSNR = MAX_POSNR + 10.
    WA_HDRX-UPDATEFLAG = 'U'.      "update
    SALES_DOC = I_SORDER.
    item data
    WA_ITEM-ITM_NUMBER = TMP_POSNR.
    WA_ITEM-MATERIAL   = 'LEFTEYE'.
    WA_ITEM-PLANT      = I_STORE.
    WA_ITEM-SHIP_POINT = I_STORE.
    APPEND WA_ITEM TO IT_ITEM.
    WA_ITEMX-ITM_NUMBER = TMP_POSNR.
    WA_ITEMX-UPDATEFLAG = 'I'.      "add
    WA_ITEMX-MATERIAL   = 'X'.
    WA_ITEMX-PLANT      = 'X'.
    WA_ITEMX-SHIP_POINT = 'X'.
    APPEND WA_ITEMX TO IT_ITEMX.
    Schedule lines
    WA_SCHD-ITM_NUMBER = TMP_POSNR.
    WA_SCHD-SCHED_LINE = TMP_POSNR.
    WA_SCHD-REQ_DATE   = SY-DATUM.
    WA_SCHD-REQ_QTY    = 1.
    WA_SCHD-SCHED_TYPE = 'CN'.
    APPEND WA_SCHD TO IT_SCHD.
    WA_SCHDX-ITM_NUMBER = TMP_POSNR.
    WA_SCHDX-SCHED_LINE = TMP_POSNR.
    WA_SCHDX-REQ_DATE   = 'X'.
    WA_SCHDX-REQ_QTY    = 'X'.
    WA_SCHDX-SCHED_TYPE = 'X'.
    APPEND WA_SCHDX TO IT_SCHDX.
    config & characteristic values
    WA_VALUE-CONFIG_ID = '000001'.
    WA_VALUE-INST_ID   = '00000001'.
    WA_VALUE-CHARC     = 'PRES_DIST_SPH'.
    WA_VALUE-VALUE     = '3.2'.
    APPEND WA_VALUE TO IT_VALUE.
    WA_INST-CONFIG_ID  = '000001'.
    WA_INST-INST_ID    = '00000001'.
    WA_INST-OBJ_TYPE   = 'MARA'.
    WA_INST-CLASS_TYPE = '300'.
    WA_INST-OBJ_KEY    = 'LEFTEYE'.
    WA_INST-QUANTITY   = 1.
    WA_INST-QUANTITY_UNIT = 'NO'.
    APPEND WA_INST TO IT_INST.
    WA_REF-POSEX     = TMP_POSNR.
    WA_REF-CONFIG_ID = '000001'.
    WA_REF-ROOT_ID   = '00000001'.
    APPEND WA_REF TO IT_REF.
    WA_PART-CONFIG_ID  = '000001'.
    WA_PART-PARENT_ID  = '00000001'.
    WA_PART-INST_ID    = '00000001'.
    WA_PART-OBJ_TYPE   = 'MARA'.
    WA_PART-CLASS_TYPE = '300'.
    WA_PART-OBJ_KEY    = 'LEFTEYE'.
    APPEND WA_PART TO IT_PART.
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
    EXPORTING
      SALESDOCUMENT      = SALES_DOC
      ORDER_HEADER_INX   = WA_HDRX
    TABLES
      RETURN                         = IT_RET
    ORDER_ITEM_IN             = IT_ITEM
    ORDER_ITEM_INX            = IT_ITEMX
    ORDER_CFGS_REF         = IT_REF
    ORDER_CFGS_PART_OF = IT_PART
    ORDER_CFGS_INST        = IT_INST
    ORDER_CFGS_VALUE    = IT_VALUE
    SCHEDULE_LINES          = IT_SCHD
    SCHEDULE_LINESX        = IT_SCHDX.
    READ TABLE IT_RET INTO WA_RET WITH KEY TYPE = 'E'.
    IF SY-SUBRC = 0.
    CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
    ELSE.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    ENDIF.
    I get the following messages from BAPI :
    ORDER_HEADER_IN has been processed successfully.
    ITEM_IN has been processed successfully
    The sales document is not yet complete: Edit data
    TIL-Direct Sales TINDC01372 has been saved
    What else is missing ? Any help is appreciated.
    thanks,
    Nagarajan.J

    Hello Nagarajan,
    I have used this BAPI in my last task. You are passing the values correctly. I will tell you why it is giving like that message.
    Whenever we will create a sales order in VA01 transaction, you will get a message like "The sales order is not complete, would you like to EDIT" while saving the sales order.... This is because of not providing complete data required for careation of sales order.
    Try to implement the changes manually in VA02, if you get same errors, then you can find your code is correct.
    Even I got same type of messages when changing a sales order to change the Rejection Reason for the items.
    Best Regards,
    Sasidhar Reddy Matli.
    Edited by: Sasidhar Reddy Matli on Jul 31, 2008 2:20 PM

  • Best practice for updating ATWRT (Characteristic Value) in AUSP

    I've notice that when we change the Characteristic Value of a Classification, that it does not update in the MM record. We have to go into MM02 for each material number that references Char Value and manually change it for row in AUSP to get updated.
    Should i just create a report to Loop through and update table AUSP directly? Or is there a better way to do this via a function or BAPI etc? Wanting to know what best practice is recommended.

    Hi Scott
    You can use a BAPI to do that.
    Check the following thread:
    BAPI to update characteristics in Material master?
    BR
    Caetano

  • Dump when trying to display characteristic values in QUERY DESIGNER

    Hi Experts,
    Life seems to become a struggle with 7.0 for me :-(.
    My current problem:
    If I try to display characteristic values  in Query Designer (left section of screnn, wthin dimensions) system dumps frequently.
    It's that kind of dump, that doen't help really (to my oponion)_
    What happened?
        The exception 'CX_RSR_X_MESSAGE' was raised, but it was not caught anywhere
         along
        the call hierarchy.
        Since exceptions represent error situations and this error was not
        adequately responded to, the running ABAP program
         'CL_RSBOLAP_BICS_SERVICES======CP' has to be
        terminated.
    How to correct the error
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
        "CL_RSBOLAP_BICS_SERVICES======CP" or "CL_RSBOLAP_BICS_SERVICES======CM003"
        "HANDLE_UNCAUGHT_EXCEPTION"
    ... etc.
    BW 79, SP21
    GUI 7100.4.14.3136
    Any ideas?
    Thanks in Advance and Regards
    Joe

    Hi Vikram,
    Thanks for reply. Reinstalling GUI was successful, but - error still occurs. ..
    Regards
    Joe
    Edited by: J.F.B. on May 28, 2010 3:02 PM

  • All Dates displayed for "Characteristic Values" in Query Designer

    Hello Experts,
    We are on BI 7.0, level 13.  I am having an issue within the Query Designer with regards to dates.  I have a write-optimized DSO that contains 3 date fields (for example, ZDATE1, ZDATE2, and ZDATE3).  Each date InfoObject is of type DATS so the system automatically creates it with reference to 0DATE. 
    When I create a query in the Query Designer, on the left hand side, I expand the "Characteristic Values" node under each date field.  The Query Designer shows the same list of values for each of the 3 dates even though they are not valid values posted in the DSO for those fields.
    For example, ZDATE1 only has 1 value posted in the DSO (01/01/2005).
    ZDATE2 only has 1 value posted in the DSO (01/01/2006).
    ZDATE3 only has 1 value posted in the DSO (01/01/2007).
    Bute when I expand the "Characteristic Values" node in the Query Designer, I see ALL THREE values under each date field.  I would expect to only see the 1 value posted for the InfoObject in the DSO.  Also note that each InfoObject is defined to show "Only posted values in InfoProvider".
    It appears that Query Designer will show all values for the reference InfoObject 0DATE instead of the ones posted to the actual InfoObject in the DSO.  If I delete the data in the DSO, the Characteristic Values list still remains because they exist in 0DATE.  Anyone encounter this before?  How can I get the Characteristic Values list to only show posted values for that InfObject?
    Thanks for your help!
    J

    Thanks for the response.  I went into the DSO and right clicked on each of the Date fields.  I looked at the Provider-specific properties and there is the option for "Query Exec.FilterVal" which only restricts what values appear when restricting during execution, not during query creation.
    Is there someplace else I should look or someplace else I can make change to only display posted dates when creating a query?  Thanks!

Maybe you are looking for