Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8533

Re: Net price variation

$
0
0

Check SAPNote  685117 - Net Price in Info Record or Contract is wrong .

 

This normally happens for SA/Contract with time dependent conditions and also in info records due to time dependent conditions. (or validity).

 

 

This is example from the SAP note witgh example of contract, but the Principle is same for Info records and SA.

 

Example of a contract with a material with time dependant conditions:
             Price all 2003: 100 EUR

             Price all 2004: 110 EUR


If you look at the contract in 2003, using ME33, the price will most likely be 100 EUR.
If you, without any other action look at it again in 2004, nothing has  changed and the price is of course still shown as 100 EUR.
This is because ME33 shows EKPO-NETPR. It does NOT look at the  conditions and eventual scales and validity periods.  By design!
Same principle goes for the info record in ME13; EINE-NETPR.

 

When you maintain a contract using ME31K or ME32K the conditions are  maintained simultaneously in the condition tables and in EKPO-NETPR.
Same principle goes for the info record in ME11 / ME12; EINE-NETPR.

 

When you distribute a contract via ALE using BLAORD and COND_A the  contract item and the conditions are sent separately and they are NOT linked together in the receiving system.

 

If you adjust Time dependant conditions in a contract or a Scheduling  Agreement automaticly via an Index (MEK32) the conditions are updated, but the equivalent price fields in the documents are not.

Solution

 

Reports are available that will update NETPR in EKPO / EINE to contain prices valid at the time the report is run:

  • RM06ENP0 for contracts.
  • RM06ENP1 for Scheduling Agreements
  • RM06INP0 for Info Records

Viewing all articles
Browse latest Browse all 8533

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>