EDI to IDOC development using B2B Add -on in SAP PI/PO

Scenario: I want to send EDI823 (bank payments) data to Idoc (FINSTA01) using B2B Add -on in
SAP PI/PO.

Prerequisite to implement scenario:

1. We need to install B2B Add-on’s in PI/PO system.

2. Once install the B2B Add-on’s check EDI Content Manager is properly installed or not.

Scenario: IDOC send to PI to Non SAP System (Third party system expects CIDX format)

EDI to IDOC development using B2B Add-on in SAP PI/PO

Scenario: I want to send EDI823(bank payments) data to Idoc (FINSTA01) using B2B
Add-on in SAP PI/PO.

Prerequisite to implement scenario:

1. We need to install B2B Add-on’s in PI/PO system.

2. Once install the B2B Add-on’s check EDI Content Manager is properly installed or not.

ESR object development:

To create EDI823 data type we can use EDI content Manager Tool.

Select EDI type and click on start button then we will get EDI823 xsd datatype.

To create Idoc type we need to import IDOC from corresponding ECC system and we
can map based on the requirement.

ID part development:

Sender adapter configuration:

To covert EDI823 data to XML format we can use File adapter with
X12ConverterModule name.

The above module class automatically converts EDI823 file format to corresponding
XML format.

Receiver adapter configuration:

For Idoc Configuration We have used IDoc_AEE adapter.

• Experienced in configuring scenarios like Soap–Proxy, Proxy-Soap, IDOC-JDBC, EDIFACT-IDOC,

File-IDOC, IDOC-File and File-Mail in PI

1. What are the mandatory parameters in SFTP?

SFTP parameters: Server, Port, Timeout, Server Fingerprint.
2. What is the difference between REST and SOAP adapters?

-
XSLT or JAVA mapping can be imported in ESR by using ZIP or JAR File, we
will be using JAR file for both java and XSLT Mapping
Open ESR  Created Imported Archives object  select JAR file  Save it

Steps required for developing XSLT Mapping

 Create a source data type and a target data type
 Create Message types for the source and target data types.
 Create Message Interfaces includes Inbound Message interface and Outbound Message
interface.
 XSLT Mapping does not require creation of Message mapping, so don’t create any Message
mapping.
 Create an .XSL file which converts source data type into target data type.
 Zip that .xsl file and import it into Integration Repository under Imported Archives.
 In Interface Mapping choose mapping program as XSL and specify this zip program.
(Through search help you will get XSL Mapping programs that you imported under Imported
Archives, select your corresponding XSL Program)
 Test this mapping program by navigating to Test tab.
Steps for creating XSL file using this tool:
1. Open the Alto MapForce, import the source .xml and .xsd file in it
2. Similarly import the target .xml and .xsd in MapForce.
3. These two data files should match with source and target data types in Integration
Repository.
4. Complete the graphical mapping using extensive list of XSLT functions available there.
5. Save the mapping file.
6. Click the XSLT tab. You will have the entire xslt logic there.
7. Copy that content and save it as .xsl file.
8. Zip above .xsl file and import the same into IR under Imported Archives.

Scenario:

IDOC send to PI to Non SAP System (Third party system expects CIDX format)
EDI to IDOC development using B2B Add-on in SAP PI/PO

Scenario: I want to send EDI823 (bank payments) data to Idoc (FINSTA01) using B2B Add -on in
SAP PI/PO.

Prerequisite to implement scenario:

3. We need to install B2B Add-on’s in PI/PO system.

4. Once install the B2B Add-on’s check EDI Content Manager is properly installed or not.
5. How capture error logs in HCI
Groovy script is to manipulate the payload like error message logs.
6. Need to upgrade PI version to PO?
7. Draw backs in HCI when compared to PI?
8. Sender SF and Receiver .Net system, now what are the steps you need to follow to
make the configuration successful.
Now providing On-premise API in order to transmit data for what are the steps need to
be followed other than HCI to make the connection, you will maintain the host and
destination is somewhere, how will you maintain?
Ans: Cockpit and could connector
9. Rest Adapter purpose: REST supports JSON and AtomPub which are part of the
OData web protocol. ... The Advantage of an REST adapter for SAP PI, is that it is
fully integrated with the Adapter Framework, which means that the REST interfaces
can be configure, manage and monitor using the standard SAP PI tools.
10. REST Adapter required configuration:
11. REST VS SOAP

SOAP
REST: - Higher bandwidth and heavy weight
apps
- Limited bandwidth and resources & - stateful operations
more suited for lightweight apps
- Totally stateless operations
- Caching is possible
- No Asynchronous support
- Communicate only over HTTP/HTTPS
- Formats like XML, JSON supported
- It's a style
- Caching not possible
- Asychronous processing and
invocation
- Communiate over web, email, private
networks
- Only XML is supported
- It's an industry standard

12. Have you worked on SFTP Adapter?

13. Receiver parallelism?