We are implementing a primarily projects organization and have a requirement around populating the POET information when creating requisitions.
Requisitioners primiraly work one one Project (and we only have one task against each one) so we want them to enter in their preferences the Project and Task and so also have to enter a default expenditure type and Org.
We have a mapping set mapping Procurement Category > Expenditure Type so when they select an item or non catlog request and populate the category the expenditure type should generate. This works fine when preferences are not entered, but means the user has to repetitively enter project information each time which isnt great on some of the multi line reqs they create.
when preferences are entered then the mapping set does not work as we have been told by Support that the preferences take priority over the mapping firing, which is the opposite of what happens on accounting where the tab settings take precedence and an ER has been raised.
Has anyone had experience of this and any suggested workaround to ensure that the expenditure type from the mapping is on the requisition rather than from the preferences, we do want the preferences filled in.
Extract from our SR 3-18639733031 for any Oracle folk who want to see the full detail.
"As per my understanding, you created a Mapping Set as per note 2250648.1
That works if there are no preferences, however when Requisition preference is entered for project and expenditure type, only the project defaults but not the expenditure type .
found Bug 24801279 : PRCCEN: EXPENDITURE TYPE NOT DEFAULTED IN ADD REQUISITION LINE PAGE
which states behavior is standard functionality.
The conclusion is: The user's preference will overwrite the DFF segment default.
It is one or the other.
Enhancement Raised: Enh 28984461 - ALLOW EXPENDITURE TYPE DEFAULTING WHEN USING BOTH PREFERENCES AND DFF SEGMENT
If it's standard functionality right now, your best bet may be to add a personalization to the form. It could fire on-new-record or on-validate-record, with an action to check the category and set the expenditure type to the user's settings. You could also have it re-check the project and task if you want, in case users try on their own to set defaults, or try un-setting them.
I will look for your enhancement request and vote for it. It should be possible to default any or all the values, whatever fits the business need.