Brief explanation of DropTargetDropEvent.acceptDrop()?

So, DropTargetDropEvent.acceptDrop()....
What does it do, really? If I'm using a DropTargetListener, why should I bother calling acceptDrop() or rejectDrop()? I mean, I run the show basically with acceptDrag() and rejectDrag(). Those have a clear meaning to me.
Also, dropComplete() clearly has a function- to notify the source of the drag drop activity that the drag-drop is complete.
Can someone offer a few words to explain? The API JavaDoc is no help.

Similar Messages

Need a brief explanation on abap/stack

Can someone please give me a brief explanation of abap/stack
Thanks
Joe

Hi,
check the master guide for Relevant SAP Release.
for ECC 6.0 check following
https://websmp207.sap-ag.de/~sapidb/011000358700000782642007E
regards,
kaushal

Brief explanation Of Dictionary Concepts...

What are done in technical settings ( Data Classes & buffering) ?
 Table Types & differences ?
 Search Help ( types ) ?
 VIews & Differences ?
 Indexes ?
 Data Element ?
 Domain ?
Plz provide some brief and exact answers for the topics above....

DATA DICTIONARY OBJECTS:
1. TABLES
2. VIEWS
3. DATA TYPES
4. DOMAINS
5. SEARCH HELP
6. TYPE GROUPS
7. LOCK OBJECTS
TABLES:
PREDEFINED TABLES - 36675 TABLES.
MARA - General Material Data.
MARC - Plant Data for material.
MAKT - Material Descriptions
KNA1 - General Data in Customer Master
KNB1 - Customer Master (Company Code)
KNC1 - Customer Master (Transaction Figures)
T001 - Company codes
LFA1 - Vendor Master (General Section).
LFB1 - Vendor Master (Company Code).
LFC1 - Vendor MAster (Transaction Figures).
Eg. code to fetch records from MARA table into LPS:
TABLES MARA.
WRITE :/40(50) 'GENERAL MATERIAL DATA' COLOR 7 CENTERED.
SKIP 2.
WRITE :/ 'MATERIAL NUMBER', 'MATERIAL TYPE', 'INDUSTRY SECTOR', 'UNITS'.
SKIP 1.
SELECT * FROM MARA.
WRITE :/ MARA-MATNR COLOR 3 , MARA-MTART COLOR 4, MARA-MBRSH COLOR 5 , MARA-MEINS COLOR 6.
ENDSELECT.
USING SELECT-OPTIONS STATEMENT:
This statement is used to create a range for selection of table records.
syntax:
SELECT-OPTIONS <variable> FOR <table_name>-<field_name>.
eg. code:
TABLES KNA1.
SELECT-OPTIONS CUSNUM FOR KNA1-KUNNR.
SELECT * FROM KNA1 WHERE KUNNR IN CUSNUM.
WRITE :/ KNA1-KUNNR, KNA1-NAME1, KNA1-ORT01, KNA1-LAND1.
ENDSELECT.
TABLES CLASSIFICATION BASED ON CLIENT:
1. CLIENT-DEPENDENT TABLE - Table defined for one particular client cannot be accessed from cross clients. In these type of tables, the first field is MANDT which holds the client number (eg. 800).
2. CLIENT-INDEPENDENT TABLE - These type of tables can be accessed from any different clients. The first field is not MANDT for these type of tables.
CREATING A USER-DEFINED TABLE IN SAP:
In SAP, we can create a table in two types:
1. Built-in Type - The user has to specify the data type and length for each field of the table.
2. Using Data Element - The data type and length for fields is created once and implemented whenever necessary.
COMPONENTS OF TABLE:
1. DELIVERY CLASS - Specifies what kind of data the table we create is going to hold.
2. MAINTENANCE - Specifies what screens should be made available to the user after the table is created and activated.
3. FIELDS - This section is used to create fields of the table.
4. TECHNICAL SETTINGS
 - DATA CLASS - Specifies the storage location of the table in database.
 - SIZE CATEGORY - Specifies initial size of the table in the form of number of records.
