LTP: how to increase the simulative requirements quantities?

Hello SAP experts,
Is there a way to increase a little bit the simulative requirements quantities, without using the scrap% (which has an impact on the finished material price)?
I have investigated the use of safety stock to increase the components demands, but obviously, in LTP, it is not considered as additional demand... But maybe I missed something...
Please, can you help me on that case?
Thanks in advance.
Regards,
Rudy

Hello Mario, thank you for your reply.
In fact, we have a demand, but the users are always ordering a little bit more that the results given by the LTP.
Now, we would like to have full control and full visibility on it.
So, the first idea was to define a scrap percentage that would increase a little bit the quantities.
But we can't use it, because it has an impact on the costing side for the material price, I think.
So, the second idea was to use the safety stock.
Unfortunately, LTP does not seem to see the safety stock as a demand (like in operative planning), but more as an opening stock...
Then, the 3rd idea was to use the rounding profile to add a percentage on the quantity, but it only applies on purchase orders, and not planned orders... No luck again...
So, none of our 3 ideas can be applied here! And I am searching for another good idea...

Similar Messages

How to increase the number of rows in Status Oveview iView in MSS?

Hi
We have implemented MSS and have a question regarding Status overview iview.
The standard status overview iview of the team workset has 5 rows and we have to scroll using the arrow buttons to select/view a request.
Now can anyone explain me how to increase the number of rows in this iview? Is this somthing that has to be accoplished through web dynpro customization?
I checked the options in iView property and do not see any option to increase the number of rows.
please help
Thanks
-Michael

Hi Micheal,
Well, I am not really sure, if you could accomplish this using customizing, but I am sure that you can accomplish this using the JDI. Well, you can extract the application's source code using JDI and then change the required display rows property and republish it.
Am not really sure if this is suggestable method for this requirement,but it can be achieved using this JDI stuff.
Regards
<b>Raja Sekhar</b><i></i>

How to increase the performance in server 2008 R2 for RDP users

Hi,
My application take to much time to load. If anyone double click on mail client the exe file will appear in task manager but it will open after 5 mins. how to increase the performance.
My sever configuration is as below,
SC2600 Intel motherboard with total 24 core processors and 32 GB RAM and 8 TB Hard Disk. RAID 5 is configured which has two lungs one is 167 GB for C drive and other is 4.5 TB for D drive.
There are 28 Thin-clients connected to server through L300 N computing Thin-clients.
Thin-clients connect to V-space server installed in server for RDP users to get connected.
we have installed around 20 applications including printer and scanner driver. And apps are has below,
Firefox browser, windows mail, Adobe acrobat XI, canon printer and scanner drivers, Epson printer and scanner driver, E scan anti-virus, office 2007, v space, power ISO, win-rar,Tally and e token drivers and some backup software's.
Below are the services and features enabled,
AD, File services, RDP, web server, Hyper-v, .net frame work.
Is there a way to increase the performance .
Very slow performance.

Hi,
what would you suggest on hardware configuration must be for above mentioned applications and services with those many users.
how many cores and ram size is required.

How to increase the length of internal table dynamically

