Sapscript: Output is continuous or contains too many pages (more than 3)

Hi,
I have developed Sapscript form for printing out material documents.
When users try to print out document with 68 positions, they receive error in MB90 -
" Output is continuous or contains too many pages (>3)".
Message no. TD405
If they try to print out small document, for example 3 positions, everything is ok.
What I have to check now?
Thanks,
Sveta.
Edited by: Julius Bussche on Sep 24, 2008 10:24 AM

Hi,
    Try to check the page counters for each page format.
    How many Page formats are there in your Form?
Check the First Page Attributes,
Page Counter
Mode                     START
Numbering Type     ARABIC
    Output length     00
which is next page to First page
Check Next Page Attributes
Page counter
Mode                     INC
Numbering Type     ARABIC
Output length         00
which is next page to Next page
Regards
Bala Krishna

Similar Messages

Script error - Output is continuous or contain too many pages and get

Hi ,
I have added one more page (name affidvt ) to the existing script.
Previously
Cover page was calling next page as cover
first    page was calling next page as next
next   page as again next.
But after new addition of the page ( called as affidvt) it is now
Cover page was calling next page as cover
first    page was calling next page as next
next   page as affidvt.
When I test run this script it gives -
Output is continuous or contain too many pages and get
terminated.
Any solution ?

Check the page assignments again. Looks like at least 2 pages are calling each other.
-Cheers

Print message - Output is continuous or contains too many pages ( 4)

I have created a new page in SAPScript called COVER_PG and now when I attempt to print an invoice I get that message. I am using Esker to send an email to a recipient and then the message comes up. I am not sure what it means or how to fix it. Any help would be appreciated.

May be your ESKER can handle upto 4 pages only... Try with some less pages like 3 or so.. and see what happens...
Regards,
Naimesh Patel

Error MDX result contains too many cells (more than 1 million). (WIS 10901)

Hi,
We have developed an universe on BI query and developed report on it. But while running this BO query in Web Intelligence we get the following error
A database error occured. The database error text is: Error in MDDataSetBW.GetCellData. MDX result contains too many cells (more than 1 million). (WIS 10901)
This BO query is restricted for one document number.
Now when i check in the BI cube there are not more than 300-400 records for that document number.
If i restrict the BO query for document number, delivery number, material and acknowledged date then the query runs successfully.
Can anyone please help with this issue.

follow this article to get the mdx generated by the webi report.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/90b02218-d909-2e10-1988-a2ca74547900
then try to execute the same in mdxtest transaction in bw

MDX result contains too many cells - But relese note applied!!!!!!

Hi experts!
When I create a query with my infoview, it retrive me the following error:
<ERROR COMPONENT="WIS" ERRORCODE="10901" ERRORTYPE="USER" MESSAGE="Si è verificato un errore del database. Il testo dell'errore del database è: Errore in MDDataSetBW.GetCellData. MDX result contains too many cells (more than 1 million). (WIS 10901)" PREFIX="ERR">
I try to understand if there are some problems about the sap.notes. In particular I ask to the technical people if the following note had installed into my system:
Note 931479 - MDX: More than 1,000,000 instances per axis
The technical people said me that this note had been installed because the system is to level 23.
bold
Then what problem may be due the fact that my mdx is not able to contains more than 1 million of cell ?
bold
thank'you in advance !

Hi,
whats the release of the SAP BW System - including patch level ?
whats the release of the SAP BusinessObjects system including patch level ?
Ingo

MDX result contains too many cells - NUMC 6

Hi to all.
I'm using I bex query in order to retrieve the field to my universe.
I know that when there is an element defined as NUMC (6), some errors may occurs into the MDX extraction (e.g. MDX result contains too many cells (more than 1 million)).
Can I set everythink in my BEX query or in my universe definition in order to not change the caratcteristic in my SAP BW system ?
Indeed I will have some bureaucratic and formal problem to change the sap bw type definition of the caracteristics.
Thank'you in advance.