Navigations to create table:
SE11 -> Select Database table radiobutton -> Specify table name starting with Z or Y -> Click on Create -> Opens an interface -> Enter short description -> Specify A (Application table) for DELIVERY CLASS -> Specify Display/Maintenance Allowed -> Click on Fields Tab button -> Specify Field names -> Select the first field as Primary key with Initial values -> Specify Data type and length for each field -> Click on Technical Settings pushbutton from Appn. Toolbar -> Save before leaving tool -> Save under a package -> Assign request number -> Opens an interface -> Specify Data Class as APPL0 -> Specify Initial Size Category as 0 -> Save -> Come back -> ACtivate the table.
To create Entries -> Click on Utilities Menu -> Table Contents -> Create Entries -> Opens an interface with fields created -> Specify records -> SAve -> Come back.
To Display Entries -> Select Display from the above menu path -> Opens an interface -> Execute.
Eg. code to insert records into table using selection-screen:
TABLES YMY_TABLE.
PARAMETERS : X LIKE YMY_TABLE-STUDID,
 Y LIKE YMY_TABLE-STUDNAME,
 Z LIKE YMY_TABLE-COURSE.
SELECTION-SCREEN PUSHBUTTON /10(10) LB1 USER-COMMAND PB1.
SELECTION-SCREEN PUSHBUTTON 40(10) LB2 USER-COMMAND PB2.
INITIALIZATION.
LB1 = 'INSERT'.
LB2 = 'EXIT'.
AT SELECTION-SCREEN.
CASE SY-UCOMM.
WHEN 'PB1'.
YMY_TABLE-STUDID = X.
YMY_TABLE-STUDNAME = Y.
YMY_TABLE-COURSE = Z.
INSERT YMY_TABLE.
IF SY-SUBRC = 0.
MESSAGE S000(Z_MY_MESSAGE).
ELSEIF SY-SUBRC = 4.
MESSAGE E001(Z_MY_MESSAGE).
ENDIF.
WHEN 'PB2'.
LEAVE PROGRAM.
ENDCASE.
In the above code, SY-SUBRC is the system variable used to handle exceptions. By default, 0 and 4 are values assigned to the system variable, where
0 specifies the specified action is successful.
4 specifies the specified action is failed.
TABLES CLASSIFICATION BASED ON BUFFERING:
1. SINGLE-RECORD BUFFERING - If a table is created with this buffer type and whenever the user tries to access table records, a buffer area will be created in AS to hold only one record.
2. GENERIC BUFFERING - With this type, by default a buffer will be created to hold a single record. Depending upon the selection criteria, the buffer size is increased or decreased dynamically.
3. FULLY BUFFERED - With this type, a buffer is created to hold all the records existing in the table.
CREATING A TABLE USING DATA ELEMENTS:
NAVINGATIONS TO CREATE A DOMAIN:
SE11 -> Select Domain radiobutton -> Specify domain name starting with Z or Y -> Click on create -> Opens an interface -> Enter short description -> Specify technical attributes (data type and length) for the field -> Save -> Activate -> Come back.
NAVIGATIONS TO CREATE A DATA ELEMENT:
SE11 -> Select Data Type radiobutton -> Specify name -> Click on create -> Opens an interface -> Select Data Element radiobutton -> Continue -> Opens another interface -> Enter short description -> Specify domain name created earlier -> Press enter -> Technical attributes are automatically called from the domain -> Save -> Activate -> Come back.
Create a table -> Specify Delivery class, Display/Maintenance Allowed -> Specify Field names -> Specify Data Element name for each field -> Press Enter -> Specify Technical settings -> Save -> Activate -> Create Entries.
PROVIDING F4 FUNCTIONALITY FOR THE INPUT FIELDS IN GUI:
SE11 -> Select Search Help radiobutton -> Specify name -> Click on Create -> Select Elementary Search Help -> Continue -> Opens interface -> Enter short description -> In SELECTION METHODS, specify table name -> In SEARCH HELP PARAMETERS, specify field names -> Check IMPORT and EXPORT checkboxes -> Specify values for LPOS and SPOS as 1 and 1 -> Save -> Activate.
Use MATCHCODE OBJECT <Search_help> in PARAMETERS statement as follows:
eg.
PARAMETERS A(10) MATCHCODE OBJECT Z_MY_SEARCH.
LPOS and SPOS parameters are used to specify the positions of fields in the search help screen for the input field.
VIEWS:
To fetch records from more than one database table, database view is used.
NAVIGATIONS:
SE11 -> Select View Radiobutton -> Specify name -> Create -> Select Database View -> Continue -> Opens interface -> Enter short description -> Specify table names in TABLES area -> Click on Relationships pushbutton -> Opens an interface -> Select relationship based on primary key values (not based on MANDT field) -> A join condition is automatically generated -> To choose fields from different tables, click VIEW FIELDS tab button -> Click TABLE FIELDS pushbutton -> Select first table -> Click on Choose -> Select required fields -> Repeat same for other tables -> Save -> Activate -> Say NO to warning message.
In SE38 editor, use the following code to access records using View:
TABLES Y_MYVIEW.
SELECT * FROM Y_MYVIEW.
WRITE :/ Y_MYVIEW-MATNR, Y_MYVIEW-MTART, Y_MYVIEW-MBRSH, Y_MYVIEW-MEINS, Y_MYVIEW-WERKS, Y_MYVIEW-LVORM.
ENDSELECT.
-> Save -> Activate.
<REMOVED BY MODERATOR>
Thanks.
Edited by: Alvaro Tejada Galindo on Feb 14, 2008 5:09 PM