How to increase the length of internal table dynamically depending on the number of fields fetched into the internal table ?
The requirement code :
types: begin of t_data,
         form          like zscr_data_hdr-form,
         werks         like zscr_data_hdr-werks,
         matnr         like zscr_data_hdr-matnr,
         verid         like zscr_data_hdr-verid,
         lot           like zscr_data_hdr-lot,
         lot_qty       like zscr_data_hdr-lot_qty,
         udate         like zscr_data_hdr-udate,
         utime         like zscr_data_hdr-utime,
         zuser         like zscr_data_hdr-zuser,
         processed     like zscr_data_hdr-processed,
         defect        like zscr_defect_data-defect,
         vornr         like zscr_route_data-vornr,
         fld1          like zscr_defect_data-defect_val,
         fld2          like zscr_defect_data-defect_val,
         fld3          like zscr_defect_data-defect_val,
         fld4          like zscr_defect_data-defect_val,
         fld5          like zscr_defect_data-defect_val,
         fld6          like zscr_defect_data-defect_val,
         fld7          like zscr_defect_data-defect_val,
         fld8          like zscr_defect_data-defect_val,
         fld9          like zscr_defect_data-defect_val,
         fld10         like zscr_defect_data-defect_val,
         fld11         like zscr_defect_data-defect_val,
         fld12         like zscr_defect_data-defect_val,
         fld13         like zscr_defect_data-defect_val,
         fld14         like zscr_defect_data-defect_val,
         fld15         like zscr_defect_data-defect_val,
         fld16         like zscr_defect_data-defect_val,
         fld17         like zscr_defect_data-defect_val,
         fld18         like zscr_defect_data-defect_val,
         fld19         like zscr_defect_data-defect_val,
         fld20         like zscr_defect_data-defect_val,
         fld21         like zscr_defect_data-defect_val,
         fld22         like zscr_defect_data-defect_val,
         fld23         like zscr_defect_data-defect_val,
         fld24         like zscr_defect_data-defect_val,
         fld25         like zscr_defect_data-defect_val,
         fld26         like zscr_defect_data-defect_val,
         fld27         like zscr_defect_data-defect_val,
         fld28         like zscr_defect_data-defect_val,
         fld29         like zscr_defect_data-defect_val,
         fld30         like zscr_defect_data-defect_val,
         fld31         like zscr_defect_data-defect_val,
         fld32         like zscr_defect_data-defect_val,
         fld33         like zscr_defect_data-defect_val,
         fld34         like zscr_defect_data-defect_val,
         fld35         like zscr_defect_data-defect_val,
         fld36         like zscr_defect_data-defect_val,
         fld37         like zscr_defect_data-defect_val,
         fld38         like zscr_defect_data-defect_val,
         fld39         like zscr_defect_data-defect_val,
         fld40         like zscr_defect_data-defect_val,
         fld41         like zscr_defect_data-defect_val,
         fld42         like zscr_defect_data-defect_val,
         fld43         like zscr_defect_data-defect_val,
         fld44         like zscr_defect_data-defect_val,
         fld45         like zscr_defect_data-defect_val,
         fld46         like zscr_defect_data-defect_val,
         fld47         like zscr_defect_data-defect_val,
         fld48         like zscr_defect_data-defect_val,
         fld49         like zscr_defect_data-defect_val,
         fld50         like zscr_defect_data-defect_val,
         fld51         like zscr_defect_data-defect_val,
         fld52         like zscr_defect_data-defect_val,
         fld53         like zscr_defect_data-defect_val,
         fld54         like zscr_defect_data-defect_val,
         fld55         like zscr_defect_data-defect_val,
         fld56         like zscr_defect_data-defect_val,
         fld57         like zscr_defect_data-defect_val,
         fld58         like zscr_defect_data-defect_val,
         fld59         like zscr_defect_data-defect_val,
         fld60         like zscr_defect_data-defect_val,
         fld61         like zscr_defect_data-defect_val,
         fld62         like zscr_defect_data-defect_val,
         fld63         like zscr_defect_data-defect_val,
         fld64         like zscr_defect_data-defect_val,
         fld65         like zscr_defect_data-defect_val,
         fld66         like zscr_defect_data-defect_val,
         fld67         like zscr_defect_data-defect_val,
         fld68         like zscr_defect_data-defect_val,
         fld69         like zscr_defect_data-defect_val,
         fld70         like zscr_defect_data-defect_val,
         fld71         like zscr_defect_data-defect_val,
         fld72         like zscr_defect_data-defect_val,
         fld73         like zscr_defect_data-defect_val,
         fld74         like zscr_defect_data-defect_val,
         fld75         like zscr_defect_data-defect_val,
         fld76         like zscr_defect_data-defect_val,
         fld77         like zscr_defect_data-defect_val,
         fld78         like zscr_defect_data-defect_val,
         fld79         like zscr_defect_data-defect_val,
         fld80         like zscr_defect_data-defect_val,
         fld81         like zscr_defect_data-defect_val,
         fld82         like zscr_defect_data-defect_val,
         fld83         like zscr_defect_data-defect_val,
         fld84         like zscr_defect_data-defect_val,
         fld85         like zscr_defect_data-defect_val,
         fld86         like zscr_defect_data-defect_val,
         fld87         like zscr_defect_data-defect_val,
         fld88         like zscr_defect_data-defect_val,
         fld89         like zscr_defect_data-defect_val,
         fld90         like zscr_defect_data-defect_val,
         fld91         like zscr_defect_data-defect_val,
         fld92         like zscr_defect_data-defect_val,
         fld93         like zscr_defect_data-defect_val,
         fld94         like zscr_defect_data-defect_val,
         fld95         like zscr_defect_data-defect_val,
         fld96         like zscr_defect_data-defect_val,
         fld97         like zscr_defect_data-defect_val,
         fld98         like zscr_defect_data-defect_val,
         fld99         like zscr_defect_data-defect_val,
         fld100         like zscr_defect_data-defect_val,
         fld101         like zscr_defect_data-defect_val,
         fld102         like zscr_defect_data-defect_val,
         fld103         like zscr_defect_data-defect_val,
         fld104         like zscr_defect_data-defect_val,
         fld105         like zscr_defect_data-defect_val,
         fld106         like zscr_defect_data-defect_val,
         fld107         like zscr_defect_data-defect_val,
         fld108         like zscr_defect_data-defect_val,
         fld109         like zscr_defect_data-defect_val,
         fld110         like zscr_defect_data-defect_val,
         fld111         like zscr_defect_data-defect_val,
         fld112         like zscr_defect_data-defect_val,
         fld113         like zscr_defect_data-defect_val,
         fld114         like zscr_defect_data-defect_val,
         fld115         like zscr_defect_data-defect_val,
         fld116         like zscr_defect_data-defect_val,
         fld117         like zscr_defect_data-defect_val,
         fld118         like zscr_defect_data-defect_val,
         fld119         like zscr_defect_data-defect_val,
         fld120         like zscr_defect_data-defect_val,
         fld121         like zscr_defect_data-defect_val,
         fld122         like zscr_defect_data-defect_val,
         fld123         like zscr_defect_data-defect_val,
         fld124         like zscr_defect_data-defect_val,
         fld125         like zscr_defect_data-defect_val,
         fld126         like zscr_defect_data-defect_val,
         fld127         like zscr_defect_data-defect_val,
         fld128         like zscr_defect_data-defect_val,
         fld129         like zscr_defect_data-defect_val,
         fld130         like zscr_defect_data-defect_val,
         fld131         like zscr_defect_data-defect_val,
         fld132         like zscr_defect_data-defect_val,
         fld133         like zscr_defect_data-defect_val,
         fld134         like zscr_defect_data-defect_val,
         fld135         like zscr_defect_data-defect_val,
         dayst         like zscr_data_hdr-dayst,
       end of t_data.
