Create BW Hierarchy - No characteristic values shown

Hi guys,
I am trying to create a BW hierarchy manually, as described in the link below.
http://help.sap.com/saphelp_nw70/helpdata/en/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm
I face this little problem where sometimes, there are no basic Characteristic values to be selected!
All I can see in the list is "#". FYI, texts has been loaded.
1 External Characteristic (which is also an attribute of the InfoObject) is included in the hierarchy.
Anyone face this before?
SJ

1. You need to <u>load Master Data Before going to CreateHierarchy in BW</u>.
2. If you are using Charecterstic and External Charecterstic, you need to work with Charecterstic Nodes not Text Nodes.
If you are already loaded master Data into your Infoobject, once you click on Insert Charecterstic Node, you will see Charecterstic Values.
Ex: Customer Io which has Sales Org as Attribute. (Sales Organization is external Hierarchy)
You need to load Customer Master Data before creating Hierarchy.
1. Create Customer Herarchy in RSH1 on Customer IO or from RSD1.
2. select Sales Org as external Charecterstic.
3. Select your Customer Hierarchy super Node... click on Insert Charecterstic Node.. then you need to select Sales Org Values.
4. Place the Cursor on one Sales Org... again click on Insert Charecterstic Node... which will show list of Charecterstic Values for Customer. pick required ones.
Save and Activate your Hierarchy.
Nagesh Ganisetti.
Assign points if it helps.

