Quality Notification is created to indicate defect in material at any stage of the work in the plant. Depends upon the details of the defects recorded the solution will be taken by the corresponding department or person responsible. This notification will also act as a record to take the evaluation to know the performance of the material in the various operation and to take right decision with the suppliers to dealt with it.

Overview:

Step1: Create a custom screen with required fields.

Step2: Configure QM Notification custom Iflow link in DMC using Manage web server.

Step3: Create data collection to collect the QM Notification number and save it.

Step4: Create a PPD to pass the values from custom screen to Iflow

Detailed steps:

Step1: Create a custom screen with required fields.

1. Custom screen should be created in Business studio.

2. Add the custom screen in DMC through manage service registry.

3. Create a button in any POD and assign this custom screen plugin to that button

Step2: Configure QM Notification custom Iflow link in DMC.

1. Create a manage web server with the custom Iflow link.

2. Configure web server in manage service registry and assign the schema.

Step3: Create data collection to collect the QM Notification number and save it.

1. Create a data collection group with parameter to collect the QM number created.

Step4: Create a PPD to pass the values from custom screen to Iflow

1. Select the created service in the production process designer and develop a PPD as per the requirement.

2. Open POD and select the SFC and operation.

3. Click QM notification button. QM pop up will open along with populated values.

4. Check all values are displayed and click submit. QM notification will create and display in the pop up.

5. Open SFC record. Select the SFC and click Data collection tab.

Conclusion:

The Quality Notification serves as a crucial record for identifying material defects during various stages of work in the plant. By documenting defects and involving the relevant departments or responsible individuals, it enables informed decision-making and facilitates communication with suppliers to address any issues effectively.

The post QM Notification Configuration from DMC to ERP appeared first on ERP Q&A.

I had the idea of posting this blog so that organizations or companies who perform inspections on their material can effectively analyses the process of their rejection process and make subsequent improvements in ensuring the rejection, lifting of material from storage locations and its visibility in the system.

In specific industry cases, Once the material is rejected and posted out of the system it is physically not lifted by the vendor due to certain reasons which means the tracking is not maintained and the physical location of the rejected material is not traceable in the system. (Location is only visible at plant level not Storage Location level when Mvt.103 (MIGO) is performed)

Organizations typically want to improve the TAT of their processes and the visibility of all the aspects are needed to make informed decisions on how TAT can be improved once date and time of certain actions are known.

After rejection material is stock out from plant level but in some cases, vendor is not lifting the rejected material at the time of MIGO-124 and rejected material physically place in warehouse and after that there is no visibility in SAP that where material is stored/kept and since how long.

Here we discuss goods receipt with movement type 103, receipt of goods in GR blocked stock. As we all know the use of such movement type will only give visibility at plant level and the stock is not yet made the company stock/company asset and it is still not valuated at that moment.

This causes a problem since in certain cases the rejected material is not lifted by the vendor and material is to be posted out through Mvt. type 124 (Return to vendor), but it is still physically present in the storage location or in the warehouse. Visibility of the location of the material is also not present in the system.

The main objective is to manage this process in a way that the detail tracking of material is conducted through SAP Quality Management and allow visibility of the material in the storage location so that when the vendor arrives to lift the material, we are aware of the location, date and time of the lifting in SAP.

Background of the process

With the suggested SAP Quality Management process below, we shall be able to accurately define each step of the rejection process with its subsequent placement of the rejected material and its corresponding date and time to its respective storage location and its intimations to the vendors via emails/rejection letters. Customized reports (Create Query reports) shall provide deeper analysis and statuses of the rejected material for better business decisions.

We shall discuss these steps in detail but first let’s lay down the basic steps that need to be performed to achieve what we want-

• Posting of material in GR Blocked stock through Mvt. type 103.
  
• Perform its Result Recording and record the defects in the case of rejection of the Inspection Lot with entry of storage location in additional info field.
  
• Perform UD against result recording with UD Codes R1 and R2 (Will discuss this further)
  
• Send Rejection Email/Rejection letter to Vendor through QM Notifications once for intimation of rejection and second time once the vendor arrives for lifting of material.
  
• Posting the rejected material (Return to Vendor) in SAP through QM-UD (if non serialized material) or MIGO-124 (Serialized Material)

Step by Step Guide:

Posting of Material through MIGO 103:

We shall first post the material which has an inspection plan and the relevant inspection type assigned in material master assigned to it in the SAP system so that its inspection lot is created, and the material is put into GR Blocked Stock for further processing.

After posting of the material the inspection lot of the material is generated created as shown below:

Result Recording of the Inspection Lot:

The result recording of the material is added in the system which will showcase any defects observed in the inspection lot. Since the material received during Mvt. 103 does not reflect any storage location.

A standard text field (Additional Info Field) is used here to record the storage location which will record the physical location of the material at the time of RR. As showcased below where storage location entry is made. This can be made visible in our reports later on.

Defects are to be entered in the RR by adding the defects as showcased below.

Entries of the Code group are added, and the defects are recorded to be used in RR. Notification can be activated through this window which will allow us to send the rejection remarks to the vendor once UD is performed.

Performing UD with code R1 to inform the vendor of decision.

