Hi Rakesh
Finding solutions can be a challenge and sometimes the area we specialise in blinkers us. As a developer or technical person it can be easy to seek our development and technical solutions when a simpler option already exists.
This is not about moving an item via the 3 tier landscape. But proposing an option like this has a cost (development/change request); a time delay (user having access to PA40/PA30 vs the build effort) and a risk (code not fully tested and direct table update)
I applaud exploring options but they should always be assessed for appropriateness. In this particular situation, the recommendation would have been better as a PA40 hire action to fix as opposed to directly updating tables (you don't know what other validations for other infotypes or even triggers to other process areas will be impacted)
A good developer can recognise when the solution does not sit with them. Not every problem sent your ways needs to result in a code change 
Regards
Colleen