erpdocs

SAP QM Master Data Training Material (141 Pages PDF)

This training material covers various topics related to QM in SAP, such as creating and changing QM master data, managing Quality Info Records (QIRs), and generating QM reports. Each topic is explained with detailed steps and screenshots as mentioned below;

  1. Quality Management Overview: This section provides an overview of the key features of QM, including integration with inspection systems, non-conformance systems, PLM systems, and direct-ship scenarios.
  2. Manage QM Master Data: This section explains how to extend the quality view of the material master, create and change inspection methods, inspection plans, work centers, and Quality Information Records (QIRs).
  3. Manage Quality Info Records (QIRs): This section covers how to create and change Quality Info Records for a specific material-vendor-plant combination.
  4. QM Reports: This part provides instructions on how to generate various QM reports.

Read more

Quality Management (QM) Configuration Guide in SAP S/4HANA

This pdf document is a sample configuration guide for Quality Management (QM) module in SAP S/4HANA, specialized for automotive industry. Each section in the document provides detailed steps on how to perform the configurations in the SAP system, including the IMG Menu Path/Transaction Code, Description and Configuration Values, and Recommendations. Here’s a summary of the key points:

  1. Introduction: The document aims to provide configuration details for the SAP QM module and is intended for application system administrators. It covers the scope of implementation, the proposed organization structure, and the configuration details.
  2. Maintain Setting at Plant Level: This setup allows you to change and supplement several central controlling functions at the plant level. These functions relate to the planning and implementation of quality inspections.
  3. Define Catalog Types: Catalogs are used in Warranty Processing when you enter items for a version. They can be used as a list of defect codes, labor values, or external services.
  4. Define Sample Type: The sampling type defines the basic conditions for determining the sample size for each inspection characteristic.
  5. Rule for Sample Determination: The sample determination rule is stored in the sampling procedure itself and not in the sampling type.
  6. Define Valuation Mode: The valuation mode, together with the sampling type, defines which parameters the system uses to determine a sample size.
  7. Modify Valuation Rule: This step is to modify the valuation rule.
  8. Assign Task List Types to Material Types: This step is to assign task list types to material types.
  9. Define Task List Usage: This step is to define task list usage.
  10. Define Task List Status: This step is to define a task list status.
  11. Inspection Type: When an inspection lot is created, the system uses the inspection lot origin to determine how the inspection lot will be processed.
  12. Assign Inspection Type to Lot Origin: This step is to maintain the inspection lot origin and assign the inspection type.
  13. Deactivate Inspection For A Goods Movement: This step is to deactivate inspection for a goods movement.
  14. Define Inspection In Plant Maintenance: This step is to define inspection in plant maintenance.
  15. Define Recording Configuration: This step is to define the recording configuration.
  16. Define Filter For Inspection Characteristics: This step is to define the Bill of Materials (BOM) and routing selection.
  17. Define Control Key In Operation: This step is to define the control key in operation.

Read more

Automatic Account Determination Process in SAP MM-FI (ECC / S4HANA)

This document is a detailed guide on the Automatic Account Determination Process in SAP MM-FI (ECC / S4HANA). Here’s a summary of the key points from the document:

  1. Integration with SAP MM and FI Module: The FI Module is linked with the MM Module because operations like Goods Receipt and Invoice Receipt directly impact the financial operation of the organization. Inventory postings update the G/L Accounts online in the background.
  2. Roles of Automatic Account Determination: In SAP MM, the procurement process involves costs that need to be paid to the vendor. Some configuration for account determination is done so that the system will automatically determine the correct G/L account that needs to be posted.
  3. Customizing: This involves several steps including:
    • Assigning the Company Code to Chart of Accounts
    • Setting the Valuation level (T-code OX14)
    • Grouping Together Valuation Areas
    • Defining Material type (T-code OMS2) and Valuation class
    • Defining Account Grouping for Movements Types
    • Configuring Automatic Postings
  4. Managing Message number no M8147 Account determination: This issue means that the system cannot update a G/L account for a transaction. You cannot post the transaction. This issue can occur in MIGO (goods receipt) and MI07 (when you post inventory difference in physical inventory). The solution is to use the OBYC t-code and go to the GR/IR clearing account (WRX).
  5. Table (T030) to get the details of OBYC: If you want to know transaction keys based on G/L Account or the G/L Accounts based on Transaction keys / valuation grouping code /Account modifier / chart of accounts, you can use two t-codes: SE11 (to display the structure of the tables (T030)) and SE16N (to see the content of table (T030)).

