Introduction: Understanding the EINE-NETPR & PRDAT Discrepancy
in SAP
SAP users often encounter inconsistencies when comparing
values of fields NETPR (Net Price) and PRDAT (Price Date) in the EINE table
via transaction SE16 against those shown in ME13. This mismatch can cause
confusion and disrupt procurement and pricing workflows. If you’re struggling
with inaccurate values in these fields, the culprit is likely the lack
of updates to the EINE table. Let’s dive into why this happens and how
to resolve it using the RM06INP0 report.
Why NETPR and PRDAT in EINE Table Show Incorrect Values
The main reason for this discrepancy is that SAP does not
automatically update the EINE-NETPR and EINE-PRDAT fields. Instead, ME13
reads condition records directly from the pricing tables, such as A017
and KONP, which contain up-to-date data.
Technical Insight
-
SE16 (Table Browser) displays raw table content from EINE.
-
ME13 (Info Record Display) retrieves data via pricing logic
using condition records.
This mismatch occurs because EINE's values become outdated
unless explicitly refreshed using a specific program.
Solution: Use RM06INP0 to Refresh EINE Table Data
What is RM06INP0?
RM06INP0 is a report designed to update the EINE-NETPR and
PRDAT fields by recalculating them from the current condition records.
SAP Note 685117 confirms this behavior and recommends this report for accurate
info record pricing data.
How It Works
-
It pulls data from condition tables.
-
It updates EINE with accurate Net Price and Price Date values.
-
Fields are updated only at the moment the report is run and
may become outdated again afterward.
Key RM06INP0 Execution Options Explained
1. Price Determination Without Purchase Order
-
Unchecked: Uses net price from the last PO (EINE-EBELN/EBELP)
if no valid condition record exists.
-
Checked: Ignores PO prices and strictly uses condition records.
This avoids fallback scenarios.
2. No Date Check
-
Unchecked: Skips any info record where PRDAT is in the future
(e.g., 31.12.9999).
-
Checked: Overrides date validation, processing all records
regardless of PRDAT.
Note: If the record isn't processed due to future PRDAT and
"No Date Check" is unchecked, the report may show: "No selection possible".
SAP Notes to Reference
-
SAP Note 685117: Clarifies how and why EINE-NETPR and EINE-PRDAT
are not updated automatically.
-
SAP Note 430543: Explains how the “Price determination
without PO” flag affects updates to pricing fields.
Programs Related to RM06INP0
| Program Name |
Description |
| RM06INP0 |
Updates Net Price and Price Date in Info Records |
| RM06ENP0 |
Net prices for Contracts (works with EKPO) |
| RM06ENP1 |
Net prices for Scheduling Agreements (also updates EKPO) |
All these programs feature a "No Date Check" option with
the same behavior logic.
Frequently Asked Questions (FAQs)
1. Why does ME13 show different prices than SE16 for the
same Info Record?
Because ME13 reads from condition records, which are always
current, while SE16 reads from the EINE table, which must be manually updated.
2. How do I update EINE-NETPR and PRDAT fields?
Run the RM06INP0 report. It refreshes these fields based
on active condition records.
3. What happens if I don’t run RM06INP0?
Your pricing data in EINE remains outdated, possibly leading
to errors in reporting or custom developments.
4. What does the "Price Determination without PO" checkbox
do in RM06INP0?
It controls whether fallback to the last PO pricing is allowed
when no condition records are available.
5. Can I bypass date restrictions during EINE update?
Yes, by enabling the "No Date Check" option in RM06INP0.
6. Are there other programs for contracts and scheduling
agreements?
Yes, use RM06ENP0 for contracts and RM06ENP1 for scheduling
agreements.
Conclusion: Keep EINE Table Data Accurate with RM06INP0
If you're working with SAP and rely on SE16 or custom reports
that use the EINE table, it's crucial to run RM06INP0 regularly to maintain
accurate data. This practice helps you ensure consistency across SAP transactions
and reports, avoiding incorrect price or date issues. |
SAP MM Tips
|