IBS Enterprise Help Centre 8.0Business Suite 2014/2015

Process overview for MDC Back-to-Back (BtB) orders

Related topics

The following describes a typical MDC BtB work flow scenario (in sequential order).

  1. A sales order from the end customer is entered into the MDC demanding company's IBS Enterprise system. A BtB transit, or direct, delivery sales order type is used for this transaction that is linked to an MDC purchase order type.
  2. During the sales order line entry stage, an MDC item availability check is performed on the MDC supplying company's system to validate the availability of the item and the feasibility of the dispatch date.
  3. If the item is available on that particular dispatch date, the sales order line can be entered. If it is not, then the system will suggest a new date on which the goods can be dispatched. If the item is available it will be automatically reserved in the MDC supplying company's system for that sale.

    Note: If transfer pricing is enabled, the sales price in the supplying company is also retrieved as per the quantity entered and becomes the purchase price for the demanding company's purchase order that is created once the sales order is created.
  4. Once the sales order is created, a purchase order is automatically created and sent via the MDC application to the MDC supplying company. When it is received a sales order is automatically generated in their system.
  5. The MDC demanding company can modify their end customer sales order according to normal BtB rules which requires that the pick list has not been printed in the MDC supplying company's system (e.g., the sales order is not at status 30).

    Note: The MDC supplying company decides if it should be backlogged but back order creation is performed in the MDC demanding company. The MDC supplying company cannot modify the sales order or backlog the orders. They can, however, modify the dispatch date and quantity.
  6. (For BtB direct orders). Once the pick list is confirmed in the MDC supplying company's system, the goods are shipped to the end customer, and a purchase order confirmation note can be sent to the MDC demanding company.
  7. (For BtB transit and stock replenishment orders). Once the pick list is confirmed in the MDC supplying company's system, the goods are dispatched to the MDC demanding company's transit warehouse and the purchase order in the MDC demanding company is updated.
  8. The invoice is created in the MDC supplying company according to normal rules. However, when it is printed it is automatically sent to the IBS Financials interface file in the MDC demanding company.
  9. If the MDC supplying company is defined for automatic matching, then both invoices, invoice lines and VAT transactions are created and loaded into the interface files in the MDC demanding company.
  10. In the MDC demanding company, run routine Retrieve financial transactions to receive the invoices. If MDC automatic matching is defined, then the invoice will be automatically matched with the purchase order lines.

The following illustrates the communication flow for BtB orders as described above:

Flowchart

Related topics