View Budget (Task Summary) details

Hi,
I was looking into View Budget (Task Summary) page. I created a view and selected
Supplier Invoices Commited Cost, Purchase Orders Commited Cost, Other Commited Costs, Total Commited Costs columns. I wanted to know technical details about these four columns. Im trying to find the page, Controller , View objects.
Thanks,
Satya

Hi,
I found the Controller and View Object for Hgrid Task Summary which displays cost and effort information.
VPBudgetTaskSumHgridVO.xml
VPTaskHgridCO.class
VPBudgetTaskSumAM.xml
when I was looking into the committed cost logic, I noticed in VPBudgetTaskSumHgridVO.xml the query
SUM(actual_mask * sup_inv_committed_cost) sup_inv_comm_cost, -- Supplier Invoices Commited Cost
SUM(actual_mask * po_committed_cost) po_comm_cost, -- Purchase Orders Commited Cost
SUM(actual_mask * pr_committed_cost) pr_comm_cost,
SUM(actual_mask * oth_committed_cost) oth_comm_cost, -- Other Commited Costs
SUM(actual_mask * (sup_inv_committed_cost + po_committed_cost + pr_committed_cost + oth_committed_cost)) tot_com_cost, Total Commited Costs
TO_NUMBER(NULL) tot_com_cost , -- Total Commited Costs
though the total committed cost was hard coded to null and commented the actual logic here, in row class the logic was implemented as
CommonUtils.divide(CommonUtils.add((Number)getAttributeInternal(112), CommonUtils.add((Number)getAttributeInternal(113), CommonUtils.add((Number)getAttributeInternal(111), (Number)getAttributeInternal(114)))), FACTOR);
And calculation of committed cost depends on actual_mask
as TO_NUMBER(DECODE(fct.plan_version_id, -1 , 1, NULL)) actual_mask
I have couple of question,
what this plan_version_id and why considering only -1 for actual_mask
And, actually I was looking into task summary for Approved Budget Type but the plan_type_id is stored as -1 at the backed pji_fp_xbs_accum_f table for the project I was looking.
And also in the same table pji_fp_xbs_accum_f the values for sup_inv_committed_cost, po_committed_cost and oth_committed_cost is null for the project.
if anybody having any clue about this, please let me know.
Thanks,
Satya Nooker

Similar Messages

Personalization Issue in Task Summary Page

My client is trying to add a new column in the Cost Details table in the Task Summary page (Under Project Performance Reporting in PJT) through personalization. They are on 11i.PA.RUP3 (Screen shot in the attachment).
They have an extended VO which basically is based on the standard Oracle VO with few additional attributes. My client is able to add the column, view the data which was displayed but that newly added column does not appear in the list of available columns when they try to create a personalized view either by duplicating the seeded views like ITD and PTD or from the scratch.
This works absolutely fine in R12, but in 11i, we are having this problem. Does any one can comment, if this is a bug in the product? or is there any patch already available for this?
Many thanks,
Devasish
[[email protected]]
Edited by: user11268976 on Aug 28, 2009 10:06 PM

Ranjit,Thanks for your reply.
I am also facing this same issue.
I just want to know that if userA creates one view,Can userB see this view which is created by userA?
Because in our case what happens when we click on Personalize button,we can see 5 views and all r not able to update.
but when we got from Functional Administrator responsibility and search for this page and Click on User Seeded Views,we can see only 4 views and all are updatable.
I just want to know how can we delete/update fifth view which is only we can see when we click on Personalize button?
Regards
Hitesh

How do I get rid of notes displayed when I view my task list

Is there a way to change the Task display so that it does not show all of the notes I have with a task? I just want to see a clean list of task names when I view my Task list, but the latest iPhone IOS includes all the notes below the task name. This makes my Task list cumbersome and unwieldy. If I want to see a Task's notes, I just want to be able to click on the task to view them, not see them as part of the Task when all the Tasks are in list display. Thanks, Chad

What app exactly are you using?

Week view and task list solutions? Solved: a way to sync notes to Mac.

