Outbound settings in ale

Hi,
i had done all the settings required for ale in the sending system.i had tested the rfc destination it is logging onto recieving sys correctly,and port is genarated correctly,but when i create the purchase order idoc is not getting genarated in we05.plz help me out.points awarded imm.

Hi Narasimh,
Even after setting up the output type for PO and creating patner profiles and adding the message types ORDER and ORDCHG etc, when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model ".
Could you suggest some solution?
Also what do you mean "have you done setting for distribution model and distribution views after creating modelview you genertae patner profiles then you distribute the modelview" ? And how do we do that?
Thanks in advance,
Shweta

Similar Messages

Single Host for netweaver/xi & Idoc settings in ale

HI,
In the case of a single system which is the R/3 system as well as the xi system...what settings are to be done from ALE to enable idoc processing...is this the same as a dual system configuration..or ?
I am pasting some of the steps suggested for the ale configuration.
Can anyone re-organize this or format this so that it applies for a single system that is the db host, Xi Host, and r/3 host.
There are several ways of doing it, all eventually leading to the same conclusion..but in the case of a non-distrubuted system, there are some differences..Can someone put some clarity here...as i have tried the steps and not all of them clearly apply in the case of a single host.
link1) https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Link 2) /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
3) ALE settings.==> Author( Raghavesh Reddy )
SAP XI1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.

If you want to configure your R/3 system to send IDocs to XI the first thing you have to do is configure the basic ALE:
Logical System
-Representation of a system R/3 will communicate with
-Every R/3 client used in ALE must have a logical system associated
-BD54 change logical systems (add), SCC4 change clients (attach logical system)
-Stored in tables TBDLS and TBDLST
Ports
-Logical representation of a communication channel
-How you refer tie together RFC destinations with partner system
-WE21 or WEDI
Partner Profile
-Ties together many pieces of the ALE puzzle
-Message types, IDoc types, process codes, partner functions, application identifiers, message function, output type, and port
-Maintain inbound and outbound parameters (partner type, port, transfer immediately or collect IDocs)
-WE20, WEDI, or SALE
-Viewed as a gateway, routes a particular message of a specific IDoc type to the given port and invoking the appropriate function modules
The next thing you have to do is configure the IDoc adapter in XI to prepare the system to accept IDoc's into the integration builder from other SAP systems.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098

Please guide me how to do the Outbound Porcess in ALE

Hi Friends,
Kindly guide me on ALE/IDOC's step by step how to work on Outbound Process.
and the generated IDOC must be download & stored on the PC of the Sending System only in .txt file format.
so that the XI will collect that particular file in .txt format & upload it for Inbound process.
Thanks in Advance
Ganesh

IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch ALE Service).
IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
you can use the file port in the partner profile to store the data in the application server.once it saved in the application server it cna be downloaded to the pc.

ALE Inbound and Outbound programs

Hi,
Can someone tell me as to how we create the inbound and outbound programs for ALEs??And the cenerio where we use the std FMs and where we use the customs programs for the corresponding action?
Thanks,
Supriya Manik.

Hi,
Go thru this Book : Aravind Nagpal
go thru this links,
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400365
Idoc's
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm (change pointer)
http://www.erphome.net/pdf/tech/J07.pdf#search=%22ALE%20Change%20pointers%22
http://www.****************/articles/ALE/IDOCExtension/IDOCExtension.htm
Thanks
Sunil

Auto SO from PO- ALE IDoc

Hi Friends,
Someone provide me basic process flow and steps to automate creation of Sales Order in another Company Code when a Purchase Order is created in a separate Ccd with the help of IDocs. Eg: (PO saved in CCd-1100 triggering a SO in CCd-2200)
I know that there are two separate settings for this,
1. PO Message settings for ALE in NACE
2. Configurations in SALE for IDoc
But I want to have a clearer idea as to how to acheive this.
Any inputs highly apprecieated!!
Thanks in adv
Suraj

To create SO from the PO, you need to set up partner profile, process code. Etc.
First from PO the outbound IDOC you can use the below FM and basic type.
The SAP std basic type : ORDERS05
For the function module: IDOC_OUTPUT_ORDERS.
Table: EDP12- Partner Profile: Outbound with Message Control
T code: WE41 to set up the out bound process code
To create sales order inbound IDOC details.
The SAP Std basic : ORDERS05
Function module: IDOC_INPUT_ORDERS
T code: WE42 to set up inbound process code
Thanks
JRP

Function Module to create Outbound IDoc

