SAP introduced B2B Integration Cockpit (add-on) to facilitate all EDI communications of an organization with one component. Let’s look at how to install B2B add-on in Process Integration (PI) or Process Orchestration (PO). We will look at the steps that should be carried out as part of the Post Installation of B2B Integration Cockpit.
B2B add-on (Integration Cockpit) is compatible with following PI and PO versions 7.1 or higher:
Process Integration (PI) with the Advanced Adapter Engine (AAE)
Process Integration installation with Advanced Adapter Engine Extended (AEX)
This article is a step by step guide on how to execute the post-installation steps after the BASIS team deploys the B2B add-on cockpit software. Note, these are only the post-installation steps PI Integration expert should carry out in order to prepare B2B add-on for design time and runtime execution.
We will discuss how to install B2B Enterprise Service Repository (ESR) content and runtime content below.
This includes Adapter metadata for EDI/B2B related adapters. B2B toolkit contains adapter metadata for AS2, EDI Separator, OFTP, and X400 adapters.
B2B Mapping Kit:
This is the repository object which contains B2B mapping templates and User Defined Functions (UDF) delivered through SAP standard content.
B2B EDI Runtime Content:
These are the objects and configuration data required at runtime of an EDI scenario. These include Control Key Information (SAP delivered) and EDI messages versions which are used by the converter for transforming EDI to XML and vice versa. Additionally, XSDs which can be used to create EDI service interface objects are also delivered with the runtime content.
SAP Versions used in the illustration:
SAP PO 7.5
Prerequisites for B2B Integration Cockpit Post Installation:
Before you install the Mapping Kit, Toolkit and Runtime Content, make sure the BASIS team has already deployed the B2B add-on Cockpit software. Once the BASIS team deploys the B2B Cockpit these Software Components should be available in your PI/PO system.
To verify if your system contains required components, go to Netweaver Java Application Server home page (http://<host>:<port>) > System Information, then view B2B component detail under Component Info tab.
Now that we made sure B2B components are available, we can move forward to post installation steps.
Download Software > Support Packages & Patches > By Alphabetical Index (A-Z) > PI B2B ADD-ON > PI B2B ADD-ON 1.0 > COMPRISED SOFTWARE COMPONENT VERSIONS
We require below three files for the setup.
Step 2: Unzip B2B files to your work station.
Files unzip as follows. Mapping Kit and Toolkit zip files contain only one .tpz file each. PIB2BCONTENT00_5-20009370.ZIP file contains Runtime Content, XSDs and com.sap.aii.adapter.archiver.mapping.jar files.
PIB2BCONTENT00_5-20009370.ZIP -> com.sap.aii.adapter.archiver.mapping.jar, Runtime Content and XSDs
Step 3: Install B2B Toolkit.
Import file XI7_3_B2B_TOOLKIT_1.0_05_00.tpz to Enterprise Service Repository (ESR).
B2B Toolkit Software Component should be created as below after upload is complete.
Step 4: Install Mapping Kit.
Import file XI7_11_B2B_MAPPING_KIT_1.0_00_01.tpz to Enterprise Service Repository (ESR).
Software Component B2B Mapping Kit should be created as below after installation.
Step 5: Install B2B Add-On EDI Runtime Content.
Depending on your organization’s EDI requirement, upload only the appropriate .b2b seed file from Runtime Content. For example, I will be using ANSI X.12, therefore I uploaded the seed file B2B_X12_TABLES-v1.0.b2b.
There are the other seed files available in the runtime content.
Go to B2B Integration Cockpit home http://<host>:<port>/b2bic and select EDI Content Manager.
Import appropriate .b2b files under respective EDI tab.
Verify that EDI content (Control Key association) is successfully imported to the B2B cockpit by accessing Editor > Message Editor
Post Installation Results:
If your Post Installation steps were successful, B2B adapters AS2, OFTP, X400 and EDI Separator should be available in your system. Login to Integration Directory (ID) to verify if the B2B adapters are correctly installed.
If these B2B adapters are still not available, request BASIS team to register the adapters using JSPM.
If you have any questions about the B2B add-on installation steps we have discussed here, please leave a comment.
Hi, I am Isuru Fernando, Senior SAP Integration Consultant with 10 years of SAP full-cycle implementation and support project experience.
From the early days, I had a passion for coding, software development, and everything tech-related. I started my carrier as an ABAP developer and soon found my love for system integration when I learned SAP XI 3.0 in 2008. Playing a variety of roles from an offshore technical consultant (ABAP, PI/PO, BW, BOBJ) at the beginning of my career to a technical lead managing a team of consultants in different countries, I have gained immense experience in SAP project implementation life cycle.
Having the opportunity to work on SAP implementation projects in USA, EU, and Asia, I learned valuable ins and outs of global business processors in Sales and Distribution (SD), Material Management, Retail, Customer Relationship Management (CRM), and Finance and Controlling (FICO).
Through this blog, I want to share my expertise in SAP technical areas such as SAP ABAP, PI/PO, AIF, and Basis. I also want to provide a platform for others with similar ambitions who would like to share their SAP technical expertise with the world!