The document also provides several examples and simulations to illustrate the concepts and steps involved in the Automatic Account Determination Process.

Read more

Configuration of Automatic Batch Determination in SAP MM-IM

The pdf document Inventory Management Process in SAP is a continuation of the guide on how to manage inventory in the MM module of SAP, focusing on automatic batch determination (general overview and configuration steps). Here’s the summary of the sections covered:

  1. Automatic Batch Determination: This section explains the purpose of automatic batch determination in the logistics process, which is used for all types of goods movements from the warehouse to find batches that meet defined specifications.
  2. Configuration of Automatic Batch Determination in SAP:The document provides a detailed guide on how to configure SAP for automatic batch determination. Here are the steps:
    • Define Condition Tables (T-code: OMJJ): This process explains how to define condition tables in SAP, which consist of a number of fields. Among those fields, particular fields are selected and assigned to the condition table.
    • Access Sequences (T-code: OMCX): This process explains how to define access sequences in SAP. For each strategy type, there is a batch determination access sequence. The main function of the access sequence is to allow the strategy type to access the condition tables in a sequential manner.
    • Batch Strategy Types (T-code: OMCW): This process explains how to define batch strategy types in SAP. It is the procedure to select what type of criteria to be used during the batch determination process.
    • Batch Search Procedure (T-code: OMCY): This process explains how to define the batch search procedure in SAP. The batch search procedure defines how the search procedure is defined for the batches.
    • Batch Search Procedure Activation (T-code: OMCG): This process explains how to activate the batch search procedure in SAP. In this step, you can assign the search procedure for the particular Movement Type.
    • Import Standard SAP Characteristics (T-code: BMSM): This process explains how to import all the important standard SAP characteristics by copying them from the client 000. These characteristics are hard-coded in the ABAP functions.
    • Creation of a Class: This process explains how to create a class named as Z-CLASS1 of Class type “Batch (023)” and assign a standard SAP Characteristics “LOBM_VFDAT – Expiration date, shelf life” and LOBM_LWEDT- Date of Last Goods Receipt to this class.
    • Material Master Settings (T-code: MM01): This process explains how to add the class to it in the classification view, activate batch management in the purchasing view, and give data for remaining shelf life and total shelf life in the Plant storage1 view.
    • Create Sort Sequence in CU70: This process explains how to create a sort sequence in CU70 and assign your characteristic value to it. This step is repeated for both FEFO and FIFO methods.
    • Create Batch Search Strategy (T-code: MBC1): This process explains how to create a batch search strategy in SAP. This step involves entering the Strategy type ME01, Movement Type 201, a plant, and the material number, and adding Classification and Sort Rule.
  3. Test Functionality: This section provides examples of how to test the functionality of automatic batch determination in SAP, covering three methods: First Expired, First Out (FEFO), First In, First Out (FIFO), and Last In, First Out (LIFO). For each method, it explains the concept, the steps to perform a goods receipt (GR) and goods issue (GI) in SAP, and how the system determines the batch based on the method used.

The document concludes by providing screenshots of the SAP system for each step of the configuration and testing process.

Read more

SAP MM Inventory Management Guide: Goods Issue, Transfer Postings, Stock Transfers

