Hi All,

Scenario: IDoc to XML

I am getting Error in Receiver SFTP Channel "Content is not allowed in prolog" while using Variable Substitution, But same configuration and IDoc (Triggered through we19)works fine with File channel.

I have checked and no space or special character in the field but numeric value.

Screenshot: SFTP Receiver Channel

Regards,

Mani

Hello All.

I am having issue while posting IDOC to ECC i have configured the receiver channel as below.

In the channel log I can see that its successfully processed idoc

And rfc destination mentioned above is also working fine.

I am able to ping it from SAP PO.

But still idocs are not reaching sap ecc.

Any suggestions where to check?

Thanks

Naveen

Hi experts,

in PI 7.0 in a SOAP synchronous receiver channel, protocol HTTPS with certificate , I get this error:

<?xml version="1.0"?>

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">

<env:Body>

<env:Fault>

<faultcode>env:Client</faultcode>

<faultstring>Internal Error</faultstring>

</env:Fault>

</env:Body>

</env:Envelope>

If I cut and paste the PI message in SOAP UI it works perfectly and web service give the correct response.

I've checked DO NOT USE Soap Envelop because Envelop is created by me with XSLT mapping.

In CC I'm using SOAP Action that I retrieved from "Action" in SOAP UI.

In module I have Transform text/xml;charset=utf-8

and

soap XMBWS.NoSOAPIgnoreStatusCode true

What could be the problem?

Thanks

Fabio

Hi Guru,

My scenario is XI to SOAP (Protocol HTTP Axis ) Sync. and in Receiver SOAP Adapter i'm getting the error message.

In the TX. SXI_MONITOR service interface Inbound shows the following error:

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

  <SAP:Category>XIAdapterFramework</SAP:Category>

  <SAP:Code area="MESSAGE">GENERAL</SAP:Code>

  <SAP:P1 />

  <SAP:P2 />

  <SAP:P3 />

  <SAP:P4 />

  <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>

  <SAP:ApplicationFaultMessage namespace="" />

  <SAP:Stack />

  <SAP:Retry>M</SAP:Retry>

  </SAP:Error>

Using PI 7.0 SP18.

Please any suggestions for this?

Thanks.

Dear Experts,

I have a requirement to pick a pdf file using SFTP channel and then to send it to the SAP system over proxy with pdf file name.

I have created a data type for proxy  with two fields, one with the File name another with the file content. It is similar as  described below.

I have used a UDF to get the file name of the pdf  and mapped this UDF to FileName field under datatype and used the dynamic file setting in the channel.

Sender channel has successfully picked up the file and sent it to adapter engine but it failed in the request message mapping stage under Pipeline  with following error : 

Runtime exception occured during application mapping

com/SAP/XI/tf/_MM_Test~

com.sap.aii.utilxi.misc.api.BaseRuntimeException : Content is not allowed in the prolog.

Although when I have sent the PDF with only one field as Filecontent, it is getting processed successfully.

Appreciate if any one can suggest any alternative/resolution. We have restriction to not use Integrated configuration in this case.

Regards,

Sudhir Kumar

Hi ALL,

I am facing issue while connecting my ERP system to PO 7.4.

I have done the exact steps as http://scn.sap.com/people/michal.krawczyk2/blog/2012/01/19/michals-pi-tips-how-do-you-activate-abap-proxies-with-aex--simplified-version, but the RFC PI_AAE is failing with 500 error.

When i checked launching the URL:
http://<aaehost>:<port>/XISOAPAdapter/MessageServlet?ximessage=true

It is failing with 500 Server error:

In default Trace, Error log says below:

Error#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#

com.sap.ASJ.web.000137#BC-XI-CON-SOP#sap.com/com.sap.aii.adapter.soap.app#C000C0A8A39802AC0000000000000DCC#1737950000000004#sap.com/com.sap.aii.adapter.soap.app#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0##12693CADAC5411E4C5F20000001A84DE#12693cadac5411e4c5f20000001a84de#12693cadac5411e4c5f20000001a84de#0#Thread[HTTP Worker [@228500667],5,Dedicated_Application_Thread]#Plain##

Cannot process an HTTP request to servlet [MessageServlet] in [XISOAPAdapter] web application.

[EXCEPTION]

null; nested exception caused by:

com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection SOAP_http://sap.com/xi/XI/Systemcannot be created as it was not registered before!

  at com.sap.engine.messaging.impl.api.ConnectionFactoryImpl.checkConnectionRegistration(ConnectionFactoryImpl.java:259)

  at com.sap.engine.messaging.impl.api.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:113)

  at com.sap.engine.messaging.impl.api.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:99)

  at com.sap.aii.adapter.soap.web.SOAPHandler.<init>(SOAPHandler.java:153)

  at com.sap.aii.adapter.soap.web.MessageServlet.init(MessageServlet.java:185)

  at com.sap.engine.services.servlets_jsp.server.application.WebComponents.getServlet(WebComponents.java:864)

  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)

  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

  at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

  at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

  at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)

  at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)

  at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

  at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

