Enum 141 "Incoming Related Document Type"
Base Application · Microsoft.EServices.EDocument
Across versions
- BC23-30present
Base Application · Microsoft.EServices.EDocument · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | true |
Values
| Ordinal | Name | Caption | Notes |
|---|---|---|---|
| 0 | Journal | Journal | |
| 1 | Sales Invoice | Sales Invoice | |
| 2 | Sales Credit Memo | Sales Credit Memo | |
| 3 | Purchase Invoice | Purchase Invoice | |
| 4 | Purchase Credit Memo | Purchase Credit Memo | |
| 5 | (blank) | ||
| 6 | Service Invoice | Service Invoice | |
| 7 | Service Credit Memo | Service Credit Memo |
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: "Incoming Related Document Type"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.