Why "OCIAQListen" function parameters are commented in ociap.h file

Why "OCIAQListen" function parameters are commented in ociap.h file
Oracle help document says that the OCIAQListen function takes the
following 7 parameters...
OCISvcCtx *svchp
OCIError *errhp
OCIAQAgent **agent_list
ub4 num_agents
sb4 wait
OCIAQAgent **agent
ub4 flags
But the params are commented in the header file.

Hi Isabelle:
Please refer to SAP Note 1388857 - Error: "Cannot open file <<path to pcache area and file name>>. Please check its path and permissions." - Data Services XI 3.2 (12.2)
Regards,
Francisco Milán.

Similar Messages

FCC Parameters are required in the Receiver File Adapter

Hi ,
   Sorry for posting this question again.. my Structure is
MT_CADVICE_STRING
.     . Batach -
1:Unbounded (Node)
.     .      .Header_String -
1:1
.     .      .Line_Item       -
1:Unbounded (Node)
.     .      .      .LineItem_String -
1:1
for this structure I'm geting data in the XML format.. .. my scenario is simple File to File scenario.. now i want to convert this XML to a normal Text file by using FCC in the Receiver file adapter..
and in the Receiver side   i want the file in the bellow format: (each field i want to get in the separate line but at presnt I'm getting the continution of all lines I'm not getting the data in a separate lines..)
Header_string
LineItem_String
LineItem_String
Header_String
LineItem_String
so, any abody can help on this...
And in the Receiver Communication channel i keep the FCC parameters like as bellow :
RecordsetStructure : Batch,LineItem
Batch.fieldSeparator: 'nl'
LineItem.fieldSeparator: 'nl'
Batch.endSeparator: 'nl'
LineItem.endSeparator: 'nl'
For more information.. My source file is like bellow
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:MT_CADVICE_STRING xmlns:nr1="urn:Test.com:SD:CAdvice">
- <Batch>
<Header_String>1 B 1110300014200804108218 36892.80 03 10.000 10.000 0.00 0.00 008000021720080410558000.00 91958.40 649958.40 0.00 649958.40 2678.40 1000003461100000346110000034611000003461123456 18 18 0.00 $</Header_String>
- <LineItem>
<LineItem_String>2 B 1110300014 1 000000000001234567000000000001 5.000 0.00 45000.00 10800.00.00 16.00 279000.00 0.00 rcl/ML0080200804100000000357 200804100.00 01 02 000000002.00 860.13321.00 $</LineItem_String>
</LineItem>
- <LineItem>
<LineItem_String>2 B 1110300014 2 000000000001234567000000000001 5.000 0.00 45000.00 10800.00.00 16.00 279000.00 0.00 rcl/ML0080200804100000000357 200804100.00 01 02 000000002.00 860.13321.00 $</LineItem_String>
</LineItem>
</Batch>
</nr1:MT_CADVICE_STRING >
Regards
Jain

Hi jain
Provide as below definitely it will work,
RecordSet Structure : batch,Line_Item,LineItem_String
batch.fieldSeparator        ---      'nl'
Line_Item.fieldSeparator -
     'nl'
LineItem_String.fieldSeparator ---   'nl'
All your fields will come in a separate line.
Regards,
Sasi
Edited by: sasitharan on Jul 28, 2008 11:36 AM

New in NW04s: FL069 TABLES parameters are obsolete (in function modules)

Can somebody explain what is the fundamental reason for this behaviour in NW04s?
In Netweaver 2004s system (like ERP2005 ) you get a warning message in SE37:
FL069 TABLES parameters are obsolete! when defining quite ordinary tables parameter using LIKE and reference to a structure in ddic.
I now speak normal function modules, not RFC enabled.
This example of tables parameter definition will cause the warning message:
return LIKE BAPIRET2
I of course looked the additional help provided by this message FL069. I understood it as following:
you should stop using TABLES parameter and more often use CHANGING parameter by referring a TABLE TYPE defined in dictionary.
if using CHANGING parameter and still want to pass the header line of your internal table you should use a separate parameter (EXPORT or CHANGING parameter)
Developers have too much used TABLES parameters for passing internal tables for reading (by value) rather than to be modified (by reference). As a consequence, fm could have change the header line without caller to know it.
in my opinion the message help is missleadingly telling that header line is no longer passed to function module if TABLES parameter is used. I made a small test program and fm (with TABLES paramerer), and everything worked as before.
The warning message can be ignored by pressing Enter a few times and your fm with TABLES parameter works as it had in older versions of Netweaver.
SAP is still using a lot of TABLES parameters in their own function modules. For example SD_SALES_HEADER_MAINTAIN.
So what is the point of this warning message while everything still works as it used to be and SAP uses this same "OBSOLETE" feature itself? Is there anything more fundamental behind this message? Like TABLES paremeters will no longer work in future versions of ABAP (or header line passing will be ignored in future versions) and therefore developers should switch to CHANGING/EXPORT parameters with TABLE TYPES as soon as possible??
Please understand that I don't need any assistance how to avoid this message, just interested to share your opinions what is the purpose of this warning message.
That is why I did not marked this thread as a question.
Br: Kimmo

