Table 8631 "Config. Table Processing Rule"

Base Application · System.IO · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Config. Table Processing Rule
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	Package Code	Code[20]	—	TableRelation Table 8623 “Config. Package” (Config. Package)
2	Table ID	Integer	—
3	Rule No.	Integer	—
4	Action	Option	Specifies an action that is related to the custom processing rule. via Page 8640 “Config. Table Processing Rules”	OptionCaption: ,Custom,Post,Invoice,Ship,Receive
5	Custom Processing Codeunit ID	Integer	Specifies the custom processing codeunit. via Page 8640 “Config. Table Processing Rules”	TableRelation AllObjWithCaption.“Object ID” where(“Object Type” = const(Codeunit))

Keys

Key1: Package Code, Table ID, Rule No. (clustered)

Events published

OnDoesTableHaveCustomRuleInRapidStart(TableID: Integer; var Result: Boolean) (integration)
- subscribers: Codeunit 1254 “Match Bank Pmt. Appl.” CheckBankAccRecOnDoesTableHaveCustomRuleInRapidStart, Codeunit 8624 “Setup Company Name” CheckCompanyInformationOnDoesTableHaveCustomRuleInRapidStart

Procedures

FindTableRules(ConfigPackageTable: Record "Config. Package Table"): Boolean
GetFilterInfo(): Text
Process(ConfigRecordForProcessing: Record "Config. Record For Processing"): Boolean
RunActionOnInsertedRecord(RecRef: RecordRef): Boolean
ShowFilters()

Plus 12 local procedures.

Triggers

OnDelete, OnInsert, OnModify

Relations

Package Code: TableRelation Table 8623 “Config. Package”

Pages and codeunits on this table

Page 8640 “Config. Table Processing Rules” (source table)

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Codeunit 13 “Gen. Jnl.-Post Batch” (2 calls: RunActionOnGenJnlBatch → (object), RunActionOnGenJnlLine → (object))
Codeunit 5704 “TransferOrder-Post Shipment” (2 calls: RunActionOnTransferHeader → (object), RunActionOnTransferHeader → SetHideValidationDialog)
Codeunit 5705 “TransferOrder-Post Receipt” (2 calls: RunActionOnTransferHeader → (object), RunActionOnTransferHeader → SetHideValidationDialog)
Codeunit 80 “Sales-Post” (1 call: RunActionOnSalesHeader → (object))
Codeunit 8625 “Setup Item Costing Method” (1 call: RunActionOnItem → (object))
Codeunit 90 “Purch.-Post” (1 call: RunActionOnPurchHeader → (object))

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "Config. Table Processing Rule"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.