I have created a segment (ZSEGPRO), basic type (ZIDOCPRO) and message type (ZMSGPRO) to create a custom IDoc. Now I have to write a Function Module to create Outbound IDoc.
I want to know what will be in Import, Export, Changing, Tables, Exceptions and Source code of that function module. The fields used in the segment ZSEGPRO is given below:
Fld NameSource Data Elmn     Description
PRODUCT MARA MATNR     Material number
TEXT     MAKT     MAKTX     Material description
PRN     MARA     YYBCEZNDR     Print Field
Additional information: Export parameter will be BAPIRETURN for holding error message(if any).
These Function Module need not require to be RFC enabled.

Hi ,
Refer these:
There are two main reasons
1) Make sure you call COMMIT WORK after the MASTER_IDOC_DISTRIBUTE
http://help.sap.com/saphelp_nw04/helpdata/en/78/21783151ce11d189570000e829fbbd/content.htm
2) The rest of the setting of the ALE IDoc might not have been done
http://help.sap.com/saphelp_46c/helpdata/en/78/2177c951ce11d189570000e829fbbd/frameset.htm
You can use the Area Menu WEDI and do the rest of the settings.
ALE Quick Start guide and ALE Programming Guides for your reference
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
Recent discussion which could be helpful,
About WE21, BD64, sm59
Regards
Shiva Kumar

Partner profile settings.. for IDOC to File

i am trying to send Idoc to XI system from my r/3..
once iam sending from r/3 we19 ,i am getting error like this
receiver port " port name " does not exist in the table of port descriptions ..
how can i maintain receiver port in sender sys..?it is asking for RFC destination which is there in receiver sys but not in sender ....
how should i configure...
(Note: i have sent file to Idoc with same configuration settings..)
NOW
i am sending IDOC FROM IDES TO XI as FILE
Control record :in we19 ( IDES5.0)
   (XI-System)(SYS ID =O36)    (IDES5.0)(SYS ID = O20)
       Receiver:                      Sender:
port:SAPO20_800                 port:XI_00_800
partnerNo:036CLNT036        artnerNo:T90CLNT090
i have maintained outbound settings in T90CLNT090..
thanks in advance..
Ramesh..
THANKS FOR YOUR QUICK RESPONSES .HERE I added ALL DETAILS OF CONFIGURATION..from which iam getting error

Hi,
Steps to do ALE Configuration with respect to IDOC:
Configuration in R/3:
1. Create a RFC destination using Transaction = SM59
2. Create the ports using we21 and refer the port to the created RFC dest in above Step.
3. Create a Logical System using Transaction BD54.
4. Create a partner profile using transaction WE20.
Also need to configure in XI:
1. Create a RFC destination using Transaction = SM59
2. Create the ports using Transaction IDX1 and refer the port to the created RFC dest in above Step.
3. The port has to be displayed in the IDX2 transaction and we should be able to view the idocs which we imported through integration repository otherwise we have to manually import the idocs from IDX2 using the port created above
Also refer to the link below for further details:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Regards,
Nithiyanandam

Need help in ALE configuaration !

Please send me an example of how to create an ALE configuaration with in one client !

HI,
What is ALE?
ALE stands for Application Link Enabling and is a remote connection technology allowing the decentralization of business processes by connecting decentralized systems together.
Using ALE, it is fairly easy to synchronize several SAP systems so that they contain the same data objects at anytime. These objects may be master data (customers, vendors, GL accounts, cost centers, ...) or transaction data (FI documents, purchase orders, ...). To enable the synchronization, ALE supports not only mass transfer of data between systems but also selective data transfers of objects changed since the last transfer.
How does it work?
Viewed from a high level perspective, the process is straight and simple: a sender system selects the data that needs to be distributed, packs it in a standard format and sends it to one or several receiving systems. When a receiving system gets the data, it unpacks the standard format and records the data.
In fact, 3 layers are involved in this process:
An application layer which selects and records data in R/3.
A distribution layer which filters and converts data.
A communication layer which ensures the actual communication of records generated in a standard format.
The senders and receivers are determined thanks to a so-called distribution model which defines the transfer rules (who sends what to who?). The definition of the distribution model must be known by all systems involved (either as sender or receiver) and must consequently exist on all those systems.
The Intermediate Document (IDoc)
The data transferred using ALE must have a SAP standard format to be understood from all partners in the communication. This format is the Intermediate Document (IDoc) which represents an intermediary structure between raw SAP data and EDI formats. This structure is not constant, it depends on the data to be transferred and SAP provides the structures for most SAP standard objects such as customers master data, sales orders, ...
An IDoc with a specific structure is said to have a specific type. The IDoc type is nothing more than a version of a specific IDoc structure designed to contain data for a specific object type. For example, the IDoc type DEBMAS05 is the fifth version of a structure that represents a customer master data. The management of versions for IDocs structures is necessary because the objects evolve with time and tend to become more and more complex with new data fields or tables being added regularly.
The conversion of raw data forth (for the sender system) and back (for the receiver system) to the IDoc format is also ensured by SAP standard function modules as long as you transfer standard objects. For non standard objects (enhancements), you must define your own IDoc structure and write your own conversion function modules.
RFC connections
The data communication between the SAP servers may be done by several ways. The 2 most common ways are the transactional RFC and the file. The RFC connection is used to make a direct connection between servers while the file interface speaks for itself, it uses a file containing the IDocs from the sender system as input in the receiver(s) system(s).
The selection of a communication method is made though the ports configuration as we will see in the next section. For the purpose of this article, we are going to choose the most efficient method: the transactional RFC method. To set it up, we first need to define the RFC destinations of the partner systems.
An RFC destination may be seen as a set of settings necessary to connect to a system using the RFC protocol. These settings include the address and type of the partner system along with connection information such as the user ID and password to use.
The RFC destinations of all partners systems must be defined on all systems to include in the distribution model. The transaction to use for this purpose is SM59.
Definition of the communication ports
The communication ports determine the type of data communication that must occur between systems. When the communication is to use the RFC protocol, transactional RFC ports must be created specifying the RFC destinations of the partner systems. Use transaction WE21 for this purpose.
Partners profiles
In SAP, all partners systems involved in a distribution model have a profile. There exist several profile types such as customers profiles, vendors profiles, ... but this distinction between profiles is generally not necessary and you will create in most cases your partners profiles using a generic Logical System type.
Before entering the settings of the logical systems partners, you have to create them in customizing. Also, each system in the distribution model must be assigned in its own system its own logical system that represents it. This assignment is done at client level and not at system level. This is not easy to explain nor to understand so let's take a simple example. Let's consider we have a simple distribution model made up of a sender system (S01) and a receiver system (R01). We need to transfer data from S01 / client 100 to R01 / client 200. In both the systems, we will define the logical systems S01_100 and R01_200. But in sender system S01, the logical system S01_100 will be assigned to the client 100 while in the receiver system R01, it will be R01_200 that will be assigned to client 200. With such a configuration you see it is even possible to transfer data between two clients from the same system.
A partner profile is used to determine a lot of important settings that will be involved in the data transfer. These settings vary depending on the role of the partner system (sender / receiver) and are defined per message type. A message type is more or less a version independent IDoc type. It is mainly a convenient way of defining settings and identifying IDocs using a criterium independent of the partner system.
For a sender partner system (inbound parameters are filled in), following important settings are set per message type in the partner profile:
A process code used to indicate which function module will be used to convert the IDoc data to SAP data.
The time of input of the IDoc: as soon as the IDoc is created in the system or on request (using program RBDAPP01).
The post processing agent who will have to treat the data input errors if need be. The post processing agent may be either a user or any other HR organizational unit.
For a receiver partner system (outbound parameters are filled in), following settings are specified in the partner profile:
The receiver port to which the data will be sent.
The sending method: one IDoc at a time or by packets.
The IDoc type that will be sent to that partner. For a given message type, the IDoc type sent may vary depending on the receiver system. Indeed you may have different versions of SAP in your system landscape.
Definition of the distribution model and data filtering
We have already seen that the distribution model is used to decide who sends what to who. But, as you guessed, there is a little bit more to be said about it and the way to manage it.
The distribution model is maintained in a central transaction (BD64) which lets you access the most useful environmental settings necessary to set up the model. Before creating the model, you must first decide on which system you are going to create it. Indeed the model must exist in all partners systems and two possibilities exist to achieve this.
Either you create the model on each system manually (with the same model technical name), which is feasible only with few systems and/or simple models. Either you create it in a specific system (usually the source system) and distribute it to the other systems thanks to the distribution command in the BD64 transaction menu.
If we want to copy the customers master data from the production system to the other systems in the maintenance line for example, we may create the distribution model on the production system and distribute it to all partners 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. You may afterwards add more sending and receiving systems in the model as well as more message types.
For each message type defined between a sender and a receiver, you may set filters on specific fields of the message type so that IDocs be generated only when these specific values are matched. For example, you may decide to send only customers of a specific account group. These filters are set by selecting the 'no filter set' text under message types in BD64.
There exists also another kind of filters which are segments filters. They do not filter IDocs creation based on values like we have just seen but filter unconditionally segments of created IDocs which must be excluded from the transfer (transaction BD56).
This article will help you understand the basics of ALE and IDocs via a simple do-it-yourself example. We will create a custom IDoc in one SAP system and then post some business data through it to another SAP system. Business data will be picked up from custom data dictionary tables.
ALE Application Link Enabling is a mechanism by which SAP systems communicate with each other and with non-SAP EDI subsystems. Thus it helps integration of distributed systems. It supports fail-safe delivery which implies that sender system does not have to worry about message not reaching the source due to unavoidable situations. ALE can be used for migration and maintenance of master data as well as for exchanging transactional data.
The messages that are exchanged are in the form of IDocs or Intermediate Documents. IDocs act like a container or envelope for the application data. An IDOC is created as a result of execution of an Outbound ALE. In an Inbound ALE an IDOC serves as an input to create application document. In the SAP system IDocs are stored in the database tables. They can be used for SAP to SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data. Complete documentation on IDOC is obtained by using transaction WE60.
Every IDoc has exactly one control record along with a number of data records and status records. Control record has the details of sender/receiver and other control information. Data records contain the actual business data to be exchanged while the status records are attached to IDoc throughout the process as the IDoc moves from one step to other.
Now, let us understand the ALE Configuration by means of an example scenario below:
The Scenario
Data from custom tables (created in customer namespace) is to be formatted into an IDoc and sent from one SAP R/3 system to another using ALE service. We need to have two instances of SAP R/3 systems or we can simulate this on two clients of the same SAP R/3 system.
Create three tables as shown below.
Creating Custom IDoc type and Message type
All the objects created should be present on both source as well as target system(s).
1. Create segments Transaction WE31
Create a segment ZRZSEG1
Add all fields of table ZCUSTOMERS to it
Save the segment
Release it using the menu path Edit -> Set Release
Similarly create two more segments given below
Seg. ZRZSEG2 to hold all fields of table ZSOHEADERS
Seg. ZRZSEG3 to hold all fields of table ZSOITEMS
2. Create Basic IDoc type Transaction WE30
Create a Basic type ZRZORDER
Add the created segments in the hierarchy shown
Maintain attributes for each of the segments
Save the object and go back
Release the object using the menu path Edit -> Set Release
3. Create/Assign Message type Transactions WE81/WE82
Go to WE81
Create a new Message type ZRZSO_MT
Save the object
Go to WE82 and create new entry
Assign the message type ZRZSO_MT to the basic type ZRZORDER
Also specify the Release Version
Save the object
Thus we have defined the IDoc structure which will hold the data to be transferred. In the [1] next part of the article we will understand the outbound settings, i.e. the settings to be done in the source system.
Outbound Settings
Define Logical Systems and Assign Client to Logical System Transaction SALE
Go to Define Logical System (See the figure)
Define a new logical system to identify the local system and save it
Now, go to Assign Client to Logical System (See the figure)
Add a new entry
Specify the client, previously created logical system and other attributes
Save the entry
Define a new logical system to identify the partner system and save it
Maintain RFC Destinations Transaction SM59
Create a new RFC destination for R/3 type connection
Specify the target host on Technical settings tab
Provide the Logon credentials on the Logon/Security tab
Save the settings
To verify the settings, Click on Test connection or Remote logon
Define Ports Transaction WE21
We need to define a tRFC port for the partner system
Click on Transactional RFC node
Create a new port
Provide a description
Specify the name of the target RFC destination
Save the object
Maintain Distribution Model Transaction BD64
Click on Change
Create a new model view
Provide a Short text and Technical name to the model view
Add message type
Specify sender and receiver systems
Also, specify the message type that we created previously
Save the Distribution model
Generate/Create Partner Profile Transactions BD82/WE20
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
On selection screen, specify the model view, target system and execute
The result log will be displayed on the next screen
To verify the partner profile go to WE20
Check the partner profile for the target system
Distribute Model View Transaction BD64
Select the Model View
Go to menu path Edit -> Model View -> Distribute
Result log will be displayed on the next screen
Outbound IDoc Generation Program
Create an executable program ZRZ_ORDER_IDOC in SE38. Below, I have described the program logic:
Fetch the data from the DDic tables ZCUSTOMERS, ZSOHEADERS and ZSOITEMS as per the selection criteria
Fill the control record structure of type EDIDC
Specify message type, Basic IDoc type, tRFC Port, Partner number and Partner type of the receiver
Fill the data records
Define structures like the IDoc segments
Fill the structures with fetched data
Pass the segment name and the above structure to the appropriate fields of EDIDD type structure
Append the EDIDD structure to the EDIDD type internal table
Now, call the function module MASTER_IDOC_DISTRIBUTE and pass the IDoc control record structure and data record table
Commit work if return code is zero
Function module returns a table of type EDIDC to provide the details about generated IDoc
Display appropriate log
You can [2] download sample code for the above program here.
Thus we have completed sender side configuration required for ALE. In the [3] next part we will see how to configure the receiving system to be able to receive and post the inbound IDoc.
Inbound IDoc Posting Function Module
In the receiving system, create a function module Z_IDOC_INPUT_ZRZSO_MT using SE37. Below, I have described the logic for the same.
Add Include MBDCONWF. This include contains predefined ALE constants.
Loop at EDIDC table
Check if the message type is ZRZORDER. Otherwise raise WRONG_FUNCTION_CALLED exception
Loop at EDIDD table
Append data from the segments to appropriate internal tables
For example: append data from ZRZSEG1 segment to the internal table of type ZCUSTOMERS
Update the DDic tables from internal tables
Depending on the result of the update, fill the IDoc status record (type BDIDOCSTAT) and append it to the corresponding table.
Status 53 => Success
Status 51 => Error
You can [3] download the sample ABAP code for the above function module here.
Inbound Settings
Define Logical Systems Transaction SALE (Please refer to Outbound Settings discussed in [4] previous part)
Assign Client to Logical System Transaction SALE (Please refer to Outbound Settings discussed in [5] previous part)
Maintain RFC Destinations Transaction SM59 (Please refer to Outbound Settings discussed in [6] previous part)
Define Ports Transaction WE21 (Please refer to Outbound Settings discussed in [7] previous part)
Generate/Create Partner Profile Transactions BD82/WE20 (Please refer to Outbound Settings discussed in [8] previous part)
Assign Function Module to Logical message Transaction WE57
Create a new entry
Specify name of the Function Module as Z_IDOC_INPUT_ZRZSO_MT
Also, specify Type as F, Basic IDoc type as ZRZORDER, Message type as ZRZSO_MT and Direction as 2 (Inbound)
Save the entry
Define Input method for Inbound Function Module Transaction BD51
Create a new entry
Provide Function Module name as Z_IDOC_INPUT_ZRZSO_MT
Specify the Input method as 2
Save the entry
Create a Process Code Transaction WE42
Create a new Process Code ZPCRZ
Select Processing with ALE Service
Choose Processing type as Processing by function module
Save the entry
On the next screen, select your function module from the list
Save the changes
Now you will be taken to the next screen
Double-click on Logical message
In the Assignment to logical message, specify the message type ZRZSO_MT
Save the changes
Send and receive data
On the sender system, execute the IDoc Generation Program. Check the status of IDoc using transaction WE02.
Check the status of the IDoc in the receiver system using transaction WE02. You can also check the contents of DDic tables to make sure that the records have been created in the receiver system.
Thus to summarize we have learned how to:
*& Report ZRZ_ORDER_IDOC *
REPORT ZRZ_ORDER_IDOC .
PURPOSE OF REPORT *
Generats an Idoc for Customer Master, Sales Master
and Sales item table.
TABLES : ZCUSTOMERS, "Cutomer Header
 ZSOHEADERS, "Sales Header
 ZSOITEMS. "Sales Items
DATA : S_CTRL_REC LIKE EDIDC, "Idoc Control Record
 S_ZRZSEG1 LIKE ZRZSEG1, "CUSTOMER Header Data
 S_ZRZSEG2 LIKE ZRZSEG2, "SALES HEADER Data
 S_ZRZSEG3 LIKE ZRZSEG3. "SALES Detail Data
DATA : T_ZCUSTOMERS LIKE ZCUSTOMERS OCCURS 0 WITH HEADER LINE.
DATA : T_ZSOHEADERS LIKE ZSOHEADERS OCCURS 0 WITH HEADER LINE.
DATA : T_ZSOITEMS LIKE ZSOITEMS OCCURS 0 WITH HEADER LINE.
DATA : T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE."Data Records
DATA : T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE.
"Generated Communication IDOc
CONSTANTS :
C_ZRZSEG1 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG1',
C_ZRZSEG2 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG2',
C_ZRZSEG3 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG3'.
CONSTANTS: C_IDOCTP LIKE EDIDC-IDOCTP VALUE 'ZRZORDER'.
Selection Screen
SELECT-OPTIONS : S_KUNNR FOR ZCUSTOMERS-KUNNR OBLIGATORY,
 S_VBELN FOR ZSOHEADERS-VBELN.
PARAMETERS : C_MESTYP LIKE EDIDC-MESTYP DEFAULT 'ZRZSO_MT',
 "Message Type
 C_RCVPRT LIKE EDIDC-RCVPRT DEFAULT 'LS',
 "Partner type of receiver
 C_LOGSYS LIKE EDIDC-RCVPRN DEFAULT 'Y901',
 C_RCVPOR LIKE EDIDC-RCVPOR DEFAULT 'A000000226',
 C_SNDPRN LIKE EDIDC-SNDPRN DEFAULT 'LSSENDS',
 C_SNDPRT LIKE EDIDC-SNDPRT DEFAULT 'LS'.
"Destination System
***START-OF-SELECTION
START-OF-SELECTION.
PERFORM GENERATE_DATA_RECORDS.
PERFORM GENERATE_CONTROL_RECORD.
PERFORM SEND_IDOC.
*& Form generate_data_records
FORM GENERATE_DATA_RECORDS .
PERFORM FETCH_ZCUSTOMERS.
PERFORM FETCH_ZSOHEADERS.
PERFORM FETCH_ZSOITEMS.
PERFORM ARRANGE_DATA_RECORDS.
ENDFORM. " generate_data_records
*& Form fetch_zcustomers
FORM FETCH_ZCUSTOMERS.
SELECT *
FROM ZCUSTOMERS
INTO TABLE T_ZCUSTOMERS
WHERE KUNNR IN S_KUNNR.
IF SY-SUBRC NE 0.
 MESSAGE E398(00) WITH 'No Customers Found'.
ENDIF.
ENDFORM. " fetch_zcustomers
*& Form fetch_zsoheaders
FORM FETCH_ZSOHEADERS.
SELECT *
FROM ZSOHEADERS
INTO TABLE T_ZSOHEADERS
WHERE VBELN IN S_VBELN
 AND KUNNR IN S_KUNNR.
IF SY-SUBRC NE 0.
 MESSAGE I398(00) WITH 'No Sales orders found'.
