topic fixed asset and multi org .. any relation
TRANSCRIPT
-
7/26/2019 TOPIC Fixed Asset and Multi Org .. Any Relation
1/2
Recently i came across an issue in Fixed Assets, for which later found the solution from Metalink. But felt the
experience must be shared with every one ....
We were testin few transactions in pro!ects module, which are bein transferred to Fixed Asset module
"nterface table. After succesful transfer of the transacitons, we came to the mass additions form which provides
the data in the interface table, and #ueried our newly created transaction and clicked $%&'.
(aw the entire details of the transaction that is bein transferred from %ro!ects to Assets, however when i was
tryin to find the pro!ect related information, system throwed an error, when i clicked the )%ro!ect *etails)Button.
+he error received was ..........
$RA-/-01 no data found
$RA-2341 at )A%%(.%A56+"7(), line 4-0
FRM/-8031 W9&''&WF$RM"'(+A':& trier raised unhandled exception $RA/-0.
"t looked like some thin very technical, as FRM errors normally demand for a recompilation of a form or
applyin a patch which will provide hiher version of Form.
Where as the classic $RA-/-0 error bein very eneric, ave suspicision as to some thin wron with the
data......
9owever $RA-234 stated, that, system failed the validation on line 4-0 for the procedure %A56+7(....
By look of the error messae, it looked as if a very stron contender for patch application or restart the
database or recompile the form ...... 9owever before makin any conclusions on my own, loed in to metalink
to find out what oracle has to say about it. Before loin a service re#uest, it is always advised to search for
the existin issues which were resolved .... " did the search with the error codes ..... " ot a Bullsyeeee hit .....
&ven thouh i was much happier that i had ot the metalink reference for the issue, some how i am not pleased
with the solution they have stated.
+he issue will be resolved by settin M$1$peratin unit profile option for the Fixed Asset Responsibility........;
(olution seemed to be very easy to implement, whereas #uestions arise as to why one must be settin up this
profile option for a Fixed Asset Responsibility .....As a pratice every one used to set Multi or related profile options for every responsibility to related to
(ubleder ... apart from Fixed Assets ..... reason bein, Fixed Assets does not fall within the purview of Multi
$r. Fixed asset is considered to be a stand alone, and it is overned by Asset Book setup only .....
Asset are not entered $peratin unit wise or 7eal &ntity wise etc ....... so settin up the M$1$peratin unit
profile option looks to be un!ustified for a moment ....
Whereas started assumin what could be the cause .... bluntly speakin the cause is some validation handled
in the procedure is failed, whereas why at all such an validation is built in first place ... what could have been
the business practice behind it ....