What E-Biz modules are present

when I down load all the 52 files/parts of 46GB from the below ORACLE LINK
http://edelivery.oracle.com/EPD/Download/get_form?egroup_aru_number=9984557...
sorry to ask this question ...but I did not understand from the
Oracle web site whether Oracle provides the complete E-Biz Suite of module like
1)Oracle Financials (AP,GL,AR,PO etc)
2)Oracle HR
3)Oracle Iprocrument
4)Oracle Supply Chain
After downloading and installing all the above modules(on Enterprise Linux provide by Oracle) will i be able to use this completely ....like many oracle s/w(oracle database) without any trial period ???
or ...will i have to insert the configuration data in the application as well(oracle provided vision database ) ?
Please let me know what else is required ?
Many Thanks in Advance.
rgds
s

After downloading and installing all the above modules(on Enterprise Linux provide by Oracle) will i
be able to use this completely ....like many oracle s/w(oracle database) without any trial period ???Yes.
or ...will i have to insert the configuration data in the application as well(oracle provided vision database ) ?Vision demo database comes with seeded data.
Please let me know what else is required ?You need to create the stage area, and start the installation.
Good Luck :)

Similar Messages

Hello! I need Apple (!!!) headphones for Ipod Shuffle 3! (only apple earphones with remote and mic!!!) Tell me, what distinguishes the model are presented in black and white boxes? They may differ in features? Can one model is more modern than the other?

Hello!
I need Apple (!!!) headphones for Ipod Shuffle 3! (only apple earphones with remote and mic!!!)
Tell me, what distinguishes the model are presented in black and white boxes? They may differ in features? Can one model is more modern than the other?
Thanks in advance!

Hi Fencer1986,
I apologize, I'm a bit unclear on your request. If you have questions about headphone compatibility for your iPod shuffle 3rd Gen, you may find the following article helpful:
iPod shuffle (3rd generation): About headphone compatibility
http://support.apple.com/kb/ht3472
Regards,
- Brenden

What kind of uncertainties are presented in catalogs of modules NI9201,9211,9203,9265 and DAQ9172

I have to calculate the total uncertainty for a compressor test-rig, so i am measuring static pressures, total temperatures, mass flow. I am using the following modules for each of the variables mentioned:
Pressure: NI 9203 (transducers) and Ni 9265 (pressure reducer)
Temperature: Ni 9211
Mass flow: NI 9203
So I have to incorporate in the total uncertainty the acquisition system uncertainty.
In the catalogs for each of the modules i found the following values
Ni 9203: Gain error +/-0.04% offset error +/-0.02
Ni 9265:Gain error +/-0.05% offset error +/-0.02
Ni9211: Gain error +/-0.05% offset error +/-15 uV
My question is about how to incorporate all this errors in the proagation of uncertainty calculation:
U(95)=((b1*theta1)^2+(b2*theta2)^2+....)^(1/2)
b1 are the errors due to each of the variables
theta is the derivative of the function for each one of the variables
According to this paper from asme http://www.barringer1.com/drbob-bio_files/ASME83.pdf which is based on th ASME PTC 19.1, which I haven't been able to get it.
The uncertainty is divided in two components bias and random errors, then each one has to be computed and in the end add all this together.
U(95)=(B^2+P^2)^(1/2)
So what i am doing is to get all the bias components from the sensors and also from the module of each sensor and adding them
Btotal=(B1^2+B2^2+....)^(1/2)
Where B1 and B2 are the bias components of the error in sensor , module and so on.
Ptotal=(P1^2+P2^2+....)^(1/2)
Where P1 and P2 are the random components of the error in sensor , module and so on.
then I am applying the propagation equation taking into account each component
Ubias(95)=((b1*theta1)^2+(b2*theta2)^2+....)^(1/2)
where b1... are just bia component and in I do the same in the other case with the random component
and in the end I sum this quantities
U(95)=(Ubiastotal^2+Pbiastotal^2)^(1/2)
So my question is if the values that i took from the catalogs of each module correspond to the bias component of the error or is a combination of random and bias component?
The other question is related with NI911 this is used for the thermocouples and i was reading in one of the forums that for this module i take the bias error or systematic directly from the figures in the catalogs so for instance if i read 1,8 C for autozero off room temperature, that value corresponds to +/-1,8.
And the last question is if you can help me with a reference book about the equations required to transform from volts to calculate the gain and offset error that you have in the catalogs.
Sorry for the long explanation but i didn't know how to pose the questions in an easier way
Thanks for the help\
Esteban