ENDIF.
ENDFORM. " fetch_zsoheaders
*& Form fetch_zsoitems
FORM FETCH_ZSOITEMS.
IF NOT T_ZSOHEADERS[] IS INITIAL.
 SELECT *
 FROM ZSOITEMS
 INTO TABLE T_ZSOITEMS
 FOR ALL ENTRIES IN T_ZSOHEADERS
 WHERE VBELN = T_ZSOHEADERS-VBELN.
 IF SY-SUBRC NE 0.
 MESSAGE I398(00) WITH 'No Sales order items found'.
 ENDIF.
ENDIF.
ENDFORM. " fetch_zsoitems
*& Form generate_control_record
FORM GENERATE_CONTROL_RECORD .
S_CTRL_REC-RCVPOR = C_RCVPOR. "Receiver Port
S_CTRL_REC-MESTYP = C_MESTYP. "Message type
S_CTRL_REC-IDOCTP = C_IDOCTP. "Basic IDOC type
S_CTRL_REC-RCVPRT = C_RCVPRT. "Partner type of receiver
S_CTRL_REC-RCVPRN = C_LOGSYS. "Partner number of receiver
S_CTRL_REC-SNDPRT = C_SNDPRT. "Sender Partner type
S_CTRL_REC-SNDPRN = C_SNDPRN. "Sender Partner Number
ENDFORM. " generate_control_record
*& Form send_idoc
FORM SEND_IDOC.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
 EXPORTING
 MASTER_IDOC_CONTROL = S_CTRL_REC
 TABLES
 COMMUNICATION_IDOC_CONTROL = T_COMM_IDOC
 MASTER_IDOC_DATA = T_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.
ELSE.
 COMMIT WORK.
 LOOP AT T_COMM_IDOC.
 WRITE:/ 'IDoc Generated - ', T_COMM_IDOC-DOCNUM.
 ENDLOOP.
ENDIF.
ENDFORM. " send_idoc
*& Form arrange_data_records
FORM ARRANGE_DATA_RECORDS .
DATA: W_INDEX1 LIKE SY-TABIX,
 W_INDEX2 LIKE SY-TABIX.
