Page 653 "Intercompany Setup"
Base Application · Microsoft.Intercompany.Setup
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Intercompany.Setup · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Intercompany Setup |
| SourceTable | IC Setup |
| PageType | Card |
| UsageCategory | Administration |
| 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 |
|---|---|---|---|
| General | IC Partner Code | IC Partner Code | Specifies your company’s intercompany partner code. |
| IC Inbox Type | IC Inbox Type | Specifies what type of intercompany inbox you have, either File Location or Database. | |
| SynchronisationGroup | Synchronisation Partner | Partner Code for Acc. Syn. | Specifies the partner you want to synchronise with. The selected partner will be used during the synchronisation of your Intercompany Chart of Account and Intercompany Dimensions. |
| General | IC Inbox Details | IC Inbox Details | Specifies details about the location of your intercompany inbox, which can transfer intercompany transactions into your company. |
| Auto. Send Transactions | Auto. Send Transactions | Specifies that as soon as transactions arrive in the intercompany outbox, they will be sent to the intercompany partner. | |
| Transaction Notifications | Transaction Notifications | Specifies whether the system should send you notifications when a new transaction is sent to the intercompany outbox. | |
| Default IC Gen. Jnl. Template | Default IC Gen. Jnl. Template | Specifies the journal template name that will be used to create journal lines as soon as transactions arrive in the intercompany inbox. | |
| Default IC Gen. Jnl. Batch | Default IC Gen. Jnl. Batch | Specifies the journal batch that will be used to create journal lines as soon as transactions arrive in the intercompany inbox. | |
| Log API Requests | Log API Requests | Specifies whether to log outgoing and incoming intercompany API requests for troubleshooting. | |
| Content | IC Partners List Part | part Page 622 “IC Partners List Part” | — |
| FactBoxes | Diagnostics | part Page 9051 “Intercompany Setup Diagnostics” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Add IC Partner | Setup a new intercompany partner. | Page 609 “IC Partner Card” |
| IC Chart of Accounts | Define the shared chart of accounts to use across different companies. | Page 605 “IC Chart of Accounts” | |
| IC Dimensions | Define the shared dimensions to use across different companies. | Page 600 “IC Dimensions” | |
| Connection Details | Access the connection details that your intercompany partners will use to connect to your company if they’re in different environments. | Page 566 “IC Connection Details” | |
| Troubleshooting | API Log Entries | View logged intercompany API requests and responses for troubleshooting. | Page 621 “IC API Log Entries” |
| Job Queue Errors | View job queue log entries with errors for intercompany background tasks. | ||
| Outgoing Notifications | View outgoing intercompany notifications and their delivery status. | Page 655 “IC Outgoing Notifications” | |
| Incoming Notifications | View incoming intercompany notifications and their processing status. | Page 693 “IC Incoming Notifications” |
Triggers
OnOpenPage
Relations
- source table Table 443 “IC Setup”
Called by
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.
- Page 608 “IC Partner List” (1 call:
OnOpenPage → (object))
Documented on Microsoft Learn
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: "page", object_name: "Intercompany Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.