NAME SPACE CHANGING

Hi ,
i want to change the existed namespace .. is it possible to change the existed name space..because after created all the scenarios we got a new requirement to change the new name space for all the scenarios..
can any body tell the steps for changing the namespaces..
thanks
babu

Babu,
In my project also we have faced same problem.after developing almost objects of a interface..clients asked 4 the namespace change. thats the problem...with XI and PI...i dont know wheather PI 7.1 will having the option to copy whole namespace.....We have found the only possibility is to create a new namespace .And manually copy all the objects...into the new namespace...
u can copy directly Message interfaces...(u need not copy data type and Message type) and remember to check the option "With all dependency"..
then automatically data type and Message type will be copied...
u can't copy Interface mapping and Message mapping :(..
u have to do it agian.......
Regards
Biplab

Similar Messages

OBS WSDL Import - Name space is changing

Hi,
I am running with a strange issue while importing WSDL from the OSB console.
During the configuration, I did import WSDl which has name space like
<code before -->
xmlns:*soap*="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:*soap1*2="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:*wsdl*="http://schemas.xmlsoap.org/wsdl/"
<code after >
but when I export WSDL from proxy service, I see all the namespace are changing something like
xmlns:*WL5G3N5*="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:*WL5G3N6*="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:*WL5G3N0*="http://schemas.xmlsoap.org/wsdl/"
Service is working as expected but its always good to have code in standard format.
Can someone please advice me whats causing this issue ..?

Hi,
That's OSB normal behaviour, notice that the namespaces aren't changing, just the aliases... This shouldn't cause any problems and there's no option to change that behaviour as far as I know...
Cheers,
Vlad

Change HA Name Spaces from Different to Same

Hello,
At a new company and they have Active/Passive model with Different Name spaces almost identical to the example below. I would like to convert it to a Active/Passive model with the Same Name spaces. Other than changing DNS, the certificates,
and the name spaces on the passive site are there any other considerations I need to be aware of?
Thank you. And credit to Henrik Walther for the diagrams.
Current:
Proposed

Hi,
Based on my knowledge, if you want to change from different namespace to single namespace, you need to change two things, DNS records and certificates, as you mentioned above.
Best regards,
Belinda Ma
TechNet Community Support

I have a question about extracting pages. When I do the function, adobe saves the individual files as " file name space page number ", so the files look like this "filename 1.pdf", "filename 2.pdf", "filename 3.pdf". Without too many gory details, I a

I have a question about extracting pages. When I do the function, adobe saves the individual files as "<file name><space><page number>", so the files look like this "filename 1.pdf", "filename 2.pdf", "filename 3.pdf". Without too many gory details, I am using excel to concatenate some data to dynamically build a hyperlink to these extraced files. It casues me problems, however, for the space to be the the file name. Is there any way to change the default behavoir of this function to perhaps use a dash or underscore instead of a space?

No, you can't change the default naming scheme. You can do it yourself if you extract the pages using a script instead of using the built-in command.

Emails being blocked for name space mining

Hello All
Once of our clients email domain is blocked by Microsoft because it detected a name space mining attack coming from the public IP assigned to the client.
We have already reported this to MS support but without any luck. All they sent are a generic script based answer asking us to rectify the issue from our end but based on the information I have I’m not sure if we can get this rectified on our end.
Basically all this started when the client sent a mass email. They have been sending this mass email for the last 2-3 years but one this instance emails to several Hotmail users were not getting delivered and following is the start of the email delivery
process.
2014-01-29T22:44:08.843Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,2,192.168.0.5:27944,65.54.188.94:25,<,"220 BAY0-MC2-F42.Bay0.hotmail.com Sending unsolicited commercial or bulk e-mail to Microsoft's computer network is prohibited.
Other restrictions are found at http://privacy.microsoft.com/en-us/anti-spam.mspx. Wed, 29 Jan 2014 14:44:43 -0800 ",
2014-01-29T22:44:08.843Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,3,192.168.0.5:27944,65.54.188.94:25,>,EHLO client server.com,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,4,192.168.0.5:27944,65.54.188.94:25,<,250-BAY0-MC2-F42.Bay0.hotmail.com (3.19.0.77) Hello [Client IP],
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,5,192.168.0.5:27944,65.54.188.94:25,<,250-SIZE 36909875,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,6,192.168.0.5:27944,65.54.188.94:25,<,250-PIPELINING,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,7,192.168.0.5:27944,65.54.188.94:25,<,250-8bitmime,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,8,192.168.0.5:27944,65.54.188.94:25,<,250-BINARYMIME,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,9,192.168.0.5:27944,65.54.188.94:25,<,250-CHUNKING,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,10,192.168.0.5:27944,65.54.188.94:25,<,250-AUTH LOGIN,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,11,192.168.0.5:27944,65.54.188.94:25,<,250-AUTH=LOGIN,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,12,192.168.0.5:27944,65.54.188.94:25,<,250 OK,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,13,192.168.0.5:27944,65.54.188.94:25,*,18243,sending message
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,14,192.168.0.5:27944,65.54.188.94:25,>,MAIL FROM:<[email protected]> SIZE=534310,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,15,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,16,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,17,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,18,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,19,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,20,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,21,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,22,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,23,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,24,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,25,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,26,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,27,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,28,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:08.937Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,29,192.168.0.5:27944,65.54.188.94:25,>,RCPT TO:<[email protected]>,
2014-01-29T22:44:09.030Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,30,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] OK,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,31,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,32,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,33,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,34,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,35,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,36,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,37,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,38,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,39,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,40,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,41,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,42,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,43,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,44,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,45,192.168.0.5:27944,65.54.188.94:25,<,250 [email protected] ,
2014-01-29T22:44:09.311Z,Windows SBS Internet Send Client server,08D0D8C0D237FAC7,46,192.168.0.5:27944,65.54.188.94:25,>,BDAT 512633 LAST,
After the last of the line then the client exchange server has tried every 2 minutes for the next 2 days and eventually failed because MS blocked the IP addresses.
Microsoft is not providing us any information and asking us to repeatedly to resolve the issue at our end but I don’t know why the exchange server never managed to deliver the email messages because all those Hotmail email addresses are legitimate and live
email addresses.
What does BDAT * LAST means? This is the last SMTP command sent/received before client s exchange server started a new communication attempt.
What are the changes that we can do to the client server in order to avoid similar issues in the future?
Thanks
Dhanushka

