Assemble components -xml message problem

Hi,
In our 5.2.3.1 we have following problem.
We are assembling components with assemby message:
Sometimes we have not all the identifiers received to the system.
These cases the assembly message returns an error but it assembles part of the components in the message. That is not wanted way of working. After error we should be able to receive the missing component to the system and send the assembly message again. But now part of the components have already been assembled and the assembly message will fail:
No quantity left to assemble for the specified location (Message 13971)
Is there any way of preventing partial assembly of components in this case?
Br,
Pete
Edited by: Petri Kauppi on Jun 7, 2010 1:32 PM
Edited by: Petri Kauppi on Jun 7, 2010 1:35 PM (xml- messages with are not show correctly, removed example messages)

Problem was so long ago...
If I remember correct there were added new tags to XML -message. Something like ALL_OR_NOTHING.
TRUE/FALSE
With this tag we can prevent partial assembly by setting it TRUE.

Similar Messages

XML Messages Problem (Whats next step ?)

I am kind of confouse right now, why i done GRMG configuration and create secronios....?
what is the link between RZ20 and RZ21 and GRMG why we are creating own monitors theres?
I will send some URL for how its look like
please
With heading
exchangeInfrastructure_systems
CCMS
CCMS2
GRMG
http://www.flickr.com/photos/25222280@N03/2397974445/
http://www.flickr.com/photos/25222280@N03/2397974429/
http://www.flickr.com/photos/25222280@N03/2398803974/
http://www.flickr.com/photos/25222280@N03/2397974409/
http://www.flickr.com/photos/25222280@N03/?saved=1
Thnaks a lot
please what i can do next....

I am kind of confouse right now, why i done GRMG configuration and create secronios....?
what is the link between RZ20 and RZ21 and GRMG why we are creating own monitors theres?
I will send some URL for how its look like
please
With heading
exchangeInfrastructure_systems
CCMS
CCMS2
GRMG
http://www.flickr.com/photos/25222280@N03/2397974445/
http://www.flickr.com/photos/25222280@N03/2397974429/
http://www.flickr.com/photos/25222280@N03/2398803974/
http://www.flickr.com/photos/25222280@N03/2397974409/
http://www.flickr.com/photos/25222280@N03/?saved=1
Thnaks a lot
please what i can do next....

Problem in XML Message creation using ABAP Proxy

Hi,
I am trying to send the data from ECC to CRM when post goods issue is done for a delivery from ECC side using ABP Proxy. I called my proxy method in BADI : DELIVERY_PUBLISH.
And after calling the method, I used commit work also.
But the problem is, some times it is working fine. and some times the XML messages are not getting created. When I go in debug, looks everything is fine.
I am unable to understand why this inconsistency.
Could you please help me out, do I need to take any more precautions.
Thanks,
Sandeep

Hi,
There is no problem in the proxy. Some small problem in the database update.
It is solved.
cheers
san

Problem in de-queuing xml messages after upgrade to 11g database

