Blog Archive

Thursday, January 26, 2017

sample RFID scenario


Monday, January 23, 2017

SAP PI certificate understanding


Let assume, we have two system,

like to use certificate( which are supposed to be deploy on SAP PI server)

AS2( Need to generate public,private certificates key)

also called keystore, keypair (in SAP PI) also we give alias name

/* some times we use private certificate +key */

SAP PI Need to generate public,private certificates key

lso called keystore, keypair (in SAP PI) also we give alias name

/* some times we use private certificate +key */

Loading/adding/deploying on SAP PI

We get only public key of AS2, We are not supposed to use private certificate/key

we create as2 view only with public certificate of as2 in SAP PI


But for SAP PI , We create view with public,private certificate + key (we know)

/* PGP process ( certificated are located in file system) this is different approach, we are not talking about this here  */


Basics about encryption and decryption
digital signature

summary of keystore name ,private,public certificate names as shown below(alias not mentioned here, which is mentioned in SAP PI view creation step)

AS2 view in SAP PI, only with as2 public certificte

 SAP PI view in SAP PI nwa, with all pub,private certificate + key

using as2 communication channel ( using both decryption + MDN singnature)

Message from AS2 is encrypted by AS2, we are supposed to decrypt that, here
using public key of as2

Friday, January 20, 2017

TDLINE field Not populated with entire value in SAP which is from 3rd party system


I was asked in one of the project saying, need to validate SAP PI mapping, to find out if any restriction in sap pi mapping.

they are supposed to see more than 70 (text length) , which is passed from 3rd system.

They have provided sample payload and soap url information.

By using that , I have identified communicaiton channel name , respective service interface, again right mapping name in ESR.

I have found , it was direct mapping.

With out opening the sap pi system,
1) first we can verify the field properly in sap.
we60 ( idoc segment name, basis type name)
2) some times if we do not access we can also check from online

In my case it was

google search site: Facet Value

Experiance with TDLINE:

Because sap of not supporting large value in SAP ECC, side, some times, we (sap pi consultants), supposed to split the less than 70 , ( either based on qualifier : map , else map to custom field of idoc)

Thursday, January 19, 2017

SAP PI ESR id jnlp files lanch problem


Update your java and try again.

Wait for few min, until it has esr content is loaded in javaws as shown in below

Wednesday, January 18, 2017

SAP PO upgrade valiation: communication channel opening error adapter engine not found


In recent PI service patch upgrade project,

SAP pi validation, found error while opening communication channel in id.

Adapter engine not found.

error and solution as follows

Open, sld ,integration directory, check associated application system is assigned not .


SFTP, PGP, REST functionalityes after upgrade of SAP PI 731 SP07 to SP04

1. validating SFTP swcv in esr
2.validating SFTP adapter in ID adapter list.

2. validating REST adapter in SAP BASIS 7.4  SWCV  in systems namespace.
a) checking that in adapter list.

About PGP.
( checking PGP version in sysinfo and checking java services in NWS)

i) double click on swcv of sftp and check version and sp details as follows

Check the information in sysinfo, compnent view. (using Keyword PGP SFTP)

Checking the adapter( if it is standard ) in sap basis 7.4 system namespace as shown in below.

check adapters(pop up), which creating communication channel and choosing adapter list.

checking the version and service pack info in sysinfo for all components of sap pi . 
( exported as sheet and comparing) also for pgp,sftp details

Monday, January 16, 2017

analysis of multiple xml files content as single file


some times, certain messages are failed in SAP PI message monitoring, we need to download and open those and analyze the data.

some times , it is difficult to navigate multiple xml file, where xml file sizes are huge.

In this can case, I used this approach.

1. download all xml files.

2. merge all xml files using dos command.
copy file1+file2+.....  TargetFile

3. Remove the addition xml initial tag.

4. add some dummp root tag, start and end

As per xml standards, any xml file should start single root node and end with single root node.

My example:

1. each failed messages has certain failed idoc and its child content.
2. we need to identify certain mandatory filed in specific idoc is missed.
(this causes entire messages is to be failed)

3. same thing with other failed messages in SAP PI.

after clubbing, remove < ? xml ...> additional root tages.

and add root tag begining and at the end.

book mark, idoc number --->
bookmark missed segments -->
( this trick helps ), idoc number, which has missed data.


Wednesday, January 11, 2017

C4C certificates deployment


Monday, January 9, 2017

SAP PI monitoring based on business terminology for support projects


Message monitoring.
Based on business terminology 

( most of service interface in SAP PI are named with technical names, also interface number , receiver usage)

First download excel file from monitoring to understand frequency of interface used for last couple of months.

Save this in your local computer, as excel format.
(Understand keyword used here, interface name, number and extract, frequency of interface used, message count also

This helps, the message flow on sap pi correctly)

Sometimes, you manager may ask you to check if specific technical name, Ex: recon. Interface has any error or not.

Now use this excel sheet, check where this keyword is used.

Now use the same service interface, in message monitoring filter search.

(your previous saved excel sheet from message monitoring for last couple of months)
( search to find the interface information based on keyword)

use the service interface information to search in message monitoring filter criteria

check all pimon, message monitoring.

( find inbound and outbound idoc list)

copy, basis message type and enhacment type(start with z)

in SAP ECC( we60, get the documentation _http view, copy the content in word document)

This document will help you to understand business terminology.

While replying mails to customer, we can use business terminology, ( strucuture name: business terminology) filed name usage, 

if you do not have access,
( copy idoc xsd and save file as xml format, view file in excel sheet, )
same thing, for 3rd party system strucutures, view in excel sheet.

In mapping you will see the field error, 
(add additional information from these files, to understand better in email communication )

if possible, copy the message mapping source code, to understand target filed and relation with source fileds.

By seeing payload of source message and mapping sheet, we can check reason for failure of not getting value