Hello!
This blog is about Frequently Asked Questions in Quality Management and aims to collect the main information of our threads in QM and publish it in one single document, so the information can be easily find and people can search for a specific subject.
This document will be updated when new important threads appears.
If you have a suggestion of a good thread that are out of the list please give some feedback and I can add it here.
Following the idea of compilation of notes (Often used QM notes) and KBAs (5 Most viewed KBAs from Quality Management), this one is for ranking the 10 most viewed notes from Quality Management (from the year and from the month).
I hope this can help to solve your issues quickly 
10 Most viewed Notes from 2015
1.543 Views - 175842 - Inspection lot: Reversal of goods movements from usage decision
980 Views - 48815 - Checking possible inconsistencies between MM and QM
515 Views -33924 - Reversing usage decisions
302 Views -208271 - Sending e-mail from notification print control
260 Views - 332626 - Inspection plan: Restoration after deletion
207 Views -1972228 - Adapting the EWM interface in QM
204 Views - 1970287 - FAQ about the Usage Decision
168 Views -736920 - Maintainance of selected sets requires transport request
160 Views -370191 - Notification worklist: User-defined fields in message list
*Until 09.06.2015
Hi all,
I checked all the threads, i found that there are many threads for recurring inspection, 09 inspection type, use of 09 inspection type etc. that's why i have decided to write this blog, which will help us to know how to handle Recurring Inspection. This Blog or Process I am writing as per my knowledge, forgive me if something is missing.
Step by step process is given below
1. For Recurring inspection we required to activate Batch Management. Go To " OMCT " T-code and set batch level as per your requirement. system gives you facility to activate batches at plant level, Material level and client level for a material.
2. Activate Batch Status Management and give number range for it.
3. Create Material Master. For Example we have material master having number "81". in Plant data / Storage 1 activate batch management. Give Minimum Remaining shelf life Days (this days system will check when every you are doing GRN system will ask date of Manufacturing and with that date system will check remaining shelf life of material, and that date system will check with remaining shelf life days) also give total shelf life in same tab of Material.
4. In Quality Management tab activate inspection type 01 and 09 and give inspection interval in Days. Inspection interval is required to put material in block stock and generate Inspection lot with inspection type 09 before these many days.
5.now first time material will be purchased with normal purchase route. such as PR --- PO --- GR (at the time of GR system will ask date of manufacturing and batch will be generated as per configuration) --- Inspection lot gets generated with inspection type 01 ----- Result recording ---- Usage decision --- Unrestricted stock.
6. To check the Shelf life and batch go to MSC2N and check status of material (it will show in unrestricted) as material is under shelf life. now go to QA05 and set program in the background. or we can run QA07 every day to check deadline monitoring of Batches.
7. Now consider we have date of manufacturing as - 05.02.2015 now SLED/BBD of that material is 25.03.2015. now run QA07 front end or system will go for QA05 run in the background. select To inspection stock at lot creation and execute it.
8. System will generate inspection stock by posting that material to Inspection stock. If you go to check status of batch you will see that batch status is showing as restricted.
9. Go to QA32, put inspection type 09 and execute it. system will show lot created with 09 inspection type. Go for Result recording and UD. at the time of UD if you find that we can extend useful life of material then edit date in Inspection lot and save it.
10. System will calculate next inspection date and we can see batch status as Unrestricted.
These are the steps for Recurring inspection.
Regards,
Chaitanya
Objective
This FAQ provide answers to repeated asked questions regarding a new functionality: Assigned Objects in Quality Notification.
Technical Name of the Business Function: EHP 4
OPS_QM_NOTIFICATION and OPS_QM_EXTENSIONS
What is Assigned Objects in Quality Notification?
You can assign multiple objects (batches, serial numbers..) to a notification at ITEM LEVEL. This enables you better document problems or errors.
How can I activate Assigned Objects in Quality Notification?
Please make sure that you have activated the EHP4 with business function OPS_QM_NOTIFICATION and all its dependencies e.g. EA-PLM and OPS_QM_EXTENSIONS.
You would see that there should be a separate tab in Item level for the assigned objects.
Please go to customization below to add the new tab. The screen area number is 840.
QM > Quality notification> 'Overview of notification type'
During results recording does it generate a single notification for all batches/serial numbers?
No, the functionality Assigned Objects is not integrated with defect recording, this is missing functionality.
How can I select and import multiple batch numbers to the Quality Notification?
You have two options:
- You can enter ranges:
When you enter a range (such as 1 - 5), the system adopts all batches and/or serial numbers where the key is between 1 and 5 as assigned objects in the notification item.
- You can enter generic values:
When you enter a range (such as 5 * ), the system adopts all batches and/or serial numbers where the key is starts with 5 as assigned objects in the notification item.
Where can I find more information about Assigned Objects?
You can find in transaction SFW5 the prerequisites of activation of business function OPS_QM_NOTIFICATION using button 'Dependencies' and a detailed documentation and release information using the correspondent buttons next to the business function.
If you have more doubts about this topic, please comment and maybe I can help you
I'm listing the QM documents I find useful in the SCN space. Will try to update it regularly.
How to find the suitable notes/KBAs
Frequently Asked Questions - FAQ QM
10 Most viewed Notes from Quality Management
5 Most viewed KBAs from Quality Management
Useful Customization Transactions for SAP Quality Management (QM) Module
How to make field as input,required,display only and hidden.
Quality Control of Geochemical Samples in Mining Industry
QM processes in Oil and Gas Industry- Feedback
QM processes in Oil and Gas Industry Part 2
Cutover Stock Migration with QM approach form As-Is to To-Be system
Customer issue management Via QM
Key Quality Management Configuration for Integration with Other Logistic Modules
Source Inspection Through Internet Results Recording
Vendor-end Quality Inspection Process
Quality Calculation in Vendor Evaluation (MM) - SAP
Calibration process mapping in SAP
DIGITAL SIGNATURE WITH SIGNATURE STRATEGY—SIMPLE GUIDE
Inspections using Multiple Specification
Inspection with batch classification
QM/Characteristics/Specifications/Classification – Blog 1
QM/Characteristics/Specifications/Classification – Blog 2
QM/Characteristics/Specifications/Classification – Blog 3
Manufacturer Part Profile in QM
Linking MIC to Class Characteristic
SAP QM Master Inspection Characteristic Architectures
Control indicators in QPMK and storage in field QPMK-STEUERKZ
Physical Samples Management in SAP QM
Recurring Inspection process with Batch
Inspection Lot Origin (Types) for Various Material Movement Types
Deactivating Inspection lot creation form MvT 107 without impacting the functionality for MvT 109
Inspection after Goods Receipt for Production Order
In-process inspection in Discrete Manufacturing
Audit Inspection (Inspection Type 07)
Calculation of Standard deviation, Cp & Cpk in SPC
Inspection Points: Key settings and Usage
Control Charts and Process Control in SAP, a White Paper By Shashank Shekhar, Deloitte Consulting
Reversal of Usage Decision and Stock Posting of Inspection Lot
Stock Posting during UD, of Non-QI stock
Dynamic Modification of Inspection Scope, a White Paper By Shashank Shekhar, Deloitte Consulting LLP
Basic Steps to Create Dymanic Modification Rule
FAQ: Assigned Objects in Quality Notification
Use of assigned object functionality in QN
User-fields in Catalog Tabs of Notifications - QQMA0008,10,11 and 12
User-Fields in QM and PM/CS Notifications : Screen-Exit QQMA0001
COA Programs - Why are they being changed?
DMS- How to Store documents in a Remotely located system Via SAP
Basic steps of report generation by query with example and scenario
If you want to learn more about QM, you may want to follow the following experts:
You can also find more useful documents in the QM WIKI page:
Product Lifecycle Management (PLM)
If you are also interested in PP(Production Planning), have a look at the following post:
Hi,I want to share my experience of implementing calibration process in SAP.we have use SAP MM,SAP QM and SAP PM module for mapping required scenario.
Business Scenario :Business has to do calibration of test equipments on periodic basis,calibration of few equipment is inhouse and for few equipment it will be done by external vendor.after calibration test equipment location details,calibration date are updated in document called history card.history card consist of unique serial number which is also label on test equipments.schedule of test equipment calibration is maintain manually.Quality control team has to review documents regularly to know Test equipments pending for Calibration.
Challenges during SAP Implementation :
1.Uploading of existing Test Equipments in SAP system
2.Capturing history of each and every Test Equipment with Calibration status,Last Calibration date,Procurement details,Location details.
3.Automatic reminder for Test Equipment Calibration.
4.Capturing Calibration Certificate.
5.Identify Test Equipments at Vendor Locations.
SAP Implementation
Steps we followed for mapping calibration process in SAP are as below :
Master data creation:
1.Identified Test equipments with common attributes and created unique material code for same with serial number profile.
2.serial number profile profile is created in such way that Equipment number and Serial number will be same
3.Physical stock of Test Equipment are noted in excel sheet.
4.Test Equipment stock upload done in SAP using initial stock movement 561.
5.Test Equipment at vendor location uploaded in system using initial stock movement 561-O.
6.Attributes required for Calibration check are created in SAP as Master Inspection Characteristics (MIC).
7.Test Equipment with common check list are identified and group task prepared for such equipment with Master Inspection Characteristics
8.For special equipments Equipment task list is prepared with MIC.
9.Maintenance Plan/Calibration Plan created with frequency of calibration period ie.monthly,half yearly or yearly.
10.Scheduling of maintenance plan (IP24) as background job.
Calibration order execution :
1.Calibration order get generated in system automatically base of calibration(IW39).
2.Calibration order are review and release for Calibration operation.
3.On release of order,In case of Inhouse Calibration,Inspection lot will get generated,Quality Inspector can perform calibration and update result in system against Inspection lot ( QA32 ).after completion of operation,operation confirmation was done.Calibration order status updated as completed.
4.In case of external calibration,Purchase requisition generated is converted into Purchase order buy purchasing,Test equipment issue (541) to vendor against PO and during good receipt Inspection lot will get generated,Inspection can be done before taking calibrated instrument into unrestricted stock, confirmation of external calibration operation and closing of calibration order will be done.
5.Calibration certificate are scanned and attached in equipment master using document Management system.
Reports
1.History of Test Equipment Captured from Equipment Master,Serial number history option (IE03).
2.Calibration orders list with status ( IW39 ).
Advantages of SAP Implementation:
1.No need to maintain history card,equipment history captured through Equipment master
2.Test Equipment pending for Calibration easily available (IW39)
3.Repeatation of work reduced
4.Tracebility of equipment is become easy.
5.Real time data available for Quality Control team.
6.Cost of Calibration can be captured.
I hoped above mention scenario will help you.
Thanks.
Hi,I would like to share one of quality inspection scenario I have mapped.
Business Scenario : Business involved in Panel manufacturing process with MTO scenario,where panel components are supplied to subcontractor and after completion of assembly at subcontractor end,subcontractor inform to buyer for Quality Inspection,Buyer inform to Quality engineer that assembly is ready for quality inspection,after completion of quality inspection at vendor location.Quality engineer give clearance to subcontractor for delivery of goods at factory.Quality report are prepared manually and informed to buyer and store manager.on receipt of assembly at factory,Final Inspection of assembly is completed.
Challenges in current process :
1.Defect occur at vendor end inspection can not be capture.
2.Reason for defect happend during inspection not available.
3.Number of Inspection held at vendor-end not available.
4.Reason for delay not captured either by subcontractor or by Quality engineer or by buyer.
5.Cost of Quality Inspection can not be identified.
SAP Solution :
Process-flow-chart for vendor end Inspection
Advantages of mapping vendor-end-inspection in SAP.
1.Defect appearing in vendor-end-inspection available for quality analysis.
2.Reason for delay is identified and corrective action taken for it,to have on time delivery to cutomer.
3.Number of re-inspection are captured which help in corrective action.
4.Cost of Inspection can be identified.
I hope scenario discuss herewith will be helpful to you
Thanks
Hi All,
Recently I have been a part of a SCN discussion thread, where we have discussed about some critical factors needed to be considered professionally while KT is planned in IT out-sourcing model. We had some really thought provoking inputs provided by Martin, Anand and off course Craig, who have moderated our entire discussion in the below thread:
http://scn.sap.com/thread/3779659
I would like to summarize this discussion in the form of a BLOG, which can add value to a wider audience, who time and again come across such situations in their business activities. Before I proceed ahead in documenting the points discussed, I would like to sincerely thank all the participants for sharing their valuable inputs. Will request others consultants/readers reading this blog to share their thoughts and experiences as well, so that this document can be improved for better usability of the community.
Their are certain essential factors needed to be considered during different stages of KT process, majorly applicable for an IT outsourcing model:
A) Before KT - A basic preparation form the team receiving KT can really help this process a big way.
B) During KT - Important technological and behavioral factors, needed to be emphasized religiously.
C) After KT -
Thanks,
Arijit
SAP Quality Management has been an integral component of the SAP ERP solution since its inception. The QM module has more than 10K customers globally and over 500K users. It is mature capability that continues to be enhanced with each new ECC enhancement and service pack. QM capability spans and is utilized in almost every step of the end-to-end, procure-to-pay and order-to-cash processes that ERP enables. The traditional challenge is that there was no way to tie each step of the end-to-end QM process together. In order to “close the loop”, SAP created the Quality Issue Management (QIM) solution as a level of abstraction to sit on top of QM and any other system with quality related information and to tie it all together. A single instance of QIM is meant to sit in top of and integrate with multiple instances of ECC across the enterprise, as well as any other non-SAP, 3rd party quality systems to tie all quality information together. It is a single place where users from across the enterprise, as well as external users (customers and suppliers), can come to raise, collaborate and resolve, not only quality related issues, but any issue, activity or topic for collaboration. QIM was built for quality issue management, but can be used to manage any type of issue, or used to manage any type of collaborative activity.
Some of the types of “issues” QIM has been specifically built and used to manage include:
• Resolution of customer complaints • Resolution of complaints against a supplier
• A CAPA process triggered by a nonconformance issue detected during production
• A Product Technical Complaint process specifically for the Life Science industry
• An 8D process for Discrete Industries
• A Claims process for Professional Services industries
• Handling of any problems that occur during a project
• Handling Change Requests
• Resolution of Compliance issue
The types of issues that can be managed by QIM span the end-to-end, procure-to-pay and order-to-cash processes of the enterprise:
• Procurement – complaints against suppliers, supplier audits
• R&D – product claims, change requests
• Manufacturing – product defects, non-compliance, issues with out-sourced production or subcontractors.
• Sustainability – environmental audits, risk management
• Distribution – inventory inspections, transportation issues
• Service – customer complaints, consumer requests
For example, QIM helps tie a customer complaint to specific product defects due to manufacturing or raw materials from a supplier or to suggested improvements for product design. QIM also helps manage different industry specific issue types such as CAPA processes for compliance in life science industries and 8D processes for managing complaints against a supplier in the automotive industry. Needless to say, QIM is a flexible, versatile solution.
QIM is relatively new to the SAP solution portfolio, released in 2012, but is gaining mindshare and traction in the industry. On September 16, come hear about how Johns Manville, a US based roofing product manufacturer, has successfully implemented QIM to manage their 8D and CAPA processes. They were challenged with getting visibility to information related to customer complaints being collected in multiple ECC and other systems. There was no one place for all the people required to resolve an issue to go to collaborate. QIM helped them bring the process, information and users across the plants into a single place for managing quality related issues. Please register now at the link below and join us for this informative session. I hope to see you there.
Friends, this indeed is a huge topic with several edges to discuss upon. You would possibly find many threads on Data Migration which discuss more about technical aspects such as specific problems related to data migration tools. Whether LSMW is good or BDC gives faster and accurate results or is there any other tool for this and so on! Here I shall not be discussing about the technical complexities involved about the tool. The idea is how neatly this entire activity could be planned, what factors should be considered for planning and how this should be executed to have hassle free experience during Data Migration phase!
Do you really think the only problems that most of you face in data migration phase, are related to the tools used? I don’t think so! There are other factors also that contribute here. If I look back to the projects I worked in or if you ask to the experienced consultants who worked on data migration, the answers are like this.
The above list could go on if we go at very minute levels. And you can observe the variety of issues here. There could be issues from consulting side or from business side covering both technical and non-technical. The important question is – Can the above problems be avoided? Answer according to me is yes. If you have strong plan and execution strategies in place, these all can be suppressed. In planning, you define the check sheet (based on your past experience) for the activities that you are supposed to do along with timelines for every single step. Planning check sheet provides the transparency and clarity to the consultant and to the business users about their individual roles in this phase.
Master data is treated as key data element in any SAP project and that is why it should be given utmost importance. Master data serves as the main base for the success or the failure of the system and hence lots of awareness needs to be spread among the users who deal with this from business side. At the same time consultant should also have the knowledge about its consequences. It is not like that the only data migration phase affects with this but it affects the entire business. Hence accurate master data should be the topmost priority for any organization that would be running on SAP. In my opinion successful data migration is joint responsibility of business and consulting team.
Many project managers and delivery managers plan this as a special event with very detailed matrix of sequential events to be followed along with responsibility fixation, which really helps in streamlining the project resources. Separate coordinator is also assigned in some cases to monitor this activity closely. Although the detailed level planning is done by most of the managers it is equally important that ever team member should understand and be aliened to the same. I may not be in a position to provide each and every single step here as it could vary project to project and industry to industry based on project size. However below are the few common factors that can help plan this activity well!
The ideal time to start is as soon as Business Blue Prints (BBPs) are signed off. The signing off indicates that the requirement gathering phase is over and there is rear or no chance that the new requirement will be entertained. So at this stage or probably when you design the solution approach you are pretty clear about what types of master data are required from business side. You should start listing down such masters (e.g. Vendor Master, Customer Master, Material Master, Routing, Inspection Plans, BOM, Equipment Master etc.) belonging to each module.
It’s not like that you utilize each and every field on SAP screen for any specific master. This depends upon the business requirements. And as the BBP phase is signed off by now, you can have idea about the fields that are required to be utilized. You should also consider the custom fields if you are planning to develop it as a part of your solutions. List down all such fields master wise and module wise. This all serves as input for data migration tool development. Tool development also takes some time. Hence it is better if you start on it as soon as BBPs are signed off.
Once you have identified the required masters and fields the next step is to develop a tool for data migration. You should choose the tool wisely.
Although there is no any specific rule that which tool should be used but I personally first try to find if the standard tool is available such as transaction codes like MASS, MM50, QA08, QI06. By opting such standard transaction codes you minimise the risk of tool failure in Production environment. The pity is you do not have standard code for every master you want.
The next featured options are LSMW or BDCs. Some consultant prefer LSMWs while others choose BDCs. There are few examples where people rely on eCATTs also. For some of the objects standard LSMWs are available by batch input method. LSMWs save much time of ABAP development over BDCs. But there are few objects where BDCs prove useful over LSMW. You should wisely opt and finalize as early as possible what you will be adopting. Accordingly you should take into consideration the needed fields that you have already listed down.
Testing of these tools is the next important factor. You should test each and every of these tools by uploading some dummy records in to your test server first. Based on the test results you should take corrective actions for the tool. May be you can verify in to SAP tables whether the records are generated or not. It is better to take dump before uploading these masters so that later you can compare for the correctness.
Once you are satisfied with the tool results, you should circulate the master data templates to your core users who will be responsible for filling up the master data. The templates should contain below information
It is better if you can share sample filled templates to core users. That will help them to understand how the master data needs to be filled.
Time saving results in to profitability! If you are working in a roll out project then there is a chance that your earlier team or you yourself have already developed the tools for data upload. And these are proven tools as they were already used for upload. So why not to use the same again to upload the data in new plant on the same server? I always recommend to use such tools to the maximum extend you can in the new plant. Assumption is all the master data fields are same in the new plant. You can thus minimize the tool failure threat.
The successful data migration does not only mean the successful data uploading in the system without any error. It means more that that. The best measure of this success is very less or merely no tickets immediately after go live related to data. It is thus joint responsibility of business users and consultants. Business users are responsible for the data collection and accuracy of the data provided while it is consultant’s skill is to upload the data as received successfully in the system. If either of above fails then it leads adverse impact on the business.
Having said this it is important that the business users should be well aware about the consequences of providing inaccurate or incomplete master data or providing tentative (to be) data that how badly it will hit to their future businesses. This point suggests that consultants should have healthy discussions with business users for making them aware about these facts and explaining the roles and responsibility.
According to me this phase should cover below points
You should demand for the sample data from your core user for your verification. This will help to ensure that users are filling the template as required. This also helps to avoid rework and clears the understanding between you and the user. Based on your consent the user can start collecting bulk data.
Perhaps this is the most scary thing that most of the folks feel. 
But it is always advisable to have meetings are regular intervals to have status review about data collection. It is the forum where both (Core User and consultants) can raise their concerns and the solution can be explored. The more transparency you maintain in these meetings the less problems you face while loading the masters. Such meetings help you to track the progress of data collection especially the dependent masters.
You should set the cut-off date in planning phase for receiving the data from business users. It is expected that business users should submit the entire or whatever applicable master data by this date. This cut-off date should be mutually agreed well in advance with them. This is really a god practice I would say , as this can suppress many problems that may arise in future. Imagine a situation where you have invested a week on the the validation work on the data received (using your excel expertise) and the file is ready for upload. At this time time an user sends many additional records saying he/she missed them to incorporate in earlier file. Gosh!
So you will think that if the proper idea was given to them well in advance they could have prepared the entire data by the cut-off date without hampering their regular office work.
I accept that every time this theory cannot be true. But if mutually agreed with customer then both the parties can save lots of time and can concentrate on further steps.
Once you receive the data from users you validate it. During validation if some abnormalities observe then you resend the file for correction to the users. The cycle repeats until the final version of file in ready to upload format is reached. Several tools are available these days for validation purpose. You can even develop a new tool for validation purpose in SAP as well which can compare the values in excel or txt file with dependent masters and can give you the list of abnormalities in few seconds. Using excel techniques you can suppress duplicate records. You can thus ask your user just to rectify those entries and resend the corrected version. Back up of the data is also important here. You should always have the practice of storing or taking back up of every file you worked on. Version management helps you to identify the latest file on which work was done. Loss of worked file may lose your hundreds of hours, remember!
Once the validation is done there should be formal sign off from the business side. This is to authenticate the contents submitted are correct from business perceptive. This can avoid many disputes.
Some teams prefer to upload the data first in mock server or QA servers to double ensure that you are not getting any errors while uploading the data. This depends on the hardware and availability of the server infrastructure for this purpose. If the results are successful you can upload the data in Production environment. Now there could be very detailed check sheet involved when you actually start the data migration. Giving such check sheet here is highly impossible. This is more or of technical sequencing part rather than administrative. For example
It is also advisable that the business team should be available while the data migration is in progress so that any decisions if required in the data correction at the last moment can be possible. To cross check the data uploaded in Production server. You should keep 2 days or some time as placeholder before you actual Go Live. You can use this time to rectify if something went wrong. This ascertains that all is well!
It is bit challenging to provide the detailed check sheet of Do’s and Don’ts here as it may vary dynamically but I am hopeful that if the above factors are considered for data migration planning, you will have less surprises in the data migration phase.
Nothing can replace your own prepared check sheet and your own experience that you have gained or the things that you have learnt from the mistakes. You should include every minute point that you think could be important (doesn't matter how silly it is) so that it would not be escaped from your mind at later stages. Go on marking it as green once you complete that step. Trust me it helps a lot especially when the dependencies are involved. We all learn from the past. Every project adds new value to our repository. So you should go on refining the check sheet based on your project learning and experiences of your seniors.
Like I mentioned in the beginning this is indeed a huge topic. I might have missed few important points as well. I sincerely invite all your ideas, suggestions or corrections to the document to make this even simpler and neatly organised. Plan wisely! I reiterate - Include every minute point that you think could be important! You will have less surprises at the data migration phase!
Thank you and good luck to you all!
Regards,
Anand Rao
Hello everyone 
I believe that there are some QM statistics that may be of your interest, so I decided to make this blog post to show you KBAs (Knowledge Base Articles) View Count.
My idea is to do two rankings, Most viewed from Year and Most viewed from Month.
But, what is these rankings for?
I believe that if any ranked KBA did not work for you, you can bring the solution that resolved your problem.
If you guys like this idea, I can monthly update the ranking (if there are changes). Please let me know 
5 Most viewed KBAs from 2015*
199 Views - 1911886- Transaction code QS41 and QS51 ask transport request
142 Views -2011512 - Dump SAPSQL_ARRAY_INSERT_DUPREC in program SAPLCOVB
138 Views - 2068196 - Error "Change the inspection stock of material XXXX in QM only" during Stock Transfer
*Until 11.11.2015
5 Most viewed KBAs from 2014*
229 Views -2011512 - Dump SAPSQL_ARRAY_INSERT_DUPREC in program SAPLCOVB
209 Views - 1911886- Transaction code QS41 and QS51 ask transport request
135 Views - 1959957 - Usage decision result is not transferred to classification system
*Until 29.12.2014
5 Most viewed KBAs from October 2015
34 Views -2011512 - Dump SAPSQL_ARRAY_INSERT_DUPREC in program SAPLCOVB
21Views - 1705428- Error message IM254 'Invalid object number (status management)' or IM258 'Object does not exist (status management)' in transaction QM02
21 Views - 1911886- Transaction code QS41 and QS51 ask transport request
20 Views - 2068196 - Error "Change the inspection stock of material XXXX in QM only" during Stock Transfer
This kind of surprised me! And you, do you use these KBAs a lot in your projects, implementations or daily work?
I'm waiting for your opinion 
Regards,
Natália Machado
I have a different material and those are produced in different batches. Say have 21 batches are there and QM user will recording the result for one batches. system will automatically copied all the characteristics result in other batches.
Please provide the standard configuration for that one. How can I mapped. Inspection type to be used 04.
Recently you may notice a problem that the GR material document is cancelled, but the corresponding inspection lot is not cancelled together with the material document. You can still see the inspection lot in t-code MD04.
Here is basically what happened:
Prerequisites:
Process:
Result:
Permanent fix:
Implement SAP Note 2186161. This note fixes a bug in this case. After applying this note, when you post new GR material document cancellations in MBST, the inspection lot will be cancelled together with it. Lot status becomes LTCA automatically and won't be displayed in MD04.
Inconsistency correction:
For existing inspection lots, to correct the inconsistency, follow the steps below:
Hi Gurus,
I have came across requirement of Printing QR Code (Quick Response Code) or 2D Bar Code on Smartforms or Download it as an Image file.
Here, I am going to explain "How it can be done?"
Step 1: Upgrade the Kernel if Required
Log in to the SAP >> SAP Easy Access Screen >> System Menu >> Status
Now, Click on the component to check the SAP_BASIS release 731
Close the pop-up dialog and click on the arrow button. The Kernel Version Should be 321 or superior. If it is not then ask your Basis Team to upgrade it.
Step 2: Implement SAP Note 2029824
Ask the Developer to implement the note
2029824 - Support for QR code and data matrix bar code
Step 3: SAP Script Font Maintenance
After successful implementation of the SAP Note. Go to Transaction SE73.
Click on System Bar Code option and Click on Change.
Click on Create(F5).
Click on New (new Barcode Technology)
Define the Name and Description of the Bar code.
Select Bar Code Symbology as "QR Code 2005" and Click OK. Select Alignment as "Normal"
Choose Mode, Module Size, Error Correction Level (Refer the SAP note 2030263 for further information)
Mode:
A - AUTOMATIC
N - NUMERIC
L - ALPHANUMERIC
B - BYTE_LATIN1
K - KANJI
U - BYTE_UTF8
1 - FNC1_POS1 (FNC1 in first position)
2 - FNC1_POS2 (FNC1 in second position)
Module Size: Numeric User Entry
Error Correction Level:
L - 7 % Error Correction capability
M - 15% Error Correction capability
Q - 25% Error Correction capability
H - 30% Error Correction capability
Save the Bar Code Definition. Select the same and Test.
Step 4: Create Program to Download the QR Code as BMP (image File)
Write the below code in the SE38 Program. This Program can download the QR Code as image (.bmp format) on your presentation system.
*YOTQR starts
*&---------------------------------------------------------------------*
*& Report YOTQR2 this program dirctly print BMP file of any barcode
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*
REPORT YOTQR.
PARAMETERS: barcode like tfo05-tdbarcode default 'ZQRCODE',
barcdata(50) type c lower case default '1234567890',
filename type string LOWER CASE default 'd:\1.bmp'.
DATA:errmsg(80) TYPE c,
bc_cmd LIKE itcoo,
bp_cmd LIKE itcoo,
bitmapsize TYPE i,
bitmap2_size TYPE i,
w TYPE i,
h TYPE i,
bitmap LIKE rspolpbi OCCURS 10 WITH HEADER LINE,
bitmap2 LIKE rspolpbi OCCURS 10 WITH HEADER LINE,
l_bitmap TYPE xstring,
otf LIKE itcoo OCCURS 10 WITH HEADER LINE.
PERFORM get_otf_bc_cmd IN PROGRAM sapmssco
USING barcode
barcdata
bc_cmd.
CHECK sy-subrc = 0.
bp_cmd-tdprintcom = 'BP'.
PERFORM get_otf_bp_cmd IN PROGRAM sapmssco
USING barcode
bp_cmd-tdprintpar.
CHECK sy-subrc = 0.
PERFORM renderbarcode IN PROGRAM sapmssco
TABLES bitmap
USING bc_cmd
bp_cmd
barcdata
bitmapsize
w
h
errmsg.
CHECK sy-subrc = 0.
perform bitmap2otf IN PROGRAM sapmssco
tables bitmap
otf
using bitmapsize
w
h.
data length type i.
data hex type xstring.
data bitmap3 type xstring.
FIELD-SYMBOLS <fs> type x.
clear: hex, bitmap3.
loop at otf.
length = otf-tdprintpar+2(2).
assign otf-tdprintpar+4(length) to <fs> casting.
hex = <fs>(length).
concatenate bitmap3 hex into bitmap3 in BYTE MODE.
endloop.
* convert from old format to new format
hex = 'FFFFFFFF01010000'.
CONCATENATE bitmap3(8) hex bitmap3+8 into bitmap3 in BYTE MODE.
clear hex.
shift hex right by 90 places in BYTE MODE.
CONCATENATE bitmap3(42) hex bitmap3+42 into bitmap3 in BYTE MODE.
data bitmap4 type SBDST_CONTENT.
CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
EXPORTING
buffer = bitmap3 " xstring
TABLES
binary_tab = bitmap4.
data bitmap4_size type i.
bitmap4_size = xstrlen( bitmap3 ).
CALL FUNCTION 'SAPSCRIPT_CONVERT_BITMAP'
EXPORTING
OLD_FORMAT = 'BDS'
NEW_FORMAT = 'BMP'
BITMAP_FILE_BYTECOUNT_IN = bitmap4_size
IMPORTING
BITMAP_FILE_BYTECOUNT = bitmap2_size
TABLES
bitmap_file = bitmap2
BDS_BITMAP_FILE = BITMAP4
EXCEPTIONS
NO_BITMAP_FILE = 1
FORMAT_NOT_SUPPORTED = 2
BITMAP_FILE_NOT_TYPE_X = 3
NO_BMP_FILE = 4
BMPERR_INVALID_FORMAT = 5
BMPERR_NO_COLORTABLE = 6
BMPERR_UNSUP_COMPRESSION = 7
BMPERR_CORRUPT_RLE_DATA = 8
BMPERR_EOF = 9
BDSERR_INVALID_FORMAT = 10
BDSERR_EOF = 11.
CALL METHOD cl_gui_frontend_services=>gui_download
EXPORTING
bin_filesize = bitmap2_size
filename = filename
filetype = 'BIN'
CHANGING
data_tab = bitmap2[]
EXCEPTIONS
OTHERS = 3.
*YOTQR Ends
Step 5: Create Smartstyle for QR Code
Define your Smartstyle as below screenshots
Define the QR Code in Character Format as below Screenshot
Step 6: Use SmartStyle in SmartForm
Define the smartstyle in the form attributes as per the below screenshot
Define Text as below screenshots. Caution: keep the <c1> (small letters) not <C1> (capital Letters) otherwise QR code will not get Printed)
in this example, I've used material Number to be encoded in QR Code.
Test The SmartForm
We can use the same procedure to include the QR code on your SmartForms.
This Bar Code can encode up to 255 characters (it is the limit).But, I think, 255 characters enough.
Using this you can shrink the size of your label. You can encode the address information as QR Code and save the space on the form for more details and many more.
Auto Usage Decision
If the goods in an inspection lot are confirmed to be free of defects in an inspection, the system can complete an inspection automatically, provided certain prerequisite conditions have been met.
Prerequisite.
The system can only make an automatic usage decision if the following conditions have been met:
Auto UD process is given Below.
Step 1.
SPRO > Quality Management > Maintain Setting at Plant Level.
In Plant dependent QM setting maintain wait time in Automatic usage decision tab as per the business requirement.
Waiting time :- The number of hours / mins entered here must have expired after creation of the Lot,before the system makes an automatic usage decision for the corresponding inspection lot.
Step 3.
In material master in QM view activate Automatic UD indicator for the inspection type.
Step 4.
QA01 > Create manual inspection lot for the material.
Inspection lot is created for the material of inspection type 09.
Step 6:-
QE01 > Perform resulting recording .
Result recording is completed for the characteristics.
Result recording is mandatory to perform Auto UD if required char indicator is activated for the characteristic.
Step 7
Execute T-code QA10 to perform Auto UD for the Inspection lot. You can also scheduled job.
Auto UD has been made successfully for the inspection lot.
I will be sharing the most crucial preparation tasks to be done for a SAP QM implementation for Procurement and Production areas. In order to have a successful QM implementation, there is groundwork required for the QM to function smoothly.
It is important to discuss the above points with the project stakeholders, as it requires significant time for the cut-over activities.
When an inspection lot is created, the system uses the inspection lot origin to determine how the inspection lot will be processed.
Suppose as per the business requirement inspection type will be use for the material for which result recording is not required and it will have the Post to inspection stock and Auto UD indicator active. I am creating customize Inspection Type Z01 which is a copy of 01.
1. SPRO > Quality Management > Quality Inspection > Inspection Lot Creation > Maintain Inspection Type.
Select the Inspection type 01 and Click on Copy.
Maintain the Inspection Type Z01 and Description.
2. SPRO > Quality Management > Quality Inspection > Inspection Lot Creation > Maintain Inspection Lot Origin and Assign Inspection Type.
Select the Lot Origin 01 and Click on Inspection type for the Origin.
Click on New Entries
Maintain Inspection Type Z01.
3. SPRO > Quality Management > Quality Inspection > Inspection Lot Creation > Define Default Values for Inspection Type .
Select the Inspection type 01 and click on copy.
Maintain the Inspection Type Z01 and field maintain here will have default value for the inspection type.
4. Assign Inspection Type to the Material.
Customize Inspection type will work only when Preferred Ins Type Indicator is activated.
Detailed information on inspection type Z01 will have default value as maintain in Define Default Values for Inspection Type.
Regards,
Vivek Malik