Just installed CC on my PC, Windows 7, 64 bit system. Not seeing any applications on the desktop or installation folder. However, all the resource files are present in the installation folder. What am I doing wrong?

Just installed CC on my PC, Windows 7, 64 bit system. Not seeing any applications on the desktop or installation folder. However, all the resource files are present in the installation folder. What am I doing wrong?
I've installed three times with no luck. I downloaded the Creative Cloud Packager off the licensing site: https://licensing.adobe.com. I unpacked and choose my applications. The install seemed to be successful, but I don't so any of the applications anywhere.

Hi,
Creating package doesn't mean it will install the product,
You will need to install the package now. Please follow the instructions mentioned in the below articles
Creative Cloud Help | Creating or editing packages
Creative Cloud Help | Deploying packages
Please let me know if it doesn't help.
Regards,
Devendra

How to find out what modules are used

In /etc/rc.conf there are a lot of modules that are loaded that don't need to be, like modules related to OSS. Is there some command that'll show me what modules are being used at the moment and/or what they do?

Yes Thinkpad FTW! Back on topic; so there are three columns: Module, Size and Used By. In the used by column what do the different numbers mean?
I ran "lsmod | less" to be able to view each individual one. (That "| less" part is really useful)
Last edited by jordanwb (2008-08-07 01:59:15)

Hi guru's what are the function modules are used in ALV

hi guru's what are the function modules are used in ALV