SORT T_ZCUSTOMERS BY KUNNR.
SORT T_ZSOHEADERS BY KUNNR VBELN.
SORT T_ZSOITEMS BY VBELN POSNR.
LOOP AT T_ZCUSTOMERS.
 S_ZRZSEG1-KUNNR = T_ZCUSTOMERS-KUNNR.
 S_ZRZSEG1-NAME1 = T_ZCUSTOMERS-NAME1.
 S_ZRZSEG1-ORT01 = T_ZCUSTOMERS-ORT01.
 S_ZRZSEG1-LAND1 = T_ZCUSTOMERS-LAND1.
 T_EDIDD-SEGNAM = C_ZRZSEG1.
 T_EDIDD-SDATA = S_ZRZSEG1.
 APPEND T_EDIDD.
 CLEAR T_EDIDD.
 CLEAR W_INDEX1.
 READ TABLE T_ZSOHEADERS WITH KEY KUNNR = T_ZCUSTOMERS-KUNNR BINARY SEARCH.
 IF SY-SUBRC = 0.
 W_INDEX1 = SY-TABIX.
 LOOP AT T_ZSOHEADERS FROM W_INDEX1.
 IF T_ZSOHEADERS-KUNNR NE T_ZCUSTOMERS-KUNNR.
 EXIT.
 ENDIF.
 S_ZRZSEG2-VBELN = T_ZSOHEADERS-VBELN.
 S_ZRZSEG2-KUNNR = T_ZSOHEADERS-KUNNR.
 T_EDIDD-SEGNAM = C_ZRZSEG2.
 T_EDIDD-SDATA = S_ZRZSEG2.
 APPEND T_EDIDD.
 CLEAR T_EDIDD.
 CLEAR W_INDEX2.
 READ TABLE T_ZSOITEMS WITH KEY VBELN = T_ZSOHEADERS-VBELN BINARY SEARCH.
 IF SY-SUBRC = 0.
 W_INDEX2 = SY-TABIX.
 LOOP AT T_ZSOITEMS FROM SY-TABIX.
 IF T_ZSOITEMS-VBELN NE T_ZSOHEADERS-VBELN.
 EXIT.
 ENDIF.
 S_ZRZSEG3-VBELN = T_ZSOITEMS-VBELN.
 S_ZRZSEG3-POSNR = T_ZSOITEMS-POSNR.
 S_ZRZSEG3-MATNR = T_ZSOITEMS-MATNR.
 S_ZRZSEG3-NETWR = T_ZSOITEMS-NETWR.
 S_ZRZSEG3-ZMENG = T_ZSOITEMS-ZMENG.
 T_EDIDD-SEGNAM = C_ZRZSEG3.
 T_EDIDD-SDATA = S_ZRZSEG3.
 APPEND T_EDIDD.
 CLEAR T_EDIDD.
 ENDLOOP.
 ENDIF.
 ENDLOOP.
 ENDIF.
ENDLOOP.
ENDFORM. " arrange_data_records

Data migration with ALE/Idoc

Hello .
I want to migrate data between two SAP system using ALE / IDOC, and I want to know the settings to make on each system (source and target).
Does someone has an idea?
Thank you all

Outbound Settings
Define Logical Systems and Assign Client to Logical System u2013 Transaction SALE
u2022     Go to Define Logical System (See the figure)
u2022     Define a new logical system to identify the local system and save it
u2022     Now, go to Assign Client to Logical System (See the figure)
u2022     Add a new entry
u2022     Specify the client, previously created logical system and other attributes
u2022     Save the entry
u2022     Define a new logical system to identify the partner system and save it
Maintain RFC Destinations u2013 Transaction SM59
u2022     Create a new RFC destination for R/3 type connection
u2022     Specify the target host on Technical settings tab
u2022     Provide the Logon credentials on the Logon/Security tab
u2022     Save the settings
u2022     To verify the settings, Click on Test connection or Remote logon
Define Ports u2013 Transaction WE21
u2022     We need to define a tRFC port for the partner system
u2022     Click on Transactional RFC node
u2022     Create a new port
u2022     Provide a description
u2022     Specify the name of the target RFC destination
u2022     Save the object
Maintain Distribution Model u2013 Transaction BD64
u2022     Click on Change
u2022     Create a new model view
u2022     Provide a Short text and Technical name to the model view
u2022     Add message type
u2022     Specify sender and receiver systems
u2022     Also, specify the message type that we created previously
u2022     Save the Distribution model
Generate/Create Partner Profile u2013 Transactions BD82/WE20
u2022     To generate Partner profiles automatically you may use BD82 or go to BD64 and use the menu path Environment -> Generate partner profiles
o     Otherwise, you may use transaction WE20 to create a partner profile
u2022     On selection screen, specify the model view, target system and execute
u2022     The result log will be displayed on the next screen
u2022     To verify the partner profile go to WE20
u2022     Check the partner profile for the target system
Distribute Model View u2013 Transaction BD64
u2022     Select the Model View
u2022     Go to menu path Edit -> Model View -> Distribute
u2022     Result log will be displayed on the next screen
Inbound Settings
u2022     Define Logical Systems u2013 Transaction SALE (Please refer to Outbound Settings discussed)
u2022     Assign Client to Logical System u2013 Transaction SALE (Please refer to Outbound Settings discussed)
u2022     Maintain RFC Destinations u2013 Transaction SM59 (Please refer to Outbound Settings discussed)
u2022     Define Ports u2013 Transaction WE21 (Please refer to Outbound Settings discussed)
u2022     Generate/Create Partner Profile u2013 Transactions BD82/WE20 (Please refer to Outbound Settings discussed)
u2022     Assign Function Module to Logical message u2013 Transaction WE57
o     Create a new entry
o     Specify name of the Function Module
o     Also, specify Type as F, Basic IDoc type , Message type and Direction as 2 (Inbound)
o     Save the entry
u2022     Define Input method for Inbound Function Module u2013 Transaction BD51
o     Create a new entry
o     Provide Function Module name
o     Specify the Input method as 2
o     Save the entry
u2022     Create a Process Code u2013 Transaction WE42
o     Create a new Process Code
o     Select Processing with ALE Service
o     Choose Processing type as Processing by function module
o     Save the entry
o     On the next screen, select your function module from the list
o     Save the changes
o     Now you will be taken to the next screen
o     Double-click on Logical message
o     In the Assignment to logical message, specify the message type
o     Save the changes

