Not allowing a paragraph to be "split up"?

Hi,
Is there a way I can style a paragraph style to "not be split up between two text frames"? I mean, I don't want my body copy paragraph to be shown on the bottom of one text frame, and then continuing on the next frame. Instead the whole paragraph should be moved to the next text frame (so it won't be broken up).
Hope you can help :-)

You're welcome. It is unusual to force all lines in a Paragraph to stay together, but there is no one size fits all rule to this.
More often, the keep option used would be Keep with Next, used for a Headline. It would be unsightly to have Headline at the bottom of a text frame and the text start at the top of the next column.

Similar Messages

MaxDB: Table with many LONG fields does not allow an INSERT: ...?

Hi,
I have a table with many LONG fields (28). So far, everythings works fine.
However, if I add another LONG field I cannot insert a dataset anymore
(29 LONG fields).
Does there exist a MaxDB parameter or anything else I can change to make inserts possible again?
Thanks in advance
Michael
appendix:
- Create and Insert command and error message
- MaxDB version and its parameters
Create and Insert command and error message
CREATE TABLE "DBA"."AZ_Z_TEST02"
     "ZTB_ID"               Integer    NOT NULL,
     "ZTB_NAMEOFREPORT"           Char (400) ASCII DEFAULT '',
     "ZTB_LONG_COMMENT"                LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_00"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_01"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_02"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_03"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_04"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_05"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_06"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_07"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_08"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_09"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_10"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_11"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_12"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_13"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_14"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_15"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_16"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_17"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_18"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_19"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_20"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_21"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_22"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_23"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_24"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_25"         LONG ASCII DEFAULT '',
     "ZTB_LONG_TEXTBLOCK_26"         LONG ASCII DEFAULT '',
     PRIMARY KEY ("ZTB_ID")
The insert command
INSERT INTO AZ_Z_TEST02 SET ztb_id = 87
works fine. If I add the LONG field
"ZTB_LONG_TEXTBLOCK_27"         LONG ASCII DEFAULT '',
the following error occurs:
    Auto Commit: On, SQL Mode: Internal, Isolation Level: Committed
    General error;-7032 POS(1) SQL statement not allowed for column of data type LONG
    INSERT INTO AZ_Z_TEST02 SET ztb_id = 88
