How to activate ABAP Dynrpo in SE80

Hi Experts,
I am using ECC 5.0, and I want to create a web dynpro using ABAP, but in SE80 transaction this option is deactivated, how to activate it ?

Hi Rajesh,
In ECC5.0 you can not work with webdynpro.
Its only avilable with Ecc6 versions.
Check this link also,
Re: ECC 5.0 or ECC 6.0?
Thanks.
Edited by: Viji on Apr 16, 2008 11:29 AM

Similar Messages

Clarifications on How to Activate ABAP Proxies

Hi,
Iam doing Proxy Outbound Scenario
Iam doing the following WEBLOG to activate the ABAP Proxy
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
In this BLOG they have mentioned 3 steps to achieve the requirement.
Do we need to do all these 3 steps in R/3 itself ?? Or do we need to do any one of the step in XI also.
Please Observe the Steps and let me know
Regards
Suman

Hi Chirag,
2) If yes means do i need to create the two RFC's LCRSAPRFC and SAPSLDAPI in R/3 side itself????
U need to create it in Xi and u need to run the SLDCHECK transaction for testing it should show sucessful message.
3) I Already Maintained These two RFC's in XI side. do i need to maintain at R/3 end also ??
No need to maintained at R3.
4) Should i get the SLDCHECK Success in R/3 also ???
In XI not at r3 end.
Are you sure about this?
You need to establish a connection between your Business system and SLD. So you need these RFCs created in Business system (R/3) also. SLDCHECK should run fine on your Business System also.
Regards,
Jaishankar

How to use abap debugger and se80

can any body give easy deatils about it?