hi Ingo,
Are you sure ? Indeed when I try to run a query where I have a NUMC6 filed and another field there is the error attached above.
Instead when I run the same query without the NUMC6 field the query ends correctly.
Moreover I see in the "SAP Note 1378064" where I see in the "Reason and Prerequisites": The internal data types are incorrect due to NUMC(6). The conversion to integer is required.
But I don't know if this conversion is allowed in the Bex Query step or in the universe filed definition.
Any advice will be accepted !

Result set does not fit; it contains too many rows

Dear All,
We are in BI7 and running reports on Excel 2007. Even though number of rows limitation in Excel 2007 is more than 1Million, when I try to execute a report with more than 65k records of output, system is generating output only for 65k rows with message "Result set does not fit; it contains too many rows".
Our Patch levels:
GUI - 7.10
Patch level is 11
Is there any way to generate more than 65000 rows in Bex?
Thanks in advance...
regards,
Raju
Dear Gurus,
Could you please shed some light on this issue?
thanks and regards,
Raju
Edited by: VaraPrasadraju Potturi on Apr 14, 2009 3:13 AM

Vara Prasad,
This has been discussed on the forums - for reasons of backward compatibility I do not think BEx supports more that 65000 rows .... I am still not sure about the same since I have not tried out a query with more that 65K rows on excel 2007 but I think this is not possible...

While importing clip getting error "The file contains too many audio channels" in premiere pro cs5

Hey,
I am using video clips from sony digital hi8 camera and trying to import video clips (.mov) 720*480 fps 29.97 .But unable to get into premiere pro cs5.System configuration:
MAC 10.6.4
2.66ghz intel core i7
4gb ram
nvidia geforce gt 330 mn.
Error :
Actually ,i have checked the inspector panel and i found same infomation in
in this panel for both clips .please check these clips screen shoots seprately .
Actually i have a long video clip and i have scatterred this clip into 6 diffrent portions
where i am not able to import the last video clip.It is giving me same error "file contain too many audio channels"".
Regards
Manoj

I too am getting this error in Premiere CS5. I was digitizing a Broadcast VHS and since I did not have a breakout box, I hooked it up to a Sony DV deck so I could connect via firewire and capture inside Premiere. I was able to capture and import 1 of the 3 clips and it did have 4 audio channels attached to it. However, upon closer inspection only 2 channels had a waveform. I captured the other 2 clips the same way, but this time, Premiere give the error "The file contains too many audio channels."
Any ideas?

11g-[nQSError: 42029] Subquery contains too many values for the IN predicat

Hi,
I am having 2 reports one is for subquery which returns inputs to Main report. Actually the report was working fine in 10g. But in 11g we are gettting following error:
View Display Error
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 42029] Subquery contains too many values for the IN predicate.Please have your System Administrator look at the log for more details on this error. (HY000)
Please have your System Administrator look at the log for more details on this error.
Getting same error after modofying the parameter value MAX_EXPANDED_SUBQUERY_PREDICATES to 12000
Please suggest what could be the other reason it may fail or any other settings we need to check.
Regards,
ckeng

ckeng,
Normally the IN clause has restriction of 10000 values in general sql/plsql we will go with inline queries i think model your rpd to generate inner queries
select * from emp where dept_id in (Select distinct dept_id from dept);
or have a condition/filter on sub report and make one more inner report with sub-filter but definitely it will cause performance issues.
thanks,
Saichand.v

Document contains too many nodes error when extracting xml tag name

