Dear All gurus,

Need your expert advice on this..

There are some customized reports(ALV) that Business is requesting and the Reports will have SAP + Legacy system information running on SQL Server. In order to cater the requirement with real time data, business is emphasizing on use of PI (JDBC will be one of main adapters to be used). Number of Users authorized for this reports will be 50.

1. Is there a message size limitation in PI (ex: 5mb) sine each report  will contain 10,000 records from legacy systems (50 Users will run daily and there are 30 various reports like this) .
3. Will these reports have an impact on performances on PI/ECC/SQL server  (Daily reports like above and there are some monthly reports that will contain 20,000 records)
   
   

I know that thee is BW module for this requirement and unfortunately the Business is not interested in investing on this..

What are the performance optimization methods for these and any alternatives and improvements on this plzzz..

Thank you all in advance...

Hi everyone!

I have an issue with a File to Idoc interface. The customer would want the IDocs arriving to R3 to be in the same order they were sent from the legacy. From the File Adapter there isn't any problem using the EOIO QoS, and in the IDoc Receiver Adapter I checked the "Queue Processing".

There is something in the R3 side that the customer doesn't like much and it's about the stop of queue when an IDoc gets in error status: all the subsequent IDocs stay in status 75 ("IDoc received via qRFC").

I can change the status of the wrong IDoc and then release the stopped queue but: Is there a way to process serialized inbound IDocs avoiding the stop of the queue if an error occurs?

I'm using PI 7.0 SP30.

Thank you in advance!

Hi,

I was recently asked to add a new field to a service interface.  I made the changes to the Data Type and Mapping as appropriate and after activating those changes went to the Sender Agreement to save the WSDL in a file so I can handle it to our business partner (I created the file on the IB under Sender Agreement-->Display WSDL).  During the testing of interface using webservice navigator response gave an exception. We checked the WSDL file and the new field is there but it's missing the  <xsd:annotation> & <xsd:appinfo> tags (which all of the other fields have).

Here's an extract of how the WSDL looks, the new field is URI, ORG_NM2, ORG_NM3:

                                                                         :

<xsd:element name="IV_J_1IPANREF" type="xsd:string">

                  <xsd:annotation>

                     <xsd:appinfo source="http://sap.com/xi/TextID">

                     c6a198762dd811e48dab0c84dcced6b4

                     </xsd:appinfo>

                  </xsd:annotation>

               </xsd:element>

               <xsd:element name="URI" type="xsd:string" />

               <xsd:element name="ORG_NM2" type="xsd:string" />

               <xsd:element name="ORG_NM3" type="xsd:string" />

                                                                         :

As you can see the annotation and appinfo tags are missing for the new field URI ORG_NM2, ORG_NM3,.  I think this might be the reason why they don't see the new field when they upload the WSDL to their system.   Is there something else I need to do for the WSDL to be generated correctly?

Please suggest urgently.

Neeraj

Hi Experts,

In SXMB_MONI  XML messages for File2File scenario are failing

with the below message:

Database access error

com.sap.aii.utilxi.misc.api.ResourceException: ORA-01555: snapshot too

old: rollback segment number with name "" too small ORA-22924: snapshot

too old at com.sap.aii.utilxi.blob.api.AIIBlob.getByteArray

(AIIBlob.java:85) at

com.sap.aii.utilxi.blob.api.AIIBlobImpl.getByteArray

(BlobServices.java:156)

I have refered this link http://scn.sap.com/thread/3147106

Kindly suggest,

Gagan.

Hi Gurus,

Need Help.

When we are trying to import Software components from SLD we are getting following error. Could not read list of software component versions from SLD. In Description  i am getting following two points.

1. Could not read list of software component versions from SLD (COULD_NOT_READ_SWCV)

2. User credentials are invalid or user is denied access

We have tried following

1. LCRSAPRFC and SAPSLDAPI are working fine.

2  SLDAPICUST is ok

3. In nwa connections are available for LCRSAPRFC and SAPSLDAPI.

Request you to let us know how to resolve this issue.

Thanks in advance.

Hi Gurus,