The pdf document of Inventory Management Process SAP is a continuation of the guide on how to manage inventory in the MM module of SAP. Here’s the summary of the sections covered:

  1. Goods Issue (T-code: MIGO): This section explains the concept of goods issue, which means moving a stock out of inventory due to several reasons like withdrawing of material for sampling or returning the goods back to the vendor. It covers goods issue for scrapping (Movement type – 551), goods issue for cost center (Movement type – 201), and goods issue with reference to a reservation.
  2. Transfer Postings (T-code: MIGO): This section discusses various types of transfer postings, including transfer stock from Quality Inspection to Unrestricted Use (Movement type – 321), Material-to-Material Transfer (Movement type – 309), and Consignment to Warehouse (Movement type – 411k).
  3. Stock Transfer (T-code: MIGO, MMBE): This section explains the process of stock transfer, including one-step procedures between storage locations (Movement type – 311), two-step procedures between storage locations (Movement type – 313, 315), one-step procedure between plants (Movement type – 301), and two-step procedure between plants (Movement type – 303, 305).
  4. Stock Transport Order Without Delivery (T-code: ME21N, MIGO, MB5T): This section explains the process of stock transport order without delivery, which involves not only Inventory Management but also Purchasing in the receiving plant. The goods issue posting in Inventory Management is carried out without the involvement of Sales (SD).
  5. Stock Transport Order with Delivery (SD) (T-code: ME21N, VL10B, MIGO): This section explains the process of stock transport order with delivery, which involves the receiving plant entering a stock transport order with order type UB and item category U. The stock transport order is used to plan the movement.

Read more

SAP MM Inventory Management Guide: Movement Types, Goods Receipt and Reservation

This pdf document of Inventory Management Process In SAP is a guide on how to manage inventory in the MM module of SAP. Here’s the summary of the sections covered:

  1. Movement Types (T-code: OMJJ): This section explains the role of movement types in SAP, how to customize them, and provides examples of movement types.
  2. Goods Receipt (T-code: MIGO, ME23N): This section provides a guide on how to manage goods receipt in SAP, including receipt into unrestricted stock, quality inspection stock, and blocked stock. It also covers automatic creation of purchase orders during goods receipt, return delivery for goods receipt, entering a subsequent delivery, goods receipt without a purchase order or production order, and checking and calculating the Shelf Life Expiration Date (SLED) in SAP.
  3. Units of Measure in Inventory Management (T-code: MM02): This section discusses how you can purchase raw material with one unit of measure (e.g., kg) but maintain the same goods in your inventory management with another unit of measure (e.g., pc).
  4. Cancellation in MIGO (T-code: MIGO): This section provides an example of how to cancel a transaction in MIGO if a mistake was made during the entry of stock.
  5. Reservation (T-code: MIGO, MMBE): This section explains the concept of reservation in SAP, which is the process of blocking stock in advance so that it can be available at a particular point in time. It also covers goods issue with reference to a reservation.

Read more

SAP S/4HANA MM Guide – Flexible Workflow for Purchase Requisitions

The flexible workflow allows you to define condition-based workflows for approval processes. It supports both overall release (header-level approval) and release of purchase requisition items (item-level approval). Notifications about new work items can be sent to approvers via the SAP Fiori launchpad or email.

This pdf document is a 9-step guide on how to set up and use the flexible workflow for purchase requisitions in SAP S4HANA MM. Here’s a summary:

  1. Check Automatic Workflow Customizing: This step ensures that the automatic Customizing is active for the workflow functionality. It can be done in transaction SWU3 or in Customizing for SAP NetWeaver.
  2. Activate Flexible Workflows Scenario: This involves activating the workflow scenarios for a type of business document, such as a purchase requisition. It’s done in Customizing for SAP NetWeaver.
  3. Define Step Names and Decision Options in My Inbox: This step involves checking step names and decision options to be used in the app My Inbox. It’s done in Customizing for SAP NetWeaver.
  4. Define Visualization Metadata for My Inbox: This step ensures that the app My Inbox is available and set up for your approvers. It involves entering data in Customizing for Materials Management.
  5. Deactivate Event Type Linkages for SAP Business Workflows: This step involves deactivating workflows based on old workflow scenarios. It’s done in transaction Event Type Linkages (SWETYPV).
  6. Generalize Tasks and Activate Event Type Linkages for Flexible Workflow: This step ensures that the system events are linked to your workflow scenarios, and defines the potential agents of workflow tasks to clearly define the organizational responsibility for processing work items.
  7. Register Gateway Service for Value Helps: This step involves registering an OData service to enable the value help in the flexible workflow. It’s done in transaction Activate and Maintain Services /IWFND/MAINT_SERVICE.
  8. Adapt Flexible Workflow Settings: This step involves adapting the default settings, if required. By default, the flexible workflow is active for the document types NB (standard purchase requisition) and NBS.
  9. Adapt the Conditions under Which the Flexible Workflow is Restarted: This step involves selecting or deselecting the fields that exist in purchase requisitions. Whenever the values of these fields are updated in a purchase requisition, the system triggers a restart of the approval process.

