Measurement Reading Transfer – A useful functionality
Introduction:
This document is about the field marked below in the IK01 transaction screen. I’m sure many of us have noticed this, but yet to explore .
Let’s consider TWO Dumpers as Equipments and their Tyres as Sub-Equipments for our Demo:
Two Dumpers, with SAP Equipment Ids V-1000 and V-1001, each having 6 Tyres as shown above.
V-1000 with tyres say TYRE0001, TYRE0002, TYRE0003, TYRE0004, TYRE0005, TYRE0006
And
V-1001 with tyres say TYRE0007, TYRE0008, TYRE0009, TYRE0010, TYRE0011, TYRE0012
(External numbering is used for easy understanding)
Each Dumper above has a meter showing the number of hours it operated.
The Objective
When we record a reading from the above meter in the SAP system (using IK11, on a Measuring point), the counters of the 6 Tyres installed in this vehicle at this time, shall be automatically updated.
This means when we create one measuring document on the vehicle, system should create a total of 7 (1 + 6) , measuring documents so that the usage hours flow from the Vehicle counter to the Tyre counter.
And then, when a Tyre is dismantled from one vehicle and installed in the other, the Tyre counter should derive its own usage hours from the present vehicle counter readings.
Let’s see how this happens:
Part1:
Preparing the Masterdata:
First let’s have a characteristic RUNNINGHOUR as shown below (Tcode CT04).
Using this characteristic RUNNINGHOUR, let us create the measuring points, on the Vehicles first.
V-1000
V-1001
Now we need to create measuring points on all the Tyres. A sample screen is …
Compare the measuring point screen of Vehicle and the Tyre. The difference is the Red Box.
Remember all these measuring points are based on characteristic RUNNINGHOUR.
So we create 12 measuring points in a similar way, one for each Tyre.
Below is the IK07 screen, where you can see at a glance, the measuring points we have created.
Notice that Transfer support ‘X’ mark is there for all the 12 Measuring points of Tyres.
Now install Tyres under the Dumpers V-1000 and V-1001 (Superior Equipment), using Tcode IE02.
Example:
Tyre: TYRE0001.
When we try to define the Superord. Equipment as V-1000 (in the Structure Tab of IE02 ) wel get this screen.
System is asking for your confirmation for Transfer of Readings from the Superord.Equipment (V-1000 in this case) to the Tyre (TYRE0001).
Click on Copy and Save the Equipment master.
In a similar way install all the Tyres under the respective Dumpers.
As mentioned above, the initial set-up will have is:
Dumper V-1000 as SuperOrd. Equipment for Tyres TYRE0001 to TYRE0006 and
Dumper V-1001 as SuperOrd. Equipment for Tyres TYRE0007 to TYRE0012.
Everytime we need to confirm Copy during Equipment installing under the Superord. Equipment.
Now the following is the Equipment tree we have just made.
The Masterdata preparation is completed.
End of Part1 ————————————————————————————————————————————————
Part2a:
Create Documents and understand the working of Transfer Support.
It is time now to see what happens when we record Dumper Hour Meter readings through IK11.
Create a measuring document on measuring point 3113 (Equipment Tyre0001), with reading 1000.
Let’s assume that the Dumper V-1000 operated for 1000 hours and its meter is showing a value 1000 Hours. We now create a measuring document to record this value.
Note:
Remember that we get the Cumulative Operating Hours from the Dumper Meter. So, we need to put this reading in the Counter Reading field of the IK11 screen.
When we save this document, we see this message on the task bar.
This is exactly what we expect from the system. As explained above 1 document is what we have created just now and the other 6 documents are automatically created for the Tyres. This means the Usage Hour counter for all the 6 Tyres started with their first reading as 1000 hours.
Likewise when we create a document with value 500 hours for Dumper V-1001 (Measuring point 3114). Measuring documents are automatically created for Tyres TYRE0007 to TYRE0012, with this reading of 500 hours.
End of Part2a ————————————————————————————————————————————————
Part2b:
Let’s now see what happens when Tyres are relocated from one vehicle to the other.
We will examine a case of TYRE0004 is dismantled from Dumper V-1000 and installed in V-1001.
And TYRE0009 is dismantled from Dumper V-1001 and installed in V-1000.
When we try to dismantle TYRE0004 from V-1000 through Tcode IE02, we get this warning message.
We can understand what the message says, It is stopping Reading transfer for this equipment (TYRE0004) from V-1000.
We continue and give value V-10001 in the Superord. Equipment field. Now we get this screen (already seen before once), asking for confirmation to establish transfer relation with the new Superord. Equipment.
We continue by clicking on Copy and Save the Equipment master.
Repeat the same for dismantling Equipment Tyre0009 from V-1001 and installing it in V-1000.
See the new structure, notice the change in the places of swapped tyres.
Now we create measuring documents on Vehicles.
I have created a document with reading 1450 hours on V-1000 (Measuring point 3113) and a document with reading 1850 hours on V-1001 Measuring point 3114).
Now see the IK17 screen below in the sequential order of Document creation.
The upper half (Green) is before the Tyre swaps, and the lower half is after.
Give special attention to Swapped Tyres (TYRE0004 and TYRE0009) to observe the system intelligence, in transfer of readings during Sub Equipment relocations.
For better understanding Equipment-wise sorted list of above is attached herewith.
End of Part2b ————————————————————————————————————————————————
Note1:
One more thing that happens in the system background during this process was not shown in pictures above.
That is when we click Copy during Equipment installation under a Superord. Equipment in IE02, some changes happen in Measuring Point data (obviously),
i.e. in IK03 screen, which is shown in the field marked below.
As soon as we install TYRE0001 under V-1000, the field marked above is filled with the measuring point of V-1000.
Similarly this field is updated whenever Equipments are relocated from one place to other.
Note2:
In this demo Equipment – Sub Equipment scenario has been dealt.
This document is valid for Functional Location –Equipment Scenario also.
Concluding Remarks
Here, a vehicle scenario has been taken for demonstration of this Measurement Reading Transfer Support functionality of SAP. It is believed that there will be several other applications requiring this feature.
Thank you
Jogeswara Rao K
Hi Jogeswara Rao,
Greetings for the day!!
Thanks a lot for sharing such a beautiful document, i hope it will definitely help me to improve knowledge base in the same.
regards
Anand Kumar KS
Thank you Anand for such good words.
Regards
Jogeswara Rao K
Hi Jogeswara,
Thanks for your efforts.
I have ECC6. EHP6, I tried to map your scenario in my system by dismantle child equipments from functional locations, attached them to to the superior equipment and followed the same steps as you mentioned above but the readings are not being transferred to the child equipments.2
Please help me.
You need to investigate your local reasons related to Measurement transfers of Measuring points in general. This is a post based on implemented process and working model.
Very nice effort.Thanks for sharing. 🙂
very usfully docment.. thanks Jogeswara rao..
Thank you Katigiri and Srinu.
Good documentation Jogeswara Rao Garu.....
Best Regards
Kalyan
Thank you Kalyan!
Very Good Documentation for capturing Tyre History ..!!!
Thanks for sharing Jogesh.
Thank you Akhilesh!
Tyres is a case for demo. There can be many such applications.
Good Document.....Thanks for sharing...
Thank you!
A good man , a good document, thanks for sharing.
Hi kangda,
Glad to know that the docuement is useful to you.
Obviously a good man (you) feels the way you felt about others (it is me here)
Regards
Jogeswara Rao K.
Good Document .. thanks for Sharing
It suites to our Organisation business structure... I will Definitely try it out to get these SAP functionalities used.
Thank you Vishal
Excellent, clearly presented document - thanks for sharing 😀
Thank you Gary,
This is a good compliment ! 🙂
Very Nice explore.. & explanation.. like earlier helpful documents. Gr8. Job done Mr. Jogeswara Rao Kavala. Thanks!! for sharing. 🙂
Thank you Pravin,
That is a great compliment.
Excellent document.. Thanks for sharing 🙂
Thank you very much Pramod!
Dear jogeswara sir,
A small doubt in this scenario.
Assume that tyre has a use full life of 10000 km. we have assembled 6 tyres for an equipment. After 8000 km out of 6 tyres one tyre has got damaged and need to be replaced with new tyre. Now the counter reading of the new tyre has to be zero has to map this scenario. Can you please guide.
Obviously,
It is similar case when we take a tyre from one vehicle to other.
The counter of any tyre is updated by not its own reading. But it is updated by the reading of the Vehicle counter.
So when a new tyre is fitted into a vehicle the counter reading of the vehicle is transferred automatically to the new tyre. And whenever a reading is taken in the vehicle, the difference reading is updated in the Tyre.
This will be very clear when you try it in test server.
Jogeswara Rao K
thank you very much sir. ill check once.
Hi Pramod,
See this
New Tyre fitted in a Vehicle and the vehicle read a total counter reading (Hrs) which gives a difference of 25 to its previous counter reading.
Now this 25 flows to all its tyres including new tyre, recently fitted.
So the first document of new tyre automatically created is
Now a second reading is read in the same vehicle and this time with a difference of 70 to its previous counter reading. Again documents are created for all its tyres.
Let's see the latest document of our NEW tyre.
Fine, our New Tyre run for 95 hours so far.
Now I have shifted this Tyre to other vehicle, by Okaying the Transfer of Measurements proposal by system during installing.
Then a counter reading performed in the new vehicle of our New tyre, with a difference of 27 hours. Documents created for all the tyres under the vehicle (including for our new tyre)
Let's see the latest document of our new tyre.
Reading 122 is earlier 95 + present 27.
So irrespective of the Vehicle, the difference of running is tranferred to the tyre from the Vehicle it is installed and its (tyre's) counter is updated.
Hope you've followed. (Try this yourself to experience)
Jogeswara Rao K
Thank you sir
Hi Jogeshwar ,
Thanks for sharing this document . A small doubt I am having :
What I have understood from the screenshots is TYRE004 was having reading 1000 (which came by posting meas. doc. on its superior equipment) .
After dismantling TYRE004 and installing it to V1001 , we have posting a meas. doc of 1350 . Now what system has done is it has added this 1350 to the earlier reading of TYRE004 so the final reading is 1000+1350 = 2350 hrs . In other words till date TYRE004 has worked for 2350hrs .
Is my understanding is correct ?
Quite Right!
The difference calculated at the time of Counter Reading on V-1001, 1350 (1850-500) is transferred to the Difference field of the TYRE004 Counter and adds to its previous Total Reading (1000).
Nice Document sir.
Thank you !
Maheshwaran,
Awesome post..... Nice understanding Shared..... Thanks a lot its really helpful.
Chin2.
Very much helpfull document...Thanks Jogeshwara...
Very nice explanation Jogeswara sir .
Thank you Nitin and Amol
Hi,
Thanks for sharing such a helpful document.
Regards,
Narresh
Thank you Naresh !
Regards
Jogeswara Rao K
Hi,
Thank You Very Excellent Post Raoji.
Helps me a lot to Understand.
Is it Possible to explain Single Value and Multiple Value in Characteristic transaction.
Regards,
Bhanu.
Thank you Bhanu,
The applications, I have come across so far, for this transfer functionality has been for Single value unambiguous characteristics only. If you have any such requirement in your area for the multiple characteristic, you may try to examine the behaviour in the same way explained in the document.
Jogeswara Rao K
Hi Jogeswara,
Thanks for sharing. We also have a similar requirement where we need to map several such attributes like Running Hour/Machine hour etc to a vehicle. I tried the Measuring Point functionality but not in such detail. Thanks again for a nice and clear presentation.
Thanks
Rakesh
Thank you Rakesh for inspiring words
Jogeswara Rao K
Thank you Mr Jogeswara,
This is a very nice document to read, I will further share it with others in this network.
Thank you.
Thank you Sibusiso !
It's very nice of you.
Thank you very much, Jogeswara!
Thanks Jogeswararao garu, very nicely presented helpful document.
Thank you Suryaprakash and Abhilash
Very nicely made doc with crisp example. Excellent Blog....
Very nice document and superb explanation sir.
Thank you Sunil for the motivating words.
Hi Jogeswara Rao,
Very nice document and recently I had worked with your colleague YS Sekhar in one of the projects and he was quoting your capability and this document making his comments true.
Any how thanks for sharing such useful information.
Regards,
Nikhil
Thank you Nikhil,
For the praise and memories of an old friend.
Sir ,,,thanks you so much for documents .....hat's off for u ......gr8 work
Thank you Lokesh,
That's a great compliment. 🙂
Thanks Jogeswarji,
This is very useful in fleet management for tracking the tyre managements as well as trailer management which is big issue in fleet management.
It is possible this scenario is work for if already tyres installed in fleet.
There should not be any issue, because the difference reading is only flown from the vehicle to the installed tyres.You need to give initial counter readings to the individual tyres as per your records or an approximate run reading so far. Try in Dev server and satisfy yourself. Thanks for the praise.
Regards
KJogeswaraRao
again thanks for reply,
this is good solution
Jogeswara Rao Kavala
Sir, I have a similar scenario implemented at one of my client's side.
Everything is working perfectly fine but I have a question here.
Equipments from 1 specific plant are not copying the reading to sub-equipment automatically, we have to get it done manually from user.
This scenario is for a single plant, rest of the plants it is perfectly fine.
Please do guide at this.
Chin2.
This situation, which I have yet to come across can not be readily answered. You can research to find the reason. Please post the solution if found one. For us it is a single plant scenario, so chances for me to simulate the scenario to find out the reason are limited.
Good luck
Sir,
Right now am searching the same in the system and will surely post once am through with the solution.
Just wanted to know whether any step is getting missed by me in this case.
I have implemented this scenario for one of my clients with the help of this post but, as I was not a part of implementing the process at the present client, is there any step which is once done cant be reverted in this case?
Anyways, will surely reply if i am done.
Thanks for this post once again sir.
Chin2.