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

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

  • 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

  • Error at sales order: Inconsistent characteristic value assignment

    Hi SAPians
    There is a problem in variant configuration. I have configurable materials at sales order level with BOMs and super BOMs. When I am executing the scenario, not able to process further after selecting characteristic values for a configurable material. The error saying " Inconsistent  characteristic value assignment". I checked all the relevant master data, every thing is okay. But I am not able to proceed further. Can any one provide some valuable inputs for this.
    Raksha.

    Hi
    Did u create variant table (CU61) if not plz and try to make it by tick mark of Decision table..
    u can check assignmebt consitance thru CU60 ..if there again blank plz maintain it manually..
    basically wt happened during creation of Characteristics and assignment of value in value tab .. there is indicator ..which influence assignment consistance..
    hope u may get clue.
    correct me if i went wrong..
    thanks
    mk

  • Error in Release strategy : Inconsistent Characteristic Value assignment

    Hello Gurus ,
    Good Day ...
    Need your help in release strategy in purchase order .
    Thanks in advance .......
    Characteristics characteristics value
    R2R_PURCH_ORD_TYPE NB
    R2R_PURCH_GRP1 001
    R2R_PURCH_ORD_VALUE 0,00 - 1000,00 USD
    1001,00 - 2000,00 USD
    2001,00 - 10000,00 USD
    Class assigned char
    Z_CLASS R2R_PURCH_ORD_TYPE
    R2R_PURCH_GRP1
    R2R_PURCH_ORD_VALUE
    Rel grp assigned class
    PH Z_CLASS
    rel grp rel codes
    PH 1 -director/VP
    PH 2 - manager
    PH 3 - buyer
    rel grp rel strategy
    PH A1
    PH A2
    PH A3
    Now in SPRO -
    > define Release Procedures for Purchase ORder -
    > Release Strategies
    PH A1 Release Strategy 1 (rel. prereq , rel statuses, classification , rel simulation ) working fine
    PH A2 Release Strategy 2 (rel. prereq , rel statuses, classification , rel simulation )
    ERROR MSG: INCONSISTENT CHARACTERISTIC VALUE ASSIGNMENT
    DETAILS :
    You want to change the value assigned to a characteristic. However, the change causes inconsistency, so the new value is not allowed.
    The inconsistency may be for the following reasons:
    A precondition or selection condition is violated.
    The characteristic is a single-value characteristic, and different values have been set by constraints, actions, or procedures.
    In classification, inconsistencies occur when you change the value set of a characteristic if objects or classes have already been classified with values from the previous value set.
    Procedure
    Choose Inconsistencies to see what triggered the inconsistency. You can also use the explanation facility for more information.
    Delete the values that triggered the inconsistency.
    You can only change or delete a value or value set that has already been used to classify objects if you delete the existing allocations.
    PH A3 Release Strategy 3 -
    > SAME AS ABOVE
    regards,
    ajay

    Hi,
    Inconsistency  due to different "VALUE" in the Release Strategy & "VALUE" present in the Release Characteristics . Check details with value assignment with designed  Strategies.
    Also keep following VALUE Release Characteristics for  value
    <=1000,00.00 USD
    1000,00.01 USD- 2000,00 .00USD
    2000,00 .01- 10000,00.00 USD
    instead of (0,00 - 1000,00 USD,1001,00 - 2000,00 USD,2001,00 - 10000,00 USD )
    Regards,
    Biju K

  • Differenct between Net Value and Document Value on a sales order

    Can someone please explain what is the difference between the Net Value that we see on the sales order (VA03) and the 'Document Value' thats checked against in Dynamic credit checking?
    Thanks

    In transaction FD32, you maintain credit limit for customer and assign risk category for the customer.
    In transaction OVA8, there are two main types of checks - Static or Dynamic.
    System checks the following for arriving at customers credit status-
    Static credit check - It compares the credit limit assigned to the customer to the total value of open sales orders, plus the total value of open deliveries not yet invoiced, plus the total value of open billing documents not yet passed on to accounting, plus the total value of billing documents that have been passed on to accounting, but which have not yet been paid by the customer.
    Dynamic credit check - It compares customeru2019s credit limit to the total of open sales orders not yet delivered, plus the total value of open deliveries not yet invoiced, plus the total value of open billing documents not yet passed onto accounting, plus the total value of billing documents that have been passed onto accounting, but which have not yet been paid by the customer. In addition you can use Horizon functionality also.
    You can perform additional checks in addition to dynamic or static credit check. One of them is document value check.
    If you check this box then a additional credit check is done when the maximum document value assigned is exceeded. This is useful if business requires that all sales orders above a certain limit are to be blocked.
    In your case, the document value is $0.00.
    So system is not doing any additional credit check.
    It would just do Dynamic or Static credit check with relevant assignment maintained in transaction FD32 for the said customer.

  • Cu 50 Inconsistent characteristic value assignment Message no. C1821

    Dear All
    sorry I come from Taiwan,my English is not well
    I have a question for SAP PP
    I study Make-to Order Production with Variant Configuration
    I read paper Make-to order Quotation Processing with Vaniant Procing(663)
    and In accordance with the file operations
    but when i According to cu50 display an error message:
    Inconsistent characteristic value assignment,Message no. C1821
    creat pland order in tcode co08 display an error message:
    No valid BOM exists
    i choices "no" display an error message:Error or warning occurred during master data transfer
    I do not know how to resolve
    Please help me  thank you very much

    Dear All
    Thank you for your help
    I found the problem
    1.cu50 error message Inconsistent characteristic value assignment,Message no. C1821
    ans: the paper Bast Practices Make-to-Order Quotation Processing with Variant Pricing(663) , page 85
    Dependency name : YI_PC_YI_005_SELE_OPT
    Syntax : $root.YI_004_ADD_OPT='01'
    2.creat pland order in tcode co08 display an error message:No valid BOM exists
    ans :
    a.Tcode cu42 , in BOM application select SD01 for Production-General
    b. IMG OPL8 BOM Application sele SD01

  • Assigning a Sales Order Number to a Purchase Order

    My company has a requirement that for every purchase order we need to identify what sales order was created to generate the PR.
    I have found that by using the Account Assignment C - Sales Order, this opens the "Account Assignment" Tab and the fields for Sales order, item, and schedule Line.
    I have saved the PO and now am trying to receive the parts into inventory.  When doing so, the inventory needs to post to our inventory GL account, in our case is 135075.  By NOT assigning the GL with the sales order in the PO it doesn't post to this account it posts to a different GL account.
    How do I go about using the "Sales Order" field in the purchase order so I can record which sales order the line item of the PO corresponds to, and when receiving the inventory into stock have it post to the correct GL account?
    Thanks,
    Karen

    The company I work for is a distributor, and doing a Make to Order order type would not be in the best business practice for our company.  We tend to purchase stock for multiple orders and put them in inventory to be sold.  We are looking for a way to "document" what sales order the purchase order line item is being bought for, and sometimes their our multiple lines.
    I understand what you are saying regarding posting to an stock GL vs a consumption GL.
    I am going to research further and see how we can post to a consumption GL and then move the remaining stock over to a stock GL account after we have sold what we have purchased and received.
    I was able to get the receipt posted to the GL 135075 by taking off the "post automatically" indicator in the configuration of the GL account, but this then posed problems when doing other inventory postings such as cycle counting or moving inventory.
    Thank you,
    Karen

  • Rounding off value problem in sales order

    Hi All,
    This is related to a rounding off value problem in sales order.
    The problem is described by an example which is as follows -
    Selling Price of Material A = Rs. 176.76
    Excise charged = Rs. 21.80
    Total Price = Rs.176.76 + Rs.21.80 = Rs. 198.56
    On this total Trade Discount (ZDTD) having access sequence,is calculated  at the rate of 4% = Rs. 7.94
    But the condition base value after the discount is showing Rs.198.60 instead of Rs.198.56
    I want the system to reflect the value as Rs.198.56 intact and it should not round up to the nearest value i.e. Rs. 198.60
    Why is this happening? Is it possible to reflect the exact value? If yes what is needed to be done?
    The commercial round off is activated for the DIFF Condition Type.
    Looking forward to some valuable suggestions.
    Thanks & Regards
    Priyanka Mitra

    Hi Ramesh,
    Thanks for your suggestion but the problem has been solved by me.
    Regards
    Priyanka Mitra

  • How to activate FM Account assignment in Sales Order

    Dear All,
    How to activate FM Account assignment in Sales Order at item level in account assignment category.
    Plz provide some solution for the same.
    Thanks & Regards,
    Pankaj

    Hi,
    Thanks for your reply.
    I am not asking of account assignment group for material.
    My problem is when i am creating Sales Order at item level in Account assignment category there is one field for Fund Mangement account assignment grp.
    I want to activate this field and i have to enter FM area in that field.
    Plz send some solution for the same.
    Thanks & regards,
    Pankaj

  • Table of accounting assignment in sales order

    Hi,
    can anyone show me the table where i can find the accounting assignment in sales-oder position.
    We have some position which have an entry on accounting assignment in sales order which is an quotation.
    thanks.
    Regards, Dieter

    Hello Dieter,
    Is it account assignment category then it is available in VBAP-KNTTP
    Regards
    Farzan

  • Addl Account assignment in Sales order

    We are in Make-to_order Scenario.
    Following is an item which as generated from a SD invoice:
    marketing and management Free : 1300
    In the additional account assignment data, sales order = 1500989
    Cost centre & Internal order fields are blank.
    Can I assign a default Cost centre for this GL account through OKB9 ?  Will it work ?

    Hi Nikki
    Cost center does not work for revenue accounts...  You can assign IO in the additional acct assignments tab
    However, by default the account assignment is to PSG if you have COPA activated
    br, Ajay M

  • WBS Element ( Billing element ) assignment  at sales order header level

    HI,
    There is provision of assign WBS Element at sales order header as well as item level , If Project WBS Element is assigned for each line item delivery  and stock updating is happening from the project, But WBSE will assign at sales order Header  system will not allowing to create project delivery( moment type 601Q), and stock updation ftom project.
    Please let me know how this will happen ,
    Regards,
    Gangi
    Edited by: Gangi Reddy Botchu on Jul 7, 2008 4:50 PM

    SPRO - SD - Billing - Billing Plan - the first 5 config nodes (Define Billing Plan types / Define Date descriptions / Assign Date categories / Maintain Date Proposals / Assign Billing Plan types to Sales Doc types) are applicable to you.
    this is pretty tranparent for a reference.
    What else is required?

  • 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

  • Inconsistent characteristic value assignment

    Hi
    When I am trying to change the value of the characteristic for relase strategy  ; the system is giving me error
    "Inconsistent characteristic value assignment"
    Kindly reply me

    Check this answered link:
    Inconsistent characteristic value assignment
    Re: PO Release Strategy on Value Based

Maybe you are looking for