Quota agreement.
Hi All,
I need one help regarding Quota agreement, I need to know is there any set up for net price in quota file.
Thanks,
Hi,
Quota Arrangement is used for source determination/ distribution. You can't specify net price in Quota Arrangement.
However, you can manintain a vendor inforecord wherein you can specify the net price and the same vendor can be entered in the quota arrangement.
By this way, you can fetch the net price thru info record.
Or else, if your concern is only to fetch the net price, that can be done by means of an inforecord alone. No need of Quota.
Antony
Edited by: Antony anburaj on Jun 12, 2010 9:15 AM
Similar Messages
-
Hi,
Is there any standard report in Quota agreement.
Thanks,
ZafinaHi,
Use t.code:MEQM Quota Arrangement for Material
For more check the link:
Source determination,Quota Arrangement Process
Regards,
Biju K -
FM for "Maintain Quota Agreement - MEQ1"
Hi,
Is there any FM or BAPI for creating / updating Quota Agreement?
Best Regards,
Phani Kumar. SPlease check the function modules below , it might help you
ME_UPDATE_QUOTA
ME_UPDATE_QUOTA_PD
"ME_UPDATE_QUOTA_BATCH
"ME_UPDATE_REQUISITION_QUOTA
"ME_UPDATE_SCHEDULES_QUOTA
"ME_UPDATE_PLAF_QUOTA
"ME_UPDATE_QUOTA_REORG
"ME_UPDATE_AFPO_QUOTA
"ME_UPDATE_QUOTA_SCHEDULES
"ME_UPDATE_QUOTA_FROM_REQ
"ME_UPDATE_QUOTA_DIALOG
Regards
Satish Boguda -
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. -
I downloaded itunes this morning and when I try to open it, the user agreement pops up and when I hit "agree" I get an error message saying it's on a locked disk or I dont have write privaliges. I have tried 1. running as an administartor 2 changing settings, file location to C:\. I am so frustrated HELP!!!
Hi lvdmerwe!
I have two articles here for you that should be able to help you troubleshoot this issue further:
Trouble adding music to iTunes library or importing audio CD
http://support.apple.com/kb/ts1387
iTunes: Missing folder or incorrect permissions may prevent authorization
http://support.apple.com/kb/ts1277
Take care, and thanks for visiting the Apple Support Communities.
-Braden -
I created a term set called 'Document Category' that has 10 different terms (e.g. Quote, Agreement, Diagram, etc.) that describe the types of documents users save into our main document library. I then created 10 different Content Types, each with it's
own template, so, from the doc library, users can click Files > New, and choose the appropriate content type to create a document. I want to be able to sort in the library using a custom column I created, called 'Document Category', that links to the 'Document
Category' managed metadata term set. When users create a new document based on one of the content types, I want the 'Document Category' field automatically populated in the Document Information Panel with the correct term. My problem is that I can't find a
way of getting each individual content type to default to it's matching term. I can set the custom column to use a default value (e.g. Quote) so it comes up automatically filled in for the 'Quote' content type. Because I'm linking the 'Agreement' content type
to the same custom column, though, it obviously then defaults to 'Quote', too. I was hoping to have a different term linked to each content type. Does anyone know how to do this? Any help would be greatly appreciated! -PeteHi,
According to your post, my understanding is that you wanted to set the 'Document Category' field automatically.
I recommend to create SharePoint 2010 Platform workflow and then set an empty Managed Metadata column using the following format: Term Name| Unique Identifier based on the item content type.
You can create workflow as below and start the workflow automatically when an item is created:
Thank you for your understanding.
Best Regards,
Linda Li
Linda Li
TechNet Community Support -
All,
is it possible to create a list with pre-defined to be ordered materials (for example) per month over a 1 year period?
So the purchase requests will be created automatically based on the order dates and the quantities in this list.
I looked in the forecasting but the situation described above is not automatic ordering based on seasons or something like that, it is already known how much is to be ordered.
Thanks a lot!
MarkHi Yawar,
this appears to be a good solution however, these quantities to be delivered are fixed per period per material but the split over the suppliers which deliver these materials can differ.
You have like 1000 pcs to be delivered and 10% has to go to supplier A, 20% to supplier B and 70% to supplier C (quota split) based on the contractprices. The next period 2000pcs with the same quota.
Based on these quota agreements 3 Purch reqs should be generated per period 1 for 100, 1 for 200 and 1 for 700 at the different suppliers.
How do I fit in the schedule line agreements here?
I understand that you can say, 'since you know period 1 = 1000pcs, 100 for sup A, 200 for B and 700 for C you can foresee the orders to be delevired by the suppliers up front so why bothering about the MRP way'. However its not clear to me how to solve it with schedule lines.....
Thanks! -
IPhone High Score Data File/Sort Oddities
Hello all.
I am working on an iPhone game which is nearly complete but I am having trouble with the following high score sort/write code. I am aiming to keep up to 10 scores, sorted from highest to lowest obviously.
The code creates a new data file with the current score added as first entry if there is no existing data file (and this works), or it creates a data file with the current score as first entry if a data file exists but is empty for some reason (and this works as well), or it adds the current score to a data file of existing scores if it is within the top ten or there are less than ten entries (this is where it gets odd).
If there is one existing score in the data file, the current score is added and sorted properly. If there are two scores in the data file, the application crashes BUT the data file shows the current score was correctly added and sorted to the existing scores. If there are three existing scores, the application crashes and the data file remains unchanged.
I have been over the logic many times and tried many different variations of the logic structure to no avail. I suspect it is something simple but I've been staring at it too long to see. Any ideas?
If there is a better way to display the code/formatting on the forum, please let me know. It doesn't look pretty this way and there must be a way to make it more readable here. I tried to manually format it some to help. The code follows (score variable is brought in from another class but works properly in my tests). At the end I have repeated an isolated snippet of the code where I think the problem occurs.
*CODE START:*
int i, ii;
struct highscoreentry {
NSString *name;
int highScore;
struct highscoreentry structArray(10);
FILE *fin = fopen("highscore.dat", "rb");
if (fin != NULL) { //if the data file exists proceed here
for (i = 0; i < 10; i++) {
if (fscanf(fin, "%s %d\n", structArray(i).name, &structArray(i).highScore) != EOF) { //if data exists for this iteration proceed
ii = i; //ii will be the last entry of existing data
for (i = ii; i > -1; i--) { //will begin at last entry and work up the list of scores to sort
if (score > structArray(i).highScore) { //if current score is higher than recoded score, recorded score moves down 1 place
structArray(i + 1) = structArray(i);
structArray(i).name = (NSString *)"JESSE";
structArray(i).highScore = score;
if (i == ii && ii < 9) //if there are less than 10 entries we will add another for our new entry
ii = ii + 1;
else if (score < structArray(i).highScore && i == ii) { //if current score is less than last recorded score it becomes new last entry
structArray(i + 1).name = (NSString *)"JESSE";
structArray(i + 1).highScore = score;
if (ii < 9)
ii = ii + 1;
fclose(fin);
if (fin == NULL) { //if the data file does not exist prepare data for new file
ii = 0; //will be used to limit write iterations to this single new entry
structArray(0).name = (NSString *)"JESSE";
structArray(0).highScore = score;
FILE *fout;
fout = fopen("highscore.dat", "wb"); //should create/rewrite data file from scratch
for (i = 0; i <= ii; i++) {
fprintf(fout, "%s %d\n", structArray(i).name, structArray(i).highScore);
fclose(fout);
*CODE END*
As far as I can tell by commenting out different portions of the code, the problem appears to be somewhere in here:
*CODE START:*
if (fin != NULL) { //if the data file exists proceed here
for (i = 0; i < 10; i++) {
if (fscanf(fin, "%s %d\n", structArray(i).name, &structArray(i).highScore) != EOF) { //if data exists for this iteration proceed
*CODE END*
...but it baffles me that this works with one structure in the data file, crashes with two structures in the data file but correctly processes/sorts them and writes the file properly, and crashes with three structures in the data file without doing any additional work.
Jesse Widener
www.artandstructure.comActually I've found online material to be adequately, and sometimes more than adequately, elucidating in learning the language. When I decided to take a stab at this I spent about 40 hours of my spare time the first week reading 2 or 3 different "takes" on the C/C++/Objective C language in addition to Apple's docs on their implementation along with the iPhone SDK. As I mentioned, I've thus far found the language quite clear and concise. I began my application the second week and this is the first time in 7 weeks of coding where I've felt the need to ask assistance. Every other problem I've solved, leaving no errors, warnings or leaks in my software and accomplishing every task I've set to this point.
I find reading several different "takes" on a subject helps fill out an understanding from different perspectives. In this case, one perspective might lead the reader to believe or misunderstand the full use/context of a particular syntax, while reading from multiple sources can show the same syntax used in different contexts, broadening the understanding of its use, and that understanding can be user further to interpolate uses in a variety of situations.
I am new to C/C++/Objective C and the iPhone SDK, but I am not new to programming. It may have been some time (other than hand-coding my website the last few years) and my language experience may be limited to BASIC, HTML, PHP and Javascript, but from my view learning a new language is relatively easy once you know one...even if it is BASIC. The general logic structure remains the same. The overall software design concept remans essentially the same. Both are going to use variables, arrays, subroutines, memory allocation/management, input and output of data, runtime logic, etc. I am 80-90% sure I know exactly how I want to attack a coding problem every time...I just need to know how to "say it in C".
I don't remember when I first started coding, but I know by age 7 I wrote a karaoke style "Happy Birthday" for my great aunt with music playing through a Commodore 16 via "beeps" figuring the particular vibrations per second of the speaker (the hertz values) and durations for each note in time and pitch perfectly along with "lyrics" printed to screen with the music. To me, learning C is like learning a new foreign language. I took 2 years of French in high school and had to study at it but aced it nonetheless. I then opted to take Spanish but after a semester I opted to stop because the pacing was too slow. Learning Spanish after learning French was a piece of cake. They are in the same general language family and the syntax construction is very similar. I only needed the raw data of the words to fit to the rules I already knew. I didn't need to learn the same rules a second time.
The C/Objective C language seems no more complicated than it need be, which is to say it seems simple in doing what it needs to do and I am impressed with that simplicity thus far. I am also impressed with Apple's implementation with regard to the iPhone. Being able to provide music via 4-5 lines of code using AVAudioPlayer is transcendental compared to "beeping" every note monophonically.
Apple's explanations are very clear and concise. It is just, sometimes their examples are sparse or too narrow in scope to get a rounded context. However, their docs are very good and there is a wealth of information here on the net. My biggest complaint with Apple's docs really stems from the fact they seem to want to shove Interface Builder at everything and provide the code to do so but leave the reader stranded if the reader would rather stay within XCode exclusively and do more programmatically rather than leave that much "behind the curtain" work to Interface Builder...but it is a minor complaint.
On pointers...I do understand the use of pointers, perhaps not to the nth degree as I am just starting out, but the concept makes sense to me. I understand they are not "content" but a memory address location of the "content". I also understand why pointing to a location which is undefined or unprotected is damaging to whatever may be in that location already and to the data being pointed since it can be inadvertently overwritten my some other memory using item.
{quote}No. The (i < 9) condition is critical. Writing to structArray[10] will crash, since structArray[9] is the end of the array. In practice such a crash might not happen right away, though. If our program's data allocation actually ended at the end of the array, the crash would be immediate. But what usually happens when we write past the end of an array is that the beginning of some other data is overwritten.{quote}
I need to slap my forehead on this one. I know better than that. I don't know why I missed that. Too many late nights I suppose.
{quote}(NSString*) is called a type cast in that context.{quote}
Yes, which is why I used it to deal with the incompatible type error I thought I had at that point, but I shouldn't have assumed by appeasing the compiler I was necessarily solving the problem.
{quote} The best I can do for now is to caution that an enquiring mind, like all virtues, can be taken too far. I think it's important to compromise and copy good models sometimes. This isn't just to avoid reinventing the wheel. Sometimes it's good to remember we only have a limited time on Earth.{quote}
Agreed...and I don't expect to understand every nuance the first time around. I expect to at least understand how each successful line of code works in its context, but I imagine some processes will take a few times through before it "clicks" how it works in a greater context than its own, and I am all right with that. I also understand deadlines are deadlines whether they be software development or otherwise and a broad eye needs to be kept to remaining on the track forward.
Anyway, off to my day job.
Thank you again...I began reading up on NSDictionary and NSUserDefaults last night. Will post soon.
Jesse Widener
www.artandstructure.com -
Thanks Toshiba for the Froyo update for the AC100. Bring back the AC100 Forum, please.
Don't give up on this kind of product.
Some have complained that the keyboard layout has changed after the update. Use CTRL+space to change it back. Sometimes restarting the browser helps.
Youtube works now in the Android Browser and Dolphin. Videos and Flash content plays.{quote:title=gunnar-mobimation wrote:}
Another reason was if I received a new GMail message, then the Mail app takes the unit out of standby.
So I turned automatic checking for mail to "Never".
{quote}
Mail app btw has an option to check mail in standby, as i understand it should not wake it up or should put it to standby after check. And here we found the real problem. Device never go to standby itself, so if it was woken up by some even intended activity it will eat your battery until you take care of it.
{quote:title=gunnar-mobimation wrote:}
After I did this the AC100 has remained in standby for some time now...........
{quote}
Mine still woken up even with disabled wi-fi. I'll try to analyze logcat later.
{quote:title=gunnar-mobimation wrote:}
Cheer up Toshiba !
Not all is lost regarding the AC100 even though it took a serious hit with all the bad reviews when on Android 2.1.
Now on 2.2 a lot of issues are gone. Give it some promotion, run a forum, etc. Nice unit and you did a great job getting
a 2.2 upgrade out.
{quote}
Agree, next should be Android 3.0, Google market and listening to your customers. Btw, you know that Nvidia released Tegra zone app to promote games for Tegra platform. It's really amazing, but i'm tired to download apps trough my phone... AC100 is a *%50* of tegra based devices available on the market and it DOESN't have an app from nvidia to promote it?!
Stop killing your own product. Be a bit flexible, it's great hardware, don't destroy it with attempts to create your own walled garden. The major part of Android system is a huge Google Android Market. -
I got an unlocked z10 im nigeria but Im having problems with the de setup. At de warranty stage I get a " No network connection change your settings" message. I have an active wi-fi connection which the device recognizes. But the warranty doesn't load up so the "agree and do not agree" options are greyed out.<br>What do I need to do?
Hey Makoiche,
Welcome to the BlackBerry Support Community Forums.
Thanks for the question.
Is your SIM card currently in the BlackBerry Z10 when going through the setup? Even when you're connected to the Wi-Fi network, it does not load up the warranty information or countries?
If the issue does persist, I suggest contacting your network service provider and ask to be transferred to BlackBerry so we can gather some logs on this issue.
Let me know if you have any more questions.
Cheers.
-ViciousFerret
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Be sure to click Like! for those who have helped you.
Click Accept as Solution for posts that have solved your issue(s)! -
I5 vs i7 processors in new MacBookPro (April 2010)? Not much in it?
http://ark.intel.com/Compare.aspx?ids=43560,47341,
Comparing the certain i5 and i7 models as likely used in the new April 2010 line up of Apple Mac Book Pros. From the table it would appear that the advantages of the i7 are not groundbreaking. Both specific i5s and i7s here are 2-core with the i7 simply having slightly faster bus speeds.
Thoughts?{quote:title=joosky wrote:}
I have been reading this forum for a while now since I wanted to buy the new macbook pro.
And I did something that nobody here tried to do which is compare prices.
Here is the link: http://ark.intel.com/Compare.aspx?ids=43560,47341,43544,
Basically, there is 32 dollars difference between I5 2.4GHZ and the I5 2.53GHZ.
Will I pay 168 dollars more to get a 500 GB HD instead of a 320 GH?
AND, there is 107 dollars difference between I5 2,4Ghz and the I7 2,66 Ghz.
Will I pay 293 dollars more (400-107) for the 500 GB HD and the 256 MB more of graphics?
You bet it a big NO.
{quote}
I agree. Apple don't separate CPU from hard disc in all the customisation options.
Dell is still the king for customisation in this respect.
I would like to be able to just upgrade the processor and not the hard disc.
The hard disc can be replaced or an external one can be added but the processor is harder (if not impossible, if hardwired onto the motherboard, to upgrade).
{quote:title=joosky wrote:}
What I did is get the best deal here which is the 2,4Ghz I5 but I had to add antiglare and no other option.
{quote}
I agree you made the right choice - best value for money. Sure there are faster processor options but they are not so good value for money.
{quote:title=joosky wrote:}
Apple products are expensive compared to the competition no matter what BUT they are great products. You just have to think if you really need the difference in speed for the difference in price.
{quote}
Agreed, you have to think harder about what you really need, given the premium prices. When there is an option to have even faster there is always the temptation to go further. Recommendations are relative, based on what is available now and in 6 months time when they refresh the line, they'll be saying: "don't go for that model, now we have this model..." and the cycle goes on.
{quote:title=joosky wrote:}
P.S: I hope my first post was helpful to someone.
{quote}
Definitely was, thankyou. -
Hi,
My PB has the following symptoms:
1. Falls into sleep and can't be woken
2. Power cord is amber (there is no residual battery life left in the battery, been like that for some time)
3. With a bit of twiddling, it might turn green for a few mins and PB comes back to life. Then goes off again, cord back to amber.
The scoket might be a little loose (there is some movement, but not sure of that's normal).
Any help gratefully received!
Mark{quote:title=cornelius wrote:}As I see it, the issue could be with the power supply, the battery or the dc-in card.{quote}
Thank you, Cornelius. Exactly my thoughts, that's why I suggested removing the battery from the test chain in the 1st place. We need to know at least if PSU and DC-in card function properly because the battery is the most likely culprit. If the PB starts up without, it's the battery; if not, try another PSU. If that does not work, DC-in card may be faulty, and because it doesn't yet have a magsafe, most probably solder connections or the inlet connector itself will have to be thoroughly checked. If it does, the PSU is not functioning properly, most likely a (nearly)broken cable right next to the connector due to frequent bending.
{quote:title=cornelius wrote:}If the power supply proves serviceable, it should then be able to charge up the battery, provided, of course, the connection at the computer and the dc-in board are all functioning properly.{quote}
Agreed, but if the battery has really had it, it will not charge properly however hard you try. I have seen a case (admitted, this was an old PC laptop) where a dead battery almost self-ignited while trying to recharge.
Always grateful for input, but right now I think it's up to Mark himself to provide us with some test results.
Take care! -
Scheduling Agreement and Quota arrangement
Dear all,
Kindly share with me the individual steps involved in in creating Scheduling Agreement as well as Quota arrangement procurement process with T.Codes and also the relevant configurations involved.
Thanks a lot.Hi,
Here is all about Quota arrangement :
Following are the configurations.
1) To specify number range for quota arrangement
SPRO > IMG > MM > Purchasing> Quota arrangement> Define number range (Int or Ext)
2) Set Quota arrangement usage indicator:
SPRO > IMG > MM > Purchasing> Quota arrangement> Define quota arrangement usage
On Application side following are the prerequisites
1) Create Quota arrangement
SAP Menu> Logistic> MM > Purchasing> Master Data> Quota arrangement > Maintain
2)specify procurement type : Int / Ext
3)Where appropriate specify the special procurement type For ex stock transfer
4) Enter the vendor or supplying plant
5) Specify the quota you want to assign to this source
Please understand terms as below,
Quota Rating = Quota allocated Qty +Quota Base Qty /Quota
Quota Base Qty: Quantity used for manual control of the quota Arrangement (For example new source is included)
Quota: Number that determines how requirement are apportioned among various sources .Decided by a Purchasing people based on confidence on source.
I source determination source with lowest quota arrangement will always be assigned
Example
Source Quota allocated Qty Quota Rating
M 1 100 100
N 2 150 75
O 3 75 25 *
In above case vendor O will be assigned as low Rating *
Now quota Base Qty will come into picture when new supplier is introduced. As you have seen that vendor with low quota Rating is assigned .In case of new supplier as no allocated qty earlier its Quota rating will always be low & all Qty will be allocated to him. To prevent this Base qty is added to allocated Qty so that accordingly it will determined accordingly
If Quota base Qty is 100 & quota is 2
For new vendor X rating will be
Quota rating = 100 + 0 / 2 = 50
I hope this gives you entire clarity.
Vivek -
Quota arrangement with schedule agreements
Dear guru's,
I maintained source list with 3 Schedule agreements with 3 different vendors, MRP indicator as 2, in Material master Quota as 4, and maintained Quota.
now after planning run i am getting two PR's for two vendors and for third vendor schedule lines are generated against that schedule agreement.
can u any one help me in this
vinayHi,
In the source list have you put a 2 as MRP indicator for all the scheduling agreements in the source list.
Also please make sure that the fixing indicator is not set in the source list.
Can you also check the if the validity period for all scheduling agreements and source list entries are correct. -
How can I will declare the symbol u2018 (Single Quote) in the report
Hi ,
Could you please tell me how can I will declare the symbol u2018 (Single Quote) in the report.
My requirement is that I have concate the data with single quote and after that I have to store the data in to an internal table and I have to download the data in the form text file in the presentation server.
For example :
Let the below data I want to download into the presentation serve in the format of text file by storing in internal table.
Assume all are constants:
1st line : abcu2019add
2nd line : defu2019gef
Thanks in advance.Hi Jyothi,
Thanks for the quick reply .
I can agree with you are point but My requirement is like this I am explaining clearly.
I have declared the internal table like this.
DATA: BEGIN OF OTAB OCCURS 0,
LINE (9024),
END OF OTAB.
So I have to append the each line item into the internal table.
So I am explaining what the data I have to append
Ist line contains
'UNBUNOC:2020308u2019 where 020308 I will get the date from reguh table
2nd line contains:
'DTM+20020510' where the 20020510 will be reference document number from the table reguh.
So I want to declare a constant 'UNBUNOC:2
2nd the date from reguh table
And another constant u2018
So that I can concate all the three and I can put into string and I will append into internal table and I can download the data into the presentation server.
Please let me know if you need any more clarification regarding my requirement.
Thanks in advance.
Maybe you are looking for
-
Time machine on two remote computers
I'm trying to set up Time Macine on two Macbooks, using one external hard drive. One is a work laptop and one is a personal laptop. They do not share the same network. How do I get access privileges for what's backed up on my work computer when I'm o
-
Inspire 5200 5.1 - Can it run Xbox 360??
I have the Inspire 5200 5.1 system on my PC. I can run the Xbox 360 through the PC by running the audio outputs through the 'Line In' port on my sound card. This is probably not 5.1 but it is good enough for what little I use the Xbox. However I woul
-
How do I unmerge connected paths in Illustrator CS5?
I was wondering if there was a way to 'unmerge' a group of connected paths. The thing is whenever I click on one of the ovals, it selects a whole group of ovals instead of just the one I selected. The problem is that I drew an oval, copied it multipl
-
Split Message, send to webservice and consolidate the results
Hello, I am looking for some support / examples for following situation: A webservice is existing that only allows a single message to be entered. The webservice will return the result on this message. The structure of the message is very simple as i
-
Hi folks, I am about to create 3 new attendance types: 1000 and 1001 should be processed in time evaluation and the other 1002 shouldn't be processed in time evaluation. I created them using the old attendance types and excluded the attendance type 1