Table 5969 "Contract Gain/Loss Entry"

Base Application · Microsoft.Service.Contract · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Contract Gain/Loss Entry
DataClassification	CustomerContent
Permissions	TableData “Contract Gain/Loss Entry” = rimd

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No.	Name	Type	Explanation	Notes
1	Entry No.	Integer	—
2	Contract No. Δ BC28	Code[20]	Specifies the contract number linked to this contract gain/loss entry.	TableRelation Table 5965 “Service Contract Header” (“Service Contract Header”.“Contract No.” where(“Contract Type” = const(Contract)))
3	Contract Group Code Δ BC28	Code[10]	Specifies the contract group code linked to this contract gain/loss entry.	TableRelation Table 5966 “Contract Group” (Contract Group)
4	Change Date Δ BC28	Date	Specifies the date when the change on the service contract occurred.
5	Reason Code Δ BC28	Code[10]	Specifies the reason code, a supplementary source code that enables you to trace the entry.	TableRelation Table 231 “Reason Code” (Reason Code)
6	Type of Change Δ BC28	Enum “Service Contract Change Type”	Specifies the type of change on the service contract.	enum Enum 5970 “Service Contract Change Type”
8	Responsibility Center Δ BC28	Code[10]	Specifies the code of the responsibility center, such as a distribution hub, that is associated with the involved user, company, customer, or vendor.	TableRelation Table 5714 “Responsibility Center” (Responsibility Center)
9	Customer No. Δ BC28	Code[20]	Specifies the customer number that is linked to this contract gain/loss entry.	TableRelation Table 18 “Customer”
10	Ship-to Code Δ BC28	Code[10]	Specifies a code for an alternate shipment address if you want to ship to another address than the one that has been entered automatically. This field is also used in case of drop shipment.	TableRelation Table 222 “Ship-to Address” (“Ship-to Address”.Code where(“Customer No.” = field(“Customer No.”)))
11	User ID Δ BC28	Code[50]	Specifies the ID of the user who posted the entry, to be used, for example, in the change log.	TableRelation User.“User Name”; DataClassification EndUserIdentifiableInformation
12	Amount Δ BC28	Decimal	Specifies the change in annual amount on the service contract.

Keys

Key1: Entry No. (clustered)
Key2: Contract No., Change Date, Reason Code
Key3: Contract Group Code, Change Date
Key4: Customer No., Ship-to Code, Change Date
Key5: Reason Code, Change Date
Key6: Responsibility Center, Change Date
Key7: Responsibility Center, Type of Change, Reason Code

Procedures

CreateEntry(ChangeType: Enum "Service Contract Change Type"; ContractType: Enum "Service Contract Type"; ContractNo: Code[20]; ChangeAmount: Decimal; ReasonCode: Code[10])

Relations

drill-down page Page 6064 “Contract Gain/Loss Entries”
lookup page Page 6064 “Contract Gain/Loss Entries”
Customer No.: TableRelation Table 18 “Customer”
Ship-to Code: TableRelation Table 222 “Ship-to Address”
Reason Code: TableRelation Table 231 “Reason Code”
Responsibility Center: TableRelation Table 5714 “Responsibility Center”
Contract No.: TableRelation Table 5965 “Service Contract Header”
Contract Group Code: TableRelation Table 5966 “Contract Group”

Referenced by

5 fields in 5 objects relate to this table (TableRelation or CalcFormula).

Table 5965 “Service Contract Header”: Contract Gain/Loss Amount
Table 5966 “Contract Group”: Contract Gain/Loss Amount
Table extension 6450 “Serv. Customer”: Contract Gain/Loss Amount
Table extension 6455 “Serv. Responsibility Center”: Contract Gain/Loss Amount
Table extension 6469 “Serv. Reason Code”: Contract Gain/Loss Amount

Pages and codeunits on this table

Page 6064 “Contract Gain/Loss Entries” (source table)

Ask your agent

Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Contract Gain/Loss Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.