Difference between CommandButton and CommandToolbarButton? (Loading popup )

Hi! I created popup and CommandButton to open it. But when I try to open popup then in Server log I have error:
<PopupRenderer><encodeAll> Loading popup: pt1:uploadWindow during a full-page request is not supported.
But when I tried to use CommandToolbarButton, not CommandButton, then the error was gone.
What is difference between these two buttons?
Best regards, Debuger!

Default value of the attribute <tt>partialSubmit</tt> is <tt>false</tt> for <af:commandButton> and <tt>true</tt> for <af:commandToolbarButton> (see tag documentation). That's why you have succeeded by using <af:commandToolbarButton>.
<af:commandToolbarButton> is intended for use mainly inside <af:toolbar> components. When used in a toolbar the border of the button renders only when you move the mouse cursor over it.
If you set <tt>partialSubmit="true"</tt> you will be able to open the popup using <af:commandButton> too.

Similar Messages

Could any one tell me what is the difference between swfloader and module loader?

Hi All,
                      Could any one tell me what is the difference between SWFLoader and Module Loader in Flex3 in detail?

Hi,
ModuleLoader is a kind of strange API that is really just intended to look like SwfLoader for modules that contain a single visual component, and hides most of the module loading infrastructure, which is all about class factories.
What I mean by "only loaded once" is that if you have several places in the code that call the ModuleManager.getModule("url").load() call, it will only ever get loaded over the wire and interpreted once, subsequent "loads" will just re-dispatch pseudo-load events to the new client. In other words, the class factory is a singleton for a given url. Unloading is a totally different story. As you note, not everything is truly unloadable, because there may be lots of references to stuff in
the module that will keep it alive and un-GC'ed.
I suggest playing with the low-level API so that you understand the backing implementation, and this should help you understand the limits of ModuleLoader.
The main difference between modules and applications is that modules have lower overhead, and they only ever get loaded once, no matter how many times you load them. If you're using the ModuleLoader API, keep in mind that you're losing about half the functionality of the module system. I will assume that you are, because otherwise it would be obvious where to expose methods. You might want to play around with the lower level ModuleManager API just to get a hang of what's going on - ModuleLoader is a pretty thin veneer over the lower API.
                Basically, what you want to do is to have your module implement an interface, say IModuleWhatever.
Also try and refer to this link which was previously discussed in this forum..
http://forums.adobe.com/message/74404
Thanks,
Bhasker

Difference between Reconstruction and regular load from PSA

Gurus,
      What is the Difference between Reconstruction and load from PSA into datatarget.I understand that during Reconstruction we are not loaing data from R3.
      I have a cube and there are 3 requests in that.I deleted all the requests went to PSA and selected one of the requests and selected reconstruct from this.I went to cube and I can see this selected request in PSA in the reconstruction requests of cube.I submitted the reconstruction/Insert button there.
      Is this the procedure to do reconstruction.If yes then how is it different from regular load from PSA.
Thanks

If look function wise both are doing samething. But there is difference in data flow, PSA is used as staging area. If we choose at first place to load only to PSA and analyze our load do manual editing if needed and then load to data target in this case ofcourse reconstruct option is not available or we could parrallely or sequencialy load to data target beside laoding into PSA. So now having already have loaded into data target if some how we needed to delete and reload we can reconstruct the request or run normal load from PSA.

What is the difference between ws_upload and gui_upload

what is the difference between ws_upload and gui_upload
what is the difference between ws_download and gui_down load
pls tell briefly

Hi Kuamr,
UPLOAD and DOWNLOAD, the function modules used until now are not part of the standard set of ABAP commands. They are used to display the file interface on the presentation server. UPLOAD and DOWNLOAD are not compatible with USs and have been replaced by GUI_UPLOAD and GUI_DOWNLOAD.
The new function modules, GUI_UPLOAD and GUI_DOWNLOAD, have an interface that also allows you to write Unicode format to the local hard drive. For a description of these interfaces, refer to the documentation for each function module, available under SAP Easy Access " Development " Function Builder " Goto " Documentation.
Instead of using the function modules, you can use the static methods GUI_UPLOAD and GUI_DOWNLOAD of the global class CL_GUI_FRONTEND_SERVICES.
Hope this resolves your query.
Reward all the helpful answers.
Regards

Difference between Clustering and Load balancing

          What is the difference between Clustering and Load balancing?
          For example, We use Cisco Arrowpoint to do load balancing and it works fine for 3
          Sun solaris boxes/WebLogic 6.1 SP1.
          So what is the value addition to buy clustering license?
          Thanks
          Selvaraj


Hi.
          Among other things, clustering allows you to share app data (such as http session
          data) across cluster members, allowing you to failover should one cluster member
          crash.
          If your app is stateless then this doesn't mean much - load balancing alone would
          probably be ok for you.
          Regards,
          Michael
          Selvaraji wrote:
          > What is the difference between Clustering and Load balancing?
          >
          > For example, We use Cisco Arrowpoint to do load balancing and it works fine for 3
          > Sun solaris boxes/WebLogic 6.1 SP1.
          >
          > So what is the value addition to buy clustering license?
          >
          > Thanks
          >
          > Selvaraj
          Michael Young
          Developer Relations Engineer
          BEA Support

What are the major differences between BODS and Talend ?

Hi Friends,
We had a client meeting 2 days back regarding BODS project, But our client is showing more interest on Talend. We have explained/demo him on BODS. Could any one please tell me, What are the major differences between BODS and Talend ? What are the features of BODS which are not there in TELEND ?
Thanks,
Bheem.

