Quantcast
Channel: SCN : All Content - SAP Process Orchestration
Viewing all 1235 articles
Browse latest View live

SOAP fault error for all SOAP receiver channels

$
0
0

Hello Experts ,

 

We are working on sap PO 7.4 version, we have so many soap receiver scenarios but for most of all the soap receiver adapter we are getting the SOAP fault error.

 

Please suggest what might went wrong ?? is there any issues with the scenario configuration ??

 

Below is the error,

 

SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Internal Error



Regards,

Amit


Authorizations needed for a Service User for consuming a PI/PO WS

$
0
0

Hi Gurus,

 

We are on a single stack PO 7.4 system.

 

The requirement is to consume a PI exposed WebService that is linked to an ECC proxy.


We have developed and downloaded the WSDL all-right but want to know what roles/authorizations are required for the Service User?


We are aware that the below are applicable for a dual stack:


SAP_XI_APPL_SERV_USER

SAP_BC_JSF_COMMUNICATION_RO

SAP_BC_WEBSERVICE_PI_CFG_SRV

 

Kindly let me know the corresponding roles in a single stack system and also the necessary steps for adding these roles.


Thanks in advance.


Regards,

Rakesh.

SFTP to NFS, NFS to RFC

$
0
0

My requirement is to get a file from SFTP server & place it in NFS/Al11 (ECC).

 

Once I place the file call an RFC enabled Function module. No mapping is involved.

 

My question is how can I call RFC from PI without mapping.

 

I have verified RFC parameters & unable to understand if I can call RFC FM using available parameters from ID.

 

Ideally RFC FM is downloaded in ESR & mapped, but I'm unable to find the solution for this requirement. Kindly help.

we are getting MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out

$
0
0

MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out

 

we are using the soap receiver and this is asynchronus .today we got this error message. it is getting only for a specific message remaining messages are delivered successfully. after that i resend this message but it is gibing same error?

Re: Disconnecting OLD PI system & Connecting ECC to new PI system (via Proxy)

$
0
0

Hi Gurus

 

We are correctly on PI 7.1 which is connected to ECC for PROXY communication.

 

However, we have a new PI 7.3 and would like to disconnect PI 7.1 and connect it to the new PI 7.3.

 

Can you please let me know - Best practice to disconnect old PI Box -

  • Is it just deleting the RFC and removing config from SXMB_ADM ?!
  • Would the below steps cover all the necessary config to connect the new PI 7.3 environment to ECC
    • SLD Entries in PI
    • SM59 HTTP Connections
    • SXMB_ADM Config
    • SLDCHECK

 

Please, ADD anything I might have missed!!

 

Your help is greatly appreciated!!

 

Thank you,

Ritu

Business System Names during integration

$
0
0

Hi

I have a number of ABAP Proxy integrations between ECC and PI. My question relates to the name of the sender service when it appears in PI.

 

I have a system that is defined in the SLD as XXX009 (where XXX is the SID and 009 is the client number). Now when making proxy calls to my legacy system (PI 7.11) it appears as XXX009 but when calling my current system (PI 7.31) the sender system appears as XXXCLNT009.

 

Can I ask why the business system names are different? Why is one XX009 and the other XXXCLNT009 when the source ECC system is the same? It doesn't make sense?

 

 

Regards

Error when using Channel Migration Tool in SAP Directory Content Migration Tool

$
0
0

Hi Experts,

 

I'm trying to migrate a file receiver channel using the Channel Migration Tool in SAP Directory Content Migration Tool.

I enter the channel name and then select it or click in "Edit"; I get the bellow error:

 

Thanks in advance.

Su May

 

500   Internal Server Error

  SAP NetWeaver Application Server/Java AS

The initial exception that caused the request to fail, was:

 

java.lang.NullPointerException: while trying to invoke the method
com.sap.pi.tools.dirmig.channel.metadata.SoftwareComponentVersion.getVersion()
of a null object returned from
com.sap.pi.tools.dirmig.channel.metadata.AdapterMetadataFactory.getLatestSWCV(java.lang.String)

  1. at
    com.sap.tc.pi.tools.dirmig.wd.wd.comp.channelmigration.ChannelSelectionView.onActionChannelTableSelect(ChannelSelectionView.java:548)

    at
    com.sap.tc.pi.tools.dirmig.wd.wd.comp.channelmigration.wdp.InternalChannelSelectionView.wdInvokeEventHandler(InternalChannelSelectionView.java:486)

    at
    com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)

    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)

    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)

    ... 56 more

 

  See full
exception chain
for details.

Failed to process request. Please contact your system
administrator.

 

While processing the current request, an exception occured which could not be handled
by the application or the framework.

 