I have to develop a customsed java module for reading Excel files from PI. I downloaded NWDS 7.31 from following location NWDS Download links - Java Development - SCN Wiki. I have installed it on my local laptop. For developing the module I need following Jar files.

1. com.sap.aii.af.ms.svc_api
2. com.sap.aii.proxy.svc_api.jar
3. com.sap.aii.sec.svc_api.jar
4. com.sap.aii.utilxi.server.jar
5. com.sap.aii.utilxi.core.jar
6. com.sap.xi.mapping.tool.lib_api.jar
7. sap.com~tc~bl~txmanagerimpl~plb~impl.jar
8. sap.com~tc~je~appcontect_api~API.jar
9. com.sap.aii.af.cpa.svc.api
10. com.sap.aii.af.lib.mod
11. com.sap.aii.af.ms.ifc_api
12. com.sap.aii.af.svc_api
13. com.sap.xpi.ib.mapping.lib

1. Where can i get these jar files. I checked these files in my downloaded NWDS 7.31  package, but cold not find them.

Thanks in advance

Hi Experts,

I am the only person working as PI resource in my project, so all the PI related decision I have to take.Basis person working with me have never dealt with PI.I am not very strong at dealing with SLD configurations, so facing some problems.

Earlier, we had only PI,Portal and ECC in our project, So, we decided to use the local SLD of PI and registered all of them(PI,Portal and ECC) in PI local SLD.

Later Solman also came into picture and we made SLD of solman as the central SLD and registered Portal and ECC in central SLD of solman(whereas PI still pointing local sld).Also, In solman SLD I gave data-supplier target as local SLD of PI, so that all registered applications could be seen in local SLD of PI as well.

Now, I made all the Business systems(of ECC), in local SLD of PI to used them, and the problem i am facing:

When I trigger proxy from ECC it says  GET_BUSINESS_SYSTEM_ERROR an error occurred when determining the Business system NO_BUSINESS_SYSTEM,

1) Is it because , although central SLD is pushing data to local sld , but still ECC is pointing to central SLD and there no business system is maintained?

2)What should I do to resolve this? make ECC point to local SLD or make PI point to the central SLD?

3) If I want to make PI point to main SLD , what changes do i need to do.Only change the entry in SLDAPICUST to solman ip or anything else?Could you please share link?

This is urgent. please advise.

Hi SAP PI experts,

   we are getting below error

SAP PI 7.1 PIDX scenario using RNIF 2.0 Error for PIP not matching

---

Channel correctly configured with the following: Receiver Agreement: |D02_010||ZZZZ|PIDX_Invoice Service: ZZZZZ<br>WARNING: Component and channel PIP do not match<br>

----

java.rmi.NoSuchObjectException: javax.ejb.NoSuchEJBException: Cannot find session IRNS2Uzwfbj3MQ99xqPE9_KKrT0glnYyY1UCEFIy_EJB for bean instance com.sap.engine.services.ejb3.runtime.impl.StatefulInstanceIdentity@8bf767ed. Possible reasons: 1) The session has timed out OR 2) An error has been thrown by the bean instance and it has been discarded OR 3) The bean has been explicitely removed. Note that any errors related to this bean instance could be foud in default server traces. ; nested exception is: com.sap.engine.session.SessionNotFoundException: AFMessageMonitoringBean/IRNS2Uzwfbj3MQ99xqPE9_KKrT0glnYyY1UCEFIy_EJB(1312503355) com.sap.engine.session.SessionNotFoundException:  AFMessageMonitoringBean/IRNS2Uzwfbj3MQ99xqPE9_KKrT0glnYyY1UCEFIy_EJB(1312503355)  at com.sap.engine.session.AbstractSessionHolder.getSession(AbstractSessionHolder.java:99)  at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ActivateStatefulContext.invoke(Interceptors_ActivateStatefulContext.java:29)  at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)  at

Hi,

When I'm defining connection RFC->PI I have to create FM + sm59 connection type T (destination to PI)

Program ID from this sm59 (T) I'm providing in communication channel.

