SAP PO Practice
cases
Different cases or Scenarios of B2B
and A2A connections an enterprise
might use to develop and manage
Integrations.
A File-To-File Transfer from one company
to other
• Objective :- Transferer a local file to a remote server.
• The test case would need access to SLD to create a Business
system to send data from local server to another company.
• To over come this, I have used Two Business Components.
The ESR Setup of file-to-file
• ESR:- I have created all the Components such as
• This is the process I have followed in most of my scenarios while linking
one component to another
Data types Message Types Message mapping Service Interface
Operation mapping
• In Message mapping I have used a user defined function to lookup the
message id of the transaction and give it to the receiver end point payload.
• Service interface I have used asynchronies inbound and outbound process.
• In Operation mapping I have used the inbound and outbound service
interface.
The ID configuration of F2F
Business Component:
• I had to create two Business component since I had no Business System
created in SLD, so I used two Business component for source and receiver.
• Communication channel :
• Sender Channel Adapter:
• File Adapter: Adapter type as File and sender , Transport protocol as FTP, Source
directory as Dummy , Server and port are dummy
• Receiver Channel Adapter:
• File Adapter: Adapter type as File and receiver Transport protocol as FTP receiver
directory as Dummy Server and port are dummy
Integration Configuration(ICO)
• ICO as I come to understand is an agreement between the sender
and receiver to exchange the data between them.
• Configured:
• Used Sender Business Component (Assumed as Business System) And
outbound service interface linked to it.
• Setup
• Inbound Processing I set Sender Communication channel.
• Receiver I set Receiver Business Component.
• Receiver Interface I set Operation Mapping.
• Outbound Processing I set receiver communication channel.
Testing of F2F
scenario
• I have tested the ICO in PIMON and monitored the test case.
• Used the goanyware to create a remote site and given the host address I the
communication channels
• The delivery states was success the remote folder received the file.
• Used WinSap to simulate a remote system with goanyware credentials
Exchange of data between two
databases
• Objective :- A JDBC-to-JDBC scenario to move data from one
database to another database.
• Obviously to send data from B2B we would need the SLD,
but I think it would make much difference whether it is the
B2B or A2A configuring the Database to send data and
receive the data is the main goal.
The ESR Setup of JDBC-to-JDBC(J2J)
• Components Created
• Data types Message Types Message mapping Service Interface
Operation mapping
• datatypes I have created sender normally but for receiver used a
JDBC pattern to insert data into a database.
• Service interface I have used asynchronies inbound and
outbound process.
• In Operation mapping I have used the inbound and outbound
service interface.
Integration Directory (ID)
configuration
• Business Component:
• I had to create two Business component since I had no Business System created in SLD,
so I created two Business component for source and Receiver.
• Communication channel :
• Sender Channel Adapter:
• Adapter type as JDBC and sender.
• Transport protocol as JDBC 2.0.
• Gave driver and connection details as dummy.
• Wrote Query SQL statement and Update SQL statement.
• Receiver Channel Adapter:
• Adapter type as JDBC and receiver.
• Transport protocol as JDBC 2.0.
• Gave driver and connection details as dummy.
Integration Configuration(ICO)
• Configured:
• Used Sender Business Component (Assumed as Business System)
And outbound service interface linked to it.
• Setup
• Inbound Processing I set Sender Communication channel.
• Receiver I set Receiver Business Component.
• Receiver Interface I set Operation Mapping.
• Outbound Processing I set receiver communication channel.
TESTING
• I couldn’t test my JDBC-to-JDBC case because I didn’t
have any database to create my test sender database
table and test receiver database table.
• tested the ICO In PIMON and monitored the
message(failed case).
Synchronies SOAP Adapter
• Objective :-
• Create a webservice to get serial number from local SAP server and
post the data to a non-local server.
• Configure a Synchronies communication.
• Create a webservice or use an existing one.
ESR setup for Soap-to-Soap
• Created two datatypes source sender and source receiver.
• Message mapping was done so that the source sender and source receiver
are both mapped to the third external definition (assumed as a WSDL
webservice)
• For this scenario I didn't create my own web service but used a preexisting
External definition file exported it and imported it to mu namespace.
• The source sender sends a service request and waits for the response.
• The Source receives picks up the response.
• Created a synchronies service interface for source and Target.
• Used the service interface to create an Operation mapping.
Integration Directory (ID)
configuration
• Business Component:
• I had to create two Business component since I had no Business System
created in SLD, so I created two Business component for source and Receiver.
• Communication channel :
• Created two communication channels as sender channel and receiver
channel
• Sender Channel Adapter:
• SOAP Adapter: The Transport protocol is HTTP. Set a dummy URL
• Receiver Channel Adapter:
• SOAP Adapter: The Transport protocol is HTTP. Set a dummy URL
Integration Configuration(ICO)
• Configured:
• Used Sender Business Component (Assumed as Business System)
And outbound service interface linked to it.
• Setup
• Inbound Processing I set Sender Communication channel.
• Receiver I set Receiver Business Component.
• Receiver Interface I set Operation Mapping.
• Outbound Processing I set receiver communication channel.
Testing:
• I couldn’t test my soap sender because I did not create or
use an existing web service
• I wanted to test the scenario in SOUPUI and explore its
contents.
• I have monitored the Synchronoss communication in PIMON.
Using a Protocol for
communication(HTTP)
• Objective :-
• To build a Synchronies Scenario ware a non-local service asks for a data In
local server and gets a response in HTTP format.
• To create a Http service using eclipse.
• Sidestep
• Did not create any ESR Objects but reused the already created objects in
SOAP scenario.
• since we are sending data between two protocol the process of creating
ESR Objects would be same as a WEB service.
Components Created For HTTP-to-
HTTP
• SLD :
• Scenario was to get a Serial number from a local Http server and post the
response to a non-local Http server. I would have to uses a Business System but
created a Business component instead.
• ESR : As mentioned above used the soap components.
• ID:
• Created two Business Components and used the service interfaces created in the
soap scenario again.
• Created communication channels for Source And Target.
• Adapters are HTTP for Both sender And Receiver channel
• Http URL is Dummy since I could not create a HTTP service in Eclipse.
Integration Configuration(ICO)
• ICO :
• configured :
• Used Sender Business Component (Assumed as Business System) And outbound
service interface linked to it.
• The service interface is the same one that i used in the Soap scenario.
• Setup
• Inbound Processing I added the Sender Communication channel.
• Receiver I added the Receiver Business Component.
• Receiver Interface I added the Operation Mapping(Dummy did not create in the
ESR).
• Outbound Processing I added the receiver communication channel.
Testing the HTTP scenario
• I could not test the scenario because I did not create a http
service to request for data and wait for the response.
• Wanted to test the scenario in postman tool.
• Rather than to use two nonlocal HTTP servers I wanted to
explore more about the http server that is available in sap
system.
Use File data to send an Email to
Users
• Objective :-
• Get the data from a file in local system and send the data to users
through a mail
ESR Setup for file to mail scenario
• Data type for the receiver I used an External definition to
minimize errors while picking up the data.
• Datatype for sender I have used just form ,to ,Subject and context.
• Message types by assigning source datatype to source message
type and same follows for target.
• Service interface I have used asynchronies inbound and outbound
process.
• In Operation mapping I have used the inbound and outbound
service interface.
Integration Directory (ID)
configuration
• Business Component:
• I had to create two Business Components.
• Communication channel :
• Sender Channel Adapter:
• File Adapter:
• Adapter type as File and sender
• Transport protocol as FTP
• Source directory as Dummy
• Server and port are also dummy
• Receiver Channel Adapter:
• Mail Adapter: Configured the SMTP URL and tested.
IDOC_AAE Outbound scenario
• Objective :-
• To Send an Idoc from our SAP system to a non-local server that
saves the Idoc as a file.
• This scenario has no real merits to it according to my knowledge.
This is just to see and work with IDOCs.
The IDOC setup requirements
• we are setting an Idoc as a sender Business system is
mandatory since I don’t have access to SAP. I have
extracted an existing idoc.
• I have Imported the Idoc as external definition in ESR.
• I have used ED as both source and receiver message type and
created message mapping.
• Created asynchronies Service interface for source and target.
• Created an operation mapping using the service interfaces.
Integration Directory (ID)
configuration
• Business Component:
• I have created two business components but if I had used a Idoc I
would have used a business system instead.
• Communication channel :
• Created sender and receiver communication channel
• Configured the sender CC with file adapter but if I had used a idoc I would
have used Idoc adapter instead.
• Configured the reviver CC with file adapter.
• while Setting up the adapter as file I followed the same settings I used in file-
to-file scenario.
Integration Configuration(ICO)
• configured :
• Used Sender Business Component (Assumed as Business System)
And outbound service interface linked to it.
• Setup
• Inbound Processing I set Sender Communication channel.
• Receiver I set Receiver Business Component.
• Receiver Interface I set Operation Mapping.
• Outbound Processing I set receiver communication channel
Testing the idoc scenario which is just a
file-to-file
• testing this scenario would be no different than testing a
file-to-file scenario. I used file adapter for both
communication channels since I did not have access to SAP
system IDOC.
EDI( Electrical Data Interchange)
• To Better understand the Concept of IDoc we need to Know EDI
• An Idoc is nothing but an standard template of XML format that is used to
understand and convert a standard type of EDI format.
• Example for 850 EDI is a standard for orders so a standard Idoc Orders.order05 is
used to convert the EDI file into the XML format.
• EDI can be of different Types based on there usage.
• Frequently used standard to send EDI messages are Ansi x12, EDIFACT and RNIF
• ANSI x12 is used in US based companies
• RNIF(RosettaNet) is used in high tech company’s.
• EDIFACT is used mostly in Europe.
EDI format a differences
• Ansi X12,EDIFACT and RNIF are just standards while EDI message
type doesn’t change they differ in structure.
• They employ different kinds of security.
• They use different type of delimiter.
• The use cases also differ.
• 850 of ANSI x12 is technically similar to Orders of EDIFACT.
• They use case is completely based on the type of company for
example an company based on Trading and shipping products
would prefer to use EDIFACT over ansi x12 and RNIF
Working With EDIs
• B2B Transaction between partner company to SAP.
• The Sender EDI Format could Be Anything Ansi x12, EDIFACT or RNIF but
the components created do not differ.
• Set ISA sender ID in SEG06 and Receiver ID in SEG08
• Set GA sender ID in SEG03 and Receiver ID in SEG04
• We can find the type of EDI file in the ST header section SEG02.
• There can be multiple GA-GS blocks but only ONE ISA-IEA block
• Multiple GA-GE blocks are found when multiple types of files are grouped
in a single ISA block
EDI’s & IDOC’s
• For any of the adapters we would need to mention the Expected URL path
because the message is sent over the internet.
• The Idea is to receive a grouped EDI file from a partner company split the EDI
file and map each EDI to IDOCs in SAP.
• Most of the time EDIs are grouped together and processing them would be
complicated so we need an intermediate channel to separate the incoming
EDIs and then map each GS-GE block to IDoc for every iteration of GS-GE
block.
• For example we could send multiple types of file like 850 and 997 in a single
ISA block with one GA containing ST 850(seg02) and the other ST containing
997 in seg02 of an other GA.
EDI Separator
• EDI separator is a type of adapter used to process EDI files and filter them
• We need to configure two EDI separators one to receive an incoming EDI
message and the other to feed the processed EDI message to the IDOC.
• The conversion is done at the sender EDI Separator.
• No mapping is needed in between the EDI sender channel and the EDI
separator receiver channel because the data has not been processed yet.
• The operation mapping is done between the sender EDI separator an the
IDOC channel.
NRO Maintenance
• NRO maintenance is used to check our B2B scenario weather
all the messages are reaching there destination or not
• We create a variable in our B2B cockpit by given the variable
mentioned in the ISA header in our EDI file and giving a
maximum and minimum values.
• When ever a EDI file is successfully sent the counter
increment the min value.
• By doing the we can check any irregularities in our messages.
THANK YOU
for your patience
