Schema owner for ECC 5.0 IDES
Hi,
When I am trying to start ECC 5.0, the work processes are dying below is the error.
OS: Windows, DB: Oracle.
Now I'm connected to ORACLE
C *** ERROR => ORA-1403 when accessing table SAPUSER
[dbsloci.c 10114]
C Disconnecting from connection 0 ...
C Closing user session (con_hdl=0,svchp=0493EFF4,usrhp=07FC1E64)
C Now I'm disconnected from ORACLE
C Try to connect with default password
C Connecting as SAPR3/<pwd>@CC5 on connection 0 ...
C Starting user session (con_hdl=0,svchp=0493EFF4,srvhp=07FB9234,usrhp=07FC1E64)
C *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
[dboci.c 3721]
C *** ERROR => CONNECT failed with sql error '1017'
[dbsloci.c 9750]
B ***LOG BY2=> sql error 1017 performing CON [dbsh#1 @ 1200] [dbsh 1200 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dbsh#1 @ 1200] [dbsh 1200 ]
B ***LOG BY2=> sql error 1017 performing CON [dblink#1 @ 419] [dblink 0419 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dblink#1 @ 419] [dblink 0419 ]
M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c 1270]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 9377]
Based on these errors I have looked at Notes: 400241, 50088.
The problem is, even though schema owner is listed as SAPSID, why is SAPR3 being used to connect to Oracle.
I have tried creating the users using note 50088, but to no avail.
I have tried creating the users with schema owner as SAPSID. Above is the error message that I get.
When trying to create the users with owner as SAPR3, I get the below error,
ERROR at line 1:
ORA-00959: tablespace 'PSAPUSER1D' does not exist
ORA-06512: at line 114
Regards,
Vishi
Hi,
I have tried suggestions from you all of you, Thank you.
However the problem still persists. I am quite unable to figure out, why it is showing SAPR3 in wp trace.
Below are the error details from dev_w0 log, trans.log
dev_w0:
Logon as OPS$-user to get SAPR3's password
C Connecting as /@CC5 on connection 0 ...
C Attaching to DB Server CC5 (con_hdl=0,svchp=0493EFF4,svrhp=07FB9234)
C Starting user session (con_hdl=0,svchp=0493EFF4,srvhp=07FB9234,usrhp=07FC1E64)
C Now I'm connected to ORACLE
C *** ERROR => ORA-1403 when accessing table SAPUSER
[dbsloci.c 10114]
C Disconnecting from connection 0 ...
C Closing user session (con_hdl=0,svchp=0493EFF4,usrhp=07FC1E64)
C Now I'm disconnected from ORACLE
C Try to connect with default password
C Connecting as SAPR3/<pwd>@CC5 on connection 0 ...
C Starting user session (con_hdl=0,svchp=0493EFF4,srvhp=07FB9234,usrhp=07FC1E64)
C *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
[dboci.c 3721]
C *** ERROR => CONNECT failed with sql error '1017'
[dbsloci.c 9750]
B ***LOG BY2=> sql error 1017 performing CON [dbsh#1 @ 1200] [dbsh 1200 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dbsh#1 @ 1200] [dbsh 1200 ]
B ***LOG BY2=> sql error 1017 performing CON [dblink#1 @ 419] [dblink 0419 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dblink#1 @ 419] [dblink 0419 ]
M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c 1270]
M in_ThErrHandle: 1
Trans.log"
4 ETW000 [dev trc ,00000] Thu Nov 24 23:48:32 2011 80178 0.132260
4 ETW000 [dev trc ,00000] Assigning server context 02C0982C to service context 02C08C24
4 ETW000 57 0.132317
4 ETW000 [dev trc ,00000] Allocating user session handle 47 0.132364
4 ETW000 [dev trc ,00000] Starting user session (con_hdl=0,svchp=02C08C24,srvhp=02C0982C,usrhp=02C123F4)
4 ETW000 165 0.132529
4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000 6620 0.139149
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000 31 0.139180
4 ETW000 [dev trc ,00000] Try to connect with default password 73 0.139253
4 ETW000 [dev trc ,00000] Connecting as SAPCC5/<pwd>@CC5 on connection 0 ...
4 ETW000 27 0.139280
4 ETW000 [dev trc ,00000] Assigning username to user session 02C123F4 19 0.139299
4 ETW000 [dev trc ,00000] Assigning password to user session 02C123F4 28 0.139327
4 ETW000 [dev trc ,00000] Starting user session (con_hdl=0,svchp=02C08C24,srvhp=02C0982C,usrhp=02C123F4)
4 ETW000 31 0.139358
4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000 7326 0.146684
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000 31 0.146715
4 ETW000 [dblink ,00419] ***LOG BY2=>sql error 1017 performing CON [dblink#1 @ 419]
4 ETW000 141 0.146856
4 ETW000 [dblink ,00419] ***LOG BY0=>ORA-01017: invalid username/password; logon denied [dblink#1 @ 419]
4 ETW000 27 0.146883
2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'CC5'"
Should I go back looking at Note: 400241.
Regards,
Vishnu
Similar Messages
-
ALDSP 3.0 -- schema owner for stored procedure or SQL Statement
Using ALDSP, I have a need to create a physical service based on a stored procedure or a SQL statement. I am wondering what will happen when I move to another deployment environment where the schema owner changes. In our QA and Prod environments, we have a different schema owner for all tables in the application (the DBAs believe this prevents unwanted updates to a prod environment). DSP elegantly supports this for normal table- and view-based physical services by mapping schemas through the DSP console after deployment. Will I get the same type of mapping capability for stored procedures and SQL statements? I noticed that I can add a SQL-based function to a physical service...is there a way to pass in the physical table name from that data service to the procedure or SQL statement?
Thanks,
JeffSchema name substitution should work for stored procedures just like it does for tables. If it doesn't - report a bug.
You don't get any help for sql-statement based data services - dsp doesn't parse the sql provided. One thing you could do is use the default schema (following the user of your connection pool), and not specify the schema in your sql-statement. -
System Config for ECC 6.0 IDES
Hi all..
what's the system requirement for ecc 6.0 ides ...
okay byeHi,
Hardware Requirement for Central System
I. Minimum disk space
1. Database Software
1 GB (x64)
2 GB (IA64)
2. SAP system files (not including paging file)
5 GB (x64)
8 GB (IA64)
3. SAP database files (not including paging file)
76 GB
4. 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk
II. Minimum RAM 4GB
III. Paging file size 1 times RAM plus 8 GB
Hardware Requirements for a Distributed System
I. Minimum disk space
1. Database software
1 GB (x64)
2 GB (IA64)
2. Database instance (not including paging file)
76 GB
3. Central instance (not including paging file)
5 GB (x64)
8 GB (IA64)
4. In addition you require 4 GB (x64), or 8 GB (IA64) per additional platform.
5. Dialog instance (optional) (not including paging file)
2.5 GB (x64)
5 GB (IA64)
5. Temporary disk space for every required installation DVD that you have to copy to a local hard disk:
4.3GB
II. Minimum RAM 2 GB
III. Paging file size n Database instance
1.5 times RAM
Central instance:
1 times RAM plus 8 GB
Dialog instance (optional)
1 times RAM plus 8 GB
These all data you can find in the Installation Guide for ECC6.0
Thanks,
Nitesh Jain -
Hi All,
I would like to download ECC 6.0 IDES (ERP) for Oracle and SQL Server for Window. Which file does I need to download from Market Place?
Thank.Hi Dusit,
Follow this path.
http://service.sap.com/swdc --->SAP Software Distribution Center ---> Downloads -->Installations and Upgrades -->My Company's Application Components >SAP ERP> SAP ERP 2005 -->IDES-Version --> Windows --- SQL server.
Under this download the revelent media list as described in the installation guide.
You would need the following
Installation Master CD
Java component CDs
Export CDs
Kernel CD
Language CD
Please go through the installation guide before downloading the software to check the correct media list.
You need OSS ID for download.
Reward if helpfull.
Regards,
Imran
Edited by: Imran Khan on Feb 20, 2008 8:57 AM -
10g required schemas/owners for htmldb
Hi
I installed 10g recently and my question is:
In a new database, which schema owners are required to run htmldb. I imagine CTXSYS,MDSYS, WKSYS among others may be required. Can you confirm with me what owner accounts need to be present and unlocked for htmldb to operate?
Thanks as usual
BillBill,
Non of the schemas you list are required nor do they need to be unlocked for HTML DB to install or operate successfully.
Sergio -
Hi Experts,
I have installed IDES ECC 6 EHP6, to learn MDG, do i have to install NWBC separately or to activate from ERP? Please guide me
Thanks & Regards
Arunprasad NDid you activate the NWBC service? Check in transaction SICF.
Also, please make sure to review the NWBC installation & configuration guides. They are available on help.sap.com. Here is one: SAP NetWeaver Business Client - SAP Library -
SLD Client Settings for ECC 6.0 IDES system
Hello Friends
I want to configure the SLD Client settings in teh ECC 6.0.
Can you suggest me the correct guide or steps to follow in order to proceed??
Thanks in advance.
Regards
PoojaHi Pooja,
Please refer to the document available @ below mentioned link.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50924080-0627-2a10-2b89-8cb87b972fb1
Page number 45 onwards will be useful for you. Please read & then perform
Also for more details refer System Landscape Directory (SLD)
NOTE : This is only applicable , if you are configuring SLD for NW 7.0 underlying engine.
I hope the provided information will help. Please revert for further clarification/details.
Best Regards,
~~ Pradeep Bishnoi ~~ -
Database restore with same SID and different schema owner
Dear all,
I have quality system on HP-UX oracle platform which has been upgraded from 4.6C to ECC 5.0
and schema owner for the database is still SAPR3
I have installed new Test system with version ECC 5.0 with same SID and now i need to refresh its database with Data from QAS system ... owner at Test system is SAPC11 which is new installation ECC 5.0 and where SID is C11.
I need to know once i restore data what steps i need to carry out at Test system
i.e like change ENV settings from SAPC11 to SAPR3.
Please note SID is same on both hosts. and owner is different SAPR3 and SAPC11
Regards,
RRDear all ,
Thanks for your views . but i have already installed ECC 5.0 on
target machine with schema owner as default SAPC11 (sid)
Is there any other way out ... instead of doing reinstallation with schema owner SAPR3 / instead of doing Export-Import system copy method which again is as good as reinstallation.
I would like to have your views on following ,
when i will restore database from source to taget
al tables in target machine will be having owner as SAPR3 ( which came from source ) ...but my DB owner at Target machine is SAPC11 ( as far as ENV and all profiles are concerned ) .... cant i use SAPR3 user which got restored with backup of source to target to start my instance at Target machine... may be by changing ENV settings.
I really appreciate and thank you in adavance for sharing your views.
Regards,
RR -
Hi,
I have installed ECC 6.0 IDES system & wants to create a Zobject, But apparently system is asking for Developer access key.
As i know in 4.7 there is a unique key for developers. (36687663221261278694) & this is not working for ECC 6.0 IDES.
Is this key user specific in ECC 6.0 IDES ? Request to clarify
If there is any unique key to access , Request to please provide.Dear ,
you have to go market place and have to generate devloper key that will be different for different user and also installation no .
For IDES 4.7 same funda will follow you can not use that key for ECC 6.0.
Cheers
Anuj -
SELECT on XML DB Table works for Schema owner, not for Schema user
Hi,
We are working on Oracle 10.2.0.3 under HP-UX.
We get ORA-01031: Insufficient Privileges when trying to execute Query
on Oracle XMLDB Table by Schema User
Here are detailed steps:
1) We have 2 users: CDROWNER (Schema Owner)
CDRJAVA (Schema User)
2) login as CDROWNER and execute following:
3) Register 2 XSDs (Common is used by CorridorRate)
Common.xsd:
<?xml version="1.0" encoding="utf-8"?>
<!-- edited with XMLSpy v2008 sp1 (http://www.altova.com) by Kent Williamson (OOCL (USA) INC) -->
<xsd:schema xmlns="http://com.oocl.schema.tnm.agreementbuilder" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:tnm="http://com.oocl.schema.tnm" xmlns:common="http://com.oocl.schema.common" xmlns:fwd="http://com.oocl.frm.common.date.dto/" xmlns:customer="http://com.oocl.schema.customer" xmlns:eqm="http://com.oocl.schema.eqm" targetNamespace="http://com.oocl.schema.tnm.agreementbuilder" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true">
<xsd:complexType name="NamedCustomer_V1" xdb:SQLType="NAMED_CUSTOMER_T">
<xsd:annotation>
<xsd:documentation>Named customer for the quote</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="SAP_IDS" type="SAPIDCollection_V1" minOccurs="0" xdb:SQLName="SAP_IDS">
<xsd:annotation>
<xsd:documentation xml:lang="en">
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="BookingConditions" type="xsd:string" minOccurs="0" xdb:SQLName="BOOKING_CONDITIONS"/>
<xsd:element name="BLConditions" type="xsd:int" xdb:SQLName="BL_CONDITIONS"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Attachment_V1" xdb:SQLType="ATTACHMENT_T">
<xsd:annotation>
<xsd:documentation>Quote attachment</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Url" type="xsd:string" minOccurs="0" xdb:SQLName="ATTACH_URL"/>
<xsd:element name="Text" type="xsd:string" minOccurs="0" xdb:SQLName="ATTACH_TEXT"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="SentOfferingRecord_V1" xdb:SQLType="SENT_OFFERING_RECORD_T">
<xsd:annotation>
<xsd:documentation>Record of quote sending out to customer</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="TimeSent" type="xsd:string" minOccurs="0" xdb:SQLName="TIME_SENT"/>
<xsd:element name="UserName" type="xsd:string" minOccurs="0" xdb:SQLName="USER_NAME"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="QuoteFormatSettings_V1" xdb:SQLType="QUOTE_FMT_SETTINGS_T">
<xsd:annotation>
<xsd:documentation>Quote format setting specification</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="TemplateName" type="xsd:string" minOccurs="0" xdb:SQLName="TEMPLATE_NAME">
<xsd:annotation>
<xsd:documentation>predefined format template</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="OptionalContentIDs" type="StringWrapper_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="OPTIONAL_CONTENTS" xdb:SQLCollType="OPTIONAL_CONTENT_V">
<xsd:annotation>
<xsd:documentation>optional contents</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="StandardRemarkIDs" type="IDWrapper_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="STANDARD_REMARKS" xdb:SQLCollType="STANDARD_REMARK_V">
<xsd:annotation>
<xsd:documentation>standard remarks specified by each region/office</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="StandardDisclaimerID" type="ID_LongNumeric_V1" minOccurs="0" xdb:SQLName="STANDARD_DISCLAIMER">
<xsd:annotation>
<xsd:documentation>standard disclaimer specified by each region/office</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ShowSurcharges" type="ShowSurchargeType_V1" xdb:SQLName="SHOW_SURCHARGES">
<xsd:annotation>
<xsd:documentation>specifies how surcharges are shown in the offering document, can be show prepaid only, collect only or all</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="SurchargeCode_V1">
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
<xsd:simpleType name="ShowSurchargeType_V1">
<xsd:annotation>
<xsd:documentation>Indicator for quote to show prepaid, collect or all surcharges</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="Prepaid"/>
<xsd:enumeration value="Collect"/>
<xsd:enumeration value="All"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="StandardRemarkAndDisclaimer_V1" xdb:SQLType="STD_REMARK_AND_DISCLAIMER_T">
<xsd:annotation>
<xsd:documentation>Region specific standard remark and disclaimer</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Id" type="xsd:string" minOccurs="0" xdb:SQLName="STD_REMARK_ID"/>
<xsd:element name="Region" type="xsd:string" minOccurs="0" xdb:SQLName="STD_REMARK_REGION"/>
<xsd:element name="IsRemark" type="xsd:boolean" xdb:SQLName="IS_REMARK"/>
</xsd:sequence>
</xsd:complexType>
<!-- END Jianming Original XSD -->
<!-- -->
<!-- All Simple/Complex Types defined below have been copied from External XSD Files -->
<!-- -->
<!-- Complex Wrapper types are needed since 10.2 Oracle XMLDB does not support indexing unbounded simple types -->
<xsd:complexType name="GeoIDCollection_V1" xdb:SQLType="GEO_ID_COLLECTION_T">
<xsd:sequence>
<xsd:element name="IDWrappers" type="IDWrapper_V1" maxOccurs="unbounded" xdb:SQLName="GEO_ID_WRAPPERS" xdb:SQLCollType="GEO_ID_WRAPPER_V"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="IDWrapper_V1" xdb:SQLType="ID_WRAPPER_T">
<xsd:sequence>
<xsd:element name="Value" type="ID_LongNumeric_V1" xdb:SQLName="ID_VAL"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="OfficeCodeCollection_V1" xdb:SQLType="OFFICE_CODE_COLLECTION_T">
<xsd:sequence>
<xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="OFFICE_CODE_V"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="SAPIDCollection_V1" xdb:SQLType="SAP_ID_COLLECTION_T">
<xsd:sequence>
<xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="SAP_ID_V"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ServiceLoopCodeCollection_V1" xdb:SQLType="SERVICE_LOOP_CODE_COLLECTION_T">
<xsd:sequence>
<xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="SERVICE_LOOP_CODE_V"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="IncludedHSCodeCollection_V1" xdb:SQLType="INCLUDED_HS_CODE_COLLECTION_T">
<xsd:sequence>
<xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="INCLUDED_HS_CODE_V"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="StringWrapper_V1" xdb:SQLType="STRING_WRAPPER_T">
<xsd:sequence>
<xsd:element name="Value" xdb:SQLName="STR_VAL">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="256"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- Below copied from tnm.agreementbuilder:GuidelineRateReference_V1.xsd -->
<xsd:complexType name="GuidelineRateReference_V1">
<xsd:annotation>
<xsd:documentation>Represents a guideline rate containing an ocean rate and up to 4 inland/port arbitrary add-on rates</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="OutboundInlandRate1ID" type="ID_LongNumeric_V1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The first outbound inland rate. If present, the location of this rate is always the point of receipt. Otherwise the point of receipt is (one of) the Trunk origin(s). The over location must match with either OB2 Location or Trunk Origin (if OB2 is not present)</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="OutboundInlandRate2ID" type="ID_LongNumeric_V1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>An optional outbound inland rate. If present, the location must match with the over location of OB1 and the over location of this rate must match with the origin of the Trunk.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="BaseRateID" type="ID_LongNumeric_V1">
<xsd:annotation>
<xsd:documentation>The BaseRate = trunk / ocean rate.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="InboundInlandRate1ID" type="ID_LongNumeric_V1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The inbound rate connecting to the destination of the trunk. If there is only one inbound rate (IB2 is not present), then this rate will have the final destination. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="InboundInlandRate2ID" type="ID_LongNumeric_V1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>A second inbound rate which connects to the first inbound rate to arrive at a final destination.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- Below copied from tnm:AgreementID_V1.xsd -->
<xsd:simpleType name="AgreementID_V1">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20"/>
</xsd:restriction>
</xsd:simpleType>
<!-- Below copied from tnm:AgreementStatus_V1.xsd -->
<xsd:simpleType name="AgreementStatus_V1">
<xsd:annotation>
<xsd:documentation>Agreement Status, like filed, approve, terminated, amend</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20"/>
<xsd:enumeration value="File"/>
<xsd:enumeration value="Filed"/>
<xsd:enumeration value="Approve"/>
<xsd:enumeration value="Terminated"/>
<xsd:enumeration value="New"/>
<xsd:enumeration value="Incomplete"/>
<xsd:enumeration value="Amend"/>
</xsd:restriction>
</xsd:simpleType>
<!-- Below copied from tnm:AgreementType_V1.xsd -->
<xsd:simpleType name="AgreementType_V1">
<xsd:annotation>
<xsd:documentation>Agreement type, like CSO, SC, AB</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
<xsd:enumeration value="CSO">
<xsd:annotation>
<xsd:documentation>Customized Service Offering</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="RA">
<xsd:annotation>
<xsd:documentation>Rate Agreement</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SVC">
<xsd:annotation>
<xsd:documentation>Service Agreement</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SUR">
<xsd:annotation>
<xsd:documentation>Surcharge Agreement</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SC">
<xsd:annotation>
<xsd:documentation>Service Contract</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="TSO">
<xsd:annotation>
<xsd:documentation>Territorial Customized Service Offering</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="TSA">
<xsd:annotation>
<xsd:documentation>Territorial Service Agreement</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="AB">
<xsd:annotation>
<xsd:documentation>Agreement Builder</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<!-- Below copied from tnm:TradeTerm_V1.xsd -->
<xsd:simpleType name="TradeTerm_V1">
<xsd:annotation>
<xsd:documentation>Trade term</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
<xsd:enumeration value="FOB"/>
<xsd:enumeration value="CIF"/>
</xsd:restriction>
</xsd:simpleType>
<!-- MODIFIED ABDateTime_V1 to be a simpleType of xsd:dateTime for DB storage -->
<xsd:simpleType name="ABDateTime_V1">
<xsd:restriction base="xsd:dateTime"/>
</xsd:simpleType>
<!-- Below copied from common:PersonName_V1.xsd -->
<xsd:complexType name="PersonName_V1" xdb:SQLType="PERSON_NAME_T">
<xsd:sequence>
<xsd:element name="FirstName" minOccurs="0" xdb:SQLName="FIRST_NAME">
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LastName" minOccurs="0" xdb:SQLName="LAST_NAME">
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- Below copied from common:EmailAddress_V1.xsd -->
<xsd:complexType name="EmailAddress_V1" xdb:SQLType="EMAIL_ADDRESS_T">
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
A common Type for EmailAddress.
</xsd:documentation>
</xsd:annotation>
<xsd:element name="EmailID" type="xsd:string" xdb:SQLName="EMAIL_ID"/>
<xsd:element name="EmailType" type="EmailType_V1" default="Unspecified" xdb:SQLName="EMAIL_TYPE"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="EmailType_V1">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="Home"/>
<xsd:enumeration value="Work"/>
<xsd:enumeration value="Unspecified"/>
</xsd:restriction>
</xsd:simpleType>
<!-- Below copied from common:PhoneNumberType_V1.xsd.xsd -->
<xsd:simpleType name="PhoneNumberType_V1">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Type refers to the contact number type associated to the contact number.
May include: Business Phone/Fax, Home Phone/Fax, Mobile Phone, Pager, Telex or Unspecified.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="BusinessPhone"/>
<xsd:enumeration value="HomePhone"/>
<xsd:enumeration value="BusinessFax"/>
<xsd:enumeration value="HomeFax"/>
<xsd:enumeration value="MobilePhone"/>
<xsd:enumeration value="Pager"/>
<xsd:enumeration value="Telex"/>
<xsd:enumeration value="Unspecified"/>
</xsd:restriction>
</xsd:simpleType>
<!-- Below copied from common:PhoneNumber_V1.xsd -->
<xsd:complexType name="PhoneNumber_V1" xdb:SQLType="PHONE_NUMBER_T">
<xsd:annotation>
<xsd:documentation xml:lang="en">
PhoneNumber is a common type that defines generic structure of a phone number object.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="CountryCode" type="xsd:string" minOccurs="0" xdb:SQLName="COUNTRY_CODE">
<xsd:annotation>
<xsd:documentation xml:lang="en">
CountryCode holds on the country code value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="AreaCode" type="xsd:string" minOccurs="0" xdb:SQLName="AREA_CODE">
<xsd:annotation>
<xsd:documentation xml:lang="en">
AreaCode holds on the area code value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Number" type="xsd:string" xdb:SQLName="PHONE_NUMBER">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Number holds on the number value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Extension" type="xsd:string" minOccurs="0" xdb:SQLName="PHONE_EXTN">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Extension holds on the phone number extension, if applicable
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Type" type="PhoneNumberType_V1" default="Unspecified" xdb:SQLName="PHONE_NUM_TYPE">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Type refers to the contact number type associated to the contact number.
May include: Business Phone/Fax, Home Phone/Fax, Mobile Phone, Pager, Telex or Unspecified
Default value is Unspecified.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- Below copied from common:ContactInformation_V1.xsd -->
<xsd:complexType name="ContactInformation_V1" xdb:SQLType="CONTACT_INFORMATION_T">
<xsd:sequence>
<xsd:element name="Name" type="PersonName_V1" minOccurs="0" xdb:SQLName="CONTACT_NAME"/>
<xsd:element name="EmailAddresses" type="EmailAddress_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="EMAIL_ADDRESSES" xdb:SQLCollType="EMAIL_ADDRESS_V"/>
<xsd:element name="PhoneNumbers" type="PhoneNumber_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="PHONE_NUMBERS" xdb:SQLCollType="PHONE_NUMBER_V"/>
</xsd:sequence>
</xsd:complexType>
<!-- Below copied from common:CardinalDirection_V1.xsd -->
<xsd:simpleType name="CardinalDirectionName_V1">
<xsd:annotation>
<xsd:documentation>A list of voyage name direction.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="North"/>
<xsd:enumeration value="South"/>
<xsd:enumeration value="East"/>
<xsd:enumeration value="West"/>
</xsd:restriction>
</xsd:simpleType>
<!-- Below copied from common:CommonRestrictions_V1.xsd -->
<xsd:simpleType name="ID_LongNumeric_V1">
<xsd:annotation>
<xsd:documentation>Represents Identifier using long as the restriction - with max - 15 digits</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:long"/>
</xsd:simpleType>
<!-- Below copied from common:ServiceLoopCode_V1.xsd -->
<xsd:simpleType name="ServiceLoopCode_V1">
<xsd:annotation>
<xsd:documentation>A simple type that holds on to the service loop code.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
<!-- Below copied from common:Currency_V1.xsd -->
<xsd:simpleType name="CurrencyCode_V1">
<xsd:annotation>
<xsd:documentation>A 3 digit currency code string (like USD)</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:length value="3"/>
</xsd:restriction>
</xsd:simpleType>
<!-- Below copied from tnm:TariffCode_V1.xsd -->
<xsd:simpleType name="TariffCode_V1">
<xsd:annotation>
<xsd:documentation>tariff code that uniquely identify a tariff</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:length value="3"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="Global_UUID_V1">
<xsd:annotation>
<xsd:documentation>This is to represent the largest UUID format in the domain. Max. length is 36.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="36"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="UUID_V1">
<xsd:annotation>
<xsd:documentation>A system generated uuid in string format. Max. length is 20.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="Global_UUID_V1">
<xsd:maxLength value="20"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="CustomerContactRoleType_V1">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20"/>
<xsd:enumeration value="Accounting"/>
<xsd:enumeration value="Booking"/>
<xsd:enumeration value="Booking_CS"/>
<xsd:enumeration value="Documentation"/>
<xsd:enumeration value="General"/>
<xsd:enumeration value="Operations"/>
<xsd:enumeration value="Pricing"/>
<xsd:enumeration value="Sales"/>
<xsd:enumeration value="Sales_SMM"/>
<xsd:enumeration value="Warehouse"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="TradeCode_V1">
<xsd:annotation>
<xsd:documentation>A simple type that holds on to the trade code.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="ShipmentBoundCode_V1">
<xsd:annotation>
<xsd:documentation>A list of shipment bound code.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="IB"/>
<xsd:enumeration value="OB"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="CustomerContactSpecification_V1" xdb:SQLType="CUST_CONTACT_SPEC_T">
<xsd:sequence>
<xsd:element name="ContactSpecUUID" type="UUID_V1" xdb:SQLName="CONTACT_SPEC_UUID"/>
<xsd:element name="ContactUUID" type="UUID_V1" xdb:SQLName="CONTACT_UUID"/>
<xsd:element name="Role" type="CustomerContactRoleType_V1" xdb:SQLName="CONTACT_ROLE"/>
<xsd:element name="SAP_ID" type="SAP_ID_V1" minOccurs="0" xdb:SQLName="CUST_SAP_ID"/>
<xsd:element name="TradeCode" type="TradeCode_V1" minOccurs="0" xdb:SQLName="TRADE_CODE"/>
<xsd:element name="TradeLaneCode" type="TradeLaneCode_V1" minOccurs="0" xdb:SQLName="TRADE_LANE_CODE"/>
<xsd:element name="ServiceLoopCode" type="ServiceLoopCode_V1" minOccurs="0" xdb:SQLName="SERVICE_LOOP_CODE"/>
<xsd:element name="ShipmentBoundCode" type="ShipmentBoundCode_V1" minOccurs="0" xdb:SQLName="SHIPMENT_BOUND_CODE"/>
<xsd:element name="CommodityGroupCode" type="AlphaCode_V1" minOccurs="0" xdb:SQLName="COMMODITY_GROUP_CODE"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="CustomerContact_V1" xdb:SQLType="CUSTOMER_CONTACT_T">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This defines a contact for a Customer. A customer contact is someone to whom an OOCL sales representative communicates regarding business transactions between OOCL and the Customer.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="ContactUUID" type="UUID_V1" xdb:SQLName="CONTACT_UUID"/>
<xsd:element name="ContactInformation" type="ContactInformation_V1" xdb:SQLName="CONTACT_INFORMATION"/>
<xsd:element name="SAP_ID" type="SAP_ID_V1" minOccurs="0" xdb:SQLName="SAP_ID"/>
<xsd:element name="Title" minOccurs="0" xdb:SQLName="TITLE">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="JobTitle" minOccurs="0" xdb:SQLName="JOB_TITLE">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Department" minOccurs="0" xdb:SQLName="DEPARTMENT">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Specifications" type="CustomerContactSpecification_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="CUST_CONTACT_SPECS" xdb:SQLCollType="CUST_CONTACT_SPEC_V"/>
</xsd:sequence>
</xsd:complexType>
<!-- Below copied from tnm:TradeLaneCode_V1.xsd -->
<xsd:simpleType name="TradeLaneCode_V1">
<xsd:annotation>
<xsd:documentation>A simple type that holds on to the trade lane code.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="CompanyName_V1">
<xsd:annotation>
<xsd:documentation>Name of a Company
This is used to denote the information about an organization which may not be a Customer</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="105"/>
<xsd:minLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
<!-- Below copied from CorridorBaseRate_V1.xsd -->
<xsd:complexType name="CorridorBaseRate_V1" xdb:SQLType="CORRIDOR_BASE_RATE_T">
<xsd:annotation>
<xsd:documentation>Corridor base rate specifications</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="SizeType" type="xsd:string" minOccurs="0" xdb:SQLName="SIZE_TYPE">
<xsd:annotation>
<xsd:documentation>container sise and type that the rate is applicable</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Amount" type="xsd:decimal" minOccurs="0" xdb:SQLName="BASE_RATE_AMOUNT">
<xsd:annotation>
<xsd:documentation>charge amount</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Currency" type="CurrencyCode_V1" minOccurs="0" xdb:SQLName="BASE_RATE_CURRENCY">
<xsd:annotation>
<xsd:documentation>charge currency code</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="OfferType" minOccurs="0" xdb:SQLName="OFFER_TYPE">
<xsd:annotation>
<xsd:documentation>offer type: either OOCL offered or customer requested</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="IsSOC" type="xsd:boolean" minOccurs="0" xdb:SQLName="IS_SOC">
<xsd:annotation>
<xsd:documentation>indicator for shipper owned container</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EffectiveFrom" type="ABDateTime_V1" minOccurs="0" xdb:SQLName="EFFECTIVE_FROM" xdb:SQLType="TIMESTAMP">
<xsd:annotation>
<xsd:documentation>effectime start time of the rate</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EffectiveTo" type="ABDateTime_V1" minOccurs="0" xdb:SQLName="EFFECTIVE_TO" xdb:SQLType="TIMESTAMP">
<xsd:annotation>
<xsd:documentation>effectime end time of the rate</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TransitTime" type="xsd:string" minOccurs="0" xdb:SQLName="TRANSIT_TIME">
<xsd:annotation>
<xsd:documentation>transit time of shipment that the rate offered</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="SAP_ID_V1">
<xsd:annotation>
<xsd:documentation xml:lang="en">
SAP ID is the unique identifier for a given Customer in reference to SAP Application.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="ABShippingParty_V1" xdb:SQLType="AB_SHIPPING_PARTY_T">
<xsd:annotation>
<xsd:documentation>Customer's roles in a shipment, like shipper, consignee, etc</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="CustomerHolder" type="CustomerHolder_V1" xdb:SQLName="CUSTOMER_HOLDER"/>
<xsd:element name="ShippingRoleGroupID" type="ID_Integer_V1" minOccurs="0" xdb:SQLName="SHIPPING_ROLE_GROUP_ID"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="CustomerHolder_V1" xdb:SQLType="CUSTOMER_HOLDER_T">
<xsd:annotation>
<xsd:documentation>A place holder where a new customer was created or modified in agreement builder</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="SAP_ID" type="SAP_ID_V1" minOccurs="0" xdb:SQLName="SAP_ID">
<xsd:annotation>
<xsd:documentation>Customer SapID if it is an existing customer</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Name" type="CompanyName_V1" minOccurs="0" xdb:SQLName="COMPANY_NAME">
<xsd:annotation>
<xsd:documentation>New customer name that is created during agreement builder creation(customer does not exist in NewCPF)</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ModifiedContacts" type="CustomerContact_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="MODIFIED_CONTACTS" xdb:SQLCollType="MODIFIED_CONTACT_V"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ShippingPartyRoleGroup_V1" xdb:SQLType="SHIPPING_PARTY_ROLE_GROUP_T">
<xsd:annotation>
<xsd:documentation>All customer's shipping role in an agreement</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="GroupID" type="ID_Integer_V1" minOccurs="0" xdb:SQLName="GROUP_ID"/>
<xsd:element name="IsShipper" type="xsd:boolean" xdb:SQLName="IS_SHIPPER"/>
<xsd:element name="IsConsignee" type="xsd:boolean" xdb:SQLName="IS_CONSIGNEE"/>
<xsd:element name="IsForwarder" type="xsd:boolean" xdb:SQLName="IS_FORWARDER"/>
<xsd:element name="IsControlParty" type="xsd:boolean" xdb:SQLName="IS_CONTROL_PARTY"/>
<xsd:element name="IsSignatureParty" type="xsd:boolean" xdb:SQLName="IS_SIGNATURE_PARTY"/>
<xsd:element name="IsNotifyParty" type="xsd:boolean" xdb:SQLName="IS_NOTIFY_PARTY"/>
<xsd:element name="IsAssociate" type="xsd:boolean" xdb:SQLName="IS_ASSOCIATE"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="AlphaCode_V1">
<xsd:annotation>
<xsd:documentation>Code of a CommodityReportGroup. The Business Community refers to this 3 digit code as the AlphaCode
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="CargoNatureCode_V1">
<xsd:annotation>
<xsd:documentation>The classification code of cargo for special stowage arrangement</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
<xsd:enumeration value="AW">
<xsd:annotation>
<xsd:documentation>Awkward</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="DG">
<xsd:annotation>
<xsd:documentation>Dangerous</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GC">
<xsd:annotation>
<xsd:documentation>GeneralCargo</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="RF">
<xsd:annotation>
<xsd:documentation>Reefer</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="ID_Integer_V1">
<xsd:annotation>
<xsd:documentation>Represents Identifier using Integer as the restriction.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:int"/>
</xsd:simpleType>
<xsd:complexType name="CorridorVolume_V1" xdb:SQLType="CORRIDOR_VOLUME_T">
<xsd:annotation>
<xsd:documentation>Corridor volumns associated with corridor base rate</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="ID" type="xsd:int" xdb:SQLName="IDNUM">
<xsd:annotation>
<xsd:documentation>A numeric identifier which identifies a CorridorVolume only in the context of a Quote/Agreement</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="SizeType" type="xsd:string" minOccurs="0" xdb:SQLName="SIZE_TYPE">
<xsd:annotation>
<xsd:documentation>container sise and type that the rate is applicable</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Volume" type="ShipmentVolume_V1" minOccurs="0" xdb:SQLName="VOLUME">
<xsd:annotation>
<xsd:documentation>corridor rate volume specification</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="VolumePatterns" type="VolumePattern_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="VOLUME_PATTERNS" xdb:SQLCollType="VOLUME_PATTERN_V">
<xsd:annotation>
<xsd:documentation>detailed volume sepecification</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Basis" type="xsd:string" minOccurs="0" xdb:SQLName="BASIS"/>
<xsd:element name="IsConditionOfRate" type="xsd:boolean" xdb:SQLName="IS_CONDITION_OF_RATE">
<xsd:annotation>
<xsd:documentation>indicate if the volume sepecification is a condition of the corridor rate</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="IsShared" type="xsd:boolean" xdb:SQLName="IS_SHARED">
<xsd:annotation>
<xsd:documentation>Indicates if the volume group is shared by more than one corridor rate. When true, sizetype should be null</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="IsForEntireAgreement" type="xsd:boolean" xdb:SQLName="IS_FOR_AGREEMENT"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="VolumePattern_V1" xdb:SQLType="VOLUME_PATTERN_T">
<xsd:annotation>
<xsd:documentation>Agreement volume pattern</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Volume" type="ShipmentVolume_V1" minOccurs="0" xdb:SQLName="VOLUME">
<xsd:annotation>
<xsd:documentation>volume amount</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Period" type="xsd:string" minOccurs="0" xdb:SQLName="PERIOD">
<xsd:annotation>
<xsd:documentation>time period for the volume</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ShipmentVolume_V1" xdb:SQLType="SHIPMENT_VOLUME_T">
<xsd:annotation>
<xsd:documentation>A measurement for shipment volume</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Unit" type="xsd:string" minOccurs="0" xdb:SQLName="UNIT"/>
<xsd:element name="Value" type="xsd:decimal" minOccurs="0" xdb:SQLName="VALUE"/>
</xsd:sequence>
</xsd:complexType>
<!-- END Simple/Complex Types copied from External XSD Files -->
</xsd:schema>
CorridorRate.xsd
<?xml version="1.0" encoding="utf-8"?>
<!-- edited with XMLSpy v2007 rel. 3 (http://www.altova.com) by Auroprem Kandaswami (OOCL (USA) INC) -->
<xsd:schema xmlns="http://com.oocl.schema.tnm.agreementbuilder" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:tnm="http://com.oocl.schema.tnm" xmlns:common="http://com.oocl.schema.common" xmlns:fwd="http://com.oocl.frm.common.date.dto/" xmlns:customer="http://com.oocl.schema.customer" xmlns:eqm="http://com.oocl.schema.eqm" targetNamespace="http://com.oocl.schema.tnm.agreementbuilder" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true">
<xsd:include schemaLocation="AB_Common_V1_XMLDB.xsd"/>
<xsd:element name="CorridorRate" type="CorridorRate_V1" nillable="true" xdb:SQLName="CORRIDOR_RATE"/>
<!-- Below copied from common:DeliveryMode_V1.xsd -->
<xsd:simpleType name="DeliveryMode_V1">
<xsd:annotation>
<xsd:documentation>2 char string representing the delivery mode associated with the rate. YY for example is a Container Yard to Container Yard move, whereas DD is a door to door move.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
<xsd:minLength value="2"/>
<xsd:enumeration value="YY"/>
<xsd:enumeration value="YD"/>
<xsd:enumeration value="DY"/>
<xsd:enumeration value="DD"/>
</xsd:restriction>
</xsd:simpleType>
<!-- Below copied from PaymentTerm_V1.xsd -->
<xsd:simpleType name="PaymentTerm_V1">
<xsd:annotation>
<xsd:documentation>Payment term, either prepaid or collect</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
<xsd:enumeration value="Prepaid"/>
<xsd:enumeration value="Collect"/>
</xsd:restriction>
</xsd:simpleType>
<!-- Below copied from CorridorMetric_V1.xsd -->
<xsd:complexType name="CorridorMetric_V1" xdb:SQLType="CORRIDOR_METRIC_T">
<xsd:annotation>
<xsd:documentation>Corridor metrics associated with corridor base rate</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="SizeType" type="xsd:string" minOccurs="0" xdb:SQLName="SIZE_TYPE">
<xsd:annotation>
<xsd:documentation>container sise and type that the rate is applicable</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="VolumeSRG" type="xsd:string" minOccurs="0" xdb:SQLName="VOLUME_SRG">
<xsd:annotation>
<xsd:documentation>guideline volume</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="AgreementSRG" type="xsd:string" minOccurs="0" xdb:SQLName="AGREEMENT_SRG">
<xsd:annotation>
<xsd:documentation>ageeement volume</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ContributionNRPO" type="xsd:string" minOccurs="0" xdb:SQLName="CONTRIBUTION_NRPO">
<xsd:annotation>
<xsd:documentation>contribution matrix NRPO</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ContributionRPO" type="xsd:string" minOccurs="0" xdb:SQLName="CONTRIBUTION_RPO">
<xsd:annotation>
<xsd:documentation>contribution matrix RPO</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="AverageRate" type="xsd:string" minOccurs="0" xdb:SQLName="AVERAGE_RATE">Thanks so much for your response - Prefixing the call to the table within the package, with the schema owner does indeed solve the problem. Since this is a Production issue, i have implemented this fix in my customer's database.
However, I would still like this issue permanently resolved. The next time we send out updated package code, this will happen again (unless we then fix it again). I'd still like info from anyone on what exactly must be done to allow the call within the package to work without specifically pre-fixing the table's schema owner. It shouldn't be needed... The DB link is connecting via the same schema on database B that owns the table in question.
pre-fixing the schema owner is something we don't do in our sql statements, and this has worked fine for many of our cusomer's environments. We're only seeing this issue on one environment. -
To access PD Repository, why do we have to connect to the schema owner?
Hi
we use Oracle for PD repository. In order to connect to the repository, we create odbc connection to the repository schema owner. The question is, can we create a application schema user and provide read/write privileges to the repository and then create odbc connection to this application schema instead of repository schema?
thanksHi Krishna,
We create odbc connection to the repository schema owner. The question is, can we create a application schema user and provide read/write privileges to the repository and then create odbc connection to this application schema instead of repository schema? Yes
I suggest that you use the proxy rather than a direct connection. Search this topic in this forum.
If you decide to keep your idea here's how :
REPOSITORY_SCHEMA (OWNER SCHEMA):
GRANT SELECT, INSERT, UPDATE, DELETE ON EACH <PD TABLES> TO <APPLICATION_SCHEMA>
(PD tables usually begin by PM%, actually PD does not use VIEW, SEQUENCE objects)
On Application Schema : Create as many synonyms as there's table to go to the schema owner
Example : CREATE SYNONYM PMTEMP FOR <OWNER_SCHEMA.PMTEMP>
Ask to your Oracle DBA. It can do, he know how do.
Warning : When you do an update of PD you will have to check if the privileges are gone,if SAP has added new tables, etc.
I do not think it's a good idea to follow this path
Note : Your evaluation of my answer would be appreciated. Please mark the answer as "Helpful” or “Correct” if this is the case. Also If you consider that I have answered mark the discussion as “Answered,” so that other members can find the answer more easily. Before posting a new question members search SCN to see if it’s already been asked / answered. That’s the fastest way to get information. -
Creating Client 800 For ECC 6.0
Hi,
I have installed ECC 6.0 IDES in my PC,i able use 001 client with DDIC user name but iam unable to open 800 client.
Can you please tell me how to create client 800 in ECC.
Thanks in Advance,
Regards,
Balu.Hi
As you said client 800 is already created in defult
Tcode SCC4 check whether you have 800 client entry there,if you have then try to login with to 800 with sap/pass if it doesn't work then you need to delete sap and so that it will be recreated and you can login with sap*/pass
Login to the SQL prompt and execute the following command.
sqlplus"/as sysdba"
sql>delete from sapsr3.usr02 where mandt='800' and BNAME="SAP*";
where,
SAPSR3 is the schema.
mandt is the client
Bname is the user name
You also need to check parameter login/no_automatic_user_sapstar is set to 0 so you can logon as SAP* password pass,you can find this parameter at /usr/sap/SID/SYS/profiles in Default profile or Instance profile
als chek the below links
http://www.sap-img.com/basis/changing-the-default-password-for-sap-user.htm
http://www.sap-basis-abap.com/bc/forgot-password-for-user-id-sap-in-client-000.htm
http://help.sap.com/saphelp_45b/helpdata/en/52/671792439b11d1896f0000e8322d00/content.htm
Regards
Uday -
Win Server 2003 DC repair the Schema owner
Hello,
I prepare a new server on Win 2012 R2 64b to add to our DC, with 2 Win Server 2003 R2 32b.
At the begin, I view the configuration of the actuel DC / W2003, but I see some trouble :
- Dcdiag
Warning: CN=NTDS Settings\0ADEL:d96382dc-30df-44f2-9044-82acedf258b7,CN=SUSLAB,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vzad,DC=lab,DC=fr,DC=at,DC=com is the Schema Owner, but is deleted.
- netdom query fsmo
Schema owner susl.vzad.lab.fr.at.com
Domain role owner pluto.vzad.lab.fr.at.com
PDC role pluto.vzad.lab.fr.at.com
RID pool manager pluto.vzad.lab.fr.at.com
Infrastructure owner pluto.vzad.lab.fr.at.com
The command completed successfully.
I think "Schema owner" must be the same as "Domain role owner", your idea ?
Is it possible to undelete the line see with Dcdiag with Ntdsutil ??
Regards, StefWarning: CN=NTDS Settings\0ADEL:d96382dc-30df-44f2-9044-82acedf258b7,CN=SUSLAB,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vzad,DC=lab,DC=fr,DC=at,DC=com
is the Schema Owner, but is deleted.
That means that you have an object that was removed and that was not properly cleaned. Is the server SUSLAB still existing? If not then simply proceed with a metadata cleanup and seize the Schema Master FSMO role to another DC.
Metadata cleanup: https://technet.microsoft.com/en-us/library/cc816907%28v=ws.10%29.aspx
Seizing FSMO roles: https://support.microsoft.com/kb/255504?wa=wsignin1.0
If the server still exist then I would recommend demoting and promoting it again.
For the Best Practices when assigning FSMO roles, you can refer to them here: http://www.windowsdevcenter.com/pub/a/windows/2004/06/15/fsmo.html
"Rule 3: For simpler management, the Schema Master and Domain Naming Master can be on the same machine, which should also be a GC."
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile -
I wanted to delete a user (no longer with the company) from a database. The delete failed indicating that the user owned a schema.... I found his AD account (no longer in our system) was the schema owner of the "db_owner" schema.
(I plan to alter the owner to "db_owner" and then delete his account from the DB but am unsure of the consequences of this.)
Any idea how this could have happened or why there would even be a need for it to happen for that schema?
TIA,
edm2
P.S. sql 2008Hello ,
TAKE OWNERSHIP permission on the entity. If the new owner is not the user that is executing this statement, also requires either, 1) IMPERSONATE permission on the new owner if it is a user or login; or 2) if the new owner is a role, membership in the role,
or ALTER permission on the role; or 3) if the new owner is an application role, ALTER permission on the application role details on:
Transfer ownership
Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/ -
OPS$, Schema Owner and dbs_ora_schema env variable.
HI All.
Have a situation where we've copied a system from one location to another using an online backup. The database is up and running (open) and lookin good.
However, when I goto start SAP, I get a ORA-1403 and ORA-1017 error on startup. As best as I can tell, the OPS$ mechanism created for the base system (before the online restore) is using SAPSID as the owner. However, the schema owner from the database we used for the recovery is SAPR3.
Now when the system goes to logon, OPS$ is looking to fetch SAPSID as the schema owner, but the effective schema owner is SAPR3. Rerunning the oradbusr. sql script as per note 361641 does not change anything.
<b>Issue is related to the environment variable "dbs_ora_schema" - it is currently set to SAPSID, but I need to change it to SAPR3. Can someone offer the proper syntax to change this value in AIX 5.3?</b>
Thanks,
Tim
Thanks!!
Message was edited by:
Tim HildHello Tim,
What i apprehend is that the SAP<SCHEMA-ID> or the password for the same has changed. When u have copied the db of another SID the SAP<SCHEMA-ID> will be according to the earlier SID so it may required to be renamed as per the new SID and so also the naming services might have changed for which the listner may not work properly. Try to rename the SAP<SCHEMA-ID> and reset the password via brtools. The SQL wont work in case of changing the password of SAP<SCHEMA-ID> . First do it from SQL then reset the password again using Brtools.
Comparing tns.ora and listnr.ora files of both the systems will give u a fair idea on the prob.
In the sap server run BRTOLS from cmd prompt then proceed as follows
Brtools----->Choose Additional Functions--->Choose Change Password of DB user
Enter choice 2(Database User/Password)
In user prompt give sapc11 and in password prompt put the password u had changed earlier ie abc123.
Then enter c (for continue) u will be prompted for the new password
When u put the new password it wont be displayed in the prompt just type
Complete the entire guided process.
Hope this resolves your prob.
Regards.
Maybe you are looking for
-
Windows 7 won't recognize iPod Touch
I syncd my new iPod touch then downloaded aps. Now iTunes wont recognize my Ipod, how do I fix this?
-
Itunes 10.5 won't install on my Windows 7 64 bit.
Please Help ! Ive Tried Everything i can think of Whenever i try to update my itunes to 10.5 i get: Can Someone PLEASE PLEASE PLEASE help me solve this problem
-
Can anyone advise?. I would like to insert a text scroll down panel on my site rather than having to look at a load of text. If people want more information and read additiuonal text, enavling them to scroll and read. Can this be achieved with iweb?
-
Using a Seq Num for Multiple Objects in Oracle Forms Ver. 6i
I have a requirement to produce SEQNO for each course taken in my organization. There are 100 courses and each course has 20 people, so each course must start with a SEQNO of 1 with the last being 20. I need to cycle the SEQNO back to the value of 1
-
Biller Direct configuration for AR and AP
Hello, I have Biller Direct 6.0 installed and already configured XCM, but I would like to know if its possible to configure the application with Accounts Receivable and Accounts Payable at the same time to show bills from both? Thanks.