Need brief explanation on new Drive Q: topic

hi,
could somebody provide a quick explanation or a link  (before I will dive deep into the docs and theory) of new features/functions
of drive Q: sequencer and most interesting on client.
If possible compare with what was in 4.6
thx.
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

In App-V 5, there is not such a virtual drive letter any longer. The most 'sensitive' item now is the 'Primary Virtual Application Directory' (or: PVAD), though that one existed in App-V 4 already.
In contrast to v4, you won't find any 'PVAD' folder on the client, and you (perhaps) won't find any reference to it. When you look into an .appv file (you know that you can create a copy of that, rename it to .ZIP and open it read-only) you'll notice a 'root'
folder that contains the files that have been palced into the PVAD and perhaps a VFS folder that contains the files that were installed somewhere else.
On the client, you can find the extartcted content in the Package Installation Root (usually C:\Programdata\App-V\Guid\Guid\..
http://social.technet.microsoft.com/Forums/en-US/ca8194b0-bdda-4175-a23b-39d9fc815380/how-to-choose-appv-5-sequencing-primary-virtual-application-directory?forum=mdopappv,
http://www.tmurgent.com/TMBlog/?p=1283
http://blogs.technet.com/b/gladiatormsft/archive/2014/05/24/app-v-5-on-sequencing-using-tokenized-paths-pvad-s-vfs-and-vfs-write-mode.aspx
http://packageology.com/2014/02/app-v-5-pvad-vfs-layering-bug/have
some more stuff to read on that (well, it's more like the old 'VFS or MNT' or 'to Q or not to Q' discussion that we had in 4.x.
Falko
Twitter
@kirk_tn   |   Blog
kirxblog   |   Web
kirx.org   |   Fireside
appvbook.com

Brief explanation about EVS

Hi All,
Give me Explanation about the EVS and wat is the use of it

Hi,
Extended Value Selector
Extended Value Selector (EVS). input help is used for selecting a key/display text pair of a simple data type. Because the SVS is not suitable for displaying large value sets (more than 50, for example), Web Dynpro provides the EVS. This input help displays a popup UI with a built-in function for browsing and filtering large value sets in a table. The EVS can be displayed for every Inputfield UI element with the value property bound to a context attribute of the type simple data type (at runtime).
Pl go through this link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/391ee590-0201-0010-1c89-f1193a886421
Regards
Ayyapparaj

I'm looking for a brief explanation of the following three ES

Cisco strongly recommended we apply some recent Dialer and Campaign Manager ES’s proactively as these have several fixes other customers have needed on the SIP Dialer:
o   8.5(3) ES3: http://i/patch?id=10746
o   8.5(3) ES5: http://i/patch?id=10755
o   8.5(3) ES6: http://i/patch?id=10766
o   Note that these are NOT cumulative so each should be applied in order.
Looking for an explanation in plain english regarding these patches above
What ES stands for and what thoses patches mean
Any help will be appreciated
Sincerely

ES stands for Engineering Special. Generally speaking an ES is a rollup of fixes that are not yet available in any public release. Additionally, the fixes have not gone through the more complete testing (e.g. regression testing) that a formal release has.
Most products have an ongoing changelog document that explain what defects are covered by each ES. You can use that to look up the details of each defect in the bug toolkit if the bug has been marked public. You typically have to obtain the changelog/release notes from the Cisco support resource you are working with. None of the ES information is public typically.
PS- Moving this thread to the Contact Center area might provide you more on-topic responses.

Brief explanation of reports and report painters

hi gurus,
pls if any one knows what is reports and report painters and how it will help ful in real time scenario, why do we prepare report painters? what it is purpose of report painters.
thanks in advance. points will be awarded.
regards,
sandeep.ch

Hi,
With the help of report painter you can create(design) your customised reports. The report painter does not require any ABAP coding, The functional consultants use this report painter tool to create the reports.
For example, In profitability analysis the report painter tool uses vastly where you can design your own report with the combination of characterstics (Customer wise, product wise, etc.) and value fields (Sales, Cost of goods sold, Gross profit, Net profit, etc.) to analyse the profitability..
Beside these reports, the ABAP reports require ABAP coding.
Hope it clarifies your doubt.

Brief Explanation Please

Hello,
I was recently given some good advise here pertaining to a script. In case you don't check the link I do not need a workable script here, that has been taken care of but thank you anyway (is not necessary to answer this question).
https://discussions.apple.com/message/26354845#26354845
However, I understand the change in the dictionary portion of QuickTime Player I am still unclear as to why there is a specifier error with the fixes that I came up with myself. Could someone explain to me please why there is a specifier error with this script;
set this_sound to (((path to folder from System domain) as string) & "Sounds:Submarine.aiff") as alias
tell app "QuickTime Player"
open this_sound
set close after completion of document 1 to true
play document 1
end tell
Hope you all have a great day!
dofromon

Hello
Just for the record, there has never been a property named "close after completion" of "movie" object or "document" object in QuickTime Player (7 or X).
In QuickTime Player 7, there're "close when done" and "quit when done" properties of "document" object, which is indeed "movie" object.
In QuickTime Player 7, the term "movie" is defined as synonym for "document" in its AppleScript dictionary (this synonym definition is hidden in aete resource), that is why the term "movie" in source code in context of QuickTime Player 7 is compiled as "document" in AppleScript editor.
And the reason why the expression such as:
set close after completion of document 1 to true
does not throw compilation error in context of QuickTime Player X is that AppleScript compiler parses it NOT as
(set
    ("close after completion"
        (of (document (1))))
    (to (true)))
but as
(set
    (close
        (after
            (completion
                (of (document (1))))))
    (to (true)))
where
(close (after (completion (of (document (1))))))
is interpreted as
(close ("insertion point" (after (completion (of (document (1)))))))
and this (close ...) construct is expected to return something to be set to true.
Of course this should fail at run-time with various reasons, which include the said coercion error (provided that "completion" is not mere user variable name but defined as constant in QuickTime Player X), but compiler doesn't care and happily yields a non-sense byte-code.
Hope this may help you understand the situation better,
H

Rate-limit command brief explanation

Hi,
There is this rate-limit command in our company's router.
rate-limit input access-group 127 1000000 187500 187500 conform-action transmit exceed-action drop
I know that the access-group part refers to an access list
conform action transmit means that packets will be transmitted
exceed-action drop means that if it exceed the values listed packets will be dropped.
What i dont understand is the logic behind the numbers 1000000 187500 187500. It would be very helpful if someone could explain it briefly, i am having a hard time understanding the cisco docs regarding this command.
thanks.

Hi @seaweeds24,
Those numbers are "average rate" "normal burts size" "excess burst size", respectively.
Average rate determines the long-term average transmission rate. Traffic that falls into this rate will always conform
Normal burst size determines how large traffic bursts can be before some traffic exceeds the rate limit
Excess burst size determines how larget traffic bursts can be before ALL traffic exceeds the rate limit.
Traffic that falls between the Normal Burst size and the Exces Burst size exceeds the rate limit with a probability that increases as the burst size increases.
HTH.
Rgrds,
Martin, IT Specialist

Brief explanation on function module mentioned...

Hello Every one,
Please explain me about SWE_EVENT_MAIL and SWW_WI_CREATE_VIA_EVENT_IBF function modules with its parameters.

Hi,
SWE_EVENT_MAIL Whenever a mail needs to be sent to a user when a particular event has raised then this function module can be used.

Where can I find an explanation of Processes and Log files for LMS 3.2?

Being fairly new to Ciscoworks, I've been scouting for documentation that explains the processes as enumerated by the "pdshow" command. Also, when there are problems, I find myself hunting through the log files without a clear understanding of which log file most likely contains the data I need for troubleshooting purposes.
Is there a document, preferably in table format, that has at least a brief explanation of each of these items? I can probably eventually glean this information from reading all of the documentation, but that would be a lengthy task.
Thanks in advance.

Hi John,
Kindly refer to below doc by Joseph Clarke which have detailed explanation for all the daemons of CiscoWorks .
https://supportforums.cisco.com/docs/DOC-8798
Hope it helps.
Thanks,
Gaganjeet

SqlTypes? Explanation Required Please

After reading this example;
http://www.oracle.com/technology/sample_code/tech/java/sqlj_jdbc/files/advanced/ObjectJavaSample/Readme.html
I have successfully created an application that maps a Java object to an SQL object within a package so that the package can insert data within the object into the appropriate table.
I have a couple of queries about some of the code that I hope someone can answer for me please.
1) The Object Class needs to have this declared:
private static int[] sqlTypes = {12, 12, 12, 2};What is this declaring? and what is it used for?
2) This line of code is used a couple of times throughout the application:
struct = new MutableStruct(new Object[numberOfAttributes], sqlTypes, oraDatafactory);I am going to look through the API about this on Monday, but I'd appreciate it if anyone could give me a brief explanation, as a starter for ten, about what this is actually doing.
Thanks
David
Message was edited by:
David Ferguson

