SAP Diagnostics Summary Details Issue

Hi,
I have Installed
1. Loadrunner Controller 9.1
2. SiteScope 9.0
3. Diagnostics Server 7.0
4. Diagnostics Collector 7.0
on the Same Machine.
I am doing performance testing for SAP R/3 Applications (ECC 6.0 to be precise)
I am able to get data in SAP Diagnostics OS Monitor, Work Process and Average Response Time, but SAP Diagnostics Summary is not getting populated with any data. It is Empty.
Please refer the attachment and kindly help me in resolving the issue.
Thanks in advance,
Regards,
Chinnadurai R

Hi Srinivasarao,
Just now I had a chance to look into one ESS system and was able to figure out the SC name.
The missing class:
Caused by: java.lang.NoClassDefFoundError: com/sap/xss/per/model/mac/Hrxss_Per_Subtype_Info
it belongs to ess~per, and this ess~per belongs to Software Component SAP_ESS.
Please check the version of SAP_ESS.
If the version is fine, please redeploy it.
BR, Tom

Similar Messages

Issue Management - Change Detailed Issue Description

Hi Dears,
I would like of change the default text in field Detailed Issue Description in create of Issue. Somebody know where I make this change?
Thanks a lot
Best
Diego Gaspar

Hi,
The Item Description field in the Issue for Production document is taking the value from the Item in the production order which has issue method as Manual. So by default it takes the value of the Item.
May be you can explain the reason behind such a requirement for further checking.
Kind Regards,
Jitin
SAP Business One Forum Team

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.

SAP HR Active Sync Issue

Hi,
I encountered SAP HR Active Sync issue: The IDM seems can't receive the IDOC but SAP side says the data already passed to port OK.
I enabled the verbose mode of the Active Sync logs and it is repeating:
2009-06-04T17:07:08.750+0800: IDOCs of message type HRMD_A will be processed.
2009-06-04T17:07:08.750+0800: {jco.server.gwhost=10.153.3.20, jco.server.progid=IDMRFC, jco.server.gwserv=sapgw01, jco.server.trace=1, jco.server.unicode=1}
2009-06-04T17:07:08.750+0800: Started IDocServer (IDMRFC)
2009-06-04T17:07:08.750+0800: Done initializing SAPHRActiveSync resource adapter.
2009-06-04T17:07:08.750+0800: SARunner: loop 0
2009-06-04T17:07:08.812+0800: Started, paused until Thu Jun 04 17:07:08 GMT+08:00 2009
2009-06-04T17:07:13.812+0800: Pause completed
2009-06-04T17:07:13.843+0800: Polling
2009-06-04T17:07:13.843+0800: Poll complete.
2009-06-04T17:07:13.843+0800: SARunner: loop 1
SAP side transaction WE02 shows the IDOC:
IDoc sent to SAP system or external program: Data passed to port OK
SAP HR Active Sync resource reference says:
1. Enter transaction code PFAL.
2. Insert the Object Type P for person objects.
3. Enter an Employee's ID for the Object ID or select a range of employees.
4. Click Execute.
5. Ensure that the status is set to passed to port okay.
6. The IDoc has been created. Check the Active Sync adapter log file to verify that
an update was received.
Now why I can't see the IDOC logs in the active sync adaptor log file?
Thanks!

Hi Wushilin,
Did you ever find a solution to this?
Thanks

SAP-ISU consultant details

Hi friends, can any halp me to know SAP-ISU consultant details,
what are all things i have in that SAP-ISU, whether it's having any programming part like ABAP,

Hi ARUNKUMAR´,
gas, water, elelctricity:
All a mass business: Big numbers of customers, much bigger numbers of document items.
Main focus is on (sub-module) FI-CA AKA RMCA, means contract acounting. Here you have an interesting kind of userexits: There are hundreds of pre-defined (and well documented) events. You can assign own FUNCTIONS to the events to enrich, change or check data.
Billing, dunning and payment procedures processed in parralel; quite complex organization of the parrallel processing transactions.
Alvaro is talking of the PRINT WORKBENCH which integrates the (SAPSCRIPT) forms handling and programming, but you can do a lot more with it.
Also important/interesting is the customer master data organized using the SAP BUSINESS PARTNER model.
This is ISU in short.
Note: The main functions of IS-U are also used in Telecommunications (IS-T) and Media (IS-M).
Regards,
Clemens

Summary Alert Issues - Summary Alert Being Sent Out as Multiple Emails

I'm sure many of you have seen the various posts online about Summary Alerts that are supposed to show changes over the last 24hrs in a single email being sent out as either multiple emails containing a random number of items per email, or individual emails
for each item that was updated. The question I have is... Has this issue been resolved with SP2 or any of the Post-SP CUs?
One of my users mentioned that the August 2014 CU was supposed to have a fix for this issue, but I am unable to find any documentation specifically mentioning alert handling or the Summary Alert issue mentioned above.
Current Environment is SP1 + Aug 2013 CU (We're a tad behind -- but I'm working on that)
Any information would be helpful.
Thank you!
MH

Hi,
I suggest you to delete the existing Rule and setup a New Rule.
I have tested this on my lab and it works fine.
You might want to refer to the below article on Setting up Alert Notifications
https://msdn.microsoft.com/en-us/library/azure/dn306638.aspx?f=255&MSPPError=-2147217396
Hope this helps !
Regards,
Sowmya

I need Bangalore SAP office Contact details

Hi,
Could you please provide Bangalore SAP office Contact details please.
Best Regards,
Kolli. Durvasulu

http://www.sap.com/india/services/education/index.epx -- Please follow this link.... All information is there including toll free numbers.
rgds
Koushik

Report with Summary & Detail - Exporting to PDF in Crystal Report

Hi,
I am using Crystal Reports XI (release 2). I am trying out a report with Summary and Detail sections.
Requirement:
1.     Report should display both Summary and Detail Sections
2.     Summary section should be displayed first followed by Detail Section
3.     A field in summary section should have a hyperlink to Detail Section
4.     On clicking the hyperlink the user should be navigated to the corresponding detail record
5.     User should be able to download the whole report as a single PDF (i.e., both summary and detail together)
Implementation in Crystal Report:
This feature could be implemented using
a.     Linked On Demand Sub report
b.     Using Hide (Drill down ok) option
c.     Hyperlinks
Issue Faced:
I used the on demand sub report option. When i clicked on the sub report (hyperlink), the details get displayed. But the details get displayed in separate viewer and hence when we export to PDF both summary and detail are not getting exported together. User has to select each detail report and export to PDF. Is this a limitation in CR XI? - proprietary Crystal Report features, such as drill-down and on-demand subreports, are supported only in the native Crystal Report format. These special features are ignored when exporting a report to a non-Crystal format like pdf.
Is there any workaround for exporting both the summary and detail (in subreport) as a single PDF file?
Any help will be greatly appreciated.
Thanks,
Viji.

Hi
Hyperlink would not be a solution to what you are asking for.
If you want to see the records related to a particular employee id by clicking on emp id, you can try the below:
- Apply a group on employee id on the main report.
- Insert a subreport with the required fields and place it on the Employee id Group header. You can put a name of the subreport as "Check Employee details" or something else as per requirement and make it a on demand subreport.
- Link the subreport on Employee id.
Hope this helps!!!
Regards
Sourashree

SAP script printout alignment issue

Hi Experts,
I have facing one Script Printout Alignment issue.
SAP Script Form printing some Values in Table format.
While debugging( in debug mode ), I am getting the correct Alignment ( Proper table format with values ).
But in printout the Alignment( The vertical and horizontal lines are not printed properly ) is not correct.
Thanks in Advance.

HI Glen Anthony,
I am not using any printer details.
from the Spol (SP01) I am checking the print priview.
Success in debug mode but not in Print.
Please suggest.
Thanks

SAP NW PI license issue

Hello,
I installed PI70 some time back and ordered SAP for license key. But, due to issues i have to re-install it later. What happened here is the hardware key is changed after the installation. Is it means i have request again SAP to get license key to match my Hardware key.
Hope it is unque to Message server, i mean when you install PI (Message server) it also generate this hardware key.
Thanks,
Srinivas

Hi
You send request sap for new licence key they will give you this Then you apply this When you change hardware The hardware key changed so you send detail to service.sap.com/licence
Thanks
Pankaj Kumar

SAP SM architecture (detailed information)

using solution manager 4.0
need help finding <b>detailed</b> information regarding Solution Manager architecture. the documentation out on <a href="http://help.sap.com">SAP Help</a> and <a href="http://www.sdn.sap.com">SAP portal Help</a> is too high level (often simply configuration steps rather than logical description behind key concepts).
not concerned if people tip me off on books through amazon or blogs online or whatever but need to find the following info rather quickly:
a) regardless of system type (Java/ABAP) my understanding is that the SAP system is defined through Solution Manager. a SAP system (again my translation) is logically associated with a particular lifecycle stage (development/test/production). looking for detailed definitions of SAP systems, client instances (0-998 possible per system), and the types of configuration/data associated with clients.
b) transport mechanism in relation to SAP systems and clients within a SAP system
c) calculations as to how many SAP system per machine are possible in regard to the type of application hosted
thanks in advance / Matthew Young

