Variant 1: Scrapping the product due to expired shelf life of the batch In the blog, I will explain how EWM can help to execute the scrapping and write-off process in both these process variants, I have taken total batch quantity scrapping as an example in order to run system steps for both the variants: If the product is found damaged and it carries no resale value, it is also usually written-off from the Inventory books by posting it’s value against cost center. If the batch is expired, typically in Food, Pharmaceutical & Health industry, the product is neither good for the production usage nor suitable for the human consumption and hence one can not sell such expired products to earn the salvage money out of the scrapped material thus it is typically written-off from the Inventory books by posting it’s value against cost center. Due to expiration of the product/batch itself 2. Scrapping could be typically required due to two main reasons: 1.
Executing the Goods Issue to Scrapping cost center. Moving the stock from storage bins to the scrapping zone or quarantine area 2. Scrapping process inherently will consist of two parts: 1. This will have financial implications as the stock which is written-off has dollar value.
Scrapping process is an Internal warehouse process in which stock of the material is written-off from Inventory books (if not sold). This is very useful from the FI point of view.In this blog, I will share with you my experience of executing different scrapping process variants in Decentral-EWM system on S/4 HANA 1909. Thus the desired results of hitting various G/L accounts based on the mvt type for the same material issued from warehouse can be obtained. Similarly we can define various account modifiers for different movement types and give the corresponding G/L accounts in OBYC settings.
Now any postings done with mvt 261 and valuation class will hit the desired G/L account, in this case 400010.Ī posting to cost center with mvt201 will hit another G/L account, in this case 400000. Now in OBYC settings (SPRO-> Materials Management ->Valuation and Account Assignment-> Account Determination -> Account Determination Without Wizard -> Configure Automatic Postings), give the corresponding G/L accounts as per the requirement of finance module. For the required movement type and the transaction event key having the updating as per our needs change the Account modifier to a custom one, say ZBR. Go to Transaction OMWN (SPRO->Materials Management->Valuation and Account Assignment-> Account Determination->Account Determination Without Wizard -> Define Account Grouping for Movement Types), change view "Account Grouping": Overview. But SAP has an option of using the same standard movement type but assign the cost to different G/L accounts. The most common practice is defining a new movement type.
#Sap movement type 701 and transaction key how to
Ever wonder how to assign a cost incurred for the material having the same material master to different G/L accounts issued from warehouse based on the movement type? This is very useful from the FI point of view.
0 kommentar(er)
