tableFinanceofficial - Microsoftderived - from the source, no model text

Table 414 "IC Outbox Transaction"

Base Application · Microsoft.Intercompany.Outbox

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC251 fields changed
  4. BC262 fields changed, 1 fields added
  5. BC271 events added
  6. BC28unchanged
  7. BC291 fields changed
  8. BC30unchanged

Neighbourhood 7 connected objects and pages

Table 413 "IC Partner" (relates to)IC PartnerCodeunit 431 "IC Outbox Export" (pages and codeunits on it)IC Outbox ExportPage 611 "IC Outbox Transactions" (pages and codeunits on it)IC Outbox TransactionsCodeunit 27 "Confirm Management" (calls)Confirm ManagementTable 1313 "Activities Cue" (referenced by)Activities CueManage intercompany transactions (Learn pages)Manage intercompany transact…Manage the Intercompany Inbox and Outbox (Learn pages)Manage the Intercompany Inbo…

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Intercompany.Outbox · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 611 “IC Outbox Transactions” (2 Learn pages).

Properties

Property Value
Caption IC Outbox Transaction
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 Transaction No. Integer Specifies the transaction’s entry number. via Page 611 “IC Outbox Transactions” not editable
2 IC Partner Code Code[20] Specifies the code of the intercompany partner that the transaction is related to if the entry was created from an intercompany transaction. via Page 611 “IC Outbox Transactions” TableRelation Table 413 “IC Partner” (“IC Partner”.Code); not editable
3 Source Type Δ BC26 Δ BC29 Option — obsolete Removed 29.0; #if not CLEANSCHEMA29; OptionCaption: Journal Line,Sales Document,Purchase Document; not editable
4 IC Source Type + BC26 Enum “IC Transaction Source Type” Specifies whether the transaction was created in a journal, a sales document or a purchase document. via Page 611 “IC Outbox Transactions” enum Enum 430 “IC Transaction Source Type”; not editable
5 Document Type Enum “IC Transaction Document Type” Specifies the type of the related document. via Page 611 “IC Outbox Transactions” enum Enum 414 “IC Transaction Document Type”; not editable
6 Document No. Code[20] Specifies the number of the related document. via Page 611 “IC Outbox Transactions” not editable
7 Posting Date Date Specifies the entry’s posting date. via Page 611 “IC Outbox Transactions” not editable
8 Transaction Source Option Specifies which company created the transaction. via Page 611 “IC Outbox Transactions” OptionCaption: Rejected by Current Company,Created by Current Company; not editable
9 Document Date Date Specifies the date when the related document was created. via Page 611 “IC Outbox Transactions” not editable
10 Line Action Option Specifies what happens to the transaction when you complete line actions. If the field contains No Action, the line will remain in the Outbox. If the field contains Send to IC Partner, the transaction will be sent to your intercompany partner’s inbox. via Page 611 “IC Outbox Transactions” OptionCaption: No Action,Send to IC Partner,Return to Inbox,Cancel
12 IC Partner G/L Acc. No. Δ BC25 Δ BC26 Code[20] — obsolete Removed 25.0; #if not CLEANSCHEMA25
13 Source Line No. Integer —
14 IC Account Type Enum “IC Journal Account Type” — enum Enum 84 “IC Journal Account Type”
15 IC Account No. Code[20] —

Keys

  • Key1: Transaction No., IC Partner Code, Transaction Source, Document Type (clustered)
  • Key2: IC Partner Code

Events published

  • OnAfterShowDetails(var IOutboxTransction: Record "IC Outbox Transaction") (integration): Integration event raised after showing transaction details to enable custom processing.
  • OnBeforeLookupDocumentNo(ICOutboxTransaction: Record "IC Outbox Transaction") (integration): Integration event raised before document number lookup to enable custom lookup logic.
  • OnBeforeOutboxCheckSend(var ICOutboxTransaction: Record "IC Outbox Transaction"; var IsHandled: Boolean) (integration): Integration event raised before outbox send validation to enable custom send checks.
  • OnOutboxCheckSendOnBeforeHandledICOutboxTransFindFirst(var ICOutboxTrans: Record "IC Outbox Transaction"; var HandledICOutboxTrans: Record "Handled IC Outbox Trans.") + BC27 (integration): Integration event raised before finding handled outbox transactions for send validation.
  • OnDeleteOnSourceTypeCase(var ICOutboxTransaction: Record "IC Outbox Transaction") (integration): Integration event raised during transaction deletion based on source type. Enables custom cleanup logic for specific source type scenarios.

Procedures

  • ShowDetails(): Opens the detailed view for the outbox transaction based on its source type. Displays appropriate page for journal lines, sales documents, or purchase documents.

Plus 2 local procedures.

Triggers

OnDelete

Relations

Referenced by

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

Pages and codeunits on this 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.

Deprecations

  • field IC Partner G/L Acc. No.: Removed 25.0 (#if not CLEANSCHEMA25), “Replaced by IC Account No.”
  • field Source Type: Removed 29.0 (#if not CLEANSCHEMA29), “Replaced by IC Source Type for Enum typing”

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). 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: "IC Outbox Transaction"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources