ALE IDOC

EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between the
computer systems of business partners, using a standard format over a communication network.
EDI is also called paperless exchange.

Reduced Data entry errors

Reduced processing time
Availability of data in electronic form
Reduced paperwork
Reduced Cost
Reduced inventories and better planning
Standard means of communications
Better business process

Outbound Process:

1.Application document is created.

2. IDOC is generated
3.Idoc is transferred from SAP to Operating system layer
4.Idoc is converted into EDI standards
5.Edi document is transmitted to the business partner
6.The Edi Subsystem report status to SA

Inbound Process:
1.EDI transmission received
2.EDI document is converted into an IDOC
3.IDOC is transferred to the SAP layer
4.The application document is created
5.The application document can be viewed.

IDOC:
IDOC is a container that can be used to exchange data between any two processes.

Each IDOC is assigned a unique number for tracking and future reference.

IDOC consists of several segments, and segments contain several fields.

PORT:
Port is used in the outbound process to determine the name of the EDI subsystem program, the directory path
where the IDOC file will be created at the operating system level, the IDOC file names and the RFC
destinations.

RFCDestination:
Used to define the characteristics of communication links to a remote system on which a functions needs to be
executed.

PartnerProfile:
Partner profile specified the various components used in an outbound process (Partner number, IDOC type,
message type, Port, Process code), the mode in which it communicates with the subsystem (batch or
immediate) and the person to be notified in case of errors.

MessageControl
Used in pricing, account determination, material determination, and output determination. The message control
component enables you to encapsulate business rules with out having to write ABAP programs.

TO Process IDOCS the following TCODES will be used.

Logical System Names SALE

Setup RFC destinations SM59
Port Destinations WE21 

In Source system:

Segment Creation WE31

Basic IDOC Type Creation WE30

Message Type Creation WE81

Assign Message Type To Basic IDOC Type WE82

Distribution Model BD64

Writing Report Program SE38

Partner Profile WE20
Message control NACE

Check IDOCs WE02, WE05

In Destination System:

Creating FM SE37

Assign FM to Logical Message WE57

Define I/P method for Inbound FM BD51

Create Process Code WE42

Generate Partner Profile BD64 

-------------------------------------------------------------------------------------------------------------------

1. Creating users for ALE Transfer

2. Creating Logical system and assign the client

3. Creating the RFC

4. Configuring Distribution Model

5. Configuring and checking the port

6. Configuring and checking the partner profile

7.  Creating the message type 

1. Create Users for ALE transfer in both receiving and sending client/systems.
Create users in both the client/systems giving the same user name and proper authorizations. We need to use
these user ids to logon through the remote connection and perform the IDOC transfers.

 2. Creating Logical Systems

o       Create logical systems for both sending and receiving systems in both systems.
o       Login to Client 105 (SENDER)
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 Logical Systems with naming convention 'system name'+'CLNT'+client no . For example for sending system ex:
SSPCLNT105
o       Create Logical Systems with naming convention 'system name'+'CLNT'+client no ex: example for receiving system ex
SEDCLNT800
o       Save and come back
o       Click on Assign client 105 to Logical system SSPCLNT105
o       Now, logon to client 800, repeat the same above process to create logical systems SEDCLNT800 and SSPCLNT105
o       Save and come back
o       Click on Assign client 800 to Logical system SEDCLNT800
 
 
3. Creating the RFCs
o       In client 105, Go to T. Code SM59
o       Expand R/3 Connections
o       Enter RFC Name as SSPCLNT105 (give this name same as that of logical name created in step1 so that the ports are
automatically created)
o       Connection Type as 3
o       Language as EN
o       Give the logon details for client 800 (usually, we create a new user with proper authorizations for this ALE data
transfer)
o       Click on Remote logon button to test the RFC
o       Now, go to client 800 and repeat the same process to create the RFC connection to client 105, giving logon credentials
to client 105
 

4. Creating Customer Distribution Model

(we usually create this in the original system(sending system) and then distribute it to other systems. The actual creation of
the model requests that you mention a technical name for the model (unique identifier in the systems landscape), a sender
system, a receiver system and message types to exchange between those systems.)

o       In Client 105, Go to T. Code BD64

o       Click on change and Create model view button
o       Enter the short text and Technical name as ZSSP_SED
o       Select the model and click on Add Message Type Button,
o       Give the Sender as SSPCLNT105, Receiver as SEDCLNT800,
o       Give Message type as required, Ex: 'HRMD_A' for HR Module.(usually Message types given by SAP are available for
a particular module, see this using tcode WE81, if not create a message type first)
o       Note: If we are performing this data transfer task for all modules at a Customer site, then we will need to use the
appropriate message type and create a new Distribution model.
o       Select the above model view and click on Environment -> Generate Partner Profiles
o       Select Transfer IDOC Immediately and Trigger Immediately radio buttonsF
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 continue
o       You should get a list saying model view is distributed successfully.
 
5. Checking the Port
o       In client 105, Go to T. Code WE21
o       Expand Transactional RFC
o       Find the port from the list which is created using BD64 for SEDCLNT800 (Receiving system) RFC Destination.

6. Checking the Partner Profiles.

o       In client 105, Go to T. Code WE20
o       Expand Partner Type LS
o       Select the Partner profile SEDCLNT800
o       Double click on Message Type (For Ex: In HR Module, HRMD_A in Outbound parameters.)
o       Check Receiver Port is assigned correctly
o       Check the Basic type as your Basic IDOC object.
o       In the sending system, select the option to transfer IDOCs immediately.
o       By default, in the receiving system IDOCS are bunched together and received.
 
 7. Creating the Message Type
o       Message type defines the 'meaning' of data. It is just a logical entity that gets connected to the Idoc type (in tcode
we82) or gets connected to the distribution model (in tcode BD64)
o       If necessary create a new message type. In client 105, go to tcode we81.
o       Click on change, continue
o       Click on New Entries button

o      Give message type in customer namespace Z* and description

o      Save and back