C_PXSUP_90

Using SAP Enterprise Support :---

The amount of time that a customer message has been the ----
Mission Critical Support ----
Recommend to the end user to wait for the next---
The time needed to display report data when ---

Basic ABAP Programming (using the Workbench):-

Enter transaction code WORKBENCH---

Display a list of possible input values---
Search for possible entries---
To maintain documentation (for example, documentation ---
Sm30---
Repository Information System (SE84)---
Double-click the keyword---
ABAP Editor---
Enter/debugging in the command field---
A client has its own database---

Using debugging tools for root cause analysis:-

Test the failed update module in SM13---

Database platform and release, for example, oracle ----
Error messages of application programs---
Until the entry is overwritten (circular file)---
SM13---
Fixed Values ----
All screens, modules of the flow logic, and ABAP message ---
Using SAP tools for root cause analysis:-

ALL SELECT statements in a n ABAP program that lead to a buffer access---

The system ----
A return code is a unique key that is sent from the ABAP program to the ----
Forms -----
The ABAP modules that have been called during program execution ---
Exactly one Open SQL statement ----
Dump Analysis (ST22)---
Message server ----

Basic understanding of SAP Solution Manager:-

Customer data for customer relationship management (CRM)---

Report development ---
An easy navigation through a central role-based access point----
Human Resource Management ----
Service Marketplace ----
A comprehensive view on a project/release plan with all ----

Providing solutions to customer/VAR Service Desk:-

Via the Tab SAP Notes in the message---

Call the transaction BP and open the business partner of type Organization----
Within the transaction for message processing----
Checks if a given note can be implemented automatically ---
Sent to customer ----
Incident Management Work Center----
The action ‘update Message with SAP’ is called. In this case,---
SAP system backup---

Problem analysis and advaced concepts :-

Update function module ----

Object Navigator----
You have to wait until the program retruns from the database ---
Update Debugging ---
ST03 (WORKload analysis) ----
Global update ----
Run the program in batch and click on DEBUGGING ----
Message Solving:-

Get a thorough understanding of the issue from the information given -----
Search on notes with customer installation number ----
It is a powerful instrument in organization and reporting within ----
Integrity----
It is an attribute that characterizes the urgencuy of an issue ----
http://service.sap.com /sap/support/partnermessagesearch----
document every activity in the message---
SAP note ----
In the SAP Partner Portal ----
Ask your colleagues for processing this message ----
Components are arranged in a hierarchy, the so-called Component Hierarchy ----
An SAP Note can only be released after dual control ----
Usename and password in your internal message notice----
Try to guess what the customer ‘might’ want to have---
Solve the customer’s issue – no more and no less ----
Up-to-date ----

Root cause analysis using ABAP Debugger :-

Analyze the entry in transaction SU53 (Authorization Data for User)----

Create a breakpoint at Event MESSAGE_SEND----
All datya objects that are defined in the current program ----
The system has not read any entries from the database table ---
The names of modules that are being executed after control returns from the ---
In the element list of the Screen Painter-----
The system will raise an ABAP message ----
The data objects used by the program ----

Understanding architecture in root cause analysis :-

FORM---
To define the field help (F1 documentation ) and field labels that ----
Maintain database tables and views from within R/3 and ---
At the beginning of a report program ---
INITIALIZATION ----
SE30----