Hi
Debugger
This section of the ABAP Workbench documentation provides information on how to use the Debugger as a test tool for finding errors in the source code of an ABAP program.
Functional Overview
Use
The ABAP Debugger is an integrated test tool within the ABAP Workbench. You use it to check the program logic and to find errors in the source code of an ABAP program. In the Debugger, you can step through the source code of a program. The running program is interrupted after each step, allowing you to check its processing logic and the results of individual statements.
As of Release 6.10, you can also run Business Server Pages (BSP) in the debugging mode. You can also display and set breakpoints here. Business Server Pages can be displayed in the Object Navigator when you select an appropriate application under BSP Application.
Features
The Debugger provides an efficient means of identifying errors in ABAP programs. It contains the following functions:
Ways of starting the Debugger
Choosing different views
Choosing different execution options in the Debugger
Displaying source code in the Debugger
Setting and deleting breakpoints
Setting and deleting watchpoints
Stopping a program at a particular statement or event
Displaying and changing field contents at runtime
Displaying ABAP Objects and references
Displaying and positioning strings
Setting and deleting database locks
Opening the ABAP Editor, or Object Navigator
System settings and runtime warnings
Starting the Debugger
There are two possible strategies for starting the Debugger in the ABAP Workbench:
By setting breakpoints then running the program
By running the program in debugging mode.
Setting Breakpoints
A breakpoint is a signal in a specific line of the program source code. This signal indicates to the ABAP runtime processor to stop the program at the relevant line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, refer to Breakpoints.
Direct Processing
You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also a useful procedure if you are not overly familiar with the program and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:
From the Object Navigator
Select a report or transaction and choose Program ® Test ® Debugging.
From the ABAP Editor
Choose Program ® Execute ® Debugging (or the Debugging pushbutton).
From any screen
Choose System ® Utilities ® Debug ABAP.
From any screen
Enter /h in the command field.
Display Modes in the Debugger
When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes.
Display Modes Available Using Pushbuttons
Fields
The scrollable field display contains the contents of up to eight fields. The contents of the three most important system fields are always displayed. This is the default display mode in the Debugger. See also Processing Fields
Table
Displays the contents of an internal table. This mode allows you to display and edit the entries in an internal table. See also Processing Internal Tables
Breakpoints
A scrollable display containing up to 30 breakpoints. Next to each breakpoint is a counter. You can also delete breakpoints in this display. See also Managing Dynamic Breakpoints
Watchpoints
You can set a watchpoint for a field so that the program is interrupted whenever the value of that field changes. This display mode contains a list of watchpoints, the fields and programs to which they are assigned, the current values of the fields, and the conditions upon which the watchpoint is activated. See also Setting Watchpoints
Calls
This mode displays the current sequence of events, and the sequence of calls up to the current breakpoint. The last active call is displayed at the top of the list; previous calls are listed in reverse chronological order. When an event (for example, START-OF-SELECTION) concludes, it is deleted from the display.
Overview
This mode displays the structure of the program. It lists its events, subroutines, and modules, and shows which sections belong to which events. It also displays the section currently being processed.
Settings
This mode displays the current Debugger settings. You can change the settings by selecting or deselecting various options. For further information, refer to Settings and Warnings
Other Display Modes
You can access other display modes by choosing Goto ® Display data object.
Single field
Displays the contents and technical attributes of a field.
Structured
field
Displays the components of a structure, along with their contents and attributes. If you double-click a component, the system displays detailed information for it.
Strings
Display the content and current length of the string. You can also display part of the content by means of offset and length.
Internal table
Displays the type, line numbers and contents of an internal table.
Object
Displays the structure of an ABAP Object.
For further information on these displays, refer to Displaying Attributes and Displaying ABAP Objects
Checking System Programs for Errors
To check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose System ® Utilities ® Debug System from any screen. To stop the system Debugger, choose Debugger ® Debugging off.
Displaying Program Attributes
You can display the attributes Fixed Point Arithmetic, System Program, and Unicode Checks of the program that has just been executed by choosing Goto ® Further Information ® Program Attributes.
Restarting the Debugger
If you choose Debugging ® Restart, debugging mode is stopped and the system takes you to the initial screen of the last transaction you called. If, for example, you started an ABAP program in debugging mode from transaction SE38 (ABAP Editor), choosing Debugging ® Restart will take you back to the screen titled ABAP Editor: Initial Screen. If you want to restart the program in debugging mode, choose Debugging.
Breakpoints
Apart from direct execution of an ABAP program in the Debugger, it is also possible to start the Debugger call by the exact setting of a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The program runs normally until the breakpoint is reached.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For further information, refer to Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.
Directly-set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statement
The Debugger stops the program directly before the specified statement is executed.
Breakpoints
at subroutine
The Debugger stops the program directly before the specified subroutine is called.
Breakpoint at function module
The Debugger stops the program directly before the specified function module is called.
Breakpoint at method
The Debugger stops the program directly before the specified method is called.
Breakpoints at system exceptions
The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are not normally user-specific. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application, when the program execution is always to be interrupted at the same place. For further information, refer to Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints, because you can deactivate or delete them at runtime. They have the following advantages:
You do not have to change the program code
You can set them even when the program is locked by another programmer
You can define a counter that only activates the breakpoint after it has been reached
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For further information, refer to Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Lifetime and Transfer of Breakpoints
A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they are effective during the entire user session, if they are saved by choosing Breakpoints ® Save in the ABAP Debugger. For more details on the subject of sessions and user sessions, refer to Modularization Techniques in the ABAP keyword documentation.
If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
Breakpoints at Statements
You can use this special kind of dynamic breakpoint to interrupt a program directly before an ABAP statement is processed.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at an ABAP statement:
1.Choose Breakpoint ® Breakpoint at ® Statement...
The following dialog box appears:
2.Enter the ABAP statement.
The system sets a breakpoint at all points in the program at which the ABAP statement occurs.
3.Choose ENTER.
The breakpoint applies to all lines containing the specified statement.
Result
The system confirms the breakpoint and adds it to the list in the display. When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Breakpoints at Subroutines
You can use this special kind of dynamic breakpoint to interrupt a program directly before a subroutine is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a subroutine:
Choose Breakpoint ® Breakpoint at ® Event/Subroutine.
The following dialog box then appears:
Enter the name of the subroutine before which you want to interrupt the program. By default, the Program field contains the name of the program that is currently active. The system sets a breakpoint wherever the specified subroutine occurs in the program code.
Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
Breakpoints at Function Module
You can use this kind of dynamic breakpoint to interrupt a program directly before a function module is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a function module:
Choose Breakpoint ® Breakpoint at ® Function module...
The following dialog box appears:
Enter the name of the function module before which you want to interrupt the program. The system sets a breakpoint wherever the specified event, module pool, or subroutine occurs in the program code.
Choose ENTER.
Result
If you entered a valid function module name, the system confirms that the breakpoint has been set. If the function module exists in the system, the new breakpoint is added to the display list.
Breakpoints at Methods
You can use this special kind of dynamic breakpoint to interrupt a program directly before a method is called.
Prerequisites
You must be already running the program in the debugger.
Procedure
To set a breakpoint for methods:
1. Choose Breakpoint ® Breakpoint at ® Method...
The following dialog box then appears:
2. Enter the name of the method and class before which you want to interrupt the program. A breakpoint is then set each time the specified processing block appears in the source code.
3. Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the list in the display.
Breakpoints at System Exceptions
You can use this special form of dynamic breakpoint to interrupt a program immediately after a runtime error has occurred.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at a system exception:
Choose Breakpoint ® Breakpoint at ® System exception.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears.
Static Breakpoints
You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.
Setting Breakpoints
To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program.
program RSDEBUG_01.
if SY-SUBRC 0.
break-point.
endif.
When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 ).
Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it.
However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name.
Deleting Breakpoints
Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities ® Global search. You can also use the Extended Program Check to find them.
If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system.
Dynamic Breakpoints
You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger.
Setting Dynamic Breakpoints in the ABAP Editor
You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor:
Position the cursor on the line of the source code at which you want to set the breakpoint.
Choose Utilities ® Breakpoints ® Set or the Stop icon. The system confirms that the breakpoint has been set.
To display a list of all dynamic breakpoints in a program, choose Utilities ® Breakpoints ® Display. You can use this list to navigate to a particular breakpoint or to delete one or more breakpoints from the program.
Setting Dynamic Breakpoints in Debugging Mode
To set a dynamic breakpoint in the Debugger:
Position the cursor on the line in which you want to set the breakpoint.
Select the line by double-clicking it or choosing Breakpoint ® Set/delete.
The system sets the breakpoint, and displays a small stop sign to the left of the relevant line. If the line already contained a breakpoint, it is deleted.
When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Saving Breakpoints
If you want to leave the Debugger temporarily, you can save your dynamic breakpoints so that they are still active when you return to the Debugger within the same terminal session.
To save the breakpoints that you have set in the Debugger:
Choose Breakpoint ® Save.
The system saves all of the breakpoints that you have set in the current program. These breakpoints will remain active until you either explicitly delete them or log off from the system.
You can also delete breakpoints that you have saved:
By deleting individual breakpoints from the display and then saving again. In this case, only your selected breakpoints will be deleted.
By choosing Breakpoint ® Delete all. In this case, the system deletes all dynamic breakpoints.
Managing Dynamic Breakpoints
The ABAP Debugger provides a convenient user interface for managing breakpoints. To open the breakpoint display, choose Breakpoints, or, from the menu, Goto ® Control debugging ® Breakpoints.
Example
Functions
This display mode contains the following functions for breakpoints:
Breakpoint Display
The scrollable breakpoint display contains up to 30 dynamic breakpoints. For breakpoints that you set directly, the program name and line number at which the breakpoint occurs are displayed. For special breakpoint forms, the list displays the statements, events, subroutines, and module calls at which the relevant breakpoints are set.
Counter
In the breakpoint display, you can specify a counter. When you use a counter, the breakpoint is not activated until it has been reached a specified number of times. For example, if you enter 5 for the counter, the breakpoint is not activated until it is reached for the fifth time. After the breakpoint has been activated, it remains so, and the counter no longer appears in the breakpoint display.
Deleting Breakpoints
Position the cursor on the breakpoint that you want to delete, and either double-click the line or choose Breakpoint ® Set/delete. To delete all breakpoints, choose Breakpoint ® Delete all.
Activating and Deactivating Breakpoints
Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint ® Activate/deactivate.
Watchpoints
Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.
Use
You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.
Features
You can set up to five watchpoints in a program.
See also Setting Watchpoints.
You can also specify the conditions on which a watchpoint is to become active.
You can specify logical conditions between up to five conditional watchpoints.
See Specifying a Logical Expression.
You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in the specified program.
You can change and delete watchpoints.
See Changing Watchpoints.
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables.
See Memory Monitoring with Watchpoints
Setting Watchpoints
If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.
A watchpoint can be either local or global. Local watchpoints are only valid in the specified program. Global watchpoints are valid in the specified program, and also in all the other programs it calls.
Procedure
To set a watchpoint, start the Debugger and proceed as follows:
Choose Breakpoint ® Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears:
Decide whether you want to set a local or global watchpoint.
Enter the program and the name of the field for which you want to set the watchpoint. In the Program field, the name of the program currently running is always defaulted.
If you want your watchpoint to be activated each time the contents of the field change, the definition is now complete, and you can return to the Debugger by pressing ENTER .
To create a conditional watchpoint, that is only activated when a particular situation arises, choose one of the following relational operators.
Operator
Meaning
<
Less than
<=
Less than or equal
=
Equal
<>
Not equal
=
Greater than or equal
Greater than
You can use the Comparison field option to specify whether the comparison is to be carried out with a value that you specify or with the contents of another field. Depending on your choice from step 6, enter a value or a field for the comparison.
Result
The system confirms the watchpoint and adds it to the list in the display. When you finish your debugging session, the watchpoint is automatically deleted unless you have explicitly saved it.
Specifying Logical Links
If you have more than one conditional watchpoint, you can specify a logical link between them:
OR
Only one of the specified conditions must be met
AND
All of the conditions must be met.
Changing Watchpoints
Choose Goto ® Control debugging ® Watchpoints or the Watchpoints pushbutton to display the watchpoint list. The following dialog box appears:
Choose the pencil icon in the line containing the watchpoint you want to change.
Change the watchpoint attributes in the Create/Change Watchpoint.
Choose ENTER .
Deleting Watchpoints
You cannot delete watchpoints by choosing Breakpoint ® Delete or Breakpoint ® Deactivate/activate. Instead, proceed as follows:
Choose Goto ® Control debugging ® Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
Choose the trashcan icon in the line containing the watchpoint you want to delete.
Memory Monitoring with Watchpoints
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables. By placing an ampersand (&) in front of the object name, you can display the reference in question in hexadecimal format. With internal tables, you can also display the table header by placing an asterisk (*) at the beginning of the name.
&objectname
Displays the references of strings, internal tables as well as data and object references
*itab
Displays the table header of the internal table itab
Example
If a watchpoint is set for the object in question at runtime, the program is stopped as soon as the reference is changed. A short dump can be intercepted in this way to stop the program being terminated when the memory is overwritten.
Analyzing Source Code
The Debugger contains an extensive range of functions that help you to analyze the source code of a program. You can step through the source code of a program in four different ways. For further information, refer to Stepping Through the Source Code
For information about functions within the source code display, see Displaying the Source Code
There are also different display modes that provide various information and display the contents of individual fields, tables, and so on:

How to activate a report in abap

hi experts,
how to activate a report in abap?
gerald

First you need a Developer Key to create or activate ABAP Reports. If you dont have any, Please ask your BASIS team. They can generate one for you.
When you done with the report hit 'Activate button' ( A Candle icon on top).
Cheers
Praveen

How to activate & use Refactoring Assistant

Hi Experts,
I want use Refactoring Assistant in ABAP Editor,
I've read a little from this link :
http://help.sap.com/SAPHELP_NWPI71/helpdata/EN/44/2afce330063ecee10000000a1553f6/frameset.htm
But couldn't find menu item in context menu and other menus in ABAP editor , se38 / se80
about refactoring.
Does anyone knows how to activate it?
Thanks.

In short,
1. Select the class and change to the
2. Class Editor. Make sure you are in Change mode.
3. Choose Utilities ® Refactoring Assistant.
The Assistant is started in a separate window.
1. Select the component to be moved and move it to the name of the superclass using Drag & Drop.
You can move several components at one time with multiple selection.
1. Save using the corresponding icon.
2. Close the Assistant.

How to Activate the Table which Doesn't Exist - Can I create Table in SE11

Hi Gurus,
I am a BASIS Person ..so, I don't have much idea about ABAP Developement side . But, while applying patches to one of the SAP Component, I get the following error message ( usr\sap\trans\log ) :
Phase Import_Proper
>>>
SAPAIBIIP7.BID
1 ED0301 *************************************************************************
1 EDO578XFollowing objects not activated/deleted or activated/deleted w. warning:
1EEDO519X"Table" "WRMA_S_RESULT_DATA" could not be activated
1EEDO519 "Table Type" "WRMA_TT_UPDTAB_DSO" could not be activated
1 ED0313 (E- Row type WRMA_S_RESULT_DATA is not active or does not exist )
2WEDO517 "Domain" "WRMA_KAPPL" was activated (error in the dependencies)
2WEDO517 "Data Element" "/RTF/DE_FISCPER" was activated (error in the dependencies)
2WEDO517 "Data Element" "/RTF/DE_FISCVARNT" was activated (error in the dependencies)
2WEDO517 "Data Element" "WRMA_DE_RCLASV" was activated (error in the dependencies)
2WEDO517 "Data Element" "WRMA_DE_RMA_AMNT" was activated (error in the dependencies)
2WEDO517 "Data Element" "WRMA_DE_RMA_INV" was activated (error in the dependencies)
2WEDO517 "Data Element" "WRMA_DE_RMA_OBJ" was activated (error in the dependencies)
2WEDO549 "Table" "V_WRMA_TRCLASVER" was activated (warning for the dependent tables)
2WEDO549 "Table" "V_WRMA_TRCLASVPE" was activated (warning for the dependent tables)
2WEDO549 "Table" "V_WRMA_TRCLPERCL" was activated (warning for the dependent tables)
2WEDO549 "Table" "WRMA_S_STOCK_SELECTION_DATE" was activated (warning for the dependent tables)
<<<
Now, I checked Domain WRMA_KAPPL in SE11 and it diplays that it is partially active :
" The obeject is marked partially active for the following reasons :
   Errors occured when adjusting dependent Objects to a change. Some of the dependent objects could not
   be adjusted to this change. To adjust the dependent objects, you must perform the following actions
   the next time you activate this object.
                    - SET THE SYNP TIME STAMP IN THE RUNTIME OBJECT OFALL DEPENDENT OBJECTS