Can anyone please assist me in resolving the same.

Regards,

Prashanth

HI friendz

I am new to pi now days every one is calling pi po what is this both are same or different  I am not able to find the difference plz xpln

With Regards

Arun

Difference between pi and po

Hi

can you tell me how to delete idocs from R/3 system

Regards

Nawa

Hi all,

I am doing EDI message to IDOC mapping in which My requirement is to map

Current date -

>DATUM

in this mapping current date should be in the format ccyymmdd

If i give this format in function current date then it gives rumtime error that C is illegal character

It only accepts y, m and d characters

any body can tell me how can i give this CCYYMMDD format in current date function?

Thanks

Sandeep sharma

Hi Friends,

I know that SMQ2 ia a inbound queue and SMQ1 is a outboud queue but wanted to know where this queues are present exactly and Purpose

.

I guess SMQ2 is the first step in IE after AE forwards the PI SOAP Message and before the Pipeline steps.

Once Pipeline completes the Call Adapter Step then message goes to Adapter through SMQ1. Please clarify

Regards & Thanks ,

Manikandan

Hi,

I am trying to setup the proxy communication from SAP to PI (7.31 single-stack).

I went through this very good blog by Michal on how to set this up.

http://scn.sap.com/people/michal.krawczyk2/blog/2012/01/19/michals-pi-tips-how-do-you-activate-abap-proxies-with-aex--simplified-version

I created the outbound proxy from my Service Interface and activated succesfully.

Now when i test i get the following error

GET_BUSINESS_SYSTEM_ERROR An error occurred when determining the business system (COMMUNICATION_ERROR)

When i do SLDCHECK i get the following error (According to blog it shouldnt be necesary to create SAPSLDAPI)

What am i missing here?

Dear Experts,

I have a requirement to pick a pdf file using SFTP channel and then to send it to the SAP system over proxy with pdf file name.

I have created a data type for proxy  with two fields, one with the File name another with the file content. It is similar as  described below.

I have used a UDF to get the file name of the pdf  and mapped this UDF to FileName field under datatype and used the dynamic file setting in the channel.

Sender channel has successfully picked up the file and sent it to adapter engine but it failed in the request message mapping stage under Pipeline  with following error : 

Runtime exception occured during application mapping

com/SAP/XI/tf/_MM_Test~

com.sap.aii.utilxi.misc.api.BaseRuntimeException : Content is not allowed in the prolog.

Although when I have sent the PDF with only one field as Filecontent, it is getting processed successfully.

Appreciate if any one can suggest any alternative/resolution. We have restriction to not use Integrated configuration in this case.

Regards,

Sudhir Kumar

Hello

we have PO 7.40, the ECC has SAP BASIS 7.31 sp06.

I've configured CBMA, error in PI, like mapping error, triggers alert and email is sent.

However no email is sent in case of ABAP proxy error at ECC side. I've configured ALERTING_IS_ACTIVE = 1 and ALERTING_TARGET = 1 in sxmb_adm in ECC.

Since ECC is on 7.31 sp6, the note 1584248 does not apply. In fact, just in case, I've also configured the steps as stated in blog http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/02/26/sap-pi-731-abap-proxy-monitoring-and-alerting-using-cbma.

Anyway, error occurs in abap proxy does not trigger email.

Anyone can shed some light on this issue?

Thanks

Jayson

HI Experts,

My scenario is IDoc to CSV and vice versa CSV to IDoc. Let us say IDoc to CSV as Outbound and CSV to IDoc is Inbound here. Please find the below requirements interface wise.

Outbound scenario: IDoc --> CSV

All the end users who has access to SAP system would be entering the ORDERS01 IDocs manually from different mines, a background job will be executed to fetch all the IDocs in a day and would be triggered to SAP PI 7.31 single stack. Based on the value of WERKS field in IDoc received all the IDocs relating to one mine [or same WERKS value] should be transformed as CSV file with each IDoc data as a single line item and should be posted to the corresponding folders that are created based on the name of the mine on receiver file system. I have done IDoc packaging on the SAP system side and settings on the channel to receive multiple IDocs at a time, FCC receiver and corresponding changes accordingly and the scenario is working like multiple IDocs to single folder only for example if 50 ORDERS01 IDocs are triggered from SAP then a CSV file with 50 line items is getting created and posting to a single folder.Now the requirement is in addition or modification to the above, suppose 70 ORDERS01 IDocs with different values are triggered from with different value to WERKS field and in PI those multiple IDocs with same WERKS value should be categorized as a group and should be transformed to one CSV file with each IDoc as single line item. Can you please suggest some standard ways like variable substitution to achieve this.

