Posting Goods Issues for Process Orders

When an order is created, the system automatically creates a reservation for the required material components. Each material component of the order receives a separate item number within the reservation. You can only withdraw the reserved materials from the warehouse if the operation to which the materials are assigned in the order has already been released. For each reservation item, the following information is available:

• Material number
• Quantity
• (Issue) Storage location

The system automatically tries to determine the issue storage location. Also, it might be necessary to organize material staging from a central storage location to the issue storage location before you can post the goods issue in the system, for example, if purchased components are delivered to a central warehouse, but your shop floor is assigned to a different storage location. We will discuss both at a later point in this chapter.

In the figure, the goods issue process to a process order is displayed. Assuming that the materials are already available at the issue storage location, 101B in our example, you can post a goods issue to a process order using one of the following options:

• Manual goods issue posting, for example, using the Post Goods Movements or Pick Components for Process Order apps.
• Automatic goods issue posting together with the order confirmation, for example, using the Confirm Process Order app.
• Automatic goods issue posting together with the operation confirmation, for example, using the Confirm Process Order Phase app.

In case of manual goods issue posting, the system proposes the component quantity and the issue storage location as both are maintained in the reservation. You can either accept the proposed values or change the quantities and/or storage locations as required. You can withdraw a lower quantity if, for example, you only manufacture a fraction of the ordered quantity, or a higher quantity if, for example, some components quantities were lost during the production process.

In case of automatic goods issue posting (→ materials with a 'backflush' indicator) together with a confirmation posting, the system automatically posts a goods issue at the issue storage location maintained in the reservation. The withdrawn quantity scales linearly with the confirmation quantity.

In SAP standard, the goods issue is posted using the movement type 261 (goods issue to a process order).

As already stated above, the components required for the production of the product might not always be available in the required quantity at the storage location. SAP S/4HANA Cloud Public Edition, offers various methods to organize the transfer of components from one storage location to another one. This process is called Material Staging.

The figure shows two different storage locations in one plant: The central storage location on the left side, 101A in our example, and the production storage location on the right side, 101B in our example. After purchasing and delivery from the supplier, raw materials are stored in a warehouse which is modeled as central storage location in the system. Furthermore, semi-finished components which were manufactured in other production facilities might also be stored here. For organizational reasons, the shop floor is modeled as a separate storage location. Therefore, before the production operators can consume the components, the latter must be staged from the central warehouse to the production storage location. SAP S/4HANA Cloud Public Edition offers several approaches, for example:

• Stock transfer using the Pull List

  The pull list controls the internal flow of material to supply production. It is assumed that the components required for production have already been produced in-house or procured externally and now merely need to be moved from their current storage location (101A) to the production storage location (101B). The pull list supports various replenishment strategies, for example, direct stock transfer (one step process) or triggering replenishment via stock transfer reservations (two-step process).

  You can, for example, execute the pull list on one day to trigger material staging of all components that are required on the shop floor on the following day. First, the system calculates the shortfall quantities at the receiving storage location. Then the system creates a replenishment proposal for the shortfall quantities. In our example, a replenishment proposal for a missing component corresponds to a direct stock transfer of a component from the central to the production storage location. In the last step, you accept the replenishment proposals and trigger staging. In the case of direct stock transfer, the system posts the stock transfer, that is, the goods issue for the components from the central to the production storage location. The physical stock transfer, however, is not executed in the system.

• Classic Kanban stock transfer

  Kanban is a procedure for controlling production and material flow based on the physical material stock in production. Material that is required on a regular basis is continually kept available in small quantities in production. With Kanban, the replenishment or production of a material is triggered only when a certain quantity of the material has been consumed.

In the classic Kanban production control method, the demand source (for example, a production work center), the supply source (for example, a central storage location), and the procedure to be used to replenish the material (for example, direct stock transfer or stock transfer with reservation) are defined in the control cycle which is displayed in the figure above. In addition, the number of Kanban containers that circulate between the supply source and the demand source, and the quantity per container are defined in the control cycle.

Each Kanban container contains the quantity of material that work center personnel need for a certain period of time. When executing the Kanban process, the Kanban container circles between the demand and supply source: As soon as a container is emptied by the demand source, a replenishment signal is triggered (for example, by scanning a barcode). The signal is received by the supply source for the required material (for example, warehouse) and replenishment is started. After the now full again container is transferred back, that is, from the supply source to the demand source, the latter acknowledges the receipt of the container (for example, by scanning another barcode), which completes the Kanban cycle for one container.

Similar to the Pull List approach, Kanban in SAP S/4HANA Cloud Public Edition, supports various replenishment strategies for stock transfer:

• The simplest replenishment strategy is a replenishment using direct transfer posting: You use this function if you want to transfer components without any previous reservation. Setting the Kanban to empty automatically triggers a transfer posting.
• If you prefer a two-step procedure, you can use the replenishment using reservations approach: Setting the Kanban container to "Empty" generates a reservation from the supplying to the receiving storage location. The material is transferred with reference to the reservation and moved to the receiving storage location. The transfer posting automatically sets the Kanban container status to "Full" or, on the other hand, the change of status to "Full" automatically triggers the transfer posting.
• And so on.

For each material component in a process order, a default issue storage location can be determined at order creation based on master data settings. Note that the automatic determination of the issue storage location is not mandatory: When manually posting the goods issue, you can use, for example, stock determination or batch determination to automatically determine the storage location of the component. If you do not want to use an automatic approach at all, you can always manually specify the goods issue storage location in the respective app.

When automatically posting goods issue, it is mandatory to maintain the goods issue storage location in the process order as the automated goods movement fails if no storage location is maintained as the system does not know in this case from which physical location the component was taken.

As stated above, when the order is created, the system checks the master data to determine the goods issue storage location for each component. Since you can maintain the issuing storage location in different master data elements, it is important to understand the processing sequence used by the system:

1. The manual assignment of a goods issue storage location to the component in the order is always considered with highest priority. In a consequence, you can always manually override the proposed storage location if required.
2. Resource → production supply area → storage location: When defining production supply areas, you can assign the former to a storage location. Furthermore, you can assign resources to production supply areas. If this is the case, the system determines the goods issue storage location of a component via the following sequence: Assignment of component to production phase → assigned resource → assigned production supply area → assigned storage location
3. BOM item: During BOM maintenance, you can assign a storage location to each BOM item. If you alternatively assign a production supply area (PSA) in the BOM item and the PSA is assigned to a storage location, the latter is automatically entered in the BOM item.
4. Material master: During material maintenance, you can assign a storage location to the component (field Production Storage Location on the MRP 2 view of the material master).

To automatically post the goods issue for a component together with the order or phase confirmation, the backflush indicator must be set for the respective component. The system offers the following options:

• You can set the backflush indicator in the master recipe (material list). If you set the indicator in the master recipe, it applies irrespective of what you have defined in the material master record.
• You can set the backflush indicator in the material master (MRP view). If the indicator is set to 'always backflush', the backflush indicator is set in the process order for the respective component. If the indicator is empty, you must manually post goods issues for the respective component. As a third option, you can let the resource decide whether a component is backflushed or not.
• You can set the backflush indicator in the resource (Basic Data tab). If the indicator is set, the backflush indicator is set in the process order for the respective component.
• You can set the backflush indicator directly in the process order (material list). Note that this usually only done in exceptional cases.

From a business perspective, SAP recommends to set the backflush indicator in the material master if the material consumption is always automatically posted, for example, in automated manufacturing environments. If the same component is consumed at different resources (some might be able to automatically consume components, some not), you can decide on resource level whether a component posting is executed automatically or not.