FIFO valuation at material level

Hi masters of SAP!
I have a question about FIFO valuation I know the answer for because I have been reading SAP help on this subject but I am reluctant to beleive that cannot be done any other way.... For FIFO valuation if you read the documentation on it will work the following way:
Period 1 -> 10 unist at 10 £/unit
Period 2 -> 10 units at 5 £/unit
Period 3 -> 5 units at 3 £/unit
If at the end of period 3 we have 7 units left and we want to calculate FIFO value on this stock SAP will do the following:
5x3 + 2x5 = £25 (this is correct)
25/7= £3.571/unit , the system will go and populate all 7 materials with this average price (this is wrong in my opinion, since the system should value differently the 5 units from period 3 and the 2 from period 2)... This is not FIFO, is it?.
Has anyone known any other way so that the material price in the extra fields of the material master gets updated accordingly to the price they were adwuired at?
Please, surprise me!!
Thanks
Mario

I never worked on 45b, but with 46c and Ecc6 it is possible to restrict based on materail type by using authorization object M_MATE_MAR

Similar Messages

  • FIFO Valuation with Material Ledger !

    Hi, 
    How do we accomplish FIFO Valuation using Material Ledger ?
    We have activated the Material Ledger, with Single - Level Determination; Standard Price S.  On execution of Single-Level Price Determination, we get the Periodic Unit Price -- which is the Weighted Average Price for the Receipts for the period involved.
    I came across SAP Forums, which claim that Material Ledger is the FIFO Valuation on real-time basis. However, this doesn't seem to be true. The Goods Issued are assigned the Periodic Unit Price (calculated above -- i.e the Weighted Average Price ).
    In addition, we have Configured the FIFO Balance Sheet Valuation Procedure, through the MM menu. The FIFO Value for the Material is giving weird results. Adding the total Inventory for all the Receipts till date and over-riding the period selection for Single Receipts.  For monthly receipts, the system just gives the Weighted Average Price again.
    The Business is expecting the FIFO valution for the Inventory Balance on Monthly Basis. ( We are using Material Ledger, so that we can roll-up this FIFO Valuation  of the Raw Material ito Gross up into the Finished Product
    -- Thanks

    Hi Kenny ,
    BASIC STEPS THAT CAN BE FOLLOWED FOR  ENDING INVENTORY VALUATION :
    Ending Inventory is valued  as per FIFO calculated through following steps:
         Run the price calculation (Txn: KSII) u2013 check that all      auxiliary Cost centers are zero
         Run Txn:MRF3 (summarization of documents for the      FIFO calculation.)
         Run MRF1 (calculation of FIFO)
         Check if the FIFO calc. is correct via MR35
    After ML run the ending inventory value should be equal to the value in MR35 and so balance amount not yet loaded to ending inventory through FIFO valuation is posted to consumption
    Exception: If total receipts for a period is less than ending inventory quantity .In this case the EI is valued at weighted average
    Please check wether the steps have been properly followed and the execption doesnot exists..
    Also, hope your Price Determination is "3" and price control is "S" in Material Master..
    Regards
    Sarada

  • MM42 change material, split valuation at batch level, M301, locking table

    Dear All,
    I'm working on ECC 6.0 retail and I have activated split valuation at batch level.  Now in MBEW for this specific material I have almost 14.400 entries.
    If I try to change some material data (MM42) I receive an error message M3021 A system error has occurred while locking and then Lock table overflow.
    I used SM12 to see the table (while MM42 is still running) and it seems that MBEW is the problem.
    What should I do?  For any material modification the system has to modify every entry in MBEW? Is there any possibility to skip this?
    Thank you.

    Hi,
    Symptom
    Key word: Enqueue
    FM: A system error has occurred in the block handler
    Message in the syslog: lock table overflowed
    Other terms
    M3021 MM02 F5 288 F5288 FBRA
    Reason and Prerequisites
    The lock table has overflowed.
    Cause 1: Dimensions of the lock table are too small
    Cause 2: The update lags far behind or has shut down completely, so that the lock entries of the update requests that are not yet updated cause the lock table to overflow.
    Cause 3: Poor design of the application programs. A lock is issued for each object in an application program, for example a collective run with many objects.
    Solution
    Determine the cause:
    SM12 -> Goto -> Diagnosis (old)
    SM12 -> Extras -> Diagnosis (new)
    checks the effectiveness of the lock management
    SM12 -> Goto -> Diagnosis in update (old)
    SM12 -> Extras -> Diagnosis in update (new)
    checks the effectiveness of the lock management in conjunction with updates
    SM12 -> OkCode TEST -> Error handling -> Statistics (old, only in the enqueue server)
    SM12 -> Extras -> Statistics (new)
    shows the statistics of the lock management, including the previous maximum fill levels (peak usage) of the partial tables in the lock table
    If the owner table overflows, cause 2 generally applies.
    In the alert monitor (RZ20), an overrunning of the (customizable) high-water marks is detected and displayed as an alert reason.
    The size of the lock table can be set with the profile parameter u201Cenque/table_size =u201C. specifies the size of the lock table in kilobytes. The setting must be made in the profile of the enqueue server ( u2026_DVEBM.. ). The change only takes effect after the restart of the enqueue server.
    The default size is 500 KB in the Rel 3.1x implementation of the enqueue table. The resulting sizes for the individual tables are:
    Owner table: approx 560.
    Name table: approx 560.
    Entry table: approx 2240.
    As of Rel 4.xx the new implementation of the lock table takes effect.
    It can also be activated as described in note 75144 for the 3.1I kernel. The default size is 2000 KB. The resulting sizes for the individual tables are:
    Owner table: approx 5400
    Name table: approx 5400
    Entry table: approx 5400
    Example: with the
    u201Cenque/table_size =32000u2033 profile parameter, the size of the enqueue table is set to 32000 KB. The tables can then have approx 40,000 entries.
    Note that the above sizes and numbers depend on various factors such as the kernel release, patch number, platform, address length (32/64-bit), and character width (Ascii/Unicode). Use the statistics display in SM12 to check the actual capacity of the lock table.
    If cause 2 applies, an enlargement of the lock table only delays the overflow of the lock table, but it cannot generally be avoided.
    In this case you need to eliminate the update shutdown or accelerate the throughput of the update program using more update processes. Using CCMS (operation modes, see training BC120) the category of work processes can be switched at runtime, for example an interactive work process can be converted temporarily into an update process, to temporarily increase the throughput of the update.
    For cause 3, you should consider a tuning of the task function. Instead of issuing a large number of individual locks, it may be better to use generic locks (wildcard) to block a complete subarea. This will also allow you to considerably improve the performance.

  • How to activate FIFO Valuation?

    Hi,
    We need to follow the steps if we need to valuate our inventory by means of FIFO Scenario (I got the link from SDN)
    1. In T-code OMWE, activate the balance sheet valuation as LIFO Valuation not active & FIFO Valuation active.
    2. In T-code MRLH, FIFO Maintained at company code or plant level.
    3. In T-code OMWL, set mean receipt price at valuation ares level if Plant or at company code level if at company code level.
    4. Configure FIFO Valuation ares for teh respective year.
    5. In T-code OMWP, Configure FIFO Method.
    6. In T-code OMW4, Movemnet type settings for FIFO maintained. Generally, no chnages made.
    7. Select material for FIFO in Tcode MRF4.
    8. Execute FIFO Valuation- Tcode MRF1.
    1. When do we need to execute T Code MRF1? Do we need to run the same on period closing or daily basis & by whom- MM or FI ?
    2. What will happen in the case of Stock Transfer? Will it transfer the Material with Price of FIRST Stocks received?
    3. Can we activate the LIFO/ FIFO in Material Master (in Accounting View) for all the Materials during Material creation only?
    4. Is it mandatory to activate Batch Management to achieve FIFO Valuation?
    Regards,
    Aditi

    hi Adi,
    please find my answers in bold letter
    1. When do we need to execute T Code MRF1? Do we need to run the same on period closing or daily basis & by whom- MM or FI ?
    A- This TCode is used to set the LIFO/FIFO indicator in accounting-2 view in material master
    2. What will happen in the case of Stock Transfer? Will it transfer the Material with Price of FIRST Stocks received?
    3. Can we activate the LIFO/ FIFO in Material Master (in Accounting View) for all the Materials during Material creation only?
    A- You can update later as well by MRF1
    4. Is it mandatory to activate Batch Management to achieve FIFO Valuation?
    A-No, I don't think so
    regards,
    Vineet

  • FIFO Valuation within MM (without WM)

    Hello SAP-Experts,
    I want to ask you how to customize the system with t.c. spro and how to setup material master
    to establish the FIFO valuation for some specific materials (e.g. for one or more material type(s)) without any WM functionalities.
    What I read in this forums were the following, but I miss a thin red line or rather a guide, and I miss complete information on this:
    1. Batch Management has to be enabled in customizing and material master.
    => customizing: logistics general - batch management - ???
    => material master: set indicator for batch management to active (is that all?)
    ... and how to make sure that when using MIGO for goods movement, the batches will be found automatically without inputing anything manually?
    2. Classification has to be enabled for those material types which do need the FIFO. A class must be assigned which includes characteristics (e.g. shelf life expiration date, sth. else?)
    3. Condition records have to be maintained (why, which?)
    4. Sorting rules have to be defined for FIFO (where, how?)
    5. Then there are also LIFO/FIFO settings within SPRO-MM-Valuationetc.-Balance Sheet Valuation Procecdure-Configure LIFO/FIFO Methods.
    Has this also to be used? Why, why not?
    6. For what is then the indicator in material master, Accounting view 2: "LIFO/FIFO relevant" - only for cost balance sheet?
    What I need is something like a guide showing the steps which have to be done.
    Then an example booking for FIFO in the system should be done as follows:
    01.01.2000: GR of material A: 2 pieces a 10 EUR = 20 EUR in sum
    05.01.2000: GR of material A: 2 pieces a 15 EUR = 30 EUR in sum
    10.01.2000: GI of material A: 3 pieces (2x10 + 1x15) = 35 EUR in sum, 15 EUR still on stock
    Thank you in advance for your help!
    Gernot

    Dear,
    I am also concentrating on this and 2,3 days back posted a question regarding FIFO valution without any answers.
    Basing on the study, what I understood is FIFO VALUATION and FIFO picking is two different configurations to be done.
    FIFO valuation is only relevant for Balance sheet valuation of material.
    FIFO picking used for inventory management.
    For FIFO balance sheet valaution :
    1. Activate balance sheet valuation (Trans: OMWE) - as LIFO not relevant, FIFO active.
    2. Defined LIFO/FIFO valuation levels (Trans: OMWL) - set as Plant (valuationa rea).
    3. Configured FIFO Valuation areas for year 2008.
    4. Define LIFO/FIFO method (Trans: OMWP) - as CUR - current.
    5. No changes made to movements relevant to FIFO (Trans: OMW4) no changes
    6. Selection of Material to FIFO (Trans: MRF4), in this getting error
    Selected material, entered plant and selected SET indicator executing. The system giving message as 'VALUATION AREA NOT DEFINED FOR FIFO' (M8885). Here i stopped and working on it. Looking like something related FI/CO configuration required.
    For FIFO inventory picking:
    You need to have a bacthmanagement activate
    Step - 1 Create Characteristics
    ZLASTGRDATE - Date of last goods receipt
    Transaction code CT04
    Step - 2 Create Characteristics
    ZBATCH - Batch Number
    Transaction code CT04
    Step - 3 Create a class MRO_BATCH_FIFO_CLS
    Transaction code CL02
    Step - 4 Add Characteristics ZLASTGRDATE
    and
    ZBATCH
    Step - 5 Create a Condition Record Batch search Strategy
    Step - 6 Select Plant and Material Key combination
    - Enter the Material code
    -Select selection Criteria save and come back
    - Select Sort rule as Ascending and Enter the validity rule
    Step - 7 Assign this class to the material in Classification view
    Step 8
    Create the PO for the Material and post the Goods Receipts MIGO.
    System will assign a batch number and also updates the Batch number and
    GR Date. Post thre four GRs with different dates. first with
    the current date , then some with the old dates. Sytem will captures the
    batch
    number and the Gr date. This is only to study how the system
    proposes the GR dates
    Step - 9 Post a Goods Issue for the material, and when you enter batchnumber
    enter * and press enter. then you will observe how system propses the
    quantities based on the batches and GR dates in FIFO order
    This I didnt try, coz our first preference is FIFO Valuation in Balance sheet.
    If you have any information regarding this point, please share with me for better results.
    Regards,
    Syed Hussain.

  • FIFO valuation at period end + consideration of valuation type

    Hi,
    I use FIFO valuation to valuate my raw materials at period end.
    Some raw materials are split valuated, e.g. the same material number can have valuation type NEW or REP (repaired). All material movements (e.g. goods receipt) happen for each valuation type at different cost (REP is much cheaper than NEW). Also purchase orders are created at movement type level.
    Unfortunately FIFO valuation does not work based on valuation type. Thus the FIFO value can be a wrong mixture of valuation type values for each material.
    Example: Starting with zero quantity/value at period begin
    Posting date
    Movement type
    Valuation type
    Quantity
    PO-Value/MAP
    05.07.2014
    101
    NEW
    500
    500 EUR
    10.07.2014
    101
    REP
    1000
    100 EUR
    15.07.2014
    261
    REP
    -500
    -50 EUR
    Total at period end
    1000
    550 EUR
    The stock value of this 1000 items is 550 EUR, the 500 items NEW have a value of 500 EUR, the 500 items REP have a value of 50 EUR.
    FIFO result:
    The 1000 items at month end are FIFO valuated based on the last goods receipt happend on 10.07.2014 which is exactly 1000 items (not considering the different valuation types).
    Thus the FIFO value is only 100 EUR although the correct value should be 550 EUR.
    I didn’t find a solution in SAP standard (FIFO related table MYMP does not contain BWTAR (valuation type) whereas table MYMFT does but its always empty in my case), but is there a solution for that case, maybe I missed it in some EhP’s?
    Best regards, Christian

    Hi,
    There is no such normal MRP run.
    Whenever we take MRP run, system will consider only the main material and not the split valuation type.
    THe main concept of using split valuation is only for that itself. It is there for planning irrespective of valuation type.
    But if you want the system to behaive in such fashion that it should plan one part and not he other then use different material code instead of split valuation. Define these two material codes as alternative and give the usage probability as 0% and 100%. MRP will consider only that material which is having 100% usage probability.
    Regards
    Amit Parkhi

  • Stock valuation at store level

    Hi Experts
    I've added the charactaristic 0STOR_LOC to cube 0RT_C36 to have stock cost by store, however, it's not working as expected, totals for any other characteristic (plant, material, month, day .. ) and ratios quantity and stock value are working fine but when I drill down to plant->store the quantities are ok but the stock value is not.
    the question is, it's possible to have stock valuation at store level?, i understand that the valuation in R/3 is at plant level not store, but in infosource 2is_03_bf we have 0STORE_LOC, so it makes sense to have a finner grain isn't it?
    I compare data from bw with transactions MC.5, with transaction RWBE its not possible have stock value at store level. 
    thanks for any help

    Thank you for your quick reply
    I've checked the link, which is just what I was looking for ...
    by the way, do you know where the these how to papers have gone?, I used to get them in
    http://service.sap.com/bi -> service & implementation -> HOW TO ... Guides -> BW 3.x (or something like that)
    now there is a list under
    http://service.sap.com/bi -> service & implementation -> HOW TO ... Guides -> Guide List Sap BW 3.5 - part of NW 04
    a list like this appears:
    Cross-Component Technical Scenarios
    Portal, KM and Collaboration
    Web Application Server
    Business Intelligence
    Master Data Management
    Exchange Infrastructure
    which is almost empty, so where the howto papers are gone?
    thanks again

  • FIFO Valuation: Two questions

    Hi there,
    I like to configure FIFO valuation and I have a couple of questions:
    Is there anything I have to take care regarding price control ? i.e. can I use FIFO valuation for materials valuated at standard and moving average price ?
    Is it possible to update the actual material price (moving or average) after FIFO valuation ? The Online Help specify that the FIFO price can be copied in either the tax price or commercial price fields but there is no mention of the actual price.
    Thanks in advance for your help and regards
    Thomas

    > * Is there anything I have to take care regarding
    > price control ? i.e. can I use FIFO valuation for
    > materials valuated at standard and moving average
    > price ?
    both is possible and makes sense.
    > * Is it possible to update the actual material price
    > (moving or average) after FIFO valuation ? The Online
    > Help specify that the FIFO price can be copied in
    > either the tax price or commercial price fields buto have an actual revaluation of the
    > there is no mention of the actual price.
    your observation about the docu is found in
    <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/3f/ce913879c8cf29e10000009b38f889/frameset.htm">http://help.sap.com/saphelp_erp2005/helpdata/en/3f/ce913879c8cf29e10000009b38f889/frameset.htm</a>
    which does not reflect the actual capabilities. If you have a look into the selection screen of transaction MRY2 you will notice that you can also updae the standard price or moving average price, when checking also 'database update'.
    best regards,
                         Udo

  • Valuation at plant level and company code level

    Hi,
    Can someone explain me the difference between the valuation at plant level and company code level with a real world example?
    Regards,
    Malsha Kalubowila

    Hi,
    Inventory can be valuated at two levels either at company code level or at plant level. If you select valuation at company code level, all materials across all the plants will have same material price since valuation is at only company code level.
    Say for example Company code 1000 is buying a material which unit price is Rs. 10 from a vendor who supplies to two different plant A & B of company code 1000.  Assume Plant A is situated near vendor premises itself (so freight cost is Re 1 extra)  whereas plant B is situated at far away from vendor place (so freight cost rs 2 extra) and both cases freight cost is borne by the company and not by vendor.
    Assuming you have selected valuation at plant level, now in plant A same material will be valauted at Rs. 11 (10 +1) whereas at plant B it is valuated at Rs. 12 (10+2).
    Whereas if you have selected valuation at company code level, price will not be valuated at plant level rather at company code level which will get updated at moving average price in this case.
    So it is always best practice to select valuation at plant level rather than at company code level.
    Reg
    Karthikeyan G

  • Sub Contracting in FIFO Valuation Method

    Dear All,
    I am facing one serious problem while using Subcontracting Addon.
    We have developed Sub Contracting Add-on based on Standard Valuation Method and it is working fine.
    But when we use FIFO Valuation method then it will not allow.
    So could you please guide me the process/procedure how to implement Sub Contracting in FIFO Valuation Method.
    Means what are changes needs to make it success in FIFO.
    Thanks
    Vikas

    Hi
    Yes its right not to change the earlier valued items on one costing method to another.
    Imp. to note that, for manufacturing/sub-contracting the best costing method is Standard. Because, in manufacturing processes, its very much impossible to track the exact in and out of material as per FIFO; costing method comes into picture as you made some inward and outward or some movement of material, i.e. in case of purchasing material FIFO starts acting as you start consuming the materials or you transfer the material from one warehouse to another, other than in which you have received the material. When you have material on floor, its quite impossible to track the exact movement of material, means which material is actually being processed on the floor. So, If we use FIFO for such items, then actual costing will be always different from executed/system costing, Also, FIFO is suggested for only those business practices who are following the JIT principle. But, by having Special as costing method for manufacturing items, we avoid such problems to have actual costing, though it may again differ from actual costing, but overall as per the business experience we come to know COGS to actual basis.
    In Special Costing method, it's recommendable to revise the Standard cost of the items, periodically.

  • Different Valuations for material under a Plant

    Dear experts,
    I have created the a plant & assigned different storage locations under the plant. Is it possible to have MAP (Valuation) at storage location level?
    Is it possible to have split valuation at a plant level or is it at the Company code level?
    If it is possible can you send the configuration to my ID vskrishna#gmail.com
    Useful answers shall be duly rewarded.
    Useful answers duly rewarded

    Hi,
    It is not possible to have split valuation activated at storage location level. But yes, it is possible to activate it at plant level.
    In Material Master Table, at the time of creation of master data, there is a field in Accounting-1 view. The field name is "Valuation Category".
    OMWC & OMW0 are t-codes for configuring & activating split valuation.
    Specify the valuation category (u can create user defined category also as per your requirement) when creating material at plant level and goto organizational level tab. Select valuation type created through above t-codes to split valuation of material.
    Also please note and ensure that if you want to have split valuation of a particular material then it has to have price indicator "V" at header level. And only at split level you can have indicator "S". Bocs if you put indicator "S" at header level you can not have split valuation activated.
    please revert in case of any doubt.

  • Split valuation in material master

    Hi all,
    I am using val category B. After I create the parent material with val cat B,  I am extending it to val type (inhouse prod and externaL proc). But in MM01 >> ORG LEVELS >> VALUATION TYPE, when I do F4, I am getting message 'NO VALUES FOUND' even after I have created it.
    Please let me know what would be the possible error ?
    Regards,
    Yogesh

    Hi
    For splitting the valuation of  material ypu have to maintain first the valuation category H  and price control V in Accounting 1 and then split valuated it with the price control S for SFG and FG
    These are SPRO setting for Split valuation
    1.SPRO> MM>VALN AND ACC ASSIGNMENT> SPLIT VALUATION> Activate Split Valuation
    2.SPRO> MM>VALN AND ACC ASSIGNMENT> SPLIT VALUATION> Configure Split Valuation
    check and revert
    Regards
    Anupam Sharma

  • FIFO Valuation w/o ML

    Hi
    Want to take the opinion of experts on this...
    1. If I want to have my stock valued on FIFO basis on Month end - Can it be done w/o ML?? ( As far as my understanding goes, it is possible)
    If any one can throw a brief light on the process, it would be great... Does FIFO valuation run at month end, posts to FI books?? If yes, Whats the Accounting entry and which keys in OBYC I need to maintain
    2. I would need ML only if I want values of the stock as well as consumption based on FIFO on real time basis.... Is this assumption correct??
    3. In the 1 above, I think it can give only stock balances based on FIFO.... But not consumption values.... Am I right??
    4. If at all I want to derive Consumption values based on FIFO w/o ML - I have a work around in mind.. Just wanted to take opinon on the same
    a. Activate Purchase Based Accounting - it would post to P&L also along with Stock a/c.
    b. Do FIFO run and it would post to the stock accounts.
    c. If we calculate (by way of ABAP report): Op Stock based on FIFO + Purchase account mentioned in 4.a - Cl Stock Value based on FIFO run - This should also give us the Consumption based on FIFO....
    br, Ajay M

    Hi Ajay,
    just focussing on your point 1.
    "1. If I want to have my stock valued on FIFO basis on Month end - Can it be done w/o ML?? ( As far as my understanding goes, it is possible)
    If any one can throw a brief light on the process, it would be great... Does FIFO valuation run at month end, posts to FI books?? If yes, Whats the Accounting entry and which keys in OBYC I need to maintain?"
    YES, FIFO valuation can be done at period end w/o ML.
    The process can look like that:
    Customizing: Materials Management /  Valuation and account assignment / Balance sheet valuation procedures / configure LIFO / FIFO Methods.
    Go through the steps in "general information", most of them are self-explaining, the interesting thing is the "define LIFO/FIFO relevant movement types", which might be different from client to client (maybe they have own defined movement types,...).
    Also "define LIFO/FIFO methods" is interesting because of the difference of calculating FIFO values based on "single receipts" or not. The difference is well explained in the SAP docu, generally I found the SAP docu for FIFO helpful when I first set up this process on a client system.
    Overall, FIFO customizing is not a big thing...
    The process itself is like:
    Executing MRF4 (or schedule it as a periodically batch job which updates new material masters where the indicator is not set so far).
    Using MRF3 to create the document extract (which contains all the necessary info to valuate your stock quantity).
    At the end MRF1 to calculate the FIFO value. Here the push button "Tolerances" is interesting which allows client specific settings under which circumstances a FIFO value is calculated or replaced by an alternative value.
    The result itself is NOT posted to accounting, but you can store the information in a price field in accounting 2 view in material master (example: tax price 2). And with this information you can use MRN0 to post the FIFO value if you want to. Here don't define a market price source, use tax price 2 as the only comparison price and if FIFO value is lower then the "actual" price in material master, you can create a price change posting based on the FIFO information.
    Guess that answers the OBYC entries also.
    Best regards, Christian

  • Initial Inventory Load - 561 mvmt type, FIFO Valuation

    Hello,
    We have a requirement wherein the client wants to have the Initial Inventory Load (Mvmt 561) to be valuated as FIFO.
    My understanding is, Initial Inventory Load will always be valuated at Std. Price / Moving Avg. Price.
    Can we have Initial Inventory Load valuated using FIFO, if so can you please explain in detail.
    Note: Not every Material being loaded is Batch Managed and am not sure if Batch Mgmt is a requirement for FIFO valuation.
    Thanks for your help.
    Regards,
    Bharat.

    FIFO is a year end valuation,
    you can load initial inventory with 561 and use the external value field to enter whatever value you want, SAP then updates the MAP in material master accordingly.

  • About FIFO valuation

    Hi Gurus,
    How to use FIFO valuation for the material with out using Batch Management. Please explain me step by step procedure.

    You cannot use FIFO valuation in normal course in SAP. FIFO valuation is available only in Balance Sheet valuation.
    During normal day-to-day operations, inventory valuation is based on standard price or moving average price. FIFO and LIFO are not followed.
    Lakshman

Maybe you are looking for