My question is - how to activate this SYNP Time Stamp.. ?
                      - Once I activate this SYNP Time Stamp.. How do I activate this ..in SE11 or some other
                        TCode..
Any / ALL Help is highy appreciated and would be rewarded with appropriate Reward Points.
Thanks,
Regards,
- Ishan
>> Ok, Now I forcefully activated the Domain and then all the 5 Data Elements in SE11 ...now I have error
     that table WRMA_S_RESULT_DATA and WRMA_TT_UPDTAB_DSO Could not be activated...
     ..And in SE11 > Input the first / Second Table > Excute > Output : Table Does not Exist !!!
      - Now, How do I activate something which does not exist in the first place ?
    Any Input about this ?
Thanks,
Regards,
- Ishan
Edited by: ISHAN P on Jun 19, 2008 3:44 PM

Read note 1152612 - Incorrect component type in structure WRMA_S_RESULT_DATA.
The error occurs in Release BI_CONT 703 Support Package 9.
If you require an advance correction for Support Package 9, make the following manual changes if the InfoObject 0TCTLSTCHG is inactive in your system.
1. Use transaction RSA1 to call the Data Warehousing Workbench.
2. Check whether the InfoObject 0TCTLSTCHG was already activated by the compilation process the first time you called transaction RSA1. You can use transaction RSD1 to check this by entering 0TCTLSTCHG in the "InfoObject" field and choosing "Display". Proceed as follows if the InfoObject is still not active:
3. Go to BI Content activation.
4. Select "Object Types".
5. Open the "InfoObjects" tree and select "Objects".
6. Search for the InfoObject 0TCTLSTCHG and select it.
7. Transfer the object and activate it.
These steps activate the required component type /BI0/OITCTLSTCHG. You can check again in transaction RSD1 to ensure that the InfoObject 0TCTLSTCHG is available as active.
Jacek Fornalczyk

