Logical systems for ALE

[Former Member]

HI all,

I'm configuring for an IDoc to be generated and downloaded to a file via a file port.

This IDoc is of message type PAYEXT.

The file is to be sent ot the bank via the meansa of third party software.

Do I have to create logical systems for these? Or only the outbound logical system?

Do I also need to set up the distribution model , and if so, how far do i need to set it up?

Points wil be awarded. Thanks!

[Former Member]

HI all,

I'm configuring for an IDoc to be generated and downloaded to a file via a file port.

This IDoc is of message type PAYEXT.

The file is to be sent ot the bank via the meansa of third party software.

Do I have to create logical systems for these? Or only the outbound logical system?

Do I also need to set up the distribution model , and if so, how far do i need to set it up?

Points wil be awarded. Thanks!

[Former Member]

hi kevin

yes u need to create logical system and distribution model.

u will have to define logical system in the partner profile in the distribution model as well.

regards

swati

<b>plz dont forget to reward points if helpful</b>

[Former Member]

Hi

Thanks for your reply

my question was more of,

do I need to create a "destination" logical system as well?

Or do i just create 1 logical system (i.e. source system)

This is because we're downloading the idoc to a file and transferring it manually using a third party ftp style program.

[Former Member]

Hi

Use BD64 Tcode to setup distribution Model

Define the 2 logical systems.

see the flow:

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

Reward points if useful

Regards

Anji

[Former Member]

hi,

for creating ale logical systems Transaction code is SALE.

navigation

sale ->click on sending & receiving system -> logical system ->define logical system ( expand logical system) -> continue -> new entries ->

clck oncreate request -> save ->

ii. click on assignment client -> double click on sender -> give logical system sender -> back ->double click on receiver -> giv logical system reveiver.

for distribution model create a partner profile [BD64]

bd64 -> click change -> create new model view -> giv short desc, technical name -> select model view -> click on add message type.

if helpful reward some points.

with regards,

suresh.