Table 1228 "Payment Jnl. Export Error Text"

Base Application · Microsoft.Bank.Payment · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 1228 “Payment Journal Errors Part” (2 Learn pages), Page 1229 “Payment File Error Details” (1).

Properties

Property	Value
Caption	Payment Jnl. Export Error Text
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	Journal Template Name	Code[10]	—	TableRelation Table 80 “Gen. Journal Template” (Gen. Journal Template)
2	Journal Batch Name	Code[10]	—	TableRelation Table 232 “Gen. Journal Batch” (“Gen. Journal Batch”.Name where(“Journal Template Name” = field(“Journal Template Name”)))
3	Journal Line No.	Integer	—
4	Line No.	Integer	—
5	Error Text Δ BC28	Text[250]	Specifies the error that is shown in the Payment Journal window in case payment lines cannot be exported.
6	Document No.	Code[20]	—
7	Additional Information Δ BC28	Text[250]	Specifies more information that may help you resolve the error.
8	Support URL Δ BC28	Text[250]	Specifies a web page containing information that may help you resolve the error.

Keys

Key1: Journal Template Name, Journal Batch Name, Document No., Journal Line No., Line No. (clustered)

Events published

OnAfterSetLineFilters(var PaymentJnlExportErrorText: Record "Payment Jnl. Export Error Text"; GenJnlLine: Record "Gen. Journal Line") + BC27 (integration)

Procedures

CreateNew(GenJnlLine: Record "Gen. Journal Line"; NewText: Text; NewAddnlInfo: Text; NewExtSupportInfo: Text): Creates a new payment export error record for a general journal line. This procedure adds error information to help track and resolve payment export issues.
JnlLineHasErrors(GenJnlLine: Record "Gen. Journal Line"): Boolean: Checks whether a specific general journal line has payment export errors.
JnlBatchHasErrors(GenJnlLine: Record "Gen. Journal Line"): Boolean: Checks whether a journal batch has payment export errors.
DeleteJnlLineErrors(GenJnlLine: Record "Gen. Journal Line"): Deletes all payment export errors associated with a specific general journal line.
DeleteJnlBatchErrors(GenJnlLine: Record "Gen. Journal Line"): Deletes all payment export errors associated with a journal batch.
DeleteJnlLineErrorsWhenRecDeleted(GenJnlLine: Record "Gen. Journal Line"): Deletes payment export errors for a journal line when the record is being deleted. This procedure is used during cleanup operations to maintain data integrity.
JnlLineHasErrorsWhenRecDeleted(GenJnlLine: Record "Gen. Journal Line"): Boolean: Checks whether a general journal line has payment export errors when the record is being deleted. This procedure is used to verify error existence during cleanup operations.

Plus 3 local procedures.

Relations

Journal Batch Name: TableRelation Table 232 “Gen. Journal Batch”
Journal Template Name: TableRelation Table 80 “Gen. Journal Template”

Referenced by

1 fields in 1 objects relate to this table (TableRelation or CalcFormula).

Table 81 “Gen. Journal Line”: Has Payment Export Error

Pages and codeunits on this table

Page 1228 “Payment Journal Errors Part” (source table)
Page 1229 “Payment File Error Details” (source table)

Countries that replace it

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: "Payment Jnl. Export Error Text"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.