Posting block in Inventory

Hi,
I set in MI02 (Change Physical inventory) "Posting block", but goods receipt are allowed ?
I don't unserstand why it happens.
Best regards

Hi,
Please check and test as below:
1. if freeze book inv.  is ticked
-book quantity 800 is detemined and frozen when the PI document created
-after GI 10 KG, the MARD quantity is now 790.
-when doing count, the book quantity is still 800 not 790, because of
freeze book inv., the count quantity is 784, so difference 16 is
going to post.
-how 702 is posted for difference 16 KG? credit from MARD for 16 KG,
so 790-16=774KG left in MARD.
2. if freeze book inv.  is not ticked
-book quantity is not determined when PI document is created.
-after GI 10 KG, the MARD quantity is now 790
-when doing count, the book quantity is now determined from MARD, so
book quantity=790, the count quantity is 784, so difference 6 is
goint to post.
-how 702 is posted for difference 6 KG? credit from MARD for 6 KG,
so 790-6=784 KG left in MARD.
Thanks and regards,
Polly

Similar Messages

  • Future Posting Block for Inventory document

    Hi Friends,
    My client want to create a PID (Physical Inventory doc) to day with planned count date next week and posting block checked.
    But, they does not want to block it to post till the begining of planned count date. Practically, they want the posting block to be effective on Planned count date.
    Can it be??
    Appreciate your help in advance.
    Regards,
    Dev.

    Hi,
    Please read SAP online help:
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/4d/2b8d3943ad11d189410000e829fbbd/frameset.htm
    Here you can see that transaction MI32 can be used to set posting block in mass.
    When count date comes:
    - user can set the block via MI32 in mass
    - in advance you can schedule ba background job for MI32 in order to set the posting block
    I wouldn't go to development...if it is not necessary...
    (my opinion)
    Regards,
    Csaba
    Edited by: Csaba Szommer on Feb 26, 2010 10:43 PM

  • Posting block - Physical inventory

    Hello,
    Is it possible to do a posting block at storage location level for physical inventory without creating a phy.inv.document? If so, could you guide me?
    Thanks
    UV

    Hello UV,
    There are three options for blocking the posting in Sloc.
    1. Create inventory document and block the posting in that sloc, once you are done then you can delete that inventory document or complete with count and clear it so you can again use the SLoc.
    2. Delete the SLoc for temporary. so it will not allow to post any transaction in that SLoc. When you are ready at that time create SLoc with the same (previous) name.
    3. Use authorization profile and restrict any transaction for that storage location.
    Hope this helps.
    Regards
    Arif Mansuri

  • Posting block in Inventory Mgmt

    Hi guys,
    what is this posting block which comes
    up in material movement recompilation
    run, elaboration is of need.
    Thanks,
    Due points will be assigned

    Hello ViJaY,
    I read Roberto's reply and made some sense,
    I.e. While filling the setup tables there are chances of getting duplicate records into it as the other LO applications update the data while running the setup.
    To avoid this, we use the Posting block concept, here u will give the From and To dates so only the records related will be filled in the setup tables. Till this job completes no other postings will be allowed.
    Also, Inventory links with many applications like MM / SD / PP, etc. Inorder to avoid the updation from other applications we follow the concept 'Posting block'.
    Roberto, Am I correct ? could u give us more info ?!
    Best Regards....
    Sankar Kumar
    +91 98403 47141

  • Why can not freeze book inventory Storage location and Posting block?

    Hello,
    I tried to freeze book inventory storage location and posting block at storage location level in SAP.
    1) OMBP -> "Freeze book inventory storage' is checked at that storage location.
    2) MI01 -> the 'Posting Block' and 'Freeze book inventory' in the Physical Inventory Document  is checked.
    3) Post the Physical Inventory Document by using MI02.
    But, I am still able to post inventory movement at that storage location after executing the above.
    (I run MB1C with movement type 501 at that location.
    I input the material number which are in the created Physical Inventory document.
    The posted manterial document is created after I run MB1C.
       The document date and the posting date in MB1C are the same date of Physical Inventoery Document.
    I can see this material inventory movement from MB51!! )
    My question is:  Why SAP is allowed to execute the inventory movement after the 'freeze book inventory storage location' and 'Posting block' are checked at OMBP and MI01 ?
    Any idea?
    Help me, thank you.
    Regards,
    Sylvia Chen

    Problem solved.  Thank you for all help!!

  • Posting block Question in How to handle inventory management scenarios

    Hi all - I have a question in document
    <b>"How to...Handle Inventory Management Scenarios in BW"</b>
    can anyone please tell me what a posting block is in this document...
    also I did not understood what a Validity table is?
    thanks,
    Sabrina.

    Hi Sabrina!
    A 'posting block' period is something that now you are facing in inventory management, but you have to consider it in ALL logistic cockpit flows (what you can see in LBWE).
    This requirement can be easily explained in this way: as you know, to fill a setup table you have to activate the extract structure of the datasource for which you want to run the setup job (otherwise the system says that no active extract structure exists, do you remember ?); but, by doing so with the posting operations open (in other words, users can create new document or change the existing ones), you run the risk that these records are automatically included in the extraction queue (or in SM13 if you are using unserialized method) AND also collected in setup table ! And you will have the same records with the initial load (from setup table) and then the same from delta load (from the queue): a nice data duplication.
    To avoid this situation, a "posting block" (or a "free-posting period" or a "downtime") is requested. No one can post new document during your setup job...
    Hope now is clearer...
    Bye,
    Roberto

  • Default check on the 'Posting block' check box in the Physical Inventory

    I am looking for a default check on the 'Posting block' check box in the Physical Inventory document for T-code MI01 or MI31. Can anyone help in this?

    Thanks for your reply. Can you send me the detail process how to do it through Transaction Variant.
    Regards,
    Tt

  • Posting block Vs Freezing Book Inventory

    Hi all.,
    During PI count, there is an option to Block the Material. In this scenario, there can be no movement of material either GI or GR, right?
    In freeze book inventory as well, "we can freeze the book inventory balance in the
    physical inventory document. This is to prevent the book inventory balance, which is relevant for physical inventory, from being changed by any movements". So the terms of Movement should mean either GR or GI, right?
    Now, how similar or different are these two conditions during PI?
    Appreciate all the help
    Thanks

    Hi Mahesh,
    <b>With regard to posting block</b>...you have understood correctly. The indicator is set for the affected stocks in each case (storage location stock, batch stock, or special stock) for all associated stock types and is not cancelled until the count results are posted. The indicator remains in the physical document header even if the stock is unblocked through the posting of inventory differences. It then only indicates that a posting block was set for the documents. The blocking indicator can be set in one of two ways:
    (a) Directly upon entry of the physical inventory document (if the count is to take place immediately)
    (b) Shortly before the count (if the count is to take place later)
    <b>With regard to Freeze the book inventory</b>, at the time of PI, when you enable this indicator, system take snap shot of Quantity and Value in internal tables. That means, you can't hold or stop your business operation during this process. This indicator has the effect that the current book inventory balance is recorded in the physical inventory document. The system compares the counted stock with the frozen book inventory balance to determine any inventory differences.
    Bye,
    Muralidhara

  • Posting block & Freeze book inventory

    What is the difference between the posting block and Freeze book inventory.
    Both does the same thing rite? by not allowing the user to post the stock till the physical check is completed.
    Note : Subject is frequently asked question,please search forum/various sap resources
    before posting.
    Edited by: Jeyakanthan A on Nov 29, 2011 12:27 AM

    Hi,
    Both are different.
    Posting Block allows you to set a block indicator so that system wont allow to make any stock postings during the Physical inventory period.
    Where as Freeze inventory will Freeze the book inventory i.e. it makes a note of the total inventory of a material and freezes it. so that you can still make stock postings even after creating physical inventory documents.
    For ex:
    Suppose you have set Freeze book inventory for a SL and you are creating a physical inventory document today and currently your total stock in un-res use for a material is 100 in that particular SL.
    After sometime you are entering a GR of say 100 qtys.
    Now as per the physical count - total stock available physically was 90 only then in this case when you do a physical inventory posting - system will do a adjustment of 10 Quantities only and not 110 Quantities.
    i,e. it will consider the freeze stock qty 100 rather than the total stock 200 Qty after the latest GRN.
    Hope its clear.
    Thanks & Regards,

  • Inventory management: posting block :  material master field

    Hi,
    In het material master you have a field  Physical Inventory Blocking Indicator, but when I create a counting document (MI01) with posting block. The field in the material master is still blank. How can this happen?
    Best regards,
    Eric.

    Hi Eric,
    I guess there is some inconsistency in your system,
    Please refer to the SAP Note 355939 & 192571 and you might be able to fix the bug..
    Note 355939
    Summary
    Symptom
    This note is only of importance for you if you execute physical inventory functions using the R/3 System. The inconsistencies can usually be adequately eliminated using Note 192571. This note is only intended for customers who did not discover the inconsistency in the first period of the new fiscal year and who now have problems with the physical inventory indicators.
    Additional key words
    RMMMPERI, MMPV, physical inventory, PIINKON, MARD-KZILL, MARD-SPERR
    Cause and prerequisites
    See Note 192571.
    Solution
    To eliminate the inconsistencies, carry out the following steps in the corresponding sequence:
    1. Implement the corrections from Note 192571
    2. Also implement the attached correction instructions
    3. Start program ZREPPI_FLAGS (from Note 192571)
    4. Start program ZINVUT30 (from Note 67072)
    Source code corrections
    Note 192571
    Summary
    Symptom
    Preliminary note:
    This note only applies to you if you execute physical inventory functions in the R/3 System.
    In the log of the period closing program running during the fiscal year change, the number of the records closed does not correspond to the actual number of records in the corresponding stock table on the database.
    As a result, the physical inventory indicators were not moved from the current fiscal year to the previous year in the records that are not closed. This means that materials, for which a physical inventory was carried out in the previous year, are dealt with by the system as if a physical inventory has already been carried out in the current year.
    This problem can affect materials created before the upgrade to Release 4.5.
    Additional key words
    RMMMPERI, MMPV, inventory, PIINKON, MARD-KZILL, MARD-SPERR
    Cause and prerequisites
    The problem is caused by a program error.
    Solution
    If you have not yet carried out the fiscal year change (for example, if you have a fiscal year variant with non-calendar fiscal year), the attached correction can correct the error.
    If you do not yet use Release 4.5B with at least Hot Package 09, in the four following form routines you must implement the deletion/insertion sequence listed in the attachment only once. Do not implement them twice each time as described in the "Corrections" section.
    - Form MARD_UPDATE_JW_DB2DB4
    - Form MCHB_UPDATE_JW_DB2DB4
    - Form MSKA_UPDATE_JW_DB2DB4
    - Form MSKU_UPDATE_JW_DB2DB4
    Caution: Implement the corrections WITHOUT comment lines or added comments !!!
    Comments between EXEC SQL and ENDEXEC can lead to the 'DBIF_DSQL2_SQL_ERROR' at the fiscal year change.
    If you carried out the fiscal year change in Release 4.5 or 4.6A and use R/3 Physical Inventory Management, you can, after implementing the attached correction in your system, repair the affected records as follows:
    Run correction report ZREPPI_FLAGS.
    After the execution of report ZREPPI_FLAGS, you should implement report ZINVUT30 mentioned in Note 67072 in your system and execute the report for those materials for which a physical inventory has already been executed in the current fiscal year.
    If you recognize the inconsistency only in a later period, also refer to Note 355939.
    Trust this helps
    Regards
    Merwyn

  • Physical Inventory Posting Block

    Hi ,
    I have Created Physical Inventory Document (MI01) with Posting Block , But i will try to do REM back flash T code MFBF, it will for all the transaction good receipt and goods issue all the transaction , kindly tell me how to control this
    Regards,
    Ranganath

    do I understand that correct your MFBF reduces the inventory that is blocked for physical inventory?
    Can it be that you already entered the count? because the count entry in MI04 removes the posting block. Often people think the posting block is removed with posting the difference, but as said, this happens already with entering the count.

  • PI - Posting Block or Freeze Book Inventory

    While generating the PI document, there are check boxes for 1)posting block & 2)freeze book inventory. I would like to know under what circumstances would we have both check boxes checked. Some business example will help my understanding of usage. Thanks in advance.

    Hi ,
    1)This freezing indicator basicaly functions like this manner, If the count results are not entered immediately after the stock has been counted, it is useful to set this indicator so that any goods movements which may take place in the meantime will not change the book inventory balance relevant to the physical inventory.
    2) blocking indicator , it will not allow any postings for this material during physical inventory count.
    regards,
    sudhakar

  • Minimize posting block time

    Hi Gurus,
    we are using inventory management in BW 3.5 , the data is loaded from SAP R/3 . for every maintenance operation in data sources (2LIS_03_Bf, ...) or upgrade, we have to do initialization in the R/3 side that means blocking all stock movements during the initialization (~ 8 Hours!) this situation is very inconvenient for the users.
    have you any solution to minimize the posting block time?
    thank you.

    hi,
    Thank you Dhanya, so if i get it right it's possible to have zero down time during setup and initialization with this method :
    1. delete data in infoprividers in BW
    2. Delete setup tables and delta queues in R/3.
    2. Run init from BW with no data transfer (supposition: this will setup delta queues).
    3. Run setup tables filling in R/3 (supposition: all documents posted while this operation is going on will be stored in delta queues)
    4. Run full repair load in BW
    5. Run delta load in BW.
    is this right?
    how about compression with and without marker update mentioned here? [https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328]
    we are using first scenario : Inventory management with non-cumulative key figures.
    Thank you.

  • Posting block check in MI31 transaction

    Hi,
    I have done following steps -
    1. Create inv document using MI31 with posting block check box selected. Step OK.
    2. Doing 311 using MB1B - System prevents me from doing this movement. Step OK
    3. Doing MI04 Step OK
    4. Again doing 311 using MB1B - System prevents me from doing this movement, but with only one material.
    If I am trying with other material, after MI04, I am able to do movement type 311 move using MB1B.
    What is that it prevent me from doing 311 activity will that material after MI04?
    Any input is appreciated,
    Regards,
    Dipak

    not fully correct. the posting block is erased whenever you enter a count, it does not matter if your count matches with the book quantity or not.
    The purpose of the posting block is to prevent entering movements in SAP while a phyiscal inventory is active. This is only one side of the medal. The other side is your organisation of a physical inventory. Here you have to take the same measures, you need to prevent people from moving materials until you have finished your count.
    Once you enter the count, then SAP is just certain that the count has finished and the block is no longer needed.
    If you counted correctly, then you will not move more than you counted, hence you will not have any issue if you post the difference some days later.

  • Posting Block in applications

    Hi guys,
    how to create posting blocks other than lockin users out and selection restrictions in inventory, sd, and other applications.
    Blocking Orders say in oli7bw doesnt really post new
    documents right, whats the relevancy of it.
    Your help is greatly appreciated.
    Thanks.

    if your delta is initialized and a doc is changed then yes you will capture the change
    the point is that you could end with double extraction: once with your init and once because y doc has been changed...
    so the procedure should be:
    1. init your delta
    2. right after start your SETUP with blocking documents
    <at this stage, user will only be able to create NEW documents which you will capture with your delta>
    3. at the end of the SETUP the docs will be released and any change will be captured as well
    This ensure procedure enable you to fill the init table and avoid duplicate information extracted to BW.
    hope this clears your doubts
    Olivier.
    Message was edited by:
            Olivier Cora

Maybe you are looking for