cancel
Showing results for 
Search instead for 
Did you mean: 

Inspection point

rajesh_sutar2
Active Contributor
0 Kudos

Hi Experts,

Can anybody please tell me,

What is role of inspection point in QM.It will be more helpful if anybody explain with giving suitable example from industry.I have already read SAP library & PDF file related that.But I want more explaination in simple word. Please please........... help.

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member186399
Active Contributor
0 Kudos

Dear Raja,

Inspection point are used for identifications. SAP defines it as A record of clearly identifiable inspection results that are assigned to an inspection operation.

1) For Production related

Suppose you are having a product for which while manufacturing you want to note down temperature ,humidity (MIC's) every hour along with that you want to note the shift , date, time or any other identification. there is only one order generated for the entire days manufacturing .This can be a 03 inspection or 04 inspection

If it is in 03 inspection, you can maintain in routing header inspection point as 150 and QM operation you can maintain a reference in Control key . The reference can be time based / quantity based or freely defined. If your maintaining time based then maintain TFac as 1 Hr.

System will automaticaly generate inspection point after every 1 hr from the inception of inspection lot.

During result recording you will get a pop up of inspection points having hourly points which you can use for result recording your MICs .

Another benefit is that you can identifier for inspection point. As said you can maintain shift, time , date as identifier and during result recording you will get these things automatically. this is done in customisation SPRO > QM> Qual Plan > Inspection Plan> General > Define identifier for inspection point.

2) For equipment and fucntional location

inspection point are mandatory for trigerring calibration inspection . it needs to be maintained in the task list.

Hope this helps you to understand. please revert back if you need more examples.

Regards

gajesh

rajesh_sutar2
Active Contributor
0 Kudos

Hello Gajaesh,

Thanks for ur reply.

Former Member
0 Kudos

Dear Gajesh

For production related inception points, referring to your explanation I need to understand a small point, I have been told that inspection points do not affect the sample size calculation, but let's go back to your example: where we check the MIC every one hour, assume that this MIC is DESTRUCTIVE, so in this case will the number of inspection points affect the sample size calculation ?

What I think is that if the sample size is 1 PC for example and I'm inspecting every 1 hour, I'll need 24 PCs as samples for the day (in the inspection lot ---> Sample size = 24), but if my inspection is every 12 hours, I'll only need 12 PCs as samples for the day (in the inspection lot ---> Sample size = 12).

Am I right about this or mistaken?

Regards,

Mahmoud Osama

Former Member
0 Kudos

Hello Raja,

STD Declination:

A record of clearly identifiable inspection results that are assigned to an inspection operation.

The inspection points are identified by the user by a combination of fields, whose meaning is defined based on their usage.

The inspection points guide the system how the inspection to be done. Whether it is to be done on some Physical samples or Time based or Event Based or Freely defined etc etc.

I mean If you select inspection point as Physical Sample then system will give Physical Sample number against which you need to record the results.

If you select the Freely defined inspection point then it will let you enter any text as inspection point identifier for the result recording.

There are inspection point types for equipment, functional locations, physical samples, and production. These inspection point types can be assigned individually in the user specifications if required. The following parameter IDs correspond to the following inspection point types:

Parameter ID Inspection point type

QB1 Equipment

QB2 Functional location

QB3 Physical sample

QBK Production

Examples

Wire basket/shift

A wire basket number uniquely identifies for all operations a production quantity for which inspection results should be recorded. For results recording, the shift should also be entered as additional information.

At the operation level, an inspection interval is predefined for every 50 units.

You can show this by the following inspection point identifier:

Predefined field dependent on inspection point type (' ')

Field active Key word

User fields Field active Key word

Text Length 18

Text Length 10

No. Length 10 1 Wire basket

No. Length 3 X Shift

Date

Time

By marking the "Field active" column, you can make a field an optional field.

In order that an inspection point can be uniquely identified, the system only considers fields with an entry between 1 and 6 in the "Field active" column.

Vessel/Date/Time

In the process industry, liquids are produced in vessels. This operation can take several days. A sample is taken on an hourly basis (a time-based inspection interval, interval = 1 hour).

This can be be shown by the following inspection point identifier:

Predefined field dependent on inspection type (' ')

Field active Key word

User fields Field active Key word

Text Length 18

Text Length 10

No. Length 10

No. Length 3 1 Vessel

Date 2 Date

Time 3 Time

Test equipment

Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test equipment, use 'test equipment' as the key word.

This can be be shown by the following inspection point identifier:

Predefined field dependent on inspection type ('1')

Field active Key word

Equipment 1 Test equipment

User fields Field active Key word

Text Length 18

Text Length 10

No. Length 10

No. Length 3

Date

Time

Note

Even if the test equipment type allows for certain fields, you can define additional user fields.

