2017 Nov 13 2:23 PM
Hi,
Is there any SAP standard way to handle exceptions from a BOR method in the front office process configuration?
Eg Step 010
BOR : instln Method: CHANGEDIRECT
raises an exception
2017 Nov 13 2:57 PM
Tony - reading the program behind the BOR, you would need to account for all the exceptions listed in the method - e.g. not found, invalid key date, etc.:
CALL FUNCTION 'ISU_S_INSTLN_PROVIDE'
EXPORTING
x_anlage = object-key-number
x_keydate = keydate
x_wmode = '2'
x_prorate = prorate
x_no_dialog = 'X'
IMPORTING
y_obj = i_obj
y_auto = i_auto
EXCEPTIONS
not_found = 1
invalid_keydate = 2
foreign_lock = 3
not_authorized = 4
invalid_wmode = 5
general_fault = 6
OTHERS = 7.
2023 May 05 8:03 AM
Dear Tammy thank you for this. Can you explain me how I do this in the FOP?
Best Regards Davide
2017 Nov 15 11:00 AM
Thanks for the reply.
I actually came across a zmethod that was created previously that uses SWO_INVOKE and BALW_BAPIRETURN_GET1 to structure the error messages. I was able to use the data from this strucutre in the front office process logic.