In this fld1 to fld135 are defined in internal table.
But if the number of fields are more than 135 then the program is going to short dump.
Some times fld1 to fid170 or more fields will be there in my internal table.
Please suggest me how to make my requirement dynamic and display this data fetched into this internal table onto a .XLS file in the presentation server ?

Hi
You can try to use the type string:
form like zscr_data_hdr-form,
werks like zscr_data_hdr-werks,
matnr like zscr_data_hdr-matnr,
verid like zscr_data_hdr-verid,
lot like zscr_data_hdr-lot,
lot_qty like zscr_data_hdr-lot_qty,
udate like zscr_data_hdr-udate,
utime like zscr_data_hdr-utime,
zuser like zscr_data_hdr-zuser,
processed like zscr_data_hdr-processed,
defect like zscr_defect_data-defect,
vornr like zscr_route_data-vornr,
fieldxx type string,
dayst like zscr_data_hdr-dayst,
end of t_data.
So you can save you informations of every fld<n> concatenating their values into fieldxx.
Max

How To Increase the Size of Memo Fields 4000 Char in WebCenter 11g?

How To Increase the Size of Memo Fields greater than 4000 Char in WebCenter Content (UCM) 11g?
I was able to increase the size of Memo field from 2000 Char to 4000 by setting parameter value MEMOFIELDSIZE=4000 . But the requirement is to increase the size more than 4000 around 7000 char but Database(Oracle 11G) is not supporting more than 4000 char.
Is there any other way to increase the size of Memo field?
Thanks in Advance!!
Regards
Ram