Hi John,
Thanks for your reply.
In the example that is provided by Oracle (see previous post for link) an array of sqlTypes is defined.
The Oracle example has an object with four attributes, and the array of sqlTypes has four elements (presume that is one for each attribute).
I have then edited this example to work with one of my sqlObjects which has 29 attributes, but I have left the sqlTypes array as having only 4 elements and it still works.
Q1. where can I find a definition of all the sqlTypes?
Q2. why does my application with 29 attributes still work when I have only declared an arrray of sqlTypes with 4 elements in it?
Q3. what is the sqlTypes array used for when mapping java objects to sqlObjects?
Any further information on this subject would be appreciated.
Thanks
David

Field Explanations

I'm looking for briefexplanatiopns about the fields in "Maintain Condition Types (SPRO > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Types > Maintain Condition Types > Condition Type)" . There are areas of Control data 1, Group condition, Changes which can be made, Master data, Scales, Control data 2 and Text determination. I'll be happy if somebody sends me brief explanations about the fields in these areas or send me a web site adress consisting of brief explanations on those areas.
Thanks in advance.

Hi,
You should know about the various fields which are there in a particular condition type. In V/06 when you define a new condition type:
1. Access sequence - Used for condition types which are kept mandatory in the pricing procedure. The access sequence searches for the condition record as per the key combination maintained in the condition table assigned to the access sequence.
2. Condition class - Preliminary structuring of condition types e.g. in surchages and discounts or prices.
A grouping that lets you control each condition type differently.
For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
3. Calculation type - Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record.
4. Condition category - A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).

