My Oracle Support Banner

E1: 45: Repost Sales Rebate History (R42760) (Doc ID 1369072.1)

Last updated on APRIL 18, 2024

Applies to:

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


The Repost Sales Rebate History (R42760) can be run for a customer to accrue rebate information from the Sales History (F42119) file. Typically, this program is used against a customer for whom rebate information has not been accrued but has advanced pricing applied, so that the customer's rebate information can 'catch up' on accruals missed. For example, on 15th June 2011 a rebate is setup for a customer that offers them a 10% rebate if they order $1,000.00 of goods during calendar year 2011. The Repost Sales Rebate History (R42760) program will accumulate past order information from either the Sales order detail (F4211) or from the Sales Order History file (F42119) to calculate the customer's volume totals and Open Rebate Amount, where appropriate.

The Repost Sales Rebate History (R42760) uses the field Price History (SO09) within the Sales order detail (F4211) or Sales Order History file (F42119) to determine if the rebate will be applied to the Rebate Volume History (P4078) and Rebate Transaction Detail (F4079) for the customer.   If the Price History is blank the Repost Sales Rebate History will not perform the 'Catch Up' function.

Note: the R42760 will NOT process lines where the Sales Order Status 18 field (SO18) field is set to value <1>. The field will be set to <1> if the price is manually overridden during the sales order entry process, or if an order is generated via the EDI R47011 functionality (Transaction Set 850) and the detail table F47012 contains a value for the unit price. 
Note 2: the R42760 is hard-coded to only look at orders where the next status is ‘999’.




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
 Setup Requirements
 Example Transactions
 Original Order has no Rebate Adjustment applied but has Price History (F4074) records
 Original Order with Rebate Adjustment, Rebates Adjustment value changed
 Original Order has a Volume Level Adjustment, no rebate on Schedule
 Original Order with Manual Override and 'Apply on Override Price Flag' activated
 Frequently Asked Questions

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