MF70 - Aggregate Collective Backflush

SAP Transaction Code - Details

• Transaction Code: MF70

  Description: Aggregate Collective Backflush

  Release: S/4HANA and ECC 6

  Menu Path:

  • Logistics > Logistics Execution > JIT Inbound > Environment > Repetitive Manufacturing > Data Entry > Separated Backflush
  • Logistics > Production > Repetitive Manufacturing > Data Entry > Separated Backflush
  • Logistics > Production > Kanban > Environment > Repetitive Manufacturing > Data Entry > Separated Backflush

• • Program: RMSERI70

    Screen: 1000

    Authorization Object:

  • Development Package: MD04

    Package Description: Repetitive Manufacturing

    Parent Package: APPL

  • Module/Component: PP-REM

    Description: Repetitive Manufacturing

Smart SAP Assistant

• SAP Tcode: MF70 - Aggregate Collective Backflush

  
  Overview:
  The SAP transaction code MF70 is used to aggregate collective backflush. This transaction code is used to backflush collective components in a production order. It is used to reduce the amount of manual work required when backflushing collective components. 
  
  Functionality: 
  The MF70 transaction code allows users to backflush collective components in a production order. It aggregates the collective components and backflushes them in one step, reducing the amount of manual work required. The transaction code also allows users to view the collective components that have been backflushed and the quantity of each component that has been backflushed. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code MF70 in the command field. 
  2. Enter the production order number in the Order field. 
  3. Select the Backflush button. 
  4. Enter the quantity of each component that needs to be backflushed in the Quantity field. 
  5. Select the Execute button to complete the backflush process. 
  6. Select the Display button to view the collective components that have been backflushed and their respective quantities. 
  
  Other Recommendations: 
  It is recommended that users check all entries before executing the backflush process, as incorrect entries may lead to incorrect results or errors in the system. Additionally, users should ensure that they have sufficient stock of collective components before executing a backflush process, as insufficient stock may lead to errors or delays in production orders.