5. Rounding rule - The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
6. Structured condition - controls whether the condition type should be a duplicated condition or a cumulated condition.
This control is only helpful when you use bill of materials or configurable materials.
Aduplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.
7. Group condition - Indicates whether the system calculates the basis for the scale value from more than one item in the document.
Use
For a group condition to be effective, the items must belong to a group. You can freely define the group to meet the needs of your own organization. The items can, for example, all belong to the same material group.
8. Routine number for creating group key - Identifies a routine that calculates the basis for the scale value when a group condition occurs in pricing.
Example
You can specify a routine, for example, that totals the value of all items in a document in order to determine the basis for a discount.
9. Rounding difference comparison - Indicator that controls whether rounding difference is settled for group conditions with a group key routine.
If the indicator is set, the system compares the condition value at header level with the total of the condition values at item level. The difference is then added to the largest item.
10. manual entries - Indicator which controls the priority within a condition type between a condition entered manually and a condition automatically determined by the system. Here you can specify whether the condition type can be processed only manually or not
11. Header Condition - If this condition is marked as a header condition, it is possible to enter the condition type in the header condition screen. Checks for changing the condition manually are unaffected by this.
12. Item condition - Mark this field if the conditions of this type are allowed to be entered in the document items. The condition is then only valid for the particular item in which it is entered.
13. Delete - Indicator that controls whether the condition type may be deleted from the document.
14. Amount/percent - Specifies whether the amout or percentage for the condition type can be changed during document processing.
15. Value - Specifies whether the value of the condition type can be changed during document processing.
16. Quantity relation - Specifies whether the conversion factors for the units of measure in conditions of this type can be changed during document processing.
17. Calculation type - Specifies whether the calculation type for the condition type can be changed during document processing.
18. Valid from - Proposed value from when the record of the condition type is valid.
19. Valid to - Proposed value for how long a condition should remain valid.
20. Reference condition type - A condition type which can be used as a reference so that you only have to create condition records once for condition types that are very similar.
21. Reference application - Application, that can be used to refer to condition records from other applications.
Use
You only have to create condition records once for condition types that are very similar. You can also refer to condition records from other applications.
You will find further information on the ReferencCondType field in the documentation.
22. Pricing procedure - Determines which condition types can be used in a document and in which sequence they appear.
Use
The system uses the pricing procedure that you enter here to control the use of condition supplements in records of this condition type. You can apply the discounts that are defined in the pricing procedure as condition supplements during pricing.
23. Delete from database - You can use this indicator to control how the system operates when deleting condition records.
24. Condition index - Specifies whether the system updates one or more condition indices when maintaining condition records.
Use
This makes it possible to list or maintain condition records indepently of condition type and condition table, for example.
25. Condition update - Controls whether limit values are relevant for pricing.
E.g.: you can make the use of a particular condition record in the document dependent on a specified total value.
This total value can be specified in the condition record.
26. Scale basis - Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume.