I've been using a Palm Tungsten T5 for years and routinely rely on the Palm's Calendar week view feature and task list. The week view is indispensable to see where I can fit in appointments. Are there any ways to achieve the same functionalities on the iPhone, whether using built-in iPhone apps or third party apps? The task list would have to include item priorities, due dates, alarms, and ideally repeating events.
I have found a way to sync notes from the iPhone to my Mac using MarkSpace's The Missing Sync for iPhone; notes are synced to the MarkSpace "notebook" application, where you can edit the notes (and copy and paste) and sync them back to the iPhone. This doesn't sync notes with any Apple applications, though.
If I could solve the week view and task list omissions, I could see my way to replace my Palm with an iPhone. (And when ePocrates releases a full suite for the iPhone, I'll be all set.) But in the absence of these, I'll have to keep using a Palm.

I'm in the same boat, unfortunately.
As a life long Palm-User the PIM-functionalities of iCal can only be described as "rudimentary". It is nowhere near DateBk6 for example. And I would be just fine if it would come close to say 50% of it's functionality. Right now it's at about 25%.
- no repeating tasks?
- no tasks+calendar in one view?
- no week view?
- no icons for event/task categories?
Come on Apple, such a great device with the amazing screen resolution, horizontal view etc. and you are not taking opportunity of it and get beat by 10 year old PDA's?

How to create/Map a User as Adminstrator in BPM Worklist to view all tasks

Hi all,
How to create/Map a User as Adminstrator in BPM Worklist to view all the tasks.
Version :Jdev 11.1.1.1.0
Regards
C.Karukkuvel

go to EM , right click on soa-infra -> security -> Applicaiton roles, then click on BPMWorkflowAdmin role. Add your user to this role.
This user will be able to view all tasks in Worklist. you have to click on "Administration Tasks" tab.
Thanks
--Sreeny
Edited by: sreeny on Sep 22, 2010 12:54 PM

How to display summary details at then end of a alv grid?

Hi.
i have a ALV grid with 4 columns.
also i need to print summary details at the end of the grid..
eg..
Total material cost 15.111
total labor cost        5.4444
total material burden 267.88
toal labor burden    253.66
How do i prinbt these details at then eend of a grid?/

Hi
Populate event END_OF_LIST into IT_EVENTS tab and use in the fun module
see the doc for population of different events to display the totals after grid
REUSE_ALV_EVENTS_GET
Description
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.
Reward points for useful Answers
Regards
Anji

Summary-Detail Report

Hi Friends,
I have a Summary-Detail report.
The report has minimum 2 pages.
First page is Summary and 2nd onwards detail...
In the first page, i will print the summary of goods despatched along with the description of goods.
eg:
To
company
..address
Subject...
Body....
Package Type | Qty | Description
Carton | 10 | Contains 100 packs in each carton
............................................ To be delivered as separate packs
..............................................Handle with care.
Despatched date is 12-sep-2009
Pallets | 250 | Despatched date is 12-sep-2009
Tins | 2100 | Despatched date is 12-sep-2009
Signatory..... Date...........................
This is my report structure....Usually one id will have only one package type. But the description against
that ID is stored in a separate table and the each letter in the description is precious. The length of the description
can be 40 to 4000..User is allowed to enter the description as a multi -record or a single record.
In the report, pkg_type and qty is one repeating frame and description is another repeating frame.
I have to print as many characters in the first page can enclose and the remaining characters i need to print after the detail part.
As the description column can contain any no.of characters, i cannot handle it using no.of records...Because if i set to print
first 5 records in the first page and the remaining in last page using serial no.column, then there is a posssibility that the when it reached the third record, whole space is consumed and
report will get extended to second page, this should not happen...summary cannot be given in 2 pages...
Am new to reports..Kindly help me to solve this problem..
Regards
Dora
Edited by: Dora on Sep 30, 2009 8:50 AM

Thanks Lalitk,
As u said...I created a db procedure...becoz i want to make several this kind of report using same table.
For the proc. I gave max.no.of characters as parameter and it returns the two strings ,first with max. no of characters (concatenating the records if it does not reach the max.no) for first page and the other with remainging of the record(s) as string for second page...
Regards
Dora.

Day Limit in Change View "Terms of Payment":Details?

What does exactly does the Daylimit field in
"Change View " Terms of payment": Details "means?
A detail explanation with an EXAMPLE is well appreciated.
Thanks for your time

Hi,
The DayLimit Under Payment Term is Used to specify Perticular date to which you want the " Payment Term" or Condition should apply on the Invoice. Explain you with simple example.
Eg: 1.Payment Term 1001
DayLimit 15
Discount 2%
With the above inputs system Consider only the invoices posted on and before 15th date for 2% discount and for the Invoices posted after 15 of every month the said discount is not calculated or system will not consider the line for discount.
Eg. Payment Term 1001
Daylimit 31
Discount 4%
with the above inputs system consider's invoices posted from 16 to 31 dates for discount of 4%.
So If requirment is like this invoices posted on or before 15 should get 2% discount and invoices posted between 16 to 31 should get 4% discount then you can create the above manner.
Hope you doupt is cleared .
Thanks
Goutam

How to fetch task list details?

I want to fetch task list details against multiple task lists.
Currently i am calling FM EAM_FM_TASKLIST_GETDETAIL in a loop.
Since it may lead to performance issues in the case of large number of tasklists, I am looking for other options.
Is there any other option?

Vivek,
If you only specify those tables you require in EAM_TASKLIST_GET_DETAIL (e.g. ET_HEADERS, ET_OPERATIONS) then the function module will run much quicker.
I'm not sure why your Code Review Team have issues with this method - its common practice to use SAP standard function modules in this way.
The only real way to know if the Code Review Team are correct is to try testing the report in a test/staging system (copy of production).
PeteA

How to view web service definition details using Netweaver ?

Hi,
I have installed Netweaver 7.01 trial version, and I have seen using the Web Service Browser, that all BAPI's are exposed as web services already. I would like to view the web service details for some of these BAPI's, in order to understand the authentication, authorization details for these as I plan to try and call these through java.
I basically want to understand whether they are using BASIC authentication by default or configured to use something else.
Any guidance on this is appreciated.
thx,
-Kev.

Did you try unpublishing it ...
HOW CAN I DELETE SERVICES IN THE SERVICES REGISTRY?
The concept of the Services Registry sees the content of the registry as a mirror of the various backend systems from which you publish into the registry. To ensure consistency, you should not manually delete service definitions from the registry, but instead it is recommended to use the publication rules functionality of SAP NetWeaver Administrator (Java) and SOA Manager (ABAP) to u2018unpublish' service definitions that are no longer required.
However, if you still need to delete service definitions, you can make use of the corresponding API and manually remove service definitions.
from the following link ...
/docs/DOC-8782#section172 [original link is broken]
Regards
M

Download Links for JMS Explorer to view message and its details

Can i get the links for downloading the JMS explorer to view messages and its details on j2ee server.

I checked Hermesjms tool but found that it does not work with j2ee server.
Is there any other JMS explorer tool to view messages and its details on j2ee server specifically.

Change view "Settings for Infosets": Details

Hi,
I would like to know why there is a value of 100 under the heading Settings for Infosets in BW when you go to the 'Change view "Settings for Infosets": Details' screen. What does it mean and what value must I input there?
Your assistance is urgently required
Thanks,

Hi Josef I'm not entirely with you on this one.
When I look on the device Apple TV in iTunes, everything I have streamed to apple TV from iTunes is grayed out but when looking at the photos tab which I have synced is not grayed allowing me to change whatever I want to sync. Is this different to yours? or I'm I misunderstanding your point.

BlackBerry 10 - how to view completed Tasks from within Calendar

How to view completed Tasks entered in Remember, but viewing not just active tasks but completed tasks from within the Calendar? Thank you.

Hi sandy1729,
Welcome to Apple Discussions
You don't say which iPod it is but I have a nano - to check the battery indicator when charging I turn the nano off, then the battery indicator fills the whole screen instead of just the bit at the top right.
See the pictures here:
http://docs.info.apple.com/article.html?artnum=60970
Regards,
Colin R.

Extending master view object to query detail records

I have two view objects, master and detail, joined by a view link. I want to extend the VO so that I can use the detail columns in the master view criteria.
My master view object is OutagesView
SELECT Outages.OUTAGE_ID,
Outages.START_DT,
Outages.END_DT,
Outages.OUTAGE_MESSAGE,
Outages.OUTAGE_TYPE,
Outages.UPDATE_ON,
Outages.UPDATE_WHO,
Outages.NAME,
Outages.OUTAGE_SCOPE,
Outages.OUTAGE_CATEGORY
FROM OUTAGES Outages
And the detail is OutageDetailsView
SELECT Apps.DISPLAY_NAME,
Apps.SHORT_DESCRIPTION,
AppOutages.OUTAGE_ID detail_outage_id,
AppOutages.APP_ID,
AppOutages.NOTES,
Apps.ID
FROM APPS Apps, APP_OUTAGES AppOutages
WHERE Apps.ID = AppOutages.APP_ID
In the view link (OutagesView.OutageId to OutageDetailsView.DetailOutageId) I have checked the boxes to Generate Accessors in both the OutagesView and OutageDetailsView. This has allowed me to build the view criteria in OutagesView referencing OutagesDetailView .
When I try run the AppModule, navigate to the view link and specify detail view criteria get an error:
I can see when it creates the query it is specifying OutagesQRST in the subquery which doesn’t exist
SELECT Outages.OUTAGE_ID,
Outages.START_DT,
Outages.END_DT,
Outages.OUTAGE_MESSAGE,
Outages.OUTAGE_TYPE,
Outages.UPDATE_ON,
Outages.UPDATE_WHO,
Outages.NAME,
Outages.OUTAGE_SCOPE,
Outages.OUTAGE_CATEGORY
FROM OUTAGES Outages
WHERE ( ( (EXISTS
(SELECT *
FROM (SELECT Apps.DISPLAY_NAME,
Apps.SHORT_DESCRIPTION,
AppOutages.OUTAGE_ID detail_outage_id,
AppOutages.APP_ID,
AppOutages.NOTES,
Apps.ID
FROM APPS Apps, APP_OUTAGES AppOutages
WHERE Apps.ID = AppOutages.APP_ID) QRSLTSQ1
WHERE ( (UPPER (DISPLAY_NAME) LIKE
UPPER (:pdisplayName || '%')))
AND (OutagesQRSLT.OUTAGE_ID =
QRSLTSQ1.DETAIL_OUTAGE_ID)))))
If I set the VO to expert mode and override the create method in the view impl with
public void create() {
super.create();
setNestedSelectForFullSql(false);
I get the error SQL error during statement preparation:
SELECT Apps.DISPLAY_NAME,
Apps.SHORT_DESCRIPTION,
AppOutages.OUTAGE_ID detail_outage_id,
AppOutages.APP_ID,
AppOutages.NOTES,
Apps.ID
FROM APPS Apps, APP_OUTAGES AppOutages
WHERE Apps.ID = AppOutages.APP_ID WHERE DETAIL_OUTAGE_ID = :Bind_OutageId;
Can someone please point me in the right direction?
Thanks
Kylie

Hi Erp,
Thanks for your response. The queries in the VOs are fine. It is when jdev creates the view criteria between the two that the problem occurs. In instance 1 it creates an alias OutagesQRSLT which doesn't exist. Had this of just been Outages the query would have run.
I tried the to use the expert mode and override the create method in the view impl as I had seen it suggested in some other posts. This is when I got the second error with the :Bind_OutageId. I assumed that jdev would take care of the binding? Perhaps I am wrong. I did pass a value to :pdisplayName.
I guess I need to know if overriding the create method is the right thing to do? and if so where I might be going wrong.
Thanks
Kylie

Restrict the users to view the column, row details

Experts
For example restrict the sales users to view the purchase price, and restrict the purchase users to view the selling price.
Any inputs highly appreciated

Hi,
Restrict the users to view the column can be done through form settings.
I don't think it is possible to restrict the users to view the particular row details. If user can open the form, no option to hide any rows through authorization.
Thanks,
Gordon

View Budget (Task Summary) details

Similar Messages

Maybe you are looking for