We just upgraded from database 10g to 11g. After upgrade we are facing a problem in processing xml messages smaller than 4000 bytes. Messages larger than 4K bytes are handled correctly.
We have Tibco IM/BW adaptors accessing Oracle AQ through JDBC Thin from other platforms than the DB is on.
These clients connect to the database with an application user (XXIO) which belongs to the APPS schema.
The client makes an enqueue to the queue-table XXIO_I00_I_JMS_Q_TABLE and in USER_DATA-part of the message the client specifies some header-information for the message with the actual data.
The enqueue is made with JDBC Thin 11.1.0.7 and with the aqapi.jar/jmscommon.jar-files from the rdbms 11.1.0.7-installation, so the API towards the database is of the correct version.
When the enqueue is done, the message has correctly been put into the table XXIO_I00_RT_I_JMS_Q_TABLE.
Now to the problem,
For example, we have a message that just has been put into the table, and it has a text_len of 3887.
The text-part of the message is put in text_lob, not in text_vc.
The problem now is that when the propagation starts
(execute DBMS_AQADM.ENABLE_PROPAGATION_SCHEDULE(queue_name => 'XXIO.XXIO_I00_RT_I_JMS_Q'),
the code for dequeue and move of the message, assumes that the text is in text_vc when text_len <= 4000 bytes.
Since that's not the case, the message propably gets errored out, and is put in the errorqueue.
The length of the messages that are put into text_lob vary from 2000 and up, so text_vc seems to be used only
for messages below 2000 bytes now. This problem occurred when we upgraded the DB and client API to 11.1.0.7.
Any pointer will be helpful.
Thanks

here is the output
HOST LOWER_PORT UPPER_PORT ACL ACLID
smtp.ABC.com 25 25 /sys/acls/ACLPORTA25.xml A275C7806DD74DE38F95D7E17794803D
mqlinuxext.serasa.com 4081 4081 /sys/acls/ACLPORTA4081.xml 85ED7A539AAC4A419C828D0EC037C090
mqlinuxext.serasa.com 80 80 /sys/acls/ACLPORTA4081.xml 85ED7A539AAC4A419C828D0EC037C090
mqlinuxext.serasa.com /sys/acls/http_access_acl.xml 40C25DBC57E4476BA7906652EBD50332
Thanks a lot

Problem in ABAP Proxy(sometimes XML Messages are not being created)

Hi,
I am trying to send the data from ECC to CRM when post goods issue is done for a delivery from ECC side. I called my proxy method in BADI : DELIVERY_PUBLISH.
And after calling the method, I used commit work also.
But the problem is, some times it is working fine. and some times the XML messages are not getting created. When I go in debug, looks everything is fine.
I am unable to understand why this inconsistency.
Could you please help me out, do I need to take any more precautions.
Thanks,
Sandeep

You mean you can't find any message in SXMB_MONI of your ECC or is it XI where you can't see message?
If you have not checked in SXMB_MONI of ECC then may be messages are created but they are going into error and that's why you are not able to see any message in XI.

XML messages eamil (Problem)

http://www.flickr.com/photos/25222280@N03/
Hi, All
We are using XI 3.0 Support package: 20
I can expalin the probelm step by step please help me about thanks in advanced
Step: 1
I am trying to get XML message from XI system messages shows in SXMB_MONI with some read flags
Step 2
SAPconnect working fine... I can send email anyone internaly through so01 so connections works
Step 3
Goto ALRTCATDEF and create alert category which is XDV_ALRT then goto RWB and click Alrt configuration, select classification and click Roules its does show my user ID and Alert cagt. there
Then I received XML messages my eamil with Attachment file and subject: Alert, which is I didn't define anywhere... I didn't know where this messages comes from?
Step 4: I put some others users using alrtcatdef tr such as make_m and amer_J and my user id in it as well but only I am getting these messages not others I double check user profile and roles all pretty much same look like...
My simple question is that I want to setup XML messages to some users through email thats it
I am sending some screen shot I thing someitng is missing or I am getting some wrong please look at this
http://www.flickr.com/photos/25222280@N03/
Thanks

Hello Aamir
Thanks for very fast responsed, Aamir when I goto SXMB_MONI first screen comes up "Monitor processed for XML messages"
First Screen
view is = Defaul
Status group is empty
Standard selection criteria (from date to date = I just define date couple of days ago!)
Sender and receiver all fields are empty
2nd Screen
When I execute its shows xml messages with black flag and Red dot all Red dot comes with attachemnt eamil
in this screen they have some button like "display", "error information" "referencing infromation" "reset" 'shows"
with Error look like that before I click on it
@5C\QSystem Error - Restart Not Possible@ @5F@ 02.04.2008 02:14:39 02.04.2008 02:14:43 MOL_NQA tp://www.abc.com/MOL/OnlineStore O_msgIF_CHECK_BILLING
dbcinqa http://www.mitel.com/MOL/OnlineStore I_msgIF_CHECK_BILLING "Current Status" @5F@ @5F@ @5F@ 6
When I click on that 3rd screen comesup with some bottons like windows1 windows2, ....
with RED error messages in right side....
that error messages comes with my attachment....
I didn't see anything scenarios, how may I check that where is it? please let me know
My name is also Aamir
Thanks

Data Services Fix Pack 12.2.1.2 issued to resolve XML loader problem

We've had a few customers contacting us about the following error message:
"The message type for datastore <my_ds> has not been set". Please notify Customer Support"
Note that the text "<my_ds> will be the name of the XML loader you have in your dataflow. This error occurs when you are adding a new loader to a dataflow that is an XML type.
The customers that have reported this issue were all building real-time jobs and the loader type was XML Message Target.
In order to address this issue you will need to download and install the latest update which is 12.2.1.2. The above issue was introduced in 12.2.1.1 (3.2 SP1). You will ONLY have to install the client components (Designer) in order to address this issue. no updates are necessary to the server side of the application to address this problem.
An SAP Note has also been written up on this issue: [1423045|https://bosap-support.wdf.sap.corp/sap/support/notes/1423045]
Thanks,
Ryan

there is a connection timeout when trying to contact the laptop.the last lines it shows are:
PCI: setting IRQ 0 as level-triggered
ALI15X3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x8080-0x8087, BIOS settings: hda: DMA, hdb:pio
ide1: BM-DMA at 0x8088-0x808f, BIOS settings: hdc: pio, hdd: pio
hda: IC25N060ATMR04-0, ATA DISK drive

Assembly failed error message

Hello Experts,
We are getting "Assemble failed" error message when we tried to assemble components. I have attached a CMS log file. You help and feedback is greatly appreciated.
David
Info:Starting Step Repository-export at 2008-10-08 05:34:02.0206 -4:00
Info:Component:alleghenyenergy/AE_IMPORTED_OBJECTS
Info:Version :JD1_XD1IR01_C.20081008093400
Info:1. PR is of type TCSSoftwareComponent
Info:the workspace will be read from XI
Info:OK   : workspacedata added.
Info:Component:ivara.com/IVARA_EXP_ENTERPRISE
Info:Version :JD1_XD1IR01_C.20081008093401
Info:2. PR is of type TCSSoftwareComponent
Info:the workspace will be read from XI
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Exception received:
ClientServerException exception:Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
com.sap.aii.utilxi.misc.api.ResourceException: Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
     at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.checkSwcvExistence(InternalRepTransportServiceImpl.java:316)
     at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.createSupportPackage(InternalRepTransportServiceImpl.java:283)
     at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.createSupportPackage(TransportServiceImpl.java:362)
     at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:206)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
     at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
:communication error: Exception received:
ClientServerException exception:Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
com.sap.aii.utilxi.misc.api.ResourceException: Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
     at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.checkSwcvExistence(InternalRepTransportServiceImpl.java:316)
     at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.createSupportPackage(InternalRepTransportServiceImpl.java:283)
     at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.createSupportPackage(TransportServiceImpl.java:362)
     at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:206)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
     at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Exception received:
ClientServerException exception:Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
com.sap.aii.utilxi.misc.api.ResourceException: Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
     at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.checkSwcvExistence(InternalRepTransportServiceImpl.java:316)
     at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.createSupportPackage(InternalRepTransportServiceImpl.java:283)
     at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.createSupportPackage(TransportServiceImpl.java:362)
     at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:206)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
     at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
     at com.sap.cms.tcs.client.XICommunicator.readWorkspaceData(XICommunicator.java:228)
     at com.sap.cms.tcs.core.RepositoryExportTask.processRepositoryExport(RepositoryExportTask.java:226)
     at com.sap.cms.tcs.core.RepositoryExportTask.process(RepositoryExportTask.java:324)
     at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
     at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)
     at com.sap.cms.tcs.core.TCSManager.assemblePropagationRequests(TCSManager.java:677)
     at com.sap.cms.pcs.assembly.manager.AssemblyManager.assemble(AssemblyManager.java:1510)
     at com.sap.cms.pcs.assembly.AssemblyQueueHandler.execAssembly(AssemblyQueueHandler.java:818)
     at com.sap.cms.pcs.assembly.AssemblyQueueHandler.startAssembly(AssemblyQueueHandler.java:133)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startAssembly(CmsTransportProxyBean.java:829)
     at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl20.startAssembly(LocalCmsTransportProxyLocalObjectImpl20.java:1836)
     at com.sap.cms.ui.wl.Custom1.startComponetAssembly(Custom1.java:14080)
     at com.sap.cms.ui.wl.Custom1.assembleQueue(Custom1.java:4685)
     at com.sap.cms.ui.wl.wdp.InternalCustom1.assembleQueue(InternalCustom1.java:2303)
     at com.sap.cms.ui.wl.Worklist.handleAssemblyOptionsEvent(Worklist.java:1487)
     at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2520)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Component.fireEvent(Component.java:283)
     at com.sap.cms.ui.wl.wdp.InternalWorklists.wdFireEventAssemblyOptionsEvent(InternalWorklists.java:388)
     at com.sap.cms.ui.wl.Worklists.fireAssemblyOptionsEvent(Worklists.java:247)
     at com.sap.cms.ui.wl.wdp.InternalWorklists.fireAssemblyOptionsEvent(InternalWorklists.java:328)
     at com.sap.cms.ui.wl.AssemblyOptions.onActionStartAssembly(AssemblyOptions.java:276)
     at com.sap.cms.ui.wl.wdp.InternalAssemblyOptions.wdInvokeEventHandler(InternalAssemblyOptions.java:339)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Info:Step Repository-export ended with result 'fatal error' ,stopping execution at 2008-10-08 05:36:32.0376 -4:00