Similar Messages

  • Transfer CO-PA Characteristic Values

    Hi All,
    I faces the situation that I need to manual create huge data of Characteristic Values every client.
    Is there any method to transfer the CO-PA Characteristic Values from source client to target client?
    Thank you in advance.

    Yes with tx ke3i.

  • How to Create and External Hierarchy and group values of IO in node

    Good morning
    BI 7:
    Please give me guidance on the following?
    I need to either to restrict a characteristic in a query to more than 800 values OR exclude values where it contains the pattern 'Z7' and 'Z8'. There are thousands of values which contains the pattern and they are not listed in such a way that I can exclude them as a value range, thus I would have to include all the values I want into the restriction, which is more than 800. An error displays when I check the query:
    ""In the structural component Warranty Damage Code, characteristic ZWR_DMGC is restricted to 838 values. This number is very large and will probably meet with technical limitations""
    The proposed solution is:
    ""Create an external hierarchy for characteristic ZWR_DMGC and group the 838 values in a hierarchy node. You can then work with the node instead of the 838 individual values.
    Alternatively, you can define a corresponding navigation attribute for ZWR_DMGC""
    I know where to create the hierarchy, but I am confused how to only include the values of the applicable IO where pattern contains 'Z7' and 'Z8'.......??
    The following are some of the steps proposed in a related thread, but I am loosing it at step 7.
    5. Confirm your entries. The Maintain Hierarchy screen appears. You can define the structure of a hierarchy here. ok
    6. To create a hierarchy node, you first need to choose an insertion mode: Insert as First Child or Insert As Next Neighbor (see Hierarchy Editing Functions). I selected first child
    7. Choose the type of node you want to create: Text Node, Characteristic Node, <Hierarchy Basic Characteristic Node> or Interval (see Hierarchy Nodes) *this is where I am lost, which should I select to list values with pattern ' *Z7' and ' Z8' in a node or two
    8. Repeat this procedure until the hierarchy structure has been set. For more information, see Modeling Nodes and Leaves.
    A hierarchy can contain 50,000-100,000 leaves at most. If your hierarchy is larger, you should insert a level that is used as a navigation attribute or preferably as a separate characteristic in the dimension table.
    9. You can use Level Maintenance and Hierarchy Attributes to set how the hierarchy is to be displayed and processed in reporting (see Level Maintenance and Hierarchy Attributes).
    10. Save the hierarchy.
    Your assistance will be appreciated.

    Hierarchy not used in this case. Could not fnd an answer.

  • 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

  • Creating A hierarchy on a characteristic.

    Hi,
    I am in process of creating a hierarchy. the problem I face is with number of hits getting displayed in the input help. I have got an overall of morethan 1500 entries, but the input help is giving me only 500 hits at a time.
    How can I get the full list of input help.
    Regards,
    Naveen.A

    When you have the list of value, choese restrict value botton and you can choose the number of hit to select.
    Regards

  • Create different hierarchy based on Dimension values

    I have a dimension called period. This dimension is having 4 different types of periods. The period table looks as below. I need to create 4 different hierarchies for these 4 types of periods based on l1 to l5 values. But all these values are in the same
    table. Is it possible in SSAS? If so please let me know how can I do it. 

    If i understand it correctly, you want one hierarchy for one row, then you need to flat the table in the view and then you can create those hierarchy. But it is no different from having one hierarchy with the table you have. your hierarchy is going to look
    like "Priod5"  <- "Priod4" <- "Priod3" <- "Priod2" <- "Priod1". this hierarchy will have all the values. Don't forget to use the composite key for each attribute except key attribute.
    hope this is helpful.
    prajwal kumar potula

  • PR created with a reference PR copied the reference material configuration( Characteristic Values).

    Hello,
    I have created a PR with reference to another PR. After adopting I changed the material and saved. After saving, when I checked the variant configuration at the line item level (Characteristic values), its showing the characteristic values of the material of the reference PR. It should be showing the details of the new material which I have used but, its showing the variant configuration of the material used in the PR which I used as reference.
    Ideally, these values has to be changed when I changed the material in the newly created PR.  What might have gone wrong here?
    Example:  PR- Purchase Requisition
                   Mat - Material.
    PR1 contains Mat1.
    I am adopting PR1 and creating PR2 with Mat2.
    After saving, when I check the variant configuration, classification values are from Mat1. I was expecting the values from Mat2 as I have Mat2 in PR2.
    Any suggestions would be of great help.
    Thanks in advance!
    Regards,
    Shaheen.

    Hi,
       Please check whether classification data has been maintained for the second material. If the configuration data doesnt exist for the second material, system cant redetermine and transfer. Refr the note: 588117 - FAQ: Configurable materials in purchasing Question number 5.
       If the configuration data exists and still the data is not changed, refer the note:  920648 - Error in the configuration when you copy PReq item  or 596994 - ME21N/ME51N: Configuration not determined again based on your release.
    Regards,
    AKPT

  • Create COPA Characteristic Value groups

    Dear All
    We need to create copa characteristic value groups as recivers in COPA assesment. Where can i do the grouping?
    Thanks
    Gayani

    Thanks Paolo...
    Your answer resolved my issue...
    Thanks

  • 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

  • Characterist Value Propagation on Multi-Level

    Hello All.
    I need restrict a characteristic propagation on my multi-level scenary.
    Anyone knows how do that?
    In ECC works fine.
    Version:
    ECC 6.0
    SCM 5.0
    Best Regards
    Marcelo

    More Information..
    The hierarchy is:
    Finished Product > P1 -> P2 -> P3 - > Raw Material.
    There is a PlOrd(R) in P3 material of 4500kg. But This order was created in  ECC6. When CIF creates the order, only 2 characteristics values was migrated. This is correct!!!.
    Well, when i run MRP all characteristic value from the finished product migrated to lower level. Characteristics like packing.
    The dependent demand of lower lever have 4 characteristics from Finished Product.
    SCM see the PlOrd(R), but because this order has only 2 characteristics and depend demand has 4. SCM creates another PlOrder ie Surplus.
    This is why i need to restrict the propagation of the characteristics.
    Thank you and best regards.
    Edited by: Marcelo Kayro Quintão on Mar 11, 2011 12:49 PM

  • 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

  • Condition type value updation using characteristic value in sales order

    Hi Experts,
    We are implementing SAP for one of our Spain client. In that one of the Legal requirements is, whenever they are selling the finished products to domestic customers who contain OIL as one of the component then, some additional cost needs to be calculated and collected from customer and which needs to be paid back to Spain Government every month on Region basis.
           If OIL is not a component to produce the finished product then, not required to charge the customer additionally.
    The OIL content used to produce every finished product will vary based on product characteristic value. Meaning, for some finished product the OIL used will be 2.2 KG and for some products it will be 3.5, 4.3 KG and etc.
    Since various combinations of products are available for the client, during sales order creation we are planning to update some special characteristic which the data flow from u201CVariant Tableu201D. In the variant table we are going to maintain the OIL Quantity required making finished product.
    But we are not sure how to activate a new condition type with the value fetched in the special characteristic. This new condition type needs to be activated based on this characteristic value and multiplied with total order quantity and price to charge from customer.
    Example, the special characteristic fetched the value of 2.2 KG based on variant table. Total Order quantity is 10 PC and charge is 0.06 EURO per KG. in this case, (2.2 x 10 ) x 0.06 EURO = 1.32 EURO
    I need the expert opinion how to activate the new condition type based on characteristic value and achieve the above requirement.
    Thanks in advance.
    Warm Regards,
    VEL

    Hello,
    I have replicated the whole requirememt in IDES and getting the price calculation as needed but the only issue with the Conversion factor for the condition type. Either you need to maintian the conv factor in material master or need to enter manually for the condition type in SO. Some how you have to maintain the conversion factor to calculate the price for the condition type in different unit.
    For easy of understanding Lets make the whole requirement in 2 parts
    Part - 1
    Oil qty calculation. For convenience sake I have taken oil qty also in TO
    1) Created a num char OIL_QTY1 with length 9 and decimal places 5 and UOM as TO
    2) Created Variant table to infer the OIL qty in TO per piece of finished prod ( This oil qty data may be depends on various factors). For certain Finished products the oil qty may be 0 or blank
    3) Created a REF char SO_QTY  to pull the SO qty to configuration and add this char in class 300(Table:VBAP,Field :KWMENG)
    4) Created another char SO_OIL_QTY  (Num with length 9 and decimal places 5 and UOM as TO)
    5) Created a PROCEDURE say PROC_SO_OIL_QTY with code
    *$self.SO_OIL_QTY = $self.OIL_QTY1 * $self.SO_QTY*
    6) Create another PROCEDURE as mentioned earlier with modified code
    $SELF.A_VARCOND = 'TEST_001' if OIL_QTY1 specified,
    $SET_PRICING_FACTOR ($SELF,A_VARCOND,'TEST_001', SO_OIL_QTY)
    Note: Maintain proper seq of the procedures in profile. The Qty cal proc should be before the price related procedures.
    PART-2
    1) For the condition type maintained 60 EUR per TO (0.06 EUR per KG)
    Now if you create SO for the Finished product of 10 PC
    the Char values will be
    OIL_QTY1  = 0.00022 TO (inferred from Variant table th proc)
    SO_QTY    = 10
    SO_OIL_QTY = 0.0022 TO
    Get into conditions tab
    Here Condition type ZSIG will be displayed as error with Amount 60 EUR per TO and condition value will be blank. Just enter value 1 in the col NumC and CCon fields.
    Now the Condition value will appear as 1.32 EUR.
    Hope this gives some more clarity
    Regards
    Brahmaji D

  • Auto Update of characteristic values in PO from SRM.

    Hi,
    For Configurable material we have characteristics values.
    Material is configurable material with material type as services.
    Same ECC material is replicate in SRM.
    Create Shopping cart in portal SRM EBP for Multiple line item for material. Each material item will have different characteristics value.
    Currently User attaching excel sheet with different characteristic value in Shopping cart.
    Once Shopping cart no is created and Shopping cart no goes for approval.
    Once approved, PR is created automatically.
    Attached document is available in PR.
    Buyer has to maintain manually characteristics value for material in Purchase order (PO) for each material item.
    Is any way to Update Characteristics values in PR automatically when saving?
    Regards,
    Swapnil

    check if the condition is marked as statstical one in the pricing procedure

Maybe you are looking for