Inound scenario: CSV --> IDoc

The requirement is like the end users of file system will place the CSV files on specific Inbound different folders and PI system will poll them and all of them should be triggered as DELVRY07 to SAP R3 from SAP PO and currently the settings in such the interface is working like from single folder a file should be picked and based on the number of line items that many number of IDocs should be triggered to SAP R3.

Kindly suggest standard ways to achieve them.

Thanks,

Nithin.

Hello Everyone,

I have to develop a File to Proxy synchronous scenario in PI 7.3.

When I'm adding the details(Pls refer to the below screen shot) in the Module tab of sender communication channel in ID part, I'm getting the follwoing error :

An error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error: invalid receiver channel 'c803d79b7f553343a836f6794a79a338'

Pls help to solve it.

Hi Experts,

I am working on FILE-TO-PROXY scenario on PO 7.4 . While running the scenario , The sender file channel is throwing the below error .

Error during parsing the received XMB message.

Error SOAP: Call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: System Error Received. HTTP Status Code = 200: However System Error received in payload ErrorCode = NOT_FOUND ErrorCategory = XIServer Parameter1 = RUNTIME Parameter2 = ENGINE_TYPE Parameter3 =  Parameter4 =  Additional text =  ErrorStack = Configuration parameter RUNTIME ENGINE_TYPE not found

[http://sap.com/xi/XI/Message/30^Error "NOT_FOUND"]

Request you to suggest the possible solutions.

Thanks & Regards

Amitosh

Hi Experts,

Recently we have upgraded our SAP PI system (from 7.1 to 7.4, dual stack) and Seeburger (from 1.8 to 2.2.2) in Dev environment.

We have successfully imported seeburger related software component version zip and tpz file available with the installation CD.

But now when we check any mapping or edit it, it is giving below error with the UDF's. Error and UDF snapshot attached.

"cannot access com.seeburger.exception.SeeException
class file for com.seeburger.exception.SeeException not found
VariableBean be=VariableFactory.getVariableInstance("");"

We already have imported SeeFunctionsPI.jar and SeeCommonCollectionPI.jar in the imported archive of our namespace also but still getting this error.

Could not understand why it is throwing "cannot access com.seeburger.exception.SeeException". In the imported archive I can see this class in SeeCommonCollectionPI.jar.

In the Quality system and production system same is working fine for the older system. They both are not being upgraded to latest version as of now and activity is in progress.

In ESR, SWCV for older seeburger version is also visible ("SEEBURGER_AUTOMOTIVE, 1.8.1 of seeburger"), which also have this jar in imported archives.

Is it creating any conflict? (I don't think so)

Also once the seeburger version is upgraded, i don't think older swcv should exist in ESR (may be a part of undeployement when basis upgrade it).

Need suggestions.

Regards

Jitender

Hi All,

My scenario is SOAP to File  Asynchronous ICO Scenario.

It is working at ESR Mapping level, but failed in ID Test configuration with error as " Receiver could not be determined".

I have tried below options to resolve this error

1) NWA Setttings  --> Value is 0 for xiadapter.version.minor

2) RFC Destinations

a) SAPSLDAPI

2) LCRSAPRFC

3)SXI_CACHE is up to date.

Please guide me to resolve this error

Thanks in advance,.

Regards,

Jeevitha N

Hello,

I receive a 500 Connection timed out error.

I know that there are some threads to this error but I can´t find a solution for us.

This is the error description:

Error:            -5

Version:        7000

Component:  ICM

Date/Time:    Tue Mar 04 07:02:38 2008

Module:        icxxthr.c

Line:             2698

Server:         crmprod_CRP_01

Error Tag:     {-}

Detail:          Connection to partner timed out after 60s

Now I have found in this forum some information about the parameters icm/keep_alive_timeout, icm/conn_timeout and icm/server_port_*

Our settings for this parameters are:

icm/server_port_0 = PROT=HTTP,PORT=8001

icm/server_port_1 = PROT=SMTP,PORT=25

icm/keep_alive_timeout (sec.) = 600

icm/conn_timeout (msec.) = 5000

Can someone please explain me which parameters occurs this error and which parameters I can change that the connection time is longer than 60 seconds?

Where can I change the parameters?

Regards

Philipp

Hi

can you tell me how to delete idocs from R/3 system

Regards

Nawa