Module Deployed for axis

Hi,
I am using AXIS adapter,
Deployment is done correctly, even tested by the url..it was successful.
I want to know what all modules are required to add in the soap receiver.
mine is proxy soap synch scenario PI 7.1,
Any help for solving this problem will be greatly
appreciated.
Regards

Hi,
Many thanks..
I concluded to use AXIS soap receiver bcos when i pasted URL in browser it opened Welcome to axis..(but no wsdl file )
i derived that probly webservices are hosted on AXIs...and so i configured soap axis adapter.
But when i execute the scenario in moni it says::
<request message name> doesnt exists.
i m in a fray that how do i know whether to use AXIS or soap receiver adapter..
rgds,

Similar Messages

Deployment issue for Axis Framework in PI 7.0 server

Hi Experts,
I have one issue regarding the deployment of AXIS framework for Receiver SOAP adapter in PI 7.0 server.
Moreover i have a requirement to use UserNameToken security with PasswordDigest.
I have deployed aii_af_axisprovider.sda file into PI server with relevant .jar files.
However when i am checking through url http://host:port/XIAxisAdapter/MessageServlet its giving that optional components are missing
1)XMLSecurityAPI
2)Apache WSS4j
3)Apache Addressing
In SAP Note 1039369 its mentioned about to use wss4j-1.5.4.jar,xmlsec-1.4.0.jar,opensaml-1.0.1.jar files.
Now my concern is to enable UserNameToken Security with PasswordDigest which version of Wss4j is required along with xmlsec version and do we need opensaml-1.0.jar file for same requirement.
Is it sufficient if we deploy wss4j-1.5.4.jar and xmlsec-1.3.0.jar to enable the UserName Token secuiry.
Request you all to please confirm the same.
Thanks in advance
Regards
Nilesh

I have the same requirement. Just wanted to know if opensaml-1.0.jar file is required to enable the UserName Token secuiry.

Error on SOAP Receiver for Axis

Hi all,
Is there anybody to help for solution?
Thanks.
Error on SOAP Receiver for axis
Error Message
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: Exception in getMethodReady() for stateless bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: com.sap.engine.services.ejb3.util.pool.PoolException: javax.ejb.EJBException: Exception raised from invocation of public void com.sap.aii.adapter.axis.modules.AFAdapterBean.ejbCreate() throws javax.ejb.CreateException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@3ff5ea5d for bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: javax.ejb.CreateException: java.lang.NoClassDefFoundError: org/apache/axis/types/URI$MalformedURIException</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

We deployed com.sap.aii.af.axisproviderlib.sda to use SOAP for axis.
We sent data from SAP to Axis, error below ocured?
What must we do to solve problem?
Thanks.
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.engine.interfaces.messaging.api.exception.MessagingException: org.apache.axis.ConfigurationException: handler is not instantiated org.apache.axis.ConfigurationException: handler is not instantiated at com.sap.aii.adapter.axis.modules.HandlerCore.process(HandlerCore.java:73) at com.sap.aii.adapter.axis.modules.HandlerBean.process(HandlerBean.java:75) at sun.reflect.GeneratedMethodAccessor360_10000.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2634_10000.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1431_10000.process(Unknown Source) at com.sap.aii.af.app.listener.AFWListenerBean.onMessage(AFWListenerBean.java:332) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1479_10000.onMessage(Unknown Source) at com.sap.engine.messaging.impl.spi.ServicesImpl.deliver(ServicesImpl.java:314) at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1000) at com.sap.engine.messaging.impl.core.queue.consumer.RequestConsumer.onMessage(RequestConsumer.java:73) at com.sap.engine.messaging.impl.core.queue.Queue.run(Queue.java:921) at com.sap.engine.messaging.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Issue on Deployment of AXIS framework in PI 7.0 Server.

Hi Experts,
We have a requirement of Using AXIS Framework in Receiver SOAP adapter in PI 7.0.Moreover we need USERNAME token with PasswordDigest.We have deployed aii_af_axisprovider.sda file in PI server with all relevant .jar files.However when we are checking the url http://host:port/XIAxisAdapter/MessageServlet its showing following optional components are missing.
1)XML Security API
2)Apache WSS4J
3)Apache Addressing
However we have used wsdl4j-1.5.1.jar file.We have added entry for wsdl4j-1.5.1.jar in provider.xml as well.However it still showing warning that optional component is missing
Could you please let us know which version we need to deploy for Apache WSS4J in PI server or do we need to do any other configuartion apart from above configuration so that to enable the UserNameToken security with passwordDigest.
Thanks in advance.
Regards
Nilesh.

