PO Value Exceeded

Dear Friends,
I've generated a PO for Rs. 100.
I have to pay advance to Vendor Rs. 50. While creating a Down Payment Request (f-47) for Rs. 50, I'm getting a Error Message as 'Purchase order Value Exceeded'.
Could any body please help me?
with regards,
Nikita Kale.

please check wht % you have maintained in Billing plan.
I think it might be Down payment less than 50%
or check the link
http://help.sap.com/saphelp_46c/helpdata/en/59/ac922bcb0411d2acbe0000e8a5bd28/frameset.htm
Edited by: WISH on Mar 11, 2008 10:30 AM

Similar Messages

  • Contract value exceeding in Release order

    Hi  All,
    The target value of the value contract is 200,000 INR. After reaching to the 190,000 INR ( Making different Release order ) the user has made one more purchase order for this value contract with the value 50,000. The system hasnt given any warning /error message that the contract value exceeding...
    In general system should have to give the error message that the contract value is exceeding???
    The message 06-042 & 06-155 set as error message.
    also if your trying to make release order of more than 200,000 INR then it is giving error message 06-42 the value is exceeding
    Please suggest
    Thanks & Regards
    Rajesh

    Please check your release order qty set in contract item / header details

  • ORA-22813: operand value exceeds system limits

    hi all,
    ORA-22813: operand value exceeds system limits
    the above error occurs while calling a function. in 10g its working fine. after moving it to 11g v r facing the error. Plz help

    KRIS wrote:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
    PL/SQL Release 11.1.0.7.0 - Production
    CORE 11.1.0.7.0 Production
    TNS for Linux: Version 11.1.0.7.0 - Production
    NLSRTL Version 11.1.0.7.0 - ProductionIt seems that is a bug,refer
    *Bug 8861467 - ORA-22813 / ORA-600 [12761] can occur in 11g [ID 8861467.8]*
    To fixing problem you need apply 11.2.0.2 (Server Patch Set)

  • Free Goods to be issues if Sales value exceed target Value

    HI,
    User wanted us to configure the sales order such that when the total sales order vlaue exceed a certain amount, the system will automatic include a certain free items to the order as FOC item.
    How do I go about configuring it?
    Thanks

    Hi Colin,
    1: With standard SAP your requirement will not be fulfilled.
    2: To do this you need some ABAP development.
    Ask your ABAPER to write a code in user exit MV45AFZZ
    where check the Value of the Sales order. If the Sales order value exceeds a specific value then add the FOC items in the Sales order where the item category should be TANN (or equivalent).
    You might need a custom Z-table where you can store what Materials are to be added as FOC items in sales order & at what value.
    regards
    Edited by: Innovation is key on Mar 4, 2011 9:22 AM

  • XML data value exceeds maximum length - ORA-30951

    Hello,
    I am receiving ORA-30951: Element or attribute at Xpath /dataroot/Respondent[1]/Response[3]/Value exceeds maximum length error during the XML load.
    I have registered the schema and it works fine when the Value is less than 64k but fails if its greater. I tried changing the type of Value to type="xsd:base64Binary" xdb:maintainDOM="false" xdb:SQLName="LOB_DATA" xdb:SQLType="BLOB" but then I get ORA-00932: inconsistent datatypes error.
    Can someone please let me know what I am doing wrong or is there a way I can load more than 64k length elements on 10g?
    Thanks
    Here is my schema.
    var SCHEMAURL varchar2(256)
    var XMLSCHEMA CLOB
    set define off
    begin
    :SCHEMAURL := 'http://xmlns.example.com/Svy_Resp.xsd';
    :XMLSCHEMA := '<?xml version="1.0"; encoding="utf-16"?>
    <xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0"; xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xdb:storeVarrayAsTable="true">
    <xsd:element name="dataroot" xdb:defaultTable="SVY_RESP_XML_SCHEMA" type="datarootType" />
    <xsd:complexType name="datarootType" xdb:maintainDOM="false"
    xdb:SQLType="Dataroot_T">
    <xsd:sequence>
    <xsd:element maxOccurs="unbounded" name="Respondent" type="RespondentType" />
    </xsd:sequence>
    <xsd:attribute name="generated" type="xsd:dateTime" />
    </xsd:complexType>
    <xsd:complexType name="RespondentType" xdb:maintainDOM="false" xdb:SQLType="Respondent_Type">
    <xsd:sequence>
    <xsd:element name="RespondentID" type="xsd:int" />
    <xsd:element name="KsID" type="xsd:int" />
    <xsd:element name="email" type="xsd:string" />
    <xsd:element name="SyID" type="xsd:int" />
    <xsd:element name="KSuID" type="xsd:int" />
    <xsd:element name="Completed" type="xsd:int" />
    <xsd:element name="SubmitDateTime" type="xsd:dateTime" />
    <xsd:element maxOccurs="unbounded" name="Response" type="ResponseType" />
    </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="ResponseType" xdb:maintainDOM="false" xdb:SQLType="Response_Type">
    <xsd:sequence>
    <xsd:element name="ResponseID" type="xsd:int" />
    <xsd:element name="RespondentID" type="xsd:int" />
    <xsd:element name="CID" type="xsd:int" />
    <xsd:element name="AID" type="xsd:int" />
    <xsd:element name="Value" type="xsd:string"/>
    <xsd:element name="QID" type="xsd:int" />
    <xsd:element name="SID" type="xsd:int" />
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>';
    end;
    /

    Thanks for the quick response. I am not able to modify the source file, but will it be possible to set the value to NULL if it exceeds the max length instead of failure?
    Thanks

  • Operand value exceeds system limits in sdo_aggr_mbr

    Hi-- i'm trying to get the MBR of a fairly large geometry (1429 vertices) and run into a strange problem:
    when i:
    select sdo_aggr_mbr(shape)
    from FEEDER_LINES_SDO
    where subname = 'OCEANO';
    i get what i expect:
    SDO_GEOMETRY(2003, 82212, NULL, SDO_ELEM_INFO_ARRAY(1,1003, 3),SDO_ORDINATE_ARRAY(712103.736,3876977.34, 733591.744, 3896557.18))
    however when i try to get the subname in my query as well:
    select subname ,sdo_aggr_mbr(shape)
    from FEEDER_LINES_SDO
    where subname = 'OCEANO'
    group by subname;
    i get
    ERROR at line 1:
    ORA-22813: operand value exceeds system limits
    The query fails with "ORA-00937: not a single-group group function" when i leave out the group by clause
    i can get around it with a kludge, but would like to know why the group by fails
    the kludge:
    select subname,min(t.x) minx, min(t.y) miny, max(t.x) maxx, max(t.y) maxy from
    FEEDER_LINES_SDO c,
    TABLE(SDO_UTIL.GETVERTICES(c.shape)) t
    where subname = 'OCEANO'
    group by subname;
    SUBNAME MINX MINY MAXX MAXY
    OCEANO     712103.736 3876977.34 733591.744 3896557.18
    where minx(), miny() etc are variations on:
    function minx (geom_in mdsys.sdo_geometry)
    return number DETERMINISTIC IS
    begin
    return sdo_geom.sdo_min_mbr_ordinate(geom_in,1);
    end;
    the group by expression seems to work fine on geometries with less than 1200 vertices. Is there a system parameter i can change?
    elvis{44}% oerr ora 22813
    22813, 00000, "operand value exceeds system limits"
    // *Cause:  Object or Collection value was too large. The size of the value
    // might have exceeded 30k in a SORT context, or the size might be
    // too big for available memory.
    // *Action:  Choose another value and retry the operation.
    i am running oracle 9.2.0.1 on solaris8
    any insight on this will be greatly appreciated
    cheers
    --kassim

    Hi Kassim,
    At KMS I recently ran into the same ORA-22813, when running this cursor SQL
         CURSOR lcur_montage IS
         select m.mont_id, m.sys_PK, m.krtp_id, m.mont_geom, m.til_dato_id , m.forloeb      
         from MTK_montage m
         where m.fra_dato_id = in_dato_id
         and m.krtp_id = 1           
         order by m.mont_id;
    Omitting the order by clause makes it work fine. If I alternatively omit the SDO_geometry m.mont_geom as a select item, the query also works.
    Our problem seems to arise when trying to sort selected rows, which contain large objects such as SDO_geometry.
    Yesterday we played around with SORT_AREA_SIZE, but to no avail. It turns out to be a known bug.
    When I today search for ORA-22813 in MetaLink, the first list item is
    1.
    9.2.0.X Patch Sets - List of Bug Fixes by Problem Type
    Type: Note
    Doc ID: 217194.1
    Score: 63%
    Modified Date: 18-FEB-2003
    Status: PUBLISHED
    Platform: Generic issue
    Product: Oracle Server - Enterprise Edition
    which unfortunately will not open and reveal its content.
    On the other hand trying MetaLink -> Bugs -> search for 'ORA-22813' gives amongst others Bug 2656107, which looks a lot like my problem.
    For Oracle eyes: - when will this bug be fixed? Does it solve the problem at hand?
    - regards
    Jens Ole Jensen
    Kort & MatrikelStyrelsen (WWW: http://www.kms.dk)
    Danmark  
    version: (32 bit) Oracle9i Enterprise Edition Release 9.2.0.2.0 - Production on Sun/SunOS 5.8 (64 bit)

  • IR Value exceed GR value

    Hi xpert,
    how to block IV from processing IR if the item value exceed GR item value.

    Hi,
    SPRO --> MM --> logistic invoice verification --> invoice Block --> Set tolerance limit
    Now u can set tolerance for a compnay code
    BR     Percentage OPUn variance (IR before GR)
    BW     Percentage OPUn variance (GR before IR)
    DQ     Exceed amount: quantity variance
    DW     Quantity variance when GR qty = zero
    here in BR and BD, you can define upper limit or lower limit.
    Regards,
    Pardeep malik

  • Target value exceed in contract

    when i try to creat the service entrysheet by adopting the service details from the contract . then i am getting  this error:TARGET VALUE EXCEED"
    COULD ANY ONE SOLVE THIS ERROR..kindly suggest the possible way to solve this error..
    regards,
    Manu

    hi Manu,
    This message appears when the value maintain at service entry sheet exceeds then that defined at the contract...
    As per this i think you have maintain a Value contract.....
    Firstly, PLs check the enter value limit in the contract....
    Then check the entry sheet, whether you are entering the more value then that defined in the contract....
    If yes, then pls correct here and check and save....
    This shd resolve your problem....
    Hope it helps....
    Regards
    Priyanka.P

  • Sum of values exceeds the allowed maximum value per service line

    Hi Guys,
      While creating PO wrt to contract : I get error msg : Sum of values exceeds the allowed maximum value per service line Message no. SE402. Can I change it to warning or should I bifurcate one line into two , as the value is very big. Totalling to 11 characters excluding decimal. Its like xxx,xxx,xxx.xx inr.
    Regards,
    SK

    Hi,
       For service line items, the maximum allowed limit is 999999999.99 (total 11 digits including 2 decimals) as per design. If you want more than that, you may split the service in to two line items.
       The note:   1810281 - System does not issue error message SE 402  explains the logic.
    Regards,
    AKPT

  • "New" error during ApplyLogOnInfo(...): Invalid parameter value: exceeds...

    Invalid parameter value: exceeds the Min or Max or conflicts with existing value or edit mask
    error during ApplyLogOnInfo() to the tables contained within a report.  Now, this is a "new" error because this was not being thrown when the application was compiled for .Net 1.1 using the Crystal Reports v9.1.5000.0 components.  When the application was migrated to .Net 2.0, and set to reference the the 10.2.3600 set of managed components, this started appearing. 
    Also, this will only occur on certain .rpt files that are loaded, and can be thrown when also executing the VerifyDatabase() method.  By certain .rpt files, I mean those that have been opened and saved with Crystal Reports 2008 (warning message when saving indicated that the report will not be able to be opened in Crystal Reports versions earilier the 9.0; should I not assume this is correct?).
    ' Load a report that had been created in v10, but opened and saved in v12
    Dim sFileName As String = "C:\test\CR2008Report1.rpt"
    crReportDocument.Load(sFileName, OpenReportMethod.OpenReportByDefault)
    crReportDocument.VerifyDatabase()  ' Throws the EngineExceptionErrorID.MissingParameterFieldCurrentValue exception:
      ' Invalid parameter value: exceeds the Min or Max or conflicts with existing value or edit mask
    ' Load a report that had been created in v10
    Dim sFileName As String = "C:\test\CR10Report.rpt"
    crReportDocument.Load(sFileName, OpenReportMethod.OpenReportByDefault)
    crReportDocument.VerifyDatabase()  ' No exceptions; whacky.

    >
    A G wrote:
    > Our product will not get integrated with SharpDevelop as it does with VS though you can use the assembly in you application.
    Right, I am aware of the IDE plugin functionality (BTW, I'm going to guess no, but is the functionality present in the "Express" editions?).  When a viewer application is created in VS, you can convert/open it in #d and have all of the designer props/pages available.  When manually adding the viewer in a new #d project, you can add it, but it doesn't show up visually in the forms designer window (boggle).
    > So just make a simple report and try to view it. can you see it?
    I will investigate this probably tomorrow...
    > Also is your report have any parameter? Dynamic or static?
    Yes, there are parameters embedded (?) in the .rpt.  There are no parameters added at runtime; only the parameter values are set at runtime.
    > Make sure you can see data in report in designer..

  • DRG-11112: length of CLOB query value exceeds maximum of 64000

    Is there a CLOB length limitation when running an Oracle Text search? (v 11.1.0.7) I have checked the Reference Guide and Application Developer's Guide.
    --create table
    create table nk_1929(id number, vc_a clob);
    --insert dummy data
    declare
    vc_clob clob;
    begin
    vc_clob := lpad(to_clob('a'), 222920, 'a');
    insert into nk_1929 values(1, vc_clob);
    end;
    --create index
    create index nk_1929_ndx on nk_1929(vc_a)
    indextype is ctxsys.context parameters('
    datastore ctxsys.default_datastore
    stoplist ctxsys.empty_stoplist');
    --run query with a search string longer than 64000
    declare
    str1 clob;
    query_term clob;
    begin
    select vc_a into query_term from nk_1929 where id = 1;
    str1 := 'select id from nk_1929 where contains(vc_a, :1) > 0';
    execute immediate str1 using query_term;
    end;
    ORA-29902: error in executing ODCIIndexStart() routine
    ORA-20000: Oracle Text error:
    DRG-11112: length of CLOB Query Value exceeds maximum of 64000
    Please let me know if I am missing something here?

    Same 64000 CLOB query value limitation is also generated with a simple select:
    --run query with a search string longer than 64000
    declare
    vn_id number;
    query_term clob;
    begin
    select vc_a into query_term from nk_1929 where id = 1;
    select max(id) into vn_id from nk_1929 where contains(vc_a, query_term) > 0;
    end;
    ORA-29902: error in executing ODCIIndexStart() routine
    ORA-20000: Oracle Text error:
    DRG-11112: length of CLOB Query Value exceeds maximum of 64000

  • COLUMN DATA VALUE EXCEEDS-REJECTED WHILE BULK LOADING

    hi
    am having a table like
    CREATE TABLE SMLC_CELLDATA
      MCC          NUMBER,
      MNC          NUMBER,
      LAC          VARCHAR2(10 BYTE),
      CELL_ID      VARCHAR2(10 BYTE),
      CELL_NAME    VARCHAR2(500 BYTE),
      LAT          FLOAT(20),
      LON          FLOAT(20),
      ORIENTATION  NUMBER,
      OPENING      NUMBER,
      RANGE        NUMBER,
      BSIC         NUMBER,
      ARFCN        NUMBER,
      HANDOVER     VARCHAR2(4000 BYTE),
      EIRP         NUMBER,
      ENVIRONMENT  VARCHAR2(50 BYTE)
    TABLESPACE SYSTEM
    PCTUSED    40
    PCTFREE    10
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                MINEXTENTS       1
                MAXEXTENTS       2147483645
                PCTINCREASE      0
                FREELISTS        1
                FREELIST GROUPS  1
                BUFFER_POOL      DEFAULT
    LOGGING
    NOCACHE
    NOPARALLEL;WHEN I TRY TO BULK LOAD DATA IN TO THIS TABLE CERTAIN ROWS WERE REJECTED. AND IT SAYS COLUMN HANDOVER VALUE EXCEEDS THE LIMIT.
    BUT THE DATA IS
    404-80-101-1021 404-80-101-1022 404-80-101-1023 404-80-101-1101 404-80-101-1103 404-80-101-1131 404-80-101-1132 404-80-101-1133 404-80-101-1151 404-80-101-1153 404-80-101-1161 404-80-101-1163 404-80-101-1322 404-80-101-1392 404-80-101-1393 404-80-120-18312
    WHICH IS OF 256 BYTES. HOW COME IT CAN REJECT IT..?
    AEMUNATHAN
    Edited by: Aemunathan on Sep 26, 2008 6:13 PM

    the bad file contains
    404     80     101     1102     110_Hotel_Madura_H2     10.79805556     78.68110833     120     60     3000     38     77     404-80-101-1021 404-80-101-1022 404-80-101-1023 404-80-101-1101 404-80-101-1103 404-80-101-1131 404-80-101-1132 404-80-101-1133 404-80-101-1151 404-80-101-1153 404-80-101-1161 404-80-101-1163 404-80-101-1322 404-80-101-1392 404-80-101-1393 404-80-120-18312     52     u
    404     80     105     9012     901_Tansi_Kumbakonam_H2     10.96108056     79.39166667     120     60     3000     34     75     404-80-105-9011 404-80-105-9013 404-80-105-9032 404-80-105-9051 404-80-105-9052 404-80-105-9091 404-80-105-9092 404-80-105-9093 404-80-105-9132 404-80-105-9133 404-80-105-9181 404-80-105-9183 404-80-105-9233 404-80-105-9282 404-80-121-17013 404-80-121-17033     52     u
    404     80     107     13012     1301_Attur_H2     11.59705556     78.59446944     100     60     3000     32     77     404-80-107-13011 404-80-107-13013 404-80-107-13023 404-80-107-13041 404-80-107-13043 404-80-107-13112 404-80-107-13113 404-80-107-13121 404-80-107-13122 404-80-107-13123 404-80-107-13441 404-80-107-13443 404-80-107-13471 404-80-107-13473 404-80-232-32842 404-80-232-32843     52     u
    404     80     107     13303     1330_Omallur_H2     11.73888889     78.04583056     210     60     3000     36     69     404-80-107-13101 404-80-107-13102 404-80-107-13241 404-80-107-13301 404-80-107-13302 404-80-107-13313 404-80-107-13322 404-80-107-13352 404-80-107-13423 404-80-204-4051 404-80-204-4052 404-80-204-4053 404-80-204-4072 404-80-204-4073 404-80-207-7201 404-80-207-7203     52     u
    404     80     107     13423     1342_Yercaud_Support_H1     11.77083056     78.19860833     240     60     3000     32     63     404-80-107-13071 404-80-107-13072 404-80-107-13073 404-80-107-13091 404-80-107-13092 404-80-107-13093 404-80-107-13102 404-80-107-13132 404-80-107-13171 404-80-107-13173 404-80-107-13301 404-80-107-13302 404-80-107-13303 404-80-107-13311 404-80-107-13313 404-80-107-13322 404-80-107-13351 404-80-107-13352 404-80-107-13353 404-80-107-13421 404-80-107-13422 404-80-136-36102 404-80-204-4021 404-80-204-4031 404-80-204-4051 404-80-204-4073 404-80-204-4261 404-80-204-4263     52     u
    404     80     109     15152     1515_Paramathy_Exg_H1U     11.15138889     78.02471944     200     60     3000     32     71     404-80-109-15141 404-80-109-15142 404-80-109-15143 404-80-109-15151 404-80-109-15153 404-80-109-15251 404-80-109-15253 404-80-109-15311 404-80-109-15312 404-80-109-15313 404-80-109-15322 404-80-109-15401 404-80-109-15403 404-80-205-5232 404-80-207-7531 404-80-207-7533     52     u
    404     80     109     15172     1517_Andalurgate_H1     11.44916667     78.15916667     80     60     3000     39     68     404-80-109-15011 404-80-109-15053 404-80-109-15161 404-80-109-15163 404-80-109-15171 404-80-109-15173 404-80-109-15181 404-80-109-15182 404-80-109-15183 404-80-109-15193 404-80-109-15261 404-80-109-15333 404-80-109-15421 404-80-109-15430 404-80-109-15463 404-80-207-7101 404-80-207-7102 404-80-207-7162     52     u
    404     80     112     20012     2001_Attur_TE_H2D     11.59705556     78.59446944     85     60     1500     32     77     404-80-107-13121 404-80-107-13122 404-80-107-13123 404-80-112-20011 404-80-112-20013 404-80-112-20022 404-80-112-20023 404-80-112-20141 404-80-112-20143 404-80-112-20153 404-80-112-20231 404-80-112-20233 404-80-112-20251 404-80-112-20253 404-80-232-32842 404-80-232-32843     52     u
    404     80     115     12222     1222_Venkateswara_Ngr_H1     11.11722222     79.66166667     210     60     3000     35     71     404-80-115-12221 404-80-115-12223 404-80-115-12231 404-80-115-12232 404-80-115-12241 404-80-115-12242 404-80-115-12243 404-80-115-12253 404-80-115-12261 404-80-115-12262 404-80-115-12311 404-80-115-12312 404-80-115-12313 404-80-115-12321 404-80-115-12353 404-80-115-12413 404-80-115-12471     52     u
    404     80     121     17011     1701_Eravancheri_H1     10.93305556     79.55416667     40     60     3000     34     82     404-80-105-9112 404-80-105-9113 404-80-105-9163 404-80-105-9742 404-80-115-12242 404-80-115-12243 404-80-115-12252 404-80-115-12403 404-80-115-12473 404-80-121-17012 404-80-121-17013 404-80-121-17041 404-80-121-17043 404-80-121-17131 404-80-121-17133 404-80-121-17182     52     u
    404     80     121     17442     1744_Exg_Pattukkottai_H2     10.42666667     79.31891667     130     60     3000     32     76     404-80-121-17111 404-80-121-17113 404-80-121-17162 404-80-121-17401 404-80-121-17402 404-80-121-17403 404-80-121-17422 404-80-121-17423 404-80-121-17431 404-80-121-17433 404-80-121-17441 404-80-121-17443 404-80-121-17461 404-80-121-17472 404-80-121-17522 404-80-121-17523     52     u
    404     80     130     30022     Coonoor_MW_2     11.34527778     76.81027778     270     65     3000     47     68     404-80-130-30041 404-80-130-30051 404-80-130-30151 404-80-130-30012 404-80-130-30031 404-80-130-30032 404-80-130-30033 404-80-130-30021 404-80-130-30052 404-80-130-30152 404-80-130-30153 404-80-130-30011 404-80-130-30211 404-80-130-30162 404-80-130-30163 404-80-130-30013 404-80-130-30361 404-80-130-30023 404-80-130-30363 404-80-130-30251 404-80-130-30253     52     u
    404     80     130     30093     Forest_Land_Ooty_3     11.395     76.70277778     270     65     3000     44     75     404-80-130-30433 404-80-130-30182 404-80-130-30142 404-80-130-30143 404-80-130-30103 404-80-130-30091 404-80-130-30092 404-80-130-30082 404-80-130-30083 404-80-130-30053 404-80-130-30321 404-80-130-30183 404-80-130-30422 404-80-130-30283 404-80-130-30423 404-80-130-30413 404-80-130-30432 404-80-130-30431     52     u
    404     80     130     30163     Vandhisolai_3     11.37222222     76.81861111     220     65     3000     47     74     404-80-130-30161 404-80-130-30162 404-80-130-30153 404-80-130-30011 404-80-130-30012 404-80-130-30151 404-80-130-30073 404-80-130-30022 404-80-130-30033 404-80-130-30051 404-80-130-30361 404-80-130-30013 404-80-130-30303 404-80-130-30383 404-80-130-30023 404-80-130-30203 404-80-130-30253     52     u
    404     80     132     32731     Collectorate_IBS TNJ     10.81458     79.60622     0     65     3000     47     74     404-80-121-17071 404-80-121-17091 404-80-121-17093          u
    404     80     134     34741     Parambikulam_IBS_1     10.390417     76.774889     0     65     3000     42     63     404-80-132-32443          m
    404     80     134     34751     TNG_Palayam_IBS2_1     10.390417     76.774889     0     65     1000     40     63     404-80-134-34141 404-80-134-34651 404-80-134-34652          
    404     80     149     49011     Tirunelveli MSC Switch     8.72777     77.7044     0     360     200                         
    404     80     149     49012     Tirunelveli MSC Switch     8.72777     77.7044     0     360     200                         m
    404     80     166     6611     Ranga_Pilllai BSNL Pondy Exchange building     11.56     79.5     0     360     200               404-80-160-60171          m
    404     80     204     4261     426_Old_Suramangalam_H2     11.67055556     78.10999722     0     60     3000     39     70     404-80-107-13072 404-80-107-13073 404-80-107-13302 404-80-107-13423 404-80-204-4051 404-80-204-4071 404-80-204-4072 404-80-204-4073 404-80-204-4251 404-80-204-4253 404-80-204-4262 404-80-204-4263 404-80-204-4270 404-80-204-4753 404-80-204-4773 404-80-204-4910     52     u
    404     80     205     5232     523_Kodumudi_H2     11.07916667     77.87999722     120     60     3000     33     69     404-80-109-15142 404-80-109-15152 404-80-109-15382 404-80-109-15412 404-80-109-15413 404-80-114-11103 404-80-114-11201 404-80-114-11203 404-80-205-5231 404-80-205-5233 404-80-205-5251 404-80-205-5252 404-80-205-5571 404-80-205-5572 404-80-206-6081 404-80-207-7552     52     u
    404     80     205     5392     539_V.P.Palayam_Erode_H1     11.29610833     77.66944444     120     60     3600     33     73     404-80-205-5593 404-80-205-5591 404-80-205-5493 404-80-205-5492 404-80-205-5393 404-80-205-5391 404-80-205-5283 404-80-205-5281 404-80-205-5163 404-80-205-5161 404-80-205-5133 404-80-205-5123 404-80-110-16762 404-80-110-16651 404-80-110-16612 404-80-110-16611     52     u
    404     80     232     32842     Thalaivasal_2     11.5698056     78.7496389     120     60     3000     43     80     404-80-107-13042 404-80-107-13441 404-80-107-13471 404-80-107-13473 404-80-2003-22253 404-80-232-32841 404-80-232-32843          u
    each row ends with "u"
    Edited by: Aemunathan on Sep 26, 2008 9:02 PM

  • ORA-22813: operand value exceeds system limits when generation XML

    Hi All,
    We are using Oracle 11GR2 database and I am trying to generate XML Files using SQL/XML Functions.
    I am in the end of development and while testing I am facing this freaking issue. ORA-22813: operand value exceeds system limits.
    SELECT XMLSERIALIZE(DOCUMENT DATA AS CLOB) AS DATA FROM (
              SELECT
              XMLELEMENT (
    "Region_Data",
    XMLAGG (
    XMLFOREST (
    R.region as "Region_Name",
    R.first_name||R.last_name as "EmployeeFullName",
    R.ntlogin as "EmployeeAlias",
    R.job_title as "EmployeeRole",
    R.sap_number as "SAPNumber",
    R.sales_transaction_dt AS "Day",
    R.region AS "RegionName",
    R.postpaid_totalqty AS "PostpaidCount",
    R.postpaid_totaldollars AS "PostpaidAmount",
    R.postpaidfeature_totalqty AS "PostpaidFeatureCount",
    R.postpaidfeature_totaldollar AS "PostpaidFeatureAmount",
    R.prepaid_totalqty AS "PrepaidCount",
    R.prepaid_totaldollars AS "PrepaidAmount" ,
    R.prepaidfeature_totalqty AS "PrepaidFeatureCount",
    R.prepaidfeature_totaldollars AS "PrepaidFeatureAmount",
    R.accessory_totalqty AS "AccessoriesCount",
    R.accessory_totaldollars AS "AccessoriesAmount",
    R.handset_totalqty AS "HandsetsCount",
    R.handset_totaldollars AS "HandsetsAmount",
    (SELECT XMLAGG (
    XMLELEMENT (
    "Division",
    XMLFOREST (
    di.division AS "DivisonName",
    di.postpaid_totalqty AS "PostpaidCount",
    di.postpaid_totaldollars AS "PostpaidAmount",
    di.postpaidfeature_totalqty AS "PostpaidFeatureCount",
    di.postpaidfeature_totaldollar AS "PostpaidFeatureAmount",
    di.prepaid_totalqty AS "PrepaidCount",
    di.prepaid_totaldollars AS "PrepaidAmount" ,
    di.prepaidfeature_totalqty AS "PrepaidFeatureCount",
    di.prepaidfeature_totaldollars AS "PrepaidFeatureAmount",
    di.accessory_totalqty AS "AccessoriesCount",
    di.accessory_totaldollars AS "AccessoriesAmount",
    di.handset_totalqty AS "HandsetsCount",
    di.handset_totaldollars AS "HandsetsAmount",
    (SELECT XMLAGG (
    XMLELEMENT (
    "District",
    XMLFOREST (
    dis.district AS "DistrictName",
    dis.postpaid_totalqty AS "PostpaidCount",
    dis.postpaid_totaldollars AS "PostpaidAmount",
    dis.postpaidfeature_totalqty AS "PostpaidFeatureCount",
    dis.postpaidfeature_totaldollar AS "PostpaidFeatureAmount",
    dis.prepaid_totalqty AS "PrepaidCount",
    dis.prepaid_totaldollars AS "PrepaidAmount" ,
    dis.prepaidfeature_totalqty AS "PrepaidFeatureCount",
    dis.prepaidfeature_totaldollars AS "PrepaidFeatureAmount",
    dis.accessory_totalqty AS "AccessoriesCount",
    dis.accessory_totaldollars AS "AccessoriesAmount",
    dis.handset_totalqty AS "HandsetsCount",
    dis.handset_totaldollars AS "HandsetsAmount",
    (SELECT XMLAGG (
    XMLELEMENT (
    "Store",
    XMLFOREST (
    mst.store_id AS "StoreNumber",
    mst.store_name AS "StoreLocation",
    mst.postpaid_totaldollars AS "PostpaidAmount",
    mst.postpaidfeature_totalqty AS "PostpaidFeatureCount",
    mst.postpaidfeature_totaldollar AS "PostpaidFeatureAmount",
    mst.prepaid_totalqty AS "PrepaidCount",
    mst.prepaid_totaldollars AS "PrepaidAmount" ,
    mst.prepaidfeature_totalqty AS "PrepaidFeatureCount",
    mst.prepaidfeature_totaldollars AS "PrepaidFeatureAmount",
    mst.accessory_totalqty AS "AccessoriesCount",
    mst.accessory_totaldollars AS "AccessoriesAmount",
    mst.handset_totalqty AS "HandsetsCount",
    mst.handset_totaldollars AS "HandsetsAmount"
    FROM stores_comm_mobility_info_vw mst
    WHERE mst.district = dis.district
    ) "Store_Data")))
    FROM diST_comm_mobility_info_vw dis
    WHERE dis.division = di.division
    ) "District_Data")))
    FROM div_comm_mobility_info_vw di
    WHERE di.region = r.region
    ) AS "Division_Data"))) AS DATA
    FROM reg_comm_mobility_info_vw R GROUP BY region)
    This is working fine for conditions where there is less amount of data, but when there is more data this query is failing.
    I do not know what to do now. Is there any way of this limit or do I need someother mechanisms to generate XML Files.
    The challenge is we need to generate XML Files and send the XML Data to an Interface which will use this data to display in a cell phone.
    I am really frustated now as I am getting this error when I am testing for huge amount of data.
    Appreciate if anyone can help me out ASAP.
    (tHE BELOW XML I am trying to generate)
    <REGION>
         <Region_Data>
              <Region_Name>Southwest</Region_Name>
              <EmployeeFullName>AllisonAndersen</EmployeeFullName>
              <EmployeeAlias>AANDERS60</EmployeeAlias>
              <EmployeeRole>District Manager, Retail Sales</EmployeeRole>
              <SAPNumber>P12466658</SAPNumber>
              <Day>JAN</Day>
              <RegionName>Southwest</RegionName>
              <PostpaidCount>52</PostpaidCount>
              <PostpaidAmount>1579.58</PostpaidAmount>
              <PostpaidFeatureCount>296</PostpaidFeatureCount>
              <PostpaidFeatureAmount>4174.19</PostpaidFeatureAmount>
              <AccessoriesCount>394</AccessoriesCount>
              <AccessoriesAmount>45213.87</AccessoriesAmount>
              <Division_Data>
                   <Division>
                        <DivisonName>Southern California</DivisonName>
                        <PostpaidCount>52</PostpaidCount>
                        <PostpaidAmount>1579.58</PostpaidAmount>
                        <PostpaidFeatureCount>296</PostpaidFeatureCount>
                        <PostpaidFeatureAmount>4174.19</PostpaidFeatureAmount>
                        <AccessoriesCount>394</AccessoriesCount>
                        <AccessoriesAmount>45213.87</AccessoriesAmount>
                        <District_Data>
                             <District>
                                  <DistrictName>Orange County West</DistrictName>
                                  <PostpaidCount>52</PostpaidCount>
                                  <PostpaidAmount>1579.58</PostpaidAmount>
                                  <PostpaidFeatureCount>296</PostpaidFeatureCount>
                                  <PostpaidFeatureAmount>4174.19</PostpaidFeatureAmount>
                                  <AccessoriesCount>394</AccessoriesCount>
                                  <AccessoriesAmount>45213.87</AccessoriesAmount>
                                  <Store_Data>
                                       <Store>
                                            <StoreNumber>9551</StoreNumber>
                                            <StoreLocation>TM - BROOKHURST &amp; WARNER</StoreLocation>
                                            <PostpaidAmount>10</PostpaidAmount>
                                            <PostpaidFeatureCount>22</PostpaidFeatureCount>
                                            <PostpaidFeatureAmount>319.89</PostpaidFeatureAmount>
                                            <AccessoriesCount>27</AccessoriesCount>
                                            <AccessoriesAmount>4330</AccessoriesAmount>
                                       </Store>
                                  </Store_Data>
                             </District>
                        </District_Data>
                   </Division>
              </Division_Data>
         </Region_Data>
    </REGION>
    Thanks,
    Madhu K.

    You didn't give any feedback in your previous thread.
    Did you try the approach suggested here in {message:id=10998557}, instead of using nested inline subqueries ?

  • How to get message Target value exceeded for value contract in consignment

    Hi Gurus,
    I have created a value contract in consignment process.
    When the TOTAL VALUE of the release orders exceed the TARGET value of the value contract, system is NOT alerting me with message "Target Value Exceedded".
    In normal value contracts, system throws error message while creating release order if target value is exceeded.
    How such message can be generated in case of consignment process?
    Is there is any configuration involved for item category 'K' for this requirement?
    Thanks in advance,
    Regards,
    Sastry

    Hi,
    Thanks for the reply.
    Those messages are already configured and they are working fine for my normal contracts.
    I need such messages for value contracts in consignment process (item category 'K').
    As there is  no net price in consignment PO, such messages are not generated even though required messages are already configured.
    Is there any other thing I need to do for CONSIGNMENT process
    Regards,
    Sastry

  • Want pull the PO's for those PO value exceeds certain limit.

    HI SAP Gurus,
    I Want pull the PO's report for those PO value exceeds certain limit ( Example I want to pull the PO's which value is more that 5 million USD for period of 1 year)
    Thanks and Regards,
    SHARAN.

    hi
    Try the table EKBE with fields WRBTR( invoice document amount) , DMBTR (Line item amount in the local currency for GRn Quantity) EBELN- (Purchase order). This will give you the details. Do check a test case with tolerance at Invoice level and post additional amount for Invoice and check the Table field updations.
    Also ,
    Try it in Tcode SE16
    table Name EKBE.
    Or,
    May be use can use standard report ME2N, with selection parameter: GUTSCHRIFT (Invoice exist), it will give you all the list of PO with invoice. Here you can check the conditions as you need.
    I hope it helps.
    Best Regards,
    Rahul.

Maybe you are looking for