How to activate class method???

Hi All,
How to activate class method?
Class Name - CL_HRCE_MASTERSWITCHES
Method name - CHECK_RELEASED
In se80 this method is showing red, means it is inactive.
Please guide me how to turn it to green?
And there is commented code "* ce_is_released = true."
How to uncomment it?
Is i need to apply access key to do this?
Regards

Thanks for reply.
It means We need to apply access key to uncomment following code in method
Class:CL_HRCE_MASTERSWITCHES
method CHECK_RELEASED .
for pilot customers the functionality is released,
for all others not to be a pilot customer please check note 520965
then activate this line here
ce_is_released = true.
endmethod.
Regards

How to activate guest user

hi guys
can anyone tel how to activate guest and Anonymous Users..
thanks
regards
kamal....

Hi ,
please find some of the information for the Guest USer.
http://help.sap.com/saphelp_nw04/helpdata/en/c2/f4e73ee7442e5ae10000000a114084/frameset.htm
In case of Add-In installation, these users are automatically created on the ABAP side in client 001. If you want to use another client, you have to create these users with their roles in this other client.
User Role
SAPJSF SAP_BC_JSF_COMMUNICATION
J2EE_ADMIN SAP_J2EE_ADMIN
J2EE_GUEST SAP_J2EE_GUEST
User SAPJSF is used for JCo (RFC) communication from Java to ABAP.
User J2EE_ADMIN is the J2EE and Portal Administrator user.
User J2EE_GUEST is used for anonymous logon.
Users with Role SAP_J2EE_ADMIN are automatically mapped to Portal Group Administrators.
thanks
Users with Role SAP_J2EE_GUEST are automatically mapped to Portal Group Guests.
The passwords of these users are defined by the customer during installation.

