Regarding assigning Maintain DB-Storage Parameters

hai
i fotgot to assing the 'Maintain DB-Storage Parameters' for Transfer Structure.I already activated the TR.Then this option 'Maintain DB-Storage Parameters' is disabled.
So how can i enable that option for assing the DB-storage parameters.
pls tell me
i ll assing the points
bye
rizwan

hi Rizwan,
you may want take a look
http://help.sap.com/saphelp_nw2004s/helpdata/en/a7/214538821ae027e10000009b38f8cf/frameset.htm
hope this helps.

Similar Messages

Regarding Maintain DB Storage Parameters

hai
we have data in Oracle data tables.
I heard that while creating chracteristics , i need to give 'MAintain DB Storage Parameters' in "Extra" on menu bar.
Can anyone explain why we need to give 'Maintain DB Storage PArameters' here and what is advatage and its funcationality pls
i ll assign the points
bye
rizwan

You have to maintain Data Class and Size Category. These things are basically used for Database settings as below.
As it is in my experience we don't fill anything in this option.
Data Class
With the data type, you determine, on a logical level, in which physical area of the database (of the TABLESPACE with ORACLE) your table is stored. With the correct choice of data type, your table is automatically assigned to the correct area when creating on the database.
The most important data types (apart from the system data) are:
APPL0    Master data
APPL1    Transaction data
APPL2    Organization and customizing data
With Master data, you are dealing with data that is often accessed read, but that is rarely activated. Transaction data is data that is often actualized. Organization and customizing data is data that is entered when setting the system, and is later rarely changed.
There are two additional data types USR and USR1 that the customers can use. These are intended for customer-own developments. The tables assigned to these data types are stored in a tablespace for customer developments.
Note:Please note that the data type only has an influence on storing the table for the database systems ORACLE and INFORMIX.
If this field is empty, then the value is respectively transferred from the table that is already saved. If the characteristic is new, meaning no saved tables yet exist, then data type APPL0 is used as default.
Size Category
Determining the expected space requirement of a table on the database.
You can choose category 0 to 4 for your table. With this, a certain fixed size for a storage of the database is assigned to a category. When creating a table, an blank space is reserved on the database for this; If it later needs more space, then the storage space is added correspondingly to the category chosen here.
Use F4 on the field Size category to see the number of data records, that can be maintained with the individual categories for your table without any complications arising (for example, for required reorganisations because the maximum space to be reserved for the table , due to the maintained size category, was overwritten).
If this field is empty, then the value is respectively transferred from the saved table that already exists. If the characteristic is new, meaning no saved tables yet exist, then category 0 is used as default.
Regs
Gopi.

Maintain DB storage parameter

Hello,
is anyone familiar with the option for DSOs, Cubes etc. to maintain DB storage parameters?
I would be interested in the impact oof adjusting this option? What is technically happening, when changing these settings?
Thank You!
Goliad

HI,
The main reason for separating the table spaces is easy monitoring as u know which data is lying where moreover there are several other benefits also like u can take backup at individual table space level. This helps in trouble shooting also.
The separation of table spaces is database depended.
Regards
Ravish

Oracle Table Storage Parameters - a nice reading

