ADAPTERS

1) transactional data

.xml format

Sender --> PI --> Receiver

native sql --> xml --> .pdf

ADAPTERS --> IT IS A MEDIUM WHICH SAP PI WILL USE TO CONNECT AND SEND OR RECEIVE THE DATA

1) SAP ADAPTERS--> SAP ADAPTERS WILL BE USED TO CONNECT SAP BASED APPLICATIONS .

ECC,S/4, CRM ,SCM,SRM, FIORI,ARIBA,PLM,

1) RFC -> SYNCH / ASYNCH

2) IDOC-> ASYNCH

3) ABAP PROXY--> SYNCH / ASYNCH

2) NON SAP ADAPTERS --> NON SAP ADAPTERS WILL BE USED TO TO CONNECT NON SAP BASED
APPLICATIONS.

1) FILE-----> WE WILL USE FILE ADAPTER TO CONNECT ANY FILE DIRECTORY / FOLDER WITH IN
COMPANY NETWORK OR OUTSIDE THE COMPANY NETWORK ( DATA WILL IN THE FORM OF FILES (
.TXX, PDF,JPG))

ASYNCH ONLY

2) SFTP --> WE WILL USE FILE ADAPTER TO CONNECT ANY FILE DIRECTORY / FOLDER FROM SFTP
SERVER WITH IN COMPANY NETWORK OR OUTSIDE THE COMPANY NETWORK ( DATA WILL IN THE
FORM OF FILES ( .XML, .TXT, PDF,JPG))

ASYNCH ONLY

3) JDBC--> WE WILL USE FILE ADAPTER TO CONNECT ANY DATA BASE APPLICATIONS WITH IN
COMPANY NETWORK OR OUTSIDE THE COMPANY NETWORK ( DATA WILL IN THE FORM OF FILES (
.TXX, PDF,JPG))

ORACLE, TERA DATA, SYBASE, HANA, DB2, MS ACCESS, MANGO DB (native sql)

SENDER ---> ASYNCH ONLY

RECEIVER -> SYNCH / ASYNCH

4) JMS---> WE WILL USE FILE ADAPTER TO CONNECT ANY MESSAGE
QUEUE APPLICATIONSBASED WITH IN COMPANY NETWORK OR OUTSIDE THE COMPANY
NETWORK

MAINFARME SERVER, WEBSPHERE, MQ SERVER

SENDER ---> ASYNCH ONLY

rECEIVER -> SYNCH / ASYNCH

5) SOAP--> WE WILL USE FILE ADAPTER TO CONNECT ANY WEBSERVCIE APPLICATIONS WITH IN
COMPANY NETWORK OR OUTSIDE THE COMPANY NETWORK

WEBPAGES

SYNCH / ASYNCH

6) MAIL--> WE WILL USE FILE ADAPTER TO CONNECT ANY MAIL SERVERS WITH IN COMPANY
NETWORK OR OUTSIDE THE COMPANY NETWORK

OUTLOOK, YAHOO, GMAIL,

ASYNCH ONLY

7) HTTP_AAE--> WE WILL USE FILE ADAPTER TO CONNECT ANY WEBSERVCIE APPLICATIONS WITH
IN COMPANY NETWORK OR OUTSIDE THE COMPANY NETWORK

WEBPAGES

SYNCH / ASYNCH

8) REST->> WE WILL USE FILE ADAPTER TO CONNECT ANY WEBSERVCIE APPLICATIONS WITH IN
COMPANY NETWORK OR OUTSIDE THE COMPANY NETWORK

WEBPAGES, MOBILE APPLICATIONS

SYNCH / ASYNCH

9) EDI SEPARATOR-> WE WILL USE FILE ADAPTER TO CONNECT ANY EDI BASED APPLICATIONS
WITH IN COMPANY NETWORK OR OUTSIDE THE COMPANY NETWORK

ASYNCH ONLY

10) AS2 --> ASYNCH ONLY

TYPES OF DATA TRANSFERS

1) ONE DIRECTIONAL OR ASYNCHROUNUS ( RQUEST ONLY)

2) BI -DIRECTIONAL OR SYNCHROUNUS ( REQUEST & RESPONSE )
 HISTORY OF SAP PI AND DEPARTMENTS
1) development--->

FS -->
interface -->

dev -->

unit testing & Functional testing

QA -> SIT, UAT

TS
Production-->

2) support--->

service now, remedy, jeera, HR berry ,,

3) incident --->

--------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------>

History

PI history

1) BC -> BUSINESS CONNECTOR

2) XI --> EXCHANGE INFRASTRUCTURE XI 1.0, 2.0, 3.0

3) PI --> PROCESS INTEGRATION -> 7.0 , 7.1,7.3,7.31, 7.4

4) PO ---> PROCESS ORCHESTRATION 7.5

 STACKS AND SAP ENGINES

BC--> Business connector

ABAP stack + Java Stack

XI -> 1.0,2.0,3.0

ABAP stack + Java Stack

Stack ->

SAP PI --> 7.0,

ABAP stack + Java Stack

7.1,--> Java stack must --> ABAP stack optional

7.3--> Java stack must --> ABAP stack optional

7.31--> Java stack must --> ABAP stack optional

, 7.4--> Java stack must --> ABAP stack optional

SAP PO --> 7.5 -> Java stack only

SAP PI /PO Engines -->

1) Integration engine---> it is responsible for transferring the data between abap stack and java stack .

2) mapping engine--> it is responsible for executing the mapping rules between source and target
structure .

3) adapter engine--> it is responsible for adapters functioning

4) BPM engine ---> it is responsible for functioning

business process management flows

Point to point

1 sender --> pi --> 1 receiver

message (data ) flow -->

Dual stack---> ABAP + JAVA STACK

1) Adapter engine --> integration engine --> Mapping engine --> Integration Engine--> Adapter
engine
Single stack--> JAVA ONLY
1) Adpater Engine --> Mapping Engine -> Adapter engine
 PI PO DIFFERENCES AND PI COMPONENTS
pi --> po

sap -> dual stack -> java stack

bpm + brm -> separate pacakage

po -> pi +bpm+brm -> single package

---------------------------------------------------------------------------------------------------------------------------------->
pi components
----------------------->
1) SYSTEM LANDSCAPE DIRECTORY -> SLD --> THIS IS THE PLACE WHERE WE CREATE OR DEFINE THE
INTEGRATION DETAILS WHICH WE ARE DEVOLPING

1) PRODUCT
2) SOFTWARE COMPONENT VERSION --> ESR DEVELOPMENT
3) TECHNICAL SYSTEM
4) BUSINESS SYSTEM --< ID DEVELOPMENT

SRI JAYA VEDONR --> MM

2) ENTERPRISE SERVICE REPOSITORY --> ESR --> THIS IS THE WHERE WE CREATE THE SENDER AND
RECEIVER STRUCTURE AND PERFORM THE MAPPING

1) NAMESPACE
2) DATA TYPE
3) MESSAGE TYPE
4) SERVCIE INTERFACE
5) MESSAGE MAPPING

6) OPERATION MAPPING

3) INTEGRATION DIRECTORY --> ID---> THIS IS THE PLACE WHERE WE CREATE THE SENDER
COMMUNICATION CHANNEL AND RECEIVER COMMUNICATION CHANNEL FOR RESPECTIVE ADAPTER AND
MERGE THE MAPPING

java stack

1) sender comm channel

2) recv comm channel
3) integration configuration --> ico

dual stack

1) sender comm chnanel

2) recv comm channel
3) sender agreement
4) receiver agreement
5) interface determination
6) receiver determination
4) COMPONENT MONITORING HOME -> MONTORING -->

this is the place where we moniotor the deployed interface flow ->

1) communication channel monitor

2) message monitor
3) performance monitor
4) idoc adapter monitor

5) NETWEAVER ADMINITSTRATOR -> NWA

this is the place we create the system user & authorization system setup -> Basis people
 SAP PI PO First Interface

Scenario:
File (Non-SAP)—File (Non-SAP)
Adapter
Behaviour—Asynchronous
Module- Material Management (MM)
Example : Aurobindo----SaiLabs

STEP1: open the server and in that go to Chrome or mozila firefox

To access the server go to this link http://stposrvr.st.com:50000/dir/start/index.jsp
Select the SLD(System Landscape Directory)
STEP2: Click on product

STEP3: Select the BY PRODUCT because we are creating for the first time and then
click on NEW

STEP4: Select the “CREATE A NEW PRODUCT” as we are creating for the first time
STEP5:
Enter the product name, product vendor and version like below
(“Aurobindo_MM”, www.sailabs.com or Aurobindo, 1.0) and click on next

STEP6: Enter the instance name, in this we give the client name and click on next
STEP7: Enter the vendor, Name and version and click on finish
(www.sailabs.com, Aurobindo_MM_O2C (sub module of MM),1.0)
STEP8: After creating the product and software comment we will use them in ESR
Click on ESR(Enterprise Service Repository)

STEP9: Click on DESIGN OBJECTS

STEP10: Click on Paper icon in this we need to import from SLD
Expand the work Areas—select the software component
STEP11: Click on import from SLD and then click on Display
Search with the created SLD client name like *Aurobindo* and click on GO

STEP12: Select the created SLD and click on import

STEP13: Click on CREATE

STEP14: After clicking on CREATE button. Need to select the original language
(ENGLISH/GERMAN) it is mandatory to select. And save it
Creating ESR Objects
In this we create NameSpace, Data Type, Message Type, Massage mapping and
Operation Mapping.
Material Management Data fields
Material Number, Quantity, Material Type, Material Name, Manufacture Date,
Expiry Date, Storage condition, Batch Number, Material transfer date, MRP, Total
Price