Once the Result Recording has been performed, we shall now perform the Usage Decision of the Inspection Lot. For this step we need to have two more codes configured in the system for usage decision. R1 (Material Rejected but return pending) and R2 (Rejected Material Returned to vendor).

R1 is going to be used incase we reject the material, and we will send the notification to the vendor informing about the decision. This will keep the material in GR Blocked Stock and date and time of the decision will be recorded which can be viewed in copy of ZABAP report which will showcase the location and the UD result of the material thus giving us its visibility.

We shall first choose R1 in our UD code and head on over to the Inspection Lot stock where we shall propose to keep the material in the GR Blocked Stock state.

After all this is done, we shall send an email to the vendor informing them about the usage decision for this. Click on the “Go To” menu tab and select “Defect Structure” from the drop down.

A window will open that will showcase the defect overview window as showcased below.

Appropriate Defects are to be selected which will open a new notification window as shown below. After selecting the appropriate line item click on the notification button in the bottom right. Notification window will open which will house our option to send the intimation to the vendor about the results.

Fill out all the entries required to process the notification such as the reference number and the quantity that is being rejected as shown below.

An enhancement has been made in the action box window in the right which will trigger the functionality to send email to the vendor.

A popup will open which will allow to either preview the rejection email/letter or send it to vendor. The typical layout of the email intimation being sent to the vendor is shown below.

You can save the UD doc. without any entry in to be posted field (stock remains same in GR blocked stock).

After posting of UD system status will be change to UD ICCO SPRQ.

Performing UD with R2 once vendor arrives to pick rejected material.

At the time of vendor arrival to pick the material up. We change the UD code using T.code QA12 (Change with History) from R1 to R2 (Rejected Material Returned to Vendor). When you change a usage decision with history, the system creates a change document that contains the relevant fields of the inspection lot with the values before and after the change.

Once this is done. We follow the same steps for email intimation (As done for R1 UD code) as showcased above and then choose the send email to the vendor intimating them about the material being lifted from the storage site.

An email message of the following format will be sent to the vendor intimating them that the material has been lifted.

After the second email intimation has been sent to the vendor. We now have to return the material back to the vendor through UD. For this, System will allow to post the return delivery to vendor from UD transaction (If material is non serialized), but the system status will remain same as UD ICCO SPRQ.

A material document has been generated with movement type 124. (Returned to vendor)

Case for Serialized Material.

The procedure that has been showcased is for non- serialized material only since SAP QM does not allow to post material document of serialized material with movement type 124 through UD with companies using movement type 103 and 105 for good receipts (Refer to screenshot below)

To post return to vendor of serialized material we shall use MIGO transaction with movement type 124 to achieve the desired result.

The post Optimization of Rejected Material Process after Inspection appeared first on ERP Q&A.

Benefits of Change Record

Key Features

Fiori App Required

1. Global Process route Workbench
   
2. Myinbox
   
3. Manage Change Record / engineering Changes,
   
4. Manage Team and Responsibilities

Required configuration

1. Define Number Range for the change Record

Path : SPRO > Logistics General > PLM > Change Record > Basic Settings > Define Number Range Interval for Change Record

2. Define Object types

Path : SPRO > Logistics General > PLM > Change Record > Basic Settings > Define Object types

Note : The object types are predefined

3. Define Object Categories

Path : SPRO > Logistics General > PLM > Change Record > Basic Settings > Define Object Categories

Note: These are predefined Category

4. Define User Status

Path : SPRO > Logistics General > PLM > Change Record > User status > Define User Status

5. Define User Action

Path : SPRO > Logistics General > PLM > Change Record > User status > Define User Action

The User Action Text Defined appear on the front end screen of the Change Record

6. Define User Action Profile

Path : SPRO > Logistics General > PLM > Change Record > User status > Define User Status Profile

As seen in the above screenshot, conditions help to navigate to different status from the current status, as in this case the status is 10, so when the change record is in status 10, then it can be moved to either 10,30,15 manually or via background task.

7. Define Item Relevance

Path : SPRO > Logistics General > PLM > Change Record > Setting for engineering Changes > Define Item Relevance.

This item relevance is used for the Items mentioned in the change record as shown in the image below for each of the object types. The control whether the enable the display the field of change relevance is covered by the configuration Define Engineering Record Type Section in Image 18

8. Define Engineering Record types.

Path : SPRO > Logistics General > PLM > Change Record > Setting for engineering Changes > Define Engineering Record Types

The change number and the status profile defined are assigned to the change record type Z01.

The check “ProcStatus” is used to control whether the item processing status is required or not as shown in the below image

SAP recommends the use of Process route for the Engineering change’s so the Check box Proc Route is enable for the Change record type : Z01.

Para Check column is used to enable the check whether same Object is used parallelly in other change number which is open or in process

The Reference Object that will be used for the change record type are updated. You can create Multiple change record type having different Reference Object

Mapping of the Item Relevance with Refence object category is done in this node. As per the mapping only the relevant item relevance will be shown.

The Configuration in this Node decide, control at which user status the Change number is created in SAP and at which user status the change number created in SAP is marked as completed. The Change number created in SAP is seen at the header of the change record also via the cc03 transaction.

It is also possible to control whether the change number should be created with released key or without release key. The below parameter defined in the creation attribute decides whether the change number creation attribute, if its blank its “without release key” and if its set to 1 its ”Release Key”

