Table 462 "Payment Term Translation"
Base Application · Microsoft.Foundation.PaymentTerms
Across versions
- BC23present
- BC24declaration changed
- BC25-28unchanged
- BC292 fields changed
- BC30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Foundation.PaymentTerms · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Payment Term Translation |
| 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 | Payment Term | Code[10] | — | TableRelation Table 3 “Payment Terms” (Payment Terms) |
| 2 | Language Code Δ BC29 | Code[10] | Specifies the language that is used when translating specified text on documents to foreign business partner, such as an item description on an order confirmation. | TableRelation Table 8 “Language” |
| 3 | Description Δ BC29 | Text[100] | Specifies the translation of the payment term. |
Keys
- Key1: Payment Term, Language Code (clustered)
Relations
- Payment Term: TableRelation Table 3 “Payment Terms”
- Language Code: TableRelation Table 8 “Language”
Pages and codeunits on this table
- Page 756 “Payment Term Translations” (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: "Payment Term Translation"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.