Hi,
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Exception received:
ClientServerException exception:Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
The error is saying that there might a communication issue with CBS to CMS. That's the reson the imported SCA version is not available in the current system to assemble. The NWDI restart may work some times.
Thanks
Krishna

View is not retuning data when creating XML message through workflow

Hi All,
This is a very critical problem for me. I am trying to send an XML message (outbound) through XML gateway. This is done from a custom workflow. The message creation is done from the standard procedure ecx_document.sendDirect. The data for the XML file is taken from two views (whcih are created in a custom schema and have synonym in apps). One view for header and another one for line information (I am creating an XML for a purchase order).
The problem is when the workflow try the first time to create a message, the views are not returning data. So message creation fails. Now, if we restart the workflow after some time, it will work and the message is created. What could be the reason for this sort of a behaviour ?
I am using business events to trigger the workflow. The data in the table/view will be updated by standard POAPPRV workflow activities. The custom workflow is subscribed to a business event raised from POAPPRV workflow, at a certain point. So this will execute when this event is raised from POAPPRV wf. The subscription has a phase value of 99.
Any help on this regard will be much appreciated, as this is a critical issue.
Thanks in advance,
Arun
PS : One more thing : this is happening mostly in the production instance where the number of messages is very high (freqency).

Hello,
With the BAPI_EQUI_CREATE you can only create PM equipments not IS-U devices that why there is no IS Tab .
You have to use the dialog transactions IQ01, IQ04 or the MM transaction, where you can create devices through a movement.
There is objecttype DEVICE (SWO1) with the following methods:
-> Device.CreateFromData (Create Equipment Master Record)
-> Device.Create (Create Equipment Master Record)
-> Device.CreateISU (Create IS-U: Modification for IS-U)
Please check whether you can use method Device.CreateISU for your requirement.
Regards
Olivia

Read XML message from a CLOB

We are currently receiving XML messages from a business partner that goes
through a transformation/parser first to make sure the xml document was
in MISMO form (Mortgage Industry Standard Message Organization). Then the
document is stored in a clob in a table. The document is stored Without
the tags. We are storing these XML messages into a CLOB datatype for
later processing. I want to read the CLOB and then parse out the
individual fields to store into a table. What is the best way to
accomplish this in PL/SQL? Here is one sample record:
<MORTGAGEDATA>
<APPLICATION LoanPurposeType="OTHER">
<LenderCaseIdentifier>3631681</LenderCaseIdentifier>
<LendersBranchIdentifier>2966448</LendersBranchIdentifier>
</APPLICATION>
<PROPERTY PropertyUsageType="Primary">
<Address1>1335 test</Address1>
<City>las cruces</City>
<State>NM</State>
<PostalCode>88001</PostalCode>
</PROPERTY>
<SUBJECTPROPERTY>
<SubjectPropertyEstimatedValueAmount>69000</SubjectPropertyEstimatedValueAmount>
</SUBJECTPROPERTY>
<BORROWERRECONCILEDLIABILITY LiabilityType="HelocSubjectProperty">
<LiabilityUnpaidBalanceAmount>0</LiabilityUnpaidBalanceAmount>
<LiabilityMonthlyPaymentAmount>0</LiabilityMonthlyPaymentAmount>
</BORROWERRECONCILEDLIABILITY>
<BORROWERRECONCILEDLIABILITY LiabilityType="MortgageLoanSubjectProperty">
<LiabilityUnpaidBalanceAmount>0</LiabilityUnpaidBalanceAmount>
</BORROWERRECONCILEDLIABILITY>
<BORROWER>
<FirstName>scooby</FirstName>
<MiddleName/>
<LastName>doo</LastName>
<NameSuffix/>
<MothersMaidenName>velma</MothersMaidenName>
</BORROWER>
</MORTGAGEDATA>
NOTE: I have tried to use DBMS_XMLQUERY and it comes out like this using a
stored procedure called printclob: When I do this the data is put into
one field called xml_app_msg. The problem is how do I reference the
individual fields like FirstName and so on to store in another table? Can
I apply a stylesheet and if so, how?
Or do I create an object type called xml_app_msg with the fields lastname
and so on?
-- The table is raw_xml_msg_tbl and the field with the stored infomation is
xml_app_msg.
set serveroutput on size 50000
declare
queryCtx DBMS_XMLquery.ctxType;
result CLOB;
begin
queryCtx := DBMS_XMLQuery.newContext('select xml_app_msg from raw_xml_msg_tbl where app_id = :APP_ID');
-- DBMS_XMLQuery.clearBindValue(queryCtx);
DBMS_XMLQuery.setBindValue(queryCtx,'APP_ID','LT1001');
-- get the result..!
result := DBMS_XMLQuery.getXML(queryCtx);
-- Now you can use the result to put it in tables/send as messages..
printClobOut(result);
DBMS_XMLQuery.closeContext(queryCtx); -- you must close the query handle..
end;
OUTPUT:
<?xml version = '1.0'?>
<ROWSET>
<ROW num="1">
<XML_APP_MSG><MORTGAGEDATA>
<BORROWER>
<FirstName>Falls</FirstName>
<MiddleName/>
<LastName>Water</LastName>
<NameSuffix/>
<SSN>123-45-6789</SSN>
</BORROWER>
</MORTGAGEDATA>
</XML_APP_MSG>
</ROW>
</ROWSET>
null