How to call abap proxy at run time?

hello frnds,
i m working on a scenario in which whenever Invoice is saved in SAP R/3 at that time same data should go to Oracle DB. i m using ABAP proxy on SAP R/3 side and JDBC receicver adapter on oracle side of XI.
so to post data i need to call ABAP Proxy whenever invoice is saved.. i have tried to find out save event for invoice but not able to get... can anybody tell me the solution that how i can call proxy at run time?
thanx in advance.
Regards,
Hetal.....

Hi Audumbar,
Check these ...
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
/people/vanita.thareja2/blog/2006/05/23/bpm-sending-message-asynchronously-and-getting-the-response-from-synchronous-system-using-abap-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
cheers,
Prashanth
P.S Please mark helpful answers

How to activate Printing option in FBCJ transaction ?

Dear all,
How to activate Printing option in FBCJ transaction for cash journal?
It is in suppress mode.
Is it through BASIS/ABAP/Configuration ...... ?
Pl' reply.

Hi:
If the Printing option in FBCJ transaction for cash journal is supressed
excute /nsu53 and you can see the authorization objects.send them to basis administrator. After giving proper authorization, you can print cash journal.
Please let me know if you need more information.
Assign points if useful.
Regards
Sridhar M

How to activate the ATP buckets in APO?

Hi,
We are in the process of changing the ATP buckets in our APO system.
I know the Path in the configuration:
Advanced Planning and Optimization -> Global Available-to-Promise (Global ATP) -> General Settings -> Maintain Global Settings for Availability Check
On the left side you will get three sections:
Global Settings
ATP Buckets (Active)
ATP Buckets (Planned)
I can change the values in (example field Shift Receipt Bucket) the ATP Buckets (Planned) section and save it with a transport. Now the question is how to activate the buckets. Is there another transaction for this? SAP Help doesn't specify how to activate.
Any ideas are highly appreciated.
Thanks,
Mahesh

Hi,
To activate the buckets one need to check the box 'Current' in the options under ATP Buckets (Active). Also, as referred earlier by Dipthi do look up the documentation under:
SAP Advanced Planning and Optimization (SAP APO) -> Global Available-to-Promise (Global ATP) -> Settings for Global ATP -> General Settings for Global ATP ->Definition of Buckets for ATP Time Series ->Activation of Bucket Parameters for ATP Time Series.
The details are as beneath:
Use
If you change bucket parameters (see Definition of Buckets for ATP Time Series), these must be activated subsequently for the ATP time series.
Features
The system activates the bucket parameters in the following situations:
Since activation in each of the situations described below leads to downtime, you should change bucket parameters less frequently than other Customizing settings.
·        Creating the active planning version for a client using transaction /SAPAPO/MVM
If you set up a system again, you should process the bucket parameters before you create the active planning version. The bucket parameters are thus activated automatically.
·        Initializing SAP liveCache for all clients using transaction LC10
In the case of an upgrade, you should process the bucket parameters before activating SAP liveCache. The bucket parameters are then activated automatically.
·        Executing the report /SAPAPO/OM_ATP_REBUILD_TS
The system only rebuilds the ATP time series here.
In this case, the SAP liveCache administrator must execute the following steps:
                            a.      Shut down SAP liveCache.
                            b.      Replace the com-file registration:
                                                  i.       At command line level, go to the SAP subdirectory of the SAP liveCache installation.
                                                ii.       Under Microsoft Windows, save the original registration files SAPAPO.lst and SAPATP.lst (UNIX: libSAPAPO.lst and libSAPATP.lst), for example, by renaming or copying to another directory.
                                               iii.       Under Microsoft Windows, rename the registration file SAPAPO_REBUILD.lst as SAPAPO.lst (UNIX: libSAPAPO_REBUILD.lstas libSAPAPO.lst) or copy it to another directory.
                                               iv.       Under Microsoft Windows, rename the registration file SAPATP_REBUILD.lst as SAPATP.lst (UNIX: libSAPATP_REBUILD.lstas libSAPATP.lst) or copy it to another directory.
                            c.      Launch SAP liveCache.
                            d.      Execute the report /SAPAPO/OM_ATP_REBUILD_TS.
                            e.      Shut down SAP liveCache.
                              f.      Replace the com-file registration by replacing the registration files SAPAPO.lst and SAPATP.lst (UNIX: libSAPAPO.lst and libSAPATP.lst) with the original versions under Microsoft Windows.
                            g.      Launch SAP liveCache.