Hello All,
Thanks for your responses.
Let me explain the scenario again in detail:
1. we have three meta-data fileds xProductCategory,xProductFamily and xProducts
2. These fields are related with DCL feature and corresponding values are being stored in corresponding custom Views
3. xProducFamily is dependent of xProductCategory and xProduct is dependent on xProductFamily
4. currently, there are around 250 Product values and average name of Product can be of 25 Char, so if we are selecting all product values for some Contents then Product Values are being stored in DocMeta table as comma separated values with one space, so total characters are being very high than 4K Char.
5. Currently view that is storing the Product values, stores "Name" column instead of ID(like 1,2,3....)
6. And our Content Server is integrated with Oracle WebSenter Portal, where logic has written to retrieve the contents based on "Product Name" instead of "Product ID" and already we are in UAT phase.Currently we are not in situation to revert the changes from Product Name to Product ID.
7. Also if we are storing the values on the basis of Product ID, then again the issue may arise in Future, if the number of Products increased.
Hoping the issue explanation is clear now and waiting for some possible solution for increasing the length of memo field.
Thanks in Advance !!
Regards
Ram

How to increase the size of sort_area_size

How to increase the size of sort_area_size and what size should be according to the PROD database
Thanks

user10869960 wrote:
Hi,
Many Thanks Charles
Oracle does not recommend using the SORT_AREA_SIZE parameter unless the instance is configured with the shared server option. Oracle recommends that you enable automatic sizing of SQL working areas by setting PGA_AGGREGATE_TARGET instead. SORT_AREA_SIZE is retained for backward compatibility."
--How can i know the instance is configured with the shared server option or not?This might be a tough question to answer. A shared server configuration may be enabled, but the clients may still connect using dedicated sessions, in which case PGA_AGGREGATE_TARGET would still apply.
From
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_2088.htm
V$SESSION includes a column named SERVER which will contain one of the following for each of the sessions: DEDICATED, SHARED, PSEUDO, or NONE. As a quick check, you could query V$SESSION to see if any sessions are connected using a shared server connection.
From:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/manproc.htm
There are several parameters which are used to configure shared server support, as well as several views to monitor shared server.
As Robert mentioned, when the WORKAREA_SIZE_POLICY is set to AUTO, the SORT_AREA_SIZE setting is not used, unless a shared server configuration is in use.
--What default value is WORKAREA_SIZE_POLICY and SORT_AREA_SIZE ?From:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams157.htm
"Setting PGA_AGGREGATE_TARGET to a nonzero value has the effect of automatically setting the WORKAREA_SIZE_POLICY parameter to AUTO. This means that SQL working areas used by memory-intensive SQL operators (such as sort, group-by, hash-join, bitmap merge, and bitmap create) will be automatically sized. A nonzero value for this parameter is the default since, unless you specify otherwise, Oracle sets it to 20% of the SGA or 10 MB, whichever is greater."
Actually I am facing performence issue since long time till now i did not get the solution even i have raised SRs but i could not.When the issue occur system seems hang.what i monitored whenever hdisk0 and hdisk1 use 100% the issue occur.
Regards,
SajidWhen you say that you have had a performance issue for a long time, is it a performance problem faced by a single SQL statement, a single user, a single application, or everything on the server? If you are able to identify a single user, or SQL statement that is experiencing poor performance, I suggest starting with a 10046 trace at level 8 (wait events) or level 12 (wait events and bind variables) to determine why the execution appears to be slow. If you have not yet determined a specific user or SQL statement that is experiencing performance problems, you might start with either a Statspack Report or an AWR Report (AWR requires a separate license).
If you believe that temp tablespace usage may be a contributing factor to the performance problem, you may want to periodically run this query, which will indicate currently in use temp tablespace usage:
{code}
SELECT /*+ ORDERED */
TU.USERNAME,
S.SID,
S.SERIAL#,
S.SQL_ID,
S.SQL_ADDRESS,
TU.SEGTYPE,
TU.EXTENTS,
TU.BLOCKS,
SQL.SQL_TEXT
FROM
V$TEMPSEG_USAGE TU,
V$SESSION S,
V$SQL SQL
WHERE
TU.SESSION_ADDR=S.SADDR
AND TU.SESSION_NUM=S.SERIAL#
AND S.SQL_ID=SQL.SQL_ID
AND S.SQL_ADDRESS=SQL.ADDRESS;
{code}
The SID and SERIAL# returned by the above could then be used to enable a 10046 trace for a session. The SQL_ID (and CHILD_NUMBER from V$SESSION in recent releases) could be used with DBMS_XPLAN.DISPLAY_CURSOR to return the execution plan for the SQL statement.
You could also take a look in V$SQL_WORKAREA_ACTIVE to determine which, if any, SQL statement are resulting in single-pass, or multi-pass executions, which both access the temp tablespace.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