it is possible to define the digital based on the User action as defined in Section 6

9. User Assignment to Receive Task

Transaction : PFTC

If you want to control the Work items from the change record to be displayed to specific set of People then assign the user by navigating to

Additional Data > Assignment > Maintain

if you want the workflow task to create workitem as per the user id mentioned in the task created for the process route then Change the attribute of the task to General task as shown above by clicking on the Attribute button.

10. Activate Event linkage

Transaction : PFTC

11. Enabling Service for MyInbox

This service is used to allow the processing of the work items generated, for the change Record.via the MyInbox App. if this service is not enabled you will be able to see the work items in the list of the Myinbox app but you cannot open / Process it

13. Define Activities for the Change Record Processing

Path : SPRO > Net weaver > Application Server > Basis Service > Records Management > Customization for Process Route > Create or change Activities and Activity Functions

Here all the Activities for the case management are defined but to filter out the relevant activities for the change record the below configuration is required, only after which you can the activities in the change record.

the above activity is required to change the status of the change record automatically based on the rules defined in the BRF+ application.

14. Define Activities for GOS Objects

Path : Spro > Logistics General > PLM > Change Record > Process route > Define Activities for GOS Objects for Process Route

Change Record Processing

1. Create Change Record

2. Fill the details in the Change Record

Add Objects to be changed via the change record

Add activities that needs to be performed for the change record. the task Can be performed Sequential, Parallel or in Background, for the sake of the Simplicity i have added the Agent for the task as a user there are other options that can be explored of, From HANA 2021, there is provision to update the Team as well which is created via the Fiori App : Manage Team and Responsibilities

the background task are not automatically added they are added as either a sequential task or parallel task, the task shown in the below image is to update the status of the change record Automatically based on the condition, which is explained further.

The task can also be added via the Template method. To Create Template Fiori App : Global Process Route Workbench is used

Template Created via the Global Process Route Workbench. The Task / Activity shown below are just for demonstration in this example are not in sync as per the status of the change record.

If there is further requirement which is almost certain. to have the template loaded automatically in the change record based on certain condition like record type, status etc, that can be done via the BRF+ Application.

The BRF + application and its functions need to be assigned in the configuration. Note: The BRF + application needs to be activated in order to have it working

BRF+ Application Creation and Assignment

Create a BRF+ Application and add a function to it by right clicking. Set the mode of the function to either functional mode or Functional or event mode.

Note: for the folks who are new to BRF+ or still not aware of the functionality. Context is the input part and result data object is the output part.

the translation of the data from the input to output is done via the expression. In the image below the Input conditions acts as a expression

Define the Context: its a structure with binding to DDIC

the output is defined as Element and has a DDIC Binding

Create a Decision table as a Top Expression, the inputs fields to the Decision table is from the context and the output is from the Results Data object.

Assign the BRF Application in the configuration Path

Path : SPRO > Logistics General > PLM > Change Record > Process Route > Define Template

Change Record Process Continuation.

Start the workflow in the change record.

the work item will be received in the my inbox App or in the SO01 Transaction. Complete the Task to move the change record to the next task as per the process route.

Change the status of the Change record. The status of the change record are as per the Section 6 ( User Action Profile )

if the request it to Update the Change record status based on the previous task decision that can be done via the BRF + Application. SAP has Predelivered standard task for the Changing the Changing status automatically based on the BRF+ Setup

Create Background Task

SPRO > Netweaver > application server > basis service > Records Management > customization for process route > Create or Change activity and activity type.

Create Background Service

Path > SPRO > Logistics General > PLM > Change record > Process route > Define Background Service

Now as per the above image the change number is not created yet for the change record, but if we see the configuration defined for the change Record Image 19,20, 21, We can see that the change number is created only once it reaches the status 40. Please refer the below image where the change record is updated with change number of attribute with release key.

Perform the changes via the change number and Release the change number. After the changes are performed, the change record is updated. Once the change reord reaches the status complete the change number created is also completed.

Refer the Configuration Section Engineering Record type : Image 19

The post Change Record in S4HANA – A New Look to ECR/ECO in S4HANA appeared first on ERP Q&A.

This blog will help people to understand the basics of new functionality added by SAP from S4H 2020 in the form of FIORI app for “Defect processing”. This functionality will help to record & process defects without creating QM Notification.

Defect processing was available in SAP QM since the functionality of Quality Notification, but from S4H 2020, it can be created and processed independently without creating quality notifications.

SAP has given Fiori applications to record, process & analyze the defect. Following are the three applications available:

1. Record Production Defect
   
2. Process Defect
   
3. Manage Defect

Configuration Requirement

From S4H 2020 onward new node of “Nonconformance Management” can be seen. One of the important task to be performed under this node is to maintain number range for following:

1. Problem Solving Process
   
2. Defect Recording
   
3. Task Processing

Config Path: Quality Management ->Nonconformance Management

Processing

To raise the defect, one need to login SAP Fiori Launchpad.

Once logged into the systems, as per available roles relevant application tiles can be seen.

• Record Production Defect App

To record the defect, click on “Record Production Defect” tile & system will give provision to enter details of the defects.

Provide necessary details in the tabs available, so that appropriate information can be captured in the defect for better resolution. Following are the tabs available:

