topic Re: ale in Application Development and Automation Discussions

ale

Former Member — Thu, 01 Nov 2007 05:59:42 GMT

hi all,

i have to migrate all data ( eg fi documents , material movt documents ) from old sap system to new sap system using ale.

i would like to know what is the role of abbaper , the role of basis and the role of functional consultant in this scenario.

also would appreciate if some one could give step by step process to migrate material master doc or material novt doc from old sap system to new sap system using ale.

points would be rewarded to all.

rgds

Re: ale

Former Member — Thu, 01 Nov 2007 06:06:53 GMT

role of abbaper : write techanical specification, write the code to migrate the data ex LSMW ,BDC

the role of basis : Monitore process

the role of functional consultant:write functinal specification ,decide method for data transfer

For BDC:

http://myweb.dal.ca/hchinni/sap/bdc_home.htm

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&;

http://www.sap-img.com/abap/learning-bdc-programming.htm

http://www.sapdevelopment.co.uk/bdc/bdchome.htm

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm

http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html

Check these link:

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://www.sap-img.com/abap/question-about-bdc-program.htm

http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/

http://www.planetsap.com/bdc_main_page.htm

http://www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_DATADICTIONARY_FAQ.html

http://www.saptechnical.com/InterviewQ/interviewQ.htm

http://help.sap.com/saphelp_46c/helpdata/en/35/2cd77bd7705394e10000009b387c12/frameset.htm

Hope this will be useful...........

Minal

null

Re: ale

Former Member — Thu, 01 Nov 2007 06:11:05 GMT

see the ALE steps

Certain configuration like Port and Partner profile creation has to be done by Basis person and certain customizing setting is to done by fun consultant

and other technical things by the ABAP person

see the doc and Steps for ALE

Application Linking and Enabling (ALE)

In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients

For our purpose we have two clients

namely Client 100 and Client 200.

System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).

Distribution of Material Master Data Between two Systems

1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)

To do this follow the following steps

Execute SALE Transaction Code

On The Screen Click on Sending and Receiving Systems.

Then Click on Logical Systems.

Then Click Defining Logical Systems.

Click New Entries Button

(E.g. (LG100 sending system)

(LG200 receiving system))

Enter two logical system names and their description.

Save

Comeback to SALE Transaction Code screen.

2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)

LG100 assign to client 100

LG200 assign to client 200

To do this, do the following.

Click Assigning Client to Logical System.

Ignore the message that comes up on the screen.

Select client 100

Click details button on the toolbar icon or press F2.

In the logical system box, enter LG100.

Click on the save Icon

Click the back button.

Now select client 200.

Click details icon or press f2.

In logical Systems box, enter LG200.

Save

Back.

Comeback to SALE Transaction Code screen.

3) Maintain RFC Destination: (TR.CODE:SM59)

(Note: Do Not Create This Step)

Click Create Button on the Screen

On the Screen Maintain RFC Destination i.e LG200.

Enter LG200 in RFC destination box.

Connection type is 3

Give a description for the RFC destination.

Maintain Technical Settings on Details on Technical Settings tab

Target Host as : SAPKDC (NOTE: Save it as a Host Name)

Maintain Logon Details on Logon/Security tab.

Language: EN.

User: MMUSER200 (This is the logon for dist.)

Client : 200

Password: MM1234.

Save.

Click on create to do the above process for Client 200 in

The client 200 system.

4) Maintain Distribution Model.(BD64). (ABAPer role starts here)

Execute Maintain distribution model directly for

creating the model.

Click on change mode button on App tool bar of the Screen.

Create Model View pushbutton on App tool bar of the Screen.

A pop screen will appear in which you specify

Short text as Distribution for MM Data.

Enter Technical Name as LGMODEL.

Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.

A popup screen will appear in which you specify

Model View as LGMODEL.

Sender as LG100.

Receiver as LG200.

Again Click on Add Message Type Pushbutton on App toolbar of the Screen.

A popup screen will appear in which you specify

Model View as LGMODEL.

Sender as LG200.

Receiver as LG100.

SAVE.

On the same screen goto Menubar and select Environment.

And then select Generate Partner Profiles , then execute it.

On the Screen specify the Logical System as LG200.

Then execute the screen.

Click back.

Again On the same screen goto Menubar and select EDIT.

Again select Model View and then select Distribute.

