Kontakt

Ansicht
Dokumentation

/CWM/CM_3: Functions in the Repetitive Manufacturing Area (New) ( RELN/CWM/606_CM3_1_REM )

/CWM/CM_3: Functions in the Repetitive Manufacturing Area (New) ( RELN/CWM/606_CM3_1_REM )

Fill RESBD Structure from EBP Component Structure   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

/CWM/CM_3: Functions in the Repetitive Manufacturing Area (New)

Use

As of SAP Enhancement Package 6 for SAP ECC 6.0, Industry Extension Catch Weight Management (IS-CWM 606), the CWM, Repetitive Manufacturing and Additional Processes (/CWM/CM_3) business function is available.

Previously Catch Weight Management did not support any functions or processes in repetitive manufacturing.

All repetitive manufacturing functions are now supported in a CWM system for non-catch weight materials (at header and component level), and for catch weight materials the main processes of a number of repetitive manufacturing scenarios (including confirmations) with CWM parallel quantities are supported.

Material master

Up to now, the specific settings for repetitive manufacturing for use by CWM for catch weight materials were locked. The fields Repetitive Manufacturing Allowed Indicator and Repetitive Manufacturing Profile are now ready for input. You can use these fields and their related functions (for example, repetitive manufacturing profile) for both catch weight materials and non-catch weight materials.

Product cost collectors

For repetitive manufacturing, there are product cost collectors for collecting the actual costs of a manufactured material within a particular period. Previously the related administrative transactions were not available in a Catch Weight Management system.

  • Create Product Cost Collector (transaction KKF6)
  • Change Product Cost Collector (transaction KKF7)
  • Display Product Cost Collector (transaction KKF8)
  • Process Product Cost Collector (transaction KKF6N)
  • Create Multiple Product Cost Collectors for Production Versions (transaction KKF6M)

These restrictions no longer apply. Furthermore, the preliminary costing of product cost collectors is possible in a CWM system for both catch weight and non-catch weight materials.

Cost estimate

The standard cost estimate for repetitive manufacturing is now supported for both catch weight and non-catch weight materials.

Material staging in repetitive manufacturing

For non-CW materials, you can now use material staging in a CWM system as in a non-CWM system. For catch weight materials, material staging is supported with staging type Storage Location Level.

The following transactions have been adapted:

  • Material Staging List (Pull List) (transaction MF60)
Note that for the staging of catch weight material components, CWM only supports a stock transfer reservation in an MM-IM managed location, and no direct transfer posting. In this case, use transaction MF65.
  • Material Staging: Situation (transaction MF63)
  • Material Staging: Stock Transfer for Reservation (transaction MF65)
  • Material Staging: Log (transaction MF63)

Confirmation in repetitive manufacturing

Confirmation of yield and scrap of assemblies, including withdrawal postings of components and also confirmation of activities are now available for catch weight and non-catch weight materials. Confirmation in Repetitive Manufacturing (transaction MFBF) has been adapted for this.

In addition, Catch Weight Management supports the integration of the confirmation in the Handling Unit Management (LES-HU) component. Pack in Repetitive Manufacturing (transaction HUP1) and HU Backflush in Repetitive Manufacturing (transaction MFHU) have been adapted for this.

Note that in a CW system, there is no automatic update of backflushing for CW materials, but they have to be managed using a dialog which gives you the option of manually correcting the proposed backflushes.

For catch weight materials, the system creates the default values for withdrawals depending on the data already entered:

  • Based on the current average weight of the batch used, or
  • Based on the current average weight of the material in the issue storage location, or
  • Based on the conversion factor from the material master

The system only ever evaluates the inventories generally available to determine the current average weights.

As an alternative, you can use a BAdI implementation for a customer logic for determining the default value [BAdI: Default Data Logic for Quantities in Different Application Components (/CWM/MAIN_QUAN_PRPSL_EHP5); method PROD_GM_CALC_QTY_PROPOSAL].

Catch Weight Management supports the following confirmation types for catch weight and non-catch weight materials:

  • Assembly confirmation
  • Component confirmation
  • Activity confirmation

These confirmation types are available for the following production scenarios (including the related enhanced BAPI function modules):

  • Confirmation for make-to-stock production (-> BAPI_REPMANCONF1_CREATE_MTS)
  • Confirmation for make-to-order production (-> BAPI_REPMANCONF1_CREATE_MTS)
  • Confirmation for production by lot procedure (-> BAPI_REPMANCONF1_CREATE_MTP)

If you have confirmed one of these production scenarios in an external system, you can transfer the confirmation with the related BAPI function module to an SAP system. These BAPIs are enhanced with CW-specific parameters /CWM/BFLUSHDATAGEN and /CWM/GOODSMOVEMENTS, so that the parallel quantity and the parallel unit of measure can be forwarded for the catch weight materials.

For additional information about these BAPIs, see the new CWM business object CWM Repetitive Manufacturing Confirmation (CWMRepManConfirm1).

Backflushing and postprocessing

If when you process backflushing you encounter an incorrect goods issue posting, the system generates and saves the related error and posting information, in order to be able to correct the goods issue posting later. The following transactions have been adapted for this, so that both quantities can be displayed and processed for catch weight materials:

  • Postprocess Backflush Items (Transaction MF45)
  • Collective Postprocessing (transaction MF46)
  • Postprocessing List for Components on Line (transaction MF47)
  • Individual Component Postprocessing (transaction COGI)

If you change one of the two quantities in postprocessing, the system creates a default for the other quantity. You can influence this default logic for each customer using method PROD_GM_CALC_QTY_PROPOSAL of BAdI: Default Data Logic for Quantities in Different Application Components (/CWM/MAIN_QUAN_PRPSL_EHP5).

Batch where-used list in repetitive manufacturing

The optional use of the m:n relationship for batch where-used lists is supported in a CWM system (repetitive manufacturing profile). The batch where-used list for catch weight materials has been enhanced for this with the parallel unit of measure, and Display Batch Where-Used List (transaction MB56) and Batch Information Cockpit (transaction BMBC) adapted.

Document log

The system saves all related documents for confirmation in a document log. You can use various selection criteria for compiling and printing the required lists.

Display Document Log Information (transaction MF12) has been enhanced with fields for catch weight materials.

CWM in production including repetitive manufacturing

Previously there were only a limited number CWM enhanced dynpros for processing material movements in production available (for example, splitting the goods movements, goods movements from the production order or process order).

As of SAP Enhancement Package 6, the default logic of method Default Values for Goods Movements in Production(PROD_GM_CALC_QTY_PROPOSAL) is available for all dynpros for processing material movements in production. You can implement different default logic (for example, depending on the order category) using a customer implementation taking into account the transferred control parameters.

Effects on Existing Data

The CWM adaptation means:

  • You can continue to use non-catch weight materials as in a non-catch weight system.
  • For catch weight materials, you can process and display quantities in parallel unit of measure in the functions supported.

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information






Vendor Master (General Section)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 10463 Date: 20240426 Time: 122237     sap01-206 ( 149 ms )