09-29-2016 4:05 PM
I am using BAPI_ALM_ORDER_MAINTAIN to create Work Orders with Service Lines. Under Service Line we are using unit of measure AU (activity units) which is accepted in IW32 transaction. But the BAPI is throwing error "SE 284 Unit of measure for work must be a unit of time" There is an existing OSS Note 1860901 that describes a similar issue but it is for an earlier support pack than our current one. AU should be accepted for the Service Line but right now we can only get it to accept H (hours) or related UoM in the BAPI. Would appreciate any help.
Thanks,
Ryan
09-29-2016 7:38 PM
Have you tried debugging the BAPI code in Include LMLSPF51 and check why the conversion fails? It could be that AU works for IW32, may be because it does a conversion internally...
09-30-2016 8:45 AM
Dear Ryan,
Ravi's said is right. There is a conversion input when you pass the UOM in
BAPI_ALM_ORDER_MAINTAIN.
Please convert the UOM using this FM : CONVERSION_EXIT_CUNIT_INPUT when you pass the parameter UOM to BAPI.
Regards,
Yance
09-30-2016 9:07 AM
To be more precise, there is no conversion exit execution in the BAPI, and there is one in IW32 PAI; A BAPI is not a BDC...
Ref: Internal and External Data Formats in BAPI Programming Guide Reference (CA-BFA). - Check online documentation
Regards,
Raymond
10-03-2016 2:05 PM
Thanks for the suggestion, but I have already tried passing the UoM through the conversion routine mentioned. The BAPI does not accept either AU or LE (the converted value) and in fact when it is passed through the conversion routine the BAPI rejects it as an invalid UoM altogether. In IW32 there is no problem with this, and we can post using a BDC but are trying to avoid this route as we have run into a lot of issues with BDC.
Thanks,
Ryan
10-03-2016 2:25 PM
So next step is SAP bug program error, so did you look for OSS notes (e.g. 1860901 - BAPI_ALM_ORDER_MAINTAIN: Create service line -> error SE 284)
Regards,
Raymond
10-06-2016 7:58 PM
Yes we looked into that OSS note but it is for a previous release/support pack and not valid for our system. I couldn't find any other OSS notes that fit. I have opened a ticket with SAP for a solution, seems to me the standard SAP is not working correctly at least in our systems.
07-04-2019 12:04 PM
Ryan Hannay,
Did you have any answer by SAP to fix your problem ? I have the same problem now... I found the note 2726182 but I can't implement it.
Thanks,
JC