Administration on Product Documentation

Role center

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The Intercompany role center is the central entry point for everyone who works with IC documents regularly. It bundles navigation, key figures, and actions in one place so that typical tasks can be done without detours.

Access in Business Central

Pick the role center through the user/role assignment in user management or through My settings.

Click to enlarge

Prerequisites

User has the right permissions (see Permissions).
Intercompany is configured at the company level.

Activities

Entry point for partner maintenance, transaction overviews, and the error log.
Direct navigation to the job queue for retries and error analysis.
Start common actions for sending, accepting, and remediating IC documents.

Click to enlarge

Permissions

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

BE-terna Intercompany ships its own permission sets that are granted in addition to the Business Central standard IC permissions. This page describes the sets and their typical assignment.

Access in Business Central

Permissions are managed through permission sets and user management.

Prerequisites

Administrator rights to assign permission sets.
Knowledge of which roles in the company work with Intercompany.

Activities

Assign the matching permission set to every IC user.
Review and adjust assignments when roles change.
Use a test company to validate new roles before rollout.

Fields and actions

Permission set	Purpose
`BET ICY BASIC`	Basic rights for every IC user; covers reading and working with IC documents.
`BET ICY SETUP`	Additional rights to maintain the intercompany setup and IC partners.
Related BC standard sets	Must be granted alongside so that sales and purchase keep working.

Monitoring and troubleshooting

Missing permissions often only surface when accepting an IC document. Check the user’s permission sets first in such cases.
Job queue and error log require additional standard rights.

Best practices

Apply least privilege: grant BET ICY SETUP to administrators only.
Audit permissions periodically, especially after rollouts or upgrades.

Inbox and outbox

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The IC inbox and IC outbox show every IC transaction and its current state. They are the primary workspace for daily operations: sending, accepting, re-queueing, error analysis.

Access in Business Central

Inbox and outbox are reached through the role center or through search.

Prerequisites

Intercompany is configured and at least one IC partner is active.
Permissions for IC transactions are granted.

Activities

Send or accept pending transactions on demand.
Analyse failing transactions and restart them.
Review processed transactions as history.

Fields and actions

Action	Effect
Send (outbox)	Transfers the transaction to the partner.
Accept (inbox)	Picks the transaction up at the receiving company.
Reject	Marks the transaction as not to be processed.
Retry	Restarts a previously failing processing.

Monitoring and troubleshooting

When transactions stay in Open for long, check the job queue.
Transactions in Error reference entries in the Error log.

Best practices

Walk through the inbox daily, even with automatic acceptance enabled.
Sweep the outbox regularly for old Open entries – they often point to disabled queue jobs.

Transaction status

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Every IC transaction moves through several statuses. This page describes what each status means and the typical transitions so users can see where a transaction stands and what to do next.

Access in Business Central

The status is visible in the IC inbox, IC outbox, and the transaction overviews.

Prerequisites

Access to IC transaction lists.
Basic knowledge of the IC flow (send, accept, post).

Activities

Check status regularly and handle outliers early.
On Error look up the cause in the error log.

Fields and actions

Status	Meaning
New	Transaction has been created but not sent/accepted yet.
Open	Transaction is being processed (for example by the job queue).
Error	Processing has aborted; details are in the error log.
Accepted	Receiver has picked the document up.
Rejected	Transaction was intentionally not processed.
Completed	Transaction has run through and is archived.

Monitoring and troubleshooting

Several transactions in Open over a longer time → check the job queue.
Do not mass-retry transactions in Error without understanding the cause.

Best practices

Include the status field in the daily tiles of the role center.
Document Rejected deliberately so that later questions stay traceable.

Error log

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The error log is the central place for failing IC processing. Every aborted transaction leaves an entry with timestamp, transaction reference, and error text.

Access in Business Central

Open the error log from the role center or via search.

Prerequisites

Permission to read IC error log entries.
Access to the source and target documents to remediate.

Activities

Read error messages and identify category and root cause.
Clean up the affected transaction and restart it.
Mark entries as handled or document why they remain deliberately.

Fields and actions

Field	Content
Date/Time	Time of the abort.
Source	Affected IC transaction or job queue entry.
Error text	Business Central error message.
User	Running user or job queue system user.

Monitoring and troubleshooting

Recurring error texts hint at a setup or data problem, not at single events.
Always clarify the cause before a mass retry; otherwise retries create new entries.

Best practices

Walk through the error log at least daily.
Fix recurring error types in partner or master-data maintenance.

Job queue

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The job queue carries automatic IC document processing. This page describes daily operations: monitoring, start/stop, error analysis, and retry strategy. Initial configuration is documented on the Job queue setup page.

Access in Business Central

Reach job queue entries from the role center or via the Job Queue Entries search.

Prerequisites

Job queue is configured (see setup page).
User has rights to start/stop entries.

Activities

Check the state of IC entries (Ready, In Process, Error).
Restart failing entries in a targeted way.
Adjust schedules when load changes.

Fields and actions

Action	Effect
Set to Ready	Restarts an entry, for example after an error.
Put on Hold	Temporarily stops cyclic execution.
Show error	Opens the last error message.
Max. no. of attempts	Limits automatic retry.

Monitoring and troubleshooting

Fix Error entries with a speaking message first before retrying.
Long-running In Process states hint at stuck sessions – put the entry on hold and restart it.
Automatic retry through the intercompany setup (see Automation) reduces manual work.

Best practices

Always set a max. number of attempts – unlimited is rarely useful.
Choose cycle frequency as high as necessary, not higher.

Azure File Share

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

BE-terna Intercompany supports file exchange between IC partners via an Azure File Share. This page describes daily administration of that exchange – the underlying permissions are maintained in the Azure portal.

Access in Business Central

Azure File Share settings are visible on the IC partner card in the transfer-type section.

Click to enlarge

Prerequisites

Azure storage account with a file share; access is granted through a SAS token (never through persistent account keys inside BC).
Partners use the same file-share path for the bilateral exchange.
Transfer type File location is active on the IC partner card.

Activities

Monitor SAS token validity and renew it in time.
Keep the share permissions in Azure as narrow as possible.
On issues: check network access and target folder before touching the IC setup.

Fields and actions

Field	Purpose
File share path	Source or target folder of the exchange.
Access token	Time-limited SAS token.
Checksum	Optional: validates exchanged files.

Monitoring and troubleshooting

File not found almost always points to an expired token or a changed path.
Connection issues create entries in the Error log.
The job queue for automatic import only works if the IC partner folder exists.

Best practices

Issue SAS tokens with the shortest reasonable validity and minimal rights.
Separate folders per partner to prevent data mixing.