...
Fields
Unique Constraints: A combination of 3 fields - compensationRecordUN, accrualType and name - must be unique.
name – name of the Accrual Record, unique within the scope of the Compensation Record that creates it. Sample of values from project: Q1-1, Q1-2, …
label – description of the meaning of this Accrual Record
startDate – (Date) first date of validity of the values stored in this record
endDate – (Date) last date of validity of the values stored in this record
payoutDate – date, when the money should be paid to the seller
compensationTypeUN – uniqueName of the Compensation Condition Type, coming from the Compensation Condition Type of the Compensation Record, in which content was this Accrual Record generated.
compensationRecordUN – uniqueName of the Compensation Record to which it belongs. Set automatically while creating the Accrual Record.
attribute1..100 – keeps the compensation calculation results - any values needed for the business
status – (String) status of the Accrual Record. Values defined by project needs. Sample of values from projects: "Pending", "Approved", "Denied", "Paid", etc.
accrualType / type – (String) type of the payout. Values are decided by needs of the project, e.g. to distinguish between more types of payouts. Sample values from projects: "Accrual", "Summary", …
intgStatus – a string representing a status of integration of this record data to the external system. The set values will be driven by the integration tool (e.g. Integration Manager) and the needs of the project. Sample of values from projects: PROCESSED, SENT, ERROR OCCURED, Allocated, …
intgStatusDetail – a string representing detail (explanation) of the intgStatus, possibly shown to the end user.
intgStatusErpReference – a string representing an ID of a document in ERP, which relates to this record (or to which this record was written to). The exact usage depends on the project needs.