Enum 6107 "E-Doc. Process Draft"
EDocument · Microsoft.eServices.EDocument.Processing.Import
Across versions
- BC23-28not present
- BC29-30present
EDocument · Microsoft.eServices.EDocument.Processing.Import · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | true |
Values
| Ordinal | Name | Caption | Notes |
|---|---|---|---|
| 0 | Purchase Document | Purchase Document | obsolete Pending 29.0 |
| 1 | Purchase Invoice | Purchase Invoice | |
| 2 | Purchase Credit Memo | Purchase Credit Memo | |
| 3 | Sales Order | Sales Order |
Deprecations
- value Purchase Document: Pending 29.0 (#if not CLEAN29), “Use “Purchase Invoice” or “Purchase Credit Memo” instead.”
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: "enum", object_name: "E-Doc. Process Draft"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.