Table 1230 "SEPA Direct Debit Mandate"
Base Application · Microsoft.Bank.DirectDebit
Across versions
- BC23present
- BC24declaration changed
- BC25unchanged
- BC26declaration changed
- BC27unchanged
- BC2812 fields changed
- BC29-30unchanged
Neighbourhood 18 connected objects and pages
Base Application · Microsoft.Bank.DirectDebit · captioned “Direct Debit Mandate” · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 1230 “SEPA Direct Debit Mandates” (1 Learn page).
Properties
| Property | Value |
|---|---|
| Caption | Direct Debit Mandate |
| DataClassification | CustomerContent |
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 | ID Δ BC28 | Code[35] | Specifies the ID of the direct-debit mandate. | |
| 2 | Customer No. Δ BC28 | Code[20] | Specifies the customer that the direct-debit mandate is activated for. | TableRelation Table 18 “Customer”; NotBlank |
| 3 | Customer Bank Account Code Δ BC28 | Code[20] | Specifies customer bank account that the direct-debit mandate is activated for. | TableRelation Table 287 “Customer Bank Account” (“Customer Bank Account”.Code where(“Customer No.” = field(“Customer No.”))); NotBlank |
| 4 | Valid From Δ BC28 | Date | Specifies the date when the direct-debit mandate starts. | |
| 5 | Valid To Δ BC28 | Date | Specifies the date when the direct-debit mandate ends. | |
| 6 | Date of Signature Δ BC28 | Date | Specifies when the direct-debit mandate was signed by the customer. | NotBlank |
| 7 | Type of Payment Δ BC28 | Option | Specifies if the direct-debit transaction is the first or the last according to the expected number of direct-debit transactions that you entered in the Expected Number of Debits field. | OptionCaption: OneOff,Recurrent |
| 8 | Blocked Δ BC28 | Boolean | Specifies that the related record is blocked from being posted in transactions, for example a customer that is declared insolvent or an item that is placed in quarantine. | |
| 9 | Expected Number of Debits Δ BC28 | Integer | Specifies how many direct-debit transactions you expect to perform using the direct-debit mandate. This field is used to calculate when to enter First or Last in the Sequence Type field in the Direct Debit Collect. Entries window. | |
| 10 | Debit Counter Δ BC28 | Integer | Specifies how many direct-debit transactions have been performed using the direct-debit mandate. | not editable |
| 11 | No. Series | Code[20] | — | TableRelation Table 308 “No. Series” (No. Series) |
| 12 | Closed Δ BC28 | Boolean | Specifies that the direct-debit mandate is closed, for example because the date in the Valid To field has been exceeded. | not editable |
| 13 | Ignore Exp. Number of Debits Δ BC28 | Boolean | Specifies that the direct-debit mandate will not be closed automatically when the debit counter reaches the expected number of debits. |
Keys
- Key1: ID (clustered)
- Key2: Customer No.
Events published
OnBeforeInsert(var IsHandled: boolean; var SEPADirectDebitMandate: Record "SEPA Direct Debit Mandate")(integration): Integration event triggered before inserting a new mandate record.OnBeforeModify(var IsHandled: boolean; var SEPADirectDebitMandate: Record "SEPA Direct Debit Mandate")(integration): Integration event triggered before modifying a mandate record.
Procedures
IsMandateActive(TransactionDate: Date): Boolean: Checks if the mandate is active and valid for the specified transaction date.GetDefaultMandate(CustomerNo: Code[20]; DueDate: Date): Code[35]: Finds the default active mandate for a customer on a specific due date. Prioritizes customer’s preferred bank account if specified.UpdateCounter(): Increments the debit counter when the mandate is used and updates the closed status.GetSequenceType(): Integer: Determines the SEPA sequence type based on mandate type and usage history.RollBackSequenceType(): Decrements the debit counter when a collection is rejected or rolled back.
Plus 6 local procedures.
Triggers
OnInsert, OnModify
Relations
- drill-down page Page 1230 “SEPA Direct Debit Mandates”
- lookup page Page 1230 “SEPA Direct Debit Mandates”
- Customer No.: TableRelation Table 18 “Customer”
- Customer Bank Account Code: TableRelation Table 287 “Customer Bank Account”
- No. Series: TableRelation Table 308 “No. Series”
Referenced by
13 fields in 12 objects relate to this table (TableRelation or CalcFormula).
- Table 1208 “Direct Debit Collection Entry”: Mandate Type of Payment, Mandate ID
- Table 112 “Sales Invoice Header”: Direct Debit Mandate ID
- Table 172 “Standard Customer Sales Code”: Direct Debit Mandate ID
- Table 181 “Posted Gen. Journal Line”: Direct Debit Mandate ID
- Table 21 “Cust. Ledger Entry”: Direct Debit Mandate ID
- Table 36 “Sales Header”: Direct Debit Mandate ID
- Table 5900 “Service Header”: Direct Debit Mandate ID
- Table 5965 “Service Contract Header”: Direct Debit Mandate ID
- Table 5970 “Filed Service Contract Header”: Direct Debit Mandate ID
- Table 5992 “Service Invoice Header”: Direct Debit Mandate ID
- Table 6010 “Service Header Archive”: Direct Debit Mandate ID
- Table 81 “Gen. Journal Line”: Direct Debit Mandate ID
Pages and codeunits on this table
- Page 1230 “SEPA Direct Debit Mandates” (source table)
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Page 456 “No. Series” (1 call:
InsertNoSeries → (object))
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "SEPA Direct Debit Mandate"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.