27. Scale formula - Formula for determining the scale base value.
28. Check value - Indicates whether the scale rates must be entered in ascending or descending order.
29. Unit of measurement - Unit of measure that the system uses to determine scales when you use group conditions
30. Scale type - Indicator that controls the validity of the scale value or percentage:
From a certain quantity or value (base scale)
Up to a certain quantity or value (to-scale)
Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
31. Currency conversion - Controls the currency conversion where the currency in the condition record varies with the document currency.
32. Accruals - Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.

33. Invoice list conditions - Marks the condition type as relevant for internal costing.
34. Inter company billing condition - Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
35. Service charge settlement(trading contract) - Indicates that the trading contract conditions should be calculated using the vendor billing document.
36. Quantity conversion - This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
37. Condition exclusion - Indicates whether the system automatically excludes the discounts that are proposed during pricing.

38. Pricing date - Enter the identification code for the date to which a condition of this type is to be calculated in the sales document. If you do not enter an identification code, the pricing date or the date of services rendered is used.
39. Relevance for account assignment - Controls how account assignment is performed for conditions of this type.
40. Text determination procedure - Identifies a group of text types that you can use in, for example, a sales document header. The text procedure also determines the sequence in which the text types appear in the document.
41. Text ID - Specifies which text ID appears in Text Edit Control.
The text ID defines the different types of texts that belong to a text object.
For the respective fields press "F4" and you will see the various options. Select those and try it out yourself by creating the sales order and see the effects. It will help you a lot. If you understand the control of each field then you will automatically understand the different condition types and how they behave in the sales documents
Reward points if solution helps.
Regards,
Allabaqsh G. Patil

