Show TOC

Background documentationTransfer of Production Yield Confirmation: Integration Details

 

  • SAP ME sends an ERP yield confirmation per SFC number / reporting step with the following information:

    • Production Order

    • Operation

    • Yield

    • Quantity

    • Base Unit of Measure of the produced material

    • Batch Number

    • Components

      Components (including component batch information provided for each component assembled onto the SFC number)

      The ERP Yield Confirmation DA Plug-In configured for the ERP_YIELD_CONFIRMATION collaboration directive support the following data acquisition parameters:

      • components

        Valid values:

        • all: reports all the components to SAP ERP irrespective of the Backflush in ERP setting on the Build tab of Material Maintenance.

        • none: does not report any components to SAP ERP.

        • noneIfBackflushed (default): does not report any components to SAP ERP if at least one of them has Backflush in ERP selected on the Build tab of Material Maintenance (see Build Tab).

        • onlyNonBackflushed: reports only components which have Backflush in ERP deselected on the Build tab of Material Maintenance.

      • timebasedComponents

        Valid values:

        • true (default): time-based components are included into yield confirmation.

        • false: time-based components are not included into yield confirmation.

      • tbCompsOnlyFromLoadedSlots

        Valid values:

        • true: Executes optimized code when retrieving the assembled time-base component information. Retrieves only components loaded on the time-based resource and does not account for the converted time-based records stored in the SFC_ASSY database table.

        • false (default): Does not execute the optimized code.

        Note that this parameter does not affect the way discrete assembly records are retrieved. Discrete components are reported to SAP ERP no matter what parameter setting is used.

      Multiple parameters are delimited by a semicolon (;).

      Example Example

      components=onlyNonBackflushed;tbCompsOnlyFromLoadedSlots=true

      End of the example.

      Goods movement is not triggered for phantom components. Goods movement is triggered for components that are members of a phantom component.

      Goods movement is not triggered for floor stock pegged to a shop order.

    • Serial Number for component

      Only if SAP ERP 6.05 (business functions LOG_PP_MES_INT_01 and LOG_PP_MES_INT_02 are activated) or later is used. See also Production Yield and Serial Numbers later in this topic.

    • Storage Location of the inventory ID or from the material master maintained in SAP ME

      Populated from SAP ERP material master (Prod. Stor. Location on the MRP 2 tab page) during the material transfer.

  • When the last reporting step is completed in SAP ME (see Routing Step Properties), SAPMEINT also sends the goods receipt of the produced material and reports the following:

    • Batch Number for shop order

      Note Note

      If a Production shop order contains a batch number that was defined in SAP ERP and the BATCH_NUMBER data parameter was entered for the planned material of this shop order, SAPMEINT sends the BATCH_NUMBER value and batch characteristics. For more information, see Transfer of Batch and Batch Characteristic Data and Transfer of Production Order with Batch Number.

      End of the note.

    • Base Unit of Measure of the produced material

    • Storage Location of the produced material and components

  • SAP ME sends the confirmation of the Automatic Final Confirmation type so that SAP ERP can automatically determine relevant actions such as clearing reservations and capacity reduction.

  • Batch characteristics are reported to SAP ERP 6.00 – 6.04 with the message type BatchCharsPosting or with the normal confirmation message to SAP ERP 6.05.

  • If a confirmation was not successful due to locking in SAP ERP, SAPMEINT re-sends the messages to SAP ERP based on Retry Period defined in SAPMEINT Workflow Configuration (see SAPMEINT Workflow Configuration).

Production Yield and Scheduling Information from SAP Shop Floor Dispatching and Monitoring Tool (SFDM)

If a Production shop order contains scheduling information transferred from SFDM, then the confirmation message contains the following data:

  • Split ID

  • Capacity Category

    Note that only category 001 (Machine) is supported.

  • Confirmed Quantity

  • If an SFC number is completed on a resource from the list of planned resources associated to a Split ID:

    • The Confirmed Quantity of the corresponding Split ID is increased and this Split ID is included in the confirmation message.

    • The Confirmed Quantity can exceed the Planned Quantity. If the Confirmed Quantity is equal to or greater than the Planned Quantity, then SAP ME assumes that this Split ID is fulfilled and it no longer appears in the POD’s Work List.

  • If an SFC number is completed on a non-planned resource and all Split IDs of the shop order have associated planned resources, then the Confirmed Quantity is increased for the last Split ID by Planned Start Time and this Split ID is included in the confirmation message.

  • If an SFC number is completed on a non-planned resource and not all Split IDs of the shop order have associated planned resources:

    • The Confirmed Quantity is increased for the last Split ID that does not have associated planned resources by Planned Start Time and this Split ID is included in the confirmation message.

    • The Confirmed Quantity can exceed the Planned Quantity.

Production Yield and Serial Numbers

When reporting yield, SAPMEINT sends collected serial numbers of assembled components at an ERP reporting step. If SAP ERP production order contains serial numbers for the main assembly, SAPMEINT reports them at the last ERP reporting step (see Transfer of Production Order with Serial Numbers).

Overproduction is possible only if the production order was updated in SAP ERP and new serial numbers were used.

Production quantity can increase only if the production order was updated in SAP ERP and new serial numbers were used.

In SAP ME, Production shop order status must be set to Done. The COLLABORATION_SHOPORDER_COMPLETE action is triggered. Then, not used serial numbers can be deactivated in SAP ERP.

Confirmation Restrictions

  • SAPMEINT does not report activity times.

  • SAP ME does not support the ERP concept of different unit of measure at the operation level.

  • Nested routings are not supported when Close and Done in SAP ME Pack/Unpack is used.

  • SAPMEINT sends confirmations to SAP ERP only for closed containers of the Material pack level. Containers of the Container or Process Lot pack level are not processed (see Container Maintenance).