E1: 45: Check Price and Price History FAQ (Doc ID 980902.1)

Last updated on APRIL 05, 2024

Applies to:

JD Edwards EnterpriseOne Advanced Pricing - Sales - Version 8.11 SP1 and later
Information in this document applies to any platform.

Purpose

This document describes functionality and differences between 'Check Price' and 'Price History'. Currently P42101 and P4210 allow users to access (Row Exit) Check Price and Price History.

This document is a part of the Information Center

Information Center: Overview of JD Edwards EnterpriseOne Advanced Pricing Product -> Information Center: Using JD Edwards EnterpriseOne Advanced Pricing Product -> Doc id 980902.1

Questions and Answers

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Questions and Answers

Question 1: What is the difference between 'Check Price' and 'Price History' row exits in Sales Order Entry (P4210/P42101)?

Question 2: After applying an ESU, we found that 'Check Price' exit is disabled for Transfer Orders. Is this functioning as designed?

Question 3: What are the conditions that disable 'Check Price'?

Question 4: What is the difference between Price History (P4074) and Price and Availability Inquiry (P41261) in Processing Option #7 of Sales Order Entry (P4210), Versions tab?

Question 5: Under what conditions are there no records in the F4074 table for an order?

Question 6: Why is the Adjustment Schedule in the Price History different from the Adjustment Schedule stored in the Sales Order Header?

Question 7: The system is displaying 'Address Book is Invalid' (Error ID: 0037) within the standalone program Check Price & Availability (P4074). When the client enters an Item, Customer Number, and Branch Plant and clicks the 'Find' button, the error occurs. However, if the customer clicks 'Find' again the error disappears. How can the client troubleshoot this issue?

Question 8: What do the different Price Override Code (PROV) values in the Price Adjustment Ledger File (F4074) represent?

Question 9: Customer is getting error ID 0002 (Record Invalid) when trying to add a manual adjustment with a sequence number that is numerically lower than the last sequence number already displayed in the Price History (P4074). Is this working as designed and if so is there a workaround?

Question 10: User is required to enter a valid value for ARSN (Adjustment Reason Code) on any manual adjustment change in Price History P4074. Is it possible to use blank or set ARSN with a default value instead of manually having to select a reason code every time a change is done in P4074?

Question 11: Why is there a Currency Exchange Rate error (ID 0949) in standalone Check Price, but not in Price History accessed from the sales order?

Question 12: Why is there no pricing history when order is created thru EDI Inbound 850 - R47011?

Question 13: In the Price History / Check Price and Availability form (W4074D), what does the “Based on Value” field (BSDVAL) show?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.