Hi,
If you talk difference than Talend is an open source. SAP DS as huge advantage when it comes to loading data into SAP and it is more flexible with lots of inbuilt features and easy to load data into SAP using DS directly and extracting data from various legacy systems.

Difference between BAPI and BADI

Hi,
Can anyone explain the difference between BAPI and BADI?

Hi Naveen,
BAPI - It is nothing, but a FM which is used to load the data into SAP system. The data may be from the Legacy system.
BADI - They are the enhancement which can be applied to the standard SAP program as per the business requirement. BADI are the newer version of user exits which uses ABAP OOPs concept.
Revert back if you have further query.
Reward points if useful.
Regards,
Atish

Differences between BDC and LSMW

Hello SAP Gurus,
Kindly let me know the various differences between BDC and LSMW.
Also, please tell me the STEPS of the CUT-OVER PLANNING (Shifting of Data from the Legacy System to the SAP System). Here, the "Data" means which data? Please explain in details.
Looking for your early feedback.
Regards,
Kaushik.

Hi,
BDC- It is Batch data communication. Its used for data conversion from legacy system to SAP system. Only technical people can do it. Tcode is SHDB.
LSMW- It is legacy system migration workbench. Its also used for data conversion from legacy system to SAP system. But it is role of functional consultant.
There are 14 steps in LSMW. As soon as you complete the one step, automatically it will go to next step.
In general you can use LSMW. But if you want to transfer more than 40,000 data, then it is not possible in LSMW. That time you can take help of BDC.
Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies.
Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds.
Please refer this link,
[PP Cut over activity|http://www.sap-img.com/production/pp-questions-answers.htm]
Regards,
R.Brahmankar

Key Configuration differences between SAP and ORACLE Financials

Hello,
After spending good 7 years in SAP related projects recently I started working in ORACLE Applications. I used to be an ORACLE programmer years back. To my surprise the same ORACLE Forms are still very much the heart of the ORACLE UI.
Then I thought what will be the key differences between ORACLE and SAP in terms of configuration elements. While I know a bunch of configuraion items in SAP , I am not sure about the same in ORACLE world. I am not even sure some of the configuration items that are available in SAP exists in ORACLE.
Does anyone know both sides of the coin ? The terminology and design ?
SAP has
Client,Company code, Business area, Functional Area, GL, Posting Key, Document Type.
I am trying to get the details of the equivalents of these in ORACLE.
Does anyone know it ?
For e.g , when you post to AP or AR in SAP , GL is updated automatically. In ORACLE you post to a AP Book or AR Book then Run a batch to move them to GL Book.
ORACLE uses SQLLoader to load data . You can write a PL SQL and update the tables directly, which is not the case in SAP. For dataloads and conversions, SAP uses BDC's ( though XI can be used but its slow).For ORACLE its the good old SQL and PlSQL combo.
What are the equivalents of the configuration elements in ORACLE world ?
Also what are the major differences between these two in terms of designing a financial system.
Does any one know ?

Genie,
I agree that a case is made on how well these two ERPs solve the day to day tasks before a company chooses one of these two. But my question is aimed at finance to begin with. You are going to need a general ledger for any company or government regardless of ERP. And how well you can drive the ledger to map your business is the key here.
The way ledger is built is around a business area ,company or country and is very tighly designed in SAP. I would like to know if there is any equivalent of the configuration items in ORACLE. I am more interested in terminology of ORACLE.
For example ,
SAP ====> ORACLE
GL ==> Book In ORACLE
Document Number ===> Invoice Number
Posting Period in SAP ==> Posting period In ORACLE
Most of the terms are finance terms , so they are common ( eg. an account number is an account number in ORACLE and SAP ) between two systems. I am interested in any specific thing that is available in ORACLE but not in SAP and vice verse.
thanks for the link you have provided.
Its very useful.

MAIN DIFFERENCES BETWEEN PARALLEL AND SEQUENTAIL PRCESSING???

HI PALS,
I WANT THE COMPLETE DIFFERENCES BETWEEN PARALLEL AND SEQUENTIAL PROCESSING!
IN THE CONTEXT OF RFC.

Hi
Parallel Processing
To achieve a balanced distribution of the system load, you can use destination additions to execute function modules in parallel tasks in any application server or in a predefined application server group of an SAP system.
Parallel-processing is implemented with a special variant of asynchonous RFC. Itu2019s important that you use only the correct variant for your own parallel processing applications: the CALL FUNCTION STARTING NEW TASK DESTINATION IN GROUP keyword. Using other variants of asynchronous RFC circumvents the built-in safeguards in the correct keyword, and can bring your system to its knees
Details are discussed in the following subsections:
·        Prerequisites for Parallel Processing
·        Function Modules and ABAP Keywords for Parallel Processing
·        Managing Resources in Parallel Processing
Prerequisites for Parallel Processing
Before you implement parallel processing, make sure that your application and your SAP system meet these requirements:
·        Logically-independent units of work:
The data processing task that is to be carried out in parallel must be logically independent of other instances of the task. That is, the task can be carried out without reference to other records from the same data set that are also being processed in parallel, and the task is not dependent upon the results of others of the parallel operations. For example, parallel processing is not suitable for data that must be sequentially processed or in which the processing of one data item is dependent upon the processing of another item of the data.
By definition, there is no guarantee that data will be processed in a particular order in parallel processing or that a particular result will be available at a given point in processing.
·        ABAP requirements:
¡        The function module that you call must be marked as externally callable. This attribute is specified in the Remote function call supported field in the function module definition (transaction SE37).
¡        The called function module may not include a function call to the destination u201CBACK.u201D
¡        The calling program should not change to a new internal session after making an asynchronous RFC call. That is, you should not use SUBMIT or CALL TRANSACTION in such a report after using CALL FUNCTION STARTING NEW TASK.
¡        You cannot use the CALL FUNCTION STARTING NEW TASK DESTINATION IN GROUP keyword to start external programs.
·        System resources:
In order to process tasks from parallel jobs, a server in your SAP system must have at least 3 dialog work processes. It must also meet the workload criteria of the parallel processing system: Dispatcher queue less than 10% full, at least one dialog work process free for processing tasks from the parallel job.
Function Modules and ABAP Keywords for Parallel Processing
You can implement parallel processing in your applications by using the following function modules and ABAP keywords:
·        SPBT_INITIALIZE: Optional function module.
Use to determine the availability of resources for parallel processing.
You can do the following:
¡        check that the parallel processing group that you have specified is correct.
¡        find out how many work processes are available so that you can more efficiently size the packets of data that are to be processed in your data.
·        CALL FUNCTION Remotefunction STARTING NEW TASK Taskname DESTINATION IN GROUP:
With this ABAP statement, you are telling the SAP system to process function module calls in parallel. Typically, youu2019ll place this keyword in a loop in which you divide up the data that is to be processed into work packets. You can pass the data that is to be processed in the form of an internal table (EXPORT, TABLE arguments). The keyword implements parallel processing by dispatching asynchronous RFC calls to the servers that are available in the RFC server group specified for the processing.
Note that your RFC calls with CALL FUNCTION are processed in work processes of type DIALOG. The DIALOG limit on processing of one dialog step (by default 300 seconds, system profile parameter rdisp/max_wprun_time) applies to these RFC calls. Keep this limit in mind when you divide up data for parallel processing calls.
·        SPBT_GET_PP_DESTINATION: Optional function module.
Call immediately after the CALL FUNCTION keyword to get the name of the server on which the parallel processing task will be run.
·        SPBT_DO_NOT_USE_SERVER: Optional function module.
Excludes a particular server from further use for processing parallel processing tasks. Use in conjunction with SPBT_GET_PP_DESTINATION if you determine that a particular server is not available for parallel processing (for example, COMMUNICATION FAILURE exception if a server becomes unavailable).
·        WAIT: ABAP keyword
WAIT UNTIL
Required if you wish to wait for all of the asynchronous parallel tasks created with CALL FUNCTION to return. This is normally a requirement for orderly background processing. May be used only if the CALL FUNCTION includes the PERFORMING ON RETURN addition.
·        RECEIVE: ABAP keyword
RECEIVE RESULTS FROM FUNCTION Remotefunction
Required if you wish to receive the results of the processing of an asynchronous RFC. RECEIVE retrieves IMPORT and TABLE parameters as well as messages and return codes.
Managing Resources in Parallel Processing
You use the following destination additions to perform parallel execution of function modules (asynchronous calls) in the SAP system:
In a predefined group of application servers:
CALL FUNCTION Remotefunction STARTING NEW TASK Taskname
DESTINATION IN GROUP Groupname
In all currently available and active application servers:
CALL FUNCTION Remotefunction STARTING NEW TASK Taskname
DESTINATION IN GROUP DEFAULT
Sequential Processing
In the following cases, the system chooses sequential (non-parallel) processing:
●      In table RSADMIN, entry QUERY_MAX_WP_DIAG has value (column value) 1.
●      The entire query consists of one sub-access only.
●      The query is running in a batch process.
●      The query was started from the query monitor (transaction RSRT) using various debug options (for example, SQL query display, execution plan display). See, Dividing a MultiProvider Query into Sub-Queries.
●      The query requests non-cumulative key figures.
●      Insufficient dialog processes are available when the query is executed. These are required for parallel processing.
●      The query is configured for non-parallel processing.
●      You want to save the result of the query in a file or a table.
In Release SAP NetWeaver 7.0, the system can efficiently manage the large intermediate results produced by parallel processing. In previous releases, the system terminated when it reached a particular intermediate result size and proceeded to read data sequentially. This is no longer the case. Therefore, the RSADMIN parameter that was used in previous releases for reading a MultiProvider sequentially is no longer used.
Reward If Helpfull,
Naresh

What is the difference between "Replace" and "Replace by Security"

Hi all,
I am implementing FDM to Load data to HFM, I set them up with a proper security on the shared service and FDM. When I load data to HFM from FDM, there are 4 options to load data. (Replace, Merge, Accumulate, Replace by Security)
A document states that
Replace: Clears all account values from the target application, and replaces that the data in the application with the data in the load file.
Replace by Security: Loads data to the target application only for members to which you have access.
However, even if I used “Replace”, it worked with security which I set.
Does anyone know what the difference between “Replace” and “Replace by Security”?
Is there any way that FDM works without security?
Thanks in advance
taku

The fact both methods are producing the same results will either be coincidence or perhaps because you are mis-interpreting the difference between the 2. When you run a Replace HFM will clear out all data based on the combination of Scenario, Year, Period, Entity and Value dimensions it does not care if you have set up security classes which may restrict access to any of the other dimensions i.e. Account, Custom1 thru 4. When you use Replace By Security HFM will still clear on the original criteria but it will respect security class restrictions set up on the other dimensions e.g. if you are assigned to a security class which is restricted to accessing only a certain subset of accounts, HFM will not clear data fro the accounts you don't have access to when you use Replace By Security

Differences between awt and swing

Ive written the following code, however Ive implemented the gui in awt rather then swing. Ive been told it hs too be in swing. What is the difference between swing and awt what will I need to change in my program so that its done using swing rather then the awt? Heres the code:
// pp.java
// Grant Brown
// 22/02/02
import java.awt.*;
import java.awt.event.*;
import java.io.*;
import java.util.*;
import javax.swing.*;
// =========================================================
// Class: pp
// This class drives the customer manager. It contains the
// main method which gets called as soon as this application
// begins to run.
// =========================================================
class pp extends Frame implements ActionListener
// Container of customer objects
private Vector customers = new Vector (100);
// List of names component. (Must specify java.awt in
// front of List to distinguish the List class in the
// java.awt package from the List class in the java.util
// package.)
private java.awt.List names = new java.awt.List ();
// Delete and update button components.
private Button delete;
private Button update;
// Default constructor.
public pp ()
// Assign "Paper Round Manager" to title bar of frame window.
super ("Paper Round Manager");
// Add a listener that responds to window closing
// events. When this event occurs (by clicking on the
// close box in the title bar), save customers and exit.
addWindowListener (new WindowAdapter ()
public void windowClosing
(WindowEvent e)
saveCustomers ();
System.exit (0);
// Place an empty label in the north part of the frame
// window. This is done to correct an AWT positioning
// problem.
Label l = new Label ();
add ("North", l);
// Place the names component in the center part of the
// frame window.
add ("Center", names);
// Create a panel object to hold four buttons.
Panel p = new Panel ();
Button b;
// Add an Insert button to the Panel object and register
// the current pp object as a listener for button events.
p.add (b = new Button ("Insert"));
b.addActionListener (this);
// Add a Delete button to the Panel object and register
// the current pp object as a listener for button events.
p.add (delete = new Button ("Delete"));
delete.addActionListener (this);
// The Delete button should be disabled until there is at
// least one customer to delete.
delete.setEnabled (false);
// Add an Update button to the Panel object and register
// the current pp object as a listener for button events.
p.add (update = new Button ("Update"));
update.addActionListener (this);
// The Update button should be disabled until there is at
// least one customer to update.
update.setEnabled (false);
// Add a Finish button to the Panel object and register
// the current customer object as a listener for button events.
p.add (b = new Button ("Finish"));
b.addActionListener (this);
// Add the panel object to the frame window container.
add ("South", p);
// Set the background of the frame window container to
// lightGray
setBackground (Color.lightGray);
// Set the size of the frame window container to 400
// pixels horizontally by 200 pixels vertically.
setSize (400, 200);
// Allow the user to resize the frame window.
setResizable (true);
// Load all contacts.
loadCustomers ();
// Make sure that the frame window is visible.
setVisible (true);
public void actionPerformed (ActionEvent e)
if (e.getActionCommand ().equals ("Delete"))
delete ();
else
if (e.getActionCommand ().equals ("Finish"))
saveCustomers ();
System.exit (0);
else
if (e.getActionCommand ().equals ("Insert"))
insert ();
else
update ();
public Insets getInsets ()
// Return an Insets object that describes the number of
// pixels to reserve as a border around the edges of the
// frame window.
return new Insets (10, 10, 10, 10);
public static void main (String [] args)
// Create a new pp object and let it do its thing.
new pp ();
private void delete ()
// Obtain index of selected contact item from the names
// component.
int index = names.getSelectedIndex ();
// If no item was selected, index is -1. We cannot update
// a contact if no contact item in the names component was
// selected - because we would have nothing to work with.
if (index != -1)
// Remove the contact item from the names component.
names.remove (index);
// Remove the Customer object from the contacts Vector
// object.
customers.remove (index);
// If there are no more customers ...
if (customers.size () == 0)
delete.setEnabled (false);
update.setEnabled (false);
else
// Make sure that the first contact item in the names
// list is highlighted.
names.select (0);
private void insert ()
// Create an Insert data entry form to enter information
// for a new customer.
DataEntryForm def = new DataEntryForm (this, "Insert");
// If the bOk Boolean flag is set, this indicates the user
// exited the form by pressing the Ok button.
if (def.bOk)
// Create a Contact object and assign information from
// the form to its fields.
Customer temp = new Customer ();
temp.name = new String (def.name.getText ());
temp.publication = new String (def.publication.getText ());
temp.round = new String (def.round.getText ());
temp.address = new String (def.address.getText ());
temp.phone = new String (def.phone.getText ());
// Add a new customer item to the names component.
names.add (temp.name + ", " + temp.publication);
// Add the Customer object to the contacts Vector
// object.
customers.add (temp);
// Make sure that the Delete and Update buttons are
// enabled.
delete.setEnabled (true);
update.setEnabled (true);
// Destroy the dialouge box.
def.dispose ();
// Make sure that the first customer item in the names list
// is highlighted.
names.select (0);
// ===========================================================
// Load all contacts from contacts.dat into the contacts
// Vector object. Also, make sure that the last name/first
// name from each contact is combined into a String object and
// inserted into the names component - as a contact item.
// ===========================================================
private void loadCustomers ()
FileInputStream fis = null;
try
fis = new FileInputStream ("Customers.dat");
DataInputStream dis = new DataInputStream (fis);
int nCustomers = dis.readInt ();
for (int i = 0; i < nCustomers; i++)
Customer temp = new Customer ();
temp.name = dis.readUTF ();
temp.publication = dis.readUTF ();
temp.round = dis.readUTF ();
temp.address = dis.readUTF ();
temp.phone = dis.readUTF ();
names.add (temp.name + ", " + temp.publication);
customers.add (temp);
if (nCustomers > 0)
delete.setEnabled (true);
update.setEnabled (true);
catch (IOException e)
finally
if (fis != null)
try
fis.close ();
catch (IOException e) {}
// Make sure that the first contact item in the names list
// is highlighted.
names.select (0);
// ========================================================
// Save all Customer objects from the customer Vector object
// to customer.dat. The number of customerss are saved as an
// int to make it easy for loadCustomers () to do its job.
// ========================================================
private void saveCustomers ()
FileOutputStream fos = null;
try
fos = new FileOutputStream ("customers.dat");
DataOutputStream dos = new DataOutputStream (fos);
dos.writeInt (customers.size ());
for (int i = 0; i < customers.size (); i++)
Customer temp = (Customer) customers.elementAt (i);
dos.writeUTF (temp.name);
dos.writeUTF (temp.publication);
dos.writeUTF (temp.round);
dos.writeUTF (temp.address);
dos.writeUTF (temp.phone);
catch (IOException e)
MsgBox mb = new MsgBox (this, "PP Error",
e.toString ());
mb.dispose ();
finally
if (fos != null)
try
fos.close ();
catch (IOException e) {}
private void update ()
// Obtain index of selected customer item from the names
// component.
int index = names.getSelectedIndex ();
// If no item was selected, index is -1. We cannot update
// a customer if no customer item in the names component was
// selected - because we would have nothing to work with.
if (index != -1)
// Obtain a reference to the customer object (from the
// customers Vector object) that is associated with the
// index.
Customer temp = (Customer) customers.elementAt (index);
// Create and display an update entry form.
DataEntryForm def = new DataEntryForm (this, "Update",
temp.name,
temp.publication,
temp.round,
temp.address,
temp.phone);
// If the user pressed Ok...
if (def.bOk)
// Update the customer information in the customers
// Vector object.
temp.name = new String (def.name.getText ());
temp.publication = new String (def.publication.getText ());
temp.round = new String (def.round.getText ());
temp.address = new String (def.address.getText ());
temp.phone = new String (def.phone.getText ());
// Make sure the screen reflects the update.
names.replaceItem (temp.name + ", " + temp.publication,
index);
// Destroy the dialouge box.
def.dispose ();
// Make sure that the first customer item in the names
// list is highlighted.
names.select (0);

Ive doen pretty much what you said burt now my program isnt working at all. The window comes up but instead of doing something when you click the button it just throws shit loads of exceptions. Heres my abridged code
// pp.java
// Grant Brown
// 22/02/02
import java.awt.*;
import java.awt.event.*;
import java.io.*;
import java.util.*;
import javax.swing.*;
// =========================================================
// Class:PP
// This class drives the Paper Round manager. It contains the
// main method which gets called as soon as this application
// begins to run.
// =========================================================
class pp extends JFrame implements ActionListener
// Container of customer objects (one object per customer)
private Vector customers = new Vector (100);
// List of names component. (Must specify java.awt in
// front of List to distinguish the List class in the
// java.awt package from the List class in the java.util
// package.)
private java.awt.List names = new java.awt.List ();
// Delete and update button components.
private JButton delete;
private JButton update;
// Default constructor.
public pp ()
// Assign Contact Manager to title bar of frame window.
super ("Paper Round Manager");
// Add a listener that responds to window closing
// events. When this event occurs (by clicking on the
// close box in the title bar), save contacts and exit.
addWindowListener (new WindowAdapter ()
public void windowClosing
(WindowEvent e)
saveCustomers ();
System.exit (0);
// Place an empty label in the north part of the frame
// window. This is done to correct an AWT positioning
// problem. (One thing that you'll come to realize as
// you work with the AWT is that there are lots of bugs.)
JLabel l = new JLabel ();
getContentPane().add ("North", l);
// Place the names component in the center part of the
// frame window.
getContentPane().add ("Center", names);
// Create a panel object to hold four buttons.
JPanel p = new JPanel ();
JButton b;
// Add an Insert button to the Panel object and register
// the current cm object as a listener for button events.
p.add (b = new JButton ("Insert"));
b.addActionListener (this);
// Add a Delete button to the Panel object and register
// the current cm object as a listener for button events.
p.add (delete = new JButton ("Delete"));
delete.addActionListener (this);
// The Delete button should be disabled until there is at
// least one contact to delete.
delete.setEnabled (false);
// Add an Update button to the Panel object and register
// the current cm object as a listener for button events.
p.add (update = new JButton ("Update"));
update.addActionListener (this);
// The Update button should be disabled until there is at
// least one contact to update.
update.setEnabled (false);
// Add a Finish button to the Panel object and register
// the current cm object as a listener for button events.
p.add (b = new JButton ("Finish"));
b.addActionListener (this);
// Add the panel object to the frame window container.
getContentPane().add ("South", p);
// Set the background of the frame window container to
// lightGray (to give a pleasing effect).
setBackground (Color.lightGray);
// Set the size of the frame window container to 400
// pixels horizontally by 200 pixels vertically.
setBounds (50, 100, 400, 200);
// Do not allow the user to resize the frame window.
loadCustomers ();
// Load all contacts.
setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
// Make sure that the frame window is visible.
setVisible (true);
public void actionPerformed (ActionEvent e)
if (e.getActionCommand ().equals ("Delete"))
delete ();
else
if (e.getActionCommand ().equals ("Finish"))
saveCustomers ();
System.exit (0);
else
if (e.getActionCommand ().equals ("Insert"))
insert ();
else
update ();
public Insets getInsets ()
// Return an Insets object that describes the number of
// pixels to reserve as a border around the edges of the
// frame window.
return new Insets (10, 10, 10, 10);
public static void main (String [] args)
// Create a new cm object and let it do its thing.
new pp ();
private void delete ()
// Obtain index of selected customer item from the names
// component.
int index = names.getSelectedIndex ();
// If no item was selected, index is -1. We cannot update
// a contact if no contact item in the names component was
// selected - because we would have nothing to work with.
if (index != -1)
// Remove the customer item from the names component.
names.remove (index);
// Remove the Customer object from the contacts Vector
// object.
customers.remove (index);
// If there are no more customers ...
if (customers.size () == 0)
delete.setEnabled (false);
update.setEnabled (false);
else
// Make sure that the first contact item in the names
// list is highlighted.
names.select (0);
private void insert ()
// Create an Insert data entry form to enter information
// for a new contact.
DataEntryForm def = new DataEntryForm (this, "Insert");
// If the bOk Boolean flag is set, this indicates the user
// exited the form by pressing the Ok button.
if (def.bOk)
// Create a Customer object and assign information from
// the form to its fields.
Customer temp = new Customer ();
temp.name = new String (def.name.getText ());
temp.publication = new String (def.publication.getText ());
temp.address = new String (def.address.getText ());
temp.round = new String (def.round.getText ());
temp.phone = new String
(def.phone.getText ());
// Add a new customer item to the names component.
names.add (temp.publication + ", " + temp.address);
// Add the Customer object to the contacts Vector
// object.
customers.add (temp);
// Make sure that the Delete and Update buttons are
// enabled.
delete.setEnabled (true);
update.setEnabled (true);
// Destroy the dialog box.
def.dispose ();
// Make sure that the first customer item in the names list
// is highlighted.
names.select (0);
// ===========================================================
// Load all customers from customers.dat into the customers
// Vector object. Also, make sure that the last name/first
// name from each contact is combined into a String object and
// inserted into the names component - as a contact item.
// ===========================================================
private void loadCustomers ()
FileInputStream fis = null;
try
fis = new FileInputStream ("customers.dat");
DataInputStream dis = new DataInputStream (fis);
int nCustomers = dis.readInt ();
for (int i = 0; i < nCustomers; i++)
Customer temp = new Customer ();
temp.name = dis.readUTF ();
temp.publication = dis.readUTF ();
temp.address = dis.readUTF ();
temp.round = dis.readUTF ();
temp.phone = dis.readUTF ();
names.add (temp.publication + ", " + temp.address);
customers.add (temp);
if (nCustomers > 0)
delete.setEnabled (true);
update.setEnabled (true);
catch (IOException e)
finally
if (fis != null)
try
fis.close ();
catch (IOException e) {}
// Make sure that the first customer item in the names list
// is highlighted.
names.select (0);
// ========================================================
// Save all customer objects from the contacts Vector object
// to customers.dat. The number of contacts are saved as an
// int to make it easy for loadCustomers () to do its job.
// ========================================================
private void saveCustomers ()
FileOutputStream fos = null;
try
fos = new FileOutputStream ("customers.dat");
DataOutputStream dos = new DataOutputStream (fos);
dos.writeInt (customers.size ());
for (int i = 0; i < customers.size (); i++)
Customer temp = (Customer) customers.elementAt (i);
dos.writeUTF (temp.name);
dos.writeUTF (temp.publication);
dos.writeUTF (temp.address);
dos.writeUTF (temp.round);
dos.writeUTF (temp.phone);
catch (IOException e)
MsgBox mb = new MsgBox (this, "PP Error",
e.toString ());
mb.dispose ();
finally
if (fos != null)
try
fos.close ();
catch (IOException e) {}
private void update ()
// Obtain index of selected customer item from the names
// component.
int index = names.getSelectedIndex ();
// If no item was selected, index is -1. We cannot update
// a customer if no customer item in the names component was
// selected - because we would have nothing to work with.
if (index != -1)
// Obtain a reference to the Customer object (from the
// customer Vector object) that is associated with the
// index.
Customer temp = (Customer) customers.elementAt (index);
// Create and display an update entry form.
DataEntryForm def = new DataEntryForm (this, "Update",
temp.name,
temp.publication,
temp.address,
temp.round,
temp.phone);
// If the user pressed Ok...
if (def.bOk)
// Update the customer information in the customers
// Vector object.
temp.name = new String (def.name.getText ());
temp.publication = new String (def.publication.getText ());
temp.address = new String (def.address.getText ());
temp.round = new String (def.round.getText ());
temp.phone = new String (def.phone.getText ());
// Make sure the screen reflects the update.
names.replaceItem (temp.publication + ", " + temp.address,
index);
// Destroy the dialog box.
def.dispose ();
// Make sure that the first customer item in the names
// list is highlighted.
names.select (0);
// ========================================================
// Class: Customer
// This class describes the contents of a business customer.
// ========================================================
class Customer
public String name;
public String publication;
public String address;
public String round;
public String phone;
// ==========================================================
// Class: DataEntryForm
// This class provides a data entry form for entering customer
// information.
// ==========================================================
class DataEntryForm extends JDialog implements ActionListener
// bOk is a boolean flag. When true, it indicates that
// the Ok button was pressed to terminate the dialog box
// (as opposed to the Cancel button).
public boolean bOk;
// The following components hold the text that the user
// entered into the visible text fields.
public JTextField name;
public JTextField publication;
public JTextField address;
public JTextField round;
public JTextField phone;
public void actionPerformed (ActionEvent e)
// If the user pressed the Ok button, indicate this
// by assigning true to bOk.
if (e.getActionCommand ().equals ("Ok"))
bOk = true;
// Destroy the dialog box and return to the point
// just after the creation of the DataEntryForm object.
dispose ();
public DataEntryForm (JFrame parent, String title)
// Call the other constructor. The current constructor
// is used for insert operations. The other constructor
// is used for update operations.
this (parent, title, "", "", "", "", "");
public DataEntryForm (JFrame parent, String title,
String name, String publication,
String address, String round,
String phone)
// Initialize the superclass layer.
super (parent, title, true);
// Choose a grid bag layout so that components can be more
// accurately positioned. (It looks nicer.)
setLayout (new GridBagLayout ());
// Add appropriate first name, last name, phone, fax, and
// email components to the current DataEntryForm container.
// (Remember, DataEntryForm is a subclass of Dialog.
// Dialog is a container. Therefore, DataEntryForm
// inherits the ability to be a container.)
addComponent (this, new JLabel ("Name: "), 0, 0, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.WEST);
this.name = new JTextField (15);
addComponent (this, this.name, 1, 0, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.CENTER);
if (title.equals ("Update"))
this.name.setText (name);
addComponent (this, new JLabel ("Publications: "), 0, 1, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.WEST);
this.publication = new JTextField (15);
addComponent (this, this.publication, 1, 1, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.CENTER);
if (title.equals ("Update"))
this.publication.setText (publication);
addComponent (this, new JLabel ("Address "), 0, 2, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.WEST);
this.address = new JTextField (15);
addComponent (this, this.address, 1, 2, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.CENTER);
if (title.equals ("Update"))
this.address.setText (address);
addComponent (this, new JLabel ("Round No "), 0, 3, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.WEST);
this.round = new JTextField (15);
addComponent (this, this.round, 1, 3, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.CENTER);
if (title.equals ("Update"))
this.round.setText (round);
addComponent (this, new JLabel ("Phone Number "), 0, 4, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.WEST);
this.phone = new JTextField (15);
addComponent (this, this.phone, 1, 4, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.CENTER);
if (title.equals ("Update"))
this.phone.setText (phone);
addComponent (this, new JLabel (""), 0, 5, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.CENTER);
addComponent (this, new JLabel (""), 1, 5, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.CENTER);
JButton b;
// Add an Ok button to this container.
addComponent (this, b = new JButton ("Ok"), 0, 6, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.CENTER);
b.addActionListener (this);
// Add a Cancel button to this container.
addComponent (this, b = new JButton ("Cancel"), 1, 6, 1, 1,
GridBagConstraints.NONE,
GridBagConstraints.CENTER);
b.addActionListener (this);
// Set the size of the dialog window to 250 pixels
// horizontally by 200 pixels vertically.
setSize (250, 200);
// Do not allow users to resize the dialog window.
setResizable (false);
// Make sure that the dialog window is visible.
setVisible (true);
private void addComponent (Container con, Component com,
int gridx, int gridy,
int gridw, int gridh, int fill,
int anchor)
// Get the current layout manager. It is assumed to
// be a GridBagLayout object.
LayoutManager lm = con.getLayout ();
// Create a GridBagConstraints object to make it
// possible to customize component positioning.
GridBagConstraints gbc = new GridBagConstraints ();
// Assign the x and y grid positions.
gbc.gridx = gridx;
gbc.gridy = gridy;
// Assign the number of grid blocks horizontally and
// vertically that are occupied by the component.
gbc.gridwidth = gridw;
gbc.gridheight = gridh;
// Specify the component's resize policy (fill) and
// the direction in which the component is positioned
// when its size is smaller than available space (anchor).
gbc.fill = fill;
gbc.anchor = anchor;
// Set the new constraints that the grid bag layout
// manager will use.
((GridBagLayout) lm).setConstraints (com, gbc);
// Add the component to the container.
con.add (com);
// ===========================================================
// Class: MsgBox
// This class displays a message box to the user. The message
// is usually an error message. The user must press the Ok
// button to terminate the message box.
// ===========================================================
class MsgBox extends JDialog implements ActionListener
public void actionPerformed (ActionEvent e)
// Terminate the dialog box in response to the user
// pressing the Ok button.
dispose ();
public MsgBox (JFrame parent, String title, String msg)
// Initialize the superclass layer.
super (parent, title, true);
// Store the msg argument in a Label object and add
// this object to the center part of the dialog window.
JLabel l = new JLabel (msg);
add ("Center", l);
// Create a Button object and add it to the south part
// of the dialog window.
JButton b = new JButton ("Ok");
add ("South", b);
// Make the current object a listener to events that
// occur as a result of the user pressing the Ok
// button.
b.addActionListener (this);
// Make sure that the Ok button has the focus.
b.requestFocus ();
// Do not allow users to resize the dialog window.
setResizable (false);
// Allow the layout manager to choose an appropriate
// size for the dialog window.
pack ();
// Make sure that the dialog window is visible.
setVisible (true);
}

What is the difference between CDC and SCD type2

I am a new user of BODS and Have used SCD type 2 (delta's) capturing and loading the difference of data to targets.
Trying to understand the difference between CDC and scd type 2.
CDC says capture changed data, so i assume both are same, is that true?
thanks for the helpful info.

CDC is Change Data Capture -
The CDC methods will enable you to extract and load only the new or changed records form the source, rather than loading the entire records from the source. Also called as delta or incremental load.
SCD Type 2 (Slowly Changing Dimension Type 2)
This lets you store/preserve the history of changed records of selected dimensions as per your choice. The transaction table / source table will mostly have only the current value and is used in certain cases where in the history of a certain dimension is required for analysis purpose.
Regards,
Suneer

Difference between "Export" and "Export form Fact Table" package

Hi experts!
Could you tell me what is the difference between "Export" and "Export form Fact Table" package?
Tkanks
Gabriel

Hi,
Basic difference between Export and Export from Fact Table is
In standard package "Export" : We can perform this function when we are online and we have adequate amount of data to be exported. We can run this package eg: weekly or monthly. Here we use u201CExport Packageu201D to pull the data
And in the administrative package "Export from Fact Table" Mostly it is used to do the backend data loading basically bulk data , also any formula logic has to be implemented on the data in that case we use the administrative package.
Hope this helps.

Can anybody give me the difference between Catt and Ecatt

Hi gurus,
Can any body give me the difference between catt and ecatt.

Hi,
I think this is new technology in sap.
I know little bit of this can u go through this.
eCATT (extended Computer Aided Test Tool)
What is eCATT?
eCATT is an SAP Testing Tool used to automate & test business scenarios in R/3. Each test generates a detailed log that documents the test process and results. If the testing is smooth without any errors, this means that the business scenarios mapped in R/3 are correct. If the test results in error then the problem can be analyzed using the error log that is generated.
eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java.
Features of eCATT:
Following functions can be performed using eCATT:
Test transactions, reports and scenarios.
Call BAPIs and function modules.
Test remote systems.
Check authorizations (user profiles).
Test updates (database, applications, GUI).
Set up customizing tables.
Test the effect of changes to customizing settings.
Perform load testing.
Check system messages.
Integrated with Test Workbench, so allows proper management of scripts using SCAT transaction.
Supports CATT migration to eCATT.
All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.
eCATT Objects can easily download & upload in XML with XSD format.
There can be several versions of Test Scripts, which allows different implementations with different releases.
The separation of Test Scripts, Test Data & System Data allows for a considerable degree of reuse.
Why eCATT?
CATT is no longer supported by SAP for the creation of new developments. Hence all the test scripts developed in CATT are now need to migrate/Update to eCATT. Comparative to manual testing, the following are advantages of using eCATT:
Due to automation, testing time is reduced to a large extent.
Due to automation, less manpower is required for testing. This helps financially.
Due to automation, manual errors are reduced to large extent. Hence results in error free testing. This helps, as no further problems will occur while the usage of R/3 system by end users and hence increases the efficiency.
Proved to be extremely useful in implementation projects.
In regression testing, automated test scripts are an ideal method of quickly detecting errors. Automatic test logs make it easy to reproduce test results, enabling fast analysis and planning of further activities, leading to cost savings for the customer.
Differences between CATT and eCATT?
Till date, CATT could only be used with the R/3 system. eCATT (which is available with SAP Web Application Server 6.20) covers the automatic testing in SAPGUI for Windows and SAP GUI for Java. For other GUIs and Applications, eCATT provides an interface for external tools. This allows companies to perform automated tests from an SAP system in a complete IT solution landscape across system boundaries. These new options enable complete automation of solution landscapes under standard Windows and Web-based user interfaces- resulting in low-cost operation of an IT Solution.
eCATT (extended Computer Aided Test Tool)
eCATT requisites
Web Application Server (WAS) 6.20 or more.
SAPGUI 6.20 or more.
R/3 4.6C or more. (Target system must have sufficient support package level (Details available in SAP Note 519858) or SAP R/3 Enterprise Release 4.7).
Before creating Test Scripts using eCATT, some system settings need to be done:
Maintain table T000.
1.      Go to transaction SM31
2.      Enter T000 and chose MAINTAIN.
3.      In the Change View Clients: Overview screen, select the relevant client and choose Details
4.      In the CATT and eCATT Restrictions field, select CATT and eCATT allowed.
5.      Click on SAVE.
Enabling scripting at the Front-end
1.      On any SAP GUI screen, choose Customizing of Local Layout.
2.      Choose Options
3.      Choose Scripting Tab
4.      Select Enable Scripting
5.      Click Apply and then OK.
Enabling Scripting on the Application Server
1.      Go to transaction RZ11.
2.      On the Maintain Profile Parameters screen, enter sapgui/user_scripting.
3.       Choose Display.
4.      If the Current Value is not set to TRUE, then click on Change Value:
5.      Enter TRUE in the New Value.
6.      Click on SAVE.
eCATT is an SAP Testing Tool used to automate & test business scenarios in R/3. Each test generates a detailed log that documents the test process and results. If the testing is smooth without any errors, this means that the business scenarios mapped in R/3 are correct. If the test results in error then the problem can be analyzed using the error log that is generated.
eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java.
Features of eCATT:
Following functions can be performed using eCATT:
Test transactions, reports and scenarios.
Call BAPIs and function modules.
Test remote systems.
Check authorizations (user profiles).
Test updates (database, applications, GUI).
Set up customizing tables.
Test the effect of changes to customizing settings.
Perform load testing.
Check system messages.
Integrated with Test Workbench, so allows proper management of scripts using SCAT transaction.
Supports CATT migration to eCATT.
All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.
eCATT Objects can easily download & upload in XML with XSD format.
There can be several versions of Test Scripts, which allows different implementations with different releases.
The separation of Test Scripts, Test Data & System Data allows for a considerable degree of reuse.
Why eCATT?
CATT is no longer supported by SAP for the creation of new developments. Hence all the test scripts developed in CATT are now need to migrate/Update to eCATT. Comparative to manual testing, the following are advantages of using eCATT:
Due to automation, testing time is reduced to a large extent.
Due to automation, less manpower is required for testing. This helps financially.
Due to automation, manual errors are reduced to large extent. Hence results in error free testing. This helps, as no further problems will occur while the usage of R/3 system by end users and hence increases the efficiency.
Proved to be extremely useful in implementation projects.
In regression testing, automated test scripts are an ideal method of quickly detecting errors. Automatic test logs make it easy to reproduce test results, enabling fast analysis and planning of further activities, leading to cost savings for the customer.
Reward points if it is helpful.
Rgds,
P.Nag

Difference between CommandButton and CommandToolbarButton? (Loading popup )

Similar Messages

Maybe you are looking for