Hi PI Guys,

There is a requirement in my scenario IDOC(Packaging) to File with an unique number in one field and this IDOC Triggers every 15 min at ECC end.

For this I decided  to use an RFC look up which fetches an unique value from Z table in ECC. While triggering an IDOC the Ztable updated with unique value using FM(RFC lookup)and maps it in Message mapping to value pass Target field.

Now due to performance, I decided to use Number Range Objects(NRO) to generate Sequence Numbers, I configured the Receiver Channel, with module "localejbs/TransmissionNumberModule". Scenario runs fine but expected result is not there.

Please let me know to configure the Channel using the above module and how get this unique value.

Note : we are not using Counter in File channel because If PI Java stack Restarts again Counter starts from the first. To avoid this I am going with NRO Approach.

Rgds,

Kumar

Hello folks,

We are facing some major challenges during the TR movements in PI 7.31 dual stack environment,  from Development system >> Quality system>> Pre-Prod system. We tried doing both CTS+ TR movement and File system movement of the .tpz file but in both we are facing the below error:

1.       During CTS movement

2.       During TPZ movement:

Though, we have maintained the target for the development business system in the central SLD, still we are getting the above errors.  We did a round of the central SLD Cache refresh. Meanwhile, we also tried assigning the quality business system in the Integration Builder, from SLD, in the quality environment,  but there we were facing the below error:

We do have the business system maintained in the central SLD for all the environment, and the source and the target Business systems has been mapped correctly. Not sure where we are going wrong.

Kindly help with your expertise inputs in here. Thanks in advance.

Regards,

Nitin

Hello gurus,

I have an XML file for ASN.  I’m using Idoc DELIVRY05 and I have also to prepare the packaging.  But I have a problem in my mapping.  I’m not able to put the Number of the Packaging in the Segment E1EDL44 (@identifier 1 and @identifier 2).

In the segment E1EDL44, OrderNumber and OrderNumberItem are correctly mapped, but never the @identifier.

For the other Segment, no problem, the mapping is ok.

Can someone help me with this mapping.

Thanks a lot

Jean-Claude Onderbeke

Hi Experts,

We have recently installed PI 7.31 Java Only.

I would like to get a complete Post Installation guide or system Readiness Check to ensure all the components and services are up and running.

I have searched sdn community and couldn't find relevant docs on the above mentioned requirements.

I have checked following links...

http://scn.sap.com/thread/3215932

http://scn.sap.com/community/pi-and-soa-middleware/blog/2010/10/17/install-and-configure-pi-73-advanced-adapter-engine-extended

http://scn.sap.com/thread/2147641

Also would like to get few links/docs on the B2B AddOns implementation and testing in PI7.31 Java only

Please let me know.

Thanks!
Praveen.

Hi Experts,

I am new to SAP PI and have below queries on Queues

1. Is the processing of queues(Sender System->AE->IE) and inbound(SMQ2) IE->AE->Target System)is same for all scenarios (SAP to non-SAP and vie versa).
2. As I observed always SMQ2 queue is stuck and I never seen SMQ1 Queue stuck

Please clarify

Hi

I have a BPM scenario which has correlation setup for request response of aync interfaces. Can i setup the Exception handling in BPM to error the message and also through an alert once the correlation times out? If so how? Currenly i am trying out with a deadline branch where i have setup the timeout time eg 1 min. and am putting an exception control block within that and using a seperate exception branch to handle it. but the thing is its not even raising an exception. Please suggest.

Hi,

  I am trying to decrypt an encrypted customer record that has Last Name, First Name and Middle Name(All these 3 fields come encrypted).

I am getting this exception while decrypting the middle name. Tried sending trimmed encrypted value to the decryption module and also non-trimmed encrypted value to the decryption module but didn't yield any furitful result.

com.triversity.security.service.GeneralTWSecurityException: com.triversity.security.service.GeneralTWSecurityException: javax.crypto.BadPaddingException: Invalid PKCS#5 padding: not all padding bytes are equal!

