Material Ledger production startup • Why the material is not active for Material Ledger being the Plant active? Values and price differences are collected (material movements, purchasing, incoices, production order settlements, debits/credits). • The actual quantity structure is built with goods issues and activities to production, goods receipts from production, material transfers. At period -end closing (transaction CKMLCP): • • The steps in CKMLCP have to be executed in the correct sequence. • A periodic unit price (PUP) is determined and used to update V-Price in Acc1-view in Material Master. Dear SAP Community Member, In order to fully benefit from what the SAP. Activate Valuation Areas for Material Ledger. IS-Retail and Material Ledger. I created a new plant ZZVS which I copied from an already existing plant 1010 in standard SAP. Activate the Material ledger. Activatipon of material ledger. • The price (and exchange rate) differences are distributed to consumption and to ending inventory. • The inventory can be revaluated with the actual price determined. Use the transaction CKMSTART to ensure that you can start extending materials to a plant that has material ledger activated. This has been a problem for me at a recent client as we’re going through pre-implementation data load cycles. The strategy I use to create the material master follows this sequence: basic data, plant data, storage location data, and sales data. The plant data is where I extend the accounting & costing views and also where I hit some errors because the plant did not have the material ledger set as “productive”. So I added logic into my plant data LSMW to catch these situations. Let’s look at CKMSTART. Below you can see the selection screen for the transaction. You are able to “startup” several plants at once, if needed, but can only execute for one exchange rate type. In the example below, I’m going to start material ledger for plant 1400 and exchange rate type M. I do not claim to be a material ledger expert and probably never will be, so I cannot speak to the configuration of or consequences from using material ledger. I can say that in this situation, no master or transactional data existed for that plant (1400) prior to material ledger activation. Thus, some of the activities that CKMSTART executes when plant data does exist are not addressed here. As with many SAP transactions, there is a test mode and I highly recommend that you use it here. Recognizing that no data exists, the background processing option is not necessary. This is the picture of CKMSTART after execution in test mode. All green lights means that things are good to go. Below is the picture of CKMSTART after execution with “Test run” unchecked. Do not be worried that there is a red light at the end of this list. Not being an expert in material ledger, I got a little worried myself. My FICO colleague assured me that this is normal for this situation and is a response to the second to last step shown in the screenshot above (“Company codes in which ML and FI can be reconciled”). The result of this startup is that an entry is made in table CKLMV allowing you to extend materials to the plant. The indicator in the red box below (MLBWI) tells you that material ledger is “live’ in for that valuation area (BWKEY). For this client, the valuation area is equivalent to the plant. You can see another key indicator in the table T001K. Again, by valuation area you have an indicator identified in the red box (MLBWA) that tells you material ledger is activated. This is not the same as being “live”. This is one of the configuration settings when a plant is identified for material ledger. Thus, in my LSMW to extend plant data, I added some logic to prohibit extending materials where this entry does not exist. I checked both of the tables mentioned above and looked for values the fields identified. This check looks something like this: SELECT SINGLE a~bwkey INTO t_bwkey FROM ( t001k AS a INNER JOIN ckmlv AS b ON a~bwkey = b~bwkey ) WHERE a~bwkey = src_data-werks AND a~mlbwa = 'X' AND b~mlbwi = 'X'. If no value is found from this SELECT, then the transaction is skipped in the LSMW. I am using the SAP direct input program RMDATIND to load the material master data. Although this program has a test mode, this test mode does not capture when a valuation area is not “live” with material medger. I should say that the test mode for this program is definitely recommended to identify many other problems that might be present in your data – testing whether material ledger is “live” is, unfortunately, not one of those that it can pinpoint.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2018
Categories |