If the information contained on this page doesn't help you to find and correct the
cause of the problem, please contact your system administrator. To facilitate
analysis of the problem, keep a copy of this error page. Hint: Most browsers
allow to select all content, copy it and then paste it into an empty document
(e.g. email or simple text file).

 

For further information about the Web Dynpro error page, error
analysis and a description of well-known error situations, see SAP note
1113811.


 

Correction Hints


 

 

Exception
could be caused by the development component: sap.com/tc~pi~tools~dirmig~wd

 

 

Note: The above hints are only a guess. They
are automatically derived from the exception that occurred and therefore can't
be guaranteed to address the original problem in all cases.

 

 

System Environment

 

Client

 

Web Dynpro Client Type

AJAX Client

User agent

Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1;
  Trident/5.0)

Client Type

msie 

Client Type Profile

ie6
ActiveXenabled

Java Applets

enabled

Accessibility mode

disabled

Inline CSS

false

Validate by rendering

true

 

 

Server

 

Web Dynpro Runtime


 

vendor: 'sap.com', name: 'tc/wd/webdynpro', scV: 'sap.com',
  scN: 'WD-RUNTIME', location: 'SAP AG', counter: '7.4008.20140808120905.0000',
  R: '7.40', SP: '8', PL: '0', change number: '613920', codeline:
  NW731CORE_13_REL

J2EE Engine

  1. 7.40.3301.367419.20140806095041

System ID (SID)

Server Node ID

|6080050|60800|Server 00
  00_60800|douaklsappod.douglas.local/10.2.0.87|SERVER|RUNNING

Java VM

SAP Java Server VM, version:6.1.071 24.55-b08, vendor: SAP AG

Operating system

Windows Server 2008 R2, version: 6.1, architecture: amd64

 

Application

 

Java EE Application (deployable object)

  1. sap.com/tc~pi~tools~dirmig~wd

Web Dynpro Application

DirectoryCockpit

Request URI

/webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd/DirectoryCockpit

Version


 

vendor: 'sap.com', name: 'tc/pi/tools/dirmig/wd', scV:
  'sap.com', scN: 'SOAMON', location: 'SAP AG', counter:
  '7.4008.20140828111619.0000', R: '7.40', SP: '8', PL: '0', change number: '9'
 

 

Web Dynpro Code Generation Infos

 

  1. sap.com/tc~pi~tools~dirmig~wd

WD web module
  webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd:
  SapDictionaryGenerationCore

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:01:39+0000, changelist=402811, host=vmw5876,
  is-central=true)

WD web module
  webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd:
  SapDictionaryGenerationTemplates

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:02:11+0000, changelist=402811, host=vmw5876,
  is-central=true)

WD web module
  webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapGenerationFrameworkCore

  7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T19:41:09+0000, changelist=402838, host=vmw5876,
  is-central=true)

WD web module
  webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapIdeWebDynproCheckLayer

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:25:15+0000, changelist=612716, host=vmw5876,
  is-central=true)

WD web module
  webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapMetamodelCommon

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T19:44:59+0000, changelist=402897, host=vmw5876,
  is-central=true)

WD web module
  webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapMetamodelCore

7.4008.20140806095041.0000 (release=NW731CORE_13_REL, buildtime=2014-08-22T19:42:52+0000,
  changelist=402897, host=vmw5876, is-central=true)

WD web module
  webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapMetamodelDictionary

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T19:51:47+0000, changelist=402813, host=vmw5876,
  is-central=true)

WD web module
  webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapMetamodelWebDynpro

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:03:52+0000, changelist=612717, host=vmw5876,
  is-central=true)

WD web module
  webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapWebDynproGenerationCore

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:25:48+0000, changelist=612716, host=vmw5876,
  is-central=true)

WD web module
  webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd:
  SapWebDynproGenerationTemplates
7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:25:36+0000, changelist=612716, host=vmw5876,
  is-central=true)
WD web module
  webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapWebDynproRuntimeGen
7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:22:51+0000, changelist=612719, host=vmw5876,
  is-central=true)
   sap.com/tc~wd~api

WD web module webdynpro/resources/sap.com/tc~wd~api:
  SapDictionaryGenerationCore

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:01:39+0000, changelist=402811, host=vmw5876,
  is-central=true)

WD web module webdynpro/resources/sap.com/tc~wd~api:
  SapDictionaryGenerationTemplates

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:02:11+0000, changelist=402811, host=vmw5876,
  is-central=true)

WD web module webdynpro/resources/sap.com/tc~wd~api:
  SapGenerationFrameworkCore