bold Gony's reading excercise for 07/09/2009 bold -
The below is from the web source http://www.praetoriate.com/t_%20tuning_storage_parameters.htm. Very good material.The notes refers to figures and diagrams which cannot be seen below. But the text below is ver useful.
Let’s begin this chapter by introducing the relationship between object storage parameters and performance. Poor object performance within Oracle is experienced in several areas:
Slow inserts Insert operations run slowly and have excessive I/O. This happens when blocks on the freelist only have room for a few rows before Oracle is forced to grab another free block.
Slow selects Select statements have excessive I/O because of chained rows. This occurs when rows “chain” and fragment onto several data blocks, causing additional I/O to fetch the blocks.
Slow updates Update statements run very slowly with double the amount of I/O. This happens when update operations expand a VARCHAR or BLOB column and Oracle is forced to chain the row contents onto additional data blocks.
Slow deletes Large delete statements can run slowly and cause segment header contention. This happens when rows are deleted and Oracle must relink the data block onto the freelist for the table.
As we see, the storage parameters for Oracle tables and indexes can have an important effect on the performance of the database. Let’s begin our discussion of object tuning by reviewing the common storage parameters that affect Oracle performance.
The pctfree Storage Parameter
The purpose of pctfree is to tell Oracle when to remove a block from the object’s freelist. Since the Oracle default is pctfree=10, blocks remain on the freelist while they are less than 90 percent full. As shown in Figure 10-5, once an insert makes the block grow beyond 90 percent full, it is removed from the freelist, leaving 10 percent of the block for row expansion. Furthermore, the data block will remain off the freelist even after the space drops below 90 percent. Only after subsequent delete operations cause the space to fall below the pctused threshold of 40 percent will Oracle put the block back onto the freelist.
Figure 10-83: The pctfree threshold
The pctused Storage Parameter
The pctused parameter tells Oracle when to add a previously full block onto the freelist. As rows are deleted from a table, the database blocks become eligible to accept new rows. This happens when the amount of space in a database block falls below pctused, and a freelist relink operation is triggered, as shown in Figure 10-6.
Figure 10-84: The pctused threshold
For example, with pctused=60, all database blocks that have less than 60 percent will be on the freelist, as well as other blocks that dropped below pctused and have not yet grown to pctfree. Once a block deletes a row and becomes less than 60 percent full, the block goes back on the freelist. When rows are deleted, data blocks become available when a block’s free space drops below the value of pctused for the table, and Oracle relinks the data block onto the freelist chain. As the table has rows inserted into it, it will grow until the space on the block exceeds the threshold pctfree, at which time the block is unlinked from the freelist.
The freelists Storage Parameter
The freelists parameter tells Oracle how many segment header blocks to create for a table or index. Multiple freelists are used to prevent segment header contention when several tasks compete to INSERT, UPDATE, or DELETE from the table. The freelists parameter should be set to the maximum number of concurrent update operations.
Prior to Oracle8i, you must reorganize the table to change the freelists storage parameter. In Oracle8i, you can dynamically add freelists to any table or index with the alter table command. In Oracle8i, adding a freelist reserves a new block in the table to hold the control structures. To use this feature, you must set the compatible parameter to 8.1.6 or greater.
The freelist groups Storage Parameter for OPS
The freelist groups parameter is used in Oracle Parallel Server (Real Application Clusters). When multiple instances access a table, separate freelist groups are allocated in the segment header. The freelist groups parameter should be set the number of instances that access the table. For details on segment internals with multiple freelist groups, see Chapter 13.
NOTE: The variables are called pctfree and pctused in the create table and alter table syntax, but they are called PCT_FREE and PCT_USED in the dba_tables view in the Oracle dictionary. The programmer responsible for this mix-up was promoted to senior vice president in recognition of his contribution to the complexity of the Oracle software.
Summary of Storage Parameter Rules
The following rules govern the settings for the storage parameters freelists, freelist groups, pctfree, and pctused. As you know, the value of pctused and pctfree can easily be changed at any time with the alter table command, and the observant DBA should be able to develop a methodology for deciding the optimal settings for these parameters. For now, accept these rules, and we will be discussing them in detail later in this chapter.
There is a direct trade-off between effective space utilization and high performance, and the table storage parameters control this trade-off:
For efficient space reuse A high value for pctused will effectively reuse space on data blocks, but at the expense of additional I/O. A high pctused means that relatively full blocks are placed on the freelist. Hence, these blocks will be able to accept only a few rows before becoming full again, leading to more I/O.
For high performance A low value for pctused means that Oracle will not place a data block onto the freelist until it is nearly empty. The block will be able to accept many rows until it becomes full, thereby reducing I/O at insert time. Remember that it is always faster for Oracle to extend into new blocks than to reuse existing blocks. It takes fewer resources for Oracle to extend a table than to manage freelists.
While we will go into the justification for these rules later in this chapter, let’s review the general guidelines for setting of object storage parameters:
Always set pctused to allow enough room to accept a new row. We never want to have a free block that does not have enough room to accept a row. If we do, this will cause a slowdown since Oracle will attempt to read five “dead” free blocks before extending the table to get an empty block.
The presence of chained rows in a table means that pctfree is too low or that db_block_size is too small. In most cases within Oracle, RAW and LONG RAW columns make huge rows that exceed the maximum block size for Oracle, making chained rows unavoidable.
If a table has simultaneous insert SQL processes, it needs to have simultaneous delete processes. Running a single purge job will place all of the free blocks on only one freelist, and none of the other freelists will contain any free blocks from the purge.
The freelist parameter should be set to the high-water mark of updates to a table. For example, if the customer table has up to 20 end users performing insert operations at any time, the customer table should have freelists=20.
The freelist groups parameter should be set the number of Real Application Clusters instances (Oracle Parallel Server in Oracle8i) that access the table.

