Stop posting to inventory in NON-traditional way through MI01

[Former Member]

Hi experts;

     I need to stop posting to WE goods receipt and WL goods issue on inventory but NOT through traditional or normal way during Physical Inventory Count by 'Posting Block' on t-code MI01

     I tried tow scenarios as work around:

1. Close the FI posting period OB52: but it is not proper scenario where it will stop posting for all company codes and I need to do that on one by one company code.

2. Block the Inventory Accounts for Posting on G/L master data FS00:but it is not a proper scenario too where it prohibited users from doing Purchase Orders as well Goods Issue or Receipt and the aim is to ONLY prevent GI and GR but to allow users to make PO.

So kindly if someone has any work around scenario to ban Goods Issue and Goods Receipt on inventory while keep allowing making Purchase Orders on the level of each Company Code alone, please advice.

N.B. I tried search for a similar case I didn't find, so if someone knows a similar case on the form kindly advice and send its link.

Thanks in advance;

Best regards;

[Prasoon · Accepted solution]

Hi,

   Could you please share why you cant use the standard SAP functionality to block the goods movement (in your language, "traditional or normal way during Physical Inventory Count by 'Posting Block' on t-code MI01" ) and thought of alternative solution. If there is any special requirement or business requirement, please share the same.

   If there is no special logic, you can go for standard SAP solution, which will block only the goods movement, but allows all other transactional data.

Regards,

AKPT

[Former Member · Accepted solution]

Hi AKPT MM;

     yes, good point of view from u.

the reason is that I do not want to do Physical Inventory in normal way. My aim is to block issue and receipt on inventory until the customer do regular physical inventory (with disregard to SAP) and they have more than company code.

     So, the scenario is to BLOCK Goods issue and receipt until they do physical count on normal XL sheets and later will be uploaded by an ABAP program instead of MI01.

     And, the reason to upload through ABAP program is:

1. They have mass number of materials and each material document upload up to 300 items per time only.

2. which is more important and is the major reason, that they made many mistakes at the time of posting to inventory, so what is existing now on SAP is totally far from the real materials on real land, so this program will upload materials and overwrite any old existing materials. And I cannot keep posting allowed until the time of upload because that shall affect the Project Costs and will accordingly increase the headache of correcting costing accounts.

So after long debate with users, it is found that best case scenario is to BLOCK posting to and from inventory and upload the counted materials through ABAP upload program and override the wrong or corrupted existing materials.

Hope it is pretty clear now and please pardon my poor language and deep experience which may lead to inability to explain the case perfectly.

I do appreciate your kind support and many thanks;

Best regards;

Ahmad Mahmud  

[Former Member · Accepted solution]

Hello Mahmud,

The statement in your reply is beyond my understanding, could you please explain it in more details?

Does it mean that you are going to wipe out the unwanted material masters & stock of it & update the info with new material masters?

Also do note that the process of physical inventory is recommended once in a year. So even if you lock the materials with MI01 then it will be on one occasion. If your client wants to perform this whole practice (within SAP or outside SAP) for multiple times in a year then I doubt business practice laid by your client.

Do you also know the T code MI31 & MI34 within SAP boundary to take care of physical inventory cycle?

Mangesh S

[Prasoon · Accepted solution]

Hi,

   Thanks for explaining the real scenario and the issue you are facing.

   I would suggest you to use authorization method for storage location. Go to the path: OLMB - Authorization Management - Authorization check for storage locations. Here, you can activate the authorization check for all your plant - storage location combination. If you activate the authorization check at storage location level, only the users with authorization for the object M_MSEG_LGO will be able to do the goods movement for the particular storage location.

  So, you may activate the authorization check for all plant and storage location combination and remove authorization for the object M_MSEG_LGO from all user roles / profiles. Eventually, the goods movements are blocked!!!.

  In order to upload the stock, you have to provide the authorization for the mentioned object with all storage locations for the user ID who is going to upload the stock.

  Once stock loading is completed, you may revert back the authorization check at storage locations or provide authorization for the users corresponding to the business requirement.

Check the above option and revert back in case of any concerns.

Regards,

AKPT

[JL23]

I actually think that the whole process is not fully understood. It starts already by mentioning MI01 as inventory transaction. it is unrealistic to assume that this transaction is used to create physical inventory documents of several hundred materials of a whole plant.

As Mangesh already pointed out, this is usually done with MI31.

Entering the count is about 20 to 50 times quicker than counting the items itself and writing the count onto the counting sheet.

Preparing Excel sheets for counting is not needed at all, and an unnecessary extra step.

I wonder how you can assume that the manual data entry causes more errors than an upload from Excel. How does the count go into an Excel other than by human interaction. So where is the difference between entering a number into Excel compared to do same in SAP.

In SAP you have even the option to set a threshold which gives the user a warning message in case the difference between entered quantity and book quantity is outside this threshold. This helps to minimize the entry errors.

You don't have such feature in Excel.

[former_member183424]

You first post was rejected...

As this is a frequently asked and answered question..

Its a standard behavior.

If you tick the option during PI creation (MI01) or MI02..

You will face an error message when you post goods receipt or goods issue.

But you can create PO at all for the material.

[JL23]

Please, freezing has nothing to do with blocking,  that is so different like putting something into the refrigerator  and thinking that this will lock the door at your car.

[ajitkumar]

I dont think blocking GL in C code or chart of accounts  will prevent creating of PO.

[former_member183155]

Hi Mahmud ;

You can set the posting block in a physical inventory document. Blocking can be done at plant level and storage location levels. Did you try these ways ?

To avoid incorrect physical inventory differences - Blocking goods movement and Freezing book inventory can be used.

Look at:

Spro / MM / Inventory Management and Physical Inventory / Physical Inventory / Allow Freezing of Book Inventory Balance in Storage Location

Regards.

M.Ozgur Unal