Quality Control of Geochemical Samples in Mining Industry
1. Introduction
This Blog describes the Quality Control of Geochemical Samples in Mining Industry and the terminology related. Very often in the mining industry, there are various physical, chemical, acid and other tests that are to be conducted to assess the quality of the metal ores. Due to the volatile nature of the various materials such Iron Ore, Phosphorus Ore etc.,, their properties needs to be checked frequently. For example, percentage of moisture, compressive strength, density, Percentage of Oxides, porosity, Loss on Ignition, Metal % etc., change with the time.
2. Terminology Used in Quality Analysis (Mining Industry)
2.1. Point of Analysis
- Origin Analysis:
Quality results are checked at the Mining site
- Destination Analysis:
Quality results are checked at the Destination/Customer site
- Negotiation:
Quality results are sometimes decided by negotiating between Mining Company & Customer. (Depends on the Agreements between two parties)
2.2. Parties conducting the Analysis
- Client:
Quality results are checked by the Mining Company
- Independent:
Quality results are checked by the Independent Vendor (decided by both Mining Company & Customer)
- Umpire:
Quality results are checked by the Third Party
- Customer:
Quality results are checked by the Customer
2.3. Geographical Location/Testing Laboratory
- Location/Laboratory:
Analysis conducted at a particular geographical place or location. For example, Laboratory, Oman, New York etc.,
3. Mining Industry Requirement
As the quality parameter values vary frequently, many a times, the quality analysis is carried out is differentiated based on the Geographical location, Time & the party conducting the tests. Due to these reasons, many results are recorded for the same characteristic. In order to accommodate these requirements in SAP Quality Management module, the Origin of Results Data can be used. This concept avoids creating multiple characteristics for the same quality parameter that is to be checked. Moreover, in Mining Industry, the invoicing and billing depends on quality of the mining material. For example, for the Material Ore with less moisture percentage is invoiced with less cost when compared to the Material Ore with more moisture percentage. This can be addressed using the Origin of Results Data.
4. Significance of Origin of Results Data
The results origin entry defines the source of information. This can be assigned to the characteristic in the Inspection Plan or in the Results recording screen. As long as the inspection characteristic has the status “in process”, results origin during results recording can be specified.
5. Configuration Required in SAP
Navigation Path: SPRO > Quality Management > Quality Inspection > Results Recording > Define Origins of Results Data
Origin of Results Data | Short Text |
Z1 | Origin – Client Analysis |
Z2 | Origin – Independent Analysis |
Z3 | Origin – Umpire Analysis |
Z4 | Origin – Customer Analysis |
Z5 | Destination – Client Analysis |
Z6 | Destination – Independent Analysis |
Z7 | Destination – Umpire Analysis |
Z8 | Destination – Customer Analysis |
Z9 | Negotiated Client and Customer Analysis |
ZA | Oman Main Laboratory |
ZB | Oman Supporting Laboratory |
ZC | Oman External Laboratory |
5.1. Detailed Explanation of Configured values
- In the Origin of Results data configured, Z1 to Z8 are analysis values with reference to the Parties conducting the Test (Client/Independent/Umpire/Customer) and the Point of Analysis (Origin/Destination)
- Z9 refers to the negotiated value between Client and the Customer
- ZA to ZB are the values with reference to Geographical location (Oman Lab)
- In addition to the description of the results origin, data source for the inspection results also can be selected in the configuration
6. SAP Scenario
Below is the scenario demonstrated for usage of Origin of Results Data.
6.1. Master Data
6.1.1. Master Inspection Characteristic
- Create Master Inspection Characteristic Master using Transaction code QS21
- Iron content (Fe) is considered in the below example with Quantitative characteristic
6.1.2. Inspection Plan – Result of Origin assignment
- Create Inspection Plan using Transaction code QP01.
- Assign Master Inspection characteristic for the Operation.
- Single Master Inspection characteristic (Fe) is assigned to assess the same characteristic at various ports or at different point of time etc.,
- Select Master Inspection characteristic and Click on General Data Details
- Assign Origin Results Data Z1- Origin – Client Analysis for the Characteristic as shown below.
- Similarly, assign Origin Results Data Z2 – Origin – Independent Analysis for the Characteristic 20 as shown below.
- After assigning the Origin results data for all the characteristics, save the inspection plan. Message will be displayed as below.
6.2. Transaction Steps
6.2.1. Inspection Lot creation
- Create Inspection Lot using Transaction QA01 (Inspection Type 01 is used in the below example).
- Enter Quantity details & assign Inspection Plan.
6.2.2. Results Recording
- Record the results for the characteristic using QA02/QE51N transaction
- In the Record Results: Characteristic Overview screen, we can observe that the result is recorded for the same characteristic with different Origin Results Data.
7. Benefits derived with Usage of Origin of Results Data
7.1. Invoicing
Depending on the agreement between the Mining Company and the Customer/Vendor, the appropriate result can be considered for the Invoicing (out of all the values recorded for the same characteristic).
7.2. Batch Update Functionality
Minor enhancement can be done to the standard batch update functionality while taking Usage decision for the inspection lot, in order to update the batch value with one of the results recorded based on pre-configured conditions.
Nice blog, I haven't used this functionality so far but I feel that it has the potential to eliminate a lot of duplicate MICs...
Hi
Nice blog and pretty useful. I guess few of the snapshots are duplicate and missing the order. Pl ignore if i'm wrong 😎 .
Regards,
Nitin
Thanks for the comment Nitin. The sequential order is right but I reduced screenshots of the regular transactions & kept the key ones only.
Hi Navin,
Cool!! Still I would like you to look after 4th and 5th snaps under 6.1.2 and 1st under 6.2.2.
They look similar under different headers.
May be Im still confused. I hope you don't mind such feed backs. Guess they are necessary 😉
Regards,
nitin
Hi Nitin, You're right. I've now added few more screenshots. plz check and let me know for any query. Thanks alot again for your comment. 🙂
Hi Navin,
Now it is corrected and looks appropriate for users to learn perfectly 🙂
Keep posted for our continuous learning
Regards,
Nitin
Hi
Nice document. You used this functionality smartly. I used this one only for copying result from previous lot.
Keep posted on based on exp.
Manish
Hi.. New to this functionality... will try to replicate and contact you for any help.
Reg
Dsk
Hi,
This is a very interesting approach on the usage of results origin field.
A 2nd Alternative could be to adhere the characteristic of the origin as an Inspection point field. The possible values of the origin can be obtained by a custom table using the standard FM provided for the IPs (F4).
With this approach, the inspection plan will contain only the specifications of the material and upon results recording the inspector will define in IP details, the origin of the values he wants to register.
In this way, in case of a new origin, it will not be required to modify all the inspection plans.
KR
Stelios
Hi Navin,
Nice Blog. Thanks for sharing.
Regards,
Ramagiri
Hello,
Nice Blog. i am looking for these kind of information only. This blog industry specific. Very nice Blog.
Thanks
Mahe
Nice blog....Thanks for sharing