topic Problem with Inbound in Application Development and Automation Discussions

Problem with Inbound

Former Member — Fri, 27 Apr 2007 13:23:11 GMT

Dear All,

I am new to ALE. I created ALE config in two different R/3 systems. After triggering ALE, I got message in Out bound as 1 i.e, Idoc generated. When I saw in Inbound systems, I got 52,62,64 and finally 50 status. Its showing as Application document not completely posted. What action I have to take further.

Regards,

Chandra.

Re: Problem with Inbound

Former Member — Fri, 27 Apr 2007 13:32:32 GMT

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

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

Re: Problem with Inbound

Former Member — Fri, 27 Apr 2007 13:33:46 GMT

Hi CSY,

ALE or Application Link Enabling ensures a distributed but integrated SAP installation. It comprises the controlled exchange of business messages and consistent data management in loosely-linked SAP application systems. ALE is point to point mainly used for integrating SAP systems and capable of creating a dialogue only between a pair of systems

For the ALE process steps you need do the following:

1) Creating the Logical System in Application Server(trnx SALE).

2)Assigning the Clients to the Logical systems(Trnx SALE).

3) Create a distribution model for the IDOC(trnx BD64)

4)Create an RFC desination for the XI(trnx SM59).

5)Create a tRFC port (trnx WE21).

6)Create partner profile (trnx WE20).

pls refer to

http://help.sap.com/saphelp_nw04/helpdata/en/b3/4bf60b4bab1343a03c004d2cb3566d/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/43/ce993b45cb0a85e10000000a1553f6/frameset.htm

Steps(ALE SETTINGS) have a look at this link..

and pls see the below links