I Have a large xml file in which the tag contains ~: as the value.
Now I am trying to extract all the tags which have ~: as the value and store that column using the following query and insert into a table.
insert into space_md select distinct xmltype(extract(value(x), '/').getstringval()).getrootelement() COLUMN_NAME
from gt_xmltype_tab gt, TABLE(XMLSequence(extract(gt.xmlfile1, '/ROWSET/ROW/*'))) x
where instr(extract(value(x),'/').getstringval(),'~:') > 1;
The xml file was generated using dbms_xmlgen.getxml. Table has 48 columns and around 4000 rows.
My above insert query gave me an error of 31186 too many nodes error.
I am using oracle version 10.2.0.3.
Following are the set of commands I ran....
SQL> insert into gt_xmltype_tab(xmlfile1)
values(XMLType(bfilename('BKUP_RES','QC.xml'),nls_charset_id('AL32UTF8'))); 2
1 row created.
SQL> SQL>
SQL> insert into restore_space_metadata select distinct 'QC', xmltype(extract(value(x), '/').getstringval()).getrootelement() COLUMN_NAME
2 from gt_xmltype_tab gt, TABLE(XMLSequence(extract(gt.xmlfile1, '/ROWSET/ROW/*'))) x
3 where instr(extract(value(x),'/').getstringval(),'~:') > 1;
insert into restore_space_metadata select distinct 'QC', xmltype(extract(value(x), '/').getstringval()).getrootelement() COLUMN_NAME
ERROR at line 1:
ORA-31186: Document contains too many nodes
Is there a better way of extracting the xml tag element name based on the xmltag content?
There is one other table which has 172 columns but only 100 rows so it doesnt create any problem on that table.
But this QC table has less columns but many many rows...
Any suggestions

There is a requiremnent of taking centain type of data backup and restore it.
It was implemented on flat file approach which was giving errors.
So it was implemented using XML approach.
Read data, store in xml file and read from xml file and load it into table.
Further, found that dbms_xmlstore is not able to handle tag only with whitespace
and tried to use the loading xml file into xmltype table column and extract data.
XMLTYPE column also has same problem of ignoring whitespace when used with extractvalue functions.
So for the workaround I update xmlfile having only one more more whitespace in the tag to have ~: character once.
After restoring data from xml to table I would run update qeury to update ~: to " ".
Now instead of running blind update for all the tables and all the columns from ~: to " " I thouhgt whyy not create a xml file of tag having ~:
along with its tablename.
and thats where I found the problem of too many nodes...
THe insert query you saw is populating table for table_name and column_name with tag having only ~: in it.
I hope this gives you the fair idea of stuff I am doing.

CHECK/EXIT contains too many ABAP statements

Hi all,
I am working in BADI MIGO. I have included few INCLUDE program in it which is throwing the following error while activating it. Please let me know if any one have come across it.
<b>Jump is too great and cannot be generated... A control structure or routine with CHECK / EXIT contains too many ABAP statements....</b>
Waiting for your reply,
Thanks,
Venki

Same error for me.
I have to call a larger macro 60 times and so I can't activate the function module. If I call the macro only 50 times it works fine.
Any idea how to solve that without a complete redesign of the code (packing the macro into a new fuction module)
Thanks,
Christian

ORA-31186: Document contains too many nodes

Hi all,
DB version:
BANNER
Oracle Database 10g Enterprise Edition Release 10.1.0.5.0 - 64bi
PL/SQL Release 10.1.0.5.0 - Production
CORE     10.1.0.5.0     Production
TNS for HPUX: Version 10.1.0.5.0 - Production
NLSRTL Version 10.1.0.5.0 - Production i am getting the "ORA-31186: Document contains too many nodes" error when listitem nodes come more then 70,000.
my code like below.
l_xmldoc := '<listitems>
<listitem><homePhone>6666446666</homePhone><mobile>9988776655</mobile><emailaddr><![CDATA[[email protected]]]></emailaddr><deviceid>1</deviceid></listitem>
<listitem><homePhone>6666446666</homePhone><mobile>9988776656</mobile><emailaddr><![CDATA[[email protected]]]></emailaddr><deviceid>1</deviceid></listitem>
<listitem><homePhone>6666446666</homePhone><mobile>9988776657</mobile><emailaddr><![CDATA[[email protected]]]></emailaddr><deviceid>1</deviceid></listitem>
</listitems>';
SELECT EXTRACT(l_xmldoc,'/listitems/listitem')   into l_xmldoc FROM DUAL;--error raising here
SELECT EXTRACTVALUE( VALUE(t),'/listitem/emailaddr')
             ,EXTRACTVALUE( VALUE(t),'/listitem/mobile')
             ,EXTRACTVALUE( VALUE(t),'/listitem/homephone')
             ,EXTRACTVALUE( VALUE(t),'/listitem/deviceid')