Please check this thread to find out more:
copy express Issue
You may search more here since most info you can find within this forum because most users are here.
Thanks,
Gordon

Raising Customer Messages with SAP OSS on BCS issues

Hi guys,
I'd be keen to know everyone's opinion on raising customer messages with SAP OSS, in particular on BCS.
Often I find that my colleagues are hesitant to raise a note with SAP because they think it either takes too long or they don't get a satisfactory answer.
Whereas as soon as I see something fishy, that I cannot explain I will check my logic once more, check on SDN, check existing OSS notes, then raise a Customer Message immediately (while I continue to investigate/test).
This is partly due to my experience that half the time I feel like a guinea pig in BCS, perhaps because BCS is not as widespread as other modules and i may be the first to try something so may be first to experience the problem.
The first line response (often from Shanghai) usually tries to send the message straight back but I find with a little persistence, clear (and irrefutable) documentation , you soon get through to the experts in Germany (or is it Czech Rep?) who actually understand the issue.
The client has paid a lot of money for the service through their SAP licensing and maintenance fees, so I have no qualms about 'reporting a product error' when I see one.
Also, I find a lot of BCS documentation is out of date, not updated as new releases/EHPs come out, eg I recently relied on the contents of OSS note 936590, which was wrong for BCS 604. So I raised a customer message and requested that they update it, which has now been done - this is too late for me but might help someone else.
Raising a Customer Message with OSS is not an excuse to avoid doing your job, but where there is a genuine error in BCS, I encourage others to raise OSS notes and persis with them until a satisfatcory response is received.

Concur with TheScotsman.
The situation is almost the same: the 1st line support (India) very often beat back the costomer message without going deep into the problem. However, if we persist and provide additional details (or when the message was made very professionally and bypassed the 1st line) the message was rerouted to consultants from Czeck Rep.). In this case the progress was significant. Since the client do not provide access to the system, in a couple of times we made a remote session: the support guy gave directions what to do in the system and where to look for some details. The problems were solved in a half an hour.

SAP GUI with SNC logon and Hummingbird Exceed - SAP GUI window size issue

We have discovered an issue when SAP GUI 7.10 is used to logon via SNC and Hummingbird Exceed is used on the same workstation to logon to a UNIX system either via x-windows or telnet.
When the user logs onto a UNIX system using Hummingbird Exceed, then uses SAP GUI to logon to a SAP system with SNC authentication, the SAP GUI authentication works, but the favourites list is not fully displayed and has to be resized before any of the entries are available.
Has anybody else seen this issue, and do they know if there is a fix available ? We wondered if there might be an issue with fonts or some other sort of conflict between Exceed and SAP GUI, but it is strange that the problem only occurs if SNC authentication is being used, and when userid+password is used to logon to SAP the problem does not occur.
Cheers,
Tim

