Extending a standard fetch BAPI (for equipment) in SAP Work Manager application

[Former Member]

Hi Experts,

I am trying to extend a particular fetch BAPI (EquipmentFetchBapi) to include a custom functionality, but I couldnt find any parameter in the config panel to set so.

In the config panel, I see that the BAPI class - com.syclo.sap.component.equipment.bapi.EquipmentFetchBapi has been assigned under the parameter group "BAPI_WRAPPER" and the parameter value is set to the FM under ECC.

Now, when the workOrderFetchBapi calls the equipmentFetchBapi to get the data from ECC, my requirement is to call the custom class (CustEquipmentFetchBapi) instead of standard one.

I see that the workOrderFetchBapi doesn't make use of Object factory while calling equipmentFetchBapi and that's why parameter configuration at ECC side wont be helpful.

Is there any other way I can enhance the equipmentFetchBapi/workOrderFetchBapi  so that the workOrderFetch bapi will call my customEquipmentFetchBapi?

Any help will be appreciated.

[jason_latko · Accepted solution]

Arihant,

You are correct that this is an extension problem in the older code.  This has been changed in the newest releases of Agentry based products so that BAPI classes are instantiated using a factory and config panel settings just like the base POJOs are.  I would suggest extending the WorkorderFetchBAPI and other classes that may call it so you can modify the code that calls EquipmentFetchBAPI to point to your new extended version of this class.  You could also upgrade to WM 6.1 where the BAPI factory has been implemented as well.

Jason Latko - Senior Product Developer at SAP