Inter-site Transactions

Introduction #

Silicon ioi is an ERP software designed for the integrated management of multiple sites within a coherent workflow. These sites can belong to the same company or different companies, while respecting logistical flows and pricing between companies or sites, with specific costs for each site.

Multi-Site Management with Distinct Costs per Site #

Silicon ioi inherently manages distinct costs for each site. The standard cost can be defined either per site or globally.

Inter-Site Flows Aligned with Customer Delivery and Supplier Reception Flows #

Stock movements between sites are handled similarly to delivering to a customer or receiving from a supplier. These flows involve the transfer of products from one site to another via a carrier, making them integral to the delivery flows for the departure site and reception flows for the arrival site. Customers and suppliers are specifically identified as “inter-site” for clear distinction.

Possibility of Inter-Site Invoicing #

If sites need to invoice each other for value transfers (e.g., when sites belong to different companies), these deliveries can lead to invoicing between the parties, following the standard workflow.

Inter-Site Configuration #

Here are the definition steps:

Customer and Supplier Identifiers #

It is crucial to define customer and supplier identifiers for each site. Please refer to the example in the demonstration database where three customer identifiers are linked to three supplier identifiers.

Here are the inter-site customer identifiers defined for three sites (BXL/ANT/LG) :

They also have corresponding identifiers on the supplier side. They are categorized as inter company and are linked through the following correspondence fields:

• Supplier Link (Customer)
• Customer Link (Supplier)

Inter-Site Rules - Automation #

In the ioi site module, you can define rules for each site in inter-site relations.

You can establish the formal customer-supplier correspondence for an inter-site and define specific rules for each site.

• What is the purchase journal to benefit from inter-site automation?
• What is the sales journal associated with these automations?
• What is the preparation time for deliveries (shipping) to a site, if there is stock?
• What is the default transport time between sites?
• What is the margin to add to the cost of the item in cost mode?
• Which family of items is exempt from the cost valuation policy (and is therefore based on purchase and sale prices)?
• Are these transfers governed by a cost-based transfer (with a possible margin)?
• Is it necessary to propose a pre-prepared reception when making the delivery?
• Can there be invoicing between sites?

Making a Delivery to a Site #

1. Go to Sales Delivery Orders.

1. Select the departure site wishing to deliver to another site.

1. Create a Delivery Order (in the correct journal).

→ Specify the delivery customer as the customer of the destination site:

→ Immediately, the system will detect that it is an inter-site delivery:

1. Complete the delivery.

→ The system will present the cost of the item in the discount field.

1. Validate the delivery.

→ If configured, the system may propose to create the receipt order on the other site:

→ By answering Yes, you will be notified of its creation:

1. In the Purchases Receipt:

→ Select the destination site:

→ You will find the receipt order ready to be received:

---

Integrating Your “Inter-Site” Supplies into Purchases #

The system allows for ‘mirror automations’ of orders between different sites.

1. Record a purchase order from a site in need of supplies by asking another site to make the delivery.

1. When you put this supplier (purchase) order in pending, a customer order is generated on the other site.

→ A link has been established between each line of the purchase order and each line of the sales order created in correspondence. You can view this link in the Document Flow tab.

1. The sales order is created in the site that will make the delivery to the requesting site.