Table extension 6101 "E-Doc. Gen. Journal Line"
EDocument · Microsoft.eServices.EDocument.RemittanceAdvice
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
EDocument · Microsoft.eServices.EDocument.RemittanceAdvice · BC29-30 · source at ea08af5e · facts from BC29
Extends Gen. Journal Line.
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 |
|---|---|---|---|---|
| 6100 | Remit. Advice E-Doc. Created | Boolean | Specifies that an electronic document (remittance advice) was created for this payment line. | not editable; DataClassification CustomerContent |
Procedures
SetRemitAdviceEDocCreated(): Flags this Gen. Journal Line as having a remittance advice e-document created for it.ClearRemitAdviceEDocCreated(): Clears the remittance advice e-document flag on this Gen. Journal Line.HasRemitAdviceEDoc(): Boolean: Returns whether a remittance advice e-document was created for this Gen. Journal Line.
Triggers
OnDelete
Relations
- extends Table 81 “Gen. Journal Line”
Recent changes
- 2026-08-11 #9578 [E-Documents Core] - Enabling remittance advice export via E-Documents (payment journal + posted payments) (main, BC30, feature, added)
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: "tableextension", object_name: "E-Doc. Gen. Journal Line"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.