Deal Head

Unique deal number, generated from a sequence.

Type of the supplier or partner the deal applies to. Valid values are: S for supplier, SS for supplier site, S1 for supplier hierarchy level 1 (e.g. manufacturer), S2 for supplier hierarchy level 2 (e.g. distributor) and S3 for supplier hierarchy level 3 (e.g. wholesaler). Descriptions of these codes will be held on the codes table under a code_type of SUHL.

Level of supplier hierarchy (e.g. manufacturer, distributor or wholesaler), set up as a partner in the PARTNER table, used for assigning rebates by a level other than supplier. Rebates at this level will include all eligible supplier/item/country records assigned to this supplier hierarchy level.

Contains the unique number representing a supplier or supplier site. It holds a value when partner_type is S (Supplier) or SS (Supplier Site).

Type of the deal. Valid values are A for annual deal, P for promotional deal, O for PO-specific deal or M for vendor-funded markdown. Deal types will be held on the codes table under a code type of DLHT.

Code for the status of the deal. Valid values are W for worksheet, S for submitted, A for approved, R for rejected and C for closed. Deal statuses will be held on the codes table under a code type of DLHS.

Currency code of the deals currency. All costs on the deal will be held in this currency.

Date the deal will become active. This date will determine when deal components begin to be factored into item costs. For a PO-specific deal, the active_date will be the orders written date.

Date the deal will/did end. This date determines when deal components are no longer factored into item costs. It is optional for annual deals, required for promotional deals. It will be left NULL for PO- specific deals.

Oracle user ID of the user that closed the deal. This will only be populated if the deal has been manually closed using the menu option in the deal header form.

Date/time stamp of when the record was created. This value should only be populated on insert - it should never be updated. This field is required by the database.

Oracle user ID of the user that entered the deal into the system.

Date the deal was approved. Oracle Retail target column APPROVAL_DATE on DEAL_HEAD.

Oracle user ID of the user that approved the deal.

Date the deal was rejected. Oracle Retail target column REJECT_DATE on DEAL_HEAD.

Oracle user ID of the user that rejected the deal.

Any given external reference number associated with the deal.

Order the deal applies to, if the deal is PO-specific.

Indicates if approved orders should be recalculated based on this deal once the deal is approved. Valid values are Y for yes or N for no.

Free-form comments entered with the deal.

Holds the Oracle user-id of the user who most recently updated this record. This date/time can be used for auditing purposes. This field is required by the database.

Holds the date time stamp of the most recent update by the last_update_id. This date/time can be used for auditing purposes. This field is required by the database.

Billing type of the deal component. Valid values are OI for off-invoice and BB for bill-back Billing types will be held on the codes table under a code type of DLBT.

Code that identifies the bill-back period for the deal component. This field will only be populated for billing types of BB and BBR. Valid billing periods will be held on the codes table under a new code type of DLBP. Valid values are W for week, M for month, Q for Quarter, A for Annual and D for Deal End.

Indicates when the deal component should be applied - at PO approval or time of receiving or when the invoice is matched or time of shipping to the deal location. Valid values are O for PO approval, R for receiving, G for Gross Receipt, I for Invoice Matched and S for Shipment. These values will be held on the codes tables under a code_type of AALC. It will be NULL for an M-type deal (vendor funded markdown).

Identifies whether thresholds will be set up as qty values, currency amount values or percentages (growth rebates only). Valid values are Q for qty, A for currency amount or P for percentage. Deal limit types will be held on the codes table under a code type of DLLT. It can only be NULL for an M-type deal (vendor funded markdown).

Unit of measure of the threshold limits, if the limit type is quantity. Only UOMs with a UOM class of VOL (volume), MASS or QTY (quantity) can be used in this field.

Indicates if the deal component is a rebate. Deal components can only be rebates for bill-back billing types. Valid values are Y for yes or N for no.

Indicates if the rebate should be calculated using linear or scalar calculation methods. Valid values are L for linear or S for scalar. This field will be required if the rebate indicator is Y. Rebate calculation types will be held on the codes table under a code type of DLCT.

Indicates if the rebate is a growth rebate, meaning it is calculated and applied based on an increase in purchases or sales over a specified period of time. Valid values are Y for yes or N for no. This field will be required if the rebate indicator is Y.

The first date of the historical period against which growth will be measured in this growth rebate. Note performance and the rebate amount are not calculated - this field is for informational/reporting purposes only.

The last date of the historical period against which growth will be measured in this growth rebate. Note performance and the rebate amount are not calculated - this field is for informational/reporting purposes only.

Indicates if the rebate should be applied to purchases, sales or issues. Valid values are P for purchases or S for sales or I for Issues. It will be required if the rebate indicator is Y. Rebate purchase/sales indicators will be held on the codes table under a code type of DLRP.

This will determine periods shown in the deal income screen and the frequency of the deal income accrual reporting. Valid values are W for week, M for month or Q for Quarter - these will be held on the codes table under a new code type of DLRL.

