Door to Door Sales

Please give me a phone number to call so the Verizon sales people will STOP coming to my door. I do not want Verizon and I have never called you asking you to send annoying people out here.  I live in Irving Texas. Zip  code 75060.  They are no polite and they won't leave untilI slam the door intheir faces and evern then I hear them talking. I have asked repeatedlyto have my name taken off whatever list you have but they still come out and now the same guy came to my door within a 3 day period of time. Now that's creepy. 

good afternoon car2421,
I apologize for the sales tactics but if you would like to send us a private message with the below post and your address, I would be happy to stop soliciting efforts for you
~Jess

Similar Messages

  • Misleading door to door sales reps.

    About 3 weeks ago a sale rep came to my door offerring service. He asked how much am I paiding for cable. I told him how much and he asked what services are prodived with those charges and I told him the services. He explain that he can give me the same channels and serivce with dvr. To make a long story short he laid out a package with price and told me that is a fees that I will be paying. He also said that he will be crediting the first month of service up to 150 dollars. Well I receive my first bill and there is no credit. I have called customer service and they said that he have no such offer going on and said to contact the sales rep. Which I did twice and even text the number he gave me no reply. Another issue is that I been having not so good services. My tv keeps on either freezing or the screen will go black for hours. I have techs come to my house run scans and say they see no problems. I am fed up now I feel mislead and lie too it's seems like everyone tells me onething and the other thing happens. I will like my credit that the door to door salemen honored or let me cancel my service with out no fine.  I need assitant ASAP !!!!

    Your issue has been escalated to a Verizon agent. Before the agent can begin assisting you, they will need to collect further information from you.
    Please go to your profile page for the forum, and look in the middle, right at the top where you will find an area titled "My Support Cases". You can reach your profile page by clicking on your name beside your post, or at the top left of this page underneath the title of the board.
    Under “My Support Cases” you will find a link to the private board where you and the agent may exchange information. This should be checked on a frequent basis as the agent may be waiting for information from you before they can proceed with any actions.
    To ensure you know when they have responded to you, at the top of your support case there is a drop down menu for support case options. Open that and choose "subscribe".
    Please keep all correspondence regarding your issue in the private support portal.

  • Dishonest door-to-door ATT sales people

    ATT
    Anybody have a good phone number and contact name for reporting door-to-door sales people preying on the elderly? I've tried calling general support number (5942), sales (2020) "escalation" (0789). Have tried to speak to a manager each time. I just get put on hold forever or told that the manager is busy.
    In meantime, please advise your loved ones of the following scam:
    ATT salesman wearing badge knocks on door to let homeowner know that neighborhoods' old wiring and in particular wiring on homeowner's street is being replaced. Homeowner will now have faster connection. This is just a friendly visit not selling anything. Just an FYI about what ATT is doing for its customers. But--will need to replace old modem for her free of charge. Just need to sign this piece of paper ...
    He didn't identify himself as a salesman said he was an installer (implied he was PR person).
    Thank goodness I was called before anything was signed. I actually talked to this person on the phone and before the conversation ended, I was given 3 different stories. the last of which he finally admitted that he was upgrading her ATT phone and internet and switching her cable to ATT. REALLY?!
    I have the paperwork, my relative would have signed which included a contract, a new modem, switching cable service from Comcast to ATT and more.
    My relative had no idea what was being signed. The salesman was, "so polite and said I didn't have to pay for anything".
    Is there anyone at ATT willing to step up to the plate to fire people like this? My relative let this person into her home without thinking twice because she trusts ATT. Would your elderly relative do the same? This must be stopped!

    The door-to-door sales people wear shirts with an AT&T logo, but they work for a independant sales contractor that AT&T does business with.
    You can click this Customer Service link to send a Private Message (PM) to the AT&T customer service team to help you report this incident, though it is not clear to me how much impact it will have, but at least you'll have done what you can. You can expect a reply via return PM (the blue envelope   in the upper right hand corner of this site, next to your avatar and name) in a business day or three.

  • Given False Information by a Door-to-Door Salesman, and Customer Service Can't Help

    Two months ago, one of the Verizon door-to-door salesmen convinced me to switch over to Verizon from my former carrier.  The price was within a few pennies, and altough I was happy with the service I had,  I was willing to give it a try because he said the speed would be faster.  I told him I would do it as long as there was a 30 day time period to cancel with no charges on my account if I was dissatisfied.  He said that Verizon had a "no worries guarantee" policy.  I asked three times if that meant that I could cancel within 30 days without being charged.  He answered, "yes."  
    I wasn't satisified with the upgrade,  and found less expensive service with another carrier, so I cancelled within the 30 days.  However, the first customer service representative I spoke with evidently didn't cancel it because I haven't yet received a return kit yet and I'm still being charged for "current activity" on my most recent bill.  She told me to wait for the return kit and closing bill to call back to get the charges reversed.  I have received neither, so I called back today out of concern.  I spoke with another customer service representative and her supervisor today.  Both nice, but they told me my service ongoing but had been suspended for non-payment, and that the "no worries guarantee policy" would refund only the early cancellation fee, and that there was a minimum 1 month charge, so no pro-rating either.  Surprise!  That's four really nice people at Verizon who have either told me false information or informed me of yet another surprise charge that I was initially told I wouldn't owe.  I've heard the words "we've never done a free trial" plenty of times, and I understand that.  It would be nice if all the representatives were in agreement about that however, especially for a family on a single fixed income.  I asked for the manager's supervisor; she said she was going to write and email up the chain regarding the false information I was given, but that I would owe the money no matter the outcome.  She said I would need to go to the Verizon website to pursue a supervisor higher than herself.  Not helpful, since the Verizon website sends you back to the customer service line I called to get her.
    This is the second time that I've tried switching to Verizon; the first time it took them a month and three phone calls from me to realize service wasn't available at my address; now this.  Is there anyone at Verizon willing to treat me fairly according to what is told me by your representatives?  Are you hoping to have a chance at winning me back as a customer in a year, or are you satisfied to simply try and collect the $126.33 that you are charging me via a false pretense?  I'm looking for a reason to give you another chance.  I'm hoping there is someone out there with a suggestion where to take this next.

    Your issue has been escalated to a Verizon agent. Before the agent can begin assisting you, they will need to collect further information from you.Please go to your profile page for the forum, and look in the middle, right at the top where you will find an area titled "My Support Cases". You can reach your profile page by clicking on your name beside your post, or at the top left of this page underneath the title of the board.
    Under “My Support Cases” you will find a link to the private board where you and the agent may exchange information. This should be checked on a frequent basis as the agent may be waiting for information from you before they can proceed with any actions. Please keep all correspondence regarding your issue in the private support portal.

  • Dual 1.25 mirror door G4 door stop

    Dunno if anyone can help, offer advice or share a similar bad experience with me..
    I bought a lovely new mirror door G4 a couple of years ago, upgrading from my trusty old beige G3 so that I could really get the most out my recently purchased Logic Pro setup.
    I was new to OS X and wasnt sure what to expect, so when I started getting occasional kernel panics I wasnt too worried, thought it was just one of those things.
    But fairly quickly they started to become quite tiresome, and after chatting to other friends with similar machines I learnt that this wasnt normal behaviour.
    I did a bit of research and discovered various things that could be triggering it, and systematically went through my list.
    External devices - gone. P-Ram - Zapped. Disc doctor - Run. Ram removed and changed - Done. Powersupplies - changed. system rebuilt - done. HD erased and reinstalled - done.
    nothing.. the kernel panics continued.
    I even got them reinstalling the basic OS!
    After 5 months of this and not much joy from the original reseller, they reluctantly took it back for a check up.
    "We checked it, reinstalled the system and it all seems fine now"
    Day one.. kernel panic..
    Reinstalling Logic and all my other apps.. kernel panics..
    Back onto the reseller..
    "but it seemed fine here... "
    I suggested the Ram again, so some more was sent out. (after a couple of months of waiting)
    Same problem. Kernel panics galore.
    Ok, so we're a year in now, and my warranty has run out.
    Apple kindly extend it and the machine is eventually taken in by another reseller who seem to thoroughly go over it and find problems with the logic board which they replace.
    Im slightly more optimistic with these guys who seem wholly more professional, but unfortunately the problems continue.
    approaching 15 months now..
    I do more research. Swap the Ram with my work machines and whammo, they kernel panic! I'm sure I've sussed it this time and speak to Apple who extend the warranty again.
    I speak to the original resellers and explain the problem and specify the top end Kingston Ram as being the only brand that I have read that works 100% with the Power Mac G4's which they agree to replace my old ram with and so another long wait begins..
    This takes almost 3 months to arrive.
    I set it up, fire up the machine and start reinstalling software...
    kernel panic.
    I am gutted. Nothing left to try.
    I speak to Apple again and they really strike the final nail into the coffin this time by telling me, Im sorry, your warranty has run out, theres nothing more we can do.
    This goes on for a few calls with me getting more and more irate, until I manage to get the details of a physical customer relations department that I can actually write to.
    So, October 2005 and I write a lengthy letter and include 2 years worth of email correspondance between me and various resellers outlining the problems I have been having.
    No reply, so November I write again...
    No reply, so December I write again...
    No reply, so I call them up to find out whats going on, only to be told that they have no record of recieving anything, the mail must have been lost, oh and you're out of warranty?! But I will not take this as closure on the case, so they suggest to fax them.
    So, I fax over all the letters and sit back waiting for the swift reply I am promised.
    No reply! So, a week and a half later, today, I call again and guess what..
    Yes, we are still waiting for your fax to arrive?!
    I explained that fax's where generally a fairly instant device and that it wouldnt take a week and half to get there (this is technical support?)
    Oh yeah, one bit of priceless support that I got was after returning from holiday last year and continuing with my enquiries, and I was told that sometimes electrical devices stop working if they arent turned on for a couple of weeks?!!! I had to ignore that one. Are they mental?!
    So now here I am, on hold, for an hour so far, waiting to be put through to an imaginary senior representative who will no doubt just tell me what Ive already been told a dozen times..
    anyone experience anything similar?
    Should I drop it off the roof and go to pc world and buy a dell?
    aghhh...
    Thanks for listening.. needed a vent for my rant!
    M

    Hey
    Yeah, it was more of a rant than anything.
    I'd been on hold for an hour to the customer support line and whilst waiting browsed onto the site and felt the need to relieve some pent up anger.
    I've used the Apple disk utility to run the hardware and disk checks.
    I used one other system profiler app when I first got it, but to no avail, and was warned away from Norton very early on so havent touched that.
    It turns out after talking to support that absolutely everything was replaced, so Ive basically got a new machine, apart from the casing and electrics, so maybe the problem lies within the construction.
    I did try running the mac with OS X, and I did indeed still get the panics, I also experienced panics whilst trying to install OS X onto an erased drive with no extra ram, peripheral devices, pci boards.... nothing...
    Hopefully now apple will see that Ive actually been trying to revive a lemon and it is beyond repair and help me out.
    To really rub my face in it, my monitor is now on the way out too!!
    I think in 2 years, I must have got about 2 months use out of the machine and it is determined to either send me grey or turn me to PC.
    Every time I power it up, I have to half prepare myself for the grey screen to slowly descend across my desktop revealing the oh so familiar restart message.
    Will it ever end?!!
    M

  • Display reads door open - doors all closed

    I have an officejet pro 8500
    display randomly reads door open
    copies start and then cancel
    This question was solved.
    View Solution.

    The troubleshooting page here may help resolve the issue.
    Bob Headrick,  HP Expert
    I am not an employee of HP, I am a volunteer posting here on my own time.
    If your problem is solved please click the "Accept as Solution" button ------------V
    If my answer was helpful please click the "Thumbs Up" to say "Thank You"--V

  • Requirements Gateway customize DOORS Advanced Type

    Hello, I am in trouble with R-Gateway...first of all i did not find a R-Gateway Board to post my question, sorry 
    I started adopting the "DOORS Linking Example" as follows:
    -added a LabVIEW project as document with [Covers: DesignReq], PASSED.
    -added attributes to DOORS Linking Example Req-Flag (which shall be used instead of Object Type) and Req-No (which shall be used instead of ReqID)
    Now 3 documents in R-Gateway configuration: DOORS SRD, DOORS SDD and LabVIEW Project
    -changed the SDD type from Object Type = Requirement and requirement ID = ReqID to Req-Flag = "R" with requirement ID = Req-No, PASSED
    -changed the SRD type from Object Type = Requirement and requirement ID = ReqID to Req-Flag = "R" with requirement ID = Req-No, FAILED (SRD requirement status changed from "covered" to "not covered" Note: the DOORS Objects are linked with "refers to" links)
    Trying narrowing...back pedal
    -changed the SRD type from Object Type = Requirement to Req-Flag = "R", PASSED
    -changed the SRD type from requirement ID = ReqID to requirement ID = Req-No, FAILED: again coverage lost
    I can not figure out the problem. Hoping there is someone out there who is familiar with R Gateway i am looking forward to hearing from you soon =)
    Thanks in advance
    RZM
    Solved!
    Go to Solution.

    Here is Req-No displayed                      Here "Absolute Number"
    DOORS uses the attribute "Absolute Number" as unique ID for DOORS objects. This attribute is read-only for all DOORS users including admins. I want to cover these IDs with [Covers: ReqID] entries in LabVIEW code. The reason is I don't want to rely on requirement numbers which shall not be changed. For example when SDD shall be exported for inital release a user might reassign consecutive requirement numbers for beautification.
    For analysis and compliance matrix I don't want to use "Absolute Number" but the "Req-No". SDD object "1" has the requirement number "SDD-10". I know haw to display it in the attributes canvas located bottom left. How can I reference it with somthing like "$i" to display it instead of "$i"?
    Thank you =)
    Yours
    RZM

  • Sales opportunities (source) -- sales report (sales analysis) link, help!

    Hello,
    Should be a simple quetion but I just can't work it out, please help!
    On our sales opportunities we record the source. Ie where we advertised to get that opp through the door.
    On Sales Reports>Sales Analysis I can see the totals for the month and the gross profit.
    What I'm trying to do is map the totals for the month and gross profit against the source. Ie to see which sources make us the money that keeps us going as a company
    But I can't seem to find the links anywhere to do a custom query.
    Can anyone help?
    many thanks

    Hi.......
    You can get this link very easily......
    Its there in standard report.
    When you punch the Sales Opportunity and conclude the same by attaching the document reference like Sales Quotation or Sales Order or any sales Doc. After that if your refer any Opportunity report (Sales Opportunity--> Sales Opportunity Reports) then you have to select the document tick. It will give you the document wise opportunity status.
    Hope this will help you.....
    Regards,
    Rahul

  • Shameful Sales Practices

    Door to door sales person comes to my house, identifies him as a Verizon employee.
    He tries to sell me TV service through Fios.
    I tell him to put it in writing, he tells me he will (but doesn't).
    Next day I get a call from Verizon scheduling my TV service (the guy slammed me).
    I call Verizon to cancel service that I never ordered and learn the sales guy doesn't even work for Verizon.
    I googled this event, turns out many people were mislead like me.
    Shameful Verizon, I expect more.

    IT is not Verizon's fault that the contractor will hire ANYONE to go door to door.... Since you googled Verizon Fios Door to door sales... try replacing verizon fios with any other providers name in your google search.... you will get simmilar sotries from everyone....
    You cant really expect much from an unskilled person that gets paid ONLY for sales that they trun in....
    Sorry that it happened to you, but that's how this world of ours is.
    Bob Robertson - Lighter Klepto - I steal lighters, not bandwith

  • Does Verizon send plain clothesed sales people to customer's homes?

    Hello,
    Today the same individual visited my home on three occaisions.  He would knock but by the time I got to the door he was gone.  I have him on camera.  I was finally able to get to the door in time to speak with him.  He said he was from Verizon and asked about my DSL service.  I didn't see anything on him that indicated he worked for Verizon. I told him I wasn't interested in changing anything, I closed the door and he left.
    Now I am wondering if Verizon actually sends sales people to customer's homes.
    Can someone from Verizon comment on this?
    Thank you.

    As CRobGauth noted, door-to-door sales folk are most likely working for 3rd party marketing companies and not Verizon.  There are many complaints about these types of folks making promises about service deals such as free activation  that aren't backed by Verizon.  I would suggest that you deal only with Verizon directly through their web site, phone sales or online chat.
    Good Luck.
    If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer as Accepted Solution so others can see the solution to the problem.

  • Shame on AT&T - SALES call on Sunday

    Why did I just have an AT&T Sales guy enter through what should have been a locked gate and knock on my door. And on a Sunday when I was trying to relax.

    Why?  Because he's trying to feed himself that those that look to him for support.
    Why was the gate (that was supposed to be locked) unlocked?  Good question.  Whose gate is it?  Who is responsible for locking it?
    AT&T doesn't directly employ door-to-door salespeople  Those are contracted out to sales outfits who do all sorts of things to make a sale.  The most tame of these things is knocking on doors.  He might have missed your No Solicitation sign.
     

  • Verizon Scam Sales

    Had just about enough.
    Some time back, notified Verizon to keep their neighborhood sales people away from my door.
    What do I see this evening? Two  Verizon FIOS hucksters.
    Why don't I want them here?
    About a year ago, they showed up here with a story that DSL was being dropped and we needed to get signed
    up for FIOS. We thought it might be a good deal, and signed up.
    Only come to find out when I called in to get some more info, the whole story was bull**bleep**.
    DSL wasn't going anywhere. We didn't "need" FIOS. So I cancelled it, told them not to install anything.
    That went real well. They  cameout anyway and laid the fiber in my yard. When I told them to get lost
    and take the **bleep** fiber with them, they left the coil hanging at the interface box.
    And what do I hear tonight? DSL is going away and we need to get hooked up on FIOS.
    Hey Verizon reps. If your reading this, guaranteed the FCC is getting an ear-full as well.

    Hate to say it but eventually those door-to-door salesmen will be right. See:
    http://www.dslreports.com/shownews/Verizon-Pushing-Troublesome-DSL-Users-Toward-FiOS-118689
    Articles like the above have been appearing for the last few years on many renowned technical sites. Areas where the copper is old and beat up are going to see DSL services no longer offered. Areas where FiOS is installed are going to see the DSL network struggle to provide bandwidth at night as seen in many threads throughout the Internet once FiOS shows up, and anyone who calls in reporting chronic DSL trouble are most likely going to be pushed to FiOS. Can't blame Verizon for doing so since copper's getting real expensive to maintain (plus it likes to get stolen!), on top of biting billions of dollars of investment being rejected by many. Any area not getting FiOS with chronic DSL troubles will most likely see a worse off wireless product.
    Bearer of bad news, but if they eventually do force you to Fiber, see if they'll let you have their super secret package that is priced exactly the same as DSL but delivers more speed. If they can give you that, get it, but don't let them remove the copper connection from the pole to your home. That's still mandated to be there. Been waiting for years to get rid of my DSL yet FiOS has not shown up yet.
    ========
    The first to bring me 1Gbps Fiber for $30/m wins!

  • Can't find my salesperson

    Ok on 9-23-13 a agent came to my door to sign me up for verizon I told her I was not interested because I was going to get time warner in two days . She ask me the price and I told her and began to day that she could beat it . I ask her to come back in the evening when my husband was around . She agree and both women came back into my home that evening . She ( main woman ) began to tell me that that they could save me money she show me the plan and said I can get you ultimate , fully loaded package and a Dvr and 3 stb- had boxes . I told her no because I was going to put six boxes and I was adding the spanish channels for my mother and she said ok I'll give you all that plus the 50/25 internet . My husband and I said it sounds good but we have time warner home security and she said no problem we can add it on their 10.00 monthly charge and the numbers still sounded good . I was so excited . Then my husband said how much would it be to do the 75/35 internet she said 10.00 and we ask about the maintenance wires and she's said 10.00 well we did not hesitate since the number was still lower then time warner . She said you will get a 400. Visa gift card too . I was happy even though I was letting go of a 500. 00 visa with time warner . Since my price was still much lower . She wrote in the contract and check off the spanish and the fully loaded, 75/35 and ultimate package . I husband ask her what about the alarm that we were discussing and she said oh I'll add it write here under list all promotions/ offer applicable to the customer . She wrote on those line 400.00 visa , security back up and inside wire maintenance and my estimated bill for $228.06 with an activation fee of 69.99. 0 charge on equipment and installation fee . 1 st est. bill 302.99 since it had my first installment of the 69.99 . She said I would be getting and email and that she would call me back and wrote her number and the the other agent name and number too. I did not recieve the email so I left a message on both agents cell phones and I never got a call back til this day . When the verizon people call to versify of my order they would not mention my complete order and they would not even mention my home alarm . Two call and then I ask wait you are all calling but no one is saying anything about the house alarm and they said said that's a different dept. huh? Well I call an d spoke to the home security Nd told him was getting worry because no one knew about my alarm order and he said I understand but no one is going to call you and you only call us if you are ordering it if they wrote it in your contract then they will get a hold of you . So I try to get the Agents again no call back . I then went to my verizon and added a note to the technician telling him about my concern with the alarm and the I wrote the name and the number to that agent . When the technician came I show him my contract and he said he was only told one Dvr but he would install the other one . I show him where the agent wrote my security . He said they would contact me when his work was done because they could not do anything Untill then I said ok . Next morning I wake up and I'm super excited to see my channels and I notice that I don't get HBO so I call them and tell them that it was part of plan and they said no that they could not charge me twice for show time since it was on my ultimate nd package so the agent had keyed it differently . I said she never said anything like that she said it was fully loaded and handed me a line up so I could see all the premiums channels I was getting . This phone agent said I'll add it her but we will have to take away 400.00 card and I said what ? Then she went on and said ok I can do I thus way and you can get your HBO and I ask is this going to cost me more now and age said no mam it's actually going to save you 3.00 oh wow ok . She said I will send you and email so you can. Understand . I said ok then we discuss the alarm and told her no one seem to know anything and she said she had to add it because the agent did not write it down and I told her I have the hard copy here. And where she wrote it I said someone has to have the original white copy the agent signed . I told her the agent said we could use our equipment from time warner because it work the same I said great but the agent on the phone said no and that I would have to purchase it and I said ok at this point I was worry more that my family did not have an alarm set in the house anymore . She explain if I was not happy I could cancel within 30 days . But the 14.99 for shipping if the kit I would have go pay . I said ok . Three hour later I go online and I see HBO is costing more not saving me 3.00 and now my shipping charges for the kit have gone from 14.00 to 19.99 and now there are equipment and installation charges . I called up again frantically and speak to a another agent who says to fax the bill .first person to seem willing to help me out . I do so and she call me and leaves a message that she received my fax and will handed to another group so they can help me and call me on Monday . I call the two door to door agents and leave. Message to one because the main one box is too full to receive any messages .meanwhile I can't understand why no one sees that she wrote about my alarm being part of it . I know that the original white copy exists somewhere. I study the form and I realized that she called it security back up and I it makes me wonder if she deliberately wrote that so I would not get the services I was promised . I've tried getting a hold of her because I figure she could be the one person to sort all of the mess easily if she forgot to key in the info on the computer when she placed my order . No answer again from both door to door salespersons .... .. Here I am waiting for Monday to arrive and the party that will help me resolve this . Scare of calling again since my bill keeps getting bigger and bigger with each call........ What happen to trusting the people that come into your home and sit down and chat with you like they really care about getting you a great deal ..... They disappear as soon as the ink dry on my paper .... Nowhere to be found . I ask myself how can anyone keep hearing your messages about the confusion and asking you to return the call to clear all the mix ups . Hiw is it that they can come into my living room and drink the beverages that I offer because they seem so hit from walking from door to door and spend two hours talking with my husband and me about my family and and their families and tend it with a shake of Hand and never to be heard of again ....... What type of sales people is verizon training ? Someone please help me get them to see the original contact and honour the quotes .......... Very hurt and disappointment doing business for the very first time with verizon

    Hi Ivebeenduped,
    Your issue has been escalated to a Verizon agent. Before the agent can begin assisting you, they will need to collect further information from you. Please go to your profile page for the forum and look at the top of the middle column where you will find an area titled "My Support Cases". You can reach your profile page by clicking on your name beside your post, or at the top left of this page underneath the title of the board.
    Under "My Support Cases" you will find a link to the private board where you and the agent may exchange information. This should be checked on a frequent basis, as the agent may be waiting for information from you before they can proceed with any actions. Please keep all correspondence regarding your issue in the private support portal.

  • 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.

  • Discoverer Date Parameters

    Hi,
    How can i perform for user date parameters to get the result of
    From Date To Date (2007) Sales , From To Date(2006)
    It is required in view that having sales of 2 Years 2006,2007 and the user
    need to compare sales of period in 2007 with same period in 2006
    Regards
    Hassan

    hi hassan,
    for having from-date & to-date parameters in ur report its better to create 2 parameters with the same names & define a condition using "between" option along with those parameters in discoverer itself.
    coming to comparison of 2 years data like "this year & last year" you should mention these in ur query itself like below:
    hope it will b helpful for ur report.
    all the best_Rakesh Reddy.
    SELECT A.Region,A.Account,A.Door,A.Location,A.retailer_month,A.week,SUM(A.Netretlsold_TY) as Netretlsold_TY,SUM(A.Netretlsold_LY) as Netretlsold_LY FROM
    SELECT
    NVL(TY.Region,LY.Region) as Region,
    NVL(TY.Account,LY.Account) as Account,
    NVL(TY.Door,LY.Door) as Door,
    NVL(TY.Location,LY.Location) as Location,
    NVL(TY.RETAILER_MONTH,substr(LY.RETAILER_MONTH,1,2) || to_char(to_number(substr(LY.RETAILER_MONTH,-4))+1) ) as RETAILER_MONTH,
    NVL(TY.WEEK,LY.WEEK) as Week,
    NVL(TY.Netretlsold,0) as Netretlsold_TY,
    NVL(LY.Netretlsold,0) as Netretlsold_LY
    FROM
    SDW.ST_WK_SALES_SUM_MV TY
    FULL OUTER JOIN SDW.ST_WK_SALES_SUM_MV LY
    ON
    TY.Door=LY.Door
    AND TY.RETAILER_MONTH = substr(LY.RETAILER_MONTH,1,2) || to_char(to_number(substr(LY.RETAILER_MONTH,-4))+1)
    AND TY.WEEK = LY.WEEK
    ) A
    GROUP BY A.Region,A.Account,A.Door,A.Location,A.retailer_month,A.week;

Maybe you are looking for