My question is, every new interface RFC->PI needs new SM59 (type T) or I can provide the same program ID in every RFC->PI interface (communication channel)?

thank You,

Regards,

Tomasz

Hi Experts,

After active objects list, in the central adapter engine: ache update not yet started.

Looking for this error, is possible that is the RFC INTEGRATION_DIRECTORY_HMI because responde 403 forbidden,

Did you have any tips?

Thank you!

Bruno

Hi Gurus,

From the last one month we are facing Entries got stuck in smq2 of Ecc system Error Status saying that Time Limit Exceed and some times Object was locked by the user xxxx .Here we observed is entries are not stucking for entire week at particular days only they are stuking like if it is week start they dont stuck after 3rd day of the week it starts stuking upto week end i.e friday and saturday and sunday they will clear if we do lot of actions.

so we are not in a stituation why the queue is behaving very stragne.

data also very less like it is on kbs only and the interface is related to FSCM Credit commitements it is successfully reached to target system as we dont see this type of behaviour on pi side.

Regards

Madhu

Hi ,

I am working on Proxy --> PI --> File scenario. At receiver end, we are using SFTP adapter.

I am getting the below error while using variable substitution but it works fine with FTP adapter.

"Delivery of the message to the application using connection SFTP_http://sap.com/xi/XI/SFTP failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: javax.resource.ResourceException: The variable substitution can not be parse the message xml: Content is not allowed in prolog."

please suggest me .

Thanks

Dhileep

Hi,

When i use the abc*.txt,  it does not pick up the file in PI 7.3 SFTP Adapter.

When we are using the wild character should we need to take care anything.

Thanks,

Jignesh shah

hi

i have po 7.4 installation -single stack.

its giving performance issues. any point of time in a day it goes unavailable.message load is not much-approx 10000 messages per day flowing.

when po system goes unavailable,we contact basis,they restart and it works fine.

how to prevent from this issue.

what need to be checked for it.

Dear experts,

This is my second blog post that i decided to share because i did´nt find something like this "Nice way to play with your PI system":

Objective: if you need creating a web page with your logo, your company or personal information, whatever that you want to share in your SAP PI Netweaver side, SAP let you add your "Web page", with the next general steps:

1.- Open your PI, Netweaver side (trx code from stack abap: SXMB_IFR):

2.- As you can see below in your page, we have the next text, so please open your PI server and follow the path that your system indicate:

To add your content here create a file named

Docu.htm in the following directory:

G:\usr\sap\PID\SYS\global\xi\directory_server\extdocu

3.- While you go to your PI file path. You can create your first "Hello World" --> Docu.htm using html code (remember the correct name file and the type of your file):

<html>

  <head>

    <title>Hola Mundo en HTML</title>

  </head>

  <body>

    ¡Hello World!

  </body>

</html>

4.- Save all in one directory that you prefer or create a new folder just to save your new web pages:

5.- Then after you create your Docu.htm file in your computer, you can copy and paste the file in your PI server:

6.- Then refresh your SAP PI Netweaver (normally with F5 or other that you prefer), and you will see your first web page into your netweaver:

I hope you enjoyed it!!!...

Thanks..

Azael

Hi,

When we try to send file over seeburger SFTP (receiver) we are getting the error as below.

Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: >> Description: SFTP transaction error occured.>> Details: putFile: Could not connect to remote host; Reason: Unable to open Sftp client. SshReasonCode: CHANNEL_FAILURE>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMMUNICATION_ERROR>>Retryable: true>>Fatal: true, >> Description: SFTP transaction error occured.>> Details: putFile: Could not connect to remote host; Reason: Unable to open Sftp client. SshReasonCode: CHANNEL_FAILURE>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMMUNICATION_ERROR>>Retryable: true>>Fatal: true

But we are able to connect through filezilla . we are able to create and delete file using the same username and password which is being used in SFTP adapter.

we have imported the both dsa and rsa keys in SFTP partner folder in NWA. Even though we are getting same error.

Thanks,

Vinayak

Hi Gurus

I'm trying to create a mapping with java, but i'm having a little trouble to append some lines to the table.

