ALE IDOC Tutorials and step by step guide:

http://sap-interview-questions-and-answers.blogspot.in/2012/05/sap-ale-idocs-interview-questions-and.html

http://www.globalguideline.com/interview_questions/Questions.php?sc=SAP_ALE_IDocs

http://www.riyaz.net/sap/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/18/

All the objects created should be present on both source as well as target system(s).
Step 1 :
Create Segment:  Tcode WE31

Step2: Create Basic IDoc type – Transaction WE30

Step3: Create Message Type in WE81

Step4: Link Message Type and Idoc Type in WE82

Step4:Define Logical Systems and Assign Client to Logical System – Transaction SALE

Step5:Maintain RFC Destinations – Transaction SM59

Step6:Define Ports – Transaction WE21
Step7:Maintain Distribution Model – Transaction BD64

Step8: 

To generate Partner profiles automatically you may use BD82 or go to BD64 and use the menu path Environment -> Generate partner profiles

• Otherwise, you may use transaction WE20 to create a partner profile

ALE IDOC part4: WE21 port configuration

What is a Port ? What are the types of Ports ?
A port is a communication channel through which Messages can be sent or received in SAP .
The sender and the receiver both specify the port through which they will communicate.

The common port types are the TRFC Port and the File Port.
If both sender and receiver mention TRFC ports, data is exchanged via RFC connections.
If however , a file port is mentioned , the IDOC is written in a flat file at the specified location at the sender system.Then a FTP transfer should be done from that location to the receiver system or a Middleware that will send the file to the receiver system.

The transaction to maintain ports is WE21.

SM59:

RFC Destination:

ALE Idoc part3: Partner profile WE20

What is a partner profile ? What are the types of partner profiles ?

To be able to communicate with a partner via an IDoc interface, each system needs to maintain a partner profile. A partner profile is a mechanism by which the system can specify what kind of messages (message types) it can send or receive.
Partner profiles can be maintained in WE20.

ALE IDOC part2: WE19- Test Inbound Idoc and we09-display all idoc and BD20 to run inbound Idoc after message 64

1. WE19 Tcode is used to test Inbound IDOC Manaully.

Take existing Idoc number from we02 or we09 .

After execution Manually feed data.

After that press marked area.

After taht below screen will come . we can debug via marked Function Module

WE09 will display all the IDOCs

2. BD20 (program RBDAPP01) usually is used to process inbound IDoc(s) for both running in the foreground and background (schedule a job).

BD87 is used to reprocess IDoc(s) in error or waiting for action for both inbound and outbound. Also it can be used to monior the IDocs as well.

Screenshot for BD20 Tcode:

ALE , IDOC part1Concepts : Tutorials WE02 and BD87- Staus monitor for ALE messages(INBOUND) and BD88(outbound) - Part1

What is ALE ?
ALE stands for Application Link Enabling. As it's name indicates , it links two systems.
ALE is a technology that can enable exchange of data between two different Systems ( Sap - Sap OR Sap - Non Sap). ALE technology enables distributed yet integrated installation of SAP systems.
ALE architecture comprises of 3 layers : 

Application layer refers to the application data ( SD , MM , FI or data for any SAP application ) . In this layer the data is collected to be distributed and then sent to the distribution layer.

Distribution layer determines to whom should the data generated by the application layer has to be distributed i.e. it is in the distribution layer that the recipient is determined , the data is formatted or filtered and then an actual is created.

Communication layer takes the responsibility of delivering the Idoc to the receiving system and communicates to the receiving system via tRFC , File ports , FTP or TCP/IP etc.



ALE uses IDoc as a vehicle to transfer data between two systems.



1.To display Runned Idoc List:

WE02 is used to check the inbound and outbound IDOCs.

2. To display Status Monitor for ALE messages:

Where all the Idocs get stored after creation?

EDIDC stores control/header record.
EDIDD/EDID4 stores data records.
EDIDS stores status records. 


What are the types of records in SAP ALE Idocs and where is this information stored ?
There are three types of records in SAP ALE Idocs:
Control Records: Control record information for an IDoc is stored in standard table EDIDC.
Data Records:     Control record information for an IDoc is stored in standard table EDIDD.
Status Records:   Control record information for an IDoc is stored in standard table EDIDS.

But here are a few that you should know:
0-49 indicates an Outbound IDoc and 50-75 as Inbound IDoc. 

01  IDoc generated
02  Error passing data to port
03  Data passed to port OK

51  Application document not posted
52  Application document not fully posted
53  Application document posted

IDoc+Statuses Messages

PI Process Integration or Process Orchestration System (INBOUND Interface)-Part5(Communication Channel)- Integrated Configuration:

Step1:

Step2:

Step3:

Step4:

Step5:

PI Process Integration or Process Orchestration System (INBOUND Interface)-Part5(Communication Channel)- Module Configuration

Process Sequence for Module for Inbound Communication Channel:

Number   Module name                                                         Type 

1.              AF_Modules/MessageTransformBean              Local Enterprise Bean

Module Key

Plain2XML

Number   Module name                                                         Type 

2.              localejbs/CallSapAdapter                                Local Enterprise Bean

Module Key

entry



Module Configuration for Inbound Communication Channel:

Module Key       Parameter Name                Parameter Value

Plain2XML      Transform.Class                  com.sap.aii.messaging.adapter.Conversion