I parse the XML doc into a domdocument and then loop through using xpath.valueof to pull the individual values from the nodes and then build a generic insert. It works quite well with a small number of columns. I'm not sure how it would work with a lot of columns. You can get code examples from Steve Muench's book "Developing Oracle XML Applications".

XML message as input for webservice gives deserialization error

Hi,
jDeveloper 10.1.3
BPEL PM 10.1.2.0.2
Carrental example
Problem:
For the Business Rule Engine I did the Carrental XML example. Based on the java application that connects to the BR engine, I created a webservice in jDeveloper and deployed it to my localhost AS 10.1.3. The webservice has a testRule method that accepts a String buf as input. For now, the only thing the webservice does is return a 'do nothing' string. This works fine:
When deployed the testpage generates the following SOAP message:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body xmlns:ns1="http://carrental/types/">
<ns1:testRuleElement>
<ns1:buf>my xml message</ns1:buf>
</ns1:testRuleElement>
</soap:Body>
</soap:Envelope>
The SOAP response is:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://carrental/types/"><env:Body><ns0:testRuleResponseElement><ns0:result>do nothing...</ns0:result></ns0:testRuleResponseElement></env:Body></env:Envelope>
In BPEL Designer I create a new asynchronous process ValidateBR, with a partnerlink for the webservice, based on the following WSDL file:
<definitions
name="Rent"
targetNamespace="http://carrental/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://carrental/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns0="http://carrental/types/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://carrental/types/"
elementFormDefault="qualified" xmlns:tns="http://carrental/types/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/">
<complexType name="testRule">
<sequence>
<element name="buf" type="string" nillable="true"/>
</sequence>
</complexType>
<complexType name="testRuleResponse">
<sequence>
<element name="result" type="string" nillable="true"/>
</sequence>
</complexType>
<complexType name="version">
<sequence/>
</complexType>
<complexType name="versionResponse">
<sequence>
<element name="result" type="string" nillable="true"/>
</sequence>
</complexType>
<element name="testRuleElement" type="tns:testRule"/>
<element name="testRuleResponseElement" type="tns:testRuleResponse"/>
<element name="versionElement" type="tns:version"/>
<element name="versionResponseElement" type="tns:versionResponse"/>
</schema>
</types>
<message name="Rent_testRule">
<part name="parameters" element="tns0:testRuleElement"/>
</message>
<message name="Rent_testRuleResponse">
<part name="parameters" element="tns0:testRuleResponseElement"/>
</message>
<message name="Rent_version">
<part name="parameters" element="tns0:versionElement"/>
</message>
<message name="Rent_versionResponse">
<part name="parameters" element="tns0:versionResponseElement"/>
</message>
<portType name="Rent">
<operation name="testRule">
<input message="tns:Rent_testRule"/>
<output message="tns:Rent_testRuleResponse"/>
</operation>
<operation name="version">
<input message="tns:Rent_version"/>
<output message="tns:Rent_versionResponse"/>
</operation>
</portType>
<binding name="RentSoapHttp" type="tns:Rent">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="testRule">
<soap:operation soapAction="http://carrental//testRule"/>
<input>
<soap:body use="literal" parts="parameters"/>
</input>
<output>
<soap:body use="literal" parts="parameters"/>
</output>
</operation>
<operation name="version">
<soap:operation soapAction="http://carrental//version"/>
<input>
<soap:body use="literal" parts="parameters"/>
</input>
<output>
<soap:body use="literal" parts="parameters"/>
</output>
</operation>
</binding>
<service name="Rent">
<port name="RentSoapHttpPort" binding="tns:RentSoapHttp">
<soap:address location="http://localhost:7780/Rules-rent-context-root/RentSoapHttpPort"/>
</port>
</service>
</definitions>
I defined the process variable inputVariable to be defined based on the carrental.xsd schema. I assign the inputVariable to the 'buf' parameter of the webservice as shown below in the ValidateBR.bpel