Hi,
I am afraid you still need to contact MS support to fix this issue.
Thanks,
Simon Wu
TechNet Community Support

BPEL FTP Adapter name space

Hi Friends,
I have a bpel process which sends xml data over ftp. The name space in FTPed data looks as below:
"<?xml version = "1.0" encoding = "UTF-8" ?>
_+<Metadata xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://aiv-external.s3.org.com/UnboxMetadata.xsd" xmlns:tns="http://www.org.com/UnboxMetadata/v1" xmlns="http://www.org.com/UnboxMetadata/v1">+_
<tns:Movie><tns:PartnerName>ABC</tns:PartnerName><tns:UniqueID>1263456</tns:UniqueID>
</tns:Movie>"
However receive of ftpied data expect following (Please note change in sehmalocation:
" <?xml version = "1.0" encoding = "UTF-8" ?>
_+<Metadata xsi:schemaLocation="http://www.amazon.com/UnboxMetadata/v1 http://aiv-external.s3.amazonaws.com/UnboxMetadata.xsd"+_
_+xmlns="http://www.amazon.com/UnboxMetadata/v1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">+_
<Movie><PartnerName>ABC</PartnerName><UniqueID>1263456</UniqueID>
</Movie>"
Is i t possible to control/change schema location and get file in expected form?
Thanks,
Sachin.
Edited by: user10051771 on May 1, 2013 2:31 PM

Thanks Everybody for the prompt response .
1) What error does one get when trying to connect to FTP Sever which only support active mode
No Error , but no file transfer happens. SR and Bug Request for the same is already in place .
QUESTION
========
Does BPEL FTP Adapter supports active ftp mode (instead of passive).
ANSWER
======
No, FTP Adapter only supports passive mode. For that purpose there is an Enhancement Request
already, the Bug 6866124 - NEED SUPPORT FOR PASSIVE FTP ADAPTER AND CUSTOM FTP
COMMANDS :
1. The FTP Server needs to be active for the Adapter to work. So, both FTP Server and the FTP adapter must be active for it to work.
Also you only support PASSIVE mode in our FTP JCA adapter. ACTIVE mode is currently
considered bad practice and a security vulnerability.
But, we would require both ACTIVE and PASSIVE modes.
2. Custom commands are not supported. But, we need the samples for custom FTP Commands and support for it.
for example: quote site fixrecfm 90...

BUG - saving with both flash pro CS6 and CC causes library symbol names to change

