topic Re: EDi,ALE,BAPI,BADIS in Application Development and Automation Discussions

Each BAdI has a definition and more than one implementation. The definition means the methods(in class concept) that are used for performing various functions. The BAdI definition can be viewed in SE18 transaction(for standard ones) and user-defined BAdIs can be created in the same transaction as well.

When you create a BAdI definition, an class interface will be automatically created and you can define your methods in the interface. The implementation of the methods can be done in SE19 transaction .

YOu can go through these links...

http://esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf

http://esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt

http://esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc

http://esnips.com/doc/1e10392e-64d8-4181-b2a5-5f04d8f87839/badi.doc

http://esnips.com/doc/365d4c4d-9fcb-4189-85fd-866b7bf25257/customer-exits--badi.zip

http://esnips.com/doc/3b7bbc09-c095-45a0-9e89-91f2f86ee8e9/BADI-Introduction.ppt

Regards,

Ranjit Thakur.

Please Mark The Helpful Answer.

Re: EDi,ALE,BAPI,BADIS

Former Member — Wed, 02 May 2007 14:33:04 GMT

Hi suneel

check out the following steps for ALE creation

Do below thing in client 100

Step – 1

T-Code: SALE

Application link Enabling -> Sending and Receiving Systems->Logical systems->Define Logical System.

We have created two logical systems.

1) MAN100

2) MAN500

Step – 2

T-Code: SALE

Application link Enabling -> Sending and Receiving Systems->Logical systems->Assign Client to Logical Systems.

Double click on client 100

Logical Systems : MAN100

Double Click on 500

Logical System : MAN500

Step – 3

Tcode: SM59 (RFC Destination settings)

Keep curser on R/3 Connections

Application tool bar Create button

RFC destination : MAN500

Connections type : 3

Description : Connect to client 500

Logon/Security : Tab

Technical Settings : tab

Target Host : IP(10.112.30.28) or Host name (mcgenp)

Step – 4

Tcode: WE21 (Port Creation)

Keep cursor on Transactional RFC then create button on app. Tool bar.

Popup menu will be displayed just click on tick mark (System Generates port)

Description : Port to connect 500 Client

Radio button Idoc record types SAP Release 4.x.

RFC Destination : MAN500

Step – 5

Tcode: WE20 ( Create Partner Profiles)

Partner Profiles -> Partner type LS

Place the cursor on Partner Type LS then App. Tool bar create button

i) To crate partner Profile for logical system 100 (MAN100)

Partner No. : MAN100 (Logical system name)

Partn.Type : LS

Post processing: permitted agent tab

Typ : US

Agent: ABAP(User name)

Lang: EN

Press Save button

Create Partner Profile for MAH500

a) Out bound Parameters

Message type : MATMAS

b) Out bound parameters

Message type : SYNCH

c) Inbound Parameters

after doing Partner profiles for MAN500 the screen look like this

Do below thing in client 500

Tcode: SM59

Create RFC destination for MAN100

Technical settings: id add. And system no.

Tcode: WE21

Create port

Tcode: WE20

i) to crate partner profile for MAN100

for this here it needs out bound and inbound parameters.

Out bound Parameters with message type : SYNCH

Inbound Parameters with message type : MATMAS

ii) to create partner profile for MAN500

for this here it needs only inbound parameters.

Inbound Parameters with message type : MATMAS

Do below thing in client 100

Tcode: BD64 (Create Distribution Model View)

Click on change button on App. Tool bar

Keep cursor on Model Views then Create Model view button(application tool bar)

click on tick mart

place the cursor on Model view which you have created: MOD_MAN

Then click on Add Message type Button on Application tool Bar.

click on tick mark

Save button

Menu bar:

Environment -> Generate Partner Profiles

In this screen

Model View : MOD_MAN

Partner System: MAN500

Automatically these will be appeared:

US : User

ABAP : abap developer

3 : Idoc record types from Version 4.0

100

Then click on Execute button

Click back button two times.

Keep cursor on Model view MOD_MAN (Model view name)

Main menu ->Edit -> Model View ->Distribute

Click tick mark.

Do the following steps in client 500

Tcode: BD64

Place the cursor on Model view : MOD_MAN

Main menu -> Environment -> Generate partner Profile

Click on Execute button

Do this in 100 client

Tcode: BD10 (To send Material to 500 system from 100)

Tcode: WE05 (To See Generated Idoc)

Execute

Do this in 500 client

Tcode: WE05

Execute

Re: EDi,ALE,BAPI,BADIS

