This document is purely based on PI point of view:

Scenario: (Inbound) : Xml File to Idoc:

Prequisites:
1) You must see/check the source structure/format.
If source is file then what is the file format (tab delimited file, csv file, pipe
delimited file, xml file) and then you must check the file structure that what
are the filed names and structure hierarchy, occurrence of fields.
2) Similarly check for target structure/format.
In Idoc case, we see the occurrence of idoc fields.
3) Mapping rule give in mapping sheet.
Compare the source fields give in mapping sheet is available in source file or
not.
Compare the target fields given in mapping sheet is available in target
structure (Idoc) or not.
And the thoroughly check the Mapping rule givenand clear all the queries if
any.

Start Development:
PI development is divided into two parts: 1) ESR 2) ID
1) ESR (Enterprise Service Repository)
Few setting needs to be done in SLD (System Landscape Directory), we
usually dont do these tasks. These are handled by client or onsite people.
Step1. Choose Software Component version.
Step2. Create namespace.
Step3. Create data type:
For source structure (xml file): If source structure is very complex then
we can ask FO to provide the source Schema (.xsd file) otherwise we
usually create source schema (by creating the data type)
For target structure (Idoc): No need to create any data type. Simply
import the idoc structure in ESR and then there are 2 ways to use it.
Directly use the structure in mapping or you export the .xsd structure
in system and then import it as External Definition.

Step4. Create message type:

In message type we have to provide the data type name and in idoc
case, no need to create message type
Step5. Create Service Interface:
For source structure: provide the message type name
For Target Structure: Provide the external definition name if you have
used idoc structure as external definition otherwise no need to create
service interface in case of idoc.
Step6. Create Message Mapping:
Mapping is done between source message type and target message
type in left to right fashion. Then as per mapping rule given in mapping
sheet, do mapping accordingly from source to target.
Step7. Create Operation Mapping:
In operation mapping you have to provide the source service interface
and target service interface (otherwise the idoc structure if not used as
external definition).Then provide the message mapping name.

2) ID (Integration Directory)
Step1. We have to check whether we have to use business system or
business component (we can use any one unless someone confirms for the
specific one).If we choose business system, then we cant create that (this is
done by onsite/client) but if we want to choose business component then we
can create it under ECC system name.
Step2. We have to create the source sender channel for sending the file
from 3rd party to PI
(file channel)
Step3. We have to create the target receiver channel for sending the file
from PI to ECC (idoc channel)
Step4. Create Configuration Scenario
Step5. Create Sender Agreement, Receiver Determination, Interface
Determination, Receiver Agreement and include all these including both
channels in Configuration Scenario.

Overall Flow (Flow starts form ID, goes to ESR and

finally ends in ID):

Step1. Sender agreement: PI picks file form the 3rd vendor using sender
channel.
Step2. Receiver determination: Here PI will look for ECC Communication
Component
Step3. Interface Determination: Here we have already provided our
Operation mapping name, so it will go to ESR and look for Operation Mapping.
In operation mapping message mapping is included so it will get executed
(and throws error if any).In message mapping PI will convert the source file
into Idoc structure
Step4. Receiver Agreement: here PI will look for idoc receiver channel and
will send the idoc to ECC via that channel.