I am using TW Security libraries for decryption provided by SAP.

Any pointers to this issue is truly appreciated.

Thanks,

Sarat

Hi Experts,

I am creating a Enhanced data Type and assigning an already created Data Type. But the newly created field is not not getting added to the node level.so the structure differs.

I am aware this Data Type Enhancement is used to add new fields for standard structures, just to give a try i am creating this scenario.

I need to create a new field under Request Node using Data Type Enhancement , but right now the new field gets created in Request node, but not under Request node. Please help me on how to achieve this.

Thanks,

Baskar

Dear All,

I am working in SAP PI 7.1

There is a huge quantity of messages stuck in the adapter engine i.e. more than 40 lacs. They are all JDBC messages. All the JDBC channels were stopped about a couple of months back and as a result this accumulation of messages.

Messages are in the following two status in the AE.

1. Error

2. Scheduled

I could easily cancel all the error messages but when I try to cancel the scheduled messages I am getting the error :

Could not execute action 'Cancel'; error: '{1}' Message: ProfileException in Method: CentralViewManager: processAction( IView, IViewData, UIPeriod, IAttribute, IAttribute ). Failed to process the action: CANCEL - general exception. Message: com.sap.engine.interfaces.messaging.api.message.MessageAccessException: Could not fail message. Reason: com.sap.engine.messaging.runtime.ClusterException: Could not trigger cluster event FAIL_MESSAGE_NOALERT for node 126412050. Reason: com.sap.engine.frame.cluster.message.RemoteClusterException: Service "com.sap.aii.af.ms.svc" on cluster element 126,412,050 thrown an exception in receiveWait(), invoked by a request by cluster element 118,105,450.

Any suggestions then please reply.

Thanks and Regards,

Rana Brata De

Hi Team,

I am facing issue with handling xml file. My XML file size is 9.61 KB and it is not processing. It shows below error in Communication channel Monitoring. When I deleted some fields and makes its size up to 6 kb, it runs correctly. Could you please suggest what could be error?

I am using SAP PI 7.1 and placing file as Test.xml at PI folder.

Error:

Error: java.io.IOException: org.xml.sax.SAXParseException: The element type "txtEmployer5" must be terminated by the matching end-tag "</txtEmployerDescription5>".

If I delete some fields and makes size 6.13 KB, even this field also does not have any error and it run successfully. I checked that it has all terminated end tag.

Thanks for your help!

Kumar

Hi all,

I am trying a develop a simple BPM scenario in NWDS 7.3 SP06 PAT0005 (EHP1) but while deploying it is getting failed with the following error:

Error Logs:

================================================

com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.

Reason: ASJ.dpl_dc.001085 Operation [deploy] of [demo.sap.com_dc_my_name_age] failed

          at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)

          at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)

          at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)

          at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:257)

          at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:135)

          at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$5$1.run(DcDeployAction.java:282)

          at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [demo.sap.com_dc_my_name_age] failed

          at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)

          at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)

          at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)

          at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)

          at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)

          at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)

          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)

Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] Operation [update] of [sdu id: [demo.sap.com_dc_my_name_age]

sdu file path: [/usr/sap/PO7/J00/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/232/demo.sap.com~dc_my_name_age.sda]

version status: [HIGHER]

deployment status: [Admitted]

description: []

] failed

          at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:100)

          at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:141)

          at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)

          at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)

          ... 8 more

Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [update] of [/usr/sap/PO7/J00/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/232/demo.sap.com~dc_my_name_age.sda] failed

          at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3365)

          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:487)

          at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:74)

          ... 11 more

Caused by: com.sap.engine.services.deploy.container.DeploymentException: Deploy Exception

          at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1274)

          at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.makeUpdate(ContentArchiveDeployContainer.java:342)

          at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:408)

          at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:477)

          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:182)

          at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:233)

          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)

          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)

          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1828)

          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:580)

          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:485)

          ... 12 more