I've attached 2 files, the "wrong" which is the way is working today, and the "correct", the way i need it to be.

Current implemented code is:

public void execute(InputStream in, OutputStream out)  throws StreamTransformationException {    try     {    // Inicio do java mapping  // getTrace().addInfo("JAVA Mapping Iniciado"); //Log para o PI/XI  // Declarações referentes ao XML de entrada  DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();  DocumentBuilder db = dbf.newDocumentBuilder();  Document xml_in = db.parse(in);   // Declarações referentes ao XML de saída  Document xml_out = db.newDocument();  TransformerFactory transformerFactory = TransformerFactory.newInstance();   Transformer transformer = transformerFactory.newTransformer();  // Remove o standalone  xml_in.setXmlStandalone(true);  // Declara a estrutura que a RFC irá receber  Element root = xml_out.createElement("ns1:ZFSD_VMOI_UPLOAD_CF_PG");  root.setAttribute("xmlns:ns1","urn:sap-com:document:sap:rfc:functions");  xml_out.appendChild(root);  Element i_cenario = xml_out.createElement("I_CENARIO");  root.appendChild(i_cenario);  Element t_input = xml_out.createElement("T_INPUT");  // root.appendChild(t_input);  Element item = xml_out.createElement("ITEM");  // t_input.appendChild(item);  Element STRING = xml_out.createElement("STRING");  // item.appendChild(STRING);  Element t_return = xml_out.createElement("T_RETURN");  root.appendChild(t_return);  Element item_r = xml_out.createElement("ITEM");  t_return.appendChild(item_r);  Element message = xml_out.createElement("MESSAGE");  item_r.appendChild(message);  // Verifica se existe algum filho no nó  NodeList nodos = xml_in.getChildNodes();    if (nodos.item(0) != null)   {       // getTrace().addInfo("O nó(XML) possui filhos"); //Log para o PI/XI  // Declaração de variáveis  String ident = ""; // <Ident>  String buyer = ""; // <BuyerLineItemNum>  String result = ""; // <Ident>;<BuyerLineItemNum>;<Date>;<QuantityValue>  // Inicia a extração das informações do XML  try{  // Recupera o nó ShipToParty  NodeList nodeShip = xml_in.getElementsByTagName("ns0:ShipToParty");  Node node = nodeShip.item(0);  Element elemXML = (Element) node;  try{  NodeList nodeIdent = elemXML.getElementsByTagName("ns0:Ident");  Element nameElement = (Element) nodeIdent.item(0);  nodeIdent = nameElement.getChildNodes();  // Recupera o valor da chave <Ident>  ident = PI_Mapping_IF.VerifyNull(((Node) nodeIdent.item(0)).getNodeValue());  }catch(Exception e){  result += "0.0;";  }  // Recupera o nó ListOfMaterialGroupedPlanningDetail  NodeList nodeBuyer  = xml_in.getElementsByTagName("ns0:MaterialGroupedPlanningDetail");  for (int i = 0; i < nodeBuyer.getLength(); i++) {  node = nodeBuyer.item(i);  elemXML = (Element) node;  try{  // Preenche a chave BuyerLineItemNum  NodeList nodeBuyerLine = elemXML.getElementsByTagName("ns0:BuyerLineItemNum");  Element elemBuyerLine = (Element) nodeBuyerLine.item(0);  nodeBuyerLine = elemBuyerLine.getChildNodes();  buyer = PI_Mapping_IF.VerifyNull(((Node) nodeBuyerLine.item(0)).getNodeValue());  }catch(Exception e){  buyer += "0;";  }  result = ident+";"+buyer+";";  Node nodeDt_Qnt = nodeBuyer.item(i);  Element elemDt_Qnt = (Element)nodeDt_Qnt;  NodeList nodeValores = elemDt_Qnt.getElementsByTagName("ns0:ScheduleDetail");  for (int j = 0; j < nodeValores.getLength(); j++) {  node = nodeValores.item(j);  elemXML = (Element) node;  try{  // Preenche a chave Date  NodeList modelExtra = elemXML.getElementsByTagName("ns0:Date");  Element extraElement = (Element) modelExtra.item(0);  modelExtra = extraElement.getChildNodes();  result += PI_Mapping_IF.VerifyNull(((Node) modelExtra.item(0)).getNodeValue())+";";  }catch(Exception e){  result += "//;";  }  try {  // Preenche a chave QuantityValue  NodeList modelURL = elemXML.getElementsByTagName("ns0:QuantityValue");  Element urlElement = (Element) modelURL.item(0);  modelURL = urlElement.getChildNodes();  result += PI_Mapping_IF.VerifyNull(((Node) modelURL.item(0)).getNodeValue())+";";  } catch (Exception e) {  result += "0.0;";  }  // Marca o final do registro  result += "||";  // Preenche os nós itens  Text srcxml = xml_out.createTextNode(result);  STRING.appendChild(srcxml);  item.appendChild(STRING);  t_input.appendChild(item);  root.appendChild(t_input);  result = "";  }  result = "";  buyer = "";  }  }catch(Exception e){  }  // Remove o standalone  xml_out.setXmlStandalone(true);  // Preenche o Cenario  Text cenario = xml_out.createTextNode("P&G");  i_cenario.appendChild(cenario);  // Preenche mensagem de retorno  Text msgxml = xml_out.createTextNode("XML lido com sucesso!");  message.appendChild(msgxml);  // Escreve a saida do XML               transformer.transform(new DOMSource(xml_out), new StreamResult(out));  }  } catch (ParserConfigurationException e) {   throw new StreamTransformationException("Can not create DocumentBuilder.", e);  } catch (SAXException e) {  e.printStackTrace();  } catch (IOException e) {  e.printStackTrace();  } catch (TransformerConfigurationException e) {  e.printStackTrace();  } catch (TransformerException e) {  e.printStackTrace();  }  }

Thank you all

Hi All ,

As per the SAP Document on SFSF Communication channel, one of the feature supported by SP00 release of the connectivity add-on 1.0 is :-

1. Delta sync to fetch only changed records

SFSF Adapter: Delta Sync

The delta sync features enables you to fetch only the records that were modified after the last successful data fetch from the SuccessFactors system.

This increases the efficiency of query operation.

So below are my question accross Successfull run date feature :

Is it SAP PI Connector internally maintains this last successful run date ?

what would be Time-Zone of Successful run date : Is it where SF DC is located or where PI Box is Located ?

what is it mean from successful run date ? - is it process successful run date or is it just communication channel successful run date ?
For Delta extraction - This Successful Run Date - Is it maintained internally for  Interface wise or Communication Channel wise ?

eg. If i have 5 Delta Interface - will SAP PI maintain 5 Successfull run dates w.r.t to each connector or w.r.t each Process ?

for more information please open below URL.

http://help.sap.com/saphelp_nw-connectivity-addon100/helpdata/en/1e/22aaf0780d4b78b6f889157f6a8035/frameset.htm

Regards

Prabhat Sharma

Hi Experts,

I need to install AEX (advanced adaptive engine extended "AS Java") using NW 7.41.

I am confused to where should I go in SWPM:

Should I go for "optional stand alone units" then "advanced adaptive engine extended" (snapshot 1)

or

go for "Application Server Java" then choose the following "usage types" as stated in Master guide (snapshot 2)

"advanced adaptive engine extended requires AS Java, NW Product Description, AS Java Extensions, PI Adapter Engine, and Enterprise Services Repository as a prerequisite in the same system"

and If I supposed to go for the second option, I can't find PI Adapter Engine as a usage type (snapshot 3)

Hi Experts,

We have the following error in the IDoc_AAE sender channel on PI7.3.

Processing error =  senderChannel 'c719d32d33423e4b9f1bcf3d874c45a5': Catching exception calling messaging system

Also we have the Idocs being sent from the ECC system to PI stuck in sm58 of the ECC system with the error Commit fault: ASJ.ejb.005043 (Failed in component:sap.com/com.sap.aii.ad

The same RFC settings and channel configuration are working fine for another interface.

Thanks,

Diptee