...
Fields
rebateType – Rebate type associated with this RR, it is the same as the one used for the line item.
rebateRecordSet – Name of the RebateRecordSet into which this RR belongs. By default, it belongs to "Default" RebateRecordSet, but you can change it when you create the RR. That can be useful if you create different "kinds" of RRs which will be used to calculate different results at different times.
rebateRecordGroupUniqueName – Name of the RebateRecordGroup into which this RR belongs. By default, it belongs to either none or automatically created RebateRecordGroup (depends on setting in HeaderRebateType.recordWorkflowFormulaTarget), but you can change it when you create the RR. That can be useful if you want to split the RRs into groups, in which the RRs can be approved all together instead of one by one.
inputs – Inputs specific to the RR. When the user reviews the individual RR, they might need to enter certain values/setting specific for that particular values. The rebate logic (for RR) can specify those input fields.
agreementInputs – Input fields copied automatically from the line item. As the RR basically calculates the same values which were calculated during the preparation of the agreement on the line item, the RR needs access to the values entered by the user on the line item.
attribute1..100 – Fields for storage of values. The values are calculated and stored here by the Rebate Record Group Logic.
attributeExtension – Additional attributes fields, which can be used in similar was as attribute1..100 fields. See Attribute Extension fields.
status – Rebate Record Status. Represents the current lifecycle status of the Rebate Record.
agreementStatus – The status of the Rebate Agreement that the Rebate Record was created from. When an agreement revision is created, the 'Agreement Status' field on the Rebate Records for that agreement (not the status of the agreement) is set to either
superseded or invalidated. All valid values are listed in the Rebate Agreement status article.calculationBase – Filter for Datamart used for the Rebate Allocation process and also to display associated transactions on the RR detail screen. Accruals and rebate estimations are typically based on data from Datamart. To specify which transactions should get a portion of the calculated rebate money amount, you need to specify the CalculationBase filter. The Datamart name is specified later, during configuration of the Allocation Process.