****LOGIN to client 200.

Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.

And then select Generate Partner Profiles , then execute it.

On the Screen specify the Model View as LGMODEL

And Specify the Logical System as LG100.

Then execute the screen.

Click back.

*******Switch back to client 100 Session.

5) Create Material using MM03 Tr.Code.

Enter the material name as LGMATERIAL

Industry sector as Mechanical Engineering

Material Type as Finished Products.

And then Click on Data Pushbutton on the App tool bar.

Select views.

In the select views box for materials check basic data 1 AND 2.

Click enter icon.

In the next screen that you get

Give the text of the material as NEW MATERIAL.

Base unit of measure as KG.

Gross Weight as 200.

Net Weight as 100.

Weight Unit as KG.

In the description area language (E) and material description.

Click Save.

Now I Created a Material in Client 100 , I want to transfer this data to Client 200.

6) Execute BD10 to transfer the material in which you specify

the material as LGMATERIAL and

message type as MATMAS (client100).

Then a Screen will be displayed in which it shows that

1 Master Idoc Generated .. Enter

1 Communication Idoc Generated..Enter.

*******LOGIN to Client 200.

7) Execute BD11 to get the material in which you specify

the material as LGMATERIAL and

message type as MATMAS (client200).

😎 Execute Tr.code MM03 and give the material as LGMATERIAL

and see that the material is displayed as it was in Client 100.

If not follow these steps.

9) Execute Tr.code WE19( for rectification of errors in client200).

Specify the Existing Idoc Number and Executes it .

A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.

10) Execute Tr.code MM03 and give the material as LGMATERIAL

and see that the material is displayed as it was in Client 100.

Now the Material is correctly displayed in Client 200.

11) Monitoring of IDOCS.

Transaction Codes:

IDOC Display of Status: WE 05.

IDOC Date and Time: WE07.

Outbound:

Step 1. Application document is created when transaction is saved.

2. Message control is invoked.

3. Messages are processed by system.

4. Messages are Edited (if desired).

5. Output (ALE / EDI) is checked

6. Validate against Message control record from Partner Profile

7. Application Document is saved.

8. Entry NAST table is created for every selected output program

along with Medium & Timing.

9. Check for Process Immediately .

If (yes)

Determine Processing Program from TNAPR Table.

ELSE

Execute RSNASTED Program.

10. Read Partner Profile to determine Process Code.

11. Process Code points to the Function Module & Invoked.

12. IDoc is generated.

13. Check for ALE Request.

if (Yes)

Perform Filters, Conversions, Version Changes etc.

Else.

IDoc is stored in DATABASE.

INBOUND:

Step 1. EDI Subsystem creates an IDoc file from EDI Messages

2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.

3. Data in Control Record is validate against the Partner Profile.

4. IDoc is generated in Database and syntax check is carried out.

5. IDoc file is deleted once file read.

6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.

7. Check for Process Immediately.

If NO

Execute RBDAPP01 Program

Else

Read Process Code from Partner Profile

Process Code Points to Function Module

Application Document Posted.

further help:

check url

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapgenie.com/ale/configuration.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapdevelopment.co.uk/training

And also u can get lots of inof from the below link.

http://www.sapgenie.com/ale/why_ale.htm

Regards

Anji

Re: ale

Former Member — Thu, 01 Nov 2007 06:14:19 GMT

hi anji,

wht are the technical steps tht abapper has to perform & the steps which functional consultant has to prform plz write in more detail .

rgds.

points would be rewarded to all answers

Re: ale

paruchuri_nagesh — Thu, 01 Nov 2007 06:16:32 GMT

CATSDB CUSTOM IDOC TRANSFERMATION BETWEEN 2 DIFFERENT APPLICATION SERVERS

For this scenario Client 800 of application server SAPADM is the Sender and client 800 of application server SAP-REMOTE is the Receiver

1. Creating Logical Systems

o Login using 800 client

o Go to T. Code SALE

o Expand Sending and Receiving Systems

o Expand Logical Systems

o Click on Define Logical System

o Click on New Entries

o Create CATSSENDER, ECC Logical Systems

o Save and come back

o Assign the CATSSENDER Logical System to client 800 of Application Server SAPADMAssign the ECC Logical System to client 800 of Application Server SAP-REMOTE

2. Creating the RFCs

o Go to T. Code SM59

o Expand R/3 Connections