How to increase the database size

Hi All ,
Our Client is going to increase their customers from 3.5 million to 5 millions
(12 millions in future ) and there is no increase in the existing licenses..
At present we have very less space in Data base server. We are Going Live at the End of the Month.
How to increase the database size to meet the Client requirements.
we have to increase the No of Processerors etc...
Below are the details of Servers:
System Model: IBM,7040-681
Machine Serial Number: 830D5BF
Processor Type: PowerPC_POWER4
Number Of Processors: 2
Processor Clock Speed: 1904 MHz
CPU Type: 64-bit
Kernel Type: 64-bit
LPAR Info: 4 bgl-svr-biap
Memory Size: 4096 MB
Good Memory Size: 4096 MB
Note : Server is IBM P690.
1) System Lansdcape --> Two System Landsacpe ( Dev to Prod )
2) BW Version --> 3.5
3) SAP Basis --- > 6.4
4) No of Application servers currently having --> Only One Server
Can any body suggest me how to solve this.....
Thanks in Advance..
Kasi Chukka

Hi Kasi,
Your question is not very clear, from the looks of it, the load on your client's system will be doubling soon.
You need to look at the system stats on how the system is handling the current load, use transactions ST06, ST04 and ST02 to check if the DB hit ratios are as expected, the cpu idle time, the busy periods. Identify if there is large amounts of paging on the server(candidate for increase in real memory).
On AIX level, you will need to look at CPU / Memory usage.
On SAP Application server, you need to look at SAP Buffers.
On Oracle end, look at SGA stats, if it need to increase, the data growth that is current and estimated growth (DB02).
You will not get an exact answer to it, you will need to analyze the existing load and then estimate (guess). The hardware upgrade will also depend on what the client is willing to spend, its always a good practise to add 20% to what you have estimated as these figures are never accurate.
All the best.
Cheers,
Nisch

How to Increase the retreving size of instances using PAPI filters.

Hi,
How to Increase the retreving size of instances using PAPI filters.
In my engine database instance size exceeds 2500 then we are getting following exception.
If we login in to user workspace able to see the instances but while trying to retrieve from PAPI getting below exception and showing the user's inbox aize as 0.
In Process Admin console we set all the required parameters.
Still I m getting the same problem.
Can you please lgive mev the solution.
<Mar 23, 2010 8:58:24 PM SGT> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: fuego.ejbengine.EJBProcessControl_1zamnl_EOImpl.getInstancesByFilter(Lfuego.papi.impl.j2ee.EJBSecureEngineInfo;Ljava.lang.String;Lfuego.papi.Filter;)
java.lang.ClassCastException: cannot assign instance of java.util.HashSet to field fuego.view.FilterImpl.attributes of type java.util.List in instance of fuego.view.FilterImpl.
java.lang.ClassCastException: cannot assign instance of java.util.HashSet to field fuego.view.FilterImpl.attributes of type java.util.List in instance of fuego.view.FilterImpl
     at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2032)
     at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1212)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1953)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
Regards,
Bharath.
Edited by: bg57295 on Mar 24, 2010 6:45 PM