MaxDB version and its parameters
All db params given by
dbmcli -d myDB -u dbm,dbm param_directgetall > maxdb_params.txt
are
KERNELVERSION                         KERNEL    7.5.0    BUILD 026-123-094-430
INSTANCE_TYPE                         OLTP
MCOD                                  NO
RESTART_SHUTDOWN                      MANUAL
SERVERDBFOR_SAP                     YES
_UNICODE                              NO
DEFAULT_CODE                          ASCII
DATE_TIME_FORMAT                      INTERNAL
CONTROLUSERID                         DBM
CONTROLPASSWORD
MAXLOGVOLUMES                         10
MAXDATAVOLUMES                        11
LOG_VOLUME_NAME_001                   LOG_001
LOG_VOLUME_TYPE_001                   F
LOG_VOLUME_SIZE_001                   64000
DATA_VOLUME_NAME_0001                 DAT_0001
DATA_VOLUME_TYPE_0001                 F
DATA_VOLUME_SIZE_0001                 64000
DATA_VOLUME_MODE_0001                 NORMAL
DATA_VOLUME_GROUPS                    1
LOG_BACKUP_TO_PIPE                    NO
MAXBACKUPDEVS                         2
BACKUP_BLOCK_CNT                      8
LOG_MIRRORED                          NO
MAXVOLUMES                            22
MULTIO_BLOCK_CNT                    4
DELAYLOGWRITER                      0
LOG_IO_QUEUE                          50
RESTARTTIME                         600
MAXCPU                                1
MAXUSERTASKS                          50
TRANSRGNS                           8
TABRGNS                             8
OMSREGIONS                          0
OMSRGNS                             25
OMS_HEAP_LIMIT                        0
OMS_HEAP_COUNT                        1
OMS_HEAP_BLOCKSIZE                    10000
OMS_HEAP_THRESHOLD                    100
OMS_VERS_THRESHOLD                    2097152
HEAP_CHECK_LEVEL                      0
ROWRGNS                             8
MINSERVER_DESC                      16
MAXSERVERTASKS                        20
_MAXTRANS                             288
MAXLOCKS                              2880
LOCKSUPPLY_BLOCK                    100
DEADLOCK_DETECTION                    4
SESSION_TIMEOUT                       900
OMS_STREAM_TIMEOUT                    30
REQUEST_TIMEOUT                       5000
USEASYNC_IO                         YES
IOPROCSPER_DEV                      1
IOPROCSFOR_PRIO                     1
USEIOPROCS_ONLY                     NO
IOPROCSSWITCH                       2
LRU_FOR_SCAN                          NO
PAGESIZE                            8192
PACKETSIZE                          36864
MINREPLYSIZE                        4096
MBLOCKDATA_SIZE                     32768
MBLOCKQUAL_SIZE                     16384
MBLOCKSTACK_SIZE                    16384
MBLOCKSTRAT_SIZE                    8192
WORKSTACKSIZE                       16384
WORKDATASIZE                        8192
CATCACHE_MINSIZE                    262144
CAT_CACHE_SUPPLY                      1632
INIT_ALLOCATORSIZE                    229376
ALLOW_MULTIPLE_SERVERTASK_UKTS        NO
TASKCLUSTER01                       tw;al;ut;2000sv,100bup;10ev,10gc;
TASKCLUSTER02                       ti,100dw;30000us;
TASKCLUSTER03                       compress
MPRGN_QUEUE                         YES
MPRGN_DIRTY_READ                    NO
MPRGN_BUSY_WAIT                     NO
MPDISP_LOOPS                        1
MPDISP_PRIO                         NO
XP_MP_RGN_LOOP                        0
MP_RGN_LOOP                           0
MPRGN_PRIO                          NO
MAXRGN_REQUEST                        300
PRIOBASE_U2U                        100
PRIOBASE_IOC                        80
PRIOBASE_RAV                        80
PRIOBASE_REX                        40
PRIOBASE_COM                        10
PRIOFACTOR                          80
DELAYCOMMIT                         NO
SVP1_CONV_FLUSH                     NO
MAXGARBAGECOLL                      0
MAXTASKSTACK                        1024
MAX_SERVERTASK_STACK                  100
MAX_SPECIALTASK_STACK                 100
DWIO_AREA_SIZE                      50
DWIO_AREA_FLUSH                     50
FBM_VOLUME_COMPRESSION                50
FBM_VOLUME_BALANCE                    10
FBMLOW_IO_RATE                      10
CACHE_SIZE                            10000
DWLRU_TAIL_FLUSH                    25
XP_DATA_CACHE_RGNS                    0
DATACACHE_RGNS                      8
XP_CONVERTER_REGIONS                  0
CONVERTER_REGIONS                     8
XP_MAXPAGER                           0
MAXPAGER                              11
SEQUENCE_CACHE                        1
IDXFILELIST_SIZE                    2048
SERVERDESC_CACHE                    73
SERVERCMD_CACHE                     21
VOLUMENO_BIT_COUNT                    8
OPTIM_MAX_MERGE                       500
OPTIM_INV_ONLY                        YES
OPTIM_CACHE                           NO
OPTIM_JOIN_FETCH                      0
JOIN_SEARCH_LEVEL                     0
JOIN_MAXTAB_LEVEL4                    16
JOIN_MAXTAB_LEVEL9                    5
READAHEADBLOBS                      25
RUNDIRECTORY                          E:\_mp\u_v_dbs\EVERW_C5
_KERNELDIAGFILE                       knldiag
KERNELDIAGSIZE                        800
_EVENTFILE                            knldiag.evt
_EVENTSIZE                            0
_MAXEVENTTASKS                        1
_MAXEVENTS                            100
_KERNELTRACEFILE                      knltrace
TRACE_PAGES_TI                        2
TRACE_PAGES_GC                        0
TRACE_PAGES_LW                        5
TRACE_PAGES_PG                        3
TRACE_PAGES_US                        10
TRACE_PAGES_UT                        5
TRACE_PAGES_SV                        5
TRACE_PAGES_EV                        2
TRACE_PAGES_BUP                       0
KERNELTRACESIZE                       648
EXTERNAL_DUMP_REQUEST                 NO
AKDUMP_ALLOWED                      YES
_KERNELDUMPFILE                       knldump
_RTEDUMPFILE                          rtedump
UTILITYPROTFILE                     dbm.utl
UTILITY_PROTSIZE                      100
BACKUPHISTFILE                      dbm.knl
BACKUPMED_DEF                       dbm.mdf
MAXMESSAGE_FILES                    0
EVENTALIVE_CYCLE                    0
_SHAREDDYNDATA                        10280
_SHAREDDYNPOOL                        3607
USE_MEM_ENHANCE                       NO
MEM_ENHANCE_LIMIT                     0
__PARAM_CHANGED___                    0
__PARAM_VERIFIED__                    2008-05-13 13:47:17
DIAG_HISTORY_NUM                      2
DIAG_HISTORY_PATH                     E:\_mp\u_v_dbs\EVERW_C5\DIAGHISTORY
DIAGSEM                             1
SHOW_MAX_STACK_USE                    NO
LOG_SEGMENT_SIZE                      21333
SUPPRESS_CORE                         YES
FORMATTING_MODE                       PARALLEL
FORMAT_DATAVOLUME                     YES
HIRES_TIMER_TYPE                      CPU
LOAD_BALANCING_CHK                    0
LOAD_BALANCING_DIF                    10
LOAD_BALANCING_EQ                     5
HS_STORAGE_DLL                        libhsscopy
HS_SYNC_INTERVAL                      50
USE_OPEN_DIRECT                       NO
SYMBOL_DEMANGLING                     NO
EXPAND_COM_TRACE                      NO
OPTIMIZE_OPERATOR_JOIN_COSTFUNC      YES
OPTIMIZE_JOIN_PARALLEL_SERVERS        0
OPTIMIZE_JOIN_OPERATOR_SORT           YES
OPTIMIZE_JOIN_OUTER                   YES
JOIN_OPERATOR_IMPLEMENTATION          IMPROVED
JOIN_TABLEBUFFER                      128
OPTIMIZE_FETCH_REVERSE                YES
SET_VOLUME_LOCK                       YES
SHAREDSQL                             NO
SHAREDSQL_EXPECTEDSTATEMENTCOUNT      1500
SHAREDSQL_COMMANDCACHESIZE            32768
MEMORY_ALLOCATION_LIMIT               0
USE_SYSTEM_PAGE_CACHE                 YES
USE_COROUTINES                        YES
MIN_RETENTION_TIME                    60
MAX_RETENTION_TIME                    480
MAX_SINGLE_HASHTABLE_SIZE             512
MAX_HASHTABLE_MEMORY                  5120
HASHED_RESULTSET                      NO
HASHED_RESULTSET_CACHESIZE            262144
AUTO_RECREATE_BAD_INDEXES             NO
LOCAL_REDO_LOG_BUFFER_SIZE            0
FORBID_LOAD_BALANCING                 NO