STEP15: Go to Design objects and search with Letter A which we created and
expanded the created SLD and select it.

STEP16: Click on Paper icon and go to the work areas and expand and select the
NameSpace
Always Namespace will start with
http://aurobindo.com/MM/O2C/MaterialInfoTransferToSaiLabs
After giving the namespace click on create

STEP17: Click on Save and then after saving we need to Activate the created
object. This should be done for every object which we create
To activate go to Namespace definition and activate (it is deployment)
Creation of Data type
STEP18: Select the created Namespace and click on paper icon (create object)
Go to the interface object and select the Data Type
For this scenario we need to create 2 data types that is one for sender and other
for receiver. Because we are using FILE adapter in this adapter the behaviour is
Asynchronous (Request only).
When we use Synchronous at that time, we need to create 4 data type those
Sender (request and response) And receiver (request and response)
Always Data type naming should start with DT
Ex: DT_MaterialInfoTransfer_From_Aurobindo_Sender(Optional)
After giving the Data type name click on create
STEP19: After creating select the Node and right click and select the insert sub
element

STEP20:
In each row enter the field which we have gathered for MM in sender side
We need to give 3 mandatory fields
Field Name—MaterialName
FieldType—XSD.string(In SAP PI always we this type only because it is a
alphanumeric)
Occurrence—Min occurrence (0(Options it comes or not) and 1( at least one time
it occurs))
Max occurrence (1(Max one time occurrence) and Unbounded
(Unlimited))
***These are mandatory types which we need to give FieldName, FieldType and
Occurrence will be given in the mapping doc.
To give multiple rows at a time right click on the element and select the insert and
then insert rows (In this enter the no of rows we want)
Instead of selecting xsd.string we can copy and paste for other elements

STEP21: After giving all the required elements we need to check whether we
entered correctly or not
To check that go to data type and select the CHECK
STEP22: After entering save the elements and data type and activate it
STEP23:
Creating Data structure for Receiver. In this we create same data fields like sender
to do that select the sender data type which we created and right click and select
copy object

Give the receiver data type name

DT_MaterialInfoTransfer_To_SaiLabs
And then click on copy

STEP24: Click on activate

Creation of Message Type

Asynchronous—2 message types for sender and receiver
Synchronous—4 message types for sender (request and response) and Receiver
(request and response)
STEP25: To create message type highlight the namespace and go to the paper icon
and go to interface object and select the message type.

STEP26:
Always start with MT for message type name
MT_MaterialInfo_Transfer_From_Aurobindo
After that click on create

STEP27: After clicking on create we need to select the sender data type
To do that go to the data type used and select the sender data type and click apply
Save and activate it
If we change any data field in sender or receive data type then we need to refresh
in message type for both sender and receiver
STEP28: Receiver message type
Highlight the namespace and go to paper icon and select the interface object as
message type
MT_MaterialInfo_Transfer_To_SaiLabs

STEP29: Select receiver data type in data type used

Click save and activate

Creation of Service Interface

It defines the mode or behaviour of communication
 We create only 2 service interfaces either synchronous or asynchronous
1) Sender and
2) Receiver
STEP30:
Select the namespace and go to paper icon and then go to interface object and select
the service interface. In this also there are 3 main fields which we need to give

Service interface name should always start with SIS (Service interface syn) and SIA
(Service interface Asyn)
SIA_MaterialInfo_Transfer_From_Aurobindo
SIA: Inbound Asynch-- Receiver
SIS: Inbound Synch-- Receiver
SOS: Outbound Synch-- Sender
SOA: Outbound Asynch--Sender
Then click on create

Three mandatory details in service interface are

1) Category---- Inbound (Receiver) and Outbound (Sender)
2) Mode--- Async and Sync
3) Request--Message Type—select sender or receiver
Receiver Service interface
SIA_MaterialInfo_Transfer_To_SaiLabs
Fault Message type: Sometimes when the receiver unable to send the response to the
sender at that time fault message type will send the response from this as a fault

STEP31:
Creation of Message Mapping
To do that highlight the namespace and go to the paper icon and select the message
object and select the message mapping
Give the name like MM_MaterialInfo_Transfer_From_Aurobindo_To_SaiLabs
If it is synch means in that last, we give like
MM_MaterialInfo_Transfer_From_Aurobindo_To_SaiLabs_Request
Message mapping: It is mapping between the sender and receiver
Synch—there will be 2 massing mapping
Request (Sender and receiver MT)
Response (Receiver and Sender MT)
Asynch—there will be only 1 messaging mapping--- request (Sender and receiver MT)
After giving click on create
STEP32:
In this step we need to drag and drop the source (Sender) and target (Receiver)
message types

In the above under receiver side there is red colour indicator which means it is
mandatory (Min occurrence is 1)
Mapping can be done in 3 options
Method 1
Double click on Target element and after the respective source element we need
to click
Right to left mapping with their respective elements

Select the white box of source and map to the target box
After mapping colour of red will change to green

Method 2
Left to right means drag and drop from source to target
In this there is a disadvantage by mistake we might map to different element
instead of mapping with the same element. So apply the method 1

Method 3
This is easy method but we won’t use. When we need to use this means when
source and target elements has same structure/fields. This mapping is called
mass mapping
To do this
Select the node elements of source and target and click on apply mass mapping
symbol
After completing the mapping we need to test whether it is correctly mapping
or not
To do this
Click on test and enter the fields elements like below

After giving click on the video symbol

Test Result
We can also save the test result also by doing this

After performing all of them save and activate it

STEP33:
Creation of operational mapping
For Sync or Async we create only one operational mapping. It is used during the
run time
Name : OM_MaterialInfo_Transfer_From_Aurobindo_To_SaiLabs
And then click on create
In source operation we select the sender service interface and in target
operation we select receiver service interface
To do this we need to drag and drop on their respective operations

After doing drag and drop click on the read operations

Select the message type and click on apply and save and activate
Creation of Technical and Business Systems
Technical Systems we create 2 systems for sender and receiver
Business systems also we create 2 systems for sender and receiver
To create technical system we need to go to the SLD in that click on technical
system
Click on new technical system
 Types of technical systems
1) AS ABAP—This is used for SAP applications. We select this TS if we have
SAP application on sender or receiver
2) AS Java--- This is used only for JMS adapter
3) Standalone--- We won’t use this as it is for practice purpose. Even though
they give also we won’t use it.
4) Third Party--- This is used for Non SAP applications (like FILE, SFTP,
JDBC….)
As we are using FILE adapter so we select the Third Party TS and click on next

After clicking Next we need to give the

System name and host name like below and always start the system name with TS
System name: TS_AUROBINDO
Host Name: WWW.AUROBINDO.COM
And then click on next

After that we need to select the product which we have created under installed
products by searching with the created product *AUROBINDO*
We need to select the product and also software component and click on finish
After clicking on finish, we need to create the sender side business system to do
that click on the Business System and click on Add new business system

Click next
Business systems in sender side will have 3 like for development, Quality and
production
We are creating for development environment so we need to give as
Name: BS_AUROBINDO_DEV
And then click on next

Click on Next
Click on Finish

Click on Save
Technical and Business Systems for receiver

Select Third party as the receiver side also we are using the FILE adapter
Give the system name and host name (TS_SAILABS, WWW.SAILABS.COM) and then
click on next

After select the product and software component and click on finish
We need to create the business system for receiver
Business systems in receiver side will have 3 like for development, Quality and
production
Click on business system and click on Add new business system
Click on next

Give the Name: BS_SAILABS_DEV

Click on next

Click on Finish and save it

Importing the Business systems of sender and receiver in the ID(Integration
Directory)

Go to the ID
To import go to tools and click on assign business systems

Click on continue

Click on continue
After that in the next window we can see all the created business systems in that
we need to select our business system of sender and receivers which we have
created.
If we are unable to see the business system then we need to clear the SLD cache 2
times
Select both the sender and receiver BS and click on finish
After assigning the sender and receiver Business systems we can those BS under
the “communication component without party”
Expand it and under that expand the business system so in that you will find the BS
systems which we have assigned

If the assigned business system is in pencil symbol that means it is in edit mode still
not yet activated
To activate that right click on the sender business system and click on activate

In the below select receiver BS also and click on activate

Creating the communication channel for sender in ID
We need to select the communication component without party under that
business system and select the assigned sender business system
Right click on the communication channel and click on new
Give the communication channel name always start with CC
CC_FILE_SND_MaterialInfo_Transfer
After that click on create
After creating in the parameters tab we need to give the following
Need to select the adapter type for that click on the Box which in the last and
select the adapter which we use. For our scenario we FILE adapter, so select that
one and click on apply
In this the fields which are mentioned with * those are mandatory
1) Transport protocol
2) Message protocol
3) Adapter engine
Transport protocol—Defines the connectivity that means How PI need to
connect the particular directory.
In this there are 2 types of protocols
1) File system (NFS)
2) File Transfer protocol (FTP)

1) NFS—When we select this file system means when the folder is in within
the company network, PI OS and folder OS should be same.
2) FTP—it is a file hosting server. When the folder is in FTP server either it
can be in within company network or outside the company network at
that time we use this
In our scenario we use NFS transport protocol
Message protocol will define the data format
1) File—The file which we take in .XML then we use this
2) File Content Conversion—Other than .XML we use this like if the file is in
.pdf,.doc ..
PI understandable format is .XML
In this we use file message protocol