Detailed Software Repair Instructions using Pc Companion(Win)or Bridge for MAC. (Update 8/5/2014)

We have an extended guide that should help you repair the system of your phone. This instructions are valid for all Android based units and for some legacy Sony Ericsson models(The list of phones that can be used with the application is displayed in Step 9 of the process). please follow the instructions carefully: Turn the phone off and disconnect it from the computer. 1. Visit this link:http://www.sonymobile.com/us/tools/pc-companion/Click on Download PC companion2.Run the software After the installation the first screen will show you the PC Companion Startup Guide which gives you a brief explanation on the main modules of PC companion (Support Zone, Xperia Transfer, Contact setup and Media Go) Keep clicking next.3.Now you will see the screen with the different modules.Select Support Zone> Click Start. The program will download the module. Then click on start on Phone/Tablet Software update. (Here you can choose to update an accessory, go to step 14 for instructions) Note: At this point if you get an error stating that "unable to install update components" or "server is busy" Please proceed to step 13 . If you not see that error then continue with step 4.
4. The program will show a window saying "could not find phone/Tablet” Do not Connect phone instead select Repair my phone/tablet. This will bring you to a window with a warning that says "data will be lost" (do you want to continue) Select to continue (Data in the phone will be deleted, only data in the SD card will remain. Make sure you have done all proper backups if possible)6. The program will issue a second warning stating that “data saved in the phone /tablet will be overwritten during the update of your phone”. Click on the checkmark box next to the acceptance text and select Next to continue.7. Next the computer will download the necessary files (Prepare stage, this can take several minutes depending on the speed of your connection) and then its done it will show you a list of recommendations for a successful update operation. When you are done reading this section click on the checkmark box and press Continue8. Next you will get a Battery level warning that states that your phone should have at least 80% battery. (If the issue in the phone does not permit the unit from turning on, then charge it connected to the wall charger for at least 2 hours and then comeback to this step) Then click on the checkmark and select Next9. Choose the Phone from the list then click on "next" then you will see a new section telling you how to connect the phone. (don't connect it yet) Again, at this point the phone must be off and disconnected from the PC. 10.. Connect the cable to the PC not to the phone, then while pressing and holding the indicated button (in the steps on screen an specific button will be shown for you to press on the phone) connect the cable to the phone and keep holding the indicated button until the program says "the update of your phone has started..." (in some cases a message of "Installing drivers" will appear before the message of "the update of your phone has started..." is shown.) 11. If you failed to follow the steps correctly the phone will turn on. If this happens disconnect the phone from the cable, turn it off and repeat from step 10). 12. If the phone is connected properly, PC Companion will proceed with the update ( It will tell you to let go of the key) then wait for the update to finish and follow instructions on screen to disconnect the unit. End of process. ----------------------------------------------------------------------If the software fails to install:13. If "unable to install update components" 1. Close Pc companion 2. Install Java from: http://www.java.com 3. start Pc companion again and try to do the software unlock process once more. 14.Select Accessories software update. Click on start and the computer will download the necessary files (Prepare Stage) it will take several minutes. Then follow the instructions from step 8. Note: Some computers may block the installation of the update service, if this happens use this:http://www.sonymobile.com/us/tools/update-service/ this is the Standalone update software. (Not globally available)If the Phone is unresponsive (Then do this extra step and when done proceed to redo the repair process:Press and hold the power button and the volume up button at the same time for 10 to 15 seconds. This will reset the unit)Note: This procedure does not work for the Xperia Play R800x (Verizon and other Non SIM card variants of the Xperia play that lack MTP support. It does work for the R800a At&t's model)Bridge For Mac instructions on my post below. Valid for all Android based units and most java Sony Ericsson units.

