Operating leasing configuration

Hi all,
I have a customer that has operating leasing. They want to have better control of their leasing costs. I have search on internet and found that there is possible to crate assets for operating leasing as follow:
I configure a new asset class, 6000 and then create a new asset in AS01. In AS01 i tell:
- Agreement number
- Agreement date
- Notice date
- Lease start date
- Lease lenght
- Type
- Base value as new
- Purchase price
- No lease paymen
- Payment cycle
- Lease payment
- Annual rate of interest
I then choose the depreciation areas tab page and select deact field for depreciation areas.
Then I can see the value in transaction S_ALR_87011992.
But how do I do when I then got invoices, how do I link the costs to this asset, so I can see that the cost belong to this asset? Do I have to create statistical orders that has the same number as the asset?
Is this the best solution for my customer, to create a new asset class and see the leasing among the other assets? If not what else can be a solution, for example only statistical orders?
They also want to have better control over the accruals of leasing. Do you have a better solution then transaction FBS1 and F.82?
Thanks in advance!
Regards Lisa

Hi Lisa
Please find answers to your questions
1. Okej, but if I have acquasition to this asset for 108 000 EUR for example and then run depreciation. Will my value of that asset still be 108 000, all time and the only thing that will be posten when I run the depreciation is the interest?
When you run depreciation, the value of asset will reduce as per percentage specified on depreciation key. Interest which you would normally pay on leasing any particular asset will be calculated and posted accordingly.
2.If I will lease this asset for 3 years, do I have to do anything after this tre years or does the system gives the value of this asset 0 EUR after the lease period automatic?
If you ahve set useful life as 3 years in asset master record and charging depreciation on useful life then asset value will become 0 at end of 3 years.
3. What does they mean with purchase price, is that price after the lease period?
purchase price  is the price at which you have purchased the leased asset.
4. - What happens to the lease payment. Does that payment posts also when we run depreciation, as the interest?
Lease payment is not posted through Asset accounting. it should be posted from FI.
hope tht helps.
Thanks
Sanjeev