7.4008.20140806095041.0000 (release=NW731CORE_13_REL, buildtime=2014-08-22T19:41:09+0000,
  changelist=402838, host=vmw5876, is-central=true)

WD web module webdynpro/resources/sap.com/tc~wd~api:
  SapIdeWebDynproCheckLayer

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:25:15+0000, changelist=612716, host=vmw5876,
  is-central=true)

WD web module webdynpro/resources/sap.com/tc~wd~api:
  SapMetamodelCommon

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T19:44:59+0000, changelist=402897, host=vmw5876,
  is-central=true)

WD web module webdynpro/resources/sap.com/tc~wd~api:
  SapMetamodelCore

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T19:42:52+0000, changelist=402897, host=vmw5876,
  is-central=true)

WD web module webdynpro/resources/sap.com/tc~wd~api:
  SapMetamodelDictionary

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T19:51:47+0000, changelist=402813, host=vmw5876,
  is-central=true)

WD web module webdynpro/resources/sap.com/tc~wd~api:
  SapMetamodelWebDynpro

 

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:03:52+0000, changelist=612717, host=vmw5876,
  is-central=true)

WD web module webdynpro/resources/sap.com/tc~wd~api:
  SapWebDynproGenerationCore

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:25:48+0000, changelist=612716, host=vmw5876,
  is-central=true)

WD web module webdynpro/resources/sap.com/tc~wd~api:
  SapWebDynproGenerationTemplates

7.4008.20140806095041.0000 (release=NW731CORE_13_REL, buildtime=2014-08-22T20:25:36+0000,
  changelist=612716, host=vmw5876, is-central=true)

WD web module webdynpro/resources/sap.com/tc~wd~api:
  SapWebDynproRuntimeGen

7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
  buildtime=2014-08-22T20:22:51+0000, changelist=612719, host=vmw5876,
  is-central=true)

 

Detailed Error Information

 

Detailed Exception Chain 

  java.lang.NullPointerException:
while trying to invoke the method
com.sap.pi.tools.dirmig.channel.metadata.SoftwareComponentVersion.getVersion()
of a null object returned from
com.sap.pi.tools.dirmig.channel.metadata.AdapterMetadataFactory.getLatestSWCV(java.lang.String)

at
com.sap.tc.pi.tools.dirmig.wd.wd.comp.channelmigration.ChannelSelectionView.onActionChannelTableSelect(ChannelSelectionView.java:548)

at
com.sap.tc.pi.tools.dirmig.wd.wd.comp.channelmigration.wdp.InternalChannelSelectionView.wdInvokeEventHandler(InternalChannelSelectionView.java:486)

at
com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)

at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)

at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)

at
com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)

at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)

at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)

at
com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)

at
com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)

at
com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)

at
com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)

at
com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)

at
com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)

at
com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:101)

at
com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

at
com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)

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

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)

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

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Cache refresh issue

$
0
0

Hello Experts,

 

I am working on SAP PO 7.4 . From past few days we are facing the cache refresh issue .

Due to this issue i am not able to develop any interface.

Below is the screen shot of the error.

 

cache refresh error1.JPG

 

cache refresh error2.JPG

 

 

Kindly help me out.

 

Regards,

Amit


Flatfile to XML

$
0
0

Hello Everybody,

 

 

My scenario is SFTP -> Proxy:

 

Input File will look like this:

 

"ET-00.0001";"BOSSARD";"3062096

"ET-00.0001";"BOSSARD";"3062096

"ET-00.0001";"BOSSARD";"3062096

 

Output structure should look like this:

 

<?xml version="1.0" encoding="UTF-8"?>

<ns0:MT_Datei_Out xmlns:ns0="http://namespace">

   <Recordset>

      <Record>

         <value0/> ===== (value0 will contain a single row from the flat file)

      </Record>

   </Recordset>

</ns0:MT_Datei_Out>

 

 

Please refer the screen-shot for module configuration:

 

Error Message: 'xml.keyFieldName' is missing (4403) Parameter 'xml.keyFieldType' is missing (4403) ;

 

As I do not have any keyfield in the input structure, I did not mentioned it in the module config. Does anyboday please help me out to get the output structure?

 

Thanks & Best Regards,

Satish.

PO 7.4 Upgradation details

$
0
0

Hi Experts,

 

Could you please guide me what are all the things need to take care while migrating from PI 7.11 to 7.4 single stack.

Also kindly let me know what are all the post configurations needs to be done once all existing interfaces are moved to 7.4


Cheers

Sai

How to create Single Queue for more than one interfaces(XI)

$
0
0


Hi Experts,

 

I want to set up a separate queue for 3 interfaces which all are outbound IDOC to FTP.

Please let me know ' Hhow to create a queue for multiple interfaces with Quality of Service 'EO''.

 

