Differents between Bespoke and Customization code

Hi,
Can any body explain me with example for the differents between Bespoke and Customization code.
Laxmn

hi
both of them are much of the same....
Bespoke: is exactly according to the Customer Specifications, for eg:- say defining Enterprise Structure of a business this is done exactly to the Client Required Specifications..
Customization Code: is to make changes to the standard form of system. say as in previous eg: for getting customer specific customization in pulling some data, say sales order details, there are standard Bapis' provided by SAP but to meet up the clients requirements u might have to go on and write a RFM if available BAPI is not suitable for ur requirement.
Reward Points if Useful
Thanx & Regards
Naren...

Similar Messages

Difference between configuration and customization

what is difference between configuration and customization?

Dear Chandu,
Configuration means allready the data given by the Standard SAP but we need to arange that data in the proper as per our requirement.
Example:Pricing procedure dtermination
Customisation means the data not avail in the standard SAP so we need to develop with the help of ABAPer.
Example: Zreports,
I hope it will clear for you,
Regards,
Murali.

What's the difference between Dreamweaver and Edge Code?

Trying to decide what to use to code a website and there's so many different programs that accomplish the same task! What do you suggest to use?
I've always used dreamweaver but all the edge programs sound useful.
Thoughts?

Edge code is simply a code editor. It does not do file uploads, provide a visual representation of your site, or some of the other functions of DW. If all you need is a code editor to make some quick changes, I would highly recommend it. But if you need the visual aspect and some other DW functionality then I would say stick to DW.

Difference between Cofiguration and Customzing

Hi,
What's the difference between Cofiguration and Customzing.
BR
Govind

Hi,
The difference between customizing and configuration is;
CONFIGURATION: - We will configure the system to meet the needs of your business by using the existing data.
CUSTOMIZING: - We will customize or adapt the system to your business requirements, which is the process of mapping SAP to your business process.
Configuration Vs Customization: -
When considering enterprise software of any type, it is important to understand the difference between configuration and customization. The crux of the difference is complexity. Configuration uses the inherent flexibility of the enterprise software to add fields, change field names, modify drop-down lists, or add buttons. Configurations are made using powerful built-in tool sets. Customization involves code changes to create functionality that is not available through configuration. Customization can be costly and can complicate future upgrades to the software because the code changes may not easily migrate to the new version. Wherever possible, governments should avoid customization by using configuration to meet their goals. Governments also should understand their vendor's particular terminology with regard to this issue since words like "modifications" or "extensions" often mean different things to different vendors.

Difference bet configuration and customization

hi,
I want a brief explanation about configuration and customization.
can any one help me out
thanx and regards
pavan

Dear Pavan,
The difference between cutomizing and configuration is:
- CONFIGURATION: we will configure the system to meet the needs of your business by using the existing data.
- CUSTOMIZING: we will customise or adapt the system to your business requirements, which is the process of mapping SAP to your business process.
- CLIENT: A client is a unique one in organizational structure, can have one or more company codes. Each company code is its own legal entity in finance.
Configuration vs. Customization
When considering enterprise software of any type, it is important to understand the difference between configuration and customization.The crux of the difference is complexity. Configuration uses the inherent flexibility of the enterprise software to add fields, change field names,modify drop-down lists, or add buttons. Configurations are made using powerful built-in tool sets. Customization involves code changes to create functionality that is not available through configuration. Customization can be costly and can complicate future upgrades to the software because the code changes may not easily migrate to the new version.Wherever possible, governments should avoid customization by using configuration to meet their goals.Governments also should understand their vendor's particular terminology with regard to this issue since words like "modifications" or "extensions" often mean different things to different vendors
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh

Difference between customizing and configuration?

Is there any Difference between customizing and configuration?