Caused by: com.sap.glx.repository.exceptions.RuntimeRepositoryException: com.sap.glx.repository.exceptions.RuntimeRepositoryException: The runtime repository handler "Exception Handler" reported an exception while trying to add new versions for component demo.sap.com/dc_my_name_age

          at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:366)

          at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:261)

          at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:251)

          at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1265)

          ... 22 more

Caused by: com.sap.glx.repository.exceptions.RuntimeRepositoryException: The runtime repository handler "Exception Handler" reported an exception while trying to add new versions for component demo.sap.com/dc_my_name_age

          at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.handlerDistributionForDeployment(RuntimeRepositoryDeployManager.java:2568)

          at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deployArchive(RuntimeRepositoryDeployManager.java:1535)

          at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:339)

          ... 25 more

Caused by: com.sap.glx.repository.exceptions.HandlerException: com.sap.glx.deploy.api.DeployException: java.io.IOException: Could not instantiate network 0AA40CFB84D512F05A41CAD2EE96F1D7/DisplayNameAgeErrorEvent.

The given process model was built with a NWDS or development track of a higher version than the target runtime. Revision number of built process model: 4.3. Revision number of process runtime: 4.0. Please refer to SAP note 1600131 for details.

          at com.sap.glx.core.resource.impl.j2ee.rrdeploy.KernelHandlerImpl.addVersion(KernelHandlerImpl.java:98)

          at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.handlerDistributionForDeployment(RuntimeRepositoryDeployManager.java:2565)

          ... 27 more

Caused by: com.sap.glx.deploy.api.DeployException: java.io.IOException: Could not instantiate network 0AA40CFB84D512F05A41CAD2EE96F1D7/DisplayNameAgeErrorEvent.

The given process model was built with a NWDS or development track of a higher version than the target runtime. Revision number of built process model: 4.3. Revision number of process runtime: 4.0. Please refer to SAP note 1600131 for details.

          at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.deploy(DeployControllerImpl.java:450)

          at com.sap.glx.core.resource.impl.j2ee.rrdeploy.KernelHandlerImpl.addVersion(KernelHandlerImpl.java:92)

          ... 28 more

Caused by: java.io.IOException: Could not instantiate network 0AA40CFB84D512F05A41CAD2EE96F1D7/DisplayNameAgeErrorEvent.

The given process model was built with a NWDS or development track of a higher version than the target runtime. Revision number of built process model: 4.3. Revision number of process runtime: 4.0. Please refer to SAP note 1600131 for details.

          at com.sap.glx.core.kernel.trigger.config.CSVNetBuilder.parse(CSVNetBuilder.java:927)

          at com.sap.glx.core.kernel.trigger.config.CSVNetBuilder.parse(CSVNetBuilder.java:229)

          at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.deploy(DeployControllerImpl.java:420)

          ... 29 more

=========================================================================

Checked in OSS note 1600131 and it has stated that the compiler version and the runtime version of the BPMN has to be same.

Can anybody help me how to check those versions from NWDS and what appropriate actions need to be taken.

thanks

Sourav

Hi,

We are working on the standard scenario of master agreement integration from Sourcing to ECC via PI.It's a synchronous interface.Sourcing posts the data to PI over HTTP communication and PI sends this data to ECC via RFC connection.

When Sourcing team is pushing data over HTTP connection, its throwing an error "Sourcing was unable to publish Test.Server returned HTTP response code: 500 for url: <>.

However the data is getting received in PI. in PI, sxmb_moni, the sender component, interface and namespace is blank, wherein receiver component, interface and namespace fields are populated with values that of sender.and error is <SAP:Stack>Connection error during RFC communication (function module SIVAPRPR, destination , message )</SAP:Stack> .

Please help.

Thanks,

Ruchi

Hi Experts, I discovered a big hole in the security in ID<-->XI, is the connection between "ID" and "XI" is "HTTP", using any sniffer is possible view all XMLs of communication channels, including passwords configured.

How it works:

ID -> XI:

ID sends decrypted passwords and XI encrypts them and stores (can see encrypted in the rwm cache)

XI -> ID:

XI decrypt the passwords and sent to ID

Is there any solution to this problem?. (the good of this problem is that it is possible to retrieve forgotten password of CCs :D)

Something that could be improved is that the password will decrypt the ID....

Best Regards.

Hi all,

we have the following situation:

We use SAP PI for a RFC -> SAP PI -> SOAP scenario.

Once in a while our Basis needs to shut down the sender SAP system. It seems that the sender RFC channel looses registration on Gateway after some time. We get the following errors:

* I replaced the ip of our gateway host with x.x.x.x

As you can see, PI tries to reconnect, first within a short time frame of 512 seconds (last line), then with 1024 seconds, 2048 seconds and then every 3600 seconds. As our sender SAP system was down a long time, at some point, SAP PI stopped trying (last try was 20130505 15:15:18).

At this point, as soon as the sending SAP system will come available again, the scenario is broken and will not work as communication channel is in erroneous status.

Q1: I know I can fix this by stopping and starting the communication channel when sending SAP system is up, but is there any way to make this more robust like automatically registering on startup of the sender system?

Q2: If not, I probably could specify a longer retry period / higher retry count. How / where would I have to specify this?

Thanks and kind regards

Jens

Hello all,

In a fresh PI 7.1 installation I've developed a SOAP-> RFC scenario and it turned out messages from the soap side (outbound request and response) aren't being displayed in the TS SXI_MONI. I do see them in Runtime Workbench under Adapter Engine.

I'm not using Integrated Configuration.

Please, any suggestion to make them appear in SXI_MONI.

Hi

I have a BPM scenario which has correlation setup for an async interface for request response. Now my question is can i setup the Exception handling in BPM to error the message and also throw an alert once the correlation times out? If so, how? Currently i am trying out with a deadline branch where i have setup the timeout time eg 1 min. and am putting an exception control block within that and using a separate exception branch to handle it. But i see that the exception is not even being raised and so the BPM is failing gracefully with checkered flag. Please suggest.

Hi,

We are trying to use JDBC sender with Oracle dataguard with Oracle connection.

Once the main server is up - it is working, but as we switchover to the backup - it can't fetch rows anymore, and complains that the server is shutting down.

Please help.

Thanks

Hi all,

The JMS-for-Tibco-EMS-FAQ talks about a possibility to enable jms topics. however, I cannot find the item in my 7.10 system.

Apparently it is available in PI 7.31, as this version of the help describes the option.

Is this topic-enable-option backported to earlier versiosn of PI ?

If so, is there a note available ?

Much obliged for any input on this matter.

Regards,

Ronald van Aalst

Hi,

Seeburger version 2.1.3 is available in PI 7.11 system. It has to be upgraded to 2.1.5

Installation document of seeburger says we should uninstall some set of components if we are upgrading from a version prior to 2.1.

Questions:

Even for 2.1.5 update, should we uninstall all the existing 2.1.3 seeburger components

If we have to undeploy,should we do it for all the existing components (or) only a specific set of components to be undeployed?

any guide (or) links would be appreciated

Thanks a ton

Hi

I have a synchronous scenario where PI sends a request to a SOAP receiver channel and the response is both an xml message plus an xml attachment. However I get the error:

SOAP: call failed: java.io.IOException: invalid syntax in MIME header:   ; HTTP 200 OK

I selected Keep Attachments" in the SOAP receiver channel.

I can make it work from SOAPUI where I can see this HTTP content regarding the response:

Tue May 07 11:16:08 CEST 2013:DEBUG:>> "</urn:FileDownloadRequestEnvelope>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:>> " </soapenv:Body>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:>> "</soapenv:Envelope>"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "HTTP/1.1 200 OK[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "HTTP/1.1 200 OK[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Date: Tue, 07 May 2013 09:16:07 GMT[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Server: Apache-Coyote/1.1[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-Type: multipart/related; type="text/xml"; boundary=_NextPart_000_0002_01C3E1CC.3BB37320; start="<TIBCO_START_PART>"[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-Length: 3434599[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Connection: close[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "--_NextPart_000_0002_01C3E1CC.3BB37320  [\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-transfer-encoding: binary [\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-type: text/xml; charset=utf-8; [\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-id: <TIBCO_START_PART>[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<soapenv:Envelope xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/'><soapenv:Header/> <soapenv:Body>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<ns0:FileDownloadResponseEnvelope xmlns:ns0="urn:nl:edsn:service:filedownloadresponse:env:1">[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "    <ns0:EDSNBusinessDocumentHeader>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        <ns0:CreationTimestamp>2013-05-07T11:16:07.87+02:00</ns0:CreationTimestamp>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        <ns0:Destination>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:Receiver>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:ContactTypeIdentifier>DDQ_O</ns0:ContactTypeIdentifier>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:ReceiverID>xxxx</ns0:ReceiverID>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            </ns0:Receiver>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        </ns0:Destination>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        <ns0:Manifest>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:ManifestItem>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:MimeTypeQualifierCode>text/plain</ns0:MimeTypeQualifierCode>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:UniformResourceIdentifier>/u01/env/UAT08/data/UAT08/fileexchange/storeCB/ADC_Verplichting/f15030ea-d3fd-44a3-a8ad-57e4"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "06356ae0</ns0:UniformResourceIdentifier>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            </ns0:ManifestItem>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:NumberofItems>1</ns0:NumberofItems>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        </ns0:Manifest>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        <ns0:MessageID>295613d6-689c-430a-b973-511ca417cb90</ns0:MessageID>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        <ns0:Source>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:Authority/>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:ContactTypeIdentifier>EDSN</ns0:ContactTypeIdentifier>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:SenderID>xxx</ns0:SenderID>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        </ns0:Source>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "    </ns0:EDSNBusinessDocumentHeader>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "    <ns0:FileDownloadResponseContent>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        <ns0:FileDownloadResponse_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:FileID>f15030ea-d3fd-44a3-a8ad-57e406356ae0</ns0:FileID>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:FileSize>3431793</ns0:FileSize>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:FileType>ADC Verplichting</ns0:FileType>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:Group>ADC</ns0:Group>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:ReceivingEntity_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:OrganisationID>xxxx</ns0:OrganisationID>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:OrganisationName>xxxx</ns0:OrganisationName>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            </ns0:ReceivingEntity_EDSN"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "FileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:SendingEntity_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:OrganisationID>xxxx</ns0:OrganisationID>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:OrganisationName>EDSN</ns0:OrganisationName>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            </ns0:SendingEntity_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:Status>Afgemeld</ns0:Status>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            <ns0:UploadDate_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "                <ns0:DateTime>2013-03-07T18:25:37+01:00</ns0:DateTime>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "            </ns0:UploadDate_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "        </ns0:FileDownloadResponse_EDSNFileDetails>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "    </ns0:FileDownloadResponseContent>[\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "</ns0:FileDownloadResponseEnvelope></soapenv:Body></soapenv:Envelope>[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "--_NextPart_000_0002_01C3E1CC.3BB37320 [\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-transfer-encoding: "

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "binary [\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-type: application/octet-stream[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "Content-id: <Attachment>[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<?xml version="1.0" encoding="windows-1252"?>[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<ccma:ObligationSpecificationEnvelope xmlns:ccma="urn:nedu:edsn:data:obligationspecification:2:standard">[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<ccma:EDSNBusinessDocumentHeader>[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<ccma:CreationTimestamp>2013-03-07T18:01:19Z</ccma:CreationTimestamp>[\r][\n]"

Tue May 07 11:16:08 CEST 2013:DEBUG:<< "<ccma:MessageID>1507</ccma:MessageID>[\r][\n]"

Is the response valid or is something missing?

BR Mikael