Adapter engine will be having only one that centre adapter engine
Next we need to give source details for that go to the source tab and give the
following details
Source directory—in this we need to give the file location folder details.
We need to create the folder in the F drive for both sender dev and receiver dev
F:\Aurobindo_DEV
file name—If we give
*-- all files will pick
*.xml—All files related to xml will pick
Mat*.xml—all files related to mat. Xml will pick
Mat*-- all files which contains with t letter will pick

MaterialInfo.xml
We will give the details for processing
Go to processing tab and enter the processing parameters
1) Quality of service
2) Poll interval
3) Processing Mode

1) Quality of Service--- There are 3 types of quality service

a) Best Effort—This is used for Sync
b) Exactly Once—This is used for Async
c) Exactly once in order—This is used for to send the data in queue order
(This we wont use)
For file adapter we exactly once quality of service

Poll Interval—60sec (1 Min) --- For every 60 sec the communication channel will
run and check whether the file is there or not and processes the file.

**Processing Mode—it has

a) Archive—File from source directory to archive directory (back Up directory)
after processing. If we select the add stamp means it shows the time and
date. In real time we use this only
b) Test—it will be in the same folder it processes repeatedly
c) Set to read only—It will be in the same folder but it is in non editable mode
d) Delete—After data sent from the sender adapter then the data will be
deleted
Archive faulty source file—Some time we get half data files or junk files at time
we can archive here

In the bottom of the page there is Duplicate Handling

If we enable means it controls the duplicate files. Once processed files we don’t
use them again means we enable this. After processing 5 times It stops
processing
Disable channel—when the limits exceed the channel then is gets disable
After processing tab go to the advanced tab
Adapter status and Adapter Specific Message Attribute will be there

Adapter Specific Message Attribute—we need to tick this field by default

Adapter Status—When we keep the channel status to Active means it runs and
when it is in Inactive channel will run. When we don’t want to work means we
keep inactive and if we want to work means we keep active
After giving all the required fields we need to save and active the channel

ASMA— it is used when the sender and receiver file is same

Ex: If sender side file name is Krishna means and same file if we want o use for
receiver then we need to enable it

Creating Receive communication Channel in ID

Go to the created receiver business system and right click and then click on
create new communication channel

Enter the receiver communication channel name like

CC_FILE_RCV_MaterialInfo_Transfer and then click on create

We need to select the receiver adapter type which is FILE and click on apply
Under the adapter type we need to select the Receiver because we are creating
the receiver communication channel

Need to select the transport protocol and message protocol which is NFS and
File
In target tab we need to give the target file path which we have created in F
drive with the server
Target Directory: F:\Sailabs_DEV
Always uncheck the Create Target Directory because by default it will be
checked
Give file name scheme: If we select the ASMA means we need to give *, because
sender and receiver file name are same in our scenario or else if we won’t select
ASMA we can give filename as per the requirement
Now go to the processing tab in that give all the mandatory fields which are in *
Under processing parameters
**File Construction Mode
1) Add Time Stamp: It will add the server time stamp. In real time we use this
2) Create: it creates the file
Overwrite exciting: It over rides the old data with new data if we check the
box
3) Append: Old data and new data will merge
4) Message Id: A unique message id will be generated for every PI processed
that will add to the file name. In real time we use this
5) Counter: It adds the serial numbers to the files

In real time we use mostly Add time stamp and message ID

We select the add time stamp

In advanced tab
When we have enabled the ASMA in sender at the same time we also need to
enable the ASMA in the receiver side also
After giving all the parameters we need to save and activate the receive
communication channel

Creation of ICO (Integrated configuration)

It will be visible under communication component or else by clicking on paper
symbol there are also we can see this ICO
In this ICO we need to give the sender details like sender side communication
component that the sender business system
Communication Component: BS_AUROBINDO_DEV
Interface: Sender service interface we need to select
Name space: after selecting the sender service interface automatically
namespace will be visible
Service interface

NameSpace
After giving all the sender details click on create

After creating go to Inbound processing this is sender agreement in dual stack

tab
Select the sender communication channel and click on apply
Go to the Receiver tab this is receiver determination
Select the receiver business system under communication component
Then go to the receiver interface tab
This is interface determination in the dual stack
We need to select the operation mapping and click on apply
Go to the outbound processing tab
This is receiver agreement
We need to select the receiver communication channel and click on apply
After giving all the required information we need to enable the locks which is in
advanced settings tab go to that and enable the locks. It is mandatory to enable
Select the use scenario specific configuration in Staging and select the store for
all
Select the use scenario specific configuration in Logging and select the Log for
all
This is useful in troubleshooting
Save and activate it
By the above steps interface development is completed
We need to start the communication channel for sender and receiver then only
we send or receive the data
Go to the Configuration and Monitoring
In that go to adapter Engine and select the communication channel Monitor

Go to the ICO and inbound processing and copy the sender channel and paste in
communication channel monitor
Paste in Find and click go
Select the channel and click on start
At the same start the receiver channel also by following above just copy paste
the receiver channel in find and click GO
Now we need to keep the file in the sender folder to do that
File name should be same which we have given in the sender communication
channel Like MaterialInfo.xml

Go to ESR
Select the created interface in that go to message mapping
Go to the test tab and click on the SRC icon
Copy and paste the XML data in the note and save with MaterialInfo in sender
(Source) folder and While saving the .xml file we need to select all files in save
as type

After that we need to monitor this file in the sender communication channel
monitoring tool
While running the channel message id will be generated
If we click on that message id means we can know the status of the message
After successfully processing the file stop the sender and receive channels

For message monitoring go to the monitoring tab and select the message
monitoring in that copy paste the name space (interface)
http://aurobindo.com/MM/O2C/MaterialInfoTransferToSaiLabs

Go to PI Messages tab under that tick on message header data

Paste the name space under interface Name space and scroll down and click go
 Scenario 2