Hello,
This is the view under Tables tab in my function builder:
I_T_SELECT     TYPE     SRSC_S_IF_SIMPLE-T_SELECT
I_T_FIELDS     TYPE     SRSC_S_IF_SIMPLE-T_FIELDS
E_T_DATA     LIKE     SFLIGHT (which I change to YBWxxxx)
The moment I change to YBWxxxxx it gives me that error '"TABLES parameters are obsolete! "'
and unfortunately hitting enter several times is not helping either
Thanks!

Why some Vi in LabVIEW Functions panel are not in PDA Functions panel?

why some Vi in LabVIEW Functions panel are not in PDA Functions panel?
such as "MT Generate System Parameters.vi".......can not run on the PDA window and say:"MT Generate System Parameters.vi":subVI is not executable.

mathan wrote:
WenBin wrote:
up
could you please explain in bit more detail
Looks like a lame attempt to "bump" the thread.
Adding a (nearly) empty message places the thread back on top of the list, in the false assumption that this would generate more replies.
Well, he's partially correct, because it added the last three posts (which of course have nothing to do with the problem at hand), but it did not increase the "real" answers.
Bumping a thread is disruptive and generally a bad idea, because it adds a lot of noise to the forum. Imagine everybody would do it! There would be so much elbowing for the top spot that all substance would be lost in the chatter.
In the NI forums, bumping a thread is very counterproductive, because blue contributions (from NI) will typically (and hopefully!) wait until the thread is idle for a while.
Overall, it is a bad idea!
LabVIEW Champion . Do more with less code and in less time .

Why simple functions are not included in iPhone?

My iPhone is a wonderful piece of equipment I can't leave home without (in addition of my Amex card :-)) But for the life of me, I can't understand why Apple could not include functions which are pretty much standard with all other inferior mobile phones. Simple functions such as bluetooth transfer between phone or just saving important sms from iPhone to computer. Nokia has a great Nokia PCSuite; Motorola has very useful MobileTools which allows full sync between mobile phone and computer. I got to ask the question ... WHY? WHY? WHY? Is there any apps developer out there that can develop an apps similar to Nokia PCSuite or MobileTools. I will be the first one to pay for it.

Abbafan1972 wrote:
1. A better camera. For the cost of the phone I would expect at least a 5mp one.
Read about the megapixel myth. More megapixels does not mean a better camera.
2. A camera flash.
Let Apple know - http://apple.com/feedback
3. The ability to use your own custom message tone.
I hope not but see answer to number 2. People's ringtones in public can be annoying enough without giving them more choices to be annoying.
4. The way text messages are organised are a bit ar$e about face, no folder for sent messages, they are just in a continuous thread.
It's called a conversation.
5. A quicker way of sending text messages to a group of people.
Pretty quick after you create the initial group but see my answer to number 2.

RFC Function Module - Message Reference parameters are not allowed with RFC

Hi,
Ive checked the Remote-Enabled Module radio button, declared Import and Export parameters using Type typing and checked the Pass Value in export and import parameters but I still receive message Reference parameters are not allowed with RFC and not able to activate the function module.
Am I missing something?
Regards,
...Naddy

Hi all,
I faced the same problem and solved it ,
You have defined a reference parameter for a remotely called
function module. However, only value parameters are allowed
for this type of module.
Procedure
Change the reference parameter to a value parameter.
Guys pls .don't leave the thread un-asnwered when you solved problem , post the solution it might be useful for others also.
Regards
Krishna Acharya

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

BPEL to JDE 811, parameters are passed as zero

Hi,
We have finished all configuration from Adapter Installation guide as well as from User's guide.
When we are making a call from our BPEL to JDE 811 functions,
1) For the functions that are not having any parameters (e.g. GetAuditInfo), are returning correct outputs or say valid response. but
2) When we make a call to function that are having parameters (e.g. GetYearDescription, GetEffectiveAddress), the values of the parameters are being passed as zero. Or JDE is sending responses like the parameters we passed were absolute zero.
like for GetYearDescription, i'm giving following XML as input,
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body xmlns:ns1="http://xmlns.oracle.com/JDE_SERVICE2">
<ns1:jdeRequest type="callmethod">
<callMethod name="GetYearDescription" runOnError="no">
<params>
<param name="mnCalendarYear">95</param>
</params>
<onError abort="yes"/>
</callMethod>
</ns1:jdeRequest>
</soap:Body>
</soap:Envelope>
But instead of 1995, we are getting response as 2000 as parameter values is somehow passed as zero.
We have checked on JDE side and tested above functions are working OK.
Can anybody help us and say why the values are being treated as zero.
Thanks,
Nirav

