Advertising:

Create wrapper for function modules and BAPIs: Difference between revisions

From SAP Knowledge Base
No edit summary
No edit summary
Line 1: Line 1:
{{#description2:Note why all code used in the future should be used at least as T2 code and how wrapping T3 code works quickly and easily manually, but with a generator.}}
[[Category:RESTful_application_programming]]
[[Category:RESTful_application_programming]]
There are good reasons to wrap a function module (BAPI).
There are good reasons to wrap a function module (BAPI).


On the one hand, to have the wrapped FuBa as Tier 2 code so that it can be exchanged with Tier 1 code if SAP offers a released cloud API or similar or to use the wrapped code to release it as Tier 1 in its SAP S/4HANA, SAP S/4HANA Cloud, private edition system.
On the one hand, to have the wrapped FM as Tier 2 code so that it can be exchanged with Tier 1 code if SAP offers a released cloud API or similar or to use the wrapped code to release it as Tier 1 in its SAP S/4HANA, SAP S/4HANA Cloud, private edition system.


On the other hand, to be able to use [[COMMIT-WORK_required_or_causing_FMs_(BAPIs)_and_classes_in_RAP|COMMIT-WORK required or causing Fubas (BAPIs)]] through the BGPF framework or through call destination 'NONE' in RAP framework if these modules are not called in the SAVE sequence.
On the other hand, to be able to use [[COMMIT-WORK_required_or_causing_FMs_(BAPIs)_and_classes_in_RAP|COMMIT-WORK required or causing Fubas (BAPIs)]] through the BGPF framework or through call destination 'NONE' in RAP framework if these modules are not called in the SAVE sequence.

Revision as of 12:11, 31 December 2024

There are good reasons to wrap a function module (BAPI).

On the one hand, to have the wrapped FM as Tier 2 code so that it can be exchanged with Tier 1 code if SAP offers a released cloud API or similar or to use the wrapped code to release it as Tier 1 in its SAP S/4HANA, SAP S/4HANA Cloud, private edition system.

On the other hand, to be able to use COMMIT-WORK required or causing Fubas (BAPIs) through the BGPF framework or through call destination 'NONE' in RAP framework if these modules are not called in the SAVE sequence.

It is helpful to use the generator of an SAP employee:

Alternatively, this can also be done manually:

This is a wiki created in the spare time of a private person working in the SAP ERP area. The aim is to collect knowledge for the own use. The wiki is maintained to the best of knowledge and belief.
All products shown, including in form of screenshots, belong to SAP SE. Their trademarks are, among others: SAP®,ABAP®,SAP Fiori®,SAP HANA®,SAP NetWeaver®,SAP® R/3®,SAP S/4HANA®,SAP S/4HANA® Cloud

Retrieved from "https://unirab.org/index.php?title=Create_wrapper_for_function_modules_and_BAPIs&oldid=666"