Hi Srinivas,
Let us explore the need for each steps and detail it now...
<b>Step-1 :</b> You need RFC destinations for placing the metadata of the IDoc.
Use transaction SM59 to maintain an RFC destination for the IDoc sender/receiver system.
This RFC destination is used to retrieve the IDoc metadata from the sender system.
The IDoc adapter needs these metadata to create the corresponding IDoc-XML message from the RFC stream.
<b>Step-2 :</b> Next You need IDx1 for getting IDoc metadata from the Sender system.
Use transaction IDX1 to assign a port (RFC destination) to the system that contains the metadata of the IDoc types.
<b>Note:</b>
There is a mechanism on the Integration Server that uses this RFC destination to retrieve and cache the metadata at runtime if it is not yet available on the Integration Server.
<b>Nut-Shell:</b>
Since IDoc metadata is cross-client, you should only assign one port for each system.
If several ports are assigned, ensure that they are all working.
This is Done in Partner Profile.
If you are not able to load the metadata from this system (because of administrative or security-related restrictions, for example),
you can also load it from a reference system (for example, a test system) and use transaction IDX2 to assign it to your production system afterwards.
For non-SAP systems, either the ports in transaction IDX1 have to point to a reference SAP system, or you copy the metadata with transaction IDX2.
I come to mean that if you double click the OutBound Parameter in the Partner Profile you will be allowed to choose the Idoc type like Matmas,Debmas blabla..
There after providing the receiver destination in that partner profile which is nothing but your Maintaining Metadata through a port,
which on double click leads to RFC destination alloted with a port to transfer its data from sender to receiver Server.
<b>Step-3 :</b> Goto SLD and do the following.
Access the System Landscape Directory (SLD) to maintain the technical systems for the sender and receiver business systems of your system landscape.
You have to define a technical system (and a client in the case of SAP systems) to which your business system belongs.
When you define a client number, you also have to specify the corresponding logical system name in the Technical System Browser.
<b>Note:</b>
The technical system configuration is not required if your business system is configured as a data supplier for the SLD.
<b>Step-4 :</b> Goto Integration Directory and do the folllowing.
Access the Integration Directory to define your business systems as services without party.
a) Either you can choose from the Objects Business Service where your client is defined for it.
With this Selected Business Service you just rightclick and choose ASSIGN TO BUSINESS SCENARIO.
b) Second choice is to choose the business system which was done in SLD.
Do the receiver determination and interface determination but since the adapter is not required to choose for Idoc dont do sender determination.
<b>Note:</b>
The IDoc adapter only uses the service definition (business system) together with the corresponding adapter-specific identifiers in the Integration Directory.
The maintenance of your IDoc sender system in the SLD is therefore not sufficient.
It is recommended that you assign your business system definition retrieved from the SLD to a service in the Integration Directory.
<b>Nut-Shell:</b>
Using this information about the system ID, client, and logical system name for a specific business system, the IDoc adapter is able to specify the corresponding service in the XML header. Routing is then based on service names.
You need the
 logical system, SAP system ID, and client for an IDoc receiver SAP system
 SAP system ID and client for an SAP system
 logical system for a non-SAP system.
This means that the business systems used for the routing definitions in the IDoc-XML message header are retrieved from the adapter-specific identifiers of the service definitions in the Integration Directory,
where for each business system client, the corresponding system ID, client, and logical system name is defined.
<b>Caution:</b>
Use the import function to retrieve the adapter-specific identifiers for a service (business system) to avoid double maintenance in the SLD and Integration Directory.
<b>Step-5 :</b> Steps in Integration Repository.
Export the IDoc in Imported Objects.
Double click the Idoc to view the structure.
This Idoc type is decided in the partner Profile.
See step-3 for further details.
Create the Interface Objects like
1.Data Type for Receiver File.
2.Message type which wrapps this Data type.
3.Interface Type.
a) For Sender Idoc just drag the Idoc name which you have loaDED IT IN YOUR imported objects.
b) For Receiver File It just wrapps the Message type of the file.
4.Message Mapping:
The Fields selected in the data type for the file should be the mandatory fields in the Idoc.
Since the Idoc is in the sender side,it just performs similar operation like selecting things from a database.
Begin and Other Attributes are neednt be worried to map.
The Mandatory fields which was chosen will need to be mapped with the target file.
5.Interface Map:
Just Wrapps the Message mapping.
<b>Step-6 :</b> BD64 is to Distribute the Idoc to Various Acceptors.
1.Create Model View.
2.Add Message Type to it.
3.So that it displays your model view with your Message type like MATMAS.
4.Goto Environment and click Generate Partner Profiles.
5.Executing it,you will get a log indicating the Partner,port and Outbound Parameters.
6.After Doing this goto Edit Menu available in the tool Bar and give Distribute.
7.After distributing it ,it shows your logical system name along with the technical name.
8.Now to fill the IDOCs with Data we have to go to Transaction bd10.
9.We can give our own selection criteria’s and select the list of materials accordingly.
10.Now to check whether the IDOCs has been correctly created and sent to the receiving system (in this case it is the SAP XI Server)
11.we have to check it out in Transaction WE05.
12.Now we can go to the Location we specified in the Configuration where the file will be created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.