Hi Rajesh,
What is Client? What is the difference between Customization and Configuration?
The difference between cutomizing and configuration is:
- CONFIGURATION: we will configure the system to meet the needs of your business by using the existing data.
- CUSTOMIZING: we will customise or adapt the system to your business requirements, which is the process of mapping SAP to your business process.
- CLIENT: A client is a unique one in organizational structure, can have one or more company codes. Each company code is its own legal entity in finance.
Configuration vs. Customization
When considering enterprise software of any type, it is important to understand the difference between configuration and customization.The crux of the difference is complexity. Configuration uses the inherent flexibility of the enterprise software to add fields, change field names,modify drop-down lists, or add buttons. Configurations are made using powerful built-in tool sets. Customization involves code changes to create functionality that is not available through configuration. Customization can be costly and can complicate future upgrades to the software because the code changes may not easily migrate to the new version.Wherever possible, governments should avoid customization by using configuration to meet their goals.Governments also should understand their vendor's particular terminology with regard to this issue since words like "modifications" or "extensions" often mean different things to different vendors.
Reg,
Ashok

T-Code for reporting stock quantity difference between IM and WM

Hi All
I'm probably going to kick myself for asking this quastion but is there a report to show the stock quantity differences between IM and WM?
I have searched the forum first but cannot find info.
We have various differences in IM and WM shown in MD04 and LS26. This is usually the result of an unplanned plant to plant transfer not being recipted in at the destination plant.
If no standard T-code is available, which tables can I join to create my own query?
Thanks in advance
Darren

compare MMBE with LS26
Make sure you dont enter a storage location and storage type in selection screen of LS26.
if you post a difference with LI20, then you have just posted a difference within WM, means you moved a quantity from a bin into the difference storate type 998. The balance of both is still equal to your stock shown in MMBE. You have to clear the difference with IM by executing LI21 transaction. Only then the quantity will disappear from difference storage type and will be adjusted in MM and FI.
LX23 will only report real inconstencies and will adjust them.
If you do a MM movement like 303, then this creates a transfer request in WM, this TR needs to be converted into a TO. to move the stock from the bin to the interim storage type for goods issue.
In your case you created just a negative quant in the interim storage type for goods issue and still have a positive quant in the bin, the balance is equal to the stock shown in MMBE.

Differences between SLIN and Code Inspector

Hi,
Can anyone tell me the differences between SLIN and Code Inspector(SCI)..?
and in which cases we use SLIN and SCI..?
and as an ABAPer, which one should we prefer..?
Thanks,
Pradeep.

Hi
Extended syntax check or SLIN is used to check the program in all aspects for the different syntaxes like
When you use select single whether you have passed all the key fields or not>
whether you have maintained the text elements texts or not,
Have you used UNIT...CURRENCY along with the QTY and AMOUNT fields when displayed using the WRITE statement
and check for all the varities of statements used in the code, and if there is some problem with that statement/command, it will display as error or warning.
Check following links -
slin
can any one tell me abt SLIN T-CODE
Reward points if useful
Regards
Anji

Difference between ob08 and oc41 Transaction code in Exchange rate

Hi,
Can any one help me out what is the difference between OB08 and Oc41 in transaction code in Exchange rates...
Thanks in Advance
Sivanand

hi Siva,
When foreign currencies are valuated, all the open items that were posted in a foreign currency are valuated. The valuation is based on the individual open items in a foreign currency, that is, each open item in a foreign currency is valuated individually.
The exchange rate table is OB08
AND
OC41 is another transaction to the exchange rate table.
When you try to change you cannt change the rates sometimes.... but u can see the rates displayed.......
Regards
Ranjit Kumar

There is a tax code difference between PO and MIRO

There is a tax code difference Between PO and MIRO.tax code is VO in PO but it must be T8 becuase invoice is T8.can you please solve this issue ?
Thanks & Regards
Raj

Hi
Put the Tax code same in PO and MIRO, because In F-47 you have to give the PO no in it. Then create MIGO, Then F-48 and then create MIRO, and Then F-54 Then F-58.
Thanks
Anil

Credit Management: Difference Between Static and Dynamic Credit Check