o Enter RFC Name as CATSSENDER

o Connection Type as 3

o Language as EN

o Client as 800

o User as SAPUSER

o Password as YESV13

o Target host as SAPADM

o Click on Remote logon button to test the RFC

o Enter RFC Name as ECC

o Connection Type as 3

o Language as EN

o Client as 800

o User as SAPUSER

o Password as YESV123

o Target host as SAPADM

o Click on Remote logon button to test the RFC

3. Creating the Message Type

o Go to T. Code WE81

o Click on change, continue

o Click on New Entries button

o Give message type as ZCATSTIME and description

o Save and back

4. Creating the Segment

o Go to T. Code WE31

o Give segment name as ZSEGMENTTIME

o Enter Short Text

o Enter the Field Name and Data Element in the text boxes

o Save, continue,

o Click on Edit -> Set Release

5. Creating the Basic IDOC Object

o Go to T. code WE30

o Give obj. name as ZTIMEIDOC

o Click on create

o Select create new radio button, give description and continue

o Select the IDOC obj name and click on create button

o Enter the segment name which is create earlier

o Select the check box if you want to make the segment mandatory

o Enter 1 in minimum number 99999 in maximum number, continue

o Save and backo Click on Edit -> Set Release

6. Creating Customer Distribution Model

o Go to T. Code BD64

o Click on change and Create model view button

o Enter the short text and Technical name as CATSSENDER

o Select the model and click on Add Message Type Button

o Give the Sender as CATSSENDER,

o Receiver as ECC,

o Message Type as ZCATSTIME

o Select the model view & click on Environment -> Generate Partner Profiles

o Select Transfer IDOC Immediately and Trigger Immediately radio buttons

o Click on Execute

o You should get a list in green color which means it executed successfully.

o Back to main screen, select the model view

o Click Edit->Model view->Distribute

o Click on continueo

You should get a list saying model view is distributed successfully.

7. Checking the Port

o Go to T. Code WE21

o Expand Transactional RFC

o Find the port from the list which is created using BD64 for ECC (Receiving system) RFC Destination.

8. Checking the Partner Profiles.

o Go to T. Code WE20

o Expand Partner Type LS

o Select the Partner profile ECC

o Double click on Message Type ZCATSTIME in Outbound parmtrs.

o Check Receiver Port is assigned correctlyo

Check the Basic type as your Basic IDOC object.

9. Assigning the Message Type to Basic IDOC Object

o Go to T. Code WE82

o Click on Change & continue, New Entries button

o Give the Message type as ZCATSTIME

o Give Basic Type as ZTIMEIDOC

o Release as 4.6C

o Save and back10. Creating Inbound Function Module (Posting Program)

o Go to T. Code SE37

o Create a function Module ZCATSDB_TIMESHEET_SURESH

o Set the Processing type as Remote Enabled Module and mode as start immed, in Attributes Tab.

o Import Parameters

P_WORKDATE LIKE CATSDB-WORKDATE

P_COUNTER LIKE CATSDB-COUNTER

P_LSTAR LIKE CATSDB-LSTAR

o Export Parameters

o Tables

S_PERNR LIKE ZCATSPERNR

[PERNR is select option parameters in ZCUSTOMIDOC report program so that it should be passed to function module ZCATSDB_TIMESHEET_SURESH in tables section. And also in tables section we used ZCATSPERNR, which is a global structure, which contains four fields as

Ø SIGN

Ø OPTION

Ø LOW

Ø HIGH]

o Exceptions

o Source Code

FUNCTION zcatsdb_timesheet_suresh.

*"----

""Local interface:

*" IMPORTING

*" VALUE(P_WORKDATE) LIKE CATSDB-WORKDATE

*" VALUE(P_COUNTER) LIKE CATSDB-COUNTER

*" VALUE(P_LSTAR) LIKE CATSDB-LSTAR

*" TABLES

*" S_PERNR STRUCTURE ZCATSPERNR

*"----

TABLES: catsdb, edidc, edidd. " using structures of catsdb, edidc, edidd

CONSTANTS: c_doctyp TYPE edidc-idoctp VALUE 'ZTIMEIDOC', " idoc type

c_segnam TYPE edidd-segnam VALUE 'ZSEGMENTTIME', "segment type

c_mestyp TYPE edidc-mestyp VALUE 'ZCATSTIME'. " message type