Defect Info:

This tab gives provision to enter exact details of the defect. Here defect description, defect code, production order details, defective material, defect quantity, etc. can be entered.

Once these basic details are entered, Click on “Create” button to create defect in the system.

Task:

The tab “Task” is used to create tasks to be performed to overcome that defect.

Click on “Create” button to create new task and system will give provision to enter the details of the task with multiple tabs.

Now click on “Create” button to create the Task.

Attachment:

This tab gives provision to attach some evidence of the defect. Select appropriate document type from “Select Doc. Type to Upload” & select the document to be attached by clicking on “Upload” button.

Also, there is provision to attach the existing DMS documents to the defect for reference. To do so, click on “Assign Doc” button & select the required document number from the available list.

Once all these details are entered, click on “Set in Process” button, to process the defect. This will change the defect status from “Created” to “In process”.

• Process Defect App

Once clicked on tile “Process Defects”, system will show multiple filter option like Status, Category, Defect Code, Created On, etc. to filter the defects.

Provide necessary values in the filter if required & click on “Go” button or simply click on “Go” button. Once clicked, system will display the list of defects satisfying the criteria.

Click on the required defect to process it.

The tasks of defect can be processed from defect itself or app “Process Quality Task” can be used for the same.

Note:

It is always recommended to process the tasks from the app “Process Quality Task”, so that only authorized persons can process them. Also, usually task creator and processor are different, so the task processor will able to independently work on task without risk of modifying defect.

To process defect from Defect app, click on the Pencil icon in front of the task.

If required, provide the necessary notes under tab “Notes” & click on “Complete” button. Finally click on “Save” button. This will update the task status as “Completed”.

Do the same for all the task, as it’s mandatory to complete all the Task before closing the Defect.

Once all the tasks are closed, click on “Complete” button to complete the task & click on “Save”.

• Manage Defect App

The purpose of this app is to get defect reports in different format. There are multiple options available to view the report.

The report can be seen Defect code wise, Supplier wise, Plant wise, etc. in different format like Pie Chart, Line Chart, Donut Chart, etc.

Please find below some of the combinations:

• Defect code wise Stacked Column Chart

• Defect code wise Pie Chart

One can explore all the options by trying different combinations of “View by” & “Chart Type”.

Basic SAP Table Details for Defect

Although, the SAP has given new Fiori apps for Defect processing, the database tables used are existing only with modification in the field values.

Let’s have a look at some of the basic database tables used in the process.

• Defect Header

The data element used for Defect is “QMNUM” which is same for SAP Notification Number but with little difference. Here for defect, it is prefixed with “$” symbol e.g. if defect number is “1” in Fiori app, it will be saved in table as “$00000000001”. Defect category used here is “07” i.e. Production Defect.

QMFE is the table used to store Defect header details.

• Defect Task

The table used to store defect task is QMSM. For each task, system will create new sequential task number i.e. one task number cannot be seen in the two defects. Here also logic of “$” symbol is used to update the QMNUM field of table.

Link to Task & Defect is established with the help of field “DEFECTINTERNALID – Internal Defect ID”

In technical terms: QMFE-QMNUM = QMSM-DEFECTINTERNALID

The post Working with Defect Processing FIORI App SAP QM appeared first on ERP Q&A.

Overview of the C_TPLM40_65 Certification:

C_TPLM40_65, or the SAP Certified Application Associate – Quality Management with SAP ERP 6.0 EhP5, tests your basic knowledge regarding SAP Quality Management.

The C_TPLM40_65 certification also proves that the candidate possesses the basic overall knowledge within the consultant profile of the QM solutions and can use his knowledge practically in projects under the guidance of a senior consultant.

Level of the C_TPLM40_65 Certification:

The C_TPLM40_65 certification is suggested as an entry-level exam to familiarize consultants with the fundamentals of SAP Quality Management. Therefore, anyone with prior SAP knowledge can appear for the exam.

What Topics Are Covered under the C_TPLM40_65 Syllabus?

The C_TPLM40_65 exam covers the following topics-

• Sample Management
• Quality Certificates
• Quality Notifications
• Audit Management
• Configuration and Organization
• Integration of QM and MM
• Integration of QM with S&D and Service
• QM in Process Industries
• Implement & Configure Quality Inspection
• Implement & Configure Quality Planning
• Implement & Configure Quality Control
• Implement QM in Discrete Manufacturing

Preparation Strategy to Ace the C_TPLM40_65 Exam:

Learn about the Exam Structure:

The C_TPLM40_65 exam is 80 questions long, and you must face multiple-choice or multiple-answer-based questions to pass the exam. You must obtain 55% marks to pass the exam. If you are mentally aware of the exam structure, you will be able to face the exam in a smooth manner.

Stay Guaranteed about Taking the Exam:

If you want to put maximum effort into the exam preparation, you must be confirmed about taking the exam and taking registration works as the assurance. You might plan to take the C_TPLM40_65 exam and drop the plan later with other workloads or mood swings. But, once you register for the exam with Pearson Vue, your money gets involved by letting you become a bit serious about the exam.

Cover the C_TPLM40_65 Syllabus Topics:

Syllabus completion is the most important aspect of your preparation, be it an associate-level exam or higher level. Therefore, keep a focus on covering the syllabus topics from the core. While covering the syllabus, you won’t get much scope to skip any syllabus section. Therefore, try to cover all syllabus domains and memorize them for a long time through writing practice. The more knowledge you earn through study, the scope of using the knowledge for a consultant profile gets better.

Making Study Plan Helps Covering the Syllabus:

Proceed in the exam preparation with a study schedule to stay stress-free. Don’t get confused in the pattern of deciding the syllabus topics while you sit studying. Better note down the topics, and chalk out what you want to study on a particular day. A study plan helps you to stay productive throughout the preparation. You won’t be wasting time anymore; following the schedule daily will keep you organized.

Broaden Your Knowledge with Sample Questions:

Syllabus completion is your primary task, but that should not become your last task. Once you get knowledge from the syllabus domain, your next task should be broadening your knowledge with other materials. Multiple valuable sample questions are available over the internet, and it helps you to explore your knowledge level.

Enroll for Practice Tests:

Enrolling for the C_TPLM40_65 practice test exams would help you earn clarity on your preparation level. The practice test exams wo0uld provide you with a real exam-like experience, and you will get insights into your strength and weaknesses. If you work on your flaws, you can score better in the future.

What Is SAP Quality Management?

SAP Quality Management (QM) has been created as a feature of SAP ERP Central Component (ECC), which is the main ERP product from SAP. Quality Management is designed to support organizations in the process of implementing and executing quality control processes.

Why There Is A Need for SAP Quality Management?

Due to the rising competitive pressure and the constant development of different technologies, the quality demands of a company are continuously increasing. The growing customer expectations allow organizations to aim for a continuous improvement of their processes, whether in the software or hardware.

C_THR81_2111: Have You Tried the SAP SuccessFactors Employee Central Mock Tests to Earn the Certification?

Suppose an organization wants to stay competitive in the market. In that case, the quality of its products and services must both reach a constant high level and be continuously and systematically promoted in all operational stages. At this stage, the use of Quality Management Software is needed to offer the necessary functions to ensure quality throughout the complete life cycle.

Benefits Organizations Earn by Using SAP Quality Management:

• Get higher customer satisfaction due to better product quality.
• Monitor supplier and customer returns by implementing quality control measures in SAP QM quality notifications.
• Full integration in procurement and production offers continuous quality assurance.
• Get certificates of quality as part of the product documentation. It confirms the quality of the products manufactured and the technologies used.
• Risk minimization, failure analysis, and stability studies can help reduce failures and delays.
• Get activation of required corrective actions by SAP QM system’s automatic quality notifications.
• Have total control of all business methods due to smooth integration of quality management methods and measures (SAP QM) into all other business areas and processes including R&D, HR, production and logistics,  finance and controlling, sales and marketing, and others.
• Offer support for the company’s ongoing and continuous quality assurance by integrating the quality methods of individual departments and areas into an overall corporate QM system.

Bottom Line:

Through the C_TPLM40_65 certification preparation, you learn more about SAP Quality Management. Implement it in the future by earning the certification and proving your qualities to potential employers.

The post C_TPLM40_65 Quality Management with SAP ERP 6.0 EHP5: Have You Started Solving Practice Test Questions? appeared first on ERP Q&A.

1. Delete all the unnecessary demand and run MRP. So that all the open planned orders will be deleted from the system.
   
2. Finish all the production bookings in MFBF, so that there’s no more cancellation. Ensure all the reprocessing records are processed successfully that are lying in MF47(if any).
   
3. Coordinate with costing team to process Overhead calculation/ WIP calculation/ Variance calculation & Settlement of the product cost collectors.
   
4. Set the deletion flag for the product cost collector in KKF6N once the cost balance is zero.
   
5. Uncheck the ‘REM Allowed’ indicator in the production version and Save the production version.
   
6. Select the required production version and delete.
   
7. Remove the REM profile, REM allowed indicator, and Action control from the material master for which REM to Discrete conversion is required.

Steps:

1. C223– Not able to delete the production version.

2. MF47– Clear the COGI/ Post processing error.

3. MF45– Clear reprocessing components: Rep.Manuf.(Cross checking)

Order settlement process

4. KKAS– WIP Calculation

Maintain below input data and click execute.

5. KKS6– Variance calculation.

Maintain below input data and click execute.

6. KK87– Actual settlement- product cost collector.

Maintain below input data and click execute.

Master data changes

7. KKF6N change – Product cost collector.

Edit> Deletion flag> Set and Save.

8. C223 or MM02- MRP4 Production version.

Uncheck Rem allowed, remove production line, click continue and save.

9. Select the relevant production version, click the delete button, and save.

10. MM02– MRP4 View

Uncheck Rep mfg, remove rem profile, remove action control, and save.

The post Convert Repetitive Manufacturing into Discrete Manufacturing Process appeared first on ERP Q&A.

Business process overview: Once goods receipt is posted in SAP if the material/article master has inspection activated, then SAP will create an inspection lot to be processed for that PO line item. If material is found defective and I need to rework it, user will log defects and a quality notification can be created automatically with defects found after user saves inspection results. Coordinator will have the item reworked and then assign to vendor compliance to charge vendor for defective inventory, after corrective action has taken place. I will bill supplier via SD debit memo.