FCC SENDER (File Content Conversion)
Sender side file adapter what ever the data we are taking other than .xml
like .csv,.txt files how these files need to take that is our scenario
.txt to .xml conversion
FCC—File Content Conversion or Flat file
** FCC will support only 3 level hierarchy
There are 2 types of FCC
1) Delimeter Separated File--- it is special character that’s using the
special character between fields (, |,:,…..etc)
2) Fixed length file—It will have fixed length that means their wont be
any special character. It contains length for every field
Whenever we create an interface there is no need to create software
component, technical system and business. When there is
requirement then only, we create them.
If we are using the same client and same related data means there is
no need to create Software component, technical system and business
system.
Links for FCC
https://erpwiz.wordpress.com/2017/01/22/file-content-conversion-on-sender-file-adapter-
fcc/#:~:text=Many%20a%20times%2C%20you%20are,file%20or%20a%20comma%20separ
ated(.

https://integrationlearn.com/sap-pi-adapter/file-adapter-sender-convert-single-fixed-length-
structure-to-xml/

https://blogs.sap.com/2014/08/21/content-conversion-for-fixed-length-files-with-key-field-
value-shorter-than-key-field-length/
Step1:
Same software component we are creating the Data type
First, we need to create the Name Space
Give Name as http://Employee_Details_Trannsfer_To_Sailabs
Click on create

Save and activate it

Now create the data types for sender and receiver

Click on paper icon and go to interface objects and select the data type
and give the DT name as follows
Sender DT name: DT_Employee_Details_Transfer_From_Aurobindo
Click on create
Enter Fields of employee like
Employee Name, Employee ID, Employee Phone, Employee Address,
Employee Email
In type definition select the Node and right click and click on insert and
then sub elements
To give multiple rows right click on the element and select the insert
rows

Give the no of rows like 3

 In this occurrence we are taking as 1 but we need to take as per the
requirement
Save and activate it

FCC will support 3 level hierarchy only for example

Give another element name under the node and the element name is
Record
In our scenario we are using 2 level hierarchy
In the RECORD is the child of parent node that is
DT_Employee_Details_Transfer_From_Aurobindo and remaining
elements are children for RECORD
Save and activate it

Now we need to create the Data type for receiver to do that

Copy the sender data type by right clicking on the sender data type
and select the copy object

Give the receiver DT name as

DT_Employee_Details_Transfer_To_Sailabs and then click on copy and
activate it
We create the message types for sender and receiver
Click on the paper icon and go to interface objects and select the message
type

Receiver Message type name :

MT_Employee_Details_Transfer_To_Sailabs and click on create
Select the receiver data type and name space and then save and activate
it

Sender Message type name :

MT_Employee_Details_Transfer_From_Aurobindo and click on create
Select the sender data type and name space and then click on save and
activate it

We need to create the service interface for sender and receiver

Go to the paper icon select the interface objects and select the service
interface

Give the service interface name like

SOA_Employee_Details_Transfer_From_Aurobindo
Then click on create

Select the category for sender it is outbound, mode is async

And select the sender message type
Save and activate it

Create service interface for receiver

Give the name as : SIA_Employee_Details_Transfer_To_Sailabs
Select the category for receiver it is inbound, mode is async
And select the receiver message type
Save and activate it
Create the massage mapping
Click on paper icon, Message objects and select the message mapping

Give message mapping name as

MM_Employee_Details_Transfer-From Aurobindo_To_Sailabs
Then click on create
Then select the sender message type and receiver message type
Drag and drop the sender MT in source and receiver MT in target

As we have same structure for sender and receiver so we perform the

mass mapping
We can test the data by giving but at this time we not testing and not
saving the test data because
Sender side is not xml file it is txt file and also we are not keep in file
directory
Save and activate it
To get the elements under the record means we need to do like below
Select the child element and right click and then click on lower like this
we need to do for all the elements which we have
Note for sub element (Record) we won’t select the Type only
occurrence will be there.
Creation of Operation Mapping
Go to the paper icon and click message objects and select the operation
mapping

Sync or Async we create only one operation mapping

Give the name as OM_Employee_Details_Transfer_To_Sailabs
 In Definition tab select the source service interface and target service
interface.
We can do drag and drop or else select from the box

Click on read operations and select the message mapping and then save
and activate it

Now we the create the communication channels for sender and receiver
Go to the Integration directory
If we create new ID means then only we will use the SLD business system
At this point we are using already created business system
Give the Sender communication channel name as
CC_FILE_SND_Employee_Details_Transfer
Then click on create

After that in parameters type we need to select the adapter which we are
using and then click apply
We need to select the
Transport protocol: File System (NFS)
Message Protocol : File Content conversion because our file is in non xml
format
When we select the FCC there you will find the extra tab that is content
conversion
In the source tab we need to give the
Source directory path and file name
Source Directory: F:\Aurobindo_DEV
File name: Employee_Details.txt

Create employee details note pad in the F drive save with the
Employee_Details.txt as we gave the same name in the sender source
communication channel.
Next tab processing give the following
Quality of service: exactly once as it is async
Poll interval: 60
Processing mode: test

Next Content conversion tab

Give the content conversion parameters
Document Name: We need to give the sender message type (
MT_Employee_Details_Transfer_From_Aurobindo)
Document Name Space: We need to give the name space (
http://Employee_Details_Trannsfer_To_Sailabs)
**Document Offset: if we give 1 means it ignores the first line or if we give 2
means it ignores first 2 lines. If we don’t want to ignore anything means we
need to give 0
Now we are giving as 1 so it ignores 1 first line
Recordset Name: when ever we have 3 level hierarchy then the 2nd node is
treated as recordset name
But in our hierarchy, we have only 2 level so we don’t keep this parameter
**Recordset structure: in our message type how many nodes we have that
many we need to give
In the hierarchy if we have 3 levels means then we give the 3rd node
In our structure what ever there are in 3rd level nodes we treat them as
recordset structure
Syntax: Node name,occurrence
Record,* (unbound)
Record,1( occurrence )
If there are 3 level hierarchy like below we need to keep
Header,* (unbound),item,1 (occurrence 1 time)
Recordset per Mesaage: If we want to generate the file for every record
means then we select this
For example If we give as 5 means it picks 5 records and gives 1 file
In real time we wont use this parameter
**Key Field Name: If we have multiple nodes in the sender structure to
identify for what structure we need to populate the value to know that this
key field name will identify. As we have only one node so we don’t use this
After that we need to give the field names we need to add the message
type field names in this
If we have multiple nodes means we need to add each and every node
values in this parameter
Record.fieldNames:
Employee_Name,Employee_ID,Employee_Phone,Employee_Email
Record.fieldSeparator: ,
Record.endSeparator: ‘nl’ always we need to keep nl in single codes. This
means new line
fieldNames and endSeparator is common for both fixedLength File and
delimeter file
Record.missingLastFields: This parameter is used for those fields which are
missed
Ignore: leaves
Add: adds the last field
Error: channel will go to error
This is not mandatory but we add this

keyFieldValue is mandatory for fixed length when we have multiple nodes

**ignore recordset name this is very useful when there is no 2nd level
hierarchy then we keep true or else false. This is mandatory when there is
no recordset name

Now go to the advanced tab as we cant select the ASAM because sender
side file is .txt and receiver is .xml
Save and activate after giving all the required values

Now receiver communication channel

As we are using the XML file for receiver so we are not creating the channel
using the existing channel
As we are not using the ASMA we need to change the file name as
Employee_Details.xml

In advanced tab need to disable the ASMA

Save and activate it

We need to create the ICO
Go to the paper icon
Select the sender communication component and sender service interface
Click on create
In inbound parameter we need to give the sender communication channel

In receiver parameter give the receiver business system name

In receiver interface we need to give the operational mapping

In outbound processing we need to give the receiver communication
channel

In advanced setting we need to unlock them and Save and activate it

 Scenario 3 FCC RECEIVER
FCC Receiver side other than xml format
Every time when we create FCC we need to create Node in receiver Data type
Namespace FCC Receiver

Data Types Sender and Receiver

Message Types for sender and receiver

Service Interface for Sender (SOA) and Receiver (SIA)

Massage Mapping

Operation Mapping

Creation of Sender and Receiver Communication channels in ID

Creation of ICO

Sender and receiver communication channels we need to start

 SCENARIO 3
PASS THROUGH
This is used for files
Sender side File and Receiver side also File
No Mapping Needed
No ESR Needed
Even though we can send the data from one system to another system this is
called pass through
Some time we don’t know the source technical details (Host Name, third Party,
Environment, IP Address) but we need to do the interface or integration at that
time we use business component instead of business system

Difference Between Business system and Business component

Business System Business Component
It is created in SLD that means it is We create directly in business
SLD dependent. In SLD we need to component in ID
create technical system
A business system is always Business Component do not have an
associated with a technical system entry in SLD

Go to the Integration Directory and select the Business Component

Right click on Business component and click on New

Give the BC name as BC_Aurobindo then click on create and save activate it

If we are using business component means if we have ESR part then we select
the sender side add the outbound service interface in sender side. If it is in
receiver side means we use receiver side service interface
We didn’t create anything in ESR so we won’t add anything in this

We need to create the communication channel

Go to the created Business component and right click on communication
channel and click on New

Give the communication channel name as CC_FILE_Pass_Throgh_SND and

then click on create

Select the file adapter and select the sender

In pass through always we select file as a message protocol even though it is
xml or pdf or any other formats.
Give the source directory and file name ( * )

And in processing tab we won’t do anything

In advanced tab we need to select ASAM for pass through this is mandatory to
select
Save and activate it

Right click on business component and click the receiver BC

Give name as BC_Sailabs
Receiver communication channel
In this we can create the business system receiver communication system or else
create a new communication channel for receiver in the business component
I am creating the new business component receiver channel in business
component
Right click on the communication channel in BC and give the name as
CC_FILE_PASS_THROGH_RCV
Give the target directory and file name ( * ) and also uncheck the create target
directory

In processing tab there is no change but in advanced tab we need to enable the
ASMA

Save and activate it

Creation of ICO this is important in pass through

Right click on ICO and click on New

In communication component select the business component and click on apply

Then interface and Namespace we need to give the dummy names like
SIA_EMP_Pass_Through and http://EMP_Transfer_Pass_Through
And click on create

Select the sender and receiver business components

In receiver service interface we need to give the dummy interface and name
Space

In outbound processing we need to select the receiver communication channel

In advanced tab need to unlock the logs

Save and activate

We need to go to the communication channel
And start the sender and receiver channels
 SCENARIO 6
SOAP SENDER

Namespace FCC Receiver

Data Types Sender and Receiver

Message Types for sender and receiver

Service Interface for Sender (SOA) and Receiver (SIA)

Massage Mapping

Operation Mapping

Creation of Sender and Receiver Communication channels in ID

Creation of ICO

Sender and receiver communication channels we need to start

SOAP: To connect any websites/ web applications we use this adapter
Behaviour: Synch/Asynch
SOAP adapter is WSDL file based connectivity
WSDL (Webservice definition language) --- The application which we get from
Webservices and want to use through SOAP adapter we need WSDL for both sender
and receiver
SOAP Adapter--- The data which we send through SOAP Adapter that will be in XML
format

Scenario: SOAP to FILE

Create the Name space like below
http://SOAP_SND_EX
Creation of Data types
We can create new data type structure or else copy from other name space data
types
If sender side or receiver side has same data structure means we can complete the
scenario with 1 data type and 1 massage type
Some times we create our own structures for sender and receiver at that time if
Asynch means 1 data type and 1 message type is enough or else if Synch means 2
data types ( request and response ) these data type we use for both sender and
receiver.
Mainly for ABAP scenarios
SOAP to proxy we get this kind of scenarios in real time
Web application--- SOAP
ABAP Proxy—SAP Applications (ECC, CRM, SRM, etc..)--- We can create our own
structure
For Synch if ABAP proxy is in receiver side and SOAP is in sender side then we use
SOAP sender structure for receiver side also.

Synch Asynch
1 data type
4 data types Sender – SOAP
Sender request & response--- SOAP Receiver—ABAP Proxy
Receiver Request & response--- ABAP Proxy
We can same sender structure in the receiver side

While copying change the name space which we have created for SOAP sender
I am creating only one data type as we have same structure for sender and receiver

Active it

Creation of message type

in this we create only one message type as we are using same structure for receiver
side also
MT_SOAP_SND

Drag and drop the data type under the Name in data type used place. After that
save and activate it

Creation of service interface

We need to create 2 service interfaces
Sender service interface
SIA_SOAP_SND

Category as outbound as it is sender

Select the message type then save and activate it

Receiver service interface

SOA_FILE_RCV
Category as inbound as it is receiver
Select the message type and then save and activate it

Creation of message Mapping

MM_SOAP_SND_EX
Drag and drop the message type on source and target as we are using same
structure for sender and receiver so we need to drag same message type for both
source and target

Perform the mass mapping because sender and receiver has the same structure so
we are doing mass mapping. Save and activate it
Creation of Operational Mapping
OM_SOAP_SND_EX

Drag and drop the sender and receiver service interfaces on source (Sender service
Interface) and target (Receiver service interface). Select the message mapping
After that save and activate it
Creation of communication channels for sender and receiver
Go to the ID (integration directory)
CC_SOAP_SND_EX

Select the adapter type as SOAP

Transport Protocol
1) HTTP
2) Servlet (Axis)
3) Task (Axis)
4) No Task (Axis)