If you enter a value for the field combination in the task list header, this value is copied to the inspection lots.

-


You define inspection points in this step. This involves defining the following:

Identification of inspection points

Default values for valuating the inspection points

Function modules for generating the inspection points

To identify the inspection points, the inspection point data record can contain a date and time field. For each of these fields, there are two text and number fields of variable length that you can freely define. You use these fields when recording inspection results, to assign the inspection points to the units that have been inspected or to the partial quantities. You do this by selecting one of the flow variants stored at operation level.

You can use this identification technique in several application areas. The standard system, therefore, provides the following inspection point types

Freely defined inspection points to identify partial lots in production

You need this inspection point type, for example, if you create inspection lots for a production order and want to carry out several inspections for each operation during the production process.

Inspection points to identify samples

You need this inspection point type if you want to manage samples and record inspection results for physical samples

Inspection points to identify maintenance objects

You need this inspection point type if you want to carry out calibration inspections and record the results of test equipment inspections or inspections of functional locations.

Inspection points during the production process

The identifiers for the inspection points are defined in the task list header and are valid for all operations. If you do not define an inspection point identifier in the task list header, the system uses a general identifier, that is stored in the settings at plant level.

Inspection points form the basis for defining partial lots with their own usage decisions. When used with control charts, inspection points are suitable for statistical process control.

If you define the use of inspection points in the task list header, you must specify whether the inspection points are to be based on time, quantity, or to be freely defined at the operation level. For inspection points based on time or quantity, you must also specify an inspection interval in the operation. During the production process, you create a data record that contains inspection results for each inspection point.

You must assign a produced quantity to each inspection point. You can combine the partial quantities for inspection points into partial lots and the partial lots into batches.

If you use freely defined inspection points with inspection plans outside the production area, the time-based or quantity-based inspection interval and the management of batches or partial lots is not supported.

In Customizing, you can define function modules to generate time-based or quantity-based inspection points. In addition, for the fields that are to be identified, you can define function modules that propose and test entries and display entries for selection.

Inspection points to identify physical samples

The identifier for this inspection point type contains an additional field for entering the physical-sample number.

This inspection point type does not contain functions for partial lot assignment or for time or quantity-based inspection intervals.

Inspection points to identify maintenance objects

The identifier for this inspection point type contains an additional field for entering the equipment or functional location number.

This inspection point type does not contain functions for partial lot assignment or for time or quantity-based inspection intervals.

Standard settings

The table has the delivery class G. The following name range is reserved for the user:

User field combination 9, A, ... , Z*

The system contains function modules for generating

Freely defined inspection points

Executable example

Default values for the inspection point identification

Non-executable example

Read the online documentation for these function modules.

Recommendation

Due to the summarization of data at the characteristic level, the maximum number of inspection points for each operation is limited in the standard system.

For performance reasons, retain the settings in the standard system.

Inspection point definitions are keys for data records in table QAPP. They should therefore not be deleted in productive operation. Do not change an inspection point definition that has already been used. Instead, create new entries in the table where required, and flag the old ones as 'no longer to be used'.

Activities

1. Determine:

a) Whether your company carries out multiple inspections for an operation during production or for other operations and how the intervals for these inspections are defined.

b) Whether you need special identifiers to record inspection results for physical samples. If the equipment number is sufficient, you should only require the standard entries.

c) Whether you need special identifiers to record inspection results for maintenance objects. If the sample number meets your requirements, the standard entry should be sufficient.

2. Define appropriate inspection point identifiers by assigning a suitable definition and sequence to the fields contained in the "Inspection Point Identifiers" table.

3. Specify default values for the usage decisions relating to the inspection points. To do this, refer to the steps contained in the subsection Inspection Completion. This describes how to define the quantity of usage decisions as well as the follow-up actions linked to the decisions. You assign follow-up actions for inspection points in production at partial lot level, and actions for other inspection points at lot level.

4. Determine whether the number of inspection points at an update is to be limited at characteristic level, and if necessary set the maximum number accordingly.

5. Determine whether you want to generate inspection points or default values for inspection point identification with your own function modules and make sure these modules are programmed.

6. Make sure appropriate sampling procedures are maintained for the inspections carried out on the basis of inspection points. For additional information, refer to the chapter Quality Planning, Basic Data.

7. Check the settings at plant level. If necessary, define the following default values:

Sampling procedure used in conjunction with inspection points in production, physical-sample processing or calibration inspections.

General inspection point identifier for inspections in production.

Way the partial lots are created

Usage decisions for inspection points or partial lots

Regards,

Shyamal

rajesh_sutar2
Active Contributor
0 Kudos

Hello Shyamal,

Thanks for giving quick reply. Your reply cleared 50% problem.Thanks.It will be more helpful if you give more example from industry.