Hi vasu,
There are some function modules which will enable to produce the reports without much effort.
All the definitions of internal tables, structures and constants are declared in a type-pool called SLIS.
1. SIMPLE REPORT.
The important function modules are
a. Reuse_alv_list_display
b. Reuse_alv_fieldcatalog_merge
c. Reuse_alv_events_get
d. Reuse_alv_commentary_write
e. Reuse_alv_grid_display
A. REUSE_ALV_LIST_DISPLAY : This is the function module which prints the data.
The important parameters are :
I. Export :
i. I_callback_program : report id
ii. I_callback_pf_status_set : routine where a user can set his own pf status or change the functionality of the existing pf status
iii. I_callback_user_command : routine where the function codes are handled
iv. I_structure name : name of the dictionary table
v. Is_layout : structure to set the layout of the report
vi. It_fieldcat : internal table with the list of all fields and their attributes which are to be printed (this table can be populated automatically by the function module REUSE_ALV_FIELDCATALOG_MERGE
vii. It_events : internal table with a list of all possible events of ALV and their corresponding form names.
II. Tables :
i. t_outtab : internal table with the data to be output
B. REUSE_ALV_FIELDCATALOG_MERGE : This function module is used to populate a fieldcatalog which is essential to display the data in ALV. If the output data is from a single dictionary table and all the columns are selected, then we need not exclusively create the field catalog. Its enough to mention the table name as a parameter(I_structure name) in the REUSE_ALV_LIST_DISPLAY. But in other cases we need to create it.
The Important Parameters are :
I. Export :
i. I_program_name : report id
ii. I_internal_tabname : the internal output table
iii. I_inclname : include or the report name where all the dynamic forms are handled.
II Changing
ct_fieldcat : an internal table with the type SLIS_T_FIELDCAT_ALV which is
declared in the type pool SLIS.
C. REUSE_ALV_EVENTS_GET : Returns table of possible events for a list type
Parameters :
I. Import :
Et_Events : The event table is returned with all possible CALLBACK events
for the specified list type (column 'NAME'). For events to be processed by Callback, their 'FORM' field must be filled. If the field is initialized, the event is ignored. The entry can be read from the event table, the field 'FORM' filled and the entry modified using constants from the type pool SALV.
II. Export :
I_List_type :
0 = simple list REUSE_ALV_LIST_DISPLAY
1 = hierarchcal-sequential list REUSE_ALV_HIERSEQ_LIST_DISPLAY
2 = simple block list REUSE_ALV_BLOCK_LIST_APPEND
3 = hierarchical-sequential block list
REUSE_ALV_BLOCK_LIST_HS_APPEND
D. REUSE_ALV_COMMENTARY_WRITE : This is used in the Top-of-page event to print the headings and other comments for the list.
Parameters :
I. it_list_commentary : internal table with the headings of the type slis_t_listheader.
This internal table has three fields :
Typ : H header, S selection , A - action
Key : only when typ is S.
Info : the text to be printed
E. REUSE_ALV_GRID_DISPLAY : A new function in 4.6 version, to display the results in grid rather than as a preview.
Parameters : same as reuse_alv_list_display
This is an example for simple list.
2. BLOCK REPORT
This is used to have multiple lists continuously.
The important functions used in this report are:
A. REUSE_ALV_BLOCK_LIST_INIT
B. REUSE_ALV_BLOCK_LIST_APPEND
C. REUSE_ALV_BLOCK_LIST_HS_APPEND
D. REUSE_ALV_BLOCK_LIST_DISPLAY
A. REUSE_ALV_BLOCK_LIST_INIT
Parameters:
I. I_CALLBACK_PROGRAM
II. I_CALLBACK_PF_STATUS_SET
III. I_CALLBACK_USER_COMMAND
This function module is used to set the default gui status etc.
B. REUSE_ALV_BLOCK_LIST_APPEND
Parameters :
Export :
I. is_layout : layout settings for block
II. it_fieldcat : field catalog
III. i_tabname : internal table name with output data
IV. it_events : internal table with all possible events
Tables :
i. t_outtab : internal table with output data.
This function module adds the data to the block.
Repeat this function for all the different blocks to be displayed one after the other.
C. REUSE_ALV_BLOCK_LIST_HS_APPEND
This function module is used for hierarchical sequential blocks.
D. REUSE_ALV_BLOCK_LIST_DISPLAY
Parameters : All the parameters are optional.
This function module display the list with data appended by the above function.
Here the functions REUSE_ALV_FIELDCATALOG_MERGE, REUSE_ALV_EVENTS_GET, REUSE_ALV_COMMENTARY_WRITE can be used.
3. Hierarchical reports :
Hierarchical sequential list output.
The function module is
A. REUSE_ALV_HIERSEQ_LIST_DISPLAY
Parameters:
I. Export:
i. I_CALLBACK_PROGRAM
ii. I_CALLBACK_PF_STATUS_SET
iii. I_CALLBACK_USER_COMMAND
iv. IS_LAYOUT
v. IT_FIELDCAT
vi. IT_EVENTS
vii. i_tabname_header : Name of the internal table in the program containing the
output data of the highest hierarchy level.
viii. i_tabname_item : Name of the internal table in the program containing the
output data of the lowest hierarchy level.
ix. is_keyinfo : This structure contains the header and item table field
names which link the two tables (shared key).
II. Tables
i. t_outtab_header : Header table with data to be output
ii. t_outtab_item : Name of the internal table in the program containing the
output data of the lowest hierarchy level.
slis_t_fieldcat_alv : This internal table contains the field attributes. This internal table can be populated automatically by using REUSE_ALV_FIELDCATALOG_MERGE.
Important Attributes :
A. col_pos : position of the column
B. fieldname : internal fieldname
C. tabname : internal table name
D. ref_fieldname : fieldname (dictionary)
E. ref_tabname : table (dictionary)
F. key(1) : column with key-color
G. icon(1) : icon
H. symbol(1) : symbol
I. checkbox(1) : checkbox
J. just(1) : (R)ight (L)eft (C)ent.
K. do_sum(1) : sum up
L. no_out(1) : (O)blig.(X)no out
M. outputlen : output length
N. seltext_l : long key word
O. seltext_m : middle key word
P. seltext_s : short key word
Q. reptext_ddic : heading (ddic)
R. ddictxt(1) : (S)hort (M)iddle (L)ong
S. datatype : datatype
T. hotspot(1) : hotspot
some theory regarding alv:
This table tells ALV which events are processed by the caller by CALLBACK.
The table of possible events per list type can be initialized using the module REUSE_ALV_EVENTS_GET.
You can display the names of the constants in the type pools SLIS which represent the individual events using the individual test function in the function module
REUSE_ALV_EVENT_NAMES_GET. Only events with a form routine name are processed.
The table structure contains the fields:
IT_EVENTS-NAME
Name of the Callback event.
Possible Callback events:
Action
USER_COMMAND USING R_UCOMM LIKE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD
Process actions on the list
As this is a frequently-used Callback event, the form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_USER_COMMAND.
PF_STATUS_SET USING RT_EXTAB TYPE SLIS_T_EXTAB
If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
The STANDARD status of the function group SALV should be used as a template for a user-specific status.
As this is a frequently-used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
ITEM_DATA_EXPAND USING RS_SELFIELD TYPE SLIS_SELFIELD RFLG_ALL TYPE C
Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT.
Exit for passing item entries (ITEM table) for a header record which was expanded interactively by the user.
RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header which is to be expanded.
RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table. RS_SELFIELD is initial in this case.
CALLER_EXIT USING RS_DATA Is called at the beginning of the function module to make special settings. It is not usually used.
List processing events
IMPORTANT: The application Callback routine must not manipulate the internal output table and/or its header record. This restriction applies to all Callbacks which are called in the list output and run under the 'List processing events'.
TOP_OF_LIST no USING parameter. Information output at the start of the list
END_OF_LIST no USING parameter. Information output at the end of the list
TOP_OF_PAGE no USING parameter
Equivalent to the list processing TOP-OF-PAGE event
END_OF_PAGE no USING parameter. Not available for hierarchical-sequential lists.
Information output at the end of a page. This is only called for printing.
TOP_OF_COVERPAGE no USING parameter
The selection information and list status are output together (if they exist) on a separate page by default. See also the documentation of the parameters:
IS_PRINT-NO_COVERPAGE
IS_PRINT-NO_PRINT_SELINFOS
IS_PRINT-NO_PRINT_LISTINFOS
IS_LAYOUT-GET_SELINFOS
The user can format the header area of the 'cover page' himself or herself by specifying a Callback routine for this event.
END_OF_COVERPAGE no USING parameter
Analogously to TOP_OF_COVERPAGE the user can add other information to the information output by ALV (selection information, list status) at this event.
FOREIGN_TOP_OF_PAGE no USING parameter
The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
FOREIGN_END_OF_PAGE no USING parameter
The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.
BEFORE_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
Output information before each output line. Should only be used in justified cases because it costs a lot of performance.
AFTER_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
Internal use only
LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
R_INDEX LIKE SY-TABIX
R_INDEX_ITEM LIKE SY-TABIX
R_INDEX_SUM LIKE SY-TABIX
IT_EVENTS-FORM
Name of the form routine which should be called in the calling program at the event.
Field_catalog:
Field catalog with field descriptions
2.7.1. Description
Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields). A field catalog is required for every ALV list output.
The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module
See also the documentation of the function module REUSE_ALV_FIELDCATALOG_MERGE.
The minimal field catalog is documented under 'default'. The caller can use the other optional parameters to assign output attributes to a field which differ from the default.
A field catalog need not be built-up and passed explicitly only under the following conditions:
The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE.
all fields in this structure are to be output
the structure name is passed to ALV in the parameter I_STRUCTURE_NAME.
See also the documentation of the IMPORTING paramter I_STRUCTURE_NAME.
Positioning
row_pos (row position)
value set: 0, 1 - 3
Only relevant if the list output is to be multi-line (two or three lines) by default.
A multi-line list can also be defined by the user interactively if the default list is one-line.
The parameter specifies the relative output line of the column in a multi-line list.
col_pos (column position)
value set: 0, 1 - 60
only relevant when the default relative column positions differ from the field catalog field sequence. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the field catalog field sequence.
Identification
fieldname (field name)
value set: internal output table field name (required parameter)
Name of the internal output table field which is described by this field catalog entry
tabname (internal output table)
value set: SPACE, internal output table name
This parameter is used in 'manual' field catalog build-up only for hierarchical-sequential lists.
Name of the internal output table which contains the field FIELDCAT-FIELDNAME.
Data Dictionary reference
ref_fieldname (reference field name)
value set: SPACE, Data Dictionary field name
Name of the Data Dictionary field referred to.
This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
ref_tabname (reference table/structure field name)
value set: SPACE, name of a Data Dictionary structure or table
Structure or table name of the referred Data Dictionary field.
This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
Reference to fields with currency/measurement unit
Each internal output table sum or quantity field whose decimal places are to be formatted appropriately for the unit in the list must follow the convention:
the field is of data type QUAN or CURR (internal type P) (the field must really have this physical data type. Overwriting the physical data type with the parameter FIELDCAT-DATATYPE has no effect)
There is a field in the internal output table which contains the associated unit.
There is also an entry in the field catalog for the unit field.
(If the unit is not to appear as a column in the list, and cannot be interactively displayed as a column, e.g. because it is always unambiguous and is therefore explicitly output by the caller in the list header, the field catalog units field entry can take the parameter FIELDCAT-TECH = 'X'.
The association of a value field to a unit affects the output as follows:
appropriate decimal places display for the unit
an initialized field with a link to a non-initial unit is output as '0' for the unit (if FIELDCAT-NO_ZERO is initial). When this field is summed, this unit affects whether the units are homogeneous.
an initialized field with a link to an initial unit is output as SPACE. When this field is summed, the unit SPACE does not affect the homogeneity of the units.
When non-initial fields with an initial unit are summed, the unit SPACE is considered to be a unit.
Link to currency unit
cfieldname (currency unit field name)
value set: SPACE, output table field name
Only relevant for amount columns with associated unit.
Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
ctabname (internal currency unit field output table)
value set: SPACE, output table field name
only relevant for hierarchical-sequential lists
Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
Link to measurement unit
qfieldname (measurement unit field name)
value set: SPACE, output table field name
only relevant for quantity columns with unit link.
Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME.
The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
qtabname (internal measurement unit field output table)
value set: SPACE, output table field name
only relevant for hierarchical-sequential lists
Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
Column output options
outputlen (column width)
value set: 0 (initial), n
For fields with a Data Dictionary link this parameter can be left initial.
For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
initial = column width is the output length of the referred Data Dictionary field (domain).
n = column width is n characters
key (key column)
value set: SPACE, 'X' 'X' = kex field (key field output in color)
Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
For exceptions see the documentation of the FIELDCAT-KEY_SEL parameter.
key_sel (hideable key column)
value set: SPACE, 'X'
only relevant when FIELDCAT-KEY = 'X'
Key field which can be hidden interactively.
The key column sequence cannot be changed interactively by the user.
The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
no_out (field in field list)
value set: SPACE, 'X' 'X' = field is not displayed in the current list.
The user can interactively choose the field for output from the field list.
The user can display the contents of these fields at line level using the 'Detail' function.
See also the 'Detail screen' documentation of the parameter IS_LAYOUT.
tech (technical field)
value set: SPACE, 'X' 'X' = technical field
Field cannot be output in the list and cannot be displayed interactively.
Field can only be used in the field catalog (not in IT_SORT, ...).
emphasize (highlight columns in color)
value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)
'X' = column is colored with the default column highlight color.
'Cxyz' = column is colored with a coded color:
C: Color (coding must begin with C)
x: color number
y: bold
z: inverse
hotspot (column as hotspot)
value set: SPACE, 'X'
'X' = column cells are output as hotspots
fix_column (fix column)
value set: SPACE, 'X'
Not relevant for block lists (output of several lists consecutively)
'X' = column fixed (does not scroll horizontally)
All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively. See also the documentation of the Layout parameter
IS_LAYOUT-NO_KEYFIX of the IMPORTING paramter IS_LAYOUT.
do_sum (sum over column)
value set: SPACE, 'X' 'X' = a sum is to be calculated over this internal output table field.
This function can also be called by the user interactively.
no_sum (sums forbidden)
value set: SPACE, 'X' 'X' = no sum can be calculated over this field, although the data type of the field would allow summing.
input (column ready for input)
Function not available
Format column contents
icon
value set: SPACE, 'X' 'X' = column contents to be output as an icon.
The caller must consider the printability of icons.
symbol
value set: SPACE, 'X' 'X' = column contents are to be output as a symbol.
The internal output table column must be a valid symbol character.
The caller must consider the printability of symbols.
Symbols can usually be printed, but may not always be output correctly, depending on the printer configuration.
just (justification)
value set: SPACE, 'R', 'L', 'C'
Only relevant for fields of data type CHAR or NUMC
' ' = default justification for this data type
'R' = right-justified output
'L' = left-justified output
'C' = centered output
The justification of the column header always follows the justification of the columns. Independent justification of the column neader is not possible.
lzero (leading zeros)
value set: SPACE, 'X'
Only relevant for fields of data type NUMC
ALV outputs NUMC fields right-justified without leading zeros by default.
'X' = output with leading zeros
Note: If a NUMC field is output left-justified or centered by FIELDCAT-JUST, leading zeros are output. If the output of leading zeros is suppressed by a Data Dictionary reference ALPHA conversion exit, the output is always left-justified.
no_sign (no +/- sign) Only relevant for value fields
value set: SPACE, 'X' 'X' = value output without +/ sign
no_zero (suppress zeros) Only relevant for value fields
value set: SPACE, 'X' 'X' = suppress zeros
edit_mask (field formatting)
value set: SPACE, template
template = see documentation of WRITE formatting option USING EDIT MASK template
The output conversion conv can be made by template = '== conv'.
Texts
The following text parameters should be specified for program fields without a Data Dictionary reference. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored. If the user changes the column width interactively, the column header text with the appropriate length is always used. The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
The 'long field label' is also used in display variant definition, sort, etc. popups.
seltext_l (long field label)
seltext_m (medium field label)
seltext_s (short field label)
reptext_ddic (header)
analogous to the Data element maintenance 'Header'
The specified text is not necessarily output in the list, an optimum among all texts is sought.
ddictxt (specify text)
value set: SPACE, 'L', 'M', 'S'
You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
Parameters for program fields without Data Dictionary reference
see also 'Text' parameters
datatype (data type)
value set: SPACE, Data Dictionary data type (CHAR, NUMC,...)
Only relevant for fields without Data Dictionary reference
Program field data type
ddic_outputlen (external output length)
value set: 0 (initial), n
Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
Prerequisites:
FIELDCAT-EDIT_MASK = '==conv'
see also the documentation of the parameter FIELDCAT-EDIT_MASK
FIELDCAT-INTLEN = n
see also the documentation of the parameter FIELDCAT-INTLEN
n = external format field output length
The column width FIELDCAT-OUTPUTLEN need not be the same as the external format output length (FIELDCAT-DDIC_OUTPUTLEN).
intlen (internal output length)
value set: 0 (initial), n
Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
Prerequisites:
FIELDCAT-EDIT_MASK = '==conv'
see also the documentation of the parameter FIELDCAT-EDIT_MASK
FIELDCAT-DDIC_OUTPUTLEN = n
see also the documentation of the parameter FIELDCAT-DDIC_OUTPUTLEN
n = internal format field output length
rollname (data element)
value set: SPACE, Data Dictionary data element name
F1 help can be provided for a program field without a Data Dictionary reference, or F1 help which differs from the Data Dictionary help can be provided for a field with a Data Dictionary reference, using this parameter.
When F1 help is called for this field, the documentation of the specified data element is displayed.
If the FIELDCAT-ROLLNAME is initial for fields with a Data Dictionary reference, the documentation of the data element of the referred Data Dictionary field is output.
Others
sp_group (field group key)
value set: SPACE, CHAR(1)
Field group key.
Keys are assigned to group names in the IT_SPECIAL_GROUPS parameter (see also the documentation of the parameter IT_SPECIAL_GROUPS).
When such an assignment is made in the field catalog and in IT_SPECIAL_GROUPS, the fields are grouped correspondingly in the display variant popup.
reprep (Report/Report interface selection criterion)
value set: SPACE, 'X'
Prerequisites:
The system contains the Report/Report interface (function group RSTI, table TRSTI)
Parameter LAYOUT-REPREP = 'X'
(see also the documentation of the parameter LAYOUT-REPREP of the IMPORTING parameter IS_LAYOUT )
'X' = When the Report/Report interface is called, the value of this field is passed in the selected interface start record as a selection criterion.
2.7.2. Default
The following entries are usually sufficient for internal table fields with a reference to a field defined in the Data Dictionary :
fieldname
ref_tabname
Notes:
ALV gets the remaining information from the Data Dictionary.
If no relative column position (COL_POS) is specified, the fields are output in the list in the order in which they were added to the field catalog.
REF_FIELDNAME need only be specifid when the name of the internal table field differs from the name of the referred Data Dictionary field.
Information which is explicitly entered in the field catalog is not overwritten by information from the Data Dictionary.
Priority rule:
Entries in the field catalog have priority over differing entries in the Data Dictionary.
The following entries are usually sufficient for internal table fields without a reference to the Data Dictionary (program fields):
fieldname
outputlen
datatype
seltext_s
seltext_m
seltext_l
Notes:
F1 help can be provided for program fields by assigning a data element to the parameter ROLLNAME.
If the parameters SELTEXT_S, SELTEXT_M, SELTEXT_L, and REPTEXT_DDIC contain appropriate field labels, the program field column headers are also adjusted appropriately when the column width changes
sites :
http://www.sapdevelopment.co.uk/reporting/alv/alv_variousfcat.htm
<b>plese reward if useful </b>
Message was edited by:
sunil kairam