Thanks,

Srinivas P.

when i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"

$
0
0

when i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"

Table lookup in sap po 7.4

$
0
0

Hi there,

   And recently we have got new PO 7.4 system , to be frank I dont have much idea on this new PO.

and the first scenario is the source input CDF file to ECC (Idoc) via PO.

we need to maintain some table (not sure where) i.e. during mapping runtime for a combination of source field (say 4 field values) from table we need to get combinaiton of target fields values and populate to the Idoc fields.

since we use single stack here my query is

1, where should we create the tables ? ECC or DB (DB2) or ?

2, which will be the best practise wrt performance ?

3, what will be best approach here?

 

pls suggest.

Trial SAP PO instance on Cloud

Development Scope through NWDS on 7.31 Dual Stack

$
0
0

Per my understanding NWDS can be used for developing ESR and ID components but only if we have installed the usage type PO.

 

We have dual stack PI 7.31. What is the scope of PI objects development through NWDS in this case other than usual JAVA coding...adapter module development, dirapi devlopment ..etc..

 

Thanks


Upgrade from NW PI 7.11 TO NW PI 7.4

$
0
0

Hi,

 

We are planning to upgrade out present PI (NW PI 7.11 ) to NW PI 7.4(I think NW 7.4 PO).

 

We are try to run MOPZ for the system we are all unable to find 7.4 , but we are see NW 7.3 SP10 .

 

I can see warning "

Dual Stack: Upgrade to NW 7.40 not possible. See note 1816819."

 

 

I am missing any step. Should I split ABAP and Java .

 

Is NW 7.4 single single stack system.

 

Please guide in right direction.

 

Regards,

Kiran M

Exchange profile error: dbconnect.prop: failed to load properties file .\dbconnect.properties

$
0
0

All,

 

We are using PO 7.4 with SP5, and we have an issue while accessing URL Exchange profile page (http://<host:port>/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp) it throw's the below error.

 

dbconnect.prop: failed to load properties file .\dbconnect.properties

dbconnect.prop: failed to load properties file


Did some one seen this before and have resolved ? Any help is highly appreciated.


Thank you, Pranay

IDOC__AAE receiver exception java.lang.String length PO 7.4

$
0
0

Hi,

 

My scenario

 

Outbound/Sender

 

data type/msg type/outbound service interface

 

Inbound/Receiver

 

2 messages- the message must generate based on mapping.. one IDOC and one normal MT.

 

Created Inbound Serivice Interface- Inserted IDoc in one operation and MT in one more operation in same inbound interface. Typical 1:n mapping

 

in  ICO created extended receiver determination to determine receiver- each message must go to different receiver.

 

1st ERROR

 

as per note- SAP NOTe- 1862655, we need to put target operation as MESTYP.IDOCTYP.CIMTYP

 

which is the IDOC itself. So i selected IDOC from value list and other one kept as same inbound operation.

 

 

2nd ERROR

 

After doing the above things scenario worked-- but now in OUTBOUND processing it asks for 4 messages, because rather than conditional receiver determination it becomes msg split for each receiver. making 4 msgs .

 

I can't give dummy channels when it goes for PRODUCTION environment. How to resolve this.

 

Please help

 

Regards,

Vikas Kumar Singh

REST Sender adapter - multiple dynamic parameters

$
0
0

Dear

 

We are currently configuring a sender REST adapter which be called as such:

http://host:port/RESTAdapter/pi/query/jira/solman/getsystems?sap-client=001&cust=00009999

(even encoding the question url or only question mark and ampersand doesn't help)

 

However whenever we try this, we can see following error returned by PI:

 

The sender adapter is configured properly according to the documentation on SAP Help:

 

Has anyone encountered this issue before?

We might think this is a bug, as the interface works fine when we use following pattern:

 

But only when we use the url as follows:

http://host:port/RESTAdapter/pi/query/jira/solman/getsystems%3Fsap-client=001&cust=00009999

 

We had to encode the question mark in the URL (%3F) in order for PI to pick the right channel with the correct parameters.

 

When using the normal question mark (e.g. used with the Chrome Advanced REST Client), we basically receive the same error as above:

 

 

Have any of you encountered this before, or have any of you used multiple parameters before in the sender REST adapter.

 

 

Thanks for any feedback.

Mapping in BPM - set value of collection item

$
0
0

Hello,

 

is it possible to set value to exact item of collection in mapping step in netweaver BPM?

 

 

I need something like set(<collection_variable>,<item_index>,<item_value>)  - so exact opposite of GET generic function, which gets specific item from collection.

 

Is it possible in NW BPM?

Viewing all 1235 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>