Variant configuration information transfer

Dear Gurus:
Here I faced a special scenario.
Our customer built huge vehicle and we will supply core components to them. For these core components, we already start vairant configuration, that means,for one core components, if the vehicle configuration is changed on customer side, our core components' configuration will be impact as well. As before, the customer's requirement is not large and we could create VC sale order manually,unfortunately, due to customer S&OP, they will increase their forecast fast in next year and we would like to accept their ordre automatically by system like EDI function, but I could not get any assisstant from SAP help document. I would like to get more insight here.
Thanks.
Dick H.

Hi Dick
Greetings
As far as VC is concerned  selection of characteristics happens only at the time of sales order and this further triggers MRP run as you know.
So If you are recieving inputs from customer through EDI you need to run BAPI to generate Sales order in background.
For configuration of material thrugh characteristics  pl check  parameter OrderCfgsValue  and dictionary object  BAPICUVAL.
check in T.code BAPI  for SD  >> Sales Order >> create Sales order >> create from Data1 or 2 .
You need to work with ABAP developer and PP consultant to finalize on BAPI Function modules to be built.
I hope this helps ,
I will appreciate if fellow consultants also put on their views,
Regards
Mandar

Similar Messages

  • Creation of sales order with Variant configuration info

    Hi friends,
       I am creating sales order along with Variant configuration data. We have 3 level BOM structure.
    I am using BAPI_SALESORDER_CREATEFROMDAT2 and filling in ORDER_CFGS_REF, ORDER_CFGS_INST, ORDER_CFGS_PART_OF ORDER_CFGS_VALUE, ORDER_CFGS_REFINST
    tables exactly the same way BAPISDORDER_GETDETAILEDLIST FM returns.
    Sales order is being created with no variant configuration information.(Not in the header level atleast)
      Can any one help me on this.
    Thanks
    Seshagiri

    Updating Variant Configuration data for SO item became little tricky for us in an ongoing implementation. After spending some hours investigating the correct combination of data to pass, we were able to post the document correctly. As no detailed documentation is available online for this scenario, I hope this post will help community for similar requirements. J
    For updating Variant configuration (VC) data for Sales order item, we need to populate below tables of standard FM or BAPI (e.g. SD_SALESDOCUMENT_CREATE).
    Normally the standard FM or BAPI does not return any error messages in case configuration data is not updated successfully.
    ·         SALES_SCHEDULES_IN: The required date field should be populated with appropriate value (REQ_DATE).
    ·         SALES_ITEMS_IN: Field PO_ITM_NO should be populated with appropriate value.
    ·         SALES_CFGS_REF Table:
    1.       This table should have 1 record per item.
    2.       Combination of CONFIG_ID and ROOT_ID should be unique across line items.
    POSEX
    000010
    CONFIG_ID
    000001
    ROOT_ID
    00000001
    SCE
    1
    COMPLETE
    T
    CONSISTENT
    T
    CBASE_ID_TYPE
    G
    ·         SALES_CFGS_INST:
    1.       This table should have 1 record per item.
    2.       Combination of CONFIG_ID and INST_ID should be unique across line items.
    CONFIG_ID
    000001
    INST_ID
    00000001
    OBJ_TYPE
    MARA
    CLASS_TYPE
    300
    OBJ_KEY
    MATNR value
    QUANTITY
    Quantity value
    QUANTITY_UNIT
    Quantity Unit
    COMPLETE
    T
    CONSISTENT
    T
    OBJECT_GUID
    MATNR value
    PERSIST_ID_TYPE
    G
    ·         SALES_CFGS_VALUE:
    1.       Combination of CONFIG_ID and INST_ID should be unique across line items.
    2.       We can have multiple characteristics for a material. In that case appropriate records should be inserted in this table. Note that CONFIG_ID and INST_ID should be same for all the rows you insert in this table for multiple characteristics for a material.
    3.       The characteristic value should be in SAP internal format.
    CONFIG_ID
    000001
    INST_ID
    00000001
    CHARC
    Material characteristics
    VALUE
    Material characteristics value
    ·         SALES_CFGS_VK:
    1.       Combination of CONFIG_ID and INST_ID should be unique across line items.
    2.       We can have multiple characteristics for a material. In that case appropriate records should be inserted in this table. Note that CONFIG_ID and INST_ID should be same for all the rows you insert in this table for multiple characteristics for a material.
    CONFIG_ID
    000001
    INST_ID
    00000001
    VKEY
    Material characteristics

  • SD Variant Configuration - characteristic value computation

    Hi Everyone
    Greetings from Vinod
    i am creating a variant material which has 3 characteristics. out of the 3 characteristics, 2 are inputed by the user and the third characteristic needs to be populated with the difference of the 2 chatacteristic values that we have entered before. is there a standard setting that we have to maintain, or should we do a custom development on the same. the third characteristic value which is computed based on the difference of the precious two characteristic will then derive pricing of the variant material. please throw some suggestions and inputs in this discussion.

    Hi,
    calculating values of characteristics is done with so-called dependencies.
    In a dependency you can define the rule how a value should be calculated.
    You have to create a class of class type 300 and assign your characteristics to this class.
    Assign the class to a material of material type "Configurable Materials".
    Open the material with transaction PMEVC (Modeling Environment for Variant Configuration).
    There you maintain a dependency of type procedure.
    The source code may look like this for your example:
    $SELF.CHARACTERISTIC_3 = CHARACTERISTICS_1 - CHARACTERISTIC_2
    You can find details for variant configuration on help.sap.com:
    http://help.sap.com
      -> SAP ERP
      -> SAP ERP Central Component
      -> Logistics
      -> Logistics - General
      -> Variant Configuration (LO-VC)
    Details on transaction PMEVC (Modeling Environment for Variant Configuration):
    http://help.sap.com
      -> SAP ERP
      -> SAP ERP Central Component
      -> Logistics
      -> Logistics - General
      -> Variant Configuration (LO-VC)
      -> Modeling Environment for Variant Configuration
    Information on dependencies:
    http://help.sap.com
      -> SAP ERP
      -> SAP ERP Central Component
      -> Logistics
      -> Logistics - General
      -> Variant Configuration (LO-VC)
      -> Dependencies
       and
      -> Dependency Syntax: General Rules
    Best regards,
    Sebastian

  • BAPI for variant configuration

    Hi all,
    I need a BAPI which loads Variant configuration information in sales order. I beleive BAPI_SALESORDER_CREATEFROMDAT2 can be used for this purpose, but I need help in finding the required structures and the fields that need to be used for this purpose. Can any one provide me the information ASAP?
    Regards,
    Asha.

    Please use FM BAPISDORDER_GETDETAILEDLIST to understand what structures need to be filled for VC.
    Example code:
      ls_view-header     = 'X'.
      ls_view-item       = 'X'.
      ls_view-sdschedule = 'X'.
      ls_view-configure  = 'X'.
      ls_view-text       = 'X'.
      call function 'BAPISDORDER_GETDETAILEDLIST'
           exporting
                i_bapi_view           = ls_view
           tables
                sales_documents       = lt_docin
                order_headers_out     = lt_hdrout
                order_items_out       = lt_itmout
                order_schedules_out   = lt_schout
              order_partners_out    = lt_prtout
                order_textheaders_out = lt_hdtxt
                order_textlines_out   = lt_txtli
                order_cfgs_cucfgs_out = lt_cucfgout
                order_cfgs_cuvals_out = lt_cuvalout
                extensionout          = lt_parex.

  • Need help on variant configuration

    Hi Guru,
    Here we need to use variant configuration.But i am new in variant configuration.Can somebody tell me the different steps of variant configuration from PP side.I have gone through standard document. But still i need this information. The Industry in which I am going to implement this,is  producing Colored, profiled sheet to provide roofing solution.The metal roofing sheet can have different profile, different colour, different thickness, different width and so on.They have nearly three thousand  of different combination.
    Please respond.
    Regards
    Rajib

    Hi,
    Pls. find herewith Variant Configuration Procedure steps as below
    VARIANT CONFIGURATION:
    1.Create a Material - KMAT type with Item category (002)
    2.Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
    Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for).
    3.Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.
    4Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.
    5Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save.
    6.Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save).
    7.Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save.
    8.Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save).
    9.Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.
    Variant Configuration: Complete Maintenance:
    Technical name: SAP_LO_VC_MAINTAIN
    Tasks
    The variant configuration processor sets up the rules for multi-variant products and maintains them in the database. He or she simulates and executes the configuration. This role is required wherever variant configuration is used.
    The complete model also contains sales order processing (VA01/VA02), and the connection to SCE/Internet Sales and Mobile Sales.
    Activities in Variant Configuration;
    Transaction
    Activity
    CC04
    Display product structure
    CWBPP
    Engineering Workbench
    Variant Configuration
    VA01
    Create sales order
    VA02
    Change sales order
    VA03
    Display sales order
    CU51
    Maintain configurable order BOM (multilevel)
    CU52
    Maintain configurable order BOM (single level)
    CU50
    Configuration simulation
    CU80
    Reporting functions for characteristics and values
    Configured Objects
    CU44
    Material
    CU45
    Standard network
    Assignment of Configured Materials
    CS40
    Create assignment for configured material
    CS41
    Change assignment for configured material
    CS42
    Display assignment for configured material
    Configuration Profile
    CU41
    Create configuration profile
    CU42
    Change configuration profile
    CU43
    Display configuration profile
    Dependencies: Single Dependency
    CU01
    Create single dependency
    CU02
    Change single dependency
    CU03
    Display single dependency
    Dependencies: Dependency Net
    CU21
    Create dependency net
    CU22
    Change dependency net
    CU23
    Display dependency net
    Dependencies: General
    CU05
    Dependency where-used list
    CU04
    Dependency list
    Tools: Variant Function
    CU65
    Create function
    CU66
    Change function
    CU67
    Display function
    CU68
    List functions
    Variant Table Structure
    CU61
    Create variant table
    CU62
    Change variant table
    CU63
    Display variant table
    CU64
    List variant tables
    Variant Table Contents
    CU60
    Maintain variant table contents
    CU59
    Transfer variant table contents to database table
    Knowledge Base for SCE: Knowledge-Base Object
    CU31
    Create knowledge-base object
    CU32
    Change knowledge-base object
    CU33
    Display knowledge-base object
    Runtime Version
    CU34
    Create runtime version
    CU35
    Change runtime version
    CU36
    Display/export runtime version
    CU37
    Create SCE database schema on PC
    For complete details of Variant Configuration go to the following link :
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/96/468f38721f9977e10000009b38f842/frameset.htm
    Hope this helps.
    Regards,
    Prakash

  • Stock Report for Variant configuration

    Hi Experts,
    Request your help to get the following information.
    We have a material which are packed in to multiple packing modes. Inorder to ease the selection of packing mode in sales order, we are thinking of introducing variant configuration. I.e all the packed materials will be created as variants in SAP and the sales order will be created for the configurable material. When the proper characteristic is selected the material will be automatically replaced by the variant.
    But the requirement is to see the stocks of all the varaints along with the configurable materials as the header. For eg. Material A is having variants A1, A2 & A3. The sales quantites are 25, 30 and 35 respectively.
    In any of the standard report, can I see the sales of these along with the total sales of config mtl A as 90
    Please guide.
    Thanks & Regards
    Prathib

    Hi Prathib,
    On my last project, we define material code with the same code at the beginning like you do A1 A2 A3 (for variants) and AC for example for configurable material. Then for stock report you can use MB52, in material field just write A* it will show you stock from material start with code A. But make sure you define material type and material group for selection wisely. It works for me. Now depends on how well you define your structure.
    Regards,
    Arman

  • The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.

    We are in the process of removing a child domain from the forest and are down to two DCs. These are both Server 2008r2 sp1 servers, one physical and virtual (PDC). When I try to remove a DC (not the PDC emulator) I get the following error:
    The operation failed because:
    Active Directory Domain Services could not transfer the remaining data in directory partition DC=DomainDnsZones,DC=mydomain,DC=local to
    Active Directory Domain Controller \\V-Svr03.mydomain.local.
    The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles."
    I have checked replication with repadmin /showrepl and all connections were successful. The dcdiag /test:kccEvent test on all servers passed.
    Most DCdiag tests are successful. The only failure is on NCSecDesc when running dcdiag /test:NCSecDesc
       Testing server: Default-First-Site\DC1-DEV-OFC
          Starting test: NCSecDesc
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=ForestDnsZones,DC=hookemup,DC=local
             ......................... DC1-DEV-OFC failed test NCSecDesc
    In researching this I find "If you do not plan to add an RODC to the forest, you can disregard this error."
    We have not successfully run ADprep /rodcPrep nor do we plan on having any Read-Only DCs, so I think we can ignor this error. We did try running ADprep /rodcPrep but got an LDAP error which I can duplicate if this is important.
    Schema and Naming FSMOs are on a DC higher in the forest. RID, PDC, and Infrastructure FSMOs for the child domain are on the Virtual server (PDC).
    Any guidance on where to go from here would be greatly appreciated as I have no more hair on my head to pull.

    Ok... I ran repadmin /showreps /v again and it shows no errors
    C:\>repadmin /showreps /v
    Default-First-Site\DC1-DEV-OFC
    DSA Options: IS_GC
    Site Options: (none)
    DSA object GUID: b294c59f-8b46-4133-89c5-0f30bfd49607
    DSA invocationID: 1054285d-cffe-42b4-8074-e2d44adbb151
    ==== INBOUND NEIGHBORS ======================================
    CN=Configuration,DC=mydomain,DC=local
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 16381490/OU, 16381490/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114817/OU, 114817/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 66047/OU, 66047/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 8098197/OU, 8098197/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
    CN=Schema,CN=Configuration,DC=mydomain,DC=local
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 8097482/OU, 8097482/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 65239/OU, 65239/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114149/OU, 114149/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 16381373/OU, 16381373/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
    DC=ForestDnsZones,DC=mydomain,DC=local
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 66295/OU, 66295/PU
            Last attempt @ 2012-10-29 13:57:48 was successful.
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 8098367/OU, 8098367/PU
            Last attempt @ 2012-10-29 13:58:13 was successful.
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 115032/OU, 115032/PU
            Last attempt @ 2012-10-29 13:58:25 was successful.
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 16381653/OU, 16381653/PU
            Last attempt @ 2012-10-29 13:58:34 was successful.
    DC=mySUBdomain,DC=local
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114871/OU, 114871/PU
            Last attempt @ 2012-10-29 13:54:02 was successful.
    DC=DomainDnsZones,DC=mySUBdomain,DC=local
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
            USNs: 114017/OU, 114017/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
    DC=mydomain,DC=local
        Default-First-Site\V-SVR03 via RPC
            DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
            Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
            DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 114017/OU, 114017/PU
            Last attempt @ 2012-10-29 13:52:39 was successful.
        Default-First-Site\HESTIA via RPC
            DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
            Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
            DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 16381614/OU, 16381614/PU
            Last attempt @ 2012-10-29 13:56:52 was successful.
        Default-First-Site\V-SVR01 via RPC
            DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
            Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
            DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 66325/OU, 66325/PU
            Last attempt @ 2012-10-29 13:58:34 was successful.
        Default-First-Site\ATHENA via RPC
            DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
            Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
            DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
            SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
            USNs: 8098385/OU, 8098385/PU
            Last attempt @ 2012-10-29 13:58:38 was successful.

  • Variant configuration u2013 availability check for Configurable material

    Hi Guys,
      We are doing the variant configuration scenario for one of our client. We are using planning strategy as 25 (sales order with variant configuration).
      When we configure the Configurable material at sales order level, we wanted to check the availability check of Configurable for the combination of selected characteristics.
    How we can configure it in the system.
    Regards,
    Shailendra

    Hi,
    availability check will work as per the checking group you had defined in system.
    additionaly you need to put tick in configuration profile for availability check.
    checking for material varient is optional, if your bussiness has materail varients you can activate type matching and while configuring the sales order if the values of charactersticks matches system will suggest you the the appropiate varient and you can replace your configurable material in sales order with it.
    hope it will help you.
    If you need some more information please explain what exactly your are expecting from system during availability check.
    Regards
    Ritesh
    Edited by: R S D on May 28, 2009 7:29 AM

  • Consuming Material Having Variant Configuration

    HI
    We are using Variant Configuration for our semi finished product and its
    batch managed.There are two plants in one plant say A and B. In A plant
    we are using Variant configuration.The same material is stock transferred
    to plant B and is further processed.
    We are creating CIR in plant B. After taking MRP run we are converting
    planned order to purchase requisition and subsequently Stock transfer
    purchase order on Plant A. When the material is produced in plant A,it is
    transferred to plant B on stock transfer order mentioned above. But the
    material is against CIR in plant B. We remove the material from CIR
    through 411E movement and system keep it as free stock in unrestricted.
    Now when i am consuming this material for further processing in
    production order of Material getting manufactured system is asking me for
    Variant Characteristics.
    System should not ask me variant characteristics once it has been removed
    from CIR i.e. special stock.
    Any Work around avilable.
    Regards,
    Anand.

    Hi Anand,
    Finally, I could understand your issue from your CSS message.
    In your description, AA is configurable material in both plant A and plant B, BB is not a configurable material in plant B, AA is a component of material BB, so when you produce BB, there will be dependent requirement generated for AA from BB, now you want to use the stock of AA to fullfill the dependent requirement, however, the system will require you to enter the characteristic at that time.
    Then where is the stock of AA comes from? I have mentioned this in my previous reply. But as I have mentioned it is not correct to have unristricted stock for the configurable material, therefore, your process to have free stock of AA is not correct.
    Another point is that, your process to have configurable material as a component of a non-configurable material is also not proper.
    For example, material BB is a Car, material AA is the Door of the Car, your Car is not configurable, but the Door is configurable, you may have green door and red door according to the configuration, but as your car is a firmed material then what's the meaning to have different door, if you want to have different door, then that means you also need to have different color of the car, like green door for green car, red door for red car, then that means your car should be also a configurable material to make you can select the color of the car too.
    Or if your Car is a firmed material as green car, then do you think there is any meaning to configure the door of the car? Unless you do want a red door for a green car, but this can also be realized with a configurable car.
    So normally, like your situation, you should use multi-level configuration structure to do the production in make to order scenario.
    Therefore, still the problem has been described in my previous reply, no matter how you get the stock of AA, the AA is produced with the configured configuration module, so the stock of AA is also with the configuration data, then no matter how you want to consume the stock of AA, system will always ask for the characteristic of the requirement to compare it with the stock configuration to see if they are same.
    For example, you are producing your Car, but as far as I can see you should have no place to configure the door in production order, therefore when you try to consume the door, the system will of course need to know which color you want, because if you want red door but there is only stock of green door, then how the system should do in your opinion?
    Then finially, the best way of solving your issue is to have material variant for the configurable material, like the door, you may have material variant as green door and red door, if your firmed Car is green car, then you can use green door as the firmed component, if your firmed Car is red car, then you can use red door as the firmed component, also when you do the production, you could simply produce the green door directly without configure the door, because the material variant is a stockable item but the configurable material is not, then your scenario would be very simple and there will no such problem any more.
    If you do still want to keep your scenario, but don't want the system requires you enter the charateristics, then you may have to do the modification of the goods movement transaction to disable that, but it may lead to the inconsistency situation, like actually you want red door, but what you have in stock is green door, without that, you may consume the green door stock for the red door requirement, then it will mess up all the following process.
    Also as you are doing the goods movement in MM transaction, so if there is user-exit could be used to change this behavior is decided by MM function, however, base on my checking there will be no such user-exit to control this behavior at MM side, because the consequnce is really dangerous for the system operation.
    Therefore, I think the best way for you is still adjust your production scenario to make your production standard, then SAP system will accept that standard production scenario under your requirement.
    Thanks and regards,
    Rachel
    Edited by: Rachel Tang on Apr 2, 2010 10:25 AM
    Edited by: Rachel Tang on Apr 2, 2010 10:32 AM

  • Copy control settings for Multilevel variant configuration

    Dear All,
    I have  the following scenario for variant configuration A quotation is created for configurable material with multilevel configurable material
    with reference to this quoatation a sales order is created.
    My requirement is that the quoatation must get copied to sales order as it is along with the values for subitems also.
    In copy control settings there is a field at item level called
    configuration :
    In this if I maintain value
    A: The variant is getting copied but  the values for subitems is not getting copied the values for main material is in changable mode.
    B: The variant is getting copied but  the values for subitems is not getting copied the values for main material are not in changable mode.
    C:The variant is getting copied   the values for subitems is  getting copied the values for main material are  in changable mode but the values for subitems are not in changable mode.
    My requiremnt  is that
    The variant must get copied
    the values for subitems must get copied
    the main material vlaues must be in changable mode
    the subitems vlaues must be in changable mode
    How can I fullfill this requiremnt, has any one of you come across this scenario, Pleae provide with solution it is urgent
    Informative answers will be provided maximum points.
    Deepak

    Hai Deepak Mehmi,
    please check in T CODE VTAA
    In the position check
    SalesDocType : Sales order type
    SalesDocType : Inquiry type
    Double clcik and check
    DataT 051 General header data       Copying requirements 002 Header-diff.customer
    DataT 101 Header business data
    DataT 001 Partner header
    And Tick mark for Copy Item Number
    For further check:
    In Item
                                      Copying requirements 301
    DataT 151 General item data                                          Pos./neg. quantity   +
                                                               Copy quantity
    DataT 102 Bus.data/item compl.                                     Pricing type         G
    DataT 002 Partner item                       2 Update document flow   Cont. item copy mode
                                                        Copy product select.
    FPLA  251 Conditions                Configuration
                                                               Campaign Deter.
    Regards,
    Mani

  • Variant Configuration Data download from R/3 to CRM

    Hello all
    It may be a very dumb question, but I would certainly appreciate an answer.
    We are currently using SAP R/3 4.6c and heavily use VC for configurable products and also for pricing.
    Now we wish to explore the possibility of using SAP CRM 5.0 to enable our sales force to use CRM PCUI to create quotes for configurable materials.
    My questions are as following:-
    1. Is it possible to download all VC related data into CRM from R/3 including pricing? I understand that for different VC object, I will have to use different CRM objects but is it possible? If the data transfer is possible, is it typically done by a middleware resource?
    2. I would also like to confirm that by creating a run time version and Kbase is pre requisite to enable the download to CRM.
    If you could please point me to the appropriate help on this topic, I would really appreciate it.
    Best regards
    Jai

    Hi Gun,
    In your message, You stated
    As recommended by SAP, if we have R/3 link into our CRM
    the best scenario is to get VC product from R/3 into CRM.
    Is there any documentation tjhat backs this up? could you give it to me
    we have  a situation in our company where we have been using a home grown product  that not only lets you configure product bu it also takes the user through a selling experience for example it asks the user if he is interested in buying any accessories for the product and provides options through pop messages and the user can select. this way it takes leads the user  through questionnaires that comes in pop ups to select a product
    we have crm service and ecc implemented and now we need to implement  this feature for the crm sales  piece
    the question is do we go for  PME  or variant config that is already set up in ECC ?
    the link and middle ware set up between ECC and CRM is also available so we can bring the variant configuration from ECC into crm.  but how about the questionnaires and the selling experience that is available  through pop up questionnaires,
    we can set up the selling experience via the Product modeler   but as a company we need to make a decision whether we bring the varinat configuration from ecc and use the selling experience  for the pop up questionnaires that leads customer
    or should we just use sales packages that behaves similarly like varinat configuration and add enahcnements to create the pop- up questionaires
    Could you direct /provide some guidance in this area?
    Sara

  • Configuration Data Transfer Tool

    Hello all,
    I am working with my client to plan our ME Configuration and we are trying to determine how best to propagate the configuration from one system to another (i.e. DEV to QA to PROD). 
    I understand there is a new tool being developed for SAP ME 6.0 called the Configuration Data Transfer Tool. 
    Will it be possible to use this tool for SAP ME 5.2.5?  Has anyone tried to do this?
    What are the overall recommendations and/or methods other folks have used to move their configuration to another system?
    The goal is to move configuration and master data only, no transactional data.
    Any insight would be greatly appreciated.
    Thank you.
    Mari Santangelo

    Mari,
    Configuration Data Transfer Tool is not a standalone application but just a feature (the activity) of ME 6.0 so you can't use it with ME 5.2.5. And there is no information about porting it back from 6.0 to 5.2.5.
    In 5.x and prior releases, there is DataXchange tool mentioned by Ivan and Site2Site Transfer activity (you can find the guide next to Xchange guide on SMP).
    Regards,
    Sergiy

  • SO BOM or Variant Configuration or Other for Technical Sale

    Dear Community,
    I would like to ask you and advice on this.
    In a Plastic Packaging Industry with lots of different products but very similar at the same time, production is triggered after the customer order.
    To me it sounds very logical to use Variant Configuration scenario to specify product details which define its components and operations. Nevertheless the Sales People are don't have the enough knowledge to define completely the product and need a Technical Area to define key information to complete the product. before sending sales order (or quotation) to customer.
    Which scenario would you use ? And most important: how would you use it to integrate  the customer requirement information with technical data from experts?
    Thank you in advance,
    Best Regards,
    Sebastián Ligueros

    Hi Mario and the rest of community, I wish you a Happy New Year!
    Answering the questions: The product is engineered specifically for the customer and is possibly (not always) subject to change in every sales order.
    The first requirement from customer goes to sales department. If the product is new there is lot of joint woirk with technical area to develop the particular product and then send the quotation to the customer when most of the processes and components are defined. Product can be further specified in the sales order. If the product has been already sold in the past, sales department send quotation/sales order taking as reference a previous one maybe changing one or two elements like graphic design.
    In this interaction between  the sales department requirement and technical area for product development at "preparation for quotation level"  and then for sales order I would like to know in your opinion which would be the best scenario.
    Thank you,
    Sebastián Ligueros

  • Custom ATP Check using Variant Configuration Data in sales order

    I have a requirement to modify the standard SAP ATP check by including the variant configuration data entered on a item.  Standard SAP does not use/include the characteristics data when doing the ATP. None of the available user exits would allow me to do this.
    The scenario is the client has a configurable product that exist in inventory as one item, base unit as IN2.  The batches that exist in inventory have the characteristics of width and length.  The order data specifies a width and a length, they need the ATP to identify the availability based on the characteristics of the batch.
    The solution was to present the user with a list of batches based on the characteristics that meet the criteria.  The user would then have the option of choosing one of the batches which would mean that the line item would include the batch #.  If the user does not want any of the batches, they could choose to select a Make to Order option, which would change the item category of the item, so that it creates a production order upon saving the order.
    The problem I am having implementing this solution is I have not been able to identify the internal table(s) that contains the characteristics data in SAPMV45A after the configuration screen is called.  If anyone knows where that information is during the sales order processing, it would be greatly appreciated.

    Hello Jean,
    Have you managed to find a solution as yet? I know you have not received any replies but am hoping you were able to resolve the problem as we are facing the exact issue on our project.
    Please let me know,
    Thanks,
    Tanya

  • Sales order costing (MTO) Variant configuration.

    Hi,
    Basically there 3 different types of finished castings :
    1.     Special finished Casting u2013 which is a configurable material . this casting is saleable as well as can be used for manufacturing machined castings. This casting is been manufactured at plant : 8110 only. The planning strategy maintained is 25 (make to order with configurable material)
    2.     Machined Casting u2013 this is also an configurable finished material which can be sold as well as can be used as an BOM for manufacturing Assembly castings. This casting gets manufactured at plant : 8130 only. The planning strategy maintained is 25 (make to order with configurable material)
    3.     Assembly casting : this is also an configurable finished material which is always saleable. This casting gets manufactured at  plant : 8130 only. The planning strategy maintained is 25 (make to order with configurable material)
    Scenario which is as follows :
    1.     Customer gives the PO for assembly casting at 8110 plant code.
    2.     Therefore Plant : 8110 will generate the stock transfer order to 8130 for assembly castings
    3.     For manufacturing of assembly castings in 8130, the plant needs to manufacture Machined castings in 8130 plant and for manufacturing machined castings in plant 8130 , the plant requires special castings which is been manufactured at 8110 plant.
    4.     So, firstly Special castings will get manufactured at 8110 plant with the reference of assembly sales order .
    5.     After that stock transfer for special castings will be done from 8110 to 8130 plant .
    6.     Then customer would start manufacturing machined castings
    7.     And then finally manufacture assembly casting
    8.     Finally assembly castings will get transferred from 8130 to 8110 plant for sale
    9.     Sale of assembly castings from 8110 plant respectively.
    Touch points of the scenario:
    1.     Cost of special casting and machined castings should get rolled up to the assembly castings
    2.     These needs to be executed in MTO scenario only because of variant configuration
    3.     While doing the stock transfer, the cost should include transfer pricing as well
    Problem Statement :
    1.     We understand that for configurable material , you cannot run the standard cost estimate, therefore the material master price with price control u201CSu201D is always zero. So when do the  stock transfer from of assembly cast or special cast for one plant to another then cost update happening at both the plants is zero.
    Please suggest some better solution for incorporating this scenario inclusive of the touch points.
    Thanks...

    Dear Srinivas,
    You can post this query to SD forum also for better response.
    Regards,
    Rakesh

Maybe you are looking for

  • Win 8.1 Lock Up After 5 min, "Memory Management" or "Cache Error"

    Systems blue screens every few minutes. MS offered a variety of error messages, now is uniformly "Memory Mangement". Chrome shows a Cache Error. Any ideas?

  • Firefox crashes on certain websites.

    Recently, I had a malware/virus attack on my computer from XP Anti-Spyware. There were many pop-ups from XP Anti-Spyware. Then later I lost connectivity to the internet. I used Norton Security Scan to get rid of the malwares and viruses. After using

  • Cfloop + Multiple DB Inserts

    Hello everyone. I have a form with a dynamically generated number of fields. Each Client has a variable number of "ItemDetails" assigned to them based upon which Item that individual is registered for. For example: Customer A is registered for a HRID

  • Condition details in Sales order using a BAPI

    Hi, I am using BAPI_SALESORDER_CREATEFROMDAT1 to create a SO. I want to add the condition type, condition value and condition currency. I think the table input ORDER_ITEMS_IN is used here. But confused with the fields. Can u help me figure out which

  • Maintenance Plan task loging

    Hi all. I am creating a maintenance plan which may have mixture of T-SQL task and build-in task like reorg, rebuild tasks... I would like to log each task output to seperate files. Is it possible to do so ?