Before Pi 7.4 that PI 7.1,7.31 there is no REST adapter

1) HTTP—For SOAP adapter we need to use only HTTP
2) Servlet (Axis)— In old versions this protocol will convert SOAP adapter to REST
adapter
Difference between SOAP and REST adapter
Message protocol for SOAP adapter always we need to keep SOAP 1.1
In General tab
HTTP security level
1) HTTP
2) HTTPS without client authentication
3) HTTPS with client authentication

When ever there is HTTPS there will lock symbol, it is secure?

Security parameter is used for banking purpose we won’t use it
Processing parameter
Best effort—Sysnch
Exactly once—Asynch we use this one
Save and activate it

SSL certificate has the validity

If we are connecting to PI server if url has HTTP means we select the HTTP
2) HTTPS without client authentication—There is no need to give our certificate
we take their certificate and authenticate
We need certificate mandatory
3) HTTPS with client authentication—Exchanging the certificates that means I
will give my certificate to them and they will give their certificate
If my company wants to authenticate

Authentication is of 2 types
1) Mutual authentication--
PI server should also be in HTTPS url

***Downloading of HTTPS certificate

Go to browser and open any HTTPS server

Click on the lock symbol

Click on the certificate

Click on details and copy to file

Select the BASE-64 and click next

Click on browse and give the path where we want to save and enter the file name
and click next

Click finish

We need to download this certificate for both with or without client authentication

After downloading the certificate, we need to place in

SAP NetWeaver Administrator

Go to configuration tab and click on certificates and Keys

Select the trustedCAs and click on import

Select the entry type as X.509 certificate and browse the file

Certificate has the validity when the validity expires it doesn’t work at that time we
need to delete that certificate and import the updated one. We wont get any alert
for expiry of validity we need to make note of it.
Receiver communication channel
CC_FILE_RCV_MaterialInfo_Transfer
We are not creating a new receiver channel using the existing channel and doing
some modifications
Un select the ASMA and change the file name as SOAP.xml
Save and activate it
Creation of ICO
Select the communication component, interface and click on create

Select the sender communication channel

In receiver interface select the operation mapping

In outbound processing select the receiver communication channel

In advanced setting tab enable the locks
Save and activate it
When ever we do SOAP sender side scenario after completion of ICO
We need to generate the WSDL file
***How generate WSDL file means
Go to ICO and in integrated configuration select the display WSDL

Click on save and select the path where we want to save the file
 ***How to import the SSL certificates
PI—SSL certificate
NWA—Configuration—certificates and Keys---TrustedCAs—import—select
X.509.certificate

***After completion of ICO we generate the WSDL file by going into ICO integrated
configuration and select the display WSDL
ICO---Display WSDL
***We need to test WSDL file
For SOAP and REST there are 2 testing tools where we test for webservice
applications
1) SOAPUI
2) Postman

Open the SOAPUI application

Go to File and click on new project
If we are using SOAP adapter means need to select New SOAP project
If we are using REST Adapter means need to select New REST project
Now we need to select the New SOAP Project
Enter Project name and select the WSDL file which we have saved from ICO and click
OK

In the below screen we need to give the values to give go to the ESR
Message mapping in test tab select the SRC and copy the content from material
number to material dat
Right click on the data and click on format
Click on validate
Start the communication channels
To start go to ICO and in integrated configuration select the open channel monitoring
for sender and receiver

After starting the channels click on play symbol which is submit

In right side column there is unauthorised for that in the left hand corner side click on
Auth
Select the add new authorization
Select basic and click OK

Enter the PI server username and password

After giving username and password click on submit

On right hand side click on RAW tab

Go to the sender communication channel and click on GO

After successful testing

END POINT URL
http://stposrvr.st.com:50000/XISOAPAdapter/MessageServlet?senderParty=&sender
Service=BS_AUROBINDO_DEV&receiverParty=&receiverService=&interface=SIA_SOA
P_SND&interfaceNamespace=http://SOAP_SND_EX
Syntax:
http://Hostname:portno/XISOAPAdapter/SenderBusinessSystemName/SenderServic
eInterface/InterfaceNamespace
PI Username and password, WSDL file, END point, these we will give to the client
PI SSL certificate with client authentication
NWA—configuration—SSL—in this we download our SSL certificate
Click on the export Keystore View to PSE File

General Tab
Conversion Parameters
1) Do not use SOAP Envelope--- If we don’t want to mask means we use this option
that means data will not mask
2) Keep Headers--- if we want to send any data in header means we will use this
option that means if we want read the values from header
3) Keep Attachments—In case if we want to the attachments along with the data
means we need to select this option
4) Use Encoded Headers
5) Use Query String
SOAP data will come in Envelope that means data will be masked
In SOAP by default data will appear in Body

In PI supported adapters for attachments are SOAP, REST, MAIL, SFTP (Non- SAP) and
ABAP Proxy (SAP)
 SCENARIO 7
SOAP RECEIVER

Scenario
File to SOAP
SOAP is at receiver side then receiver application will give the following details for
us
WSDL File, Server, End Point, User name and password
In WSDL file structure is inbuilt so in SOAP receiver we won’t create data type and
message type

Create the namespace

http://SOAP_RCV_SAMPLE
Save and activate
Creating data type for sender no need to create for receiver side
Change the namespace and save activate it

We need structure for SOAP receiver

Now we need to import the WSDL file
Go to ICO—IC—Display WSDL—save in the path
To import WSDL go to paper symbol and go to interface objects and select the
External Definition
Give name as
ED_SOAP_RCV_SAMPLE
In file select the path where the file is located
After importing go to the message tab and check whether the data is available or
not
Save and activate
Creation of message type for sender
MT_FILE_SND_SAMP

Drag and drop the sender data type and save activate it

Creation of service interface

We need to create service interface for sender and receiver
Sender service interface: SOA_FILE_SND

Drag and drop the message type and save activate it

Receiver service interface: SIA_SOAP_RCV

Select category as inbound and mode as Asynch
Under request we need to select external message
PI will support External file and WSDL file
When ever we import the WSDL or external file we need to select the external
message

After selecting the external file save and activate

Creation of Message mapping
MM_FILE_To_SOAP_RCV
Drag and drop the sender message type in source and External definition in target
side and perform the mass mapping
Save and activate

Creation of operation mapping

OM_SOAP_RCV_SAMPLE
Select the sender and receiver service interface and massage mapping after that
save and activate

Creation of communication channels

Sender channel copy the file sender channel and change the name for our scenario
Right click on the file sender channel and select the copy object and then change
the name of the channel

CC_FILE_SND_MaterialInfo_Transfer_SOAP

Change the file name as File.xml and then save and activate it
Receiver channel
CC_SOAP_RCV_SAMPLE

Select the adapter as SOAP and select receiver

Transport protocol, message protocol and adapter engine will not change
Target URL means End point
Application receiver will give the target URL/end point to us and that one we need
to keep in this target URL place
http://stposrvr.st.com:50000/XISOAPAdapter/MessageServlet?senderParty=&send
erService=BS_AUROBINDO_DEV&receiverParty=&receiverService=&interface=SIA_S
OAP_SND&interfaceNamespace=http://SOAP_SND_EX
copy paste the end point which given by the receiver in the target url field

Enable the configure User authentication and enter the client given user name and
password but for our use we are giving our server user name and password
***Configure Proxy
In any company we can’t access all the web sites that’s means there is a firewall
which will block that website
Every time when we hit the URL that is not mandatory to be in company network it
might be in outside the company network
To enable the firewall, we use the proxy servers/web dispatcher
There are 2 types of proxy servers/web dispatchers
1) Reverse Proxy—It takes the request which we get. It is used for SOAP Sender
side
2) Forward Proxy—It forwards our request. It is used for SOAP Receiver side

After completing SOAP scenario if there is any firewall then proxy team (Network
team)
We send the end point to the reverse proxy team then they will give one URL that
URL we give to the SOAP sender

Proxy is a middle ware between sender and PI

It is SOAP receiver so we use forward proxy but now we are not using as we are
doing practice
Save and activate
Creation of ICO
Select the interface
Enable the locks in advanced tab

Save and activate it

***SOAP Action: It determines which operation to call
If our WSDL file having multiple operations to call the particular operation we use
this
In SOAPUI Operations will be in service interface

Start the sender, receiver and end point channels

When we start the SOAP receiver channel at that time, we need to click on the Ping
channel mandatory
 SCENARIO 8
REST Sender XML format

REST Adapter is used for web services and mobile applications

REST adapter supports XML and Json format data
REST will support the attachments

****Difference between REST and SOAP

REST SOAP
REST without WSDL connectivity SOAP WSDL Based connectivity
REST will support XML and JSON SOAP will support only XML
REST light weighted—compared to SOAP will support only GET and POST
SOAP REST performance is fast methods
REST will support CRUD (GET, PUT,
POST, DELETE)
REST supports Custom error Handling
REST supports O-auth

***Difference between GET and POST

GET--- Data will be passed in the URL
POST—Data will be passed in the message body

We create ESR part for REST for sender and receiver

Creation of name space in ESR
Name Space: http://REST_SND_XML_EXAM
Save and activate

Creation of DATA type

Copy the material data type and change the name space
Creating only 1 data type because using this data structure for both sender and
receiver
Save and activate

Creation of message type

Creating only 1 message type because using this data structure for both sender and
receiver
MT_REST_XML_SND_EXAM
Drag and drop the data type
Save and activate

Creation of service interface for both sender and receiver

