Page 613 "Handled IC Outbox Transactions"
Base Application · Microsoft.Intercompany.Outbox
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Intercompany.Outbox · captioned “Handled Intercompany Outbox Transactions” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Handled Intercompany Outbox Transactions |
| SourceTable | Handled IC Outbox Trans. |
| PageType | List |
| UsageCategory | Lists |
| ApplicationArea | Intercompany |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Control1 | Transaction No. | Transaction No. | Specifies the transaction’s entry number. |
| IC Partner Code | IC Partner Code | Specifies the code of the intercompany partner that the transaction is related to if the entry was created from an intercompany transaction. | |
| Status | Status | Specifies what action has been taken on the transaction. | |
| Source Type obsolete Pending 27.0; #if not CLEAN27 | Source Type | Specifies whether the transaction was created in a journal, a sales document, or a purchase document. | |
| IC Source Type | IC Source Type | Specifies whether the transaction was created in a journal, a sales document, or a purchase document. | |
| Document Type | Document Type | Specifies the type of the related document. | |
| Document No. | Document No. | Specifies the number of the related document. | |
| Posting Date | Posting Date | Specifies the entry’s posting date. | |
| Transaction Source | Transaction Source | Specifies which company created the transaction. | |
| Document Date | Document Date | Specifies the date when the related document was created. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Outbox Transaction | Go to Document | Navigate to the document sent. | |
| Go to Inbox | Navigate to the intercompany inbox transactions. | Page 615 “IC Inbox Transactions” | |
| Go to Handled Inbox | Navigate to the intercompany handled inbox transactions. | Page 617 “Handled IC Inbox Transactions” | |
| Go to Outbox | Navigate to the intercompany outbox transactions. | Page 611 “IC Outbox Transactions” | |
| Details | View transaction details. | ||
| Comments | View or add comments for the record. | Page 620 “IC Comment Sheet” | |
| Functions | Re-create Outbox Transaction | Re-creates a transaction in the outbox. For example, if you accepted a transaction in your outbox but then deleted the document or journal instead of posting it, you can re-create the outbox entry and accept it again. |
Relations
- source table Table 416 “Handled IC Outbox Trans.”
Documented on Microsoft Learn
- Manage the Intercompany Inbox and Outbox
- Set up intercompany transaction posting
- Manage intercompany transactions
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: "page", object_name: "Handled IC Outbox Transactions"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.