Show TOC

  Xsteps in Shop Floor Control Locate this document in the navigation structure


With execution steps (XSteps), you can describe the concrete execution of the production process and group and structure this information in the form of modules. XSteps can be nested hierarchially. Such hierarchial nesting results in XStep trees.

The following describes a possible process flow.

Process Flow

  1. Under   Logistics   Production   Master Data,the   work scheduler enters new standard XStep modules in the standard XStep repository for those process parameters that are to be sent via the interface as process instructions or entered as process messages.

    These process control parameters can be required-measurement specifications (width, height, length, diameter), required-pressure and required-temperature specifications (for injection molding machines, milling and turning machines, presses, drying chambers, etc.).

    The standard XStep building blocks entered can be exported and later reimported.

    See also: Standard XSteps

  2. The work scheduler assigns the standard XStep building blocks entered with the standard XStep repository on the operation overview in the routing. In making this assignment, he or she can reference or copy the standard building block (by referencing and subsequently exploding the reference) (see also Assign XSteps in Application ).

    You have the following further options:

    • Import a previously exported standard XStep building block

    • Enter new XStep building blocks in the routing without reference to the standard XStep repository

      When maintaining XStep building blocks in the routing, you can make concrete assignments of the various XSteps to the operations. The work scheduler describes these assignments in the properties of an XStep and maintains the context here.

  3. The work scheduler checks the XStep building blocks he or she has written. This is done either in the standard XStep repository or in the routing.

  4. If necessary, the MRP controller or production supervisor creates production orders using the relevant routing. When the production order is opened, routings are selected and the valid routing is copied. In the process, the complete XStep trees valid as at the basic start date are copied into the order.

  5. In exceptional cases, the production supervisor can also create an XStep tree directly in a production order. For this purpose, the same options are available as in the maintenance of the XStep trees in the routing.

  6. In the production order, a Generate Control Instructions for Test function is available, with which he or she can generate a sendable set of control instructions without process messages being created and the production order being updated (see Control Instructions ).

  7. The production supervisor releases the production orders in good time prior to the start of production. Sendable control instructions are generated automatically when an order is released. The production supervisor can tell the result of the generation from the corresponding status of the order (XSez, XSgn, XSpr) from a list of the control instructions for the order.

  8. The control instructions generated must be sent to the control instruction destination (sub- or SAP system) in each case. (Example: required-pressure and required-temperature specifications sent to a control computer for an injection molding machine.) The sending is carried out under the responsibility of the production supervisor by means of the control instruction monitor. Instead of using the dialog transaction, you can periodically start a background job (see Sending Control Instructions ).

    The control instruction destination has been defined in Customizing under   Production   Shop Floor Control   Integration   Process Integration   Control Instructions/Work Instrctions   Control Instruction Destination   Define and Set Up Control Instruction Destination   and assigned to the XStep.

  9. The control instructions that have been sent are processed by the recipient. There are two basic situations:

    • The control instruction destination (recipient) is an SAP ECC system

      1. In this case, the production worker (machine or line operator, worker etc.) works at a PC connected to an SAP system and receives the control instructions in the form of work instructions (see Work Instructions ).

      2. He or she administers the control instructions sent to his or her destination number using the Find Work Instructions function ( see Worklist for Work Instructions ).

      3. He or she chooses the next work instructions awaiting processing, and displays them or works through them in active change mode.

      4. The work instructions are carried out in the so-called Process Manufacturing Cockpit (refer to the documentation for Production Planning in the Process Industries: Process Manufacturing Cockpits ).

      5. The work instructions provide guidance to the machine operator in the performance of his or her work. Input that is required from him or her usually leads to the generation of so-called process messages (see Process Message Categories in Shop Floor Control ).

      6. The input required from the machine operator can be linked to a digital signature. This enables a higher degree of production discipline to be achieved. In addition, all input is saved with timestamp and user and terminal information. (Provided this has been set up in Customizing for the control instruction destination.)

    • The control instruction destination is any subsystem (tRFC-enabled) that has been prepared for the so-called PI-PCS interface.

      In this case, the production worker (machine or line operator, worker etc.) works at a terminal in a non-SAP system. This system receives the control instructions (including all process instructions) and takes over with its software the administration of the work instructions received as well as their presentation for the production worker. While the process instructions are being carried out, corresponding process messages can be entered by the subsystem.

  10. The process messages issued during the production process are collected, administered, and sent to a wide variety of message destinations in the system (production order, confirmation, stock posting, e-mail recipient etc.) via a message monitor and processed via function module.

  11. An enhancement of the mass-processing function for production orders (transaction HVOM) is available to the production supervisor for the complete administration of control instructions, work instructions (plus their processing), and process messages.

    This enables the production supervisor to perform the functions in the aforementioned case using a single transaction and interface. This considerably simplifies his or her work. Possible functions are the sending of control instructions, the processing/carrying out of work instructions, and the receiving/sending of process messages and processing of errors.

For more information on Xsteps, refer to the SAP Library under   Production Planning for Process Industries   Process Management   XSteps (Execution Steps).