# JD Edwards Advanced Pricing: Adjustment Types, Schedules and Definitions Explained > Source: https://netray.co/erp-help/jd-edwards-advanced-pricing-setup > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer JD Edwards Advanced Pricing computes a sales price by walking a price adjustment schedule: an ordered list of adjustment names, each tied to an adjustment type that defines how the price is found (basis, level, preference hierarchy) and a definition that supplies the actual discounts or prices. Customers and items are linked to the schedule through price groups. ## Kind how-to ## System jd-edwards ## Erp Oracle JD Edwards EnterpriseOne ## Module Sales Order Management / Advanced Pricing ## Query jd edwards advanced pricing ## Alternate Queries - jde advanced pricing setup - jde price adjustment schedule - jde price adjustment types and definitions ## Applies To JD Edwards EnterpriseOne 9.x Sales Order Management with Advanced Pricing enabled. Menu names vary slightly by release. ## Steps ### Typical setup order **Items:** - Turn on Advanced Pricing in the Sales Order Management constants and the order type or line type rules where pricing should apply. - Define the preference hierarchies and pricing groups you need, for example customer group and item group, so prices can target categories instead of single records. - Create price adjustment types, which control how the adjustment is calculated and which preference hierarchy it uses. - Create price adjustment definitions that specify the calculation basis, such as a unit price, a percentage off, or a markup, and any quantity or amount breaks. - Create price adjustment names and attach the types and definitions, then build the price adjustment schedule that lists those names in sequence. - Attach the schedule to customers in the customer billing instructions and to items in the item branch or sales category, as your hierarchy requires. - Test on a sales order: review the price adjustments on the order line and the price adjustment ledger to see which adjustments applied and why. ## Sections ### How the pieces fit **Body:** Think of it as layers. A schedule says which adjustments to consider and in what order. Each adjustment name points to a type and a definition. The type decides how to search for a match, and the definition holds the numbers. A match requires that the customer and item on the order belong to the groups named in the adjustment detail. This flexibility is why setup feels heavy compared with simple base pricing. The reward is that one rule can express, for example, ten percent off a product family for a customer group above a quantity break without touching individual records. ### Tables you will see in support and reporting **Body:** Adjustment data lives in the F407x family: F4070 (price adjustment schedule), F4071 (adjustment name or type information), F4072 (adjustment detail) and F4074 (the price adjustment ledger recording what was applied to each sales order line). Exact roles of the other tables in the family differ by release, so confirm in the data dictionary before building reports against them. The ledger is the one most useful for troubleshooting. When a customer asks why a line was priced a certain way, F4074 shows the adjustments that fired and their amounts, which is faster than re-deriving the logic by hand. **Code:** - -- which adjustments were applied to a sales order line (names vary by release) SELECT * FROM PRODDTA.F4074 WHERE ALDOCO = 100234 ORDER BY ALLNID ### Common modelling decisions **Body:** Decide early whether prices are stored as base prices in the Base Price file with adjustments layered on top, or whether most pricing lives in adjustments. Mixing both without a rule makes it hard to explain a price later. Keep a naming convention for adjustment names and schedules and document the hierarchy. Pricing that grew organically over years is the usual reason implementations become hard to change. ## Pitfalls - Attaching the schedule to the customer but not setting the customer or item groups the adjustment detail relies on. - Overlapping adjustments in the same schedule without a clear sequence, giving different prices depending on evaluation order. - Not testing with realistic quantity breaks, so the rule works for one unit and fails for a pallet. - Changing definitions in production without effective dates, instantly repricing open orders. - Building reports on pricing tables without checking the data dictionary, leading to wrong joins between tables in the F407x family. ## Ai Angle Pricing disputes are mostly a lookup problem: which rule won and why. An assistant grounded in your JDE pricing tables and ledger can answer that for a given sales order line, showing the query and the adjustments it found, read-only and under JDE security. Netray can run this on-prem alongside your existing environment. ## Faq ### What is the difference between basic and advanced pricing in JDE? **Answer:** Basic pricing reads a price from the base price file by item and customer or group. Advanced Pricing adds a schedule of ordered adjustments, with types, definitions, hierarchies and breaks, so it can express discounts, markups and rebates by many conditions. ### Where do I see which price adjustment was applied to an order? **Answer:** On the sales order detail, review the price adjustment information for the line. The price adjustment ledger (F4074) stores the applied adjustments per line, which is the reliable source for explaining a price after the fact. ### How do I attach a price schedule to a customer? **Answer:** Through the customer billing instructions, where you assign the price adjustment schedule and pricing groups. Items can be grouped through sales category codes or item branch data, depending on how your preference hierarchy is defined. ### Can I upload many price adjustments at once? **Answer:** Yes. Use the supported batch upload interfaces or Orchestrator flows for the adjustment detail rather than inserting rows with SQL, so validation and key assignment are applied. ## Search terms jd edwards advanced pricing, jde price adjustment schedule, jde price adjustment type, jde advanced pricing setup, jde f4074, jde pricing groups, jde preference hierarchy, jde sales order pricing, jde price adjustment definition, jde customer price group --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json