Inbound & outbound process

Hi All,
I am new to ALE. I want to know what is the actual process behid inboud and outbound services in ALE.

Hi,
1.Here out bound means sender.Inbound mens --receiver.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Regards,
Shiva.

Outbound Proxy error when triggering from SPROXY

Hi Everyone,
I was working on outbound proxy from ECC to PI. I have generated the proxy and activated. When I am trying to test the proxy manually from SPROXY the message is not getting triggered to SXMB_MONI in ECC itself. But I didn't get any error message as well. When I am executing the proxy from SPROXY I was getting below message in the status bar. So can anyone help me with the possible solution why the message is not getting triggered.
Below is the options I have selected while executing the proxy.
This was the status message which was giving after execution of proxy from SPROXY. The same status was giving for all the Proxy interface which ever is executing from SPROXY.
Regards,
Kankipati.

Hi Kankipati
can you please try Commit work by navigating on test proxy screen .
Extra- Trigger Commit work .
Follow the below link .
SAP PI Reference: SAP PI ABAP Proxy Outbound settings, Triggering message to SAP PI(When many sap pi systems)
Best Regards
Srinivas

Sending outbound invoice idoc's by MIRO transaction

Hello Friends,
I want to send outbound IDOC via ALE to some third party system
I have created output type with application MR
Also created new outbound process code with FM IDOC_INPUT_INVOIC_MRM
I am using basic type INVOIC02
Now when I try to post MIRO document I get below error:
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_DYN_CALL_PARAM_MISSING',
was neither
caught nor passed along using a RAISING clause, in the procedure
"NEW_DYN_PERFORM" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
When calling the function module "IDOC_INPUT_INVOIC_FI", one of the parameters
needed according to the interface description was not specified.
This parameter was "INPUT_METHOD".
My requirement is to send outbound idoc from miro ......Please suggest.
Thanks

Hi Raghvendra,
I my scenario, i will be creating the inovice in SAP manually using t.code MIRO and once the invoice is posted i need to capture the details in IDOC. The EDI customization would come into picture for receiving invoices through EDI.
Regards

Message type US for ALE distribution

I want to create an outbound IDOC using ALE distribution.
I have to assign Partner type as 'US' - user. Can anyone give me some input. I got the error when trying to do the same
" No partner profiles (message control) maintained
Message no. B1127 Diagnosis No IDOC partner profiles have been created for the message control for
 for application EF, condition key ZNBR and change message '' with
 partner type 'LS' and partner role ' '.
Procedure Please create the partner profiles for the logical system that should
 contain the IDOC. You can either generate them from the ALE model or
 create them manually.
Step by step will be helpfull.
Thanks

Hi Preethi,
You can use this program RBDCUS15 to generate outbound partner profile.
Also you use distribution model (t/code BD64) as well.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Ale audit steps

Hi,
Can anybody please explain ale audit steps.
1. i am sending idocs from send1 rece1. how i can i know the status of outbound idocs using ale audit
i want to know the process behinds this.

Hi Sudhakar..
ALE Audit Steps:
In the Sender system:
1. In the Model view (BD64) : Add the Message type ALEAUD
Note: Sender and Receiver has to be reverse..
Distribute the Model view to the Receiver system.
2. Audit data can be confirmed periodically back to the sending system, you have to use the program RBDSTATE to specify a variant and schedule a background job in the receiving system
Reward if Helpful

ALE SETTING

Hi ALL,
I have doubt in ALE SETTINGS
what is the difference between IDOC to FILE and FILE to IDOC ale setting. Can any one help me in this regard.
thanks
saranya

hi saranya,
ALE settings for IDOC to file scenario. Pls refer my article:
http://www.architectsap.com/expertise-Publications.htm(Custom IDOC creation and integration with xi)
i think this will give you good info aboutidoc to file ale settings.
ALE settings for File to IDOC scenario. Pls refer foll articles:
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Regards,
Mandeep Virk
*reward points if helpful*

Outbound settings in ale

Similar Messages

Maybe you are looking for