Hi,
Thanks for the response, but I'm still facing the issue.
As you suggested, I configured my Application Explorer for Attribute Style and get connected. I generated the WSDL and Schema for GetYearDescription. I created the BPEL process and again gave the input as I mentioned above, but it is still giving me 2000 as output. Am'I following the correct process ?
Invoke Audit Trail from BPELConsole for after running the process is as below :
<messages><Invoke_1_GetYearDescription_InputVariable><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="input_GetYearDescription"><jdeRequest type="callmethod" session="" xmlns="urn:iwaysoftware:jde/services/JDEJAVA_CMFGBASE/B3000260/GetYearDescription">
<callMethod name="GetYearDescription" runOnError="no" xmlns="">
<params>
<param name="mnCalendarYear">95</param>
</params>
<onError abort="yes"/>
</callMethod>
</jdeRequest>
</part></Invoke_1_GetYearDescription_InputVariable><Invoke_1_GetYearDescription_OutputVariable><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="response-headers">[]</part><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="output_GetYearDescription"><jdeResponse xmlns="urn:iwaysoftware:jde/services/JDEJAVA_CMFGBASE/B3000260/GetYearDescription" user="PSFT" type="callmethod" session="6656.1211956064.15" environment="DV811" role="*ALL">
<callMethod name="GetYearDescription" runOnError="no">
<returnCode code="0"/>
<params>
<szYearDescription>2000</szYearDescription>
</params>
</callMethod>
</jdeResponse>
</part></Invoke_1_GetYearDescription_OutputVariable></messages>
And here is my WSDL which I generated with Attribute_Style JDE Connection from Application Explorer :
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="GetYearDescription"
targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/JDEdwards/JDEOne/GetYearDescription"
xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"
xmlns:iWay="http://xmlns.oracle.com/pcbpel/adapter/iWay/"
xmlns:GetYearDescription="http://xmlns.oracle.com/pcbpel/iWay/wsdl/JDEdwards/JDEOne/GetYearDescription"
xmlns:pc="http://xmlns.oracle.com/pcbpel/"
xmlns:iWayRequest="urn:iwaysoftware:jde/services/JDEJAVA_CMFGBASE/B3000260/GetYearDescription" xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:iwaysoftware:jde/services/JDEJAVA_CMFGBASE/B3000260/GetYearDescription"
xmlns:ns="urn:iwaysoftware:jde/services/JDEJAVA_CMFGBASE/B3000260/GetYearDescription" elementFormDefault="qualified">
<xsd:element name="jdeRequest">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="callMethod">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="params">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="param" minOccurs="0" maxOccurs="2">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="name" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="mnCalendarYear"/>
<xsd:enumeration value="szYearDescription"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="onError" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:any minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="abort" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="yes"/>
<xsd:enumeration value="no"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="name" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="GetYearDescription"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="app" type="xsd:string" use="optional"/>
<xsd:attribute name="runOnError" use="optional">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="yes"/>
<xsd:enumeration value="no"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="returnNullData" use="optional">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="yes"/>
<xsd:enumeration value="no"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="trans" type="xsd:string" use="optional"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="type" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="callmethod"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="session" type="xsd:string" use="optional"/>
<xsd:attribute name="sessionidle" type="xsd:string" use="optional"/>
</xsd:complexType>
</xsd:element>
</xsd:schema>
...Response Schema ...
Can you tell me that what exactly should be my input XML. soap:Envelope and soap:Body are required right ?
Thanks,
Nirav

How do I code relative links as function parameters within Templates?