Hello Tim and Wolfgang,
I was curious too as I found it interesting... so I tested a few combinations, but could not reproduce what Tim has described, at least not before my CPU reached 100% and the applications stopped responding (~2GHz processor, 1GB RAM, 48 kbps connection, latency ~ 2 x width of the Pacific Ocean, but Backend 7.00!).
However I did notice some indications which might be a help (based on 7.00!):
Back in 4.?? there was a problem in that large menus could not be searched(!). Sorry, I don't have access to SAP now, but from memory the note # was 444043 (or very similar) and introduced a form routine for large menus - from a printscreen I still have the message number which led me to the note - 'I476(S#)'.
The system certainly distinguishes between MENU_TYPEs and the above note corrections could be found in several locations relating to the SAP menu 'S', the role menu 'A' etc, but I could only see that for favourites 'F' this is implemented for the menu search (when searching, not when loading).
@ Tim: Ask you customer to create a favourites menu which only has 1 node or max 2 (certainly not more than 4!) and ~ 20 executable objects in it (not more than 30!)? Can they under any conditions achieve the described problem with such a menu?
If not possible to reproduce, then the closest I could guess is a maximum limit of 4 nodes and max 30 objects for a 'F'avourite menu, before it is a minimum candidate for "performance problems" and consideration to be converted to a role ('A'ctivity group) menu instead.
Sorry that I can only help by speculating, because I could not reproduce what you have described.
Hopefully this problem will not happen to me in the New Year, and hope you will solve it for the rest of the year
Cheers,
Julius
Updated memory (not RAM) by: Julius Bussche on Jan 3, 2008 9:07 AM

Mail attachment generated in UDF in SAP PI 7.1 - Issue with line feed

Hello,
Situation is:
Implemented a scenario in SAP PI 7.1 with a mail receiver following this thread:
/people/samuel.chandrasekaran2/blog/2008/10/06/xi-mail-adapter-dynamically-building-attachment-and-message-body-content-using-a-simple-udf
which is about moving message lines from sender into an attachment forn the receiver mail.
It is working great!
The receiver gets the mail including the attachment with all added lines.
But when opening this mail there is an issue depending on the program we are using to open the attachment
which is defined as txt file
- Using MS Editor 5.1 (Windows XP 2007, SP3) the Carriage returns and line feeds (added with
in the UDF) to separate the message lines are not recognized. In the Editor each
    is shown as □   within the text. Word wrap (flag set in the editor) is different to the carriage return/line feeds set in the file.
- Using MS Notepad 5.1 (Windows XP 2007, SP3)   situation is the same but
    is NOT shown as □ , it simply seems to be unvisible. Word wrap (flag set in the editor) is different to the carriage return/line feeds set in the file.
- Using Word 2007 the carriage returns are recognized and used in a correct way to display the file content. But now mutated vowels (äüö) are not recognized. They are displayed as
So I followed this thread:
http://help.sap.com/saphelp_nw04/helpdata/en/96/f04142099eb76be10000000a155106/content.htm
Nice....
In the editors there is no change, but when opening the file in Word it asks now how to convert the file content
(proposing UTF-8) and Word recognizes mutual vowels.
But there seems to be a side effect....
Following the second link, PI recognizes an error.
This is the error message.
MP: exception caught with message Null as XI message received (PrincipalData in ModulData is null)
Adapter Framework caught exception: Null as XI message received (PrincipalData in ModulData is null)
Delivering the message to the application using connection Mail_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Null as XI message received (PrincipalData in ModulData is null).
But the message is sent to the mail recipient which could be ok if PI would not repeat the mail sending now for several times.
So we will receive not one but a number of mails.
So we removed the modul recommended in this help link from the channel.
Result: Behaviour in Word changed now to the described one. But the errors are no longer coming up in channel monitoring incl. message send repetition. So this is a first success. But the partner wants to process the files first with one of the named editors. So we are looking for another solution now to fix the last issue!
Your ideas are really welcome!
Best regards
Dirk

Hi,
as I found this in wikipedia:
Another common problem is the use of '\n' when communicating using an Internet protocol that mandates the use of ASCII CR+LF for ending lines. Writing '\n' to a text mode stream works correctly on Windows systems, but produces only LF on Unix, and something completely different on more exotic systems. Using "\r\n" in binary mode is slightly better, as it works on many ASCII-compatible systems, but still fails in the general case. One approach is to use binary mode and specify the numeric values of the control sequence directly, "\x0D\x0A".
Back to my issue:
In the UDF I am adding "\r\n" but only the "\n" seems to survive!
In Mapping test line feeds are available and the lines are shown as expected.
Using Notepad ++ to open the created txt file from the mail shows that LF is in the file at each end of line but CR is missing.
CR is only at the end of the last line in the file and is not from the UDF that creates the mail or the UDF that creates the attachment lines. Seems that this is added somewhere else behind the mapping.
This is what I found in galileo computing
(http://www.galileocomputing.de/glossar/gp/anzeige-11241/FirstLetter-Z, SORRY, only available in german language!):
In Parsing of XML-Documents the XML-Parser changes the end of line delimiter internally in general to a simple line feed (LF, #0A) as usual in UNIX. ..... In Windows this could result in problems with readability of source texts (e.g. in Notepad) which can be solved by choosing the right editor.
My target application is on Windows and not able to "choose" the right editor (PI system is on windoes OS too) !
But Im wondering where the CR at the end of the text comes from when all the \r\n will be replaced with \n as described.
Ideas are really welcome!
Best regards
Dirk
Edited by: Meinhard Dirk on May 31, 2011 2:45 PM

SAP Diagnostics Summary Details Issue

Similar Messages

Maybe you are looking for