‎2008 Mar 31 7:37 PM
BAPI is processed without returning any screen dialogs to the calling application.
But there are some released BAPIs provided by SAP like BAPI_CUSTOMER_EDIT, in which statement CALL TRANSACTION 'XD02', causes screen return to the user.
This prevents it to be used in background, to be called from some external system application.
What is that in these BAPIs that makes it different with any other normal function module which has user interface?
G@urav.
‎2008 Mar 31 9:06 PM
Hi,
Keep in mind the history of BAPI's. Originally, Business Objects and BAPI's were created for Business Workflow, not for the outside world. Often there are existing BAPI's that send screens (for workflow), but BAPI's outside of workflow should only send back info, not screens. The original BAPI's did not have this restriction.
As for BAPI_CUSTOMER_EDIT it may be worth noting that this function module was one of the early BAPI's (R/3 release 3.0A). Also worth noting: In the BAPI browswer (transaction BAPI) there is a "Dialog" checkbox in the "Method (BAPI)" details screen. The checkbox is on for BAPI's that use "call transaction/screens" and off for the other BAPI's.
Regards,
Jamie
‎2008 Mar 31 8:39 PM
any suggestions..
Is it allowed to call screens in BAPI?
G@urav.
‎2008 Mar 31 9:06 PM
Hi,
Keep in mind the history of BAPI's. Originally, Business Objects and BAPI's were created for Business Workflow, not for the outside world. Often there are existing BAPI's that send screens (for workflow), but BAPI's outside of workflow should only send back info, not screens. The original BAPI's did not have this restriction.
As for BAPI_CUSTOMER_EDIT it may be worth noting that this function module was one of the early BAPI's (R/3 release 3.0A). Also worth noting: In the BAPI browswer (transaction BAPI) there is a "Dialog" checkbox in the "Method (BAPI)" details screen. The checkbox is on for BAPI's that use "call transaction/screens" and off for the other BAPI's.
Regards,
Jamie