I am a newcomer looking for best practices for a "How Do I?" properly code relative links as function parameters within an Adobe template (DWT) which accomodates page creation at 2 different level of folders. Dreamweaver doesn't appear to handle auto-correction of relative links as function parameters as far as I can see. It's not clear to me what the best practice I should be following. While this is not exactly a SPRY question, I am hoping that someone using the Spry.Data.XMLDataSet had already found the best practice to use.
My Site
-- Multiple pages at this level and the parameter needs to be "_includes/UnitSideNavigation.xml"
SubFolder
-- Other pages at this level. and the parameter needs to be "../_includes/UnitSideNavigation.xml"
And this is the particular code snippet within a non edtable template area I would like to work for 2 levels of pages created from the template.
<script type="text/javascript">
var dsItems1 = new Spry.Data.XMLDataSet("_includes/UnitSideNavigation.xml", "/links/firstlevel");
var dslinks = new Spry.Data.NestedXMLDataSet(dsItems1, "secondlevels/secondlevel");
</script>
My environment is Windows/Vista using latest CS4 dreamweaver.
Any pointers appreciated. This is learn time for me. Hope I have made myself clear. Andy

I use serverside includes instead of DWT for exactly that reason. Not only that, if you change anything within the template you must re-upload all of the files affected by the change; only the modified include file needs to be uploaded.

Performance... Why a function column in a view is executed more than once...?

Why a function column created inside a view is executed more than once when called more than once?
EXAMPLE:
create or replace view aux1 as
date_column,
any_function(date_column) column1
from any_table
create or replace view aux2 as
column1 c1,
column1 c2,
column1 c3
from aux1
select * from aux2
It will execute 3 times the function any_function... logically the value will be the same for all columns...
I understand why!... are 3 calls... but...
Why not to create a "small" verification and if the function column was execute replace the second, the third... value? ... instead of execute 3, 4... times...
tks
Braga

Actually, this is more than a performance issue. This is a consistency problem. If the function is NOT deterministic then you may get different values for each call which is clearly not consistent with selecting 3 copies of the same column from a row. Oracle appears to have fixed this in 9i...
Connected to:
Oracle8i Enterprise Edition Release 8.1.7.2.0 - Production
With the Partitioning option
JServer Release 8.1.7.2.0 - Production
create view v1 as select dbms_random.value(1,100) r from dual;
create view v2 as select r r1, r r2 from v1;
select * from v2;
          R1           R2
          93           74
Connected to:
Oracle9i Enterprise Edition Release 9.0.1.3.0 - Production
With the Partitioning option
JServer Release 9.0.1.3.0 - Production
create view v1 as select dbms_random.value(1,100) r from dual;
create view v2 as select r r1, r r2 from v1;
select * from v2;
          R1           R2
          78           78Richard

Why do comments in comments list disappear when file is saved after a signature is added?

When working with a workpaper file we are using sticky notes, highlight, adding text to annotate a file. Then later we go back and add "place initials" by things that we verify either have been done or the workpapers support that statement. Upon saving the file before adding the initials the file name is XXXX.pdf and the 110 comments I've made in the file are listed in the comments list. Then when I add my initals the file name changes to XXXX-signed.pdf and the 110 comments I've made are still present, but not viewable in the comments list nor when I click on the sticky note is the information in the note viewable. Why would this information disappear? How do I get it back?
If there is no fix for this Adobe...this is a great reason for my bosses to decide not to spend the thousands of dollars it's going to cost us to buy and implement your software throughout our firm. We need to retain the comments on a workpaper file as well as be able to inital and sign our workpapers. Many people work in a single workflle and putting our intials next to an item tells the reviewer that not only did we see the comment from the client, but we also double checked to make sure the inforamtion was input into the system and included in the workpapers farther back in the file.
Any help from the user community would be apreciated.
Tanya

I replied to this with a hacky solution over at Stack Overflow: http://tinyurl.com/ybwjfeg
I would prefer that this is resolved via a bug fix, because it certainly appears to be a bug.

Parameters are not Passed in a Struts(JPDK) Portlet

Dear All,
I am getting below problem in Oracle Portal Environment(10.1.2)
I am passing news_id parameter along with title from one page to another page like below code
In CompanyNewsShowPage.jsp
<tr>
<td class="desc">
<%
page_url ="/showpageNews.do?news_id="+com_events[0];
// System.out.println("value of page url : "+ page_url);
%>
<input type="hidden" value="<%=page_url%>" id="hdnpageurl"/>
<pdk-html:link page="<%=page_url%>" styleClass="desc">
<%
String obj_title= com_events[1];
if((obj_title.length())>30)
out.println(obj_title= obj_title.substring(0,15)+ "...");
else
out.println(com_events[1]);
%>
</pdk-html:link>
</td>
TO passing
shownews.jsp
The code for accepting parameter is below
<%
System.out.println("value of newsid :"+ newsid);
String news_id=request.getParameter("news_id");
if(news_id !=null)
newsid= Integer.parseInt(news_id);
System.out.println("value of newsid :"+ newsid);
%>
Kindly any one help me how to pass the parameter from one page to another page above problem, because our go live date is very close.
But same code it is works in IE browser, but not working after deployed in Oracle Portal Environment.
However, the
parameters are not passed from the form to the Struts action. When retrieving the parameters, then
a null value is retrieved, even when the parameter was specified in the form.
Regards,
Chandrashekhara
Message was edited by:
user487286
Message was edited by:
user487286