Similar Messages

  • Operating Lease

    Dear Experts,
    Our company would like to introduce Operating Lease. I have read about customizing this operating lease but at the moment, it is still not working.
    FYI - I have activated cost accounting depreciation area 20 (post to GL inactive). I also have created the leasing type - operating lease with the necessary doc type, posting key. I have also have created the asset class which is pointing to only depreciation area 20 with no depreciation. This asset class has leasing information - the vendor, amount, term and etc.
    However, when I post a cost to this asset (created using the above asset class), I can only post in AA module with no corresponding entry in FI-AP (because post to GL is inactive). (btw - I am not able to post via FI - I have tried using standard transaction type for leasing as well as customised). I am just wondering how this can relates with - one time posting and clearing using recurring document (read this in SAP Document - Posting acquisition of Lease Asset (Operating Lease) http://help.sap.com/saphelp_erp60_sp/helpdata/en/4f/71fd71448011d189f00000e81ddfac/frameset.htm -  if the debiting the assets does not hitting FI. I am also wondering at what point that I can debit the expenses (with appropriate cost center). I have tried a few scenario with different posting key to get the asset to be posted as statistical (some notes are tallking about statistical assets) and actual to expense, but still does not work. I also wondering how the payment to vendor will be updated in Asset Master.
    I really appreciate some clue or any notes that I can read on this subject.
    Thanks.
    Regards
    Fauzi

    This is what I get from SAP documentation:
    Post the asset acquisition using a transaction type that only posts to cost-accounting depreciation areas.
    In FI, create a recurring document for lease payments.
    After invoices are posted in the system, payment can be processed using the FI payment program.
    How you process the cancellation of a lease depends on the lease method:
    In the case of a capital lease you determine if the asset is being purchased or returned. If the asset is being purchased, you post an asset transfer, if it is being returned, you post a retirement.
    In the case of an operating lease, you simply delete the master record for the statistical asset. The rental agreement must also be closed in FI (flag the recurring entry document for deletion).
    If the lease is canceled ahead of time, you have to reverse the future liabilities that are due.

  • Operation Selection Configuration - Please Explain

    I was looking for an example in the ALSB Book (Apress) or through ALSB documentation and cannot find a good definition of the different selections for the "Operation Selection Configuration". The Operation Algorithm (when configuring a Proxy Service) gives the following options:
    Transport Header
    SOAPAction Header
    WS-Addressing
    SOAP Header
    SOAP Body Type
    The default used is SOAP Body Type. I know that SOAPAction relates to a SOAPAction being defined in the WSDL, which doesn't seem to matter because if my WSDL has SOAPAction defined and I use a client to send a SOAP Request with a bogus Action...I still get a response. So I am definitely confused on what these selections detail and how they are effected by the type of information a calling client includes.
    Thanks -jay

    I should have explained that I already knew that.
    The thing is that the service still works if you select one of the other options even though I am not sending any WS-Adress information or I don't have a SOAP Action and they still work.

  • Post expense of operating leased asset

    Dear experts
    i want to know how to post the operating leased asset expense periodocally ???
    is there a way to post it automatically or even how to post it manually

    any help experts??????

  • Rework operation in configurable products

    Dear Experts ,
    I need your expertise knowledge in Re-work scenario for configurable product.
    I have a scenario where i have produced one configurable product which is lying in stock against specific customer.
    Now at some point of time , i came to know that this product can be sold to some other customer with just change in the few variants like color and
    Cylinder capacity. In this kind of scenario , to carry our re-work process my business wants to consume the stock lying against different customer in
    stock ( hopefully customer delaying to get it delivered)  Is this the right approach..? Can i consume the configuarablke material stock and make few
    changes and deliver to the customer..? Is this the right approah.
    Need you expertise knowledge on impact of both Finance. Production.
    Note : i have tested the scenario , system is allowing me to consume Stock of configuarable product ( For testing purpose i did transfer posting from customer stock to own stock by 411 E.
    regards,
    Daya

    Hi Daya,
    To understand myself the above scenario, I used the
    example of Tined drinks/beers. The product beer is going to be the same for the
    brands UB and Kingfisher, only the difference is brand sticker pasted over the
    tin.
    Now, the retailer of UB had placed some order and the
    stock for them is produced as well and available at UB sales order stock. In
    business perspective it is required to remove the UB sticker from tin and paste
    the kingfisher stickers over it.
    In the above structure, I hope there is no standard SAP transaction available for links in colour red(For dis-mantle and re-assembling). All the links in Green are available in standard SAP. If the scenario is often occuring, then it is good to have a custom program for this in the below mentioned way.
    Step 1
    The final product (UB Beer), to dismantled to beer and UB sticker (may be 132 and 262 - Consumption reversal), here it is possible to custom single level or multi level as well - The cost of dismantling also to be capture in a seperate cost center (may be a re-work cost center).
    Step 2
    Assemble the Beer and KF sticker (131 and 262) - Assembling cot needs to be captured in seperate cost center if required. Or for ex, if this stickering operation is defined as a seperate level of process, then this can be handled by cretaing a regular production order.
    This dis-mantling custom program can be used for scrapping as well, for ex, the final product is rejected and needs to be scrapped for some reason, But some of its components are re-usable.
    This dismantling and re-assembling is very often in breweries as there would be lot of promotions and discount sales will be going on and to push the produce stock it is required to go with the brands which is selling high in a particular season.
    But it is good to go for custom program only if the dis-mantling and assembling is often in the business process. Other wise it is better to split the configured product into two process like
    Process 1 - Until the configuration come into place, produce the product at this level in MTS scenario
    Process 2 - Pick the MTS product and go either for ATO or STO scenario.
    Let the community know any further inputs are required.   
    Regards,
    Chinna.

  • Looking for SAP Leasing Configuration guide

    Hi,
    I am looking for SAP Leasing related configuration/best practices guide.
    Can any one help me on this?
    Thanking you in advance.
    Regards,
    Ram.

    Check:
    http://help.sap.com/bp_profservicev1600/ProfServ_US/HTML/Scenarios/DUB_Scen_EN_US.htm
    http://help.sap.com/bp_profservicev1600/ProfServ_US/Documentation/Scenarios/DUB_Scen_Overview_EN_US.ppt
    http://help.sap.com/content/bestpractices/industry/index.htm
    http://help.sap.com/bp_retail603/Retail_US/HTML/index.htm

  • Operational (vs Configuration) Clustering of ESAs

    Hi,
    Is there an ESA clustering solution that presents a virtual ip address to an inside Exchange server and/or an outside MTA, in other words operational clustering? These c170 ESAs are already clustered for configuration purposes but the interfaces are physically separate.
    I'd like to come up with an SMTP failover configuration that works in a particular environment.
    The environment
    Two ESAs
    A single ASA with two ISPs directly connected in the normal ISP standby/failover configuration
    A single Exchange server inside sending to both smart hosts (ESAs)
    So far the limitations are
    outbound from the inside, Exchange cannot selectively send to one ESA or another unless the ESA private interface itself was down
    inbound on the ASA if  publish the 2nd ESA to the failover interface before failover occurs that according to TAC doesn't work until failover
    inbound on the ASA if we wait until failover to publish the 2nd ESA to the failover interface we need DNS failover to make that work.
    Appreciate any known working solutions.
    Thanks

    Virtual IP functionality is currenly unsupported, it is on the roadmap though. Currently you can use DNS load balancing to specify a single server on either Exchange or internet, or you can use the standard MX records..
    Sent from Cisco Technical Support Android App

  • Can multiple 1394 Controllers be switched in and out of operation and configured correctly?

    The test system I'm working on has a 'core' VXI System using a Slot-0 1394 Controller that is always powered up but also requires other systems to be switched in and out as required under the control of LabVIEW 7.1 software. The interface to all of the VXI systems is made via PCI Firewire interface to the single controlling PC.
    The test system needs to be able to perform various sequences of actions using multiple peripheral systems but always with the 'core' system powered up. An example sequence would be:
    1) Power up the 'core' VXI system and communicate with the instruments
    2) Power up  peripheral VXI system '1' and communicate with the instruments
    3) Power down  peripheral VXI system '1' 
    4) Power up  peripheral VXI system '2' and communicate with the instruments
    5) Power down  peripheral VXI system '2'
    6) Power down the 'core' VXI system
    In order to simulate the above sequence of actions in a test environment I have two VXI Chassis systems and three Slot-0 Controllers which I have attempted to use as follows:
    1) Power up VXI Chassis 1 and communicate with the instruments
    2) Power up peripheral VXI Chassis 2 and communicate with the instruments
    3) Power down  VXI Chassis 2 and replace the Slot-0 Controller 
    4) Power up VXI Chassis 2 with the new Slot-0 Controller and communicate with the instruments
    5) Power down VXI Chassis 2
    6) Power down VXI Chassis 1
    I have registered all of the Slot-0 Controllers in MAX beforehand and they are persistent and appear as VXI systems '0'-'2' in the GUI.
    I have run resman programmatically in LabVIEW 7.1 (using NI-VXI 3.3.1 and the suggested patch) using a command line of "resman -b'n' -o" (where 'n' is the system number) in order to run the executable silently (which will be required for the completed test system). Resman is run after the power up of each chassis (for that VXI system only) in steps 1 and 2 and works ok at these stages. When resman is run after the power up in step '4' however, resman crashes along with LabVIEW.
    As an extra test I tried just attempting to 'find' each of the systems using the 'VISA find resource' VI after the power-up of each VXI system but without performing any other actions (i.e. running resman or communicating with the instruments). For steps 1 and 2 this also works ok but in step 4 this again results in a fatal crash in LabVIEW. 
    Could you tell me if these crashes are to be expected or if I am doing something wrong?
    thanks
    Lee Hutchinson
    Test Software Engineer
    BAE Systems
    Waterlooville
    Hants

    Hi Lee,
    In the VXI-1394 User Manual we say that you should always have VXI unit powered up before the PC. I think this would go for peripheral VXI units as well. For this system to work stabley I would have thought that you need to power up the peripheral VXI chassis, then the core then the PC.  The way you are doing it at the moment you are effectively replacing one 1394 controller with another and I don't think the PC will be able to handle the references to them in this manner.
    Regards
    Jon B
    Applications Engineer
    NIUK

  • Lease Accounting Scenario

    Dear:
                We have Lease accounting for assets configured in Organization Now the leasing process has changed. Management now receives funds from bank for the value of asset being purchased i-e finance lease. AS-IS process (currently running ) and TO-BE (what we want ) are given
    Where lessor don't transfer funds for car in which accounting entries are as follows
    AS-IS Process
    At inception:
    Security deposit               Dr.
                                    Bank                      Cr.
    Leased Asset                     Dr.
                                    Lease Liability    Cr.
    Monthly installment:
    Lease Liability                    Dr.
    Lease interest                   Dr.
                                    Bank                      Cr.
    TO-BE Process
    ·         We want this to be used Where lessor transfer funds for car. Please advice on the feasibility of automating this process in lease asset module. Specially the first entry is confusing. How will we cater it in AA module or passing a manual JV will be a solution. Please guide.
    At inception:
    Bank                                      Dr.
    Security deposit               Dr.
                                    Lease Liability                    Cr.
    Monthly installment:
    Lease Liability                    Dr.
    Lease interest                   Dr.
                                    Bank                      Cr.
    Regards
    Edited by: Atif Farooq on Jul 23, 2011 10:00 AM

    Just a few question to clarify your scenario.
    Your organization acquired the cars from the car dealership or manufacturer?
    Your organization is the (lessor), and there are customers (lessees) who lease your cars?
    When customers make payments, your bank receives the money and gives it to your organization?
    If these 3 questions all have answer of Yes, then you have to decide what accounting rules you wish to follow.  US GAAP, IFRS, something else.  The reason must decide on accounting rules is because leasing rules are changing, and early adoption of the new rules may already be in place in your firm.
    To get SAP advice, you have to be able to say whether or not this is a capital financing lease or is an operational lease.
    If it is a capital financing lease (for your customer/buyer) then in the substance of the actual transaction you have already sold the car according to US GAAP existing rules.  You do not have a capital asset (car) in your AA sub-ledger any longer.  Instead you have a long-term lease receivable for the present value of all future payments to arrive.  The current year portion of the amount will be classified as current year.  As payments come in, you reduce the current receivable by the previously recorded present value amount, and you credit imputed effective interest income for the difference to balance your entry with cash.
    But if the leases are operational leases, then you will depreciate the cars while you receive lease and imputed effective interest revenue.  You will get the cars back with more than just small residual value left.

  • Lease Assets Management

    Hi Gurus,
    Thanks in advance
    I need Lease Assets Management in SAP configuration documents.
    If any body have please send me on following mail ID : [email protected]
    Thanks

    Hi deepika.... the following notes may useful to u ..
    The "Leased Assets" scenario describes the management of leased assets from the standpoint of the lessee.
    Leased assets create special accounting requirements for the lessee, as compared to assets that an enterprise purchases or produces itself. During the term of the lease, leased assets remain the property of the lessor or manufacturer. They represent, therefore, a special form of rented asset. Such assets are legally and from a tax perspective the responsibility of the lessor, and are not relevant for assessing the value of the asset portfolio of the lessee. However, in certain countries, you are nonetheless required to capitalize leased assets, depending on the type of financing.
    This scenario makes it possible to handle different types of leased assets differently. Depending on legal restrictions, you can capitalize and depreciate leased assets (capital lease) or post their rent expense periodically to the profit and loss statement (operating lease).
    There are different ways of handling the values of leased assets in the system. Depending on legal requirements and the conditions of the lease, there are two different options:
    You have to capitalize and depreciate certain leased assets (capital lease).
    You treat others as periodic rent expense, which flows into the profit and loss statement (operating lease).
    This second type is not relevant to the fixed assets of the lessee. It is therefore sufficient to do one of the following:
    Manage operating leases as statistical assets in the Asset Accounting component (with no active depreciation areas)
    Manage them only as cost-accounting values (or for group accounting) in the corresponding depreciation areas
    There is a special report on rent liability that can be used for all types of leased assets (see below).
    You can also manage insurance values for purely statistical leased assets (without depreciation areas). You enter a manual insurance value and an index series for the leased assets in the asset master record. You obtain reports on these values using the standard report for insurance values.
    <b>Capital Lease Method</b>
    Leased assets can be capitalized in the Asset Accounting component using the capital lease method. The system calculates the acquisition value from the present value of the future lease payments in the leasing agreement. To be able to determine the future burden of payment, you need to maintain the following leasing conditions in the asset master records:
    Amount of lease payment
    Number of payments
    Payment cycle
    In order to calculate present value, also enter an interest rate. The system requires that you post a leasing partner as a vendor in the asset master record at the time of the acquisition posting (opening posting).
    <b>Periodic Posting</b>
    The depreciation posting program posts the depreciation of leased assets and the write-off of the interest. You can use any depreciation key. The standard R/3 System includes a special depreciation key, in which the depreciation amounts correspond to the present value of the periodic leasing payments (LEAS). Using this key, interest is determined as the difference between the leasing payments and the present value.
    <b>Calculation of Present Value</b>
    The present value of the leased asset is calculated on the basis of the following specifications:
    g : Amount of lease payment
    i : Annual interest rate
    n : Number of lease payments
    r: Leasing cycle (for example, 3 = quarterly, 6 = semiannual)
    m : Number of periods in a year
    q : Period interest factor = 1 + ( i / 100 * r / m)
    If payment is made at the beginning of the period, the present value then results from the following formula:
    Present value = g + g * q** (n-1) - 1 / (q**n-1 * (q - 1))
    With payment at the end of the payment period, on the other hand, the present value is calculated as follows:
    Present value = g * ( q*n - 1) / ( q*n * ( q - 1))
    Example
    g : 100
    i: 10.000 %
    n: 20
    r: 3
    m: 12
    q: 1 + (10.000 / 100 * 3 / 12) = 1.025
    Present value at the beginning of the payment period:
    100 + 100 * (1.025*19 - 1) / (1.025*19 * (1.025 - 1)) = 1597.89
    Present value at the end of the payment period:
    100 * (1.025*20 - 1) / (1.025*20 * ( 1.025 - 1)) = 1558.92
    <b>Reports</b>
    There is a standard report in the system for determining future leasing liability (especially in regard to leased assets that are not capitalized). The report displays for each leased asset:
    The payments already made
    The payments due up to the date of the report
    The total lease payments to be made for the asset
    You can create a totals list with cumulative values for each fiscal year and company code. In order for the report to work properly, you must make sure that the following leasing conditions are properly maintained in the asset master record:
    Start date of the lease
    Payment information (lease payment amount, payment cycle, number of payments)
    Leasing type
    Using the APC by acquisition year indicator, you can display the theoretical acquisition value of leased assets according to acquisition year. This statistical analysis is required in some countries for financial reports. The system uses the base new value that is specified in the asset master record in the leasing information. The acquisition year is determined from the start date of the lease.
    <b>Implementation Considerations
    General Tips</b>
    If you want to manage capitalized leased assets in the system, follow these steps:
    Define leasing types in Customizing for Asset Accounting with the specifications for posting asset acquisitions.
    Create special asset classes and account allocations for your leased assets.
    Define depreciation areas, in which you plan to capitalize leased assets using the capital lease procedure, so that they manage interest that can be posted with the depreciation posting program.
    Activate the depreciation areas, in which the leased assets will be capitalized and depreciated, in these asset classes.
    Assign a leasing type to the asset master records for leased assets.
    Maintain the information and conditions of the leasing agreement in the master records of the leased assets. Specify an interest rate for calculating the present value and determine whether the lease payments should be made at the beginning of the payment period or at the end of the payment period.
    Post the acquisition of a leased asset with the display transaction for asset master data.
    <b>Leased Asset acquisition</b>
    The "acquisition of a leased asset" is considered for our purposes to be the entry of the leased asset in the FI-AA System. This does not necessarily mean that the leased asset must be capitalized. You can enter a leased asset simply to manage purely statistical data. You handle the leased asset as a master record, with no values in the book or tax depreciation areas.
    Posting the acquisition of a leased asset may be necessary for one of the following reasons:
    You have received a new leased asset (goods receipt).
    You need to change the way bookkeeping is handled for a leased asset due to a change in the conditions of the lease.
    You need to post a leased asset to a new asset master record due to a transfer.
    <b>Process Flow</b>
    Before posting the acquisition of the leased asset, you must determine the bookkeeping method to be used, either:
    Capitalization of the leased asset to fixed assets, with the present value of the future lease payments and depreciation of the present value (capital lease)
    Statistical management of the leased asset (no capitalization), and direct posting of the lease payments as rental expense in the profit and loss statement (operating lease)
    For more details.....
    http://help.sap.com/saphelp_47x200/helpdata/en/4f/71fd71448011d189f00000e81ddfac/frameset.htm
    If u satisfied... please assif=gn me points...
    Dasharathi

  • Lease Assets

    Hi there,
    Can you please explain how a capital lease works.  I have configured an operational lease and it works perfectly - updates the vendor account with all the payments due and the asset is not capitilised.
    What happens with the Capitilised lease - on creating the master data in AS01 does it automatically create the capitilization of the asset? Is there another posting we have to do eg an acquisition? does it create any line items in the vendor account?
    i am really interested and would like to know.
    Thank you
    Regards
    Jacqui

    Hi,
    Please check this and create asset as suggested by inputing the values in the tab for leasing.
    http://help.sap.com/saphelp_46c/helpdata/EN/48/ae9b9da63511d3a7320060087d1a6b/content.htm
    Trust this helps much!
    Cheers!

  • Varinat configuration

    Variant Configuration
    Variant configuration is for manufacturing complex products in which customer determines the features of the product. Objective of variant configuration is to react quickly to customers' requirements.
         Here it needs not to create separate material for each variant of a product. When companies introduce variant configuration this often goes beyond a business process re-engineering project. Variant configuration offers an opportunity to restructure product structures for which then processes are defined. This has a direct impact to the core areas such as marketing and product data management.
    2     Advantages of VC
    &#61623; No need to Create separate material master for each variant combination.
    &#61623; Super BOM and Super Routing is enough for representing all possible Variants and Operations.
    &#61623; Able to react more flexible to customer demands.
    &#61623; Increase Information exchange between sales, engineering and production.
    3     What is Configurable Material?
    &#61623; A material with different features or characteristics and options is known as configurable material. Example: PC, Car.
    &#61623; Configurable materials are either created in a material type that allows the configuration (n the standard system, the material type KMAT) or they are given the indicator Configurable in the material master record.
    4     Master Data used for VC
    Following Objects are used as Master data for Variant configuration.
    1. Super BOM
    2. Super Routing
    3. Characteristic
    4. Class
    5. Object Dependencies
    6. Configuration Profile
    7. SD Condition records
    4.1 Super BOM
    Super BOM Contains all the components for producing configurable product. It contains both variant as well as non-variant parts required for producing configurable product.
    4.1.1 Super BOM configuration
    Super BOM can be created either one of the following methods.
    &#61623; Create BOM with class Item of 200-class type that contains all characteristic of a configurable material.
    &#61623; Create BOM with all possible materials as its components. Then assign /define dependencies to each component.
    The different between this two method is
    &#61623; BOM with class item, no need to assign or define object dependencies. Instead of that each material is classified in material master itself using class 200.
    &#61623; For both cases all characteristics are assigned to class 300 which is again assigned to KMAT material in order to trigger configuration in configuration profile.
    4.1.2 Super BOM with Class Item
         Class items used to control the selection of variant parts in a BOM. Variant parts are classified in a class, and the class is entered in the BOM as a class item. When you configure the material, the class is replaced by a suitable variant part.
    4.1.3 Advantages of using Class Item in BOM
    &#61623; Only one item for the class is enough, instead of several items for the individual variant parts.
    &#61623; No need to create and assign selection conditions.
    &#61623; Able to classify additional objects in the class at any time, without having to change the BOM.
    4.1.4 Steps involved in super BOM with Class
    – Define all Characteristics and its Values assign it to Class with type 200.
    – Assign characteristic Values to materials by Classification  material
    – Assign class 200 with material instead of assigning all BOM items.
    – Create and Assign class 300 (with same characteristics) with configurable product using configuration profile.
    4.1.5 Super BOM with Material Components
    This bill of material (BOM) of a configurable material contains all the components that are required to manufacture the material. The BOM contains components that are only used in specific variants (variant parts), as well as components that are used in all variants (non-variable parts).
    4.1.6 Steps involved in super BOM with Material Components
    – Define all Characteristics and its values assign it to Class with type 300.
    – Assign Class with configurable material in Configuration profile.
    – BOM is created with all variant and non-variant items.
    – Define interdependency between objects (Characteristic, BOM item, Routing Operation etc…) by using Object Dependencies.
    – Assign class 300 with configurable product using configuration profile.
    4.2   Super Routing
         A configurable routing describes the production process for all variants of a product. Instead of creating a routing for each variant of a product, you can create operations for one routing, or a "super" routing.
    It is possible to maintain Object dependencies for following in super routing:
    &#61623; Sequences
    &#61623; Operations/sub-operations
    &#61623; Production resource/tool assignments
    The routing is configured by system, when order is created for KMAT material.
    4.3   Characteristic
    Characteristic is used to define the features of a configurable material. To enable to use characteristics to configure a material, assign the material to a class of class type 300. The customer can choose from among different options for each characteristic.
    &#61623; Characteristics describe the properties of objects. The values of a characteristic specify these properties.
    &#61623; Value assignment to characteristic may be single value or multiple value with required entry or restrict able entry.
    &#61623; In characteristic it is also possible to use table name and its field name in order to change the Object quantity or values. I.e. BOM item quantity or Operation time, which is known as ‘reference characteristic’.
    &#61623; In Restriction screen allowed Class types are entered i.e. for what are the class this characteristic may used. In general for Variant configuration class 200 and 300 are used.
    &#61623; It is also possible to assign Dependency to characteristic values maintained in Characteristic.
    4.4 Variant Class
    &#61623; In Variant configuration, Class is used to hold the characteristics that describe about configurable material. Class type to determine which object types can be classified.
    &#61623; Class is used in variant configuration if the class has a class type that supports variant configuration. In Customizing for Classification, the Variant class type indicator must be set for the class type. In the standard system, this is class type 300.
    4.5   Dependencies
    &#61623; Dependencies restricts the combinations of options i.e. characteristic that are not allowed. It also select exactly the right BOM components and operations to produce a variant.
    &#61623; It also describe the interdependencies between characteristics and characteristic values
    &#61623; It control which components are selected from a bill of material (BOM) and which operations are selected from a task list
    &#61623; It also changes the values of fields in BOM items and operations during configuration.
    4.5.1 Global and Local Dependencies
    Global dependencies have the following properties:
    &#61623; They are independent of any object.
    &#61623; They are identified by a name that you assign, and are maintained and managed centrally.
    &#61623; If you change a global dependency, the change affects all the objects where the dependency is used
    Local dependencies have the following properties:
    &#61623; They are only available to the object for which you create them
    &#61623; You cannot use the central maintenance functions on these dependencies, and you cannot allocate them to other objects
    &#61623; They are identified by a number assigned by the system, not an external name
    Local dependencies are only used where certain dependency will not be needed elsewhere
    The differences between global and local dependencies are as follows:
    &#61623; Global dependencies are created centrally and can be assigned to several objects.
    &#61623; Local dependencies are created for one object and can only be used with this object
    4.5.2 Declarative and Procedural Dependency
    &#61623; In Declarative dependencies the result are explained logically
    &#61623; Declarative dependencies are easier to trace than procedural dependencies, because the point in time when the dependency is processed and the sequence in which the dependencies are processed are not relevant.
    &#61623; Example for Declarative dependency:
    - Constraint
    - Actions
    - Preconditions (provided that they contain no non-declarative expressions)
    - Selection conditions (provided that they contain no non-declarative expressions)
    &#61623; In Procedural Dependency result depends on the processing sequence and the point in time when the dependency is processed.
    - Procedures
    - Preconditions (only if they contain non-declarative expressions)
    - Selection conditions (only if they contain non-declarative expressions)
    4.5.3 Dependencies Types
    The SAP System supports the following types of dependencies:
    &#61623; Preconditions
    &#61623; Selection conditions
    &#61623; Procedures
    &#61623; Actions (obsolete)
    &#61623; Constraints
    4.5.4 Preconditions
    Preconditions can be allocated to the following objects:
    &#61623; A characteristic that you want to hide
    &#61623; A characteristic value that you want to hide
    Preconditions are used to hide characteristics and characteristic values that are not allowed and thereby ensure that the configuration of an object is consistent. In the precondition, it is also possible define the circumstances under which a characteristic or value is hidden.
    A precondition is fulfilled if the condition you enter is either true or not violated.
    4.5.5 Selection Conditions 
    Selection conditions used to ensure that all the objects relevant to a variant are selected:
    &#61623; Selection conditions determine which variants require a specific component or operation
    &#61623; Selection conditions determine when it is mandatory to assign a value to a characteristic
    Selection conditions may allocate to the following objects:
    &#61623; Characteristics
    &#61623; BOM items
    &#61623; Operations in task lists
    &#61623; Sub-operations
    &#61623; Sequences of operations
    &#61623; Production resources/tools (PRTs)
    A selection condition is fulfilled if the condition in it is unambiguously true.
    4.5.6 Procedure
    Procedures can be assigned to the following objects:
    &#61623; The characteristic value that triggers the procedure
    &#61623; The characteristic that triggers the procedure
    &#61623; The configuration profile of the configurable object
    Procedure is used for following purposes.
    &#61623; A procedure is used to infer a value for a characteristic, you enter the variable $SELF before the characteristic.
    &#61623; Procedures can overwrite values that are set by other procedures.
    &#61623; Procedures are always used for pricing (see Variant Conditions).
    Processing Sequences of Procedure
    If an object has more than one procedure, a processing sequence is used to define the point when the procedure is processed.
    4.5.7 Action
    Actions are used to infer characteristic values. An action is processed as soon as the characteristic to which it is assigned has a value. It is not possible to overwrite the characteristic values that are set by an action.
    The following Objects can assign to action:
    &#61623; The characteristic value that triggers the action
    &#61623; The characteristic that triggers the action
    &#61623; The configuration profile of the configurable object
    &#61623; Configuration profile
    &#61623; BOM items – to change the quantity
    &#61623; Operations in task lists – to change the standard values
    Since Action is lead to serious system performance problems, it is replaced by Procedure and Constraint.
    4.5.8 Constraint
    This dependency type is mainly for intensively interactive configuration tasks and for configuration tasks in which you need to take into account the dependencies between the characteristics of several objects. The main purpose of a constraint is to monitor the consistency of a configuration.
    Constraints have the following distinguishing features:
    &#61623; Constraints are used to describe the dependencies between completely different objects and their characteristics.
    &#61623; Constraints are used to store information on which conditions must be fulfilled if the configuration is to be consistent.
    &#61623; Constraints are not directly allocated to individual objects. They are grouped together to form dependency nets and allocated to a configurable material in the configuration profile.
    &#61623; In constraints, you enter objects in their general form of expression, without using $SELF, $ROOT, or $PARENT to identify objects. As a rule, you refer to objects in constraints by entering the class to which the objects are allocated.
    &#61623; Constraints are declarative dependencies. The processing sequence of constraints and the point in time when constraints are processed is not relevant.
    &#61623; Constraints are not processed in a specific order. You cannot determine when a specific constraint is used.
    In any processing situation, a constraint is only processed once. If a value that is relevant to the constraint is changed, the constraint is triggered again.
    4.5.8.1 Structure of Constraints
    There are four sections in a constraint. Each part is identified by a keyword. A colon follows the keyword. Each section ends with a period.
    OBJECTS:
    In this section, you enter the objects that are relevant to the constraint. You must enter the relevant objects in all constraints. You can also define variables for objects or characteristics.
    CONDITION:
    The condition entered here must be fulfilled in order for the constraint to be used. You do not need to enter a condition in a constraint. You can leave out the keyword CONDITION: if required. However, if you enter the keyword you must enter a condition.
    RESTRICTIONS:
    In this section, you enter the relation that must exist between the objects and characteristics if the configuration is to be consistent. You must enter a restriction in a constraint.
    INFERENCES:
    In this section, you enter the characteristics for which characteristic values are to be inferred. The main purpose of constraints is to check the consistency of a configuration. Usually, values are only inferred if you make an entry in this section.
    For reasons of performance, only use constraints to infer values if it is really necessary. Constraints are grouped together to form dependency nets. The dependency net is allocated to a configurable material in the configuration profile.
    4.5.9 Dependency Net:
    Constraints are grouped together in dependency nets. For this reason, the variant configuration menu does not support a function for creating constraints directly. So that only constraints are defined within a dependency net.
    5     Configuration Profile
    The configuration profile for a material controls the configuration process in sales order. Configurable profile also used to define central settings for configuring the object. Using this profile it is possible to hide some of the characteristic value defined during characteristic creation. We can assign any number profile for a configurable material in which selection is based on either priority or manual selection during configuration.
    By defining a filter in the configuration profile, possible to determine the scope of the BOM items to improve system performance when exploding the BOM. The filter is active in high-level configuration, in result-oriented BOMs, and in SET processing.
    5.1     Filters in Configurable Profile
    Following objects can be used as filter:
    &#61623; Object type
    Class, material, document, text
    In the standard system, all object types are selected and therefore exploded in the configuration. Deselect the object types that you do not want to be displayed.
    &#61623; Item category, for example, stock or non-stock item
    All item categories in the configuration are exploded in the standard system. Remove the selection for the item categories you do not want to be displayed.
    &#61623; Item status
    You maintain the status of a BOM item in maintain BOM dependent on its usage.
    All items are displayed regardless of their item status in the standard system. However, only the items with this status are displayed when you select specific item statuses. Items are not displayed that do not have the selected status.
    &#61623; Sort string
    You can assign sort strings for BOM items in maintain BOM. You can restrict the display of the BOM items by using these sort strings.
    Only items that carry sort strings are checked and only those that match are displayed. Items that have no sort string are always displayed.
    5.2     Component availability in the configuration profile
    The availability check is just a snapshot, telling that whether the materials required are in stock at this moment. Several users can access the same material at once. This means that supply problems can sometimes be overlooked.
    Example: Only 2 pieces of a material are in stock, but the material is used in 3 BOMs. The availability check does not detect a supply problem. The availability check for all 3 BOMs shows 2 pieces in stock.
    5.3      Process Overview
    There are different processes for configurable materials in sales documents. These processes can be defined on the Configuration initial screen tab in the configuration profile, by choosing the Configuration parameter tab.
    The Process are described in the following scenarios:
    Planned/Production orders
    This processing type is used to describe variant products whose configurable materials are assembled using planned and production orders. The bill of material (BOM) can have single-level, multi-level, or no explosion.
         Sales Order (SET)
    This processing type is used to describe variant products that comprise salable configurable materials. These products are supplied together, but are not assembled in a production order. Only sales-relevant BOM items are exploded in the sales order.
    Order BOM.
    You use this processing type if you want to make customer-specific changes to the BOM of a material that you configure in the sales order. In the sales order, you assign values to the characteristics of the header material, but the BOM is not exploded in the sales order.
    6     Material Variant and Planning Material
    6.1     Material Variant
    &#61623; Material Variant is an material that can arises from individual Configuration of a configurable product and can be kept in stock
    &#61623; For variants that are required frequently, we can create material variants, which can be produced without a sales order and kept in stock. When a sales order is received, it is possible to check whether the variant required is in stock, so that it can deliver immediately.
    &#61623; For material variants, a separate material master record is created with a material type that is kept in stock.
    &#61623; Separate BOM and routing for a material variant, or you can link the material variant to the BOM and routing of the configurable material. The correct BOM items and operations are determined from the characteristic values assigned to the variant.
    6.2     Planning Material
    &#61623; Planning Material is a material, which contains all the non-variant parts.
    &#61623; By using planning material all non-variants are procured / produced before sales order.
    &#61623; It is also possible for Planing the Planning Materials without reference to any sales requirement.
    &#61623; Planning material is planned separately using strategy 65 and produced before sales order creation.
    7 Planing in VC
    The following strategies are used for planning configurable materials and its variant parts.
    Make to Order production of Variants
    – Make to Order for Material Variant. - 26
    – Planning Variants without final Assembly- 55
    – Planning Variants with planning Material - 65     
    – Make to order with configurable material.-  25
    – Characteristic Planning with dependent requirement - 56  and
    – Assembly Processing with Characteristic  Planning - 89
    8 Variant Configuration: (Object Diagram)
    9 Variant Pricing and  Surcharges
    9.1     Sales BOM
    A bill of material (BOM) describes the different components that together create a product. A BOM for a bicycle, for example, consists of all the parts that make up the bicycle: the frame, the saddle, wheels, and so on.
    When you enter the material number of a bill of materials that is relevant for sales order processing, the system displays the material that describes the whole bill of materials as a main item. The individual components are displayed as lower-level items.
    There are two ways to process a bill of materials in Sales. Once you have entered a bill of material in a sales order, the system runs pricing, inventory control, and delivery processing at: Main item level if the material is assembled, or - Component level if the material is not assembled.
    9.2     Processing at Main Item Level (ERLA)
    If you want the system to carry out pricing, inventory control, and delivery processing at main item level, enter ERLA in the Item category group field of the Sales: sales org. 2 screen in the material master record of the finished product. This means that the components only function as text items and are not relevant for delivery.
    9.3     Processing at Component Level (LUMF)
               If you want the system to carry out pricing, inventory control, and delivery processing at the component level, enter LUMF in the Item category group field of the Sales: sales org. 2 screen in the material master record of the finished product. In this case, only the components are relevant for delivery. During processing the system automatically creates a delivery group. The latest delivery date among all the components becomes the delivery date for the entire delivery group.
    10   Configuration of VC
    10.1 Production Planning and Control
    10.1.1 Creating Material
    Use
    The purpose of this activity is to create the material masters for the materials required in this scenario.
    Procedure
    Access the activity using one of the following navigation options:
    SAP Menu     Logistics &#61614; Materials Management &#61614; Material Master &#61614; Material &#61614; Create (General) &#61614; Immediately
    Transaction Code     MM01
    In Material Master of KMAT material following settings are maintained:
    &#61623; Configurable material indicator in Basic Data must set.
    &#61623; MRP type is PD.
    &#61623; Lot size – EX ( Lot for lot size)
    &#61623; Availability check – 02
    &#61623; Planning Strategy 25 is entered in MRP 3 screen view.
    &#61623; Item category group 0002 or 0004 is to be given in sales view.
    10.1.2 Creating Bill of Material
    Purpose:
    &#61623; The purpose of this activity is to create bills of material (BOMs) for the configurable material which is known as ‘super BOM’
    &#61623; Super BOM comprise all the variant as well as non-variant parts required for producing configurable material.
    Procedure
    1. Access the activity using one of the following navigation options:
    SAP Menu     Logistics &#61614; Production &#61614; Master Data &#61614; Bills of Material &#61614; Bill of Material &#61614; Material BOM &#61614; Create
    Transaction Code     CS01
    &#61623; The Create Material BOM: initial screen appears. On this screen, data that identifies the bill of material are maintained as well effectivity data.
    &#61623; In the Material field, the configurable material for which super BOM need to create is entered.
    &#61623; Plant and BOM usage is entered. In general BOM usage 1 for production and 3 is for Universal.
    &#61623; In Component screen list of variant and non-variant parts are entered along with that quantity is entered based on Base qty. of the configurable material.
    &#61623; It is also possible to enter a class as a BOM component with item category ‘class Item’. This class must hold all characteristics and also classified with each material.
    &#61623; Class type 200 and 300 can be used as a class item.
    Following Procedure is followed for assigning class with BOM as a class Item.
    &#61623; Enter the item category for class items in BOM.
    &#61623; Make entries in the fields that identify the class
    – Class types
    – Class
    &#61623; Enter the quantity.
    - Enter a unit of measure if appropriate.
    - The system determines the unit of measure from the additional data of the class.
    -  If a unit of measure without a dimension is maintained in the additional data of the class, you cannot change this unit.
    10.1.3 Creating Characteristic
    Purpose:
    &#61623; Characteristic is created with possible values.
    &#61623; It is also possible to use table name and its field name in order to change the Object quantity or values. Ie BOM item quantity or Operation time. This is known as ‘Reference characteristic’.
    &#61623; For changing BOM quantity Characteristic is created with table name STOP-MENGE is used.
    &#61623; For Variant pricing purpose SDCOM-VKOND is used.
    &#61623; Characteristics allow describing and distinguishing between objects, such as length, color, or weight within the classification system.
    Procedure
    SAP Menu     Logistic->Centralfunction->Environment->classification->Chracteristics
    Transaction Code     CT04
    &#61623; From the classification menu, choose Characteristics.
    &#61623; Enter data on the initial screen.
    &#61623; In the Characteristic field, enter a name for new characteristic
    &#61623; Enter a change number if you want to create the characteristic using engineering change management.
    &#61623; To do this, choose processing type Create characteristic.
    &#61623; You can also copy the data of an existing characteristic. Use the pushbutton Create by copying. Enter the name of a characteristic you want to copy.
    &#61623; Confirm the entries.
    &#61623; On the Basic data tab page enter the most important control data for the characteristic.
    &#61623; You must maintain the basic data for all characteristics. All other screens are optional.
    &#61623; In the formatting data for value assignment, whether a characteristic is single-value, multiple-value, or retractable is defined. It is not possible change the value assignment indicator once it has set. It applies wherever the characteristic is used.
    &#61623; The data type of the characteristic determines which values can be entered for the characteristic. I can any one of the following
    - Characters
    - Numeric
    - Time format/Date format
    - Currency format and
    - User defined data type.
    &#61623; For numeric characteristic it need to maintain that whether interval values to a numeric characteristic, or only individual values need to be maintain in Basic Data screen itself.
    &#61623; Languages in which characteristic want to describe are entered.
    &#61623; Choose the tab page Values.
    &#61623; Enter values in the entry fields. Enter each value in a separate field.
    &#61623; The values must match the format that you defined on the Basic Data screen. You can enter up to the number of characters that you defined in the format.
    &#61623; If your characteristic is an alphanumeric characteristic, enter a language-dependent value description. You can enter up to 30 characters.
    &#61623; It is not possible to  enter a language-dependent description for numeric values
    &#61623; It is also possible to define one value as a default value. This value then appears as a default in characteristic value assignment functions
    &#61623; Additional value indicator determines that whether values that are not defined as allowed values can be assigned to a characteristic
    &#61623; The following value check strategies are available in value maintenance screen.
    - Allowed Values:
    - Check Tables
    - Function module
    - Catalog character
    &#61623; Allowed values permits only values defined in characteristics maintenance are used to check a characteristic value
    &#61623; Check table permits only values entered in characteristics maintenance is used to check a value
    &#61623; Function module entered is used to check characteristic values.
    &#61623; Value catalog entered is used to check characteristic values
    &#61623; Documents, such as drawings or photographs, with characteristics can be linked in additional data screen. Before link a document to a characteristic, it must create a document info record in the document management system.
    &#61623; In this screen it also possible to restrict or hidden or displaying only allowed values to characteristic.
    &#61623; It is possible to that characteristic can be only assigned to particular class type by assigning type in restriction screen.
    &#61623; To change a characteristic selects the pushbutton Change in characteristics after entering the characteristic. To display the characteristic chooses the pushbutton Display.
    10.1.4 Creating Class:
    Purpose:
    &#61623; A class is used to hold the characteristics that describe a configurable material. By linking the class to the configurable material, you allow the material to be configured using the characteristics of the class.
    Procedure
    SAP  Menu     Logistic->Central function->Environment->classification->Class
    Transaction Code     CL01
    &#61623; Class holds all characteristics describe configurable material.
    &#61623; Class with class type 300 is used in configuration profile.
    &#61623; On basic Data screen class description, its status is entered. Status determines:
    &#61623; whether a class can be maintained
    &#61623; whether objects can be allocated to a class
    &#61623; whether the class can be used for selecting objects
    &#61623; Class group is used to group together related classes and also for finding classes quickly via a matchcode.
    &#61623; ‘Same Classification ‘indicator determines whether system check for identical characteristic values. In this case, where several objects are assigned that have the same values for all characteristics to the same class. Depends upon indicator system give warning or error message or no message.
    &#61623; Keyword string is used for finding a class via matchcode.The description entered on the basic data screen serves as the first keyword
    &#61623; On characteristic screen list characteristic which has to attach with configurable material is entered.
    &#61623; Using document tab screen it is possible to assign documents related to configurable object.
    &#61623; On additional data screen whether or not this class can be used as a class component in bills of material. If it is yes then Unit of measure in which stocks of the material are managed. The system converts all the quantities you enter in other units of measure (alternative units of measure) to the base unit of measure and resulting item category which will replace this class item in BOM (i.e. Stock, Non-stock item etc…).
    10.1.5 Creating Dependency
    Purpose
         Dependency describes the interdependencies between characteristics and characteristic values and it controls which components to be selected from a bill of material (BOM) and which operations to be selected from a task list. It also changes the field values in BOM items and operations during configuration.
    Procedure
    SAP  Menu     Logistic->Central function->Variant Configuration->dependency->Single Dependency->Create Dependency
    Transaction Code     CU01
    &#61623; From the variant configuration menu, choose Dependency -> Single dependency-> Create
    &#61623; In initial screen name of the dependency is entered. If dependency need to create for a specific date, enter a change number. It is also possible to create dependency by copying from existing dependency.
    &#61623; On basic data screen the following data are required to enter
    - A language-dependent description for the dependency
    - Also possible to enter descriptions in different languages by choosing Descriptions.
    - Long texts for the dependency, choose Extras -> Documentation.
    - In the standard R/3 System, the status ‘In preparation’ when a dependency is created first time. The status is set to ‘Released’ when the source code is syntactically correct.
    - Finally suitable dependency type is selected.
    &#61623; In Dependency editor the source code for the dependency is entered. Once the source code is syntactically correct, the source code is saved.
    &#61623; Now the status of the dependency is turns to ‘Released’. Save the Dependency and exit.
    10.1.6 Changing Bill of Material (Assign Dependencies)
    Purpose:
    By assigning dependencies to BOM components, it is possible to restrict the selection of irrelevant variant parts.i.e correct BOM components are get selected at result of configuration. It is also possible to change the component quantity depends upon characteristic value changed.
    Procedure
    1. Access the activity using one of the following navigation options:
    SAP Menu     Logistics &#61614; Production &#61614; Master Data &#61614; Bills of Material &#61614; Bill of Material &#61614; Material BOM &#61614; Change
    Transaction Code     CS02
    &#61623; Dependencies are assigned with respect to characteristic for each variant part.
    &#61623; Dependencies are created either locally within object or globally which can be assigned to any objects.
    &#61623; In BOM General Item overview screen choose the component in which dependency need to assign and choose menu path Extras -> Dependency -> assignment of dependency for assignment.
    &#61623; It also possible to enter dependency directly in BOM itself by choosing Extras -> Dependency -> dependency editor.
    10.1.7 Creating Configuration Profile
    Purpose
    &#61623; Configuration profile used for assigning configurable material with variant class (300) and also used to maintain some central settings.
    &#61623; It is possible to assign more than one configurable profile for one KMAT material.
    &#61623; The selection of profile depends upon either by priority or by manual selection.
    &#61623; It is also possible to assign dependencies to configurable profile.
    &#61623; Class with type 300, which hold the entire characteristics of KMAT material, are assigned to each profile
    Procedure:
    Access the activity using one of the following navigation options:
    SAP Menu     Logistics &#61614; Production &#61614; Master Data &#61614; Material Master &#61614; Environment &#61614; Configuration Profile &#61614; Create
    Transaction Code     CU41
    &#61623; From the Variant Configuration menu, choose Configuration profile->Create.
    &#61623; A dialog box will be displayed. The object name is entered. Confirm your entries.
    &#61623; On profile overview screen the following data need to be entered.
    &#61623; Profile name and the class type of classes used for configuration. In Customizing for the Classification System, the class type must be defined as a variant class type.
    &#61623; Choose Goto -> Class assignments or the ‘Class assignment ’ pushbutton to assign the object to a class.
    &#61623; In the classification screen, names of the classes are entered.
    &#61623; It is possible to restrict allowed characteristic  values for the configurable object if required.
    &#61623; Release of profile is possible only if configurable object is assigned to a class. To go to the detail screen, where you define further settings, choose the Profile detail pushbutton or double-click on the profile.
    10.1.7.1 Optional Settings on the Profile Overview
    &#61623; Organizational Areas
    You can specify organizational areas for configuration. If you restrict a profile to specific organizational areas, you only see the characteristics that are relevant to your area when you configure the object.
    You can change how characteristics are displayed according to organizational area for your user on the value assignment screen.
    &#61623; Priority of Configuration Profiles
    You can create several configuration profiles for a configurable material. The profile with the lowest number has the highest priority.
    If you define several profiles for an object, you see a dialog box for selecting a profile when you start configuration. The profile with the highest priority is at the top of the list.
    The priority is also relevant if you use Application Link Enabling (ALE) or intermediate documents (IDocs) to run configuration, rather than dialog mode. In this case, the profile with the highest priority is selected for the object. Profiles that have no priority are at the top of the list, because they automatically have priority 0.
    10.1.7.2 Profile Detail
    &#61623; Configuration Profiles for Materials
    The configuration profile has several screens. Depending on what you enter for the BOM explosion and configuration process, fields are shown or hidden.
    The parameters you maintain for a material apply to the material as a header material in a BOM structure. You cannot define separate settings for use of a configurable material as an assembly in a BOM.
    - By choosing the Assignments pushbutton, you can assign dependencies to the configuration profile. You also see this pushbutton on the basic data tab, once at least one dependency is assigned.
    &#61623; Basic Data Tab
    - In the basic data, click on the profile overview data.
    - If configuration process need to starts with a Start logo, documents are assigned such, as a graphic showing the product you want to configure, to the variant class.
    - Configuration Initial Screen Tab
    &#61623; Configuration parameters
    - The parameters for BOM explosion and the configuration process in the sales order are specified here.
    - BOM application must be entered, if BOM explosion ‘None’ is selected rather than single and multi level explosion is selected.
    - By entering a level of detail for a multi-level configuration, system performance will be improved.
    - It is also possible to define a filter and set the indicator for an availability check on assemblies.
    10.1.8 Changing Configuration Profile: Add User Interface Settings
    Purpose
    Settings for the configuration editor in user interface.
    - An interface design is used to group characteristics together on the value assignment screen.
    - Here it also possible to define object-specific settings for functions in the configuration editor. These settings are defaults for configuration, and can be overwritten for your user in the configuration editor.
    - For all configuration parameters except BOM explosion ‘None’, manually select the screens for the configuration editor and define which screen configuration starts with. The start screen must be one of the allowed screens.
    - The indicator for the configuration browser independently of the other start screens can be selected, because the browser is an additional screen section.
    Configuration Profiles for Objects Other than Materials
    - Object-specific settings for displaying characteristics and characteristic values in the configuration editor can be defined. These settings are defaults for configuration, and can be overwritten for your user in the configuration editor.
    Procedure
    Access the activity using one of the following navigation options:
    SAP Menu     Logistics &#61614; Production &#61614; Master Data &#61614; Material Master &#61614; Environment &#61614; Configuration Profile &#61614; Change
    Transaction Code     CU42
    10.1.9 Configuration Simulation
    Purpose:
    &#61623; Configuration simulation is used to check the configuration model. In the configuration simulation, the whether or not Object structure is created correctly and dependencies are working fine is checked.
    &#61623; Simulation of Sales/Engineering
    - The configuration parameters in the configuration profile apply. Whether the configuration is simulated from the sales point of view or the engineering point of view is defined.
    - If select Sales & distribution is selected the configuration in a sales document will be simulated (sales order or quotation), so the BOM explosion depends on the settings in the configuration profile.
    - If Engineering is selected, the configuration in order BOM processing will be simulated. The configuration and BOM explosion depend on the configuration parameters in the same way as when maintaining an order BOM. For example, we cannot configure the header material, because the configuration is copied from the sales order.
    &#61623; Simulation of a Planned Order
    - On the characteristic value assignment screen, we can choose Planned order to display the components that are determined in material requirements planning (MRP) according to the characteristic values assigned. This is especially relevant to assemblies whose BOMs are exploded in MRP, not in Sales & distribution (for example, assemblies with the BOM explosion setting None in their configuration profile).
    Procedure:
    SAP R/3 menu     Logistics &#61614; Production &#61614; Master Data &#61614; Bills of Material &#61614; Environment &#61614; Variant Configuration &#61614; Environment &#61614; Configuration Simulation
    Transaction Code     CU50
    &#61623; On the initial screen of the configuration simulation, select BOM to display the entire structure on the result screen.
    &#61623; If you have created more than one configuration profile for a material, you see a dialog box. Select a profile and choose Continue. If you want to call detailed information on the profile, choose Profile Detail or double-click on the profile.
    &#61623; To display the task list of an assembly on the result screen, select the assembly and choose View &#61614; Objects &#61614; Task list.
    &#61623; You see the operations or activities in the task list that was selected for the assembly during configuration.
    &#61623; Operations that have been changed by dependencies have an information icon next to them. You can display changes by choosing Information.
    &#61623; To return to the BOM explosion, choose View &#61614; Objects &#61614; BOM
    10.2 Sales and Distribution
    10.2.1 Creating Condition Records - VA00
    Purpose:
    The purpose of this activity is to create condition records for VA00.
    Procedure
    1. Access the activity using one of the following navigation options:
    SAP Menu     Logistics &#61614; Sales and Distribution &#61614; Master Data &#61614; Conditions &#61614; Select Using Condition Type &#61614; Create
    Transaction Code     VK11
    &#61623; Create price for each value of the characteristics by select using condition type VA00.
    &#61623;  Create the Price for the condition type that represents these types of the standard-delivered condition type for this functionality is “VA00.” 
    &#61623; Condition type VA00 requires as key fields the sales Organization, distribution channel, and material number of the configurable.
    &#61623; Condition type PR00 used to maintain base price of the configurable material.
    &#61623; Using VA01it is also possible to maintain Surcharges and discounts.
    10.2.2 Condition records for Variant Price and Surcharges
    Purpose
    Condition records allow you to store and retrieve pricing data in the system. All the pricing elements of your daily business - the prices, discounts, and surcharges for freight and taxes - that you want to use for automatic pricing must be stored in the system as condition records. You can define as many condition records as you want for the different pricing elements for any validity period.
    You create condition records for all the pricing elements that the system takes into account during automatic pricing. During document processing, the system transfers data from the condition records and determines the amounts for individual pricing elements (prices, discounts and surcharges) and the final amount for the sales document
    Procedure
    10.2.2.1 Create a characteristic for the Pricing
    - Create Pricing characteristic like CAR_Pricing and go to additional data tab give SDCOM table name VKOND field name.
    SAP Menu     Logistic->Centralfunction->Environment->classification->Chracteristics
    Transaction Code     CT04
    10.2.2.2   Assign  the characteristic to the class
    Assign given characteristics to class, In variant configuration, a class is used to hold the characteristics that describe a configurable material. By linking the class to the configurable material, it allows the material to be configured using the characteristics of the class. In the standard R/3 System, the class type for configurable material is 300.
    SAP  Menu     Logistic->Central function->Environment->classification->Class
    Transaction Code     CL01
    10.2.2.3 Create a dependency that triggers the price
    A Dependency is a rule that defines how the different options and option values, represented by characteristics and characteristic values, relate to one another.  To create a dependency, follow the menu path
    SAP  Menu     Logistic->Central_function->VariantConfiguration->dependency->Single Dependency->Create Dependency
    Transaction Code     CU01
    10.2.2.4   Assign the dependency to the characteristic value that triggers the price
    For example eCar2002, the value “V8” refers to the engine selected by the customer.  Therefore, the dependency must be linked to the value “V8” of the characteristic that represents the engine type.  To do this, go to the master data record of the characteristic CAR_ENGINE
    SAP Menu     Logistic->Centralfunction->Environment->classification->Chracteristics
    Transaction Code     CT04
    Go to the “Values” tab.  From there, select the“V8” entry and use the menu path Extras Object dependencies Assignments, which brings you to the screenshot to the right; if you have created a global dependency, you can link it to the characteristic value.2 Once the dependency has been assigned, the information on this screen, such as the description (“Engine price”), will default to the information entered when you created the characteristic.
    10.2.2.5    Create variant price
      Create price for each value of the characteristics using condition type (or transaction VK11).  Create the Price for the condition type that represents these types of the standard-delivered condition type for this functionality is “VA00.”  Condition type VA00 requires as key fields the sales Organization, distribution channel, and material number of the configurable.
    In the same way using condition type VA01 is also used to maintain prices for surcharges and discounts.
    10.2.2.6   Creating the output condition records for sales
    Output types are used to represent various forms of output in the SAP system. Examples of output types in Sales and Distribution processing are order confirmations, freight lists, and invoices. You use the output type to control how the output should be transmitted, for example whether an order confirmation should be sent via EDI, or be printed
    10.2.3 Creating Output Condition Records: Sales
    Purpose:
    Output types are used to represent various forms of output in the SAP system. Examples of output types in Sales and Distribution processing are order confirmations, freight lists, and invoices. You use the output type to control how the output should be transmitted, for example whether an order confirmation should be sent via EDI, or be printed
    Procedure
    1. Access the activity using one of the following navigation options:
    SAP Menu     Logistics &#61614; Sales and Distribution &#61614; Master Data &#61614; Output &#61614; Sales Document &#61614; Create
    Transaction Code     VV11
    &#61623; Choose Edit >Key combination
    &#61623; Select the key combination for which condition records are to be created.
    &#61623; Choose Enter.
    &#61623; Enter the appropriate key for each condition record, according to the key combination you selected.
    &#61623; For transmission medium 1 (Print output) or 7, you can maintain the communication data. To do this, choose Communication.
    &#61623; Save the condition records.
    10.2.3.1 Creating Output Condition Records: Billing
    Purpose
    The purpose of this activity is to create output condition records for billing. Output types are used to represent various forms of output in the SAP system. Examples of output types in Sales and Distribution processing are order confirmations, freight lists, and invoices. You use the output type to control how the output should be transmitted, for example whether an order confirmation should be sent via EDI, or be printed
    Procedure
    1. Access the activity using one of the following navigation options:
    SAP Menu     Logistics &#61614; Sales and Distribution &#61614; Master Data &#61614; Output &#61614; Billing Document &#61614; Create
    Transaction Code     VV31
    Enter an output type.
    &#61623; Choose Edit >Key combination
    &#61623; Select the key combination for which condition records are to be created.
    &#61623; Choose Enter.
    &#61623; Enter the appropriate key for each condition record, according to the key combination you selected.
    &#61623; For transmission medium 1 (Print output) or 7, you can maintain the communication data. To do this, choose Communication.
    &#61623; Save the condition records.
    10.2.4 Order BOM
    Purpose:
    Products that are made to order in plant engineering and construction and mechanical engineering are generally very complex and are specific to one customer. For this reason, you cannot define a BOM entirely in advance. Once you have created your sales order, you need to make manual changes to the BOM by creating an order BOM especially for the sales order, without changing the original BOM.
    The sales order, sales order item, and material number identify an order BOM. In variant configuration, you can work with 2 types of order BOM. The difference is in the way they are saved.
    Knowledge based order BOM
    The order BOM is saved as a copy of the super BOM with manual changes and dependencies.
    Result Oriented BOM
    The configuration result is saved as an order BOM, with manual changes but without dependencies.
    Procedure (For knowledge based BOM)
    SAP Menu     Logistics &#61614; Production Planning &#61614; Master Data &#61614; Bills of Material -> Order BOM  Maintain (Multi-Level)
    Transaction Code     CU51
    &#61623; The Create Order BOM: initial screen appears.
    &#61623; Enter the sales order number, the order item, the material number and the BOM usage
    &#61623; If you want to use material BOM, or an existing order BOM to copy from, go to step 4. If you want to create an order BOM without a reference, click and go to step 7
    &#61623; You cannot use a configurable BOM as a reference
    &#61623; Click on copy order BOM or Click on copy material BOM
    &#61623; The Copy material BOM or Copy order BOM dialog box appears
    &#61623; Enter the data required and click . The item overview appears, for the bill of material you are using as a reference.
    &#61623; Enter new items and alter items if necessary. Entering items in order BOMs is similar to entering items in material BOMs. However, you

    <u><i><b>Steps for SD Variant Configuration</b></i></u>
    Some light on Variant Configuration in Detail.
    The procedure is as follows:
    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
    3. 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)
    4. Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.
    5. Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.
    Now 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.
    Reward if it helps
    Regards,
    Anbu

  • When trying to setup a new Operating Unit gives an error: FRM-40735: PRE-FORM trigger raised unhandled exception ORA-06502

    EBS - Payables - Version 12.1.3.
    We Have many others Operating Units configured and no errors occurs.
    This error occurs only if we set a new OU.
    All profiles have been configured properly. (MO: Operating Unit, HR: Security Profile, etc..)
    The trace shows:
    SELECT PROFILE_OPTION_VALUE
      FROM FND_PROFILE_OPTION_VALUES
    WHERE PROFILE_OPTION_ID = 5852                           
       AND APPLICATION_ID = 178
       AND LEVEL_ID = 10003
       AND LEVEL_VALUE = 124280
       AND LEVEL_VALUE_APPLICATION_ID = 200        
       AND PROFILE_OPTION_VALUE IS NOT NULL
    The PROFILE_OPTION_ID = 5852   is  "ICX:Session Timeout".
    If I set this profile the error does not occur. But its is very strange to have to configure it for a responsibility level.

    Hi All.
    I discovered what the problem was.
    The size of the name of the responsibility was with many characters.
    Reduced the size and the error stopped occur.
    Tks!

  • Refx lease rental cash flow for non-cancellable contracts

    Dear Refx Group,
    As per Accounting Standard (AS) 19 - Leases, the lessee should make the following disclosures for operating leases:
    a) the total of future minimum lease payments under non-cancellable operating leases for each of the  following periods:
    ('i) not later than one year;
    (ii) later than one year and not later than five years;
    (iii) later than five years;
    Is there any standard report or any methodology whereby we can get the above information.
    Regards,
    Sudhir Chattapan

    Dear Refx Group,
    As per Accounting Standard (AS) 19 - Leases, the lessee should make the following disclosures for operating leases:
    a) the total of future minimum lease payments under non-cancellable operating leases for each of the  following periods:
    ('i) not later than one year;
    (ii) later than one year and not later than five years;
    (iii) later than five years;
    Is there any standard report or any methodology whereby we can get the above information.
    Regards,
    Sudhir Chattapan

  • Automatically post the lease rental charges for oprating lease asset using

    hi
    i tried that way which you have given but the wht tac and tax code i am not getting
    anyone can send  the coding accordingly
    the requirement is like that
    Company code (BUKRS)  - Mandatory 
                 Asset class (ANLKL)  - Mandatory -
                 Vendor (Leasing company) (LEAFI) - Mandatory
                 Business Place (BUPLA)
                 WHT Tax code (QSSKZ)
                 Tax code  (MWSKZ)
                 Document type (BLART) - Mandatory
                 Document Date (BLDAT) ) - Mandatory
                 Posting Date (BUDAT) - ) - Mandatory
                 Reference (XBLNR) - ) - Mandatory
                 Document Header text (BKTXT) - ) - Mandatory
    Logic: 
    Pass the values in ANLA for .
    Company code-BUKRS
    Asset Class-ANLKL
    Vendor (Leasing company)-LEAFI
    Get ANLA-ANLN1 and Lease payment (ANLA-LEGEB) from ANLA table
    where Leasing Type ANLA-LEART=02(Operating Lease) . Check Deactivation date ANLA-DEAKT=space OR Posting date in selection BUDAT<= ANLA-LKDAT
        After getting all Assets related to selection vendor post the lease rental document by calling F-02 transaction code (Check BAPI available)
    The program should post the lease payment amount by crediting vendor with sum of lease payment for all assets selected for this vendor and debiting the individual lease payments to u2026u2026. 
    Checks at the time of posting:
    1. Pass the Business place value in to Section code also
    2. Ensure except WHT code entered in selection screen, all the other WHT codes are deleted at the time of posting.
    3. At the time of posting document in the lease rental for Asset line item text it should fill with u201CLease rent for Asset numberu2026u2026u2026for the month of u2026.u201D
    Edited by: jnanaranjan.paikray on Jul 30, 2010 9:26 AM

    hi raj
    i got it
    thk for everything