Concise problem statement:
If you save with flash pro CC and then save with CS6, in the library panel, symbol names are changed.
Specifically, pipes | and trailing spaces ("|Divider", "Divider ") get replaced by escape sequences ("&#124Divider", "Divider&#032" ...) Ampersands & and number signs # also get replaced, such that symbol names grow exponentially if you continue to save with both flash pro CC and CS6 ("Divider&#032", "Divider&#038&#035032", "Divider&#038&#035038&#038&#035035032" ...) This makes it difficult to transition a team from CS6 to CC.
Sometimes, the original-name symbol remains, and an escaped-name symbol is also created. In this case, the children are removed from the original-name symbol, so it doesn't render anything to the screen; a mysterious, silent failure.
Steps to reproduce bug:
1. Create a library symbol named "|", save an xfl with flash pro CC, and close.
2. Open, save, and close with flash pro CS6.
3. Open, save, and close with flash pro CC.
Results:
A library symbol named "&#124".
Expected results:
A library symbol named "|".
I submitted this bug with the bug form, and also with adobe bugbase (in case it isn't obsolete) - I'm just trying to maximize my chances of getting a fix. Has anyone else encountered this bug?

Hi,
We are aware of this issue and its open for investigation internally. This issue is observed when you have certain special characters in your symbol names and try to open that file in Flash CS6. This happens due to a change in the way symbol naming is handled in Flash CC and in Flash CS 6.
As a workaround, request you to use only Underscore or Hyphen as special characters while naming symbols or library layers etc.
We shall update you as soon as this has been fixed.
Thanks,
Nipun

Webdynpro abap application name space.

hi guru,
i have created webdynpro abap iview for an application .
while running the application in se80 application->run .
its working fine .
where as in portal iview its not working ( i.e iview
trying to load ).if i change the name
of that application its working fine .
Is there any name space standard to create a application for
iview.
Regard's
Vivekananthan.s

Hi Vivek,
When you run the webdynpro application in application you can find the url generated as
http://ssecvpiv.corp.satyam.ad:8000/sap/bc/webdynpro/sap/zse_mis_reports say something like this then in portal we have an options to enter as sapnamespace component name
""""sap/zse_land_admin?sap-system-login-basic_auth=X&sap-client=040&sap-language=EN
here zse_land_admin is my componenet name and client number should be yuor client number just copy paste this u can run the application of the webdynpro abap into the portal.
Before this please make sure that you have done seetings in system administration (which register s your login details of yuor server ).
Hope it helps you .:)
Regards,
Sana.

Consume WSDL in ABAP proxy : Issue with name space

Hi,
I was trying to consume a WSDL in ABAP and I have created ABAP proxy using wizard in SE80 and also did the LPCONFIG.
While calling the proxy methods it is throughing the "authrization failed" error because of the following issue.I have successfully executed same WSDL from some third party tools with out error.only difference I have observed in SOAP request is, Third party tools passing all name spaces at envelope level but in ABAP proxy it is not passing all name spaces at envelope level.
1. SOAP genarated from WSDL in third party tool.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://schemas.xxxxx.com ">
<soap:Body>
 <tns:GetKMContent>
 <tns:request>
 <tns:clientID>1</tns:clientID>
 <tns:employeeID>307478</tns:employeeID>
 <tns:languageCountryCode>en-US</tns:languageCountryCode>
 <tns:wscVariables>
 <tns:empcountry>US</tns:empcountry>
 </tns:wscVariables>
 </tns:request>
 </tns:GetKMContent>
</soap:Body>
</soap:Envelope>
SOAP genarated from WSDL in ABAP proxy.
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header>
<n0:Trace xmlns:n0="http://www.sap.com/webas/630/soap/features/runtime/tracing/">
<TraceLevel xmlns="http://www.sap.com/webas/630/soap/features/runtime/tracing/">Full</TraceLevel>
</n0:Trace></soap-env:Header>
<soap-env:Body>
 <nr1:GetKMContent xmlns:nr1="http://schemas.xxxxx.com ">
 <nr1:request>
 <nr1:clientID>1</nr1:clientID>
 <nr1:employeeID>307478</nr1:employeeID>
 <nr1:languageCountryCode>en-US</nr1:languageCountryCode>
 <nr1:wscVariables>
 <nr1:empcountry>US</nr1:empcountry>
 </nr1:wscVariables>
 </nr1:request>
 </nr1:GetKMContent>
</soap-env:Body>
</soap-env:Envelope>
I was trying to use the SOAP genarated in ABAP proxy in thrid party tool and end up with same "authrization failed " error. If I move the name space nr1 from <nr1:GetKMContent xmlns:nr1="http://schemas.xxxxx.com "> GetKMContent node to soap-env:Envelope <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:nr1="http://schemas.xxxxx.com "> then it is working fine.
Question :Is there any way in ABAP proxy to pass name space at soap-env:Envelope level or is there any way to change the SOAP request once it is genarated from ABAP Proxy?. Is there any API to change SOAP information?
Thanks,

Hi Kavitha,
I am also facing the same issue.
Could you please share the solution if you have solved this.
Thanks,
Arun

Name space problem in a WSDL

hello
I have an RFC 2 WS sync message. in the reply, I seem to have a problem with my name space in the WSDL that I recieve. (I see 2 arrays with the same name in the response). I tryed to change the WSDL so it will be with one name space only but with out success. when I try to test the xml in the MM I I see it red in the tree.
I attached the wsdl and the xml response that I recieve. (there are 2 processBPRArr array in the reponse with the same name space even though it seems that I have in the WSDL different name spaces).
help will be appreciated.
my WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://CRMWorkQueue.ws.migdal.co.il" xmlns:intf="http://CRMWorkQueue.ws.migdal.co.il" xmlns:tns1="http://CRMWorkQueue.ws.migdal.co.il" xmlns:tns2="http://CRMWorkQueue.ws.migdal.co.il" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://CRMWorkQueue.ws.migdal.co.il">
 <wsdl:types>
 <schema elementFormDefault="qualified" targetNamespace="http://CRMWorkQueue.ws.migdal.co.il" xmlns="http://www.w3.org/2001/XMLSchema">
 <import namespace="http://beans.hafaka.scheme.migdal"/>
 <import namespace="http://out.beans.hafaka.scheme.migdal"/>
 <element name="getWorkQueue">
 <complexType>
 <sequence>
 <element name="in0" type="tns1:CRMWorkQueue"/>
 </sequence>
 </complexType>
 </element>
 <complexType name="ArrayOf_tns1_PaymentDetails">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:PaymentDetails"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns1_DOColl">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:DOColl"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns1_PSColl">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:PSColl"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns1_DGColl">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:DGColl"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns1_AttachedFile">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:AttachedFile"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns1_Party">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:Party"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns1_FundRequest">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:FundRequest"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns1_Relation">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:Relation"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns1_OptionalBenefit">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:OptionalBenefit"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns1_LifeParticipant">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:LifeParticipant"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns1_Coverage">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:Coverage"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns1_Policy">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:Policy"/>
 </sequence>
 </complexType>
 <element name="getWorkQueueResponse">
 <complexType>
 <sequence>
 <element name="getWorkQueueReturn" type="tns2:CRMWorkQueueNotify"/>
 </sequence>
 </complexType>
 </element>
 <complexType name="ArrayOf_tns2_PathNoteInfo">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:PathNoteInfo"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_ChangeEssence">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:ChangeEssence"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_xsd_string">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_HistoryState">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:HistoryState"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_WorkQueue2000">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:WorkQueue2000"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_ReceivedDocument">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:ReceivedDocument"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_ExpectedDocument">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:ExpectedDocument"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_NoteInfo">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:NoteInfo"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_ProcessBPR">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:ProcessBPR"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_Restriction">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:Restriction"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_Addition">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:Addition"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_Taarif">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:Taarif"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_ProductOffer">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:ProductOffer"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_Agreement">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:Agreement"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_FundDetails">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:FundDetails"/>
 </sequence>
 </complexType>
 <complexType name="ArrayOf_tns2_Funds">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns2:Funds"/>
 </sequence>
 </complexType>
 <complexType name="UserPswd">
 <sequence>
 <element name="pswd" minOccurs="0" nillable="true" type="xsd:string"/>
 <element name="cryptPswd" minOccurs="0" nillable="true" type="xsd:string"/>
 <element name="cryptType" minOccurs="0" nillable="true" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="UserAuthRequest">
 <sequence>
 <element name="userLoginName" minOccurs="0" nillable="true" type="xsd:string"/>
 <element name="userPswd" nillable="true" minOccurs="0" type="tns1:UserPswd"/>
 </sequence>
 </complexType>
 <complexType name="AgreementRequest">
 <sequence>
 <element name="organizationKey" minOccurs="0" nillable="true" type="xsd:string"/>
 <element name="all" minOccurs="0" type="xsd:int"/>
 <element name="carrierPartyId" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="agreementID" minOccurs="0" type="xsd:int"/>
 </sequence>
 </complexType>
 <complexType name="Organization">
 <sequence>
 <element name="directDeliveryByPost" minOccurs="0" type="xsd:int"/>
 <element name="natureCategory" minOccurs="0" type="xsd:int"/>
 <element name="policyHolderNumber" minOccurs="0" type="xsd:int"/>
 <element name="govtID" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="commissionPayeeType" minOccurs="0" type="xsd:int"/>
 <element name="salesManagerNum" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="organizationKey" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="residenceCounty" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="allowAppPaymentDetermining" minOccurs="0" type="xsd:int"/>
 <element name="contactPersonName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="orgCode" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="abbrName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="carrierPartyId" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="orgForm" minOccurs="0" type="xsd:int"/>
 <element name="publicCompanyIndicator" minOccurs="0" type="xsd:int"/>
 <element name="addressCountry" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="commissionPayeeID" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="estabDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
 <element name="signedAgreementInd" minOccurs="0" type="xsd:int"/>
 <element name="percentForSalesManager" minOccurs="0" type="xsd:double"/>
 <element name="fullName" nillable="true" minOccurs="0" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="Fax">
 <sequence>
 <element name="areaCode" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="dialNumber" nillable="true" minOccurs="0" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="PaymentDetails">
 <sequence>
 <element name="creditConfirmationID" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="cardOwnerID" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="creditCardType" minOccurs="0" type="xsd:int"/>
 <element name="bankBranchName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="accountNumber" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="paymentMethod" minOccurs="0" type="xsd:int"/>
 <element name="creditCardExpDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
 <element name="acctHolderName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="bankName" nillable="true" minOccurs="0" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="Person">
 <sequence>
 <element name="fatherName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="firstName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="primaryProfession" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="secondaryEmailAddress" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="primaryEmailAddress" minOccurs="0" nillable="true" type="xsd:string"/>
 <element name="personKey" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="passportCountry" minOccurs="0" type="xsd:int"/>
 <element name="birthDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
 <element name="secondaryProfessionCode" minOccurs="0" type="xsd:int"/>
 <element name="cellularNumber" minOccurs="0" type="xsd:int"/>
 <element name="confirmationDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
 <element name="englishFirstName" minOccurs="0" nillable="true" type="xsd:string"/>
 <element name="gender" minOccurs="0" type="xsd:int"/>
 <element name="occupationCode" minOccurs="0" type="xsd:int"/>
 <element name="lastName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="sendMailInd" minOccurs="0" type="xsd:int"/>
 <element name="proofOfAgeInd" minOccurs="0" type="xsd:int"/>
 <element name="carrierPartyId" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="selfEmployedDeclaration" minOccurs="0" type="xsd:int"/>
 <element name="marStat" minOccurs="0" type="xsd:int"/>
 <element name="smokerStat" minOccurs="0" type="xsd:int"/>
 <element name="primaryProfessionCode" minOccurs="0" type="xsd:int"/>
 <element name="issueDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
 <element name="secondaryProfession" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="englishLastName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="occupation" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="cellularAreaCode" minOccurs="0" type="xsd:int"/>
 <element name="declarationDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
 </sequence>
 </complexType>
 <complexType name="LS">
 <sequence>
 <element name="drugs_ls" minOccurs="0" type="xsd:int"/>
 </sequence>
 </complexType>
 <complexType name="DC">
 <sequence>
 <element name="name_dc" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="street_dc" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="first_name_dc" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="town_dc" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="id_no_dc" nillable="true" minOccurs="0" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="GH">
 <sequence>
 <element name="drinking_x_gh" minOccurs="0" type="xsd:int"/>
 <element name="drinking_from_year_gh" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="gen_questions19_gh" minOccurs="0" type="xsd:int"/>
 <element name="ever_smoked_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions20_gh" minOccurs="0" type="xsd:int"/>
 <element name="number_cigarettes_then_gh" minOccurs="0" type="xsd:int"/>
 <element name="height_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions2_gh" minOccurs="0" type="xsd:int"/>
 <element name="family_disorders_x_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions12_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions7_gh" minOccurs="0" type="xsd:int"/>
 <element name="number_cigarettes_now_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions17_gh" minOccurs="0" type="xsd:int"/>
 <element name="ever_drunk_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions23_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions5_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions10_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions15_gh" minOccurs="0" type="xsd:int"/>
 <element name="smoking_started_year_gh" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="smoking_x_gh" minOccurs="0" type="xsd:int"/>
 <element name="smoking_stopped_year_gh" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="gen_questions21_gh" minOccurs="0" type="xsd:int"/>
 <element name="weight_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions3_gh" minOccurs="0" type="xsd:int"/>
 <element name="heathy_able_to_work_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions13_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions8_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions18_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions1_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions24_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions6_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions11_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions16_gh" minOccurs="0" type="xsd:int"/>
 <element name="drinking_until_year_gh" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="gen_questions22_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions4_gh" minOccurs="0" type="xsd:int"/>
 <element name="hiv_infection_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions9_gh" minOccurs="0" type="xsd:int"/>
 <element name="gen_questions14_gh" minOccurs="0" type="xsd:int"/>
 </sequence>
 </complexType>
 <complexType name="PM">
 <sequence>
 <element name="pursuit_x_pm" minOccurs="0" type="xsd:int"/>
 <element name="occupation_hazards_x_pm" minOccurs="0" type="xsd:int"/>
 <element name="substandard_pm" minOccurs="0" type="xsd:int"/>
 </sequence>
 </complexType>
 <complexType name="DOColl">
 <sequence>
 <element name="treatment_year_do" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="start_month_do" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="has_fully_recovered_do" minOccurs="0" type="xsd:int"/>
 <element name="hospital_admission_do" minOccurs="0" type="xsd:int"/>
 <element name="end_year_do" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="several_times_do" minOccurs="0" type="xsd:int"/>
 <element name="type_of_treatment_do" minOccurs="0" type="xsd:int"/>
 <element name="disorder_name_do" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="consequences_do" minOccurs="0" type="xsd:int"/>
 <element name="start_year_do" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="treatment_month_do" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="right_left_do" minOccurs="0" type="xsd:int"/>
 <element name="code_do" minOccurs="0" type="xsd:int"/>
 <element name="end_month_do" nillable="true" minOccurs="0" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="PSColl">
 <sequence>
 <element name="pursuit_name_ps" minOccurs="0" nillable="true" type="xsd:string"/>
 <element name="code_ps" minOccurs="0" type="xsd:int"/>
 </sequence>
 </complexType>
 <complexType name="DGColl">
 <sequence>
 <element name="drug_name_dg" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="code_dg" minOccurs="0" type="xsd:int"/>
 <element name="quantity_dg" minOccurs="0" type="xsd:int"/>
 </sequence>
 </complexType>
 <complexType name="Questionnaire">
 <sequence>
 <element name="LS" nillable="true" minOccurs="0" type="tns1:LS"/>
 <element name="DC" nillable="true" minOccurs="0" type="tns1:DC"/>
 <element name="GH" nillable="true" minOccurs="0" type="tns1:GH"/>
 <element name="PM" nillable="true" minOccurs="0" type="tns1:PM"/>
 <element name="DOCollArr" nillable="true" minOccurs="0" type="impl:ArrayOf_tns1_DOColl"/>
 <element name="PSCollArr" minOccurs="0" nillable="true" type="impl:ArrayOf_tns1_PSColl"/>
 <element name="DGCollArr" minOccurs="0" nillable="true" type="impl:ArrayOf_tns1_DGColl"/>
 </sequence>
 </complexType>
 <complexType name="HealthStatement">
 <sequence>
 <element name="questionnaireStr" minOccurs="0" nillable="true" type="xsd:string"/>
 <element name="tkufatBituach" minOccurs="0" type="xsd:int"/>
 <element name="trdMiluiMevutach" nillable="true" minOccurs="0" type="xsd:dateTime"/>
 <element name="medicalPcntAddition" minOccurs="0" type="xsd:double"/>
 <element name="professionalPcntAddition" minOccurs="0" type="xsd:double"/>
 <element name="questionnaire" nillable="true" minOccurs="0" type="tns1:Questionnaire"/>
 <element name="maslulChitum" minOccurs="0" type="xsd:int"/>
 </sequence>
 </complexType>
 <complexType name="Phone">
 <sequence>
 <element name="areaCode" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="dialNumber" nillable="true" minOccurs="0" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="Address">
 <sequence>
 <element name="zip" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="buildNum" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="street" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="buildEnt" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="cityName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="cityCode" minOccurs="0" type="xsd:int"/>
 <element name="addressValidInd" minOccurs="0" type="xsd:int"/>
 <element name="POBox" minOccurs="0" type="xsd:int"/>
 <element name="buildLet" nillable="true" minOccurs="0" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="AttachedFile">
 <sequence>
 <element name="fileType" minOccurs="0" type="xsd:int"/>
 <element name="originalFileName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="fileContent" nillable="true" minOccurs="0" type="xsd:base64Binary"/>
 <element name="fileName" nillable="true" minOccurs="0" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="Party">
 <sequence>
 <element name="organization" nillable="true" minOccurs="0" type="tns1:Organization"/>
 <element name="partyResultCode" minOccurs="0" type="xsd:int"/>
 <element name="fax" nillable="true" minOccurs="0" type="tns1:Fax"/>
 <element name="paymentDetailsArr" nillable="true" minOccurs="0" type="impl:ArrayOf_tns1_PaymentDetails"/>
 <element name="person" nillable="true" minOccurs="0" type="tns1:Person"/>
 <element name="healthStatement" nillable="true" minOccurs="0" type="tns1:HealthStatement"/>
 <element name="phone" nillable="true" minOccurs="0" type="tns1:Phone"/>
 <element name="address" nillable="true" minOccurs="0" type="tns1:Address"/>
 <element name="attachedFileArr" nillable="true" minOccurs="0" type="impl:ArrayOf_tns1_AttachedFile"/>
 </sequence>
 </complexType>
 <complexType name="Parties">
 <sequence>
 <element name="partyArr" nillable="true" minOccurs="0" type="impl:ArrayOf_tns1_Party"/>
 </sequence>
 </complexType>
 <complexType name="FundRequest">
 <sequence>
 <element name="indexEndDate" minOccurs="0" nillable="true" type="xsd:dateTime"/>
 <element name="carrierPartyId" minOccurs="0" nillable="true" type="xsd:string"/>
 <element name="indexStartDate" minOccurs="0" nillable="true" type="xsd:dateTime"/>
 <element name="linkingType" type="xsd:int"/>
 </sequence>
 </complexType>
 <complexType name="Relation">
 <sequence>
 <element name="relationRoleCode" type="xsd:int"/>
 <element name="relationOriginatingObjectID" nillable="true" type="xsd:string"/>
 <element name="relationRelatedObjectID" nillable="true" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="KolRega">
 <sequence>
 <element name="providentFundType" type="xsd:int"/>
 <element name="providentFundNumber" type="xsd:double"/>
 </sequence>
 </complexType>
 <complexType name="BudgetSplit">
 <sequence>
 <element name="rule45" type="xsd:double"/>
 <element name="amount" type="xsd:double"/>
 <element name="pcntCompensation" type="xsd:double"/>
 <element name="pensionEmployer" type="xsd:double"/>
 <element name="rule47" type="xsd:double"/>
 <element name="pensionEmployee" type="xsd:double"/>
 </sequence>
 </complexType>
 <complexType name="Migdalor">
 <sequence>
 <element name="equityCourse" type="xsd:int"/>
 <element name="lifeEquity" type="xsd:double"/>
 <element name="compensationInvestmentCourse" type="xsd:int"/>
 <element name="constStipend" type="xsd:double"/>
 <element name="reduction" type="xsd:int"/>
 <element name="manLifeStipend" nillable="true" type="tns1:BudgetSplit"/>
 <element name="manEquity" nillable="true" type="tns1:BudgetSplit"/>
 <element name="manConstEquity" nillable="true" type="tns1:BudgetSplit"/>
 <element name="manStipend" nillable="true" type="tns1:BudgetSplit"/>
 <element name="lopping" type="xsd:int"/>
 <element name="constEquity" type="xsd:double"/>
 <element name="pcntEquity" type="xsd:double"/>
 <element name="salaryEquity" type="xsd:double"/>
 <element name="pensionLifeInvestmentCourse" type="xsd:int"/>
 <element name="lifeInvestmentCourse" type="xsd:int"/>
 <element name="stipend" type="xsd:double"/>
 <element name="equity" type="xsd:double"/>
 <element name="lifeCycleCompensationMigdalorForLife" type="xsd:int"/>
 <element name="lifeCyclePensionMigdalorForLife" type="xsd:int"/>
 <element name="lifeCycleCompensationMigdalor" type="xsd:int"/>
 <element name="pcntExpenseToSaving" type="xsd:double"/>
 <element name="manLifeEquity" nillable="true" type="tns1:BudgetSplit"/>
 <element name="paramInsuranceCourse" type="xsd:double"/>
 <element name="insuranceCourse" type="xsd:int"/>
 <element name="lifeStipend" type="xsd:double"/>
 <element name="pensionInvestmentCourse" type="xsd:int"/>
 <element name="investmentCourse" type="xsd:int"/>
 <element name="compensationLifeInvestmentCourse" type="xsd:int"/>
 <element name="manConstStipend" nillable="true" type="tns1:BudgetSplit"/>
 <element name="lifeCyclePensionMigdalor" type="xsd:int"/>
 </sequence>
 </complexType>
 <complexType name="OptionalBenefit">
 <sequence>
 <element name="optionalBenefitID" type="xsd:int"/>
 </sequence>
 </complexType>
 <complexType name="OptionalBenefits">
 <sequence>
 <element name="optionalBenefitArr" nillable="true" type="impl:ArrayOf_tns1_OptionalBenefit"/>
 </sequence>
 </complexType>
 <complexType name="Mitria">
 <sequence>
 <element name="additionalShalvaAmount" minOccurs="0" type="xsd:double"/>
 <element name="shalvaAmount" minOccurs="0" type="xsd:double"/>
 <element name="fundStartDate" minOccurs="0" nillable="true" type="xsd:dateTime"/>
 <element name="fund" minOccurs="0" type="xsd:int"/>
 <element name="restPensionAmount" minOccurs="0" type="xsd:double"/>
 <element name="disabilityPensionAmount" minOccurs="0" type="xsd:double"/>
 <element name="fundPremium" minOccurs="0" type="xsd:double"/>
 <element name="salaryEquity" minOccurs="0" type="xsd:double"/>
 <element name="equityCourse" minOccurs="0" type="xsd:int"/>
 <element name="pcntEquity" minOccurs="0" type="xsd:double"/>
 </sequence>
 </complexType>
 <complexType name="Product">
 <sequence>
 <element name="productCode" minOccurs="0" nillable="true" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="LifeParticipant">
 <sequence>
 <element name="commissionPayeeType" minOccurs="0" type="xsd:int"/>
 <element name="beneficiaryType" minOccurs="0" type="xsd:int"/>
 <element name="lifeParticipantRoleCode" minOccurs="0" type="xsd:int"/>
 <element name="lifeParticipantKey" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="lastUpdateDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
 <element name="beneficiaryRoleCode" minOccurs="0" type="xsd:int"/>
 <element name="participationPct" minOccurs="0" type="xsd:double"/>
 <element name="collectionPct" minOccurs="0" type="xsd:double"/>
 <element name="deathBenefitAmt" minOccurs="0" type="xsd:double"/>
 <element name="participantType" minOccurs="0" type="xsd:int"/>
 <element name="productionPct" minOccurs="0" type="xsd:double"/>
 </sequence>
 </complexType>
 <complexType name="LifeParticipants">
 <sequence>
 <element name="lifeParticipantArr" minOccurs="0" nillable="true" type="impl:ArrayOf_tns1_LifeParticipant"/>
 </sequence>
 </complexType>
 <complexType name="Coverage">
 <sequence>
 <element name="lifeParticipant" minOccurs="0" nillable="true" type="tns1:LifeParticipant"/>
 <element name="coverageAction" minOccurs="0" type="xsd:int"/>
 <element name="riskGroupName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="coverageName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="paymentPeriod" minOccurs="0" type="xsd:int"/>
 <element name="paymentCode" minOccurs="0" type="xsd:double"/>
 <element name="duration" minOccurs="0" type="xsd:int"/>
 <element name="msManotCollective" minOccurs="0" type="xsd:double"/>
 <element name="coverageSignDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
 <element name="pcntValue" minOccurs="0" type="xsd:double"/>
 <element name="policyValue" minOccurs="0" type="xsd:double"/>
 <element name="release" minOccurs="0" type="xsd:int"/>
 <element name="numSalaries" minOccurs="0" type="xsd:double"/>
 <element name="coverageKey" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="mandatoryIndicator" minOccurs="0" type="xsd:int"/>
 <element name="mix" minOccurs="0" type="xsd:double"/>
 </sequence>
 </complexType>
 <complexType name="Life">
 <sequence>
 <element name="coverageArr" minOccurs="0" nillable="true" type="impl:ArrayOf_tns1_Coverage"/>
 </sequence>
 </complexType>
 <complexType name="Pension">
 <sequence>
 <element name="transferFromAnotherFund" minOccurs="0" nillable="true" type="xsd:string"/>
 <element name="mainCover" minOccurs="0" type="xsd:int"/>
 <element name="riskDeduce" minOccurs="0" type="xsd:int"/>
 <element name="pcntPension" minOccurs="0" type="xsd:double"/>
 <element name="finalPaymentAge" minOccurs="0" type="xsd:double"/>
 <element name="solitudeDeclarDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
 <element name="insuranceCourse" minOccurs="0" type="xsd:int"/>
 <element name="retAge" minOccurs="0" type="xsd:int"/>
 <element name="orgFund" minOccurs="0" type="xsd:int"/>
 <element name="pcntDisability" minOccurs="0" type="xsd:double"/>
 <element name="pcntRest" minOccurs="0" type="xsd:double"/>
 <element name="solitudeStatus" minOccurs="0" type="xsd:int"/>
 <element name="qualificationPeriod" minOccurs="0" type="xsd:int"/>
 <element name="pensionAge" minOccurs="0" type="xsd:int"/>
 </sequence>
 </complexType>
 <complexType name="Risk">
 <sequence>
 <element name="loanType" minOccurs="0" type="xsd:int"/>
 <element name="interestCode" minOccurs="0" type="xsd:int"/>
 <element name="loanNumber" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="premiumCode" minOccurs="0" type="xsd:int"/>
 <element name="pcntInterest" minOccurs="0" type="xsd:double"/>
 </sequence>
 </complexType>
 <complexType name="Policy">
 <sequence>
 <element name="carrierCode" minOccurs="0" nillable="true" type="xsd:string"/>
 <element name="pcntPensionEmployee" minOccurs="0" type="xsd:double"/>
 <element name="printPolicyIndicator" minOccurs="0" type="xsd:int"/>
 <element name="policycarrierPartyID" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="replacingForm" minOccurs="0" type="xsd:int"/>
 <element name="proposalDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
 <element name="linkingMode" minOccurs="0" type="xsd:int"/>
 <element name="polNumber" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="acctHolderName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="compensationAgreement" minOccurs="0" type="xsd:int"/>
 <element name="numSalaries" minOccurs="0" type="xsd:double"/>
 <element name="riskDeduce" minOccurs="0" type="xsd:int"/>
 <element name="organizationKey" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="creditCardType" minOccurs="0" type="xsd:int"/>
 <element name="externalPolNumerator" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="agreementID" minOccurs="0" type="xsd:int"/>
 <element name="compensationInvestmentAuthority" minOccurs="0" type="xsd:int"/>
 <element name="kolRega" nillable="true" minOccurs="0" type="tns1:KolRega"/>
 <element name="contIndicator" minOccurs="0" type="xsd:int"/>
 <element name="bankBranchName" nillable="true" minOccurs="0" type="xsd:string"/>
 <element name="creditCardExpDate" nillable="true" minOccurs="0" type="xsd:dateTime"/>
 <element name="salary" minOccurs="0" type="xsd:double"/>
 <element name="policyValue" minOccurs="0" type="xsd:double"/>

any suggestions?
Thanks
Kfir

Xml name space for generated types

By default the autotype or the servicegen ant task seem to be creating a namespace
from the java package name (like java:com.ventaso.external.common) for xml mapping
of user defined java classes. Is there a way to change this to name space I want
? Specifying the targetnamespace doesn't seem to help.
Thanks,
Siva

The targetNamespace is for webservice and not for the user defined classes.
Sorry for the confusion
Ajay
"Ajay" <[email protected]> wrote in message
news:[email protected]..
There is a targetNamespace attribute in the autotyp ant task. But there
was a bug in 8.1. Contact the support for a patch.
The following mail explains that
This looks like a bug. There is an undocument, not officially
supported workaround: add the following java doc
to yours source code -
* @wlws:webservice targetNamespace="http://foo.bar"
public class MyService {
Details here:
http://www.manojc.com/tutorial/sample3/source2wsdd.html
Regards,
-manoj
http://manojc.com
"Mark Fine" <[email protected]> wrote in message
news:[email protected]..
The attribute targetNamespace (of the autotype task) doesn't seem to putany
information into the types file and later my deployment descriptor (viathe
source2wsdd task) contains an invalid targetNamespace attribute with a
http://tempuri.org:
eg.
<web-services>
<web-service name="IndexService"
targetNamespace="http://tempuri.org/"
uri="/IndexWebService">
I don't think this causes any problems but there should be a way tospecify
the namespace.
Has anyone else seen this is WLS8.1?
"Siva" <[email protected]> wrote in message
news:[email protected]..
By default the autotype or the servicegen ant task seem to be creating anamespace
from the java package name (like java:com.ventaso.external.common) for
xml
mapping
of user defined java classes. Is there a way to change this to name
space
I want
? Specifying the targetnamespace doesn't seem to help.
Thanks,
Siva

Global element declaration/definition of name: Duplicate name spaces

Hi,
I have two wsdls provided by a target systems. Both the wsdls are using same name space and few elements descriptions are different.
Obvisouly i am getting the Global element declaration/definition of name error.
I have to use the two wsdl with in the same bpel process and invoke them one after the other. My target system is not ready to make changes in thier wsdl to change name space as the product is generating these wsdls for them. All i have to do is in BPEL process only.
Is there any idea how can we resolve the namespace issue to continue using these wsdl in the same bpel process.
Only alternative i am seeing is, to have two bpel subprocess for each service and call these bpel processes from my parent bpel process.
Thanks

the cause of this error that you have different definition of the same element , so what you need to make sure that the element with the same name have the same definition on those wsdls.

Extract structure name space

Hi ,
When I try to create a datasource in RS02 transaction, by defalut SAP assigns a ZXXXXXX to extract structure. Is there way to change it to some other name space like YXXXXX or /MG/XXXX.
Is there a setting to change it.?
Appreciate your help.
Regards
Madhukar

Hi,
you can reserve a cusotmer namespace at SAP, so that you can create your datasources under e.g. /ABC/ for company ABC. Normally Z- and Y-names are reserved for customers. For objects beginning with other letters are for use by SAP developments.
Regards,
Juergen

Single name space in between Exchange 2010 and 2013

Hi,
In my current environment I have 2 Exchange 2010 servers with DAG no CAS NLB. I installed Exchange 2013 with 2 CAS with WNLB and 2 Mailboxes with DAG. The main requirement is to configure Single name space to access in between Exchange 2010 and Exchange
2013. On Exchange 2010 DAG there is a URL using is owa.domain.com and I also configured in Exchange 2013 all the virtual directories with this name owa.domain.com but having an issue that when I open explorer and use the owa.domain.com URL the user on Exchange
2013 gets their mailbox but user on Exchange 2010 gets error HTTP 403 blank page.
I observed that in Exchange Organization settings CAS settings one server OWA, ECP etc shows their internal external URL but the other server unable to open the OWA, ECP URL and give error message that "An IIS directory entry
couldn't be created. The error message is Access is denied. HResult = -2147024891"
Please guide how to resolve this issue and use the same name URL in Exchange 2010 and Exchange 2013
Thanks,

Hi,
See the below brief:
User will connect to mail.contoso.com as his namespace endpoint. CAS2013 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox version is 2010 and is located within the local AD site. CAS2013 will proxy the
request to an Exchange 2010 Client Access server which will retrieve the necessary data from the Exchange 2010 Mailbox server
Go through the full blog for better understanding of the redirection.
Client Connectivity with Exchange 2013
Hope you have changed your DNS records to direct connections only to your new Exchange 2013 server. You'll move the host names (for example, mail.contoso.com) users have been using to connect to Outlook Web Access, Autodiscover, and so on, from your
Exchange 2010 server to your Exchange 2013 server. When an Exchange 2010 user tries to open their mailbox, the Exchange 2013 server will proxy their request and communicate with the Exchange 2010 server on their behalf.
Configuring DNS includes the following:
Change the primary host names, such as mail.contoso.com, autodiscover.contoso.com, and owa.contoso.com (if used) to point to the external, publically-accessible, IP address of the Exchange 2013 Client Access server with your public DNS provider.
Change the primary host names, such as mail.contoso.com (or internal.contoso.com if you're using different internal host names) and owa.contoso.com (if used) to point to the internal machine name of the Exchange 2013 Client Access server on your internal
DNS servers.
NOTE- Go through the Exchange Deployemnt Assitant - Configure DNS Records section
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

What is SAP name space for different objects.

Hi Guys,
Kindly let me know the SAP name spaces for different objects.
Thanks

hi,
Naming Conventions in ABAP Objects
Global classes and interfaces that you create in the Class Builder are stored in the class library and administered by the R/3 Repository: they therefore have the same namespace as all other Repository objects (database tables, structures, data elements, and so on).
It is therefore necessary to have naming conventions for object types and their components and to use them uniformly within program development.
The following naming convention has been conceived for use within the SAP namespace:
If you do not observe the naming conventions for object types (classes and interfaces), conflicts will occur when the system creates persistent classes, since it will be unable to generate the necessary co-classes.
Namespace for Components
A single namespace within a class is shared by:
All components of the class itself (attributes, methods, events, constructors, interfaces, internal data types in the class, and aliases)
All public and protected components of the superclasses of the class.
Method implementation has a local namespace. The names of the local variables can obscure those of class components.
Naming Convention
The naming convention has been kept as general as possible to avoid adversely influencing the naming of objects.
General Remarks
When you choose names for development objects, you should:
Use English names
Use glossary terms when possible
For example, CL_COMPANY_CODE instead of BUKRS
In compound names, use the underscore character (_) as a separator. Since names are not case-sensitive, this is the only character that you can use to separate names.
Example: CL_COMPANY_CODE, CL_GENERAL_LEDGER_ACCOUNT
Names should describe the action, not the implementation of the action.
Example: PRINT_RECTANGLE, not RECTANGLE_TO_SPOOL
Conventions for Object Types
Class and interface names in the class library belong to the same namespace as data elements, tables, structures, and types. They are maintained centrally in table TADIR.
Class in the class library
CL_<class name>
The class name should be made up of singular nouns.
CL_COMPANY_CODE, CL_GENERAL_LEDGER_ACCOUNT
Interfaces in the class library
IF_<interface name>
The same naming convention applies to interfaces as to classes.
IF_STATUS_MANAGEMANT, IF_CHECKER
Local classes in programs
(recommendation)
LCL_<class name>
The class name should be made up of singular nouns.
LCL_TREE_MANAGEMENT
Local interfaces in programs
(recommendation)
LIF_<interface name>
The sane naming convention applies to interfaces as to classes.
LIF_PRINTER
Recommended naming conventions are not compulsory. However, if you use prefixes for these class and interface names, you should use those listed above.
Conventions for Components
Method name
<method name>
Method names should begin with a verb:
GET_STATUS, CREATE_ORDER, DETERMINE_PRICE
Events
<event name>
Event names should have the form
<noun>_<participle>:
BUTTON_PUSHED, COMPANY_CODE_CHANGED, BUSINESS_PARTNER_PRINTED
Local type definitions within a class
(recommendation)
TY_<type name>
TY_INTERNAL_TYPE, TY_TREE_LIST
Data definitions (variables)
<variable name>
When you name variables within a class (CLASS-DATA or DATA), avoid using verbs at the beginning of the name (to avoid conflicts with method names).
LINE_COUNT, MARK_PRINTED, MARK_CHANGED, STATUS
Data definitions (constants)
(recommendation)
CO_<constant name>
CO_MAX_LINE, CO_DEFAULT_STATUS, CO_DEFAULT_WIDTH, CO_MAX_ROWS
Recommended naming conventions are not compulsory. However, if you use prefixes for these class and interface names, you should use those listed above..
Concrete Method Descriptions
Attribute access
SET_<attribute name>, GET_<attribute name>
Methods that access attributes of any kind should be prefaced with GET_ or SET_.
GET_STATUS, SET_USE_COUNT
Event handler methods
ON_<event name>
Methods that handle events should begin with ON, followed by the name of the event that they handle.
ON_BUTTON_PUSHED, ON_BUSINESS_PARTNER_PRINTED
Methods that perform type conversions
AS_<new type>
AS_STRING, AS_ISOCODE
Methods that return a Boolean value
These methods may not return any exceptions.
Recommendation: Use SPACE and 'X' to represent false and true respectively.
IS_<adjective>
IS_OPEN, IS_EMPTY, IS_ACTIVE
Check methods
CHECK_<objective>
CHECK_AUTHORIZATION, CHECK_PROCESS_DATE
Local Conventions Within Methods
For parameters
The parameters are regarded from the point of view of the method that implements them:
IMPORTING parameters
IM_<parameter name>
EXPORTING parameters
EX_<parameter name>
CHANGING parameters
CH_<parameter name>
RESULT
RE_<result>
Using prefixes is NOT compulsory. However, if you do use them, use those listed above.
For exceptions
The following table contains a series of possible exception names, that can also be used generically (for example, NOT_FOUND could also be used as DATE_NOT_FOUND)
EXCEPTION
Meaning
ACTION_NOT_SUPPORTED
The requested action or function code is not supported.
CANCELLED
If a method uses a dialog to find out what has to be dome (for example, a list of choices), and the user chooses "Cancel", you can set this exception.
EXISTING
A new object that you want to create already exists in the database.
FAILED
The method could not be executed because of the current environment. This exception is intended for cases where the method cannot be executed because of variable system circumstances.
..._FAILED
Part of the method could not be completed because of the current environment. (OPEN_FAILED, CLOSE_FAILED, SELECTION_FAILED, AUTHORIZATION_FAILED)
FOREIGN_LOCK
Data is locked by another user.
INCONSISTENT
Object data in the database is inconsistent.
..._INCONSISTENT
The component data for of an object in the database is inconsistent.
INVALID
The object data entered is incorrect (for example, company code does not exist). Compare NOT_QUALIFIED.
..._INVALID
The component data entered for an object is incorrect. Compare NOT_QUALIFIED.
INTERNAL_ERROR
Last resort. Only use this exception if you cannot be more precise about the nature of the error.
NOT_AUTHORIZED
The user does not have the required authorization.
NOT_CUSTOMIZED
The object requested is not correctly customized.
..._NOT_CUSTOMIZED
The component of the requested object is not correctly customized.
NOT_FOUND
Unable to find the requested object.
..._NOT_FOUND
Unable to find component of the requested object.
NOT_QUALIFIED
The combination of input parameters is insufficient to run the method. Compare INVALID.
..._NOT_QUALIFIED
One parameter of the method is not qualified.
NUMBER_ERROR
Error assigning a number.
SYSTEM_ERROR
This exception is set if the Basis system returns an unexpected error message.
regards,
sudheer.

NAME SPACE CHANGING

Similar Messages

Maybe you are looking for