What SAP modules are required for insuance sector

what SAP modules are required for insuance sector

Hi,
Following authorizations are required to be able to use all the functions of Support Package Manager:
S_CTS_ADMI
S_TRANSPRT
Additional objects required and which can be used to restrict further the functionality are:
S_C_FUNCT
S_CTS_ADMI
S_DATASET
S_GUI
S_RFC
As available in the SAP help,standard SAP S_A.SYSTEM contains all necessary access for importing support packages.
Regards,
Nagendran

What modules are available in Ltd CRM, Ltd Logitic and Ltd Finance User.

Dear All,
         I just want to know what modules are available in Ltd. CRM, Ltd. Logsitic and Ltd. Finance User.
        If possible can anybody give me the link from where i can get information which template is accessble by which user.
Regards
Hitesh Parsawala

Hi Hitesh,
Complete details about new user types is available in the service
market place in the path mentioned below
https://service.sap.com/smb
> License Key Requests
> Additional Documentation
    > New Pricing and Licensing structure
Also, refer to SAP Note : 1223477
Regards,
Vijay kumar
SAP Business One Forums Team

What modules are included with my license

Hi,
I am using ECC 6.0. I would like to know what modules are included with my license. For eg. SD, MM, FICO and whether we also have CRM or EP with our package? How do we find that out? Please help.
Cheers