*001 comment begin

creating internal tables with out header lines for catsdb, edidc, edidd and also

- work areas

*001 comment end

DATA: it_edidc TYPE edidc OCCURS 0, " control internal table with out header line

it_edidd TYPE edidd OCCURS 0, " data internal table with out header line

wa_catsdb TYPE it_catsdb1, " work area for it_catsdb internal table

wa_edidc TYPE edidc, " work area for it_edidc internal table

wa_edidd TYPE edidd, " work area for it_edidd internal table

wa_zsegmenttime TYPE zsegmenttime, " work area for zsegment internal table

v_occmax TYPE idocsyn-occmax,

v_nbseg TYPE i.

CLEAR wa_catsdb. " clears work area of catsdb

CLEAR wa_edidc. " clears edidc work area

*002 comment begin

Save the message type and the basic IDoc type in the control segment.

*002 comment end

MOVE c_mestyp TO wa_edidc-mestyp. " assigning custom message type to edidc workarea

MOVE c_doctyp TO wa_edidc-idoctp. " assigning custom idoc type to edidc workarea

*003 comment begin

Retrieve the maximum number of segments in the basic IDoc type.

*003 comment end

SELECT MIN( occmax ) FROM idocsyn INTO v_occmax WHERE idoctyp EQ c_doctyp AND segtyp EQ c_segnam.

*004 comment begin

Save the whole CATSDB table content in the IT_ZCATSDB internal table.

*004 comment end

SELECT pernr workdate lstar counter FROM catsdb INTO CORRESPONDING FIELDS OF TABLE it_catsdb WHERE pernr IN s_pernr AND workdate EQ p_workdate.

*005 comment begin

Create a data segment for each line of IT_ZCATSDB.

*005 comment end

IF sy-subrc EQ 0.

LOOP AT it_catsdb INTO wa_catsdb WHERE pernr IN s_pernr.

MOVE-CORRESPONDING wa_catsdb TO wa_zsegmenttime.

CLEAR wa_edidd.

MOVE c_segnam TO wa_edidd-segnam.

MOVE wa_zsegmenttime TO wa_edidd-sdata.

APPEND wa_edidd TO it_edidd.

CLEAR wa_catsdb.

CLEAR wa_zsegmenttime.

ENDLOOP.

ELSE.

MESSAGE 'NO DATA FOUND FOR GIVEN SELECTION' TYPE 'I'.

ENDIF.

*006 comment begin

Count the number of data segments.

*006 comment end

DESCRIBE TABLE it_edidd LINES v_nbseg.

*007 comment begin

If the number of data segments exceeds the maximum allowed number,then display an error message.

*007 comment end

IF v_nbseg GT v_occmax.

MESSAGE 'IDOC ERROR Message' TYPE 'E000'.

ENDIF.

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' " for creating an catsdb idoc

EXPORTING

master_idoc_control = wa_edidc

OBJ_TYPE = ''
CHNUM = ''

TABLES

communication_idoc_control = it_edidc

master_idoc_data = it_edidd

EXCEPTIONS

error_in_idoc_control = 1

error_writing_idoc_status = 2

error_in_idoc_data = 3

sending_logical_system_unknown = 4

OTHERS = 5

IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.

ENDFUNCTION.

Save, check and activate

111. Assigning the Inbound Function Module to Basic Type & Message Type

o Go to T. Code WE57

o Click on change, continue, continue and New Entries Button

o Enter the Module as ZCATSDB_TIMESHEET_SURESH Type as "F"

o Basic Type as ZTIMEIDOC

o Message Type as ZCATSTIME

o Direction as 2

o Save and back

Now Login in 800 client of Application Server SAP-REMOTE

12. Assigning the Inbound Function Module in ALE Table

o Go to T. Code BD51

o Click on continue, New Entries button

o Give the Inbound Function Module ZCATSDB_TIMESHEET_SURESH

o Give Input t. as 0 (zero)

o Save and back13. Creating Process Code

o Go to T. Code WE42

o Click on Change, New Entries Button

o Give Process Code name as ZCATSDB, give Description & Save

o Select Processing with ALE Services Radio button

o Select Processing by Function Module Radio button

o Click the ALE Table (arrow Icon) in Identification

o Give the Function Module Name ZIDOC_INPUT_ZBAPI_STUD_MAS