Hi Bharath,
Believe me, you have an incompatibility between different build#.
PAPI has an instance cache. When certain process has more instances than the maximum specified, the cache is switch to status OPEN. That means, that PAPI will not be able to resolve some instance queries using the information in the cache. When that occurs, PAPI forward all those queries to the engine.
The incompatibility introduced is in the communication between PAPI and Engine. So, you only get the exception when you have more instances than the maximum cache size.
Regards,
Ariel

How to increase the speed of Zoom on TIFF image

Hi everyone,
i m doing zooming operation on tiff image.
when i applied zoom in operation on image which have properties
Bit per sample =1
Image Length = 2200 Pixel
Image Width = 1700 Pixel
Resolution(x) = 200 dpi
Resolution(y) = 200 dpi
then it require 2 sec.
then i apply the same code with tiff image which have properties like,
Bit per sample =1
Image Length = 3300 Pixel
Image Width = 2500 Pixel
Resolution(x) = 300 dpi
Resolution(y) = 300 dpi
then it require 9 to 10 sec.
my code is:
RenderedImage src= oriRndImage[selectedButtonIndex];(orirndImage is Rendered
Iamge)
//Transfer Current RenderedImage object into BufferedImage object
Raster ra= currRimage.getData(); //it take time.
DataBuffer db = ra.getDataBuffer();
SampleModel sa = ra.getSampleModel();
ColorModel cm = currRimage.getColorModel();
final BufferedImage currImage = new
BufferedImage(cm,Raster.createWritableRaster(sa,db,null), false, new
Hashtable());
//Create new Bufferred Image
BufferedImage bi = new BufferedImage(zoomW,zoomH, BufferedImage.TYPE_INT_RGB);
Graphics2D g = bi.createGraphics();
double scaleW = (double)(zoomW)/(double)(prev_width);
double scaleH = (double)(zoomH)/(double)(prev_height);
transAtZoom = AffineTransform.getScaleInstance(scaleW,scaleH);
g.drawRenderedImage(src, transAtZoom);
can any one plz suggest me the way ,how to increase the speed. of Zoom effect?
how to handle this problem?
thnxs..

Are you using NI Vision IMAQ AVI Read Frame or anther method to read the AVI file?
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

How to increase the line items against the std no of line items in MIGO

hi,
I have PO with more than 100 line items
During GR system is showing the error message as
Maximum number of items F1 reached
What is the standard no of line items in MIGO
And how to increase the line items
Is there any notes to apply
plz give sutable solution
K.Raghuram

Do you get message F5727 "Maximum number of items in FI reached"? reason is that in FI the posting line has a three-digit line item number (BSEG-BUZEI).
SAP's note 117708 provides a modification. I am pasting solution below.
Via the summarization you can post documents with more than 999 items in
FI.
The modification required for this is small, in addition you have to
change 2 tables. The modification is carried out in FI not in invoice
verification.
To activate document summarization in FI proceed as follows:
- The changes are described in Note 36353 and for the
modification in Note 77161. You may also have to apply Note
67640 so that the document summarization affects inventory
management.
An advice for the notes:
36353: Solution point 3: Field name WERKS
77161: Solution point 2: Maintain table TTYPV with Transaction
SE16
- this has the following effects; you can no longer clear the
GR/IR clearing account on purchase order item level (but only
on purchase order level) and you can only display the FI data
summarized (also see Note 36353)

How to increase the font size of the report output in the printout.

Hi Team,
i have a requirement like to print the report output as a direct print from an internal table.I am using the below mentioned code, the output is printing fine but the Font size of the output text is so small so i need to increase the font size of the text of output data.
call function 'GET_PRINT_PARAMETERS'
   exporting
     immediately                    = 'X'
     line_count                     = 65
     line_size                      = 320
     mode                           = 'CURRENT'
     no_dialog                      = ' '
     release                        = 'X'
     user                           = sy-uname
   importing
     out_parameters                 = st_param
   exceptions
     archive_info_not_found         = 1
     invalid_print_params           = 2
     invalid_archive_params         = 3
     others                         = 4.
if sy-subrc eq 0.
    new-page print on parameters st_param no dialog.
could you please suggest me how to increase the font size while printing the report output..
Thanks in Advance.
Puneet.

hey,
in our system when we click on print. on widow is coming.
there is a properties button.
we click on it.
there FORMAT----AND then we select forat from there and then printing .
not sure. but check on ur system. is there properites button.
HI,
READ THIS,
You can specify attributes such as the character width and font size in the device type formatting yourself.
contact ur basis team .
in the report PRINT-CONTROL SIZE option is there. try to find more o this.

How to increase the size (Length and width) of check box

Hi All,
I have to increase the size of ( width and length) of check box, I have revised to check box topic in dev guide but didnt find any clue, i have also tried to use CCStyle class but that is also not working, I would appreciate if some can help me out on this. Thanks in advance , let me know if any clarification required.
Thanks
Pratap

Hi Pratap ,
I honestly don't know how to increase the size
But i am giving you an alternate solution : we can create two Images with check box type 1 ) with checked
2 ) with unchecked . ( you can create image of any size ) and get them displayed on OAF screen dynamically using switcher case .
Dynamically displaying image will give the illusion of check box being checked and unchecked .
keep this image moved to following media directory
eg : /oraapp/mfgtestcomn/java/oracle/apps/media .
Implement the switcher case , add the fire action to this Image Column , create a transient attribute and attach to this
column . Depending on the value returned by transient attribute display the image on the column .
Let me know if its not clear .
Keerthi

How to increase the DFF fields length

Hi Gurus,
its very urgent requirement ,how to increase the dff field length in standard page i.e self-service appraisal page,please help me
Regards,
Sreeni

Hi Ayaz/Sreese,
As per my requirement user enable the DFF Fields in perticuler pages in sshr module like PMS So ...i create the attribute columns and viewinstance through personlization create the column and i give the hight and lenght in column cration time i create the id like "XXApr" same id name i gave in DFF Field Names.....so i did like ....this is my approch.....
---u have any doubts fell free to post the mail..i fwd through screen shots then only u undershood ,([email protected])
Regards,
Srinivas

Long Term Planning: Simulative Order not covering the Simul.Requirements

Hello everybody,
Maybe someone has an idea what can be the reason of the following problem:
For some raw materials, the total of simulative requirements per day is not equal to the generated simulative order quantity.
For example:
For material RAW, I have:
13/01:
Simulative Planned Order, Qty = 100
Simulative Requirement, Qty = 40
Simulative Requirement, Qty = 40
Simulative Requirement, Qty = 10
Simulative Requirement, Qty = 10
Simulative Requirement, Qty = 10
Simulative Requirement, Qty = 10 ---> Total of Sim.Reqts = 120
I don't understand why the LTP RUN gives me this result...
Does somebody have an idea?
Thanks in advance for your help,
Regards,
Rudy

Thank you, but I finally got it...
The problem was that the MRP type of some raw materials had been changed from X0 to ND.
So we had old simulative planned orders that were not corresponding exactly to the simulative requirements...
Regards,
Rudy

How to increase the time for detect a device down on Prime 2.0

Hi,
I would like to know how to increase the time for detect when a device has lost connection, currently I monitor several stand alone Access Points that are paleced on differents locations connected to prime through 256 Mbps Links, so when the location has very high bandwith utilization, an e-mail notification about the unreachable Access Point is sent, but if we check te reachability, the Access Point is reachable, and we don´t want to receive to many of this notificatios,
thanks for your help

Go to the Console, Select the server --> configuration --> tuning tab,
Stuck Thread Max Time and Stuck Thread Timer Interval (give your required time)
This will definitely increase the Stuck Thread time interval.
or
by using work manager also you can define Stuck Thread Max Time interval by editing deployment descriptor file
<work-manager>
<name>wm_name</name>
<max-stuck-thread-time>30</max-stuck-thread-time>
<stuck-thread-count>5</stuck-thread-count>
</work-manager>

LTP: how to increase the simulative requirements quantities?

Similar Messages

Maybe you are looking for