Plain2XML       Transform.ContentType      text/xml;charset=utf-8

Plain2XML      xml.Header.fieldNames      vbeln,posnr,matnr,maktx,meins,waerk,zmeng,proj

Plain2XML     xml.Header.fieldSeparator    '0x2C'

Plain2XML      xml.conversionType             StructPlain2XML

Plain2XML      xml.documentName             MT_ALCON_II1

Plain2XML       xml.documentNamespace      http://csscorp.com/Alcon/II1

Plain2XML      xml.documentSkipFirstRows           1

Plain2XML       xml.ignoreRecordsetName          'true'

Plain2XML      xml.recordsetStructure            Header,1

OutBound communication Channel Parameters in PI

Processing Sequence for Outbound Communication Channel:

Number      Module Name                                                                    Type                                                
1                  localejbs/AF_Modules/MessageTransformBean        Local Enterprise Bean


Module Key

XML2Plain

Number      Module Name                                                                    Type                                                
2                  localejbs/ModuleProcessorExitBean                        Local Enterprise Bean


Module Key

exit


Module Configuration  for Outbound Communication Channel:

Module Key        Parameter Name                          Parameter Value

XML2Plain          Transform.Class                      com.sap.aii.messaging.adapter.Conversion
    
XML2Plain          Transform.ContentType          text/xml;charset=utf-8

XML2Plain         xml.addHeaderLine                 0

XML2Plain        xml.conversionType              SimpleXML2Plain

XML2Plain        xml.fieldSeparator              '0x2C'

exit                    JNDIName         deployedAdapters/com.sap.aii.adapter.sftp.ra/shareable/com.sap.aii.adapter.sftp.ra

PI Tutorials:

Links:
https://blogs.sap.com/2014/09/25/soap-with-xi-30-message-protocol/

https://blogs.sap.com/2014/07/04/video-tutorials-for-sap-process-orchestration/
https://blogs.sap.com/2013/05/21/sap-pi-for-beginners/



Important Tcode:
Sproxy - Proxy Creation,
SM59 - RFC Creation,
A)PO Configuration for Advanced Adaptor Engine ( AAE Engine )(G-HTTP Connection to External Server)
Gave as administrator username and Password Username: Administrator (PI Administrator User)
Target Host: PI host
Service No: PI port number
Path Prefix: /XISOAPAdapter/MessageServlet?ximessage=true

B)HTTP Connection to Connect SAP R/3 to SAP XI (H- Http connection to ABAP System)
 Gave us Java connector username and password for basic authentication client:120 username: JCOUSER ( Abap user from SU01 Tcode)
 Target Host: PI host
 Service No: PI port number
 Path Prefix: /sap/xi/engine?type=entry
C)Connection between Business System and System Landscape Directory (ECC System)
   Create RFC destination (TCP/IP) LCRSAPRFC for the SLD connection.It is used to read the exchange profile.
  Create RFC destination (TCP/IP) SAPSLDAPI for the SLD connection.It is used by the ABAP API.

SXMB_ADM - Integration Engine Configuration
SLDAPICUST - Maintain SLD Access

System Requirements
• One Business Systems in SLD (System Landscape directory) is required which should be created
using Third Party Option and one Business System is required which should be created using
ABAP Option
• Access to Transactions SPROXY on ERP development system and SXMB_MONI, SXMB_IFR are
required for PI System.
• To be able to create proxy in ERP development system, Developer key must be assigned to your
user.
• Access to database is required. You should have a user who has access and update rights to
database. This user name and password will be used in receiver communication channel.
Tip: If you don’t have access right to any of this transaction, you can contact your basis /XI administrator so
that he can help you to create / configure objects for you including SLD.
• Developer Access to PI System is required to create this scenario


Abaper to check:
SLDAPICUST T-code is used for
Execute SLDCHECK T-code and check if it takes you to PI SLD webpage. If not request basis team to configure this.
Execute SPROXY T-Code in ECC system. You should be able to see ESR content there. Else, request basis team to maintain connections.
SXMB_IFR - Tcode is used for Poniting to different server

PI Process Integration or Process Orchestration System (INBOUND Interface)-Part4(Communication Channel)

Communication Channel Configuration CC_sender_ALCON_II1  in communication component
BS_FTP_Dev  under Business System.

PI Process Integration or Process Orchestration System (INBOUND Interface)-Part3(Communication Channel)

1. Communication Channel for Inbound processing:
                                   Create communication channel  CC_Proxy_Common_Receive in  communication component SAPECCCLNT120_CDH under Business System.

ModuleName:

sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

Type:

Local Enterprise Bean

Module Key:

soap

PI Process Integration or Process Orchestration System (INBOUND Interface)-Part3(Communication Component)

Development system , Quality System and Production System having separate Business system ,
So  we need to Create separate communication channel in each System.
Two types of communication channel:

Sender communication channel - for Inbound business system interface is receiver
Receiver communication channel - for Outbound business system interface is sender.

PI Process Integration or Process Orchestration System (INBOUND Interface)-Part2

step1:

Step2:

step3;

PI Process Integration or Process Orchestration System (INBOUND Interface)-Part1

Step1:

                                                       Step2:
Create namespace

                                                        Step3:
Create Enterprise Service in Repository (ESR Objects)

                                                    Step4:

                Step5: