Page 1230 "SEPA Direct Debit Mandates"
Base Application · Microsoft.Bank.DirectDebit
Across versions
- BC23-25present
- BC26declaration changed
- BC27-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Bank.DirectDebit · captioned “Direct Debit Mandates” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Direct Debit Mandates |
| SourceTable | SEPA Direct Debit Mandate |
| PageType | List |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Group | ID | ID | Specifies the ID of the direct-debit mandate. from the table field |
| Customer No. | Customer No. | Specifies the customer that the direct-debit mandate is activated for. from the table field | |
| Customer Bank Account Code | Customer Bank Account Code | Specifies customer bank account that the direct-debit mandate is activated for. from the table field | |
| Valid From | Valid From | Specifies the date when the direct-debit mandate starts. from the table field | |
| Valid To | Valid To | Specifies the date when the direct-debit mandate ends. from the table field | |
| Date of Signature | Date of Signature | Specifies when the direct-debit mandate was signed by the customer. from the table field | |
| Type of Payment | Type of Payment | 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. from the table field | |
| Expected Number of Debits | Expected Number of Debits | 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. from the table field | |
| Ignore Expected Number of Debits | Ignore Exp. Number of Debits | Specifies that the direct-debit mandate will not be closed automatically when the debit counter reaches the expected number of debits. from the table field | |
| Debit Counter | Debit Counter | Specifies how many direct-debit transactions have been performed using the direct-debit mandate. from the table field | |
| Blocked | Blocked | 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. from the table field | |
| Closed | Closed | Specifies that the direct-debit mandate is closed, for example because the date in the Valid To field has been exceeded. from the table field |
Triggers
OnNewRecord
Relations
- source table Table 1230 “SEPA Direct Debit Mandate”
Pages and codeunits on this table
- Table 1230 “SEPA Direct Debit Mandate” (drill-down page)
- Table 1230 “SEPA Direct Debit Mandate” (lookup page)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "page", object_name: "SEPA Direct Debit Mandates"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.