Hi,
Post the answer for your issue, so that others can have!

SOAP receiver adapter for Axis

Hi,
I used SOAP receiver adapter for Axis like below:
Transport Prorocol : HTTP
Message Protocol : Axis
Url: http://<IP>:<Port>/xxx/WebService/services/Head/yyy
Authentication : Basic
User: <user>
Password: <password>
SOAP Version : 1.1
SOAP Action: : <method>
Encapsulation Format : MIME
Payload Extraction : SOAP Body
When i drive PI message it generates error below.
What must i do to solve this problem?
Thanks.
Error message
com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: Exception in getMethodReady() for stateless bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: com.sap.engine.services.ejb3.util.pool.PoolException: javax.ejb.EJBException: Exception raised from invocation of public void com.sap.aii.adapter.axis.modules.AFAdapterBean.ejbCreate() throws javax.ejb.CreateException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@20715646 for bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: javax.ejb.CreateException: java.lang.NoClassDefFoundError: org/apache/axis/types/URI$MalformedURIException

*Url:* http://172.28.6.194:8080/AssetManagerWebService/services/Head/SapTest
When i use Url with *?wsdl* it generates below (it'is very long. I give part of it)
wsdl
<?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions targetNamespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:intf="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns:tns1="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Types" xmlns:tns2="http://schemas.hp.com/AssetManager/R51/ACMetaData" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- 
- <wsdl:types>
- <schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Wsdl" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:AdministrationTypes="http://schemas.hp.com/AssetManager/Custom/Head/Administration/Types" xmlns:CableTypes="http://schemas.hp.com/AssetManager/Custom/Head/Cable/Types" xmlns:CatalogTypes="http://schemas.hp.com/AssetManager/Custom/Head/Catalog/Types" xmlns:ChargebackTypes="http://schemas.hp.com/AssetManager/Custom/Head/Chargeback/Types"
<import namespace="http://schemas.hp.com/AssetManager/R51/ACMetaData" />
<import namespace="http://schemas.hp.com/AssetManager/Custom/Head/SapTest/Types" />
- <annotation>
<documentation>Auto-generated schema for AssetCenter web services for Head/SapTest Implementation</documentation>
</annotation>
<import namespace="http://schemas.hp.com/AssetManager/Custom/Head/SAM/Types" schemaLocation="../../schema/Head/SAM/SAMTypes.xsd" />
<import namespace="http://schemas.hp.com/AssetManager/R51/ACMetaData" ......
<wsdl:operation name="retrieveAllBusinessAPIListByName">
<wsdlsoap:operation soapAction="retrieveAllBusinessAPIListByName" />
<wsdl:input name="retrieveAllBusinessAPIListByNameRequest">
<wsdlsoap:body use="literal" />
</wsdl:input>
<wsdl:output name="retrieveAllBusinessAPIListByNameResponse">
<wsdlsoap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SapTestService">
<wsdl:port binding="impl:SapTestSoapBinding" name="SapTest">
<wsdlsoap:address location="http://172.28.6.194:8080/AssetManagerWebService/services/Head/SapTest" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Verify EJB after Cannot determine the Java EE module type for

Hi All,
I start verify EJB it's throw an exception
Which cases occurring this exception, how can I resolve this?
Could not verify successfully.
java.io.IOException: Cannot determine the Java EE module type for C:\Mystuff\projects\Naki\Naki-ejb\dist\Naki-ejb.jar
     at com.sun.enterprise.deployment.archivist.PluggableArchivistsHelper.getArchivistForArchive(PluggableArchivistsHelper.java:137)
     at com.sun.enterprise.deployment.archivist.PluggableArchivistsHelper.getArchivistForArchive(PluggableArchivistsHelper.java:98)
     at com.sun.enterprise.deployment.archivist.PluggableArchivistsHelper.getArchivistForArchive(PluggableArchivistsHelper.java:110)
     at com.sun.enterprise.deployment.archivist.ArchivistFactory.getArchivistForArchive(ArchivistFactory.java:93)
     at com.sun.enterprise.tools.verifier.VerificationHandler.initStandalone(VerificationHandler.java:204)
     at com.sun.enterprise.tools.verifier.VerificationHandler.<init>(VerificationHandler.java:109)
     at com.sun.enterprise.tools.verifier.Verifier.verify(Verifier.java:140)
     at com.sun.enterprise.tools.verifier.Verifier.main(Verifier.java:114)
Thanks,

I'm getting the same error although i'm not receiving those entries in the log. Can someone please respond to this post. I've tried a lot of things but can't seem to figure it out. Please email me at [email protected] if you can help.
Thanks

Setting format and format options in Output module settings for render queue item

Hello,
I am unable to set the "Format" and "Format options" for video in output module settings programatically using After effects apis.
I referred the after effects cs3 sdk guide for the apis.
I find apis for all other options in the "outputmodule settings " like :
AEGP_SetEmbedOptions
AEGP_SetOutputChannels
AEGP_SetStretchInfo
AEGP_SetSoundFormatInfo
But there is no api listed for setting the options available in the "Format" tab and "Format options" tab.
The "Format" tab and "Format options" tab is available in the dialog that opens when user clicks on the Output module settings for the render queue item.
The format tab when clicked shows a drop down list with aff different formats. By default "Video for Windows" is set.
The drop down list contains following format options
Adobe Clip Notes
Adobe Flash video
Quicktime movie
Video for Windows
I need to be able to set the "Quicktime movie" option in the Format tab programmatically and then set the compression type as "Animation" in the compression settings programatically using the api functions available in AE CS3 SDK
Please suggest the suitable api to do so.
I need to write my own plugin to export to Quicktime movie using the after effects apis.
I follow below steps to do so.
1. AEGP_InsertMenuCommand and add export option to AE with my own plugin name
2. In the command hook, select active item using AEGP_GetActiveItem
3. Add it to render queue
4. Set the output module settings for 0 th output module using
suites.OutputModuleSuite1()
5. Use different functions from suites.OutputModuleSuite1() to set the output module settings like EmbedOptions,StrechInfo etc.
6. Till this step, I am doing it right. But I am not able to find any api for setting Format options using suites.OutputModuleSuite1()
I also checked all other suites available for setting FormatOptions but no luck.
Please help.
Thanks,
-Namita

Hi Namita,
I am experiencing the same problem.
I am using AE CC SDK, and I am unable to change the outputmodule format to any of the other movie format types (mov, mpg, flv, etc.).
It is always set to "avi"
I even compiled and ran the Queuebert example in the SDK, and there I get the same problem: the path extension is always left on ".avi"
Does anyone know how to change this?

"Common module" missing for XP on Satellite Pro A200

Hello everyone,
I received my Satellite Pro A200 (PSAE7) laptop with a Vista OS.
I have made a fresh & clean XP installation on it using the Toshiba's installation instructions document.
Everything is working fine except my Fn+F6 Fn+F7 Fn+F8 hotkeys for Wireless and screen brightness.
I have made a few search over the internet and I found that page :
- http://support.toshiba-tro.de/kb0/TSB7401VB0003R01.htm
Looks like that I need to setup "common module" installer in order to make work those hotkeys.
But the problem is that the "common module" is not available on the driver page for XP ....
If I change the OS type to Vista there is "Value Added Package" available but it's not compatible on XP ...
I tried to download and setup a "common module" for Sat Pro A120 model but i got an "TVALZ" error during the installation ....
Did Toshiba support forget to put online a "common module" installer for XP for Sat Pro A200 ??
How can I make work my Fn+F6 Fn+F7 Fn+F8 hotkeys ?
Any help will be really appreciated !
Thanks,
Can

Hello darkmatterman,
First of all thanks for you reply and for your tips about the Bios version (Vista vs XP).
The first day I received my laptop on Vista OS, I already made a Bios update "the Vista compatible one". So my Bios is v1.70 actually.
I will try monday morning to update the latest XP compatible Bios version which is v5.20...
Do you know if it's possible to apply the latest XP bios upgrade on a bios which was already been upgraded with a Vista compatible version ?
And if the XP comptabile Bios upgrade works, do you think that I will need to setup my fresh XP again (with all Toshiba drivers & utils setup order...) ?
Regards,
Can

Creating SOAP Receiver comm.channel for axis web service

Hi,
I created Soap Receiver comm. channel fro Axis web service like below:
*Target URL* : http://<IP>:<Port>/<x>/service
*User:* <user>
*Password :* <password>
*SOAP Action:* <target namespace>/method
when i drive PI Message that use Soap Receiver it get error below
I do same method for .Net web service, it runs properly.
How can i solve this problem?
Error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID B3004965647F340C997B5F2CC9EA7E22 Software Component 4CF44F80503211DEB2A0D3F40A194B29</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID B3004965647F340C997B5F2CC9EA7E22 Software Component 4CF44F80503211DEB2A0D3F40A194B29</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
I did all but nothing changed?
I have doubt about axis side. Because respose like below.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
May be Soap Receiver setting for axis web service must be different.
Thanks.

Function module exits for Tcode MD11.

Please tell me, Function module exits for Tcode MD11.
Reg .
Praju

Hi
LMDR2001
LMDZU001
Try out these exits.
Check the folloing BADI's
MD_PLDORD_SCHEDULING
MD_PIR_FLEX_CONS
MD_PLDORD_SCHEDULING
Regards
Divya

Function module name for routing fom production orders

Function module name for routing fom production orders

Hi
There are lot of fun modules related to routing
like
BAPI_ROUTING_CREATE
BAPI_ROUTING_EXISTENCE_CHECK
goto SE37 Tcode
enter routing press F4
you will get a lot out of that use the required one
Reward points for useful Answers
Regards
Anji

Function Module (BAPI) for Delivery Change

Dear All,
We have a Function Module "BAPI_SALESORDER_CHANGE" for changes in sales order, wherein we also can enter Texts in sales order.
Please tell me similar such function module for Outbound Delivery, wherein I can enter / insert / change the Texts (both Header & Item) in a deivery document.
Regards,
Dhananjay

Thanks
Where in this Function Module do I find the table / parameter for adding text at item & header level.
Regards
Dhananjay

Function module need for 0fiscvarnt

Hi i have 0comp_code,budat and 0fiscper as a source fields,now i want to get 0fiscvarnt...please give me any logic or function module available for that
thanks

Hi,
Usually fiscal year variant is constant if not getting populated from source system.
Check with function team member what Fiscal year variant they using.
Regards,
Akshay

Function module used for ENQUEUE_EIQMEL & DEQUEUE_EIQMEL function

Hi All,
It should be highly appreciable if any one could please help.
I need the name of the function module used for ENQUEUE_EIQMEL & DEQUEUE_EIQMEL function.
waiting for help.
Thanks
Shaw

Hi,
The names 'ENQUEUE_EIQMEL' and 'DEQUEUE_EIQMEL ' you have mentioned are itself the function modules. Which other FM's you need i didnt understand.
These are FM to ahndle lock objects 'QMEL'.
please reframe your question in case of further issues.
Regards,
Mansi.

Function module(s) for Cube Collapsing/Compression

Hi Experts,
can anybody tell me if there's a SAP Function module availbale for Collapsing/Compressing requests of a cube ?
Background is we want to automate collapsing of cubes by an APAB report instead of using a process chain or RSA1.
Any suggestions? Any pitfalls for such an implementation ? Any expieriences ?
We're on SAP BI 7.00 19, Oracle 10.2.0.4
Best regards,
yk

Hi Srinivas,
thanks for the quick answer, I will check the FM you mentioned.
We think of a cube exceptions list wich should NOT be condensed, and all OTHER cubes should be condensed.
With a process chain we have to maintain these OTHER list manually. In an ABAP report we could exclude the exceptions and condense the rest.
Developers tend to "forget" to add the CONDENSE step. So with time more and more cubes store only in F-tables and nothing in the E-tables (producing more workload as query runtime, DB maintanence like index creation runtime , statistic runs ...) and last but not least occupy disk space wich is expensive if you have a mirrored high performance disk system .
Best regards,
yk

Module Deployed for axis

Similar Messages

Maybe you are looking for