o Give maximum number of repeats 0

o Save and back, back

o Select the process code from the list & click on Logical Messages Icon

o Give the Message Type as ZCATSTIME

o Save & Back, Save & Back, Save & Back

14. Changing the Customer Distribution model in receiving system

o Go to T. Code BD64

o Click on change and Create model view button

o Enter the short text and Technical name as CATSECC

o Select the model view & click on Environment -> Generate Partner Profiles

o Select Transfer IDOC Immediately and Trigger Immediately radio buttonso Click on Execute You should get a list in green color which means it executed successfully.15. Assigning the Process Code to Message Type in Receiving System

o Go to T. Code WE20

o Expand Partner Type LS

o Select the Partner Profile CATSSENDER

o Double click on Message Type ZCATSTIME in Inbound parmtrs.

o Give the Process Code as ZCATSDB

o Click on Trigger Immediately Radio button

o Save & Back

Save & Back

16. Creating the Selection Program (Outbound Program)

- Login in client 800.

- Go to T. Code SE38

- Create a Report Program as ZCUSTOMIDOC with the following code

REPORT ZCUSTOMIDOC

NO STANDARD PAGE HEADING.

TABLES:catsdb. " using structure of cats db table

*000 comment begin

this selection screen contains one select option and one parameter

*000 comment end

SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.

SELECT-OPTIONS pernr FOR catsdb-pernr.

PARAMETER: workdate LIKE catsdb-workdate,

LSTAR like catsdb-LSTAR,

COUNTER like catsdb-counter.

SELECTION-SCREEN: END OF BLOCK b1 .

DATA: wa_val TYPE i.

wa_val = pernr-high - pernr-low.

*001 comment begin

calling custom function module

*001 comment end

CALL FUNCTION 'ZCATSDB_TIMESHEET_SURESH'

EXPORTING

p_workdate = workdate " passing workdate parameter

p_LSTAR = LSTAR

p_counter = counter

TABLES

s_pernr = pernr. " passing pernr select option

IF sy-subrc EQ 0.

MESSAGE i000(zaluri) WITH 'IDOCS CREATED FOR EMPLOYEES BETWEEN' pernr-low ' AND ' pernr-high .

MESSAGE i000(zaluri) WITH 'IDOCS CREATED FOR EMPLOYEES BETWEEN' PERNR-LOW 'TO' PERNR-HIGH.
gives information message if idocs are created for given employees

ELSE.

MESSAGE e000(zaluri) WITH 'NO IDOCS CREATED FOR EMPLOYEES' pernr-low 'TO' pernr-high. " gives error message

" if idoc is not created

17. Transferring the CATSDB records from sender Application Server SAPADM to receiver Application Server SAP-REMOTE

- Execute Report Program ZCUSTOMIDOC

- Give the Range of PERSONNEL NO'S, Date, Activity Type, Counter to Transfer

- Give Message Type as ZCATSTIME

- Give Receiver Logical system as ECC

- Execute

- You should get the IDOC Number

- Take the IDOC Number and go to T. Code WE05 & Execute

- In Outbox you can see the IDOC Status

- Select the status record in left side window

- Double click on the Status record in right side window- You can see the Control Record, Data Record and Status Records for that IDOC

If the ICON is green and the status code is 3, it means the IDOC is passed to PORT Successfully

18. SENDING IDOCS FROM APPLICATION SERVER SAPADM

TO APPLICATION SERVER SAP-REMOTE USING WEDI

- Go to T. Code WEDI & execute or T. Code WE19

- Give idoc number it is generated recently

- Continue & double click on segment to view data in segment

- Click on EDIDC to give port, partner no, message type, partner

type of receiver. [For sender no need to give any port no leave it as

blank]

- Click on Standard Outbound Processing button and click continue

- You will get a message as idocs successfully transferred

Now Login in Receiver 800 client

- Go to T. Code WE05 & Execute

- You can see the status record in left side window

- If the status no is 53 and color is green, it means the IDOC is posted to Application successfully.

- You can see the Log Information by double clicking on the status record in right side window.

- Now in left side window, you can see the Control Record, Data Record & Status Record of the IDOC

- Now go to T. Code SE16

- Give the table name CATSDB & press F7

- See the contents of the table

- The table is updated with the catsdb records transferred from 800 client with our selection program.

regards

Nagesh.Paruchuri