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

BAdi implementation(appl transfer)

hi mates,

Is it compulsory to implement BADI implementation for transferrting data from one appl to other? Can i do transfer just by using script logic without going for BADI implementation?

If BADI implementation is compulsory, do i need to create multiple BADI implemenations for different trasnfer of data among mulitple applications?

THanks

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Sep 12, 2010 at 05:36 PM

    Hi Naresh,

    If the *DESTINATION_APP script meets your needs, then there is no need to write a BADI. You can find documentation on this script logic statement here: [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/f4/33f0bbc46c4a53860f1410f20ffb8b/frameset.htm]

    There is a lot that *DESTINATION_APP doesn't do (I think Dries just brought up one of the more nuanced problems with the BADI on this forum, but there are others as well). If you need something beyond the capabilities of this script logic statement to push data from one application to another, then you will need to create a custom BADI. There is a How To Guide that provides a BADI called DEST_APP, which would be a good starting point.

    Another option is to use transformation files to pull data from one application to another using Data Manager using the InfoProvider Load package. Sometimes this is easier than implementing a BADI.

    Ethan

    Add a comment
    10|10000 characters needed characters exceeded

    • Yes, you are correct. Since *DESTINATION_APP doesn't exist in BPC NW 7.0, you must use a BADI if you want to transfer data between applications from script logic in this version of the product. The How To guide with the BADI is here: [http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e04b5d24-085f-2c10-d5a2-c1153a9f9346] Even if it doesn't completely fit your requirements, it is a good starting point.

      Using transformation files and the Load InfoProvider data manager package works fine in BPC NW 7.0. You do need to use the BW technical names of the InfoCube and InfoObjects in the transformation file. You can find these in the RSA1 transaction code in BW (make sure to get the InfoObject technical names and not the Dimension technical names when you are looking at the InfoCube - you need to open up the dimension folders to see the InfoObjects). The technical names aren't pretty, but they will work! If it suits your needs, this is a good solution that avoids the need to maintain an ABAP BADI.

      Ethan

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.