Here are the basic Steps for Bridge for MAC.Download Bridge for MAC from:http://www.sonymobile.com/gb/tools/bridge-for-mac/The phone should not be connected to the MAC.
The phone should be off.After the Download unzip the file and drag the bridge for MAC icon to the Applications folder. (install then use finder to locate icon)In the Main "No phone connected" window, on the top menu (top application menu) Select "Phone" and scroll down to "Repair phone"
This will open the Phone Software Restore window with the 3 sections for Start, Prepare and Update.
Click on continue bellow. Doing so will popup a window warning you about the loss of your personal info. Click on the checkmark signaling that you understand the data loss situation,
This will take you to the Connection Procedure Screen. Follow the instructions in the screen and click on continue*.
*One key aspect of the last step to keep holding the indicated button before and after you connect the phone to the MAC until the update starts. IF this is not done correctly then the phone won't connect to the MAC

Create J2EE Application in Release 6.20

Hi All,
I'm quiet new to SAP WAS.
I read in the documentation that JAVA IDE (SAP NETWEAVER DEVELOPER STUDIO) is added start on Release 6.30 (Please, correct me if I'am wrong).
If it so, how can I create J2EE application in Release 6.20. A brief explanation will be highly appreciated.
Thanks,
Edward (Indonesia).

Hi Kalle,
Thx, I have got the CD brom the Basis guy, and sucessfully installed it on my PC.
But when I try to execute Stand Alone Server, this error occured:
Loading core services:
Starting core service monitor ... done.
Starting core service p4 ... done.
Starting core service log ... done.
Starting core service dbms ... done.
Starting core service security ... done.
System Exception * Fail to start Naming. Exception is: java.security.AccessContr
olException: access denied (com.inqmy.lib.security.DomainsEnumerationPermission
ProtectionDomainEnumeration)
java.security.AccessControlException: access denied (com.inqmy.lib.security.Doma
insEnumerationPermission ProtectionDomainEnumeration)
 at java.security.AccessControlContext.checkPermission(AccessControlConte
xt.java:269)
 at java.security.AccessController.checkPermission(AccessController.java:
401)
 at com.inqmy.core.policy.PolicyManager.getProtectionDomainStack(PolicyMa
nager.java:311)
 at com.inqmy.core.service.context.container.security.DefaultProtectionDo
mainContext.getProtectionDomainStack(DefaultProtectionDomainContext.java:99)
 at com.inqmy.services.security.domains.ProtectionDomainManagerImpl.getPr
otectionDomainStack(ProtectionDomainManagerImpl.java:96)
 at com.inqmy.services.jndi.InitialContextFactoryImpl.getInitialContext(I
nitialContextFactoryImpl.java:72)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
62)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
 at javax.naming.InitialContext.init(InitialContext.java:219)
 at javax.naming.InitialContext.<init>(InitialContext.java:175)
 at com.inqmy.services.jndi.JNDIFrame.bindReferences(JNDIFrame.java:278)
 at com.inqmy.services.jndi.JNDIFrame.start(JNDIFrame.java:176)
 at com.inqmy.core.service.application.ApplicationServiceRunner.startFram
e(ApplicationServiceRunner.java:55)
 at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java
:126)
 at com.inqmy.core.thread.impl2.SingleThread.run(SingleThread.java:118)
Starting core service naming ... done.
Please Help.
Warm regard,
Edward.

Brief explanation of DropTargetDropEvent.acceptDrop()?

Similar Messages

Maybe you are looking for