sb92075 wrote:
goni ,
Please let go of 20th century & join the rest or the world in the 21st century.
Information presented is obsoleted & can be ignored when using ASSM & ASSM is default with V10 & V11I said the same over here for the exactly same thread, not sure what the heck OP is upto?
Oracle Table Storage Parameters - a nice reading
regards
Aman....

Two Warehouse can Assigned to one Storage Loc

Dear All,
Is it possible having :
"Two Warehouse can Assigned to one Storage Loc ?????"
If yes how it can be achieved.
Regards,
Rocky
Edited by: Csaba Szommer on Sep 8, 2011 7:46 AM

Hi
Yes...we can do in enterprise structure assignment.>le....
Plant sloc warehouse...
Kuber

EREC: "Assign Values to Interface Parameters" query

Hi All,
I am currently on ehp4, sp4. I had a requirement to change the format of the form to display the posting. Hence i took the help of the node: technical settings>User Interfaces>Administrator and Recruiter>General Settings>Assign Values to Interface Parameters. Here i user the parameter: FORM_PUBL_INT_DOVR and parameter value as the new Z form created. The new form was visible in the publication area of the job posting.
But when i try to view the form by searching the job posting (as a candidate), it is still displayed in the old format. i.e when i try to view the posting using the posting search functionality.
Can anybody please tell me what is the configuration left from my side
Note: Majority of my application is a BSP application
Regards,
Kishore

Dear Kishore,
Please do the entry in the table V77RCF_PRM_PL for custom entries. Also check the table T77RCF_UI_PARAM whether correct form is used or not ??
Best Regards,
Deepak.

Maintained the storage location in MRPview2

Hi,
Though I have maintained storage location in MRP view2, while reversing the document from m.type 103 to 105 system is asking storage location in GR, then entered the storage location in GR, even though system is not allowing to post the GR because system is giving error message saying that inbound delivery storage location can not be changed to here.
We don not want to maintain the storage location in PO and Inbound delivery
We are creating inbound delivery in VL31N against the PO, after that posting the GR with m.type 103 once that is complete then will reverse the document from m.type 103 to 105 while reversing the document we are facing the above said problems.
Appreciate for your effective action.

Hi,
You have two queries:
1.You entered your required storage location in material master ,MRP2 screen to have Default storage location for external procurement, so that when you enter plant while creating the PO, this SL will be written automatically.This storage location nothing to with GR, during GR you need to enter your storage location.
2.While reversing the document you are facing the problems.
The movement types 103 is used for Goods receipt for purchase order into GR blocked stock & 105 is used for Release from GR blocked stock for purchase order.
But as you are reversing the document use 104 movement type instead of 105.
Regards,
Biju K

(PCTFREE, PCTUSED) and Storage parameters

HI,
I am confused about (PCTFREE, PCTUSED) and Storage parameters(initial, next, pctincrease etc.)
As far as i have read PCTFREE and PCTUSED are used to control free and used space in a datablock and also these parameters related to Manual segment space management in Locally managed tablespace(i.e we need to manually set and tune these parameters). Whether these parameter are used in Dictionary managed tablespace or not?
Also, Storage parameters(intital, next, PCTUSED etc) are used in Dictionary managed tablespace. But in locally managed tablespaces how they are set as i have read we need not set these in locally managed tablespaces.
So, can you explain me about differences of these parameters with regard to Locally and Dictionary managed tablespaces in Oracle 9i and 10g platform on RHEL.