Hi,
Could anyone tell the difference Between Static and Dynamic Credit Check?
According to website: http://www.sap-basis-abap.com/sd/difference-between-static-and-dynamic-credit-check.htm ... this is the answer:
====================
Simple Credit Check : Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value : Sales Order Has been saved but not delivered
Open Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received the payment from the customer.
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value : Which is save but not delievered
2) Open Delivery Doc.Value : Which is delivered but not billed
3) Open Billing Doc.Value : Which is billed but not posted to FI
4) Open Item : Which is transfered to FI but not received from the customer.
Dynamic Credit Check         1) Open Doc
                                            2) Open Delivery
                                            3) Open Billing
                                            4) Open Items
                                            5) Horizon Period = Eg.3Months
Here the System will not consider the above 1, 2, 3 & 4 values for the lost 3 months.
====================
Question 1: Could you further explain the above information, if there is any?
Question 2:: What is the Tcode to customize settings of:
a) Simple Credit Check (isn't this same with b) below?)
b) Static Credit Check
c) Dynamic Credit Check

Hi Tanish,
Diff between Static and Dynamic Filters.
Example One at report Level.
Create a variable for a Infoobject say ,Material .
1)In the Query Designer and if u restrict it to some 10 materials at query level, the report will display for only those 10 materials only.This is Static Filter.UR AHrdcoding it to those materials.You cant change them at Query Run time.i.e not changeable by user.
2)If u give the variable as input ,and when u run the query ,u can can choose the material,may 10 may be 1 or may 20 .It is dynamic.Changeable by user at run time
Example Two at DTP and Start Routine Level,say Document Type.
1)If u give filters in Start routine it is Static as u cannot change it in Production,not changeable by user.
2)f u give filters in DTP it is Dyanamic as u can change it in Production.U can give any doc type,Changeable by user at run time.
Hope it is Understood.
Rgds
SVU

Difference between validation and susbstittution with tcodes

hi all can any body tell me about difference between validation and susbstittution with tcodes
regars
sravya

Hi,
Settting up the FI Validations
You can use additional validation to supplement the existing SAP logic to fit you into your businness needs.
For e.g. to allow postings from company code 0001 to business area AA only.
GGB0 - To maintain the validations
Validation - Enter a validation name e.g. VBUS
Applicaion Area - SAP module e.g. FI
Calling Point - Dependent upon the application area that is selected.
0001 - Document Header - validate enteries at document header, e.g BKPF table
0002 - Line Items - check line item entris within a document, e.g. BSEG table
0003 - Complete Document - check settings for the whole documents.
e.g. Validation step 001
Allowed company code '0001' to post to business area AA only. 'FI00' checks that line item is from FI.
If checks failed, the error message number 14 is displayed to stop the transaction.
Prerequisite
<BSEG> $BUKRS = '0001' AND
<BKPF> $GLVOR = 'FI00'
Check
<BSEG> $GSBER = 'AA'
Message
Type E No. 14 - Business Area not allowed for company 0001
Output fields 1 - BSEG - GSBER 2 - BSEG - BUKRS
3 - 4
OB28 - Define Validations for Posting
CC CallPnt Validation Description Activtn Level
0001 2 VBUS Business Area Validation 1
Activtn Level - 0 - Not Active 1 - Activated 2 - Activated for all except batch input
GGB4 - Manage the activation of all validations in the SAP system.
Validations, Substitutions, and Rules
Purpose
With the validations and substitutions software, you can validate and/or substitute data at the time of entry in the FI-SL System and other SAP Systems.
Implementation Considerations
You do not need to change the standard system to customize your validations and substitutions. For each installation, you can define exactly which validations and substitutions are necessary to ensure the integrity of your data.
Features
Validation
In the SAP System, almost all input values are validated by a program or against tables or master files. Since some types of validations cannot be standardized, you can use FI-SL's validations program to create validations for your system.
With validations, you can check values and combinations of values as they are being entered in the SAP environment. Validation rules are stored in the Rule Manager; as data is entered, the Integration Manager validates the data against the validation rules stored in the Rule Manager. Because data is validated before it is posted, only valid information enters the FI-SL System.
You define validation rules using Boolean logic. When you define a validation rule, the system checks the validation rule to ensure that it is syntactically correct.
You can also define the result of breaking the validation rule. For instance, you can specify that a message is issued but the user can continue processing. You can also force the user to correct the error before processing can continue.
For more information, see Validation or What Are Validations?. For more information on using validations, see Creating a Validation. For more information on Boolean Logic, see Introduction to Boolean Logic.
Substitution
Substitution rules are stored in the Rule Manager. When data is entered in the system, it is substituted by the Integration Manager. The Integration Manager calls the Rule Manager. Substitution occurs before the data is posted to the FI-SL databases.
You define substitution rules using Boolean logic. When you define a substitution rule, the system checks the substitution rule to ensure that it is syntactically correct.
For more information, see Substitution or What Are Substitutions?. For more information on using substitutions, see Creating a Substitution. For more information on Boolean Logic, see Introduction to Boolean Logic.
Rules
A rule is a Boolean expression that you can use as a condition, as a check, or in another rule. Rules enable you to refer to frequently used Boolean statements simply by specifying the rule name.
The FI-SL Integration Manager uses Boolean logic. When you use Boolean logic and syntax, you can:
Validate data
Substitute data
Select ledgers for posting
Transfer substitution data to a rollup ledger
Select report data
The Rule Manager stores the Boolean rules used to analyze data. The Integration Manager calls the Rule Manager and determines whether entered data should be used. If a Boolean statement is true, an action is taken; if a statement is false, no action is taken.
Boolean logic is used in the following FI-SL modules:
Validation
Substitution
Ledger selection
Report Writer
Rollups
To use Boolean Logic in one of the functions listed, you create statements that are used as formulas in the FI-SL System. For more information on using Boolean Logic, see Introduction to Boolean Logic or Boolean Logic Statements and Rules.

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 task and change request?