Problem: Per standard practice I can activate QM order. This talks to Controlling cost collector for non-conformities (Issues identified during GR). Problem with this is I am not able to generate an invoice or debit memo to bill suppliers. Therefore, I will go via SD and create a debit memo and post it to supplier’s customer account.

Currently if I have a quality notification I cannot create a sales document (DR – Debit memo) as there is additional configuration that SAP is looking for.

SAP output sales order creation is not possible for this notification type. SAP is looking into table TQ80. SAP requires a value against notification in table TQ80-SDAUART. Since this is blank, I will get below message.

SAP is checking table TQ80-SDAUART. Per below screen shot there is no sales document assigned to quality notification. This blocks me from integrating with SD.

Configuration requirements:

1. Quality Notification type (I will configure a new notification type just so I have standard to always reference back to).

i. I can use exiting notification F2 and only do following configurations:

• Step 2 in config
  
• Step 4 in config
  
• Step 5 in config

2. Quality Notification action box (Optional) I will skip this config
3. Inspection type (assignment of notification type to inspection type)

Master Data requirements:

1. Material/Article master – must exist for sales area
   
2. Vendor master – Business partner needs to exist for following roles:

i. FLVN00
ii. FLVN01
iii. FLCU00
iv. FLCU01

• For GR/IR clearing vendor must be assigned to customer and customer to vendor in general data
  
• Clearing flag must be set in the payment transaction views of supplier and customer accounting roles. Also, payment method needs to be same for both roles. FLCU00 and FLVN00

Below steps are needed to configure Quality Notification Type in SAP

Step 1 – Create/Define Notification type

1.1 – Path- QCC0 –> Quality Notification –> Notification Creation –> Notification Type –> Define Notification type.

Select F2 and click on copy as I will create my own notification type.

My Notification type will be Z9. Notification origin should be “Q2 Complain against vendor”. Assign number range. Save –> Back.

1.2 – Path- QCC0 –> Quality Notification –> Notification Creation –> Notification Type –> Define Number Ranges. Define number ranges and the assign to notification type refer to 1.1

1.3 – Path- QCC0 –> Quality Notification –> Notification Creation –> Notification Type –> Define Screen Templates.

To copy from existing notification, click on select “Copy Screen Areas from the Standard System”.

Double click on Define Screen Areas and Tabs. Select notification type Z9 and double click on “Notification Header: Screen areas”. Maintain same values as F2 notification type and save back.

Now I need to define initial screens of quality notification.

I can test if all the screens I want to copy are ok by leaving X in test once ok remove X and execute. Save Back.

Step 2 – Define and Assign Partner determination

2.1 – Path- QCC0 –> Quality Notification –> Notification Creation –> Partners –> Define Partner Determination Procedure –> Define Partner Determination Procedure

Select quality management click on change Partner

Select Q2 and click on copy as

Select name for description than save output to copy all entries.

Select Z9 notification type and double click on “Functions in determination procedure”

Make sure sold to Party, Supplier, and Coordinator Partner Functions are flagged so I will not forget to maintain value during notification creation. If any other is required should be maintained here than Save and back.

Double click on “Assign partner functions to notification type”

I will select my notification type and click on details

Assign sold to party and Supplier partner functions and all the others that are required in appropriate field. Since I mentioned in the partner functions that Sold to party, Supplier, and Coordinator are required, I need to mention those here so SAP can determine and require user to input partners (Value in partner functions). Now save and back.

Step 3 – Define Priorities

3.1 – Path- QCC0 –> Quality Notification –> Notification Processing –> Response Control –> Define Priorities –> Priority type for Notification type

I will select my Notification type Z9 and click on details

Assign priority type QM to notification. Save and Back

Step 4 – Assign Notification type to Inspection type

Now assign notification type to Inspection type to automatically create notification during results recording. QCC0 –> Quality Inspection –> Inspection lot Creation –> Maintain inspection types. Since I will be doing charge back against goods receipt, I’ll select 01 inspection type (Goods Receipt Insp. for Purchase Order) click on details and I will maintain my newly configured notification type. Save and back

Step 5 – Assign Sales order type to Quality Notification type

To assign sales order type, I must make the notification type as customer facing. Otherwise, I won’t be able to see and maintain any value against notification type. Currently I don’t see it per below snapshot of Tcode – OIM9 (Path: SPRO –> Plant Maintenance and Customer Service –> Maintenance and Service Processing –> Maintenance and Service Notifications –> Notification Creation –> Notification Types –> Define Order Types and Special Notification Parameters).

Configuration – B:

5.1 – Path- QCC0 –> Quality Notification –> Notification Creation –> Notification Type –> Define Notification type. Select Z9 and click on details.

Change Notification origin to Q1 Customer Complaint and Save and back.

5.2 – Path SPRO –> Plant Maintenance and Customer Service –> Maintenance and Service Processing –> Maintenance and Service Notifications –> Notification Creation –> Notification Types –> Define Order Types and Special Notification Parameters (tcode – OIM9). Now my notification Z9 will be visible I will select and click on detail

Assign a sales document type (any sales document). I will assign DR (Debit Memo) as this is the one I will be utilizing this process for now Save and back.