Hi,
Locally Managed Tablespace :-
A tablespace that can manage extent allocation by itself is called locally managed tablespace.
Using the bitmap in each datafile to keep track of the freed or used status of blocks in that datafile.
Each bit in the bitmap corresponds to a block or a group of blocks.
When an extent is allocated or freed for reuse, Oracle changes the bitmap values to show the new status of the blocks.
These changes do not generate rollback information because they do not update tables in the data dictionary.
Now remember, storage parameters
NEXT,
PCTINCREASE,
MINEXTENTS,
MAXEXTENTS, and
DEFAULT STORAGE are not valid for extents that are managed locally
Extents allocated in LMT :-
LMT have extent sizes either UNIFORM or variable extent sizes
For UNIFORM extents you can specify an extent size. The default size is 1MB.
and for AUTOALLOCATE extents you can specify the size of the initial extent and Oracle determines the optimal size of the additional extents, with a minimum extent size of 64KB
Example :-
Extent of uniform size
CREATE TABLESPACE test
DATAFILE 'tet.dbf'
EXTENT MANAGEMENT LOCAL
UNIFORM SIZE 256K;
Specifying Segment Space Management in Locally Managed Tablespaces
When you create a locally managed tablespace using the CREATE TABLESPACE statement, the SEGMENT SPACE MANAGEMENT clause allows you to specify how free and used space within a segment is to be managed.
MANUAL (MSSM) :- refers to oracle use free lists for managing free space within segments
because of the need to specify and tune the PCTUSED, FREELISTS, and FREELISTS GROUPS storage parameters for schema objects created in the tablespace
AUTO :-
Oracle use bitmaps to manage the free space within segments- automatic segment-space management
(ASSM)
Example :-
CREATE TABLESPACE lmtbsb DATAFILE '/u02/oracle/data/lmtbsb01.dbf' SIZE 50M
EXTENT MANAGEMENT LOCAL - LMT
SEGMENT SPACE MANAGEMENT AUTO; - ASSM
- DMT :-
Example :-
CREATE TABLESPACE tbsb
DATAFILE '/u02/oracle/data/tbsa01.dbf' SIZE 50M
EXTENT MANAGEMENT DICTIONARY -- specified how to manag the extent in DB
DEFAULT STORAGE (
INITIAL 50K
NEXT 50K
MINEXTENTS 2
MAXEXTENTS 50
PCTINCREASE 0); -- you have specified how extents in memory should increase
In the above example you have created dmt and specified the storage parameter for Extents, that is
how they much allocated as data get inserted in to the segments(tables) .
refer : http://www.mpi-inf.mpg.de/departments/d5/teaching/ss05/is05/oracle/server.920/a96521/tspaces.htm#636
- Pavan Kumar N
Oracle 9i/10g - OCP
http://oracleinternals.blogspot.com/

Create table with storage parameters in a locally managed tablespace

Hi,
Can we create object with storage parameters in a locally managed tablespace.
CREATE TABLE my_hash_table_6 (
name VARCHAR2(30),
value VARCHAR2(4000) )
STORAGE (
INITIAL 1M
NEXT 512K
PCTINCREASE 0
MINEXTENTS 2
MAXEXTENTS UNLIMITED )
users default tablespace is locallly managed.
Then this table's extent management will be managed as per the tablespace or as the storage parameters which
were specified at the time of table creation.

Why don't you try it yourself ?
TEST@db102 > select * from dba_tablespaces
2 where TABLESPACE_NAME='USERS';
TABLESPACE_NAME                BLOCK_SIZE INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS
MAX_EXTENTS PCT_INCREASE MIN_EXTLEN STATUS    CONTENTS LOGGING   FOR EXTENT_MAN
ALLOCATIO PLU SEGMEN DEF_TAB_ RETENTION   BIG
USERS                                8192          65536                       1
2147483645                   65536 ONLINE    PERMANENT LOGGING   NO LOCAL
SYSTEM    NO AUTO   DISABLED NOT APPLY   NO
TEST@db102 > CREATE TABLE my_hash_table_6 (
2 name VARCHAR2(30),
3 value VARCHAR2(4000) )
4 STORAGE (
5 INITIAL 1M
6 NEXT 512K
7 PCTINCREASE 0
8 MINEXTENTS 2
9* MAXEXTENTS UNLIMITED )
TEST@db102 > /
Table created.
TEST@db102 > select * from user_segments
2 where segment_name='MY_HASH_TABLE_6';
SEGMENT_NAME
PARTITION_NAME                 SEGMENT_TYPE       TABLESPACE_NAME
     BYTES     BLOCKS    EXTENTS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS
MAX_EXTENTS PCT_INCREASE FREELISTS FREELIST_GROUPS BUFFER_
MY_HASH_TABLE_6
                               TABLE              USERS
   2097152        256          2        1572864                       1
2147483645                                         DEFAULT
TEST@db102 >

Regarding Table Maintainance

Helo All. I have a query regarding table maintainance.
I have created a transaction for a table, and allowed only SHOW and VIEWNAME in default values.
Still it is allowing to update the table.
Can you tell me why?
Thanks in advance !!!

Your transaction is just calling SM30, even though you specify these defaults all of functionality of SM30 is available.
To limit access to the table to display only you would need to either apply the authorisation concept (set an authorisation group in the table maintenance settings and restrict user access) or write a simple list report that displays the table contents and link that to a transaction.
Regards,
Nick

I need help regarding measurement of "time domain parameters of Heart rate variability" using labview.