Hi Anton,
I make some tests and it appeared that it's only the output parameter which is not passed through the step (why ?).
I get this output parameter by a post-running action which parse the joblog and retrieve the sequence number at the line with the pattern "vendor" (hereunder) :
100601 20091008 00 516 Job started 0
100601 20091008 00 550 Step 001 started (program ZCO_MANAGE_FILE, variant ECLO2, user ID ABAPUSER) 0 001 ZCO_MANAGE_FILE ECLO2 ABAPUSER
100601 20091008 00 001 No vendor specified 0 00233
100602 20091008 00 517 Job finished 0
Here is the postrunning action script wich was working before we upgrade :
JobFile log = jcsJob.getJobFileByName("log");
if (log != null)
    com.redwood.scheduler.api.search.SearchResultSet myResultSet = log.search("No vendor specified");
    com.redwood.scheduler.api.search.SearchResult myResult = null;
    while (myResultSet.next())
      myResult = myResultSet.getSearchResult();
      String [] line = myResult.getLineText().split(" ");
      JobParameter jp = jcsJob.getJobParameterByName("VendorCode");
      if (jp != null)
        jp.setOutValueString(line[line.length-1]);

SAP fails to find uninstaller or uninstaller parameters are not passed

We have a custom add-on , and we intend to deploy the add-on with professional quality. However I have a issue with the uninstaller area.
Scenario 1;
Installer name = AddOnInstaller.exe
Uninstaller name = AddOnUnInstaller.exe
I have created a proper uninstaller and have created the ARD file with the uninstaller listed there. The proper parameters were given, However when registering the add-on ( with SAP) , SAP throws a message saying that uninstaller could not be found. However the uninstaller is present in the given path. I have checked the path in the ard file too. SAP however installs the add-on properly.
Also During the install SAP copies the Installer.exe to the local profile temp folder, and runs from there. Does this have something to do with SAP not finding the uninstaller?
Scenario2:
This time I tried creating the Install and Uninstall function within the same program. So I have one exe now called AddOnInstaller.exe
I have set the installer in the ard file to the AddOnInstaller.exe and given the proper parameters. And I have set the Uninstaller in the ard file to another parameter such as /u|uninstall;.
When registering the add-on within SAP, SAP now dose NOT give an error ( could not find uninstaller ). And also the add-on installs properly.
Within my AddOnInstaller.exe, I check the command line to see if the command line is for an Install, or an Uninstall.
However when the add-on is removed and deregistered, when I log back in to SAP, and when SAP runs the uninstaller, it passes Install parameters to the AddOnInstaller.exe. I have checked this with message boxes. Should it not pass Uninstall parameters as given in the ard file?
I need a fix for this or a workaround please. all help is appreciated.
regards,
Indika.
Message was edited by: changed the header title
        Indika Dekumpitiya

yes the fixing the parameter helped, now SAP passes the correct parameter. I pass /u ( no | hwoever ).
    vCommand = Split(Trim(Command), "|")
    mInstallPath = Trim(vCommand(0))
    If UBound(vCommand) > 0 Then '---means Install paramaters
        mInstallerPath = Trim(vCommand(1))
    Else
        bUninstall = True
    End If
    If bUninstall Then
        Call UninstallAddOn
    Else
        Call Install
    End If
this code above worked, thanks.

The page parameters are not showing in the URL .

I my appliaction all the pages have textboxes with some values . But the URL for none of the page shows the parameters like every page has url :
http://127.0.0.1:8080/apex/f?p=105:8:598450314306501::NO:::
but none of the page parameters are being shown . What is the problem here
please help

You can setup a page branch that responds to your specific button and within that branch definition you can specify page items and values to be set when that branch fires.
Is there a specific reason that you want the values passed on the URL? That's not really required to make ApEx function properly.
Earl

Parameters are not created for M0001 feature

Hi Friends,
During Hiring activity in IT0002 after entering all the fields, while saving i got a warning message - parameters are not created in M0001 feature. Please give me your views & answers why i got this message.
Edited by: sharada vemula on Apr 4, 2010 11:31 AM

Hi,
Go to PE03 enter M0001
create a structure till Personal Area and enter **** unless you want to maintain Administrator group in here.
Hope this helps
Ajay

Why "OCIAQListen" function parameters are commented in ociap.h file

Similar Messages

Maybe you are looking for