This will determine the bill back method. It will be required for bill back deals only. Valid values are Credit note or Debit note - these will be held on the codes table under a new code type of DLBM.

This will determine how the income will be calculated. Valid values are Actuals earned to date or Pro- rated using forecast - these will be held on the codes table under a new code type of DLIC

This will determine if the credit notes or debit notes created should be created manually or require manual intervention and also if negative amounts should be included. Valid values are AA for Automatic All values, MA for Manual All Values, AP Automatic Positive values only, MA Manual Positive values only, NO - no invoice processing - these will be held on the codes table under a new code type of DLIP.

Indicates if the deal income accrual will also be written to the RMS stock ledger. Valid values are Y for yes or N for no.

Indicates if VAT will be included in the billing information. Valid values are Y for yes or N for no.

Type of the partner the deal applies to. Valid values are S1 for supplier hierarchy level 1 (e.g. manufacturer), S2 for supplier hierarchy level 2 (e.g. distributor) and S3 for supplier hierarchy level 3 (e.g. wholesaler).

Level of supplier hierarchy (e.g. manufacturer, distributor or wholesaler), set up as a partner in the PARTNER table, used for assigning rebates by a level other than supplier. Rebates at this level will include all eligible supplier/item/country records assigned to this supplier hierarchy level.

Unique identifying number for a supplier within the system. This indicates the supplier that will included on the invoice information.

The budget growth rate percentage for the deal to date.

The budget total turnover for the deal to date.

The total monies earned for the deal to date.

Indicator to determine deal security. If this indicator is checked, then only people with the same or greater access as the user that created the deal will be able to view and edit the deal (similar to fixed deal security for non-merchandise fixed deals see the deals01 functional spec for more details). If the indicator is not checked, a user with one element in common with the deal will be able to view and edit the entire deal.

This is the estimated next invoice date for the deal.

This is the last time an invoice was raised for the deal.

Used to indicate whether the packs are to be tracked at pack level or not.

This column specifies the number of extra reporting days to add to the DEAL_ACTUALS_FORECAST table for late transaction postings after the deal close date, applied only to the last reporting period if BBD_ADD_PERIOD_SCOPE is 'L'.

This field indicates if Manufacturer Suggested Retail (instead of selling unit retail) is to be used while calculating deal income in case of Sales-based deals. Valid values are Y or N.

Holds the tax region for which the corresponding tax rates would need to be considered while processing the income for the related deals. It will only hold a value for Bill Back and Bill Back Rebate deals and when INCLUDE_VAT_IND is Y.

This field defines whether franchise purchases need to be considered as part of the deal income calculation in case the related invoicing location has been added as part of the deal definition. Valid values are Y and N. It can only be Y for Purchase-based deals (i.e. rebate_purch_sales_ind is P.) and for deal application timings as Gross receipt and Receipt (i.e. deal_appl_timing as G and R).

This field defines whether franchise sales need to be considered as part of the deal income calculation in case the related invoicing location has been added as part of the deal definition. Valid values are Y and N. It can only be Y for Sales-based deals (i.e. rebate_purch_sales_ind is S).

This field controls whether deal income will be posted in aggregate or should impact the Weighted Average Cost (WAC) of the item locations on the deal. For off-invoice and allowance deals, this indicator will have 'Y'. For vendor-funded promotion, vendor-funded markdown, clearance consignment rate and promotional consignment deals, this flag is always 'N'. For Billback/Billback Rebate deals, this flag is defaulted to 'N' and can be updated to 'Y' before the deal is approved.

This field indicates if a deal is eligible for retroactive deal processing. For deals created post-upgrade, this flag is always N for Vendor Funded Promotion (VFP), Vendor Funded Markdown (VFM), Clearance Consignment Rate (CCR) or Promotional Consignment Rate (PCR) deals since they are NOT eligible for retroactive deal processing. Other deals created post-upgrade will default to 'Y'. This field will be NULL for all existing deals prior to the upgrade. A NULL value is treated as N.

Indicates the type of date on the purchase order used determine deal eligibility. The column will only have a value for off-invoice deals. Default value is NBD (Not Before Date). Valid values and description are held in the codes table under a code_type of DQCD

Code that determines whether to apply BBD_ADD_REP_DAYS to the last reporting period. Valid values are 'L' (apply to last period) or 'A' (apply to all periods). These values are maintained in the codes table under code type 'BAPS'.

This indicates if Supplier Unit Cost should be used for deal income calculation. It is applicable to Purchase and Issue based Bill-Back (BB)/Bill-Back Rebate (BBR) deals and for Vendor Funded Promotions (VFP). If this option is chosen while creating a BB/BBR, the deal income calculation logic will use the cost defined and stored at item-supplier-country-location or item-supplier-country level without removing Off-Invoice (OI) deals. Similarly, if the option is chosen while creating a Vendor Funded Promotion (VFP), the income calculation will use the same supplier unit cost when vendor contribution type is Percent. Valid values are Y/N.