I need help regarding measurement of "time domain parameters of Heart rate variability" using labview.
I am using Labview 8 ... I need to develop a software to accquire the ECG data (simulated enironment ) and compute the time domain parameters of Heart rate variability like "SDNN, SDANN...etc". Can some 1 plllzzzz help me out.Plzz help me if u can.Thanx in advance.

Hi Andy,
Thanx for responding. The input is from a text file. SDNN, SDANN,etc are the timedomain parameters of heart rate variability.
SDNN: the standard deviation of the NN or RR interval i.e. the square root of variance.
SDANN:the standard deviation of the averageNN interval calculated over short periods, usually 5 min,which is an estimate of the changes in heart rate due tocycles longer than 5 min
SDNN index, the meanof the 5-min standard deviation of the NN intervalcalculated over 24 h,
RMSSD: the square root ofthe mean squared differences of successive NN intervals
NN50: the number of interval differences of successiveNN intervals greater than 50 ms, and
pNN50 the proportionderived by dividing NN50 by the total numberof NN intervals.
The problem is dat I am a fresher to the world of Labview. I have jus recently started working on it. Can u please suggest me some some idea as soon as possible.
As i said I have the ECG data in the form of text files..I need to create sort of GUI to calculate the time domain parmeters....I need help urgently. Plzzz help me if u can. If u have and .vi example to calculate the RR interval plzz send it to me ASAP.
Thanku

IMP - EXP and storage parameters

Hi All,
I am planning to import few tables from one database to another database using our good old import-export (even when I am on 10g).
Tables which I am importing do not exist in the target database. So, when I create them from the export dump, I think they will be created "with the same storage parameters (i.e. initial extent, next etc etc) as the source database". If I want import tables to take up the storage parameters of the target database/tablespace instead of the source, what is the way ??
Thanks in advance

Sabdar is right. Pre-defining the objects using the desired storage clause is the best way to do this.
If using locally managed tablespaces in the target database the tablespace parameters will override the next extent and pct_increase information on import but the initial extent setting will influence how many extents are allocated.
I suggest in either case: dictionary or locally managed target tablespaces that the export be made using compress=n. This will give you the best control over how much space the objects take on import.
HTH -- Mark D Powell --

Specifying storage parameters for indexes

Hi
Could be I'm blind or something, but....
When I create an index in SQL Dev: How do I specify storage parameters (e.g. tablespace) for that index?
:-)Roald

In the truth a visual way does not exist to make this.
Just with the command line, in the SQL Worksheet, as example below.
create index your_index on your_table (
index_column ASC
) tablespace your_tablespace
Bigger details on the parameters of storage can be gotten in link:
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_5010.htm#i2062403

Storage type to be assigned to particular storage location

Hi,
As per clients new business requirement, 2 storage locations of a plant are assigned to same warehouse.
But as the storage types comes under warehouse they come under both the storage locations. Is there any configuration to assign specific storage types to a particular storage location.
I tried in SPRO under interfaces>IM>Storage location control but it does not allow.
Please advice.
Regards,
Pratap

Hi,
I feel the solution given by E060123 in his first reply should work well.
Did you first define the storage location refernce and then in the same config node under "Control of Assignment "Plant / Stor.Loc. - Whse Number" assigned the sloc reference to the respective storage location
And then assigned the reference to the search table as mentioned previously.

Regarding assignment of physical path to logical file name

Hi All,
We have created one logical file name and assigned physical path to it in FILE tcode.
IN PATH table also these details got updated with correct logical file name & physical path.
But in my program when i have used FILE_GET_NAME F.M to retrieve physical path from logical file.
Here this F.M is not returning anything.
What is the issue over here.
We are working in ECC 6.0
Can anybody resolve this issue!
Thanks,
Deep.