BULK COLLECTION INTO t_table
FROM TABLE(XMLSEQUENCE(l_xmldoc)) t;Please help me to understand why this error occurs and how to resolve.
Thanks,
Ram

>
You can find a little bit extra info in the search errors section on OTN regarding doc's 10gR2:
* ORA-31186: Document contains too many nodes
Cause: Unable to load the document because it has exceeded the maximum allocated number of DOM nodes.
Action: Reduces the size of the document.
>
Check this discussion -- ORA-24817 and ORA-31186 (undocumented errors)
Somebody suggested - Increasing the shared_pool_size and the java_pool_size will fix this.
Please check,
Edited by: ranit B on Nov 27, 2012 4:37 PM

MDX result contains many cells. (more than 1 million)

Hi experts!!!
I have a webi report, but when i try to refresh te report, the report show me the following message:
The database error text is: Error in MDDataSetBW.GetCellData. MDX result contains many cells. (more than 1 million). (WIS 10901)
I was reading that this error is because the report has too many information but it can be solve.
I was reading the following sap notes:
1232751 (this note is for sap bw release 7)
931479 (this note is for sap bw 3.5 Package 17)
We have SAP BW 3.5 and package 22, for this reason this notes are not for me.
Do you know some sap note that solve this problem and works with my sap bw??
I will wait for your answer.
Ruddy Alvarado.

