Table 6109 "EDoc. Purch. Line Field Setup"
EDocument · Microsoft.eServices.EDocument.Processing.Import
Across versionsobsolete pending since 26.0
- BC23-28not present
- BC29-30present
EDocument · Microsoft.eServices.EDocument.Processing.Import · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
| ObsoleteState | Pending |
| ObsoleteTag | 26.0 |
| ObsoleteReason | Replaced by “ED Purchase Line Field Setup” |
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 | Field No. | Integer | — | not editable; DataClassification SystemMetadata |
Keys
- PK: Field No. (clustered)
Deprecations
- object: Pending 26.0 (#if not CLEANSCHEMA29), “Replaced by “ED Purchase Line Field Setup””
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: "table", object_name: "EDoc. Purch. Line Field Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.