cancel
Showing results for 
Search instead for 
Did you mean: 

BAdi implementation(appl transfer)

Former Member
0 Kudos

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

Accepted Solutions (1)

Accepted Solutions (1)

esjewett
Active Contributor
0 Kudos

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

Former Member
0 Kudos

Thanks Ethan for your reply.

Is SAP made any enhancement related to syntax *DESTINATION_APP between 7.0NW & 7.5 NW?

THanks

esjewett
Active Contributor
0 Kudos

Hi Naresh,

Yes, *DESTINATION_APP is new in BPC NW 7.5. It did not exist in 7.0. Before 7.5 was finished, SAP provided the DEST_APP BADI How To guide for use in 7.0 as an interim solution, but in fact it works differently and may still meet use-cases that *DESTINATION_APP does not.

Ethan

Former Member
0 Kudos

Hi Ethan,

Just talk about *DESTINATION_APP syntax for BPC70 NW version. Is it compulsory to implement BADI implementation for data transfer between applications? Can it possible to transfer data between applications just by script logic?

One more option seems to be transformation file(Load Infoprovider data package)(as you said: is it works for BPC70NW)?

THanks

esjewett
Active Contributor
0 Kudos

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

Answers (0)