5.3 – Now I need to change the notification back to complaint against vendor, as my notifications will be created once GR is posted against PO/inbound delivery. Go back to path QCC0 –> Quality Notification –> Notification Creation –> Notification Type –> Define Notification type. Select Z9 and click on details. I will change notification origin to Q2 Complaint against vendor and save.

5.4 – Table TQ80 now has value DR that I just assigned.

Step 6 – Test:

6.1 now I will use notification 200000049 I created earlier to test if SAP allows me to create a debit memo. In QM02 I will input my notification number and enter.

6.2 Now to create a debit memo click on More –> Notification –> Functions –> Sales Order –> Create Selection of order type

6.3 Enter sales org. distribution channel and division than click on ok or enter.

6.4 I will select order type DR by double clinking for debit memo. SAP will allow to create any sales document if the Material/Article master has appropriate sales area as well as vendor.

6.5 SAP will open VA01 transaction to allow me to create a debit memo. I will enter article with issues, quantity, and order reason. For pricing, please reach out to your SD consultant. To do billing against debit memo I need to remove billing block. Now go back and in notification click on save. SAP output sales order has been created.

6.6 Now go to back to Change notification QM02 document flow. More –> Extras –> Notification Documents –> Document Flow–> List.

SAP will give show all the documents that were created with reference to this notification.

6.7 Now do billing in VF01 and save. Let’s go back to Quality notification document flow. I can double click and view debit memo request or any of the documents mentioned here.

The post Charge vendors for non-compliance or issues identified during GR via SD appeared first on ERP Q&A.

There are 2 approaches considered in this blog:

1. Restrict GR creation, if certificate is missing.
   
2. Allow GR creation, if certificate is missing.

Pre-requisites

To achieve this, QM control key with “Cert required” checkbox active is required. SAP Standard control key “0005 – Delivery release, certificate” is used here.

Config Path : Quality Management -> QM in procurement -> Define Control Key

Configuration Required

One of the important configuration required is Certificate type. Certificate type will decide how system should behave in case of receipt or missing of certificate. Setting “Control without certif” is a key parameter which will decide the behavior at the time of GR.

The certificate type “QCGR” used here, is a custom certificate type.

Config Path : Quality Management -> QM in procurement -> Define Keys for Certificate Processing -> Define Certificate Types

Below are the options available under “Control without certi.” option. In this document below indicator are used:

“C Without lot: Error message, with lot: Status”

“D Without lot: Error message, with lot: Error message”

Master Data

Following are the master data used in the process:

1. QM View of Material Master (MM01/02/03).
   
2. Quality Info Record (QI01/02/03), applicable as per the control key used.

1. QM View of Material Master

In QM view, maintain Procurement Data & Activate inspection type ’01’, as shown in the images below:

2. Quality Info Record

As per standard control key “0005” settings, quality info record is mandatory.

Make sure under “Insp. Control => 1 Inspection Active Regardless of Supplier Certification” is active as inspection lot to be created in the process & “Release Until have future date” (as per business requirement).

Note: Quality Info Record creation can be excluded, if “Release Required” indicator of the QM Control key is unchecked.

Processing

Scenario 1 : Restrict GR creation, if certificate is missing.

For this scenario, “Control without certif => D Without lot: Error message, with lot: Error Message” is applicable in certificate profile.

A. GR Creation

Under tab “Purchase Order Data“, it is mandatory to select value in “Cert. Enclosed?” else system will not allow to create GR.

If Selected ‘No’, System will not allow GR creation, as it is selected to display error message in certificate type config.

In this case, GR can be created only if ‘Cert. enclosed’ selected ‘Yes’.

GR creation is successful. Also, system will create inspection lot with status “CROK”.

Scenario 2 : Allow GR creation, if certificate missing.

For this scenario “Control without certif => C Without lot: Error message, with lot: Status” will be applicable.

A. GR Creation

At the time of GR creation,, system will ask for confirmation of certificate receipt & based on the input given, system will update the necessary status for inspection lot.

i. Cert. Enclosed = Yes.

In this case, system will allow the GR creation & inspection lot will have status ‘CROK‘ i.e. ‘Certificate receipt confirmed‘ & usage decision can be taken.

a. GR Creation

b. Inspection Lot Processing

ii. Cert. Enclosed = No.

In this case, system will allow the GR creation but the inspection lot will be created with status ‘CTCM‘ i.e. Certificate conformation missing & usage decision can’t be taken till status changed to ‘CROK‘.

a. GR Creation

b. Inspection Lot Processing

So, in this case system will not allow to post the UD, till the ‘CROK’ status is updated to the inspection lot.

c. Confirming Receipt of Certificate

As the inspection lot is in CTCM status, system will not allow to take the UD. To perform the UD, it’s required to tell system that certificate is received. This can be done in 2 ways:

• From Inspection Lot

Use below path:

Inspection Lot Number => Edit => Confirm Receipt of Certificate =>Save

• From Quality certificates

There are two transactions which can be used for this i.e. QC52 and QC55, but the process to change the status remains the same.

QC52: This transaction is used for single record processing

QC55: This transaction is used for work list processing

Here, transaction QC55 is used.

Based on the input parameter, system will display the record/s.

Now, select the record & click on button “Change Certificate Data“.

In field “Cert. status“, there are multiple options available. Select status as “2 Certificate received” to update inspection lot status as CROK & Save.

Now, system has updated inspection lot status to CROK & usage decision can be taken for the same.