Sender service interface
SOA_REST_XML_SND_EXAM
Drag and drop the message type
Save and activate

Receiver service interface

SIA_REST_XML_SND_EXAM
Change the category and drag and drop the message type

Creation of message mapping

MM_REST_XML_SND_EXAM
Drag and drop the message type on source and target and perform the mass mapping
Save and activate

Creation of operational mapping

OM_REST_XML_SND_EXAM
Select sender and receiver service interface click on the read operations
And select the message mapping save and activate it

Creation of communication channels for sender and receiver

Sender communication channel
CC_REST_XML_SND_EXAM
REST Adapter is available after PI 7.4 version only

Select the adapter type as REST and select the sender

In general tab
Transport protocol will be HTTP
Message protocol will be REST
Data format will be 2 XML and JSON
For our scenario we select XML
Quality of service will be best effort (Synch) and exactly once (Asynch)
If we select Best effort then output message format need to update
Ours is Asynch so we select exactly once

In Channel selection tab

For rest adapter we need to prepare our own END POINT because it is not WSDL
connectivity
Select the Specify End point
End point name should be unique this is
/REST
In REST resources tab
Select the URL Pattern custom pattern
/XML_RCV_EXAM
In Rest Operation tab
Select the value source as manual value
In static value we select the method what ever we use like get, post, put, delete
In our scenario we select the post method
Save and activate it

For file receiver we are not creating any channel using the existing channel
Creation of ICO
Select the communication channel
Select the interface
In inbound processing select the communication channel

In receiver tab select the receiver channel

In receiver interface select the operation mapping

In outbound processing select the receiver communication channel

In advanced setting enable the locks
Save and activate it

***End point format:

http://Hostname or IPaddress:Port No/RESTAdapter/REST/XML_RCV_EXAM
http://stposrvr.st.com:50000/RESTAdapter/REST/XML_RCV_EXAM
This end point we need to test in SoapUI or postman
In SoapUI
Select the New REST Project
Give REST end point URL and click OK

Select the method as POST

In media type select the application/xml

In message body we need to give the sample data for that

Go to the mapping and how we prepare the test data for file adapter we need to
prepare like that
Copy the material information data from file adapter and paste in the REST sender
XML message mapping
Then test whether the values of the data is getting correct or not
Copy REST sender message mapping data and paste in SoapUI tool in message body
We can give the headers also in REST

To test in SoapUI we need to give the username and password

Start the channels sender and receiver

In SoapUI click on the submit after that on right hand side
Under raw tab we will find code 202 ok that means it is working

***After completing REST sender testing, we need to give the following details to
receiver
End Point
PI username and password
Sample data
Method
 SCENARIO 9
REST Receiver XML Format

REST Receiver we need to create Data type and message type mandatory
Create the receiver name space
http://REST_XML_RCV_EXAM

Creation of data type

We copy the existing data type and change the name space
Creation of message type
MT_REST_XML_RCV_EXAM

Drag and drop the data type

Creation of service interface for sender and receiver

Sender: SOA_FILE_XML_RCV
Drag and drop the message type
Category as outbound

Receiver: SIA_REST_XML_RCV
Category: inbound
Creation of message mapping
MM_REST_XML_RCV_EXAM

Drag and drop the message type on source and target

Perform the mass mapping
Creation of operational mapping
OM_REST_XML_RCV_EXAM

Drag and drop the sender and receiver service interface and click on read operations
Drag and drop the message mapping
Save and activate it
Creation of ID
File communication channel creation
Copy the existing communication channel and change the channel name
CC_FILE_REST_XML_RCV

Change the file name as Mane.xml and save activate

Creation REST Receiver channel
CC_REST_XML_RCV_EXAM

Select the adapter as REST and select receiver

In General Tab
There is no change in transport and message protocols
In case if there is any firewall for end point then we use the proxy (Reverse or
forward proxy)
Select the use basic authentication so give the PI server username and password
In REST URL Tab
We give end point URL which is given by the receiver but in our scenario we are using
our created end point
http://stposrvr.st.com:50000/RESTAdapter/REST/XML_RCV_EXAM

In REST Operational Tab

Value source select as manual
Static value as POST
In Data Format tab
Select the XML format as we are using xml format data
Save and activate it

Creation of ICO

In inbound Tab
Select the file sender communication channel
In receiver Tab
Select the Sailabs receiver

In receiver interface
Select the Operation mapping
In outbound Tab
Select the receiver channel

In advanced tab
Enable the locks and save activate
 MAIL, HTTP, JMS and JDBC ADAPTERS
JMS Adapter
It is used to connect any message queue-based applications
Behaviour: Sender: Asynch only
Receiver: Synch/Asynch
Examples: Main frames, server, WebSphere, MQ Server
For JDBC and JMS firstly we need to install drivers to receive the data
Driver deployment--- we need to collect the queue details
**There is no specific naming convention for JMS only for JDBC there is specific
naming convention.
In ESR for sender 2 DATA type, 2 Service interface, 2 message types, Message
mapping and operation mapping
**For JMS we need to create the As JAVA technical system
For every application there is separate driver syntax this driver will deploy by the
BASIS team
Data will pass through queue
**For JMS receiver if behaviour is synch, then we create 2 communication channels
because data will pass through queue and there will one queue for request and
response
JDBC Adapter
It is used to connect any data base applications
Behaviour: Sender: Asynch only
Receiver: Synch/Asynch
First, we need to deploy the drivers
**For which data base we are connecting for that data base we need to deploy the
drivers in our PI system. These drivers will be deployed by the BASIS team
After deploying the drivers then we need to start the interface
**We need to follow a dedicated naming convention for JDBC for both sender and
receiver
**In JDBC sender data type 1st Node always we create with “row” in small letters
because in data base data will be in rows and columns
Under the created Node with name “row” we need to create the structure
In JDBC receiver data type 1st Node always we create with “any name (Statement)”
like below

Node name and give name as Statement and type as XSD:string

Insert the element and give name as DBTable and type as XSD:string
Insert the attribute and give name as ACTION and type as XSD:string
Insert the element by clicking right click on DBTable and give the name as Table and
type as XSD:string
Insert the element under the Table and give name as ACCESS (Node)
Insert the elements that’s means fields (Name, Id) under the ACCESS (Node) and
type as XSD:string

**In JDBC there will be different structures for sender and receiver

**By using JDBC adapter we perform the following actions

INSERT, UPDATE, UPDATE-INSERT, DELETE and SELECT
In JDBC if we want to perform any action in the data base application, we need to
write a SQL Query

JDBC driver details will be given the data base team

In JDBC sender communication channel JDBC driver and connection will have
different drivers for every data base

In sender communication channel in processing tab we need to give the document

name with message type name and message type namespace this is for mapping
***Query SQL statement: In this if we want to read any data in the data base means
we need to write select query
In JDBC if we want to select the data there are 2 type
1) Select query and
2) Stored Procedure
**How do we call the stored procedure
We use EXECUTE command and write the stored procedure name
**Update SQL Statement: This is used not process the duplicate records
In JDBC receiver communication channel we don’t write any query it will be handled
by mapping
In data base we insert the data by performing the mapping

HTTP Adapter
It is used to connect any web service applications like web sites, web pages
Behaviour: Synch/Asych
It is ABAP stack-based adapter as it runs on ABAP stack
In PI 7.1 it is not possible to use HTTP adapter because there is not HHTP adapter in
java stack
From 7.3 SAP introduced HTTP—AAE Adapter it runs on java stack
This adapter we used in the old versions when there is no SOAP and REST Adapters,
after introducing SOAP and REST adapters this HTTP-AAE is not using
HTTP-AAE supports GET and POST methods only

REST CUSTOM ERROR HANDLING

Instead of sending the system error we can give our custom error to the receiver
Example:
I have received an error with 505 code and system is showing lengthy error message
now I want to send to the receiver less error message
For each rule you have to define a condition and an action. The condition usually
consists of a source and a value, the action can be either raising an error, ignoring
the error, or replying with a custom message.
Two types of error
1) Data error—Mapping error
2) System error

REST OAuth
OAuth is an open standard for authorization, commonly used as a way for Internet
users to log in to third party websites using their Microsoft, Google, Facebook,
Twitter, One Network etc. accounts without exposing their password.

MAIL Adapter
It is used to connect any mail server
Ex: Gmail, Outlook,..etc
Behaviour: Asynch
Mail, JDBC, File, SFTP--- these are based on polling concept that means if these
adapters are in sender side means we need to take the data
Mail adapter sender side
Transport protocol will be IMP4 (We use this protocol mostly) and POP3 these are
mailing server protocols
Message protocol: XIALL and XIPayload
Difference between XIALL and XIPayload
XIALL—We can’t send attachments
XIPayload—we can send the attachments

Mail adapter Receiver Side

Transport protocol will be IMP4 and SMTP (we use this protocol mostly) these are
mailing server protocols
 SCENARIO 4 FILE TRANSFER PROTOCOL (FTP Server)

**Advanced Selection for Source file:

Using single sender communication channel, we can send the files from
multiple directories to target by selecting this.
Exclusion Mask: This means if we want to exclude any file means we need to
mention the file name in this tab then those files will exclude and send to the
target
File Name Mask: the files which we are sending to the target in this we need
to mention the file names

FTP Server details we take from tools like WinSCP and FileZilla
First, we need to check whether we are able to access those servers or not to
do that we need to use these tools WinSCP or FileZIlla
FTP there will be different FTP servers for production, quality, development.
We need to change the FTP server details in the communication channel
WinSCP
Select the FTP in file protocol
Host Name or IP address of the
**FTP has by default port no 21
User name and password