>
Lars Breddemann wrote:
> Hi Michael,
>
> this really looks like one of those "Find-the-5-errors-in-the-picture" riddles to me.
> Really.
>
> Ok, first to your question: this seems to be a bug - I could reproduce it with my 7.5. Build 48.
> Anyhow, when I use
>
> insert into "AZ_Z_TEST02" values (87,'','','','','','','','','','','','','','','',''
>                                           ,'','','','','','','','','','','','','','','','')
>
> it works fine.
It solves my problem. Thanks a lot. -- I hardly can believe that this is all needed to solve the bug. This may be the reason why I have not given it a try.
>
Since explicitely specifying all values for an insert is a good idea anyhow (you can see directly, what value the new tupel will have), you may want to change your code to this.
>
> Now to the other errors:
> - 28 Long values per row?
> What the heck is wrong with the data design here?
> Honestly, you can save data up to 2 GB in a BLOB/CLOB.
> Currently, your data design allows 56 GB per row.
> Moreover 26 of those columns seems to belong together originally - why do you split them up at all?
>
> - The "ZTB_NAMEOFREPORT" looks like something the users see -
> still there is no unique constraint preventing that you get 10000 of reports with the same name...
You are right. This table looks a bit strange. The story behind it is: Each crystal report in the application has a few textblocks which are the same for all the e.g. persons the e.g. letter is created for. Principally, the textblocks could be directy added to the crystal report. However, as it is often the case, these textblocks may change once in a while. Thus, I put the texts of the textblock into this "strange" db table (one row for each report, one field for each textblock, the name of the report is given by "ztb_nameofreport"). And the application offers a menue by which these textblocks can be changed. Of course, the fields in the table could be of type CHAR, but LONG has the advantage that I do not have to think about the length of the field, since sometime the texts are short and sometimes they are really long.
(These texts would blow up the sql select command of the crystal report very much if they were integrated into the this select command. Thus it is realized in another way: the texts are read before the crystal report is loaded, then the texts are "given" to the crystal report (by its parameters), and finally the crystal report is loaded.)
>
- MaxDB 7.5 Build 26 ?? Where have you been the last years?
> Really - download the 7.6.03 Version [here|https://www.sdn.sap.com/irj/sdn/maxdb-downloads] from SDN and upgrade.
> With 7.6. I was not able to reproduce your issue at all.
The customer still has Win98 clients. MaxDB odbc driver 7.5.00.26 does not work for them. I got the hint to use odbc driver 7.3 (see [lists.mysql.com/maxdb/25667|lists.mysql.com/maxdb/25667]). Do MaxDB 7.6 and odbc driver 7.3 work together?
All Win98 clients may be replaced by WinXP clients in the near future. Then, an upgrade may be reasonable.
>
- Are you really putting your data into the DBA schema? Don't do that, ever.
> DBM/SUPERDBA (the sysdba-schemas) are reserved for the MaxDB system tables.
> Create a user/schema for your application data and put your tables into that.
>
> KR Lars
In the first MaxDB version I used, schemas were not available. I haven't changed it afterwards. Is there an easy way to "move an existing table into a new schema"?
Michael

Item category 02100 not allowed in accounting transactio 0300/0001 FB60

Hi,
ERROR MESSAGE : Item category 02100 not allowed in accounting transactio 0300/0001
The above error message is coming when trying to post in FB60 tcode ( Enter vendor invoice ).
please provide necessary information to rectify this problem.
regards,
Hari

Hi Balaji,
i checked in classify g/l accounts for document splitting ,
my g/l account is coming under item category 02100-Customer: Special G/L Transaction in spro.
Also i checked classify document types for document splitting
TYpe : KR
Des : Vendor Invoice
Transn: 0300
variant ": 0001
des : Vendor invoice
name : standard.
Actually g/l account for CANTEEN DEDUCTION.
Regards,
Hari priya

Table of contents will not allow additions

I am creating a portrait-oriented book. The TOC function is not allowing me to add paragraph styles nor is it automatically picking up the Chapter names. When I click the + symbol on the TOC inspector pane the only option I am given is "Add Section". In Preview my Front matter is properly listed in the TOC but the chapters are not there. What am I missing?
Alice
iBooks Author 2.0

KT -- Thanks for replying. I'm not sure exactly what you mean but it is all rather moot at this point. I reloaded the chapters into a Landscape template and found the TOC worked just great. The landscape format offers some nice benefits and I can let the reader decide whether he/she wants to read in portrait. Thanks again.

Item category is not allowed

hello all,
I am getting the below error " Item category 02000 not allowed in accounting transaction 0300/0001Message no. GLT2001".
while posting the FB60. New GL is activated in the system.
he is using   fb60
31    xyz           2500
40    121041     2500
Then i am getting the above error.....
The below details are from the Classify GL A/c for Document Splitting. Step.....
Acct from    Acct to       Category             Description
100000          100409        04000             Cash Account
112000          112040        01000                Balance Sheet Account
121000          125310        02000             Customer
125500          125500        01000             Balance Sheet Account
130000          135510        06000             Material
141020          159999        01000             Balance Sheet Account
160000       170200        07000             Fixed Assets
180000          192050        01000             Balance Sheet Account
199999          199999        01000            Balance Sheet Account
211000          211030        03000            Vendor
211040          211050        01000            Balance Sheet Account
Regards
Kumar

Hi
From the example provided by you, it seems you had not clasified any expenses / Income account. In case of FB60, the 40 posting key can't be any reconciliation account. Can you confimr what is the description of the G/L you are posting using posting key 40.
Based on that we can proceed further to correct the issue reported by you.
Regards
R.Karthigayan

Item category 06000 not allowed in accounting transaction 1000/0001

Hi,
We try post following entry and getting this error.
Debit    Exp. --- 50
Credit   Exp -
40
Credit   Out bank----
10.
Please help out with solution.I cannot deactivate document splitting.

HI,
The problem is G/L account xxxx. In IMG customizing [Classify G/L
accounts for document splitting], this account is classified as
material which has item category 06000 assigned. However, as you
mentioned, the document type does not allow this item category, so
the error is issued here.
Please change the assignment of item category for G/L account xxxxx
to either Revenue(30000) or Expense(20000) depending on your business
requirement. This should solve the problem.
reg
Madhu

In MIRO screen, if clicked on 'TAX' tab error 'Entry of tax not allowed in

Hi,
In MIRO screen, if clicked on 'TAX' tab error 'Entry of tax not allowed in current account line' is displayed. Message number FF847. What may be the reason for this error message?
Entry of tax not allowed in current account line
Message no. FF847
Diagnosis
If you enter a tax amount in the current account line, the system does not allocate the amount to one tax code, but instead to all tax codes that exist in the document. In this case, the amount needs to be split up using the rule-of-three procedure. The sum of the computed taxes of all tax codes is used as the comparison basis. If each of the computed tax amounts of all tax codes equals zero, the system uses the sum of the tax base values as the comparison basis.
System Response
If the respective comparison basis equals zero, the system issues an error message.
Procedure
Go to the tax screen or tax tab page and enter the appropriate tax amounts for each tax code.

Hi,
Please check SAP Note- 1551857 for the same.
Other terms
FF707, FF716, FF796, FF847, FB70, SAPLTAX1
Reason and Prerequisites
There is a program error.
Solution
Implement the program corrections.
When you choose "Cancel" on the tax screen during posting or simulation, the system returns to FB60 or MIRO again.
The message FF 847 on the "Basic data" tab page is suppressed for company codes with jurisdiction codes if no expense items exist.
Hope this will resolve your query.
Regards,
Sandesh Sawant

Item catagory 06000 not allowed in accounting transaction 0200/0001

Hi Guru's,
My client wants to sell Raw Material & pass the entry in the system but now system gives an error message Item catagory 06000 not allowed in accounting transaction 0200/0001
Document spliting is activated in our company.
whether to use revenue instend of material catagory?
Please help me.
Thanks & Regds
Santosh Rothe

Hi,
First please check what Item Category is assigned against the relevant GL account.
Financial Accounting (New)-General Ledger Accounting (New)-Business Transactions-Document Splitting-Classify G/L Accounts for Document Splitting
Then check what accounting transactions are allowed for the item category
Financial Accounting (New)-General Ledger Accounting (New)-Business Transactions-Document Splitting-Extended Document Splitting-Define Document Splitting Rule.
You will have an idea what to change here.
Regards,
Saravan Kanuparthy

U201CItem category 02000 not allowed in accounting transaction 0300/0001

Hi,
Hello Friends
I am posting a accounting document through F-02 then its gave an error message: u201CItem category 02000 not allowed in
accounting transaction 0300/0001u201D.
The accounting entry the client wants is
DR 29 1000145 VENDOR
CR 11 60001 CUSTOMER
Please help me
Thanks & Regards,
Arman
Edited by: akausar on Mar 4, 2011 2:46 PM

Hi,
02000 is a Customer Item category and 0300 is related to vendor transactions. Try adding Customer Item category 02000 in business transaction 0300.
SPRO-Financial accounting (New)-General Ledger Accounting (New)-Business Transactions-Document Splitting-Extended document splitting-Define business transaction variant.
Select Vendor Invoice-0300 and assigned Item categories, then enter Business transaction 0001
Enter Customer Item category
If you want document splitting based on customer relating to this business transaction, then do this step also
Add Item category 80000 in business transaction 0300/0001 in Define document splitting rule.
Regards,
Radhika.
Edited by: Balaji Radhika on Mar 4, 2011 10:59 AM

Idoc in error while trying to post vendor invoice(higher items not allowed)

Hi All,
we have two SAP systems. SAP A and SAP B.
SAP A is the vendor for SAP B system we have created a sales order/delivery/out bound invoice in SAP A system.The sales order has BOM material with main item and sub items. We have the same material master data and BOM master data in system A and system B since we are following split architecture.
The outbound invoice(with main and sub item) in system A has generated an outbound idoc and the idoc has gone to SAP
system B. There are the usual segments like E1EDP01 for main item and another E1EDp01 for the sub itmes in the outbound
idoc.The message type is INVOIC and basic type INVOIC02 with no extension.
In system B, the inbound idoc (coming from system A) has failed giving the error message "higher level items not allowed". The
segment E1EDP01 for sub item is highlighted in red ! basically the inbound idoc in sap system B is posting a vendor
invoice since the inbound idoc in B is calling the FM IDOC_INPUT_INVOIC_MRM... I think this is doing vendor invoice
verification.
I have checked in system A, all is ok and the outbound idoc is ok but the issue is in sap system B, the inbound idoc has failed
with message "higher level items not allowed". The segment E1EDP01 for sub item is highlighted in red in inbound idoc in
system B. The segments are the same for inbound idoc in B and outbound idoc in A.
Can someone pls tell what is wrong in system B.(config or data issue) as we are managing both systems.
regds
Edited by: sapsd73 on Jul 9, 2010 3:26 PM
Edited by: sapsd73 on Jul 9, 2010 3:27 PM

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

Transfer to R/3 using mixed periodicities is not allowed

Hi,
We are in the process of implementing DP for one of our clients,
We are facing the following problem, while releasing the Demand ( as PIR) to SAP R/3.
Transfer to R/3 using mixed periodicities is not allowed
We have maintained below mentioned steps;
1.Periodicities of Planning area maintained only weekly buckets.
2. Maintain Transfer Profile (SAPAP/MC8U)
3. Define activities for Mass Processing (SAPAPO/MC8T)
4. Create Demand Planning for Background job
(SAPAPO/MC8D)
5. Schedule demand planning in Background (SAPAPO/MC8G)
6. Through SM37 I checked the Spool List.*Error: Transfer to
R/3 using mixed periodicities is not allowed*
Kindly request if anyone knows provide solution.
Regards
Sadasivam R K

I think you can have only month, quarter and year in your storage bucket profile when you release forecast to ECC.
Anything lesser than that will give you an error when you release forecast to ECC.
If you want to send forecasts in weekly buckets, then you need to maintain the period split profile (Transaction /SAPAPO/SDP_SPLIT - Maintain Period Split Profile ) and assign this profile to the transfer profile.

Does not allow to set time characteristics while performing Partition

I had loaded the monthly inventory cube without setting any partition.
Now, when I tried to partition the cube thru RSDCUBE >> Change >> DB performance >> Partition, the time characteristic is greyed off and does not allow to set.
Is it becuase the cube had been loaded? Can I perform the partition now that I had compressed the request in the cube?

Yes you are correct....You want to modify an InfoCube into which data has already been loaded. You use remodeling to change the structure of the object without losing data.
You use partitioning to split the total dataset for an InfoProvider into several, smaller, physically independent and redundancy-free units. This separation improves system performance when you analyze data delete data from the InfoProvider.
You can only partition a dataset using one of the two partitioning criteria u2018calendar monthu2019 (0CALMONTH) or u2018fiscal year/period (0FISCPER). At least one of the two InfoObjects must be contained in the InfoProvider.
But you are trying to partition the cube which already has data so...You choose Repartitioning...
Repartitioning can be useful if you have already loaded data to your InfoCube, and:
●      You did not partition the InfoCube when you created it.
●      You loaded more data into your InfoCube than you had planned when you partitioned it.
●      You did not choose a long enough period of time for partitioning.
●      Some partitions contain no data or little data due to data archiving over a period of time.
Let me know if you need help with the steps to perform repartitioning

Content not allowed problems

On posting a reply to this thread ...
which study guides are good for 10g oca?
Yes this thread
which study guides are good for 10g oca?
I seemed to get a lot of content not allowed unless I split to several posts.
Evidently it is a not that I am restricted to one hyperlink per post ( I thoight it might be that)
Anyone any thoughts ... or am I just having a crazy moment?

user999999 wrote:
is there a link where they are compared? last time I used ucertify, but I was disappointed, as in ucertify I was scoring around 95% whereas in the real exam I just about passed.The Oracle Approved Practice Test supplier (Kaplan IT) is here: [http://www.oracle.com/global/us/education/certification/sts.html]
Transcender and Selftestsoftware may use some or even a lot of the same material .... Basically you pay a bit more for Transcender compared to Selftestsoftware and you get a little more.
I have never used them myself but understand them to be of good quality.
see: [http://blogs.oracle.com/certification/2009/12/0099.html]
A lot of practice test suppliers source back to the same dodgy material and should be avoided ... see http://blogs.oracle.com/certification/2009/05/the_route_you_choose.html
Ucertify is certainly regarded by http://www.certguard.com as a legitimate supplier (ucertify.com = SAFE ... checked at tiem of post), and they sometimes offer exams the official suppliers do not. Several comments I have seen indicate SOME of their material is not of the highest quality and may not stress you as much as the real exam. That said they appear to taking trouble to produce original material and get exams quickly to market, and seem to price competively when necessary. They may well be trying to improve there precieved quality issues in the marketplace.
( I apologise for many splits in this reply ... I have had a lot of content not allowed).
Edited by: bigdelboy on 12-Jan-2010 03:49 As one can see ... I have managed to integrate the messages I have used previously and managed to post them to this forum. I did have a few network issues at the time of the last post so perhaps that was it .... perhaps I am gong a insane after all. I don't believe I had removed anything significant. But perhaps I am wrong.

Error Item Category 04000 not allowed in accounting transaction 0300/0001

When we are posting a Incoming payment document with debit to -bank charges refund and bank account ,got the error Item Category 04000 not allowed in accounting transaction 0300/0001.
Please advice.
Edited by: mysap query on Feb 24, 2009 2:56 AM

Hi
This issue is related to document splitting. Unfortunately I don't have access to an ECC6 system today so can't give you the specific solution, however you need to check the config settings in the following path:
IMG > Financial Accounting (New) > General Ledger Accounting (New) > Business Transactions > Document Splitting > Classify Document Types for Document Splitting
If you are unable to resolve this, you should ask for assistance from a FI consultant.
Regards
Kylie

Posting in foreign currency not allowed for external tax system

Hello all,
I created a purchase order for inter-company stock transfer. Then created a corresponding outbound delivery and goods issue using VL10h and completed goods issue. Then I completed good receipt using MIGO. When I was trying to create a sales order I got this message "Posting in foreign currency not allowed for external tax system". What could be the reasons for this message. The message number said FS885.
One final note. I am able to create Billing document with manual batch number input in Delivery document item. But when I am using Batch split I am not able to generate invoice. Can anyone tell me what could be the problem here.

Hi Samir,
The Goods Received NI (Allocation Cost Account) need to be balaned in Local and System Currency as this is a Multi Currency account and these are the currencies that Business One will offer reports in.
The Foreign Currency for this account is irrelevant as you can never get a balance in FC for a multi currency account, neither will you find any reports for this.
If the client insists you can create a manual Journal entry in FC only to correct this. Business One does not offer any functionality to correct the Foreign Currency in this scenario. (like Exchange Rate difference for Local Currency and Conversion Differences for System Currency)
To do the manual JE open the form settings and the tab 'table', here untick the box 'From FC Field'. This will enable you to create a FC JE only.
Hope it clarifies the issue.
Jesper

Not allowing a paragraph to be "split up"?

Similar Messages

Maybe you are looking for