The post Quality Certificate Check at Goods Receipt appeared first on ERP Q&A.

In this example, Area of Triangle is calculated. The formula for Area of Triangle is:

Area of Triangle = 1/2 ( Base * Height )

This blog is written on the assumption that one is well aware of MIC & it’s control indicators, sampling procedures & inspections plan.

Pre-requisites

Following are the Pre-requisites:

1. Sampling procedure( if sampling procedure is selected at MIC level) T-Code : QDV1
   
2. QM should be active for the material

Master Data

In this process Master Inspection Characteristic & Inspection plan are the key master data. Here we will be needing 3 MIC’s one for each Length, Height, Area and an inspection plan to formulate the MIC.

• Master Inspection Characteristic:

a. Length:

Create an MIC with following control indicators. The control indicator for Type i.e. tolerance limit are optional and can be kept blank if required.

It is mandatory to keep the Formula radio button at “No Formula” as this is a regular MIC.

b. Height

Second MIC we need to create is Height. This MIC is also like previous MIC & Formula indicator should be “No Formula” only.

c. Area

This MIC is going to be little different, as this is the MIC which is going to be formulated.

Here, it is mandatory to select Formula indicator as ” Calc. charc.” i.e. Calculated Characteristic. If this indicator is selected, then only the system will allow to enter the formula.

• Inspection Plan:

After MIC, inspection plan is next master data which needs to be maintained for this process. Here we are assigning the MIC Length at 0010 number and Height at 0020.

Now as soon as we add Calculated characteristic, system will immediately ask to provide the formula for calculation.

The area highlighted in the above image is the place where formula needs to be entered. To enter the formula, any one of the systems defined formula parameters should be used, as per the requirement for each MIC. In this example, Formula parameter ‘C0‘ is used.

While entering the formula make a note that, MIC can’t be directly used in formula. Instead of that, the position number, where MIC is assigned should be used. In this case, Length is assigned at position 0010 & Height at 0020. So, the formula will be:

Area = 1/2*(C00010 * C00020)

Once, all the MICs are assigned & formula is entered, save the Inspection Plan.

Inspection Processing

Once the inspection lot for the material is created, result recording can be done. To do the result recording, go to transaction QE51N. On opening the inspection lot, it can be noticed that, for calculated characteristic, system will not allow to enter the result.

Enter values in “Result” field of Length & Height. After entering the result make sure both the MIC are Valuated i.e. status 3, else system will not allow to perform calculation. In the image below, MIC are in Close status i.e. status 5 as this is a good practice to close the MIC.

Now, select the “Area of Triangle” MIC & click on “Evaluate Formula” button.

As soon as “Evaluate Formula” button is clicked, system will perform the calculation and display the result.

Now, valuate and close the result recording.

The post Working with Formula Based / Calculated MIC (Master Inspection Characteristics) appeared first on ERP Q&A.

Pre-requisites

Following are the pre-requisites:

1. Activity type should be available (T-Code: KL01)
   
2. Activity rates should be maintained (T-Code: KP26)
   
3. QM should be active for the material & Inspection setup is maintained (T-code: MM01/MM02)

Note: For point 1 & 2, one can take help of controlling consultant.

Introduction

This blog will guide you to implement Cost of Quality Inspection in SAP QM. As a business requirement you might come across capturing cost involve in quality inspection. I’ve tried to give detailed information how the process needs to be implemented. You can take reference of this blog to implement process as per your requirement.

Master Data

Following are the master data required throughout the process:

• Creating & assigning QM order (QK04): This is very important step in entire process. You need to create QM order type before implementing the process & same should be assigned to the material. These both the activities can be performed by T-Code QK04. Take help of your controlling consultant to get required values of Cost Centre / Profit Centre to execute the transaction.

Order Type QN01 is used for the process.

Now select the check box & click on “Assign QM order” button.

Once you do that you will find “Assign” status updated to the record.

Now, click on “Save” button. After Save, order will get created & assigned to the material. The assigned order can be checked in “Inspection Setup” by using T-code MM03.

• Work Centre (CRQ1): Create a work center with T-Code CRQ1 & assign activity type to it. You can use formula SAP001 for the calculation purpose.

• Inspection Plan (QP01): Create inspection plan using work center created in previous step. As soon as you enter the work center system fetches the Activity type. Here I’ve used control key ‘QM04′ as I wanted pop-up for activity confirmation on completion of result recording. You can also enter planned time required for the operation completion.

Now assign MIC (Master Inspection Characteristics) to the operations as per your requirement & Save the inspection Plan.

Activity Confirmation

Once the inspection lot is generated, to confirm the Activity, you need to perform result recording in T-Code QE51N.

Once you done with result recording, click on “Save” button & system will give a pop-up to enter the time taken to perform the operation. Whatever time you enter here will be considered for calculation of the cost.

Provide time you have spent to perform the activity & click on ‘Continue’ button.

Now, repeat this process for all the remaining operations and confirm the activities.

Displaying Cost Report

To get the cost report you can go to transaction QA32 or QA13. Enter inspection lot number and follow below path:

Extras -> Costs -> Activity Confirmation

In this report you will get operation wise cost of the inspection.

The post Cost of Quality Inspection appeared first on ERP Q&A.