On the SAP side our functional MM guy has it set up (for a single site) that when they put in a purchase requisition for something with UoM K6 it automatically gets converted to K3 when the PR is approved. However in Fiori this config doesn't appear to be triggered. Does anyone know if the Fiori app should be triggering backend config, and if not is there a way to set up similar config that will get executed in Fiori?
After debugging my way through the code I found that when it called BAPI_SOURCEDETERMIN_GETSOS it was getting the correct UoM for the site in question. However it then simulates a PO by calling BAPI_PO_CREATE1 and that returns the incorrect UoM. And it's the results of the simulation that Fiori seems to be using. I've opened up an incident with SAP to review BAPI_PO_CREATE1 getting the incorrect UoM.
In this case the backend server is also the gateway server, so the configuration should be good for both, unless there's another setting somewhere that was missed.
Share the detail logic for converting UoM when PR is approved. Is it handled by BADI or workflow logic or GUI screen logic? Fiori app just has approval function, so you have to implement UoM conversion in your project.
It would be simple, if PR has correct UoM when it is created.
He's got the custom UoM set up in tcode CUNI (K2 and K6). And then for the specific article he is specifying that for a particular site, it should always be in K6. So if he creates a purchase requisition with unit K2, when it gets approved/assigned it converts it to K6 (in SAP, but not in Fiori). What we're then trying to figure out is if this *should* be taking place in Fiori but it's not, or if Fiori has it's own workflows and so we'd have to look for another solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.