Pre
 SAP ADAPTER (RFC, ABAP Proxy and IDOC)
RFC Adapter
RFC (Remote Function Call) Sender
RFC is used to connect the SAP based applications like ECC, CRM, S/4 hana, etc..
RFC/BAPI/Functional module are same
SAP applications all will be in ABAP stack
When we are using ABAP stack, we need to install SAP Logon pad (SAP GUI)
In case PI is dual stack means we can access in SAP Logon pad itself
In SAP Logon pad application, we can access the ABAP based applications
In SAP Logon application if we want to perform any action we need to use “T-code
(Transaction code)”
RFC Behaviour: Synch/Asynch
RFC consists of 3 types
1) Standard—In built—a- to x (If any RFC name starts from a to x that means it is
standard RFC)
2) Custom—New Development—this development handling will be taken care by
ABAP team-- We need to start with Y or Z for RFC name
3) Extended—in built modification—In the last we give the standard name- exten
(Like a-exten)

If we are doing any SAP adapter scenario, we need to do some manual

configuration/set up in ECC and PI
In the below blog there is some set up which we need to do that one we can follow
Blog: SAPTechnical.COM - A Step-by-Step Guide on Asynchronous RFC - to – JDBC Scenario Using SAP PI
7.0

To create RFC/BAPI/Functional module the transaction code is SE37

Functional consultant will confirm the ABAPer what to use either custom,
standard, extended
 Transaction codes
1) SE38—This is used by ABAP’er to write the ABAP code
2) SE11—This is use to create any custom table by the ABAP’er
3) SE37--- To create RFC/BAPI/Functional module
4) SM59—To create RFC destination
5) SMGW—It is used to know the gateway details
6) RZ70---It is used to create the As ABAP technical system automatically
RFC is different and RFC destination is different

To create RFC destination

In SAP Logon application search with SM59
Select the TCP/IP connections and click on paper icon
RFC destination Name, Type, select the registered server program, Program Id,
gateway Host and gateway service and save it and click on connection test

In SAP Logon already on function is opened and if we want to open another function
means we need to type /osmgw
To know the gateway details in SAP logon application type SMGW—GOTO---
Parameters—Display/change
In real time BASIS team will give the gateway details
Program id purpose: It is used to identify the RFC sender channel within the SAP
gateway ( To tell the ABAP system what is the RFC sender channel )

Creation RFC is mandatory for all like custom, standard and extended
For standard RFC creation of functional module in SAP logon application is not
required directly we need to create RFC destination

Creation of ABAP report is mandatory for all like custom, standard and extended
ABAP report is written by ABAP’er
RFC sender side or receiver side then no need to create the Data type, message
type and service interface
RFC will be in SAP system so that we need to import to SAP PI system
In our created software component, we need to import the RFC
Click on the software component which we have created already
Go to imported objects right click and select the import SAP objects
If we get any error means then double click on the system name and give the
following details
System E72, Client 800, Message server- 192.168.1.72 and save
After that go to imported objects and select the import SAP objects
Give the IP address which we have given in system component
ECC username and password

For SAP application we need to create As ABAP technical system

ABAP Proxy
It is used to connect any SAP applications (ECC, CRM, S/4 hana, etc)
ABAP proxy is available from ECC 4.0 version
Latest version of ECC is ECC 6.0
ABAP proxy concept is adapter less communication that is there is no need of
adapter
If ABAP proxy is in dual stack (before 7.4) then ABAP proxy sender side no need to
create sender communication channel and sender agreement
ABAP proxy receiver side in dual stack means we use XI adapter

From 7.5 version integration engine is removed so we need to use adapter engine
mandatorily so we are using SOAP adapter as a proxy
For SOAP adapter in communication channel, we use message protocol with XI 3.0
for ABAP proxy
Because SOAP will support only xml format and proxy is also XML format by this data
transfer is fast
To connect ECC we have IDOC and RFC adapters
In proxy PI structure will be created as proxy class by the ABAP’per
Based on our PI structure ABAP’per will create the proxy
For proxy we need to create mandatorily data type, message type and service
interface. This structure is used by the ABAP’per
In ECC if we execute the SPROXY transaction code means ESR should be visible
If proxy is in sender side means outbound service interface name should be given to
the ABAP’per
If proxy is in receiver side means inbound service interface name should be given to
the ABAP’per
The ABAP’per will go to ECC and execute SPROXY transaction code by this they
should see the ESR part which we have created

In sender communication channel we use SOAP adapter with message protocol XI 3.0
as a proxy
In receiver communication channel we use SOAP adapter with message protocol XI
3.0 and in connection parameter we select addressing type as HTTP Destination
HTTP destination name creation
Go to SAP NetWeaver administrator
Configuration
Destinations
After completing the interface development Inbound (Receiver) service interface
name and Outbound (Sender) service interface name will be given to the ABAP team
After that ABAP team will log in into ECC and execute SPROXY transaction code

ABAP proxy setup in single stack

Step1:
We need to go to SM59 transaction code and create the 2 TCP/IP destinations with
SAPSLDAPI, LCRSAPRFC, these 2 connections are used for SLD connection
1st destination name SAPSLDAPI
2nd destination name, LCRSAPRFC
If it is single stack means we need to create 2 G type destination connections
3rd destination name SAP_PROXY_ESR (ESR Setup) and 4th destination name (SOAP
Adapter details) we should give anything
If it is in dual stack means we need to create 2 H type destination connections
SAP_PROXY_ESR and 4th destination name we should give anything

This is for 3rd destination name SAP_PROXY_ESR

In target host we need to give PI server details and Pi port number
In path prefix we need to give as /rep (Repository) because it is for ESR setup
After that go to log on security and give PI username and password
For 4th destination name we need to give SOAP adapter details

Step2:
After creation of 4 destination names, we need to run this SLDAPICUST transaction
code to append complete SLD content
In this give the system details and click on test then we should get like this
Connection to SLD works correctly
Step3:
SLDCHECK transaction code if we run this code means SLD should open that means
ESR page should open

Step4:
SXMB_ADM transaction code in that call the Integration Engine Configuration
Go to configuration and give IS_URL parameter
Click on edit, new entries, in category select RUNTIME and parameter as IS_URL and
in current value we need to give 4th destination name (dest://4th destination name)

When we have one ECC system and multiple PI systems

Go to SXMB_ADM code and we do sender/receiver ID configuration
For this we need to create separate 4th destination
In data type if we do any modification means we need to inform to the ABAP’per by
that ABAP’per will re generate the proxy
Proxy is fast compared to RFC because it is fast in data transfer
To check proxy message we use SXMB_Moni transaction code
If it is in Red it is in error
If it is in Green it is in schedule (it is struck in queue) we check this struck message in
SMQ1 ( Proxy sender outbound) and SMQ2 ( Proxy receiver Inbound) transaction
code
If it is in black and white flag it is successful

Transaction codes used in ABAP Proxy

1) SPROXY—Used for ESR visible
2) SM59— To create RFC destinations
3) SLDAPICUST--- To append complete SLD content
4) SLDCHECK— To open the SLD (ESR page should open)
5) SXMB_ADM—To call the integration engine configuration and sender/ receiver id
6) SXMB_Moni—To monitor the proxy messages
7) SXMB_Moni— SMQ1 ( Proxy sender outbound) and SMQ2 ( Proxy receiver
Inbound) these are used to check the struck messages

IDOC
IDOC adapter is used to connect any SAP applications (ECC,SRM,CRM, etc.)
Behaviour: Asynch
IDOC has 3 types
1) Standard IDOC –If IDOC name starts from A to X that is standard IDOC
2) Custom IDOC—If IDOC name starts with Y or Z that is custom IDOC
3) Extended IDOC
In IDOC we won’t create DATA Type, Service Interface and Message Type
Standard IDOC types
1) Cremas Vendor related data transfer
2) DebmasCustomer data transfer
3) Invoice Invoice data transfer
4) Orders Purchase orders and orders data transfer
5) Matmas Material data transfer
6) Shicon Shipment data transfer
7) Desadv Dispatch advise

IDOC is basically build on ABAP stack

In IDOC ABAP stack if it is in sender side then no need to create sender
communication and sender agreement
From PI 7.3 SAP has introduced IDOC_AAE which works in java stack only

IDOC settings or ALE Settings (Application Link Enable)

These settings are different for java stack and ABAP stack
IDOC Setup in Dual stack
ABAP Stack
ECC step Up
Step1:
First, we need to create the RFC destination with SM59 transaction code with type 3
SM59 types (3, g, h, t)
SM59 3 type is used for ABAP stack IDOC adapter
SM59 g (Single stack), h (Dual stack) types are used for proxy
SM59 t type is of RFC adapter single stack
Target host is PI server details, Host is PI Host and gateway (SMGW) host and server
details
Step 2:
Port creation
For this we use WE21 transaction code
We need to select the Transaction RFC
Step 3:
Logical system
For this creation there are 2 transaction codes (SALE and BD54)
Step 4:
Creation of partner profile
To create partner profile we use WE20 transaction code
Partner Type KU is used for customer related IDOC
Partner Type LI is used for vendor related IDOC
Partner Type LS is used for PI inbound
For outbound always partner type will KU and LI
Select the required partner type and give the unique partner no and select the
partner type (KU, LS, LI)
If IDOC is in sender side means in outbound we add the below parameters
IDOC type, message type, receiver port
In partner profile we have an option to send the IDOC as a batch that is collect IDOC’s
If we want to send in queue need to select the queue processing
If IDOC is in receiver side means in inbound we add parameters
In receiver side we give the processing code