The document provides detailed instructions and screenshots for each step. It’s intended for users who are setting up or managing the flexible workflow for purchase requisitions in SAP S4HANA MM.

Read more

SAP PP User Manual: Create and Confirm Production Order

This pdf document provides a guide on how to create new production orders and confirm them in the SAP Production Planning (SAP-PP) module.

The process allows users to create new production orders with respect to the material to be produced, the quantity, production schedules, and input material batches. The main purpose of creating a production order is to meet specific requirements on a particular day and to send this production to the shop floor with the desired quantity and input material on the scheduled date/time.

  • Procedural Steps: The document provides a step-by-step guide on how to create a production order (Transaction Code: CO01) and confirm a production order (Transaction Code: CO11n). It also provides instructions on how to handle errors during the confirmation of a production order using the COGI transaction.
  • Production Order Creation [Tcode CO01]: The user enters the material to be produced, the production plant, order type, and order quantity. The system automatically proposes the current date as the scheduled start date. After entering the required data, the production order is released automatically.
  • Production Order Confirmation [Tcode COGI]: The user enters the production order number, and the system proposes the ordered quantity. After confirming the production order, the system provides the number of successful and failed goods movements. Failed goods movements with errors need to be processed in the COGI transaction.
  • Error Handling During Production Order Confirmation: The document provides examples of how to handle errors during the confirmation of a production order. For example, if a material number is not maintained for a plant at a certain storage location, the user needs to maintain the material at the correct storage location to clear the error. The document concludes with a note that there should be no COGI records against the production order after all errors have been successfully handled.

Read more

PM Breakdown Maintenance Guide in SAP S/4HANA

In SAP S/4HANA PM, a breakdown maintenance is a type of corrective maintenance that is done when a machine or equipment stops working unexpectedly and needs to be fixed or replaced as soon as possible. It is also known as reactive maintenance. In SAP, the Breakdown Maintenance process generally consists of the following major activities:

  1. Raising of Breakdown Notification with correct priority by operation group to notify the responsible Maintenance department/ main work center. The priority can be E (emergent), A (urgent), B (important), S (shutdown), or O (opportunity), depending on the effect on generation and safety.
  2. Creating a breakdown maintenance order by the maintenance department if material, external service, or permit is needed to carry out the maintenance.
  3. Releasing the notification and the order by the maintenance department.
  4. Performing the maintenance work by the maintenance personnel and recording the actual data.
  5. Completing and closing the notification and the order by the maintenance department after verifying the results.
  6. Issuing work permits by operation department
  7. Performing Work Completion (WOCO), Notification Completion (NOCO) and Tehnical Completion (TECO) subsequently

In this guide, following list of PM transaction codes involved in breakdown maintenance (including permit procedures) are explained step-by-step with screenshots;

  • Create Breakdown Notification [IW21]
  • Receipt Of Breakdown Notification By Maintenance [IW22]
  • Permit(S) Applying By Maintenance [IW32]
  • Work Approval [WCLE]
  • Release Of Breakdown Order – By Maintenance – [IW32]
  • Time Confirmation Of Order Operations– By Maint. Dep’t [IW41]
  • Work Completion In The Breakdown Order – Permit Return [IW32]
  • Untagging/Normalisation Of Isolations – By Operations Dep’t [WCLE]

Read more

Master Data in SAP MM: Sample Guide for Healthcare Industry

The purpose of this manual is to provide a comprehensive guide for end-users on Material Master Management in SAP MM specifically tailored for the healthcare industry. Material Master Management plays a crucial role in managing the procurement, inventory, and supply chain processes for healthcare organizations. This manual is designed to help end-users understand the key steps for the maintenance of Material Master Management in SAP MM, and how they can effectively use it to streamline their day-to-day operations and control over their materials and inventory.
In this document you will also find specific material types created for healthcare industry which can be a reference if you are involved in SAP project implementation team.

Read more