Important points before configuring interfaces

The following points should be considered before configuring any of the three standard M3 SWB interface technologies:
  • Order status: Must be between 1 and 80.
  • Order group and color group: Used to control the order list selections and colors that are used in the Scheduling Boards and load profiles.
  • Network priority: During order input or local order generation a network priority is assigned to individual orders in the network. Normally the network priority should be maintained in M3 SWB: When using local order generation, the priority (defined in the ITEM file) is transferred as a network priority.
  • Stored in the central system (if you want to save it for use in other complete order transfers).
  • Transferred from the central system along with the order transfer.
  • Co-sorting key: 20-character field that is used to control the sorting and calculation of setup and changeover times during sequencing.
  • Sequencing status: the sequencing status on operations can be modified in M3 SWB, especially in these cases:
  • Status 15: Both sequence locking and timestamp fields are used to define the sequence.
  • Status 20: Fixed locking status. The timestamp controls the start of the operation To assure that new order transfers do not destroy existing information you must store planning status codes and associated timestamp information in special fields in the central database and upload them from M3 SWB.
  • M3 SWB order number: when M3 SWB generates a manufacturing order locally with one level MRP it gets a unique identification ITEM number combined with an M3 SWB order number.
  • M3 SWB assigns each ITEM a field based on the highest order number it has generated so far. This number increases by 1 for each order generated. When the generated orders have been uploaded to the central system, a new order number can be inserted and the orders can subsequently be downloaded to M3 SWB again. The order number in M3 SWB is temporary until a new order number is inserted by the central system.
  • Due date and release date: when you extract order data you may want to insert a time and date option.
  • Delivery date for purchased orders: the planned delivery date for purchased items can be transferred from the central system. The delivery date can include expected delivery times, as well as time for various acceptance procedures (inter lead-time). The availability date for purchased materials is used by the synchronization function in M3 SWB.
  • Order time stamp: the time stamp records the time at which the order was first generated or last modified and stores it in the central system. You can select orders based on this time stamp. M3 SWB automatically inserts it into the local order generation procedure.
  • Release date: when orders are transferred from the central system and no release date is defined, M3 SWB uses the planned start date from the last upload to the central system as the earliest start date assigned to the order.
  • Synchronization. This function generates:
    • A demand date for planned deliveries of purchased items. This date is inserted in the demand record for the purchased material.
    • The component order number for the manufactured item that meets the demand is inserted in the material link to the parent order.