PI set up
Step 5:
Creation of RFC destination – SM59—type 3
Step 6:
Port creation—IDX1 transaction code
Port name should be 6 characters like
SAP<System ID>
Step 6:
IDX2 transaction code is used to create meta data
Meta data is in segments in IDOC
In dual stack always need to delete the meta data and import it again if there are any
structure change

IDOC Single stack Setup

1) Creation of RFC destination –SM59—type TCP/IP
2) Port creation—WE21
3) Logical system—SALE and BD54
4) Partner profile—WE20
PI setup
In java stack their won’t be any transaction code to create rfc destination
So, for that we need to do
1) Creation of RFC destination—NWA---Configuration—Destinations
Click on create and select destination type as RFC destination for IDOC

2) Inbound RA/ Outbound RA (Resource Adapter)—NWA—Configuration—

Infrastructure—Application resource
IDOC Sender—Inbound RA—JCA Factory
IDOC Receiver—Outbound RA—JCA (Java Connectivity Adapter) Factory

3) IDOC monitor—Meta data creation

In this we preload or reload the meta data
Preload means first time when there is no idoc in this
Reload means already there is IDOC and there is a structure change then we click
on reload

After completing all the settings, we need to start the interface development
In ESR part
For IDOC we won’t create DATA TYPE, MESSAGE TYPE and SERVICE INTERFACE
Instead, we need to go to import of SAP objects and select the IDOC like
ORDERS (Message Type).ORDERS05 (IDOC Type/ Basic Type)
In IDOC data will be in segments and also in records
In IDOC there will be 3 types of records
1) Control Record—It contains the IDOC technical details ( Unique IDOC number,
Direction {1 [ Sender side], 2 [Receiver side]}, Basic type, partner type, partner
number)
2) Data Record—in actual data will be there
3) Status Record – Status of the IDOC
How to identify the control record in IDOC means EDI_DC40
In mapping Specification, we don’t have the control record details
In mapping specification data record related data will be there
Anytime in data we need to hag the begin in IDOC with constant 1
In the same way there will be segment for that also we need to map with constant 1
Direction need to map with constant if IDOC is in sender means 1 and If it is in
receiver side means 2
IDOC type need to map with constant with ORDERS05 which will be in Right hand
side
MESType need to map constant with ORDERS which will be in Left hand side
Follow the below blog for IDOC control log mapping
https://sapintegrationhub.com/pi-po/idoc_aae/idoc-control-record-mapping-in-sap-pi-po/

Status Code for iDOC for monitoring

Status 03—outbound success
Status 53—inbound success
Status 51—data issue
Status 56—partner not selected
Status 30—in progress

When I checked in ECC IDOC is in 03 status but data is not reached in PI where do
we check
We check SM58 transaction code
 ALERTS, TRANSPORTS, MAPPING
ALERTS:
These alerts are used when any interface in PI fails at that time through email we can notify to
the particular persons
This is very useful for support project
Alerts are of 2 types
1) Dual Stack alerts (ABAP based alerts)—It works only in ABAP stack
2) Single Stack alerts (Java bases alerts)—It works on both ABAP and Java stack
Alert rule is available in the ID part (Integration Directory)
Alerts are also called as component based alerts
Follow this blog
https://blogs.sap.com/2012/03/25/michals-pi-tips-component-based-message-alerting/

Step 1: We create alert rule for each priority like P1 (Very High), P2 (High), P3 (Medium) and P4
(Low)

What are the alert consumer details?

Alert to Mail is standardly used for all alerts
Step 2: After creating the alert rule in the ID we need to check in the configuration and monitoring
--- Adapter Engine---Configuration and Administration--- Message Alert Configuration--- In this the
alert rule should be in green colour that is in activate state
Step 3: Java mail client details we need to maintain
NWA—Configuration—Infrastructure—Java System Properties—Services—Java Mail Client
In this we give parameters which are mentioned in the blog
Step4: We need to create the Job
NWA—Operations—Jobs—java Scheduler—Job Definitions
 TRANSPORTS
Transports are used for multiple environments like Development, Quality and Production
In ESR we create the following components NM, DT, MT, MM, OM and SI
In ID we create the following components Sender/ Receiver Communication channels and ICO

We create the objects in only development environment for remaining environments we

transport those created objects from development to other environments (Quality, Production)

In PI there are 2 types of transport mechanism

1) FILE TRANSPORT
2) CTS PLUS TRANSPORT
3) CCMS TRANSPORT—this is also one type of transport but we use mostly File and CTS plus
transports

Always we transport the ESR and ID objects but we wont transport the SLD components through
transports
File Transport
If we want to move entire software component means then select the software component

Right click on Software component and select the export

After clicking on export if in case CTS Plus is enabled means the mode will not be in grade out mode
The mode is by default grade out because there is no CTS Plus

Check the download file to client so that we can save in our desktop and click on continue
Always uncheck the Include deleted objects and skip preview
In Object set we have the following options
1) All Objects of a Software Component version--- This option is used to move entire software
component
2) Only definition of software component version and namespace
3) All objects of individual namespaces--- This option is used to move the particular namespace
objects
4) Individual objects—This option is used to move only individual objects like (MM, DT, OM, MT,
SI)
Click on Finish

After performing the file transport the file will be saved in .TPZ format

To move the particular Namespace

If we want to move a particular namespace means we need to select that particular namespace and
right click on it then select the export

If there are any IDOC and RFC scenarios means we need to select those scenarios because for this
namespace those will not be selected.

In the below screen shot if we want to select the with namespace definition means we need to
check that box

Click Finish
To move the individual objects
For suppose if we want to move the data type then simply we do drag and drop or select the object
which we want to move
Now to need to import the ESR part from development to quality environment

Earlier we have exported the ESR objects from development so now we will import those ESR
objects in the Quality environment
Go to Tools---Import Design Objects

Click on client
Select the exported .TPZ file which we have saved in a path

Click on import
After importing we need to check whether the objects got imported or not
Go to ---Tools—Find Transports
Now moving the ID objects through file transport
In this the objects will have separately so we create a folder in ID to move the ID objects
Creating a folder to move the ID objects is called as Configuration Scenario
Click on the paper icon and select the Configuration Scenario
Give the Configuration scenario name
In this configuration scenario we add all the details related to namespace (Sender BS, Receiver BS,
Sender Comm, Receiver Comm and ICO)
After that save and activate it
This created configuration scenario we will export to the other environments
To check the created configuration scenario we need to click on the binoculus symbol
Select the configuration scenario view

Select the created configuration scenario and right click on it

Select the export
If we want to move individual channel at that time go to the particular channel which you want to
move and right click on it and then select the export
Now to need to import the exported ID objects in the other environment
Go to – Tools—Import Configuration Objects

Select the client

Business systems names will have different for each environment ( Dev, QA, Prod) for that we
create GROUPING in SLD
Go to SLD
Mandatorily we need to grouping for all the business systems
If we don’t create grouping for business system in SLD means we get an error
After creating the configuration scenario in ID those will be available in the change list

In CTS+ transport for every transport the request number will be created

MAPPING
Mapping specification will be given in the FS document
In real time
90% mapping will be Field to field mapping (Direct Mapping no conditions required)
5% Requires Node functions/functions
4% Requires UDF
1% Requires Java Mapping/XSLT mapping

In SAP Mapping functions are classified into

1) Arithmetic
2) Boolean
3) Text
4) Conversions
5) Date
6) Constants
7) Node Functions
8) Statistic

Constants:
It is used when the target side field has always a fixed value that means it doesn’t depend on the
source value. PI consultant will give manual value to the constant so that it always populates that
value to the target side particular field

**CopyValue:
when we have same field values at that time if we want to copy same field value to the other fields
we use this copyvalue function. This copies the index values
It copies the index value from a particular index and populates that value into target side in all the
context (Record {Node} is called context)
If we keep copyvalue(0) means it copies only the starting (1st record) record field value to the other
field values

If we keep copyvalue(1) means it copies the 2nd record field value to all other fields
Sender/receiver business system/component is used during the runtime to populate

Date Function:
CurrentDate: It is used to populate the PI server time to the particular field
If we click on the question mark in that we have options to keep different formats
**DateTransformation:

From side we are getting on date format and that date format need to change in another format in
target side at that time it is used
In some case we need to send some English character at that time we need to add like
DDMMMYYYY
***Text Function:

Substring: In Particular field if I want to take only some specific length of a character means we use
this function
There will be 2 input values Starting Position and Character count
For example I need to only starting characters from 0 and count is 5
Concatenation function:
It is used to concatenate the 2 input values and sends to one field value
To identify the 2 string values we can use delimiter also

EqualsS Function:
It checks the 2 input values whether they are equal or not if it is equal means it returns TRUE or
else FALSE
Touppercase function:
It converts the lower case values to upper case values
ToLowercase Function:
It converts the upper case characters to lower case characters
**Length Function:
It returns the length of the field value
**Trim Function:
It is used to remove the left and right side unwanted spaces from a character.
Note: Trim function cannot remove the spaces between the characters
ReplaceString Function:
It is used to replace the string from source side. It consists of 3 input parameters
1st is source field value, 2nd parameter is the value which we want to change that one we need to
give as constant and 3rd is which we want to replace the value that one we need to give as
constant
Arithmetic function
In this we use mostly Less than, Greater than, FormatByNumber and Round functions
Round function is used to round off the value

FormatbyNumber
It also works same like round function
***Boolean Function:
AND Function:
It returns TRUE if both the input parameters are true
OR Function:
It returns TRUE if any input parameters are true