Intercompany partner

IC partner card setup: transfer, exchange format, and process-specific options per IC partner.

Purpose

The partner card describes a concrete business partner in the intercompany exchange. Settings on the partner level override the global switches from the intercompany setup and define the transport channel, file format, and process-specific behaviour.

Prerequisites

  • Intercompany setup is completed.
  • The partner company is known (company name or external IC code).
  • The exchange method (server directory, Azure File Share, or direct company access) is agreed with the partner.
  1. Create the partner, record the code and company/path information.
  2. Pick the import/export implementation (XMLport) – keep the default for the standard format.
  3. Set process options for purchase, sales, drop shipment, and warehouse receipt.
  4. Send a test document to the partner and verify the outcome in the role center.

Setup building blocks

General

Define the partner code, base information, and whether the partner actively participates in the exchange.

IC partner: general Click to enlarge

Sales transaction

Controls behaviour when sending and receiving sales documents: handling of deviating prices, descriptions, and quantities; shipment transfer and order changes. Details on the Extensions and Order changes pages.

IC partner: sales Click to enlarge

Purchase transaction

Controls behaviour for incoming IC shipments and invoices: warehouse receipt, invoicing through the purchase order, item tracking permission, drop shipment. Details on the Warehouse receipt, Purchase invoice, and Drop shipment pages.

IC partner: purchase Click to enlarge

Transfer format

The Import/Export field sets the XMLport used for file exchange. For custom file formats a dedicated interface implementation can be selected (see Custom file formats).