Hi all
What is the difference between task and change request?
thanks all

Dear Ispit,
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/19/3f5bf8a4b011d285090000e8a57770/content.htm">Request Types and Task Types</a>
<a href="http://help.sap.com/saphelp_sm32/helpdata/en/dd/cc86a571464559a2685a404397065b/content.htm">Change Transactions in Change Request Management</a>
For more information about the SAP Change and Transport System (CTS), visit the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/57/38ddff4eb711d182bf0000e829fbfe/frameset.htm
Transport Request is generated in following scenarios:
1. Customizing Request - When doing or changing some customization.
2. WorkBench Request - When configuration is cross-client. Eg Generating new Table, making changes in access sequence, Abap development, etc.
Transport request is not generated for Master Data. For eg: Customer Master, Material Master, price master, etc.
Benefit of Transport Request:
SAP Landscape normally has 3- Tier system:
Development Server - Where customization takes place. Transport request is generated at this level & then first transported to Quality server for testing whether it meets the requirement or not. Once the requirement is met in Quality server then Request is transported from Development Server to Production Server (Actual / Live System)
Quality Server - Mainly useful for testing.
Production Server Actual / Live server, where the real transactions are created & posted.
Procedure to Release & Transport Request:
1. In development server, go to T.Code: SE10 & select the check box Modifiable & enter
2. In the next screen, you will see list of transport request created.
Note: Transport request consist of main request along with sub request. These sub request hold the object to be transported.
3. Expand the main request & you will be able to view the sub requests attached to main request.
4. First release the sub requests.
Note: To release the request, select the request ni & click on release request individually (Do not select release all request)
5. Next release main request.
6. Once the request is released sucessfully, imform the basis person to import the request to QA server.
or
If the authority is with you, through T.Code: STMS, select development server --> select request no & release to QA server. Here when it pops up client no, user id & password, maintain it of QA server & release the request to QA server.
Reward points if this is helpful.
Regards,
Naveen.

Difference Between BADI and User Exits

Hi..
generally BADIs & User Exis are used exensively in SAP SD...
Can anybody throw some light waht is difference between them ...
Kindly please reply......
Regards
Nisha

Hi
ifference Between BADI and User Exits
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
    i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
    Ex:- 'Development server'>'Quality server'-> 'Production server'......

Differents between Bespoke and Customization code

Similar Messages

Maybe you are looking for