Hi!!
This is my mdx query:
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGRXW55RLOXZEFNWEPC11Z], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ], [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LGOGS5KO4DB7KIULHYQZDZRR], [Measures].[4LGOGSD972Z0Q72ARC139FYHJ], [Measures].[4LGOGSKXQ1KQ8TLQX63FJHX7B], [Measures].[4LGOGSSM906FRG57305RTJVX3], [Measures].[4LGOGT0ARYS5A2ON8U843LUMV], [Measures].[4LGOGT7ZAXDUSP83EOAGDNTCN], [Measures].[4LGOGWF77CFHK3BTU79KKHA3B], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [0CUST_SALES__0SALES_DIST].[LEVEL01].MEMBERS, [ZSIOCOPRO__ZSIOSABOR].[LEVEL01].MEMBERS ), [0CALDAY].[LEVEL01].MEMBERS ), [ZSIOCOPRO__ZSIOTAMAN].[LEVEL01].MEMBERS ), [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS ), [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS ), [0CUST_SALES__0SALES_OFF].[LEVEL01].MEMBERS ), { [0SOLD_TO__0REGION].[GT G20] } ) DIMENSION PROPERTIES [0CALDAY].[20CALDAY], [0CUST_SALES__0SALES_DIST].[10CUST_SALES__0SALES_DIST], [0CUST_SALES__0SALES_DIST].[20CUST_SALES__0SALES_DIST], [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0CUST_SALES__0SALES_OFF].[10CUST_SALES__0SALES_OFF], [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION], [ZSIOCOPRO__ZSIOSABOR].[5ZSIOCOPRO__ZSIOSABOR], [ZSIOCOPRO__ZSIOTAMAN].[5ZSIOCOPRO__ZSIOTAMAN] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [0CUST_SALES__0SALES_OFF].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ), [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS ), [0CUST_SALES__0SALES_DIST].[LEVEL01].MEMBERS ), [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS ), [ZSIOCOPRO__ZSIOTAMAN].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES [0CUST_SALES__0SALES_DIST].[20CUST_SALES__0SALES_DIST], [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0CUST_SALES__0SALES_OFF].[10CUST_SALES__0SALES_OFF], [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION], [ZSIOCOPRO__ZSIOTAMAN].[5ZSIOCOPRO__ZSIOTAMAN] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [0CUST_SALES__0SALES_OFF].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ), [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS ), [0CUST_SALES__0SALES_DIST].[LEVEL01].MEMBERS ), [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES [0CUST_SALES__0SALES_DIST].[20CUST_SALES__0SALES_DIST], [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0CUST_SALES__0SALES_OFF].[10CUST_SALES__0SALES_OFF], [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( [0CUST_SALES__0SALES_OFF].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ), [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS ), [0CUST_SALES__0SALES_DIST].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES [0CUST_SALES__0SALES_DIST].[20CUST_SALES__0SALES_DIST], [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0CUST_SALES__0SALES_OFF].[10CUST_SALES__0SALES_OFF], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( [0CUST_SALES__0SALES_OFF].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ), [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0CUST_SALES__0SALES_OFF].[10CUST_SALES__0SALES_OFF], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ] } ON COLUMNS , NON EMPTY CROSSJOIN( [0CUST_SALES__0SALES_OFF].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ) DIMENSION PROPERTIES [0CUST_SALES__0SALES_OFF].[10CUST_SALES__0SALES_OFF], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ] } ON COLUMNS , NON EMPTY { [0SOLD_TO__0REGION].[GT G20] } DIMENSION PROPERTIES [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[ZSIOCTCOR/ZSIO_BO_CXC]: SELECT { [Measures].[3Z4D1BQHVZ7VR5IJWHLKNPIL8], [Measures].[3Z4D1BY6EXTL9S202BNWXRHB0], [Measures].[3Z4D1BITD0M68IZ3QNJ8DNJVG], [Measures].[3Z4D1BB4U20GPWFNKTGW3LL5O], [Measures].[3Z4D1B3GB3ER79W7EZEJTJMFW], [Measures].[3Z4D1AGEQ7LMNE9UXH7IZDQAK], [Measures].[3Z4D1AVRS4T1ONCR95C7JHNQ4], [Measures].[480ABQOBFURXYE3L9IUXLSHNB] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [ZSIOCLIE__ZSIOTCOB].[LEVEL01].MEMBERS, [ZSIOCLIE__ZSIORUTA].[LEVEL01].MEMBERS ), [ZSIODAFA].[LEVEL01].MEMBERS ), [ZSIOCLIE].[LEVEL01].MEMBERS ), [ZSIOCLIE__ZSIOCET].[LEVEL01].MEMBERS ), [ZSIOAGENC].[LEVEL01].MEMBERS ), { [ZSIOCLIE__ZSIOREGIO].[90120] } ) DIMENSION PROPERTIES [ZSIOAGENC].[5ZSIOAGENC], [ZSIOCLIE].[2ZSIOCOSIM], [ZSIOCLIE].[2ZSIOLICRE], [ZSIOCLIE].[4ZSIOCLIE], [ZSIOCLIE__ZSIOCET].[5ZSIOCLIE__ZSIOCET], [ZSIOCLIE__ZSIOREGIO].[5ZSIOCLIE__ZSIOREGIO], [ZSIOCLIE__ZSIORUTA].[5ZSIOCLIE__ZSIORUTA], [ZSIOCLIE__ZSIOTCOB].[1ZSIOCLIE__ZSIOTCOB], [ZSIODAFA].[2ZSIODAFA] ON ROWS FROM [ZSIOCTCOR/ZSIO_BO_CXC]
[Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]: SELECT { [Measures].[4LGOQ5A0UT58OU46P0PO9LN4N] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS, [0CALDAY].[LEVEL01].MEMBERS ), [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS ), { [0SOLD_TO__0REGION].[GT G20] } ) DIMENSION PROPERTIES [0CALDAY].[20CALDAY], [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]
[Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]: SELECT { [Measures].[4LGOQ5A0UT58OU46P0PO9LN4N] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ), [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]
[Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]: SELECT { [Measures].[4LGOQ5A0UT58OU46P0PO9LN4N] } ON COLUMNS , NON EMPTY { [0SOLD_TO__0REGION].[GT G20] } DIMENSION PROPERTIES [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]
[Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]: SELECT { [Measures].[4LGOQ5A0UT58OU46P0PO9LN4N] } ON COLUMNS , NON EMPTY CROSSJOIN( [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ) DIMENSION PROPERTIES [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]
[Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]: SELECT { [Measures].[4LGOQ5A0UT58OU46P0PO9LN4N] } ON COLUMNS , NON EMPTY CROSSJOIN( [0CALDAY].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ) DIMENSION PROPERTIES [0CALDAY].[20CALDAY], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]
[Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]: SELECT { [Measures].[4LGOQ5A0UT58OU46P0PO9LN4N] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( [0CALDAY].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ), [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES [0CALDAY].[20CALDAY], [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]
How to put it on mdxtest??

Document contains some order item more than once - invoice verification

Hi,
we have one cross company stock transfer process in which when a billing is created in SD side, an IDOC will be triggered automatically and create an invoice verification at the MM side.
The problem is some of our billing of this process having an IDOC application error that said.
Document contains same order item more than once
Message no. M8321
Diagnosis
Under the following circumstances, you can settle an order item in an invoice received via EDI more than once:
- Goods-receipt-based Invoice Verification has been defined for the order item.
- The IDoc contains the delivery note numbers of the goods receipts.
System Response
If this is not the case, the system cancels posting of the IDoc.
Question:
1 - The funny thing is IDOC showing 51 IDOC error code message on status record of INVOIC. But the invoice verfication get created in PO history.
2 - I think this error is because we need to make the PO as GR-based Inverifcation. We have flagged it in Vendor master, and Info record, but this indicator is not flag automatically in the PO (and we cannot manually change the PO as this indicator is grey-out). How?
3 - how to solve this error?
Thanks

Once PO history is created, you cannot change the "GR-based-IV" flag. Two options are there before you.
1. Cancel all the GRs & Invoices posted in the STO then system will allow you to update the GR-based-IV flag. After updating this flag repost the GRs and invoices.
2. Create a new STO, now since you have updated the vendor maser & info-record, this flag will automatically get updated during the STO creation itself.
First option is tedious and should be selected only if you can go option 2 is not at all feasible

Error : Document contains same order item more than once in IDOC

We have Intercompany IDOCs getting created in our system. The
trigger for this is the Billing Document in the same system in
differenct company code. The MEssage type being used is INVOIC and the
basic type is INVOIC01.
The IDOC is in the status of 51 with the error message
Document contains same order item more than once
Message No : M8 321.
Can anyone tell me why raise this error and how to resolve it?
Thanks.

What I have recently learned is that in 6.0 SAP allows the same line item to be on an idoc multiple times. However, the item has to be GR-based-IV and there has to be a unique entry in the delivery note of the GR.   I have successfully tested this in my development system.
What I can't get to work is if the GRs have the same delivery note value.   What I think is happening is these GRs are not unique so SAP cannot match a GR with an IR so it fails with this error.
Here are the examples:
Works
GR# A           deliverynote/BOL    "abcd"
GR# B           deliverynote/BOL     "efgh"
Invoice idoc
e1edp02    qualifier 016          abcd
e1edp02    qualifier 016          efgh
Doesn't work:
GR# A           deliverynote/BOL    "abcd"
GR# B           deliverynote/BOL     "abcd"
Invoice idoc
e1edp02    qualifier 016          abcd
e1edp02    qualifier 016          abcd
If anyone knows of a way to make the second scenario work, I'd like to hear your solution.
Thanks
Sandra

Sapscript: Output is continuous or contains too many pages (more than 3)

Similar Messages

Maybe you are looking for