Table 1209 "Credit Trans Re-export History"
Base Application · Microsoft.Bank.Payment
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC282 fields changed
- BC29-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Bank.Payment · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 1209 “Credit Trans Re-export History” (1 Learn page).
Properties
| Property | Value |
|---|---|
| Caption | Credit Trans Re-export History |
| 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 | No. | Integer | — | AutoIncrement |
| 2 | Credit Transfer Register No. | Integer | — | TableRelation Table 1205 “Credit Transfer Register” (Credit Transfer Register) |
| 3 | Re-export Date Δ BC28 | DateTime | Specifies the date when the payment file was re-exported. | |
| 4 | Re-exported By Δ BC28 | Code[50] | Specifies the user who re-exported the payment file. | DataClassification EndUserIdentifiableInformation |
Keys
- Key1: No. (clustered)
Triggers
OnInsert
Relations
- Credit Transfer Register No.: TableRelation Table 1205 “Credit Transfer Register”
Pages and codeunits on this table
- Page 1209 “Credit Trans Re-export History” (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: "Credit Trans Re-export History"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.