Skip to Content
author's profile photo Former Member
Former Member

Hi!

Hi all!,

Can u plz send me the details of how to use the two or more function modules as a wrapper function modules...wht r the steps regarding these/...

Regards,

Sana.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 28, 2008 at 05:21 AM

    Only systems of mySAP Technology (that is: SAP_BASIS/SAP_ABA) release 4.5 or above can be called, because the data element BWAFCONT only exists for these releases. For releases 4.5 - 4.6C, the R/3 Plug-In needs to be applied to the system (PI 2001.1 or later).

    As wrapper functions typically are processed asynchronously by a batch user, the authority check of the wrapped function module will not fulfill its purpose. You should ALWAYS simulate the authority check for the user who created the data container. The user information can be taken from the data container.

    Wrapper functions can be called in any RFC connection maintained in table MEMAPPDEST. To call non-SAP systems, just use an RFC connection pointing to an SAP Business Connector and create an method on the SAP Business Connector that has the same interface as a wrapper function module.

    The generated coding may sometimes not be unicode-enabled. You'll need to modify the generated coding then.

    In order to minimize the data transport to the device, you can modify the generated coding in such a way that only relevant data is actually put into outbound containers. The same optimization could also be done by modifying or wrapping the wrapped function module directly.

    The Java skeletons generated by the MI Wizard can no longer be used. They do not conform to the Generic Sync API.

    The MI Wizard also generates entries for the table BWAFMAPP. These are integral part of your development and need to be transported.

    Wrapper functions will be called by the MI framework. They do not need to be RFC-enabled.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 28, 2008 at 05:09 AM

    Could you pls elaborate your requirement,.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 28, 2008 at 05:17 AM

    Follow this link:

    https://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/bapi_wrapper_types.html

    or

    go through this,

    General Rules of BAPI Wrapper

    For an ABAP function module to be a BAPI wrapper, certain rules (interface and behavior) need to be followed by each function module. Basically, any BAPI wrapper needs to cover the BAPI development rules (please see service.sap.com/bapi for detailed information on BAPI development rules); however, there are some BAPI wrapper specific development rules, that all types of BAPI wrappers must comply with:

    Rules for BAPI Wrappers

    • Processing type of a function module must be remote-enabled module.

    • Parameter named “RETURN” where the type is BAPIRET2 structure needs to be defined as either Export or Tables parameter

    • Parameters can only refer to either a structure or a field of a structure (<structure>-<field>)

    • Changing parameter can NOT be used

    • Exceptions can NOT be used

    • Parameters can NOT refer to structures that include other structures within: the reference structure needs to be a flat structure, and fields in the structure can NOT refer to types

    • Consistency within the business object must be ensured by defining Export/Import/Tables parameters of 5 types of BAPI wrappers appropriately

    • “Commit Work and Wait” needs to be executed in the update BAPI wrappers (Create/Change/Delete)

    Please also observe the following:

    • Whether “RETURN” parameter is defined as an Export or Tables parameter is typically determined by the “RETURN” parameter of the BAPI called in the BAPI wrapper.

    • The rule that BAPI wrapper parameters cannot refer to structures including other structures within is equivalent to the following rule in “BAPI Programming Guide”:

    • You must not use APPENDs and INCLUDEs in BAPI data structures.

    • The structures of Tables parameters in GetList and GetDetail functions will be the HEADER and ITEM structures of the SyncBO. Some of the fields in the table can be mapped to be the fields synchronized with the clients, while some other fields can be mapped to be the default fields, which will not be synchronized with the clients. There can be also fields that will not be mapped. Such fields will not be used either for data synchronization with clients or for BAPI wrapper function calls by Smart Synchronization. (For more information, refer to Defining SyncBO)

    • “Commit Work and Wait” is always required after the update logic is executed successfully within a Create, Change or Delete BAPI wrapper. Otherwise, “Rollback Work” is necessary. “Wait” is required because Smart Synchronization assumes that the updated values are already available when the function call is ended. (For additional information, refer to More about Commit Work and Wait)

    hope this would help u,

    dont forget to reward points

    kush

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.