Former Member — Wed, 02 May 2007 16:08:58 GMT

hi,

Thanks for ur help, u gave me step by step, its great advantage for me, can u give me steps like edi, bapi and badi also.

Thanking u

suneel.

Re: EDi,ALE,BAPI,BADIS

Former Member — Thu, 03 May 2007 16:13:13 GMT

hi sunnel

just check the following steps for BAPI and let me know if it is useful

BAPI Step by step Guidance

BAPI stands for Business Application Programming Interface.

There are 5 different steps in BAPI.

- Create BAPI Structure

- Create BAPI Function Module or API Method.

- Create BAPI object

- Release BAPI Function Module.

- Release BAPI object.

Step1.

Creating BAPI Structure:

- Go to <SE11>.

- Select Data Type & Enter a name.

- Click on Create.

- Note: Always BAPI should be in a development class with request number (Not Local Object).

- Select Structure & hit ENTER.

- Enter the fields from your database. Make sure that the first field is the Primary Key Field.

- Then SAVE & ACTIVATE.

Step 2.

Creating BAPI module:

- Enter TR.CODE <SE37>.

- Before entering any thing, from the present screen that you are in, select the menu

Goto -> Function Groups -> Create Group.

Enter a name (Note: This name Must start with ZBAPI)

Let this screen be as it is and open another window and there, enter TR.CODE <SE80).

Click on the Third ICON that says Inactive Objects.

Select the group that you just created and click on Activate.

Notice that the group you created will disappear from the list of inactive objects.

- Go back to <SE37> screen and enter a name and hit <ENTER>. Then enter the group name that you just created and activated.

NOTE: When you release a function module the respective group will be attached to that particular application. It cannot be used for any other application. NEVER include an already existing group that is attached to another module.

Now click on the first Tab that says [ATTRIBUTES] and select the radio button that says remote-enabled module since we will be accessing this from any external system.

Then click on the second tab that says [IMPORT].

Enter a PARAMETER NAME, TYPE and the structure you created in the first step. Also select the check box ‘Pa’. All remotely enabled functional modules MUST be Pa enabled, where Pa means ‘Passed by Value’ and if you don’t select ‘Pa’, then that means it will be passed by reference..

Then click on tab that says [EXPORT].

Enter the following as is in the first three fields

RETURN TYPE BAPIRETURN (These 3 field values are always same)

Here also select ‘Pa’ meaning Pass by value.

Note: BAPIRETURN contains structure with message fields.

Then SAVE and ACTIVATE.

Step 3.

Creating BAPI object:

- Enter Tr.Code <SWO1> (Note. It is letter ‘O’ and not Zero).

- Enter a name and then click on create. Enter details.

NOTE: Make sure that that Object Type and Program name are SAME.

- Enter Application ‘M’, if you are using standard table Mara. If you are using your own database then select ‘Z’ at the bottom.

- Then hit <ENTER>.

- Now we have to add ‘Methods’. High light METHODS and then select the following from the menu:

Goto Utilities -> API Methods -> Add Methods.

- Enter function Module name and hit <ENTER>.

- Select the second FORWARD ARROW button (>)to go to next step.

- Check if every thing looks ok and again click on FORWARD ARROW button (>).

- Then select ‘YES’ and click on <SAVE>.

- Now on a different screen goto TR.CODE <SE37>. Enter Function Module name and select from the top menu Function Module -> Release -> Release.

- Goback to TR.CODE <SWO1>.

Here select the menu combination shown below in the same order.

- Edit -> Change Release Status -> Object Type Component -> To Implemented.

- Edit -> Change Release Status -> Object Type Component -> To Released.

- Edit -> Change Release Status -> Object Type -> To Implemented.

- Edit -> Change Release Status -> Object Type -> To Released.

- Then click on <SAVE>.

- Then click on Generate Button (4th button from left hand side looks like spinning wheel).

- Then Click on the button that says ‘PROGRAM’ to see the source code.

To check if this is present in work flow goto TR.CODE <BAPI>.

Here it shows business object repository.

- First click on the middle button and then select “ALL” and hit ENTER.

- Goto tab [ALPHABETICAL] and look for the object that you created. This shows that the BAPI object has been created successfully.

Re: EDi,ALE,BAPI,BADIS

Former Member — Thu, 03 May 2007 16:43:21 GMT

hi,

thanks for ur reply, i am unable to assign 10 points to u, bec i already assigned , that why its showing. u have me very good reply.

can u give me steps for badis with any scenerio and edi also.

Thanking u

suneel.