ML_Not Distributed Line in ML analysis

1. Not distributed Line Item in ML analysis (CKM3)
   

PVTDJ3E75EN5

**'Not distributed' price differences can be due to four reasons:
A) System applied a 'Price limiter' logic (stock coverage check).
You can analyze this case using the value flow monitor transaction:
- for release 4.7 , transaction CKMVFM
- for release 4.6C, program SAPRCKM_VERIFY_PRICE_DET (note 324754 is required).
- for release < 4.6C: Program ZVERIFY_PRICE_DET (included in the note 324754) Or directly checking the field CKMLPP-PBPOPO manually.
In this case the value CKMLPP-PBPOPO is bigger than cumulative inventory.
If you still want these price differences to be distributed, you can switch off price limiter logic. Then all price differences are posted to stock, and the price difference account is cleared. You should decide for each material if you want to switch off price limiter logic or not. So you can achieve a compromise between realistic prices and clearing the balance of the price different account.
Price limiter logic can be switched off in the following way:
* Resetting the price limiter quantity
In release 4.7 this is done using transaction CKMVFM.
In release <= 46C using the program ZREMOVE_PRICE_LIMITER (see note 325406).
* Note 855387: Application of this note will create an additional selection parameter for step 'Single Level Price Determination' to switch on/off price limiter logic.
This option is the better way, as it simplifies the process and provides more flexibility (see the note for more information).



B) System applied a fallback strategy during price determination (see note 579216) to avoid a negative periodic unit price (PUP).
Please check the attached note 579216: If the regularly calculated PUP (based on 'Cumulative Inventory' line) would become negative, the system uses a different strategy to calculate the PUP:
The PUP is calculated with these priorities:
1. 'Cumulative Inventory' line (no fallback)
2. Receipts ('ZU') line (Info message C+ 135 in the log)
3. Beginning inventory ('AB') line (Info message C+ 138 in the log)
4. PUP-price of previous period (Info message C+ 136 in the log)
5. S-price (Info message C+ 137 in the log).
The fallback strategy is active by default for Single-Level price determination.
For multilevel price determination it must be activated with parameter 'Negative price: automatic error management'.
As a solution, you might check the postings of these materials if they really need to have such big negative price differences or if there is some kind of error in the posting or the production structure
If you find such errors, you might reverse the corresponding postings and post them in a correct way.
Or, you might use transaction MR22 (debit/credit material) in order to post an appropriate positive amount of differences to the concerned materials so that the resulting actual price would no longer be negative. This allows performing the period closing regularly. In the next period, you might remove this manual posted value from the materials (again with MR22) in order to correct the overall stock values back to their original amounts.



C) Execution of transaction CKMM.
The above situation may be produced because transaction CKMM was executed during the corresponding period.
When transaction CKMM is processed the system deletes the price differences for the material in the period and these differences are not longer in the period record tables.
See note 384553 for further details.
The fact is that the price differences are still visible in CKM3 (as not distributed). This is due to the missing reset of summarization records (MLCD).
This error is just a problem of CKM3 display, because the differences shown as 'not distributed' do not exist in the periodic records. The PUP of the material is calculated correctly.
The error is solved with note 838989:


D) A subsequent price change (LTPC).
In transaction CKM3 when a subsequent price change (LTPC) is carried out, the preliminary valuation and all differences are rescaled at category level. Additionally, the corresponding lines for price change documents are sorted and flagged with the text "Subsequent price change".
If a late price change is run with transaction MR21 and there were not a previous reversal of the consumptions already posted in the period, these documents cannot be rescaled by transaction MR21.
Therefore transaction CKM3 will show a "Not distributed line" although the PRDs are rescaled correctly. This is then a display side-effect in CKM3.

FI_VAT

1. VAT Configuration
   

 

FI Global Settings
Tax on Sales/Purchases
		Tcode
Basic Settings
Check calculation procedure	Check calculation procedure - condition types	OBQ1
Check calculation procedure	Check calculation procedure - access sequences	OBQ2
Check calculation procedure	Check calculation procedure - procedures	OBQ3
Assign country to calculation procedure		OBBG
Check and change settings for tax processing		OBCN
Fiscal Regional Codes	Define fiscal regional codes for Italy/Spain	OBAD
Fiscal Regional Codes	Define fiscal regional codes for other countries	OBAE
Calculation
Define taxes on sales/purchases codes		FTXP
Specify base amount		OB69
Posting
Define tax accounts		OB40
Define account for exchange rate difference posting		OBYY
Allocate tax codes for non-taxable transactions		OBCL

 

1. 
   
   Configuration steps : Basic Settings, Calculation, and Posting
   1. SAP uses condition types (e.g., MWAS sales tax and MWVS input tax) as the basis of a calculation procedure, which enables integration between the SD, MM, and FI modules.
      
   2. Create an Access Sequence (MWST Tax Indicator) and underneath it an access code (10 (Table 3) Tax Code).
      
   3. Create a calculation procedure for each country or jurisdiction for which you need one (for example, TAXF = sales tax for France and TAXIT = sales tax for Italy). Behind this you put a control procedure, which defines the calculation steps (TAXF).
      
   4. Procedure TAXF Sales Tax – France:
      

Steps	Control	Condition Type	Description	From
100	0	BASB	Base Amount
110	0	MWAS	Sales Tax	100
120	0	MWVS	Input Tax	100
140	0	MWVN	Non Deductible input tax	100
150	0	NLXA	Acquisition tax credit	100
160	0	NLXV	Acquit ion tax debit	150

 

1. Next assign a country to a calculation procedure (AT Austria = TAXAT).
   
2. Check and change settings for tax processing as follows:
   

Process	MWS
Text	Output Tax
Tax Type	1 Output Tax
Not deductible	Not used here
Posting indicator	2 Separate line item

 

1. Define tax codes, which will be used in transactions. (Tcode: FTXP)
   

Country key	FR
Tax code	D1
Procedure	TAXF
Tax Type	V
Behind the VAT code define its properties
Tax code	D1 Deferred input tax - standard rate 19,6%
Tax Type	V Input tax
Check	Select if SAP to check calculation
Target tax code V1	This tax code transfer input tax to code V1 when related invoices area paid
Assign GL a/c to the tax code	Tcode FTXP / OB40. Maintained in table T030K When entering tax codes with no tax rate, entering 0 rate allows accessing them. Also need to assign GL a/c to these tax codes.

 

1. 
   
   Finally, tax codes have to be allocated for non-taxable transactions, outside the scope of VAT (e.g., general ledger journal entries between accounts which require a valid tax code) – e.g.: Input VN and Output AN. The codes are created in the normal way first, but with a zero percentage rate. Use Tcode OBCL to jump directly to where these tax codes are defined.
   
   
   
2. VAT Return configuration
   

When configuring VAT processing it is also necessary to maintain Table TRVOR (with transaction code SM31) and enter the company code and fiscal year against the ABAP which runs the advance tax return (e.g., RFUMSV20 for Italy and Spain prior to Release 4.6C) and against the ABAP which runs the document journal (RFBELJ10). Otherwise the report will not run and the error report does not tell you much except to point you towards Table TRVOR.