Regards
Vinod

Activate abap proxy withou java stack on ECC side

Hi gurus,
Can we activate abap proxy on ECC side if the ECC don't hava java stack? As you know , we need to create two jco RFC provider in Visual Administrator, but without installing java stack, we can't do that. Any ideas? Thanks in advance.

Thanks all.
Solved by using program id of XI system in the RFC of application system.
But we still face the issue in SPROXY. It gave the error "No connection to Integration Builder ".
Then I runned connection test, and found SPROX_CHECK_IFR_ADDRESS and SPROX_CHECK_HTTP_COMMUNICATION
are right, but SPROX_CHECK_IFR_RESPONSE and SPROX_CHECK_IFR_CONNECTION are giving the error "Integration Builder data not understood". Any ideas?
Edited by: xinjiang li on Sep 10, 2010 6:40 PM

How to activate all inactive objects for current user

Hi
How to activate all inactive objects for current user ...
... I have found a (long winded) way to do this:
- Environment / Inactive Objects
- Add to Worklist
- Display Worklist
- Select All
- Activate
this will open a dialog titled "Inactive Objects for <username>"
which has the exact functionality I need ... but I can't figure out how to get to this dialog directly - without so many intermediate steps
the SAP docs repeatedly mention the ability to activate the inactive worklist - but do not mention how
does anybody know the TCode for this dialog?
thanks
ps does the term "mass activation" apply to importing change requests rather than development activation?
Edited by: FireBean500 on Jun 4, 2010 11:07 PM

No other way. But usually it's far more simple as all objects are already in our own worklist.
I wonder why your objects are not already in your worklist, as everytime you create or maintain an object, it is added to your worklist.

I bought an ipod touch 5 from Dubai carrefour. Th seller told me that the ipod that ı bought has a facetime . But when ı want to activate ipod ı couldnt see the facetime app. Please show me how ı could activate facetime.

I bought an ipod touch 5 from Dubai carrefour. Th seller told me that the ipod that ı bought has a facetime . But when ı want to activate ipod ı couldnt see the facetime app. Please show me how ı could activate facetime.

If FaceTime is not hidden by Restrictions (Settings>General<Restrictions) you got duped. iPods officially sold in Dubai and some other countries that prohibit FT do not have FT and there is not way to get FT on those iPods.

How to activate the IS-Retail in ECC 6.0 R/3 system

Dear Guru's...........
Can any one tell me how to activate the IS-Retail in ECC 6.0 R/3 system.
I have IDES system in my home I donu2019t know how to activate retail settings.
Please suggest me how to do that.
Regards
dnr

Dear DNR,
SPRO --> IMG --> Activate SAP ECC Extensions (Or, T. Code: SFW5)
Go to Tab: Industry Business Function
Select Business Function Set: ISR_RETAIL - SAP Retail
A new line will be appeared below.
Current Status will be OFF. Click within Field: Current Status. It will pop-up a list. Select "X - ON".
Important: I've read somewhere - Once Activated, cannot Roll-back.
Best Regards,
Amit
Note: For more, go to - http://help.sap.com
Follow the menu tree: SAP for Industries/SAP for Retail
Click on the link for "SAP industry Specific Components"
Choose the document "Business Function Set Retail"
Also,
Check https://websmp103.sap-ag.de/erp-upgrade --> mySAP ERP 2005: Updated upgrade FAQs, there you will find the list of Industry solutions which are supported by mySAP ERP.
https://websmp103.sap-ag.de/~sapidb/011000358700006168472006/
You must this thread in to [Forum: SAP Enhancement Packages|/community [original link is broken]; OR [Forum: Enterprise Resource Planning (ERP)|Enterprise Resource Planning (SAP ERP); as Nowhere, it is related to SAP SD.

How to activate ABAP Dynrpo in SE80

Similar Messages

Maybe you are looking for