<process name="ValidateBR" targetNamespace="http://xmlns.oracle.com/ValidateBR" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:ns1="http://rules.oracle.com/carrental" xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns3="http://carrental/types/" xmlns:ns2="http://carrental/" xmlns:client="http://xmlns.oracle.com/ValidateBR" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
<partnerLinks>
<partnerLink name="client" partnerLinkType="client:ValidateBR" myRole="ValidateBRProvider" partnerRole="ValidateBRRequester"/>
<partnerLink name="CheckBR" partnerRole="Rent_Role" partnerLinkType="ns2:Rent_PL"/>
</partnerLinks>
<variables>
<variable name="inputVariable" messageType="client:ValidateBRRequestMessage"/>
<variable name="outputVariable" messageType="client:ValidateBRResponseMessage"/>
<variable name="InvokeValidateBR_testRule_InputVariable" messageType="ns2:Rent_testRule"/>
<variable name="InvokeValidateBR_testRule_OutputVariable" messageType="ns2:Rent_testRuleResponse"/>
</variables>
<sequence name="main">
<receive name="receiveInput" partnerLink="client" portType="client:ValidateBR" operation="initiate" variable="inputVariable" createInstance="yes"/>
<assign name="Assign_1">
<copy>
<from variable="inputVariable" part="payload" query="/ns1:repository"/>
<to variable="InvokeValidateBR_testRule_InputVariable" part="parameters" query="/ns3:testRuleElement/ns3:buf"/>
</copy>
</assign>
<invoke name="InvokeValidateBR" partnerLink="CheckBR" portType="ns2:Rent" operation="testRule" inputVariable="InvokeValidateBR_testRule_InputVariable" outputVariable="InvokeValidateBR_testRule_OutputVariable"/>
<invoke name="callbackClient" partnerLink="client" portType="client:ValidateBRCallback" operation="onResult" inputVariable="outputVariable"/>
</sequence>
</process>
When I deploy the process and initiate a testinstance from the BPEL console, the assign looks as follows:
<InvokeValidateBR_testRule_InputVariable>
<part name="parameters" >
<testRuleElement>
<buf>
<driver>
<driver-license-number>15-PS-FZ</driver-license-number>
<name>Rob de Haan</name>
<age>39</age>
<vehicle-type>Saab</vehicle-type>
<license-type>B</license-type>
<pre-convictions>0</pre-convictions>
<pre-accidents>0</pre-accidents>
<able-to-drive>true</able-to-drive>
</driver>
</buf>
</testRuleElement>
</part>
</InvokeValidateBR_testRule_InputVariable>
The InvokeValidateBR shows the following error:
<remoteFault>
<part name="code" >
<code>Client</code>
</part>
<part name="summary" >
<summary>when invoking endpointAddress 'http://localhost:7780/Rules-rent-context-root/RentSoapHttpPort', caught exception while handling request: deserialization error: unexpected XML reader state. expected: END but found: START: {http://rules.oracle.com/carrental}driver</summary>
</part>
<part name="detail" >
<detail>AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client faultSubcode: faultString: caught exception while handling request: deserialization error: unexpected XML reader state. expected: END but found: START: {http://rules.oracle.com/carrental}driver faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace:caught exception while handling request: deserialization error: unexpected XML reader state. expected: END but found: START: {http://rules.oracle.com/carrental}driver at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221) at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128) at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:226) at org.collaxa.thirdparty.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:645) at org.collaxa.thirdparty.apache.axis.Message.getSOAPEnvelope(Message.java:424) at org.collaxa.thirdparty.apache.axis.client.Call.invokeEngine(Call.java:2754) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:2715) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:1737) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeAXISMessaging(WSIFOperation_ApacheAxis.java:2113) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1611) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.executeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1083) at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:452) at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317) at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:188) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3408) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1836) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:166) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:252) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5438) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1217) at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:511) at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:335) at ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1796) at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125) at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70) at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86) at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123) at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755) at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186) at java.lang.Thread.run(Thread.java:534) {http://xml.apache.org/axis/}hostname:NL-GRH-L120981 </detail>
</part>
</remoteFault>
FYI: the webservice only contains a return "do nothing"
Question:
What is the proper way to assign an XML message to the web service?
Any help would be appreciated.
Rob
Message was edited by:
[email protected]

Hi,
Reading only is not possible..
I will be still more clear in my question this time..
I have deployed my bpel. My receiveInputVariable is of type xsd:string.
So when i run the bpel in my console, i will be asked to give input as string data.
So when i go to the XMLView, it will be like this.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Body xmlns:ns1="http://xmlns.oracle.com/Sabari_POC_Appln/DOM_Parser/ConvertToBLOB">
          <ns1:process>
               <ns1:input></ns1:input>
</ns1:process>
</soap:Body>
</soap:Envelope>
Now, i am going to give my input like this. --- which leads to error.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Body xmlns:ns1="http://xmlns.oracle.com/Sabari_POC_Appln/DOM_Parser/ConvertToBLOB">
          <ns1:process>
               <ns1:input>
*<?xml version="1.0" encoding="UTF-8"?>*
*<projects>*
*<project id = "BP001">*
*<name>Banking Project</name>*
*<start-date>Jan 10 1999</start-date>*
*<end-date>Jan 10 2003</end-date>*
*</project>*
*<project id = "TP001">*
*<name>Telecommunication Project</name>*
*<start-date>March 20 1999</start-date>*
*<end-date>July 30 2004</end-date>*
*</project>*
*<project id = "PP001">*
*<name>Portal Project</name>*
*<start-date>Dec 10 1998</start-date>*
*<end-date>March 10 2006</end-date>*
*</project>*
*</projects>*
</ns1:input>
</ns1:process>
</soap:Body>
</soap:Envelope>
This xml is not accepted as string input.. so kindly suggest me some other solution.
I also tried.. like.. making my receiveInputVariable of type xsd:anyType, it also dint help. same error occurred.
Thanks,
Sabarisri. N
Edited by: Sabarisri N on Jul 20, 2011 1:03 PM

Reading the XML message from Xi stored in XML format from a abap program.

Hi Gurus,
My requirement here is to read the data that will be coming from Xi from my custom abap program and updating 2 data base tables. The method is after the data mapping is done a class is generated in abap proxy in which a method is available. Inside the method i am writing the code for getting the Xi data stored as a payload message which can be seen in the transaction SXMB_MONI. My code is given below.
***begin code***
method ZII_PAYROLL_HEADER_IN~PAYROLL_HEADER_IN.
**** INSERT IMPLEMENTATION HERE **** ***
data: ln type i.
DATA: i_items TYPE TABLE OF ZPAYLOAD_WRAPPER_EMPLOYEE_REC3.
*DATA: wa_items type ZPAYLOAD_WRAPPER_EMPLOYEE_TAB5.
data: wa_items type ZPAYLOAD_WRAPPER_EMPLOYEE_REC3.
DATA:PERNR TYPE STRING.
*data: it_ZPAYLOAD_WRAPPER16 TYPE ZPAYLOAD_WRAPPER16.
I_ITEMS[] = INPUT-PAYLOAD_WRAPPER-BODY-XMLDOC-PAYROLL_PERIOD_OVERVIEW-EMPLOYEE_RECORD[].
*I_ITEMS = INPUT-payloadWrapper-Body-XMLDOC-PayrollPeriodOverview-EmployeeRecord.
describe table i_items[] lines ln.
endmethod.
**End code***
As per the logic the data stored in the XML message should be avaialble in INPUT-payloadWrapper-Body-XMLDOC-PayrollPeriodOverview-EmployeeRecord which i am assigning to a local internal table in the class.
But in my case there is no data coming in
INPUT-payloadWrapper-Body-XMLDOC-PayrollPeriodOverview-EmployeeRecord.
But i can see the data transffered from XI in the transaction SXMB_MONI->XML message->inbound message->payload.
Is there any way to read the data stored in the XML message in the transaction SXMB_MONI.
Also why the data is not coming in
INPUT-payloadWrapper-Body-XMLDOC-PayrollPeriodOverview-EmployeeRecord inside the class.
If there is any solution for this problem please post it.

You can use function module SXMB_GET_MESSAGE_PAYLOAD.
Code snippet:
DATA: ls_mast      TYPE sxmspmast,
      ls_msgkey    TYPE sxmsmkey,
      lv_bin_xml   TYPE xstring,
      lv_str_xml   TYPE string.
* select sxmspmast into ls_mast
ls_msgkey-msgid = ls_mast-msgguid.
ls_msgkey-pid    = 'RECEIVER'.
CALL FUNCTION 'SXMB_GET_MESSAGE_PAYLOAD'
    EXPORTING
      im_msgkey      = ls_msgkey
      im_archive     = ' '
      im_version     = ls_mast-vers
    IMPORTING
      ex_msg_bytes   = lv_bin_xml
    EXCEPTIONS
      not_authorized = 1
      no_message     = 2
      internal_error = 3
      no_payload     = 4
      OTHERS         = 5.
IF sy-subrc EQ 0.
      lv_str_xml = cl_soap_moni_helper=>convert_xstring_to_string( xstring_in = lv_bin_xml ).
ENDIF.

Is there any way in the SOA suite to reject XML messages over certain size?

I am working for a client at the moment and we are currently in the system test phase of the first SOA implementation project.
We have a process that is made externally available to third parties via an ESB service which is secured using the OWSM. The problem we are having is that the XML message schema has some elements that are unbounded meaning that potentially the messages could be submitted into our system of an unprocessable size. We have been testing with message of 10Mb which fail and 5Mb which have severe performance problems. We would like to be able to reject messages over a specified limit (3Mb for example) to ensure our service is not detrimentally affected by a single message.
Does anyone know of a way of checking a message size before processing it in either OWSM, ESB or BPEL processes?

I don't know your deployment details, but I would definitely try something easy and straightforward. If there is HTTP transport layer used, my first choice would be Apache HTTP Server.
http://httpd.apache.org/docs/2.0/mod/core.html#limitrequestbody
At least for WebLogic, there is very good Apache plugin.

Mapping entire XML message to a database table field

I receive a XML message from a topic. I want to store that entire XML message in database field of XMLType. My components are lined like this.
JMS Adapter (Consumer) ---> Mediator ---DBAdapter
My question is how will I use XSL tranformation in this case to put the XML message I receive to the XML type data field. Should I be using any other approach.
Regarsd
Thomas

have a look at this code for reference. Not sure what you mean my map the whole message. It should be such a matter of dragging the route element to the blob object of the DB adapter.
create or replace PROCEDURE INSERT_INBOUND_MESSAGE (
       p_ID       in out nocopy varchar2
    , p_Payload in out nocopy blob
    , p_Date     in date
    , p_Error   out varchar2
    , p_Status out varchar2)
IS
l_clob        CLOB;
l_dest_offset NUMBER          := 1;
l_src_offset NUMBER          := 1;
l_amount      INTEGER         := dbms_lob.lobmaxsize;
l_blob_csid   NUMBER          := dbms_lob.default_csid;
l_lang_ctx    INTEGER         := dbms_lob.default_lang_ctx;
l_warning     INTEGER;
l_length      BINARY_INTEGER;
l_error_text VARCHAR2(80);
BEGIN
p_Error := 'SUCCESS';
p_Status := 'S';
dbms_lob.createtemporary( lob_loc => l_clob
                          , cache   => TRUE
                          , dur     => dbms_lob.session);
dbms_lob.converttoclob ( l_clob
                          , p_Payload
                          , l_amount
                          , l_dest_offset
                          , l_src_offset
                          , l_blob_csid
                          , l_lang_ctx
                          , l_warning);
Begin
    Insert Into inbound_message values (p_ID, p_Payload, p_Date);
Exception
    When others Then
      p_Status := 'E';
      p_Error := SQLERRM;
End;
END INSERT_INBOUND_MESSAGE;
--EXIT

Multiple lines in a Output XML message

Hi all,
     I am currently implimenting a simple scenario of creating a file in a particular format using XI.The working scenario is that we get an XML message from BO which will be mapped to the required format of the file.But for testing we are using an hardcoded XML file as the incoming message to XI.
     But there is a problem I am facing. The incoming XML message will contain multiple information and this has to be mapped to a header information followed by items.Like for example I have a payment document which has paid some 5 invoices.The incoming XML message will have this information and what I need in the output is to have the invoice information in 5 different lines.
For eg - Assume I have the following structure for incoming message
REGUH
REGUP
....and so on
Here for every REGUH entry we can have mulitple REGUP and also we can have multiple REGUH.
Say my target structure is -
Header Info
Record Info
so for every REGUH and corresponding REGUP combination I will have a Header Info and Record Info.For the next REGUH and corresponding REGUP I will have another Header and Record Info.
     I tried testing this in message mapping by duplicating the node REGUH and REGUP but it does not work.I also tried by having the occurances as 1 to n on both sides.It did not seem to work.
Can you guys give some feedback on this.
Thanks..
Sandeep

Manish,
    Thanks for the information.But this was a simple case which works.But in my case I have something like -
one field in REGUH will appear once in the file while some other fields will appear multiple times.Also I have a lot other structures which are something like this.
I assume that occurence for both sides should be 1 to n.
But it does not seem to work for me.Its a bit complicated target structure.

Assemble components -xml message problem

Similar Messages

Maybe you are looking for