do one thing i give my report so according to do this
*& Report ZMIO_MANU_VENDOR_EXTR
report zmio_manu_vendor_extr.
DATA BASE TABLES
tables: lfa1 ,eina, lfm1 .
STRUCTURES
*---structure for the vendor details.
data: begin of ws_lfa1 ,
lifnr type lfa1-lifnr,
name1 type lfa1-name1,
end of ws_lfa1 .
*---structure for the pur org details.
data: begin of ws_lfm1 ,
lifnr type lfm1-lifnr,
kalsk type lfm1-kalsk,
minbw type lfm1-minbw,
end of ws_lfm1 .
*---structure for the pur inf rec.
data: begin of ws_eina,
lifnr type eina-lifnr,
relif type eina-relif,
end of ws_eina .
*--structure for the output file
data: begin of ws_final,
lifnr(10) type c,
name1(35) type c,
kalsk(1) type c,
minbw(13) type c,
eoln(1) type c,
end of ws_final .
INTERNAL TABLES
*---internal table for vendor details
data:i_lfa1 like ws_lfa1 occurs 0.
*---internal table for pur org details
data:i_lfm1 like ws_lfm1 occurs 0.
*---internal table for pur inf details
data:i_eina like ws_eina occurs 0.
*---internal table for final file output
data:i_final like ws_final occurs 0.
*DATA : P_FLAG(1) TYPE C.
CONSTANTS
*-- Default file name
constants: c_filename_default(40) type c
value 'VOLSAP/MAXVRLIB/manu_retail_vendor',
c_kalsk(2) type c value '05'.
SELECTION SCREEN
selection-screen begin of block b1 with frame.
selection-screen: begin of block b2 with frame title text-001 .
select-options:s$lifnr for lfa1-lifnr .
parameters:p$relif as checkbox.
selection-screen end of block b2.
selection-screen: begin of block b3 with frame title text-002 .
parameters: p$file(128) obligatory default c_filename_default.
selection-screen end of block b3.
selection-screen end of block b1 .
START OF SELECTION
start-of-selection.
if not s$lifnr is initial.
perform get_vendor_data .
endif.
perform build_file .
perform display_file .
END OF SELECTION
end-of-selection .
*& Form GET_VENDOR_DATA
form get_vendor_data .
select lifnr
name1
from lfa1
into table i_lfa1
where lifnr in s$lifnr .
if not i_lfa1[] is initial.
sort i_lfa1 by lifnr .
select lifnr
kalsk
minbw
from lfm1
into table i_lfm1
for all entries in i_lfa1
where lifnr = i_lfa1-lifnr .
select lifnr
relif
from eina
into table i_eina
for all entries in i_lfa1
where lifnr = i_lfa1-lifnr
and relif = 'X'.
endif.
endform. " GET_VENDOR_DATA
*& Form BUILD_FILE
form build_file .
loop at i_lfa1 into ws_lfa1 .
ws_final-lifnr = ws_lfa1-lifnr .
ws_final-name1 = ws_lfa1-name1 .
read table i_lfm1 into ws_lfm1 with key lifnr = ws_lfa1-lifnr .
if ws_lfm1-kalsk = c_kalsk .
ws_final-kalsk = 'X'.
endif.
ws_final-minbw = ws_lfm1-minbw .
ws_final-eoln = 'X'.
if p$relif = 'X'.
CLEAR P_FLAG.
LOOP AT I_EINA INTO WS_EINA
WHERE LIFNR = WS_LFA1-LIFNR
AND RELIF = 'X'.
P_FLAG = 'X'.
EXIT.
ENDLOOP.
IF P_FLAG = 'X'.
APPEND WS_FINAL TO I_FINAL .
CLEAR WS_FINAL.
ENDIF
read table i_eina into ws_eina with key lifnr = ws_lfa1-lifnr
relif = 'X'.
if sy-subrc = 0.
append ws_final to i_final .
clear ws_final.
endif.
else.
append ws_final to i_final .
clear ws_final.
endif.
endloop .
endform. " BUILD_FILE
*& Form DISPLAY_FILE
form display_file .
data: l_lines type i.
describe table i_final lines l_lines.
if l_lines > 0.
perform open_file using p$file.
loop at i_final into ws_final.
transfer ws_final to p$file.
endloop.
close dataset p$file.
else.
write: / 'no data found'.
endif.
endform. " DISPLAY_FILE
*& Form open_file
Open an output file, customizing default name to include
vendor number and job completion timestamp.
form open_file using file_nm.
data: l_vendor like eina-lifnr,
l_timestamp(12) type c.
Get correct path/filename for the system we're running on
call function 'FILE_GET_NAME'
exporting
logical_filename = 'ZVOL'
parameter_1 = file_nm
importing
file_name = file_nm.
Open file for output
open dataset file_nm for output in text mode encoding default.
if sy-subrc ne 0.
message e368(00) with 'Error opening output file:' file_nm.
endif.
endform. "open_file
All definitions needed for the platform-independent assignment of file names are maintained client-independently with transaction FILE. Logical file names (but not logical file paths) can also be defined specifically for the current client with transaction SF01. Transaction SF07 generates a list of current definitions.
Edited by: krupa jani on Aug 20, 2008 6:55 AM

Regarding assigning Maintain DB-Storage Parameters

Similar Messages

Maybe you are looking for