Answer 1: 'Check Price' enables users to Check Price and (Item) Availability. This function can be useful for sales staff to simulate price by changing values of 'Sold To', 'Ship To', 'Branch/Plant', 'Price Effective Date', 'Adjustment Schedule', 'Quantity From' and 'Pricing UOM'. The values that appear in the Grid are cached and will be changed accordingly as per the 'Advanced Price Schedule' being populated and upon clicking the Find Button. If the new price is not desired, be sure to 'Cancel' out of the form. Clicking 'Ok' will change the price on the order detail line.
'Price History' will give users the actual price applied for the line(s) entered based on Advanced Price Schedule defined.
Answer 2: Yes this is functioning as designed. This functionality was changed because these orders' price will be the cost of an item. Therefore, since the Check Price row exit will always pull in the price of an item, users will not be allowed to access the Check Price row exit for all transfer, intercompany and interbranch orders.
Listed bugs below disable 'Check Price' for Transfer Orders, Interbranch and Intercompany Orders:
NOTE: Through Bug 10834732: WRONG COST CHECK PRICE - SAR: 7012565, the default Branch/Plant in Check Price and Availability (P4074) is:
Answer 3: Following are the conditions that disable the check price:
Configured Items
Individually Processed Kit Component Lines (see Doc. ID E1: 45: 9.0 Individually Processed Kit Components and Advanced Pricing [ID 1188333.1] for additional information)
Transfer Order
Interbranch Order
Intercompany Order
Last Status (F4211.LTTR) is equal to '914' - Added in Ship. Conf.
Answer 4: Price History (P4074) can be used with Advanced Pricing Adjustments. Price and Availability Inquiry (P41261) is used with Base Pricing to display Trade Discounts and with Standard Pricing to display Standard Pricing Rules. See Doc. E1: 41: Comparison of Base Pricing, Standard Pricing, and Advanced Pricing (P4106/P4271/P4072/P4074/P4210) [ID 625607.1] and E1: 41: Standard Pricing Overview and Setup (P4106/R42950/P4210/P42101/P4271) [ID 625608.1].
Answer 5: When using advanced pricing, there should be at least one record in the F4074 for the base price, whether or not adjustments are applied to the same order line. If the item does not have a base price, one F4074 record is still created for with zero base price.
Note: an F4074 record is not written if Advanced Pricing is turned off (ADVP = N) in the Pricing Constants (P41001).
Note 2: In World, even if Advanced Pricing is turned off via the Pricing Constants P41009W ADVP field, a F4074 record is written for a normal sales order with a base price file F4106 record.
Answer 6: A preference may be active for the item/customer combination on the line. In the Preference Master (P40070) check for Preference Type 14, Price Adjustment Schedule.
Answer 7: Check the following programs:
1) Check the Address Book Revision (P01012) to make sure that a valid record exists for the Branch/Plant.
2) Verify that the B/P Constants (P41001) has the same address book number.
3) Verify that the address book number matches with the address number defined in the Revise Single Business Unit (P0006). Customer needs to verify that the address number in the 'More Detail' tab of the P0006 is not blank but populated with the correct address number.
Answer 8: In Price Adjustment Ledger File (F4074) here are the following values and what they mean:
PROV Flag set to N -> Basket Level Adjustment
PROV Flag set to blank -> For Price Adjustment Lines
PROV Flag set to 1 -> The system retrieve the Base price from F4106 (Base Price table) and Sales Price On Override Flag set to N in Pricing Constants.
PROV Flag set to 2 -> The user Manually Overrides the unit price in Sales Order Detail Revision screen and Sales Price On Override Flag set to Y in Pricing Constants.
Answer 9: An adjustment that is ordained as a manual adjustment can only be added manually to the bottom of the sequence within the price history (P4074) table. If the user tries to add a sequence number other than the last sequence number available the error 0002- Blanks invalid will be thrown and this is working as designed per Bug 12470916 : RECORD INVALID ON MANUAL ADD - SAR: 4381269. The proper way to add an adjustment that is considered a manual adjustment and to place it within the price history table other than the last position is to use the Row exit –insert adjustment. The system will add the sequence number below the row selected and then the user can manually update the manual adjustment as required. This is the only way to add the manual adjustment in a position other than the last position within the table.
Answer 10: ARSN cannot be blank or defaulted from DD when manual adjustment is changed in P4074 and this is working as per design. ARSN is used to trace any manual override against F4074. So, if there is no manual override this column has to be remained as blank and if it got overridden then it should contain a specific value.
Blank code for UDC 40/AR is not valid due because whether reason code is blank or not is checked at the Event Rule level. Default value is not allowed because this will set F4074.ARSN even for the data with no manual override.
Answer 11: When viewing the Price History (P4074) from Sales Order Entry (P4210), price and advanced pricing adjustments are seen without problem. However, when viewing the same data in the stand-alone version of Check Price and Availability (P4074) or via a Row exit from the Sales Order Detail, the system returns the following error: Currency Exchange Rate Not Found - Error ID 0949. The cause is due to someone turning on currency (setting the Currency Conversion Y/N/Z box <Alias CRYR> to a Y or Z in the General Accounting Constants - P0000), then turning it off (changing the setting to N). Check Price functionality performs a currency validation while the Price History does not.
Answer 12: Check Request Date field in F47011/F47012 EDI tables and compare the same with adjustment effective date in P4070 & P4072. Request Date should be within the range of effective date in P4070 & P4072 both.
Answer 13: Where a price adjustment is applied, this field indicates the quantity (or weight, or monetary amount) of the item that was used to calculate the adjustment. It is recorded in the F4074 table. The field is NOT populated for Basis Code 1 or 2 adjustments (% of base or current cost) but it is written for Basis Code 5 adjustments (add on amount). This is for a Line Level adjustment. The field is NOT written to for Basket level adjustments, but it is written for Volume Level adjustments. In the standalone P4074 (Check Price and Availability), if the user changes the value in the “Quantity From” field and performs the “Find” action, the value in BSDVAL is updated accordingly.