Call you SAP Account Manager

Can I detect if a module is present in CRIO FPGA?

I have a cRIO-9073 controller chassis with 8 NI 9237 modules. I plan to use FPGA reads - not the scan engine. Can I detect whether a module is present or not within my FPGA VI? If not, is there a way to do this within the RT Host VI? (This is my first cRIO project so I'm still a bit green). I can foresee my client needing to replace a module sometime in the future and still needing to operate the system with the remaining modules - so the system must be robust and adaptible to fault conditions.
- Thanks in advance
- Tore
Solved!
Go to Solution.

I switched to the Find Hardware VI and it doesn't error, but what I need is network devices. I have expansion chassis on the network that I need to confirm are connected. The Find Hardware VI only lists off local devices. I asked about the error over at this topic here:
https://forums.ni.com/t5/LabVIEW/LV-RT-System-Config-Find-Systems-vi-Error-quot-2147220620-quot/m-p/...
Thanks,
James
LabVIEW Professional 2014

Memory Slot Utility "memory modules are installed in the recommended slots"

I've got two Mac Pros that give me this message. Every time I boot them up the Memory Slot Utility gives me the message that my memory modules are installed in the recommended slots.
This started after I installed an additional 8GB of RAM, bringing them up to 16GB. 8x2GB sticks.
I checked the login items and it's not there, so what else could I be missing?

I have this problem too on a Mac Pro Quad Early 2009.
Has 2x4GB + 2x1GB Runs fine with 10GB, but everytime I log in the memory utility pops up as if I have a problem.
How do I stop it annoying me?

My iPod no longer appears as folder/file in Itunes when connected. Library, genius, playlists, etc. are present, but there is no longer cross reference with the iPod itself. Help!?

My iPod no longer appears as folder/file in Itunes when connected. Library, genius, playlists, etc. are present, but there is no longer cross reference with the iPod itself. Help!?

I just tried it again and this time a different message showed up "The iPod 'name' cannot be synced. The required folder cannot be found." I have no clue what folder it could be talking about.

What is best blue tooth presenter for macbook pro and air

What is best Blue Tooth presenter for MacBook Pro and Air?

You got lots of choices such as:
WD Studio
http://www.wdc.com/en/products/products.aspx?id=200
WD Studio 2
http://www.wdc.com/en/products/products.aspx?id=210
WD My Book
http://www.wdc.com/en/products/products.aspx?id=250
Lacie:
http://www.lacie.com/dk/products/range.htm?id=10007
http://www.lacie.com/dk/products/range.htm?id=10036
The are tons of external storage for mac out there but these are a few of them...
I personally like the WD Studio 2 and the LaCie 2big Network 2

2500 images flowed into iPhoto that aren't mine! What happened? Whose are they?! Do I have to go through

When I opened iPhoto about 2500 images imported that are not mine. What happened? Whose are they? How do I get rid of them?

We live in a rural area and have a small business. No one has access to my computer except me. My husband doesn't use it -- ever -- so no one else has connected a device unless some mysterious remote visitor obtained access. The pictures are labeled "Resources" and "theme-files". They are not of people but a lot of flat squares of color. They are dated from early 2000's (around 2003) until the present. When I opened iPhoto, the number of pictures I have went from over 7500 to over 10,000 lickety split. I clicked "stop import" but nothing doing -- it said I had to wait until the download was complete. So there they are -- lots and lots of squares of color and shape type imagery. Is there a way to find a "location" on the map of where they came from? Also, I quite recently did a cleaning with MacKeeper and it came up with nothing malicious there.

IPhoto 5 album names are present; photos are missing

One month ago I installed Mac OS X (10.5.4) on my iBook G4 to resolve issues with my browser and hotmail. Today after having loaded new photos into iPhotos within the last month, I entered iPhotos and found the last two years of photos missing. The album names are there but no photos appear to the right when I click on the album name for photos imported from March 2006 to present. In fact the right side picture viewing area is grayed out as are the photo manipulation icons on the bottom of the screen. I had no iPhotos problems since purchasing my iBook G4 in February 2005 until now shortly after the OS upgrade. Any suggestions?
I have viewed other similar posts but those circumstances are slightly different from mine.

Brian
The database becomes corrupted from two principle causes:
1. The app is interrupted in the act of writing to the database - by a crash or force quit for instance
2. User activity in the iPhoto Library Folder - moving or renaming things.
If iPhoto Library Manager is not fully rebuilding then it suggests that your main db is so corrupted that it's not writing out to the Albumdata.xml file correctly. The only solution to that is to restore from a back up or start over new.
What version of iPhoto are you using? This is the iPhoto 08 forum, the original poster is referring to v5 and the instructions for starting over are different.
Regards
TD

What E-Biz modules are present

Similar Messages

Maybe you are looking for