Maybe you are looking for

  • Logic bounces won't open in Sound Studio

    Properly speaking, this is a Sound Studio (2.0.7) problem, but as I've used it for many months (and would like to continue) for minor tweaking of bounced Logic AIFs, I'm hoping someone will have some idea as to what's going on here. Since I got my G4

  • I would like to see history on my form from Day 1, currently I can only see partial history! Help!

    I would like to see history on my form from Day 1, currently I can only see partial history! Help!

  • Blue Screen of Death on Startup

    I have been using Windows 7 x64 for about 3 months but recently, whenever I boot into Windows 7 it starts the load and gets up to the animation then it BSODs with this error code: Stop 0x000000ED UNMOUNTABLEBOOTVOLUME I believe this may be linked to

  • Is the non-multi-room DVR also 500 hours?

    My ReplayTV just died and I am thinking of upgrading to a FiOS DVR. We currently have a multi-room DVR that my daughter uses and I don't want to share it with her (and vice versa) plus it's the old 80 hour model. It seems like I can only get one mult

  • I cannot capture Audio

    MacBook Pro 2.33 GHz Final Cut Pro 5.1.4 Quicktime Pro 7.1.5 JVC Camcorder GR-DV4000E Connected via firewire direct to the MacBook I have reinstalled Quicktime and trashed the FCP preferences. When I go to Audio/Video settings>Capture Presets and edi