Differences between regular and Japanese localized

What are the differences between regular JDeveloper 2.0 and
Japanese localized versions ?
I received regular JDeveloper 2.0 (Build 343) from the U.S.
Is there any issue or limitation to use it in order to use
Oracld RDBMS 8.0.5 & 8.1.5 created with character set JA16EUC
running on Solaris ?
I think there is no issue or limitation if we use it with
NLS-zip.
Or do we have to use Japanese localized versions ?
Then what's the benefit of using it ?
Any information about this would be much appreciated.
Best regards,
null

The US JDeveloper version if used with Japanese fonts , or
better with a Japanese NT will allow for display and input of
Japanese text including when interacting with Oracle databases.
This is the internationalization support and JDeveloper is
internationalized for Japanese
The only difference between the versions (other than a couple OS
dependent bugs in the readme file) is that the Japanese version
has a UI and documentation in Japanese as opposed to English.
Hope this helps.
Yoshikazu Ichitsuka (guest) wrote:
: What are the differences between regular JDeveloper 2.0 and
: Japanese localized versions ?
: I received regular JDeveloper 2.0 (Build 343) from the U.S.
: Is there any issue or limitation to use it in order to use
: Oracld RDBMS 8.0.5 & 8.1.5 created with character set JA16EUC
: running on Solaris ?
: I think there is no issue or limitation if we use it with
: NLS-zip.
: Or do we have to use Japanese localized versions ?
: Then what's the benefit of using it ?
: Any information about this would be much appreciated.
: Best regards,
null

Similar Messages

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.

Difference between Regular Reversal and out-of-sequence reversal

Can anyone help me understand the difference between Regular Reversal and out-of-sequence reversal? How does the system behave differently i these two reversals?
Thanks
Charlene

Sorry for the long reply, as here's some information that I have on Voids and Out-of-Sequence reversals.
On occasion, SAP payroll results can be created in error. In these cases, the payment never goes to the employee and the payroll result should never have been created. These cases are considered reverse payments in the off cycle workbench.
There are two forms of reverse payments: voids and out of sequence reversals. Notes 160515, 159701 and 337626 should be reviewed carefully.
An out of sequence reversal occurs when third party remittance has been run for the payroll result, or when the payroll result is not the most recent result in the cluster directory for the employee. Wage type /568 (total reversal amount) is created in the reversed result for posting purposes. Wage type /571 replaces any /559 wage types in the reversed result and the BT cluster is cleared.
Wage type /568 is created for posting purposes and it will not appear in any retros over the reversed result.
An out of sequence reversal should not occur when the employee receives the money unless the actual check is returned or the direct deposit is reversed by the bank. Because of the tax when paid principle, even if an employee writes a check back to the company for the overpaid amount, this should be processed by retro master data changes and the employee check should be used to relieve any claims in the most recent period. The claims processing guide gives details on how to relieve claims. Out of sequence reversals depend on third party remittance but not on posting to FI.
/568 - Total reversal amount - If you cancel a payroll result that A. Has had payments made to third parties or B. is other than the last one. This is considered an out of sequence reversal. If these two conditions do not apply, a true void occurs. Wage type /568 is the total reversal amount. Should be the sum of /569, /570 and /571.
/571 - Reversal of /559 - Wage type /571 is the reversal of /559 (bank transfer). /571 will record the amount from wage types /559. The /559 wage types will be deleted from the cluster that was reversed. Wage type /571 will have the same sign as wage type /559.
In payroll reporting, the reversal amounts are evaluated in the next payroll period. The same is true for posting to FI.
The out of sequence reversal should have been accompanied by a master data change that forced a retro via infotype 0003.
This retro will fix FI postings in the posting process that accompanies the retro run.For this reason, out of sequence reversals do not need an entry in table T52OCG for processing by the off cycle batch process.
Regardless of if a reverse payment is a void or an out of sequence reversal, there should be an associated master data change to perform this process properly. There had to be a reason that the payment should not have been made and this reason needs to be reflected in the employees master data. Both voids and out of sequence reversals can occur before or after the master data change, but the safest method is to perform the master data change first to ensure it occurs before the next payroll is processed.
In payroll reporting, voids are bypassed in the period for which they were originally paid. This means that if a payroll report is run for a specific period containing a void, the voided result will not be picked up. In FI, voids are bypassed in the period in which they were voided. This is possible because the off cycle batch process already reconciled any incorrect posting that occurred before the payroll result was voided.
A voided payroll result occurs when no money was given to the employee and no money was remitted through third party remittance. A void is simply a check or direct deposit that was created in error. The payroll control record was already exited and the check or direct deposit was already processed, therefore the payroll result can not be recalculated in the original period.
A void can only occur if the payroll result is the most recent result for the employee.
If the payroll result is not the most recent result, an out of sequence reversal occurs by default. It is irrelevant whether the transfer to FI has occurred or not with relation to voids. Some OSS notes state that posting to FI does matter and these notes are in error.

What is difference between Iterator and Collection Wrapper?

Hi all,
I dont understand the actual difference between Iterator and Collection Wrapper. I observed both are used for the same purpose. Could any one please let me know when to use Collection Wrapper and when to use Iterator??
Thanks,
Chinnu.

L_Kiryl is right.
Collections support global iteration (through collection->get_next( )) and local iteration (through iterator->get_next( )).
Each collection has a focus object. Initially, the first object has the focus.
Any global iteration moves the focus, which is published by the event FOCUS_CHANGED of the collection.
If you want to iterate on the collection without moving the focus (and without triggering timeconsuming follow-up processes) you can use local iteration. To do so, request an iterator object from the collection and use this to iterate.
And one more advantage of using iterator: it takes care of deleted entities. If you use global iteration then when you reach deleted entity it will be an exception. But there is no exception with iterator in the same situation.

ABST2 - Differences between Assets and G/L accts

Hi Experts
We are working on ECC 6.0 and INR is our local currency.
At the end of FY 2007 by mistake direct postings were made to Dep Fund Account which is a Recon a/c and FY 2007 was closed
And because of which FI-GL and FI-AA doesnt match by INR 37353.71 (amt posted in above doc) as shown in ABST2
I've referred SAP notes 104567 & 69225 and found the note 69225 relevant to follow as the difference has not resulted in the current or open years.
So we have passed direct entry which is exactly the reversal of entry posted above using ABF1 (INR -37353.71)
After posting the 2nd document, in ABST2 another line has appeared of INR -37353.71. Although the sum for my recon GL is now zero.
The output of ABST2 is as below now -
Sc Acct no.   BusA Year SG 1st local difference LCurr Doc.no.    Period
AS 31100                2009               37,353.71-        INR     W004
AS 31100                2009               37,353.71         INR     W004       999
When I come out of ABST2 , addition to 1st, error no 2 is also coming which I thought would disappear.
1.Differences between assets and G/L accts in the balance carried forward
     Message no. MQ555
2.Differences between assets and G/L accounts at the key date
     Message no. MQ557
Is still something else needs to be done?
Or can I move ahead as the summation of the difference is now zero?
Please suggest.
Kapil

We referred to SAP and they suggeted that the tagging of W004 in both the lines means that now there is no error even system prompts it as error.
So we continued with the transactions and after closing the FY 2009, today when we run ABST2, we dont get any error messages as there is no difference left between Assets & GL.

Difference between VAT AND EXCISE DUTIES

HI ginius
can any body give the difference between vat and excise duties

VAT is value added tax. a tax levied by the government at the time of sales earlier it was LST ( local sales tax ) this is livied by the state goverments.
ok...example .like if colgae is manufacturing toothpaste and yu are buying it ... so at the time of buying ap[art from the price of material you are payin the vat also.
but wher as excise duty is concerend it is levied by the central excise departments
it is lived on colgate company after it manufactured the product even before selling the toothpaste colgate should pay excise to central excise dept on toothpaste becasue it manufactured it in india ( ofcourse it again collects frm the customer by hiking price )
and excise is calulate don advolrem basis whcih is approx 16% on base price.

What is the difference between TO_CHAR and TO_DATE()?

Hi everybody,
i am facing a problem in my system.It is quite urgent, can you explain me "What is the difference between TO_CHAR and TO_DATE()?".
According to user's requirement, they need to generate a code with format "YYMRRR".
YY = year of current year
M = month of current month (IF M >=10 'A' ,M >=11 'B' , M >=10 'C')
RRR = sequence number
Example: we have table USER(USER_ID , USER_NAME , USER_CODE)
EX: SYSDATE = "05-29-2012" MM-DD-YYYY
IF 10
ROW USER_ID , USER_NAME , USER_CODE
1- UID01 , AAAAA , 125001
2- UID02 , AAAAA , 125002
10- UID010 , AAAAA , 12A010
This is the original Script code. But This script runs very well at my Local. Right format. But it just happens wrong format on production.
12A010 (Right) => 11C010 (Wrong).
SELECT TO_CHAR(SYSDATE, 'YY') || DECODE( TO_CHAR(SYSDATE, 'MM'),'01','1', '02','2', '03','3', '04','4', '05','5', '06','6', '07','7', '08','8','09','9', '10','A', '11','B', '12','C') ||     NVL(SUBSTR(MAX(USER_CODE), 4, 3), '000') USER_CODE FROM TVC_VSL_SCH
     WHERE TO_CHAR(SYSDATE,'YY') = SUBSTR(USER_CODE,0,2)
     AND TO_CHAR(SYSDATE,'MM') = DECODE(SUBSTR(USER_CODE,3,1),'1','01',
          '2','02', '3','03', '4','04', '5','05',
          '6','06', '7','07', '8','08', '9','09',
          'A','10', 'B','11', 'C','12')
I want to know "What is the difference between TO_CHAR and TO_DATE()?".

try to use following select
with t as
(select TO_CHAR(SYSDATE, 'YY') ||
         DECODE(TO_CHAR(SYSDATE, 'MM'),
                '01', '1',
                '02', '2',
                '03', '3',
                '04', '4',
                '05', '5',
                '06', '6',
                '07', '7',
                '08', '8',
                '09', '9',
                '10', 'A',
                '11', 'B',
                '12', 'C') as code
    from dual)
SELECT t.code || NVL(SUBSTR(MAX(USER_CODE), 4, 3), '000') USER_CODE
FROM TVC_VSL_SCH
WHERE SUBSTR(USER_CODE, 1, 3) = t.codeand yes you need check time on your prodaction server
good luck
Edited by: Galbarad on May 29, 2012 3:56 AM

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 ws_download and gui_download

Hi
Can anyone explain briefly the difference between ws_download and gui_download
Thanks in advance
sapien

Hai,
in ws_download is Obsolete in Higher Versions
file type is as follows
PARAMETERS: P_FILE LIKE RLGRAP-FILENAME.     "local file with contracts
CALL FUNCTION 'DOWNLOAD'
     EXPORTING
         FILENAME                = ' '
          FILETYPE                = I_TYPE
     TABLES
          DATA_TAB                = T_DOWNLOAD
     EXCEPTIONS
          INVALID_FILESIZE        = 1
          INVALID_TABLE_WIDTH     = 2
          INVALID_TYPE            = 3
          NO_BATCH                = 4
          UNKNOWN_ERROR           = 5
          GUI_REFUSE_FILETRANSFER = 6
          OTHERS                  = 7.
in gui_download -->is using instead of 'ws_upload'
file type is as follows
PARAMETERS: P_FILE LIKE STRING.     "local file with contracts
DATA: D_FILENAME TYPE STRING,
      D_FILEPATH TYPE STRING,
      D_FULLPATH TYPE STRING,
      L_FILETYPE TYPE CHAR10.
IF L_FILETYPE = 'ASC'.
L_FILETYPE = 'ASC'.
ELSE.
L_FILETYPE = 'DAT'.
ENDIF.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_SAVE_DIALOG
EXPORTING
   WINDOW_TITLE         =
   DEFAULT_EXTENSION    =
   DEFAULT_FILE_NAME    =
   FILE_FILTER          =
   INITIAL_DIRECTORY    =
   WITH_ENCODING        =
   PROMPT_ON_OVERWRITE = 'X'
   CHANGING
    FILENAME             = D_FILENAME
    PATH                 = D_FILEPATH
    FULLPATH             = D_FULLPATH
   USER_ACTION          =
   FILE_ENCODING        =
EXCEPTIONS
    CNTL_ERROR           = 1
    ERROR_NO_GUI         = 2
    NOT_SUPPORTED_BY_GUI = 3
    others               = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
           WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF NOT D_FULLPATH IS INITIAL.
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
BIN_FILESIZE                    =
    FILENAME                        = D_FULLPATH
    FILETYPE                        = L_FILETYPE
APPEND                          = ' '
WRITE_FIELD_SEPARATOR           = ' '
HEADER                          = '00'
TRUNC_TRAILING_BLANKS           = ' '
WRITE_LF                        = 'X'
COL_SELECT                      = ' '
COL_SELECT_MASK                 = ' '
DAT_MODE                        = ' '
CONFIRM_OVERWRITE               = ' '
NO_AUTH_CHECK                   = ' '
CODEPAGE                        = ' '
IGNORE_CERR                     = ABAP_TRUE
REPLACEMENT                     = '#'
WRITE_BOM                       = ' '
TRUNC_TRAILING_BLANKS_EOL       = 'X'
WK1_N_FORMAT                    = ' '
WK1_N_SIZE                      = ' '
WK1_T_FORMAT                    = ' '
WK1_T_SIZE                      = ' '
IMPORTING
FILELENGTH                      =
TABLES
    DATA_TAB                        = T_DOWNLOAD
FIELDNAMES                      =
EXCEPTIONS
   FILE_WRITE_ERROR                = 1
   NO_BATCH                        = 2
   GUI_REFUSE_FILETRANSFER         = 3
   INVALID_TYPE                    = 4
   NO_AUTHORITY                    = 5
   UNKNOWN_ERROR                   = 6
   HEADER_NOT_ALLOWED              = 7
   SEPARATOR_NOT_ALLOWED           = 8
   FILESIZE_NOT_ALLOWED            = 9
   HEADER_TOO_LONG                 = 10
   DP_ERROR_CREATE                 = 11
   DP_ERROR_SEND                   = 12
   DP_ERROR_WRITE                  = 13
   UNKNOWN_DP_ERROR                = 14
   ACCESS_DENIED                   = 15
   DP_OUT_OF_MEMORY                = 16
   DISK_FULL                       = 17
   DP_TIMEOUT                      = 18
   FILE_NOT_FOUND                  = 19
   DATAPROVIDER_EXCEPTION          = 20
   CONTROL_FLUSH_ERROR             = 21
   OTHERS                          = 22

Difference between BBP_GET_STATUS_2 and CLEAN_REQREQ_UP reports

Could someone explain in simple way what is the difference between BBP_GET_STATUS_2 and CLEAN_REQREQ_UP reports? I have read the differences in standard documentation but it is a little confusing.
Thanks!
Regards,
Madhur

Hi
CLEAN_REQREQ_UP (Cleaner Job)
You can use this function for document types Shopping cart, (Local) Purchase Order, Confirmation, and Invoice to trigger a synchronization with the associated documents in the back-end system. The system checks whether and how the (follow-on) documents were posted in the back end, and updates the object link and references, as well as the document status.
A job (background processing) is generated for the program CLEAN_REQREQ_UP. When this is run, the system queries a database table containing the transfer information of the documents to the back end. The entries are checked with the data of the respective back-end systems. If the back-end transfer is successful, the respective entries are deleted and the prerequisites for further processing are created.
BBP_GET_STATUS2 (Status Job)
The status job was created by SAP to update the EBP system with data such as purchase requisition number, purchase order number, goods received or invoices recorded manually in R/3, etc. The report should not be run on a frequent basis at short intervals unless the order count from EBP to R/3 is not that high. Otherwise, a recommended interval for running the report is approximately every hour. Basically the schedule times depend on your business requirements.
Until this job runs, the user will not see the number of the backend document created in R/3 for a particular shopping cart in the history tab of the check status transaction.
Some more information :
Go to:
SPRO->IMG->Integration with Other SAP components->Advanced Planning and
Optimization->basic Settings for the Data Transfer->Change Transfer->
change Transfer for Transaction Data->Active Online Transfer using BTE
Here you should maintain the application 'SRMNTY' with active flag.
Once this customizing is enabled, whenever a follow-on document
(either confirmation or invoice) for an extended classic PO is created
in the backend R/3 system, the R/3 system communicates to the SRM system
by creating an entry in the table BBP_DOCUMENT_TAB for this PO.
The item level of the SRM PO has fields to store the actual quantity
and values entered for the corresponding confirmations and invoices.
After that, run the reports CLEAN_REQREQ_UP and BBP_GET_STATUS_2.
When the report CLEAN_REQREQ_UP runs this will update the
PO with statistical information. With the latest information in
BBP_PDIGP table (statistical information) the query should work fine.
Summer

Difference between BAPI and IDocs

hello all
what is difference between BAPI and IDocs

Hi,
BAPI
One of the big plusses for BAPIs is that the interface and function are not supposed to change. This is a big plus when you do upgrades or hot packs because the transaction can change (format, required inputs etc) which means you then need to update the call transaction.
Some of the BAPIs are better documented and easier to use than others. You usually need to perform the BAPI that actually does the COMMIT after you call your BAPI.
The Program coding for calling a BAPI is usually cleaner than setting up the screen flow etc for the Call Transaction.
You don't need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that.
BAPIs probably have better performance since they don't do the screen flow processing.
In general if the BAPI exists for the transaction you want to perform and you can figure out how to use it the BAPI is probably the best way to go.
BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
IDOC
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
Regards,
Bhaskar

Regional Settings differences between 2008 and 2012

Hi There,
Can anyone explain why some of the regional setting details have changed with Win 2012?
Example: Dutch (Belgium) - nl-BE
The 'Digital Grouping Symbol' has changed from a DOT to a WHITESPACE.
2008 - €1.000,00 whereas 2012 - €1 000,00
If the settings are changed on the servers will they persist after OS updates etc?
Rgds,
Frank

Hi Vivian,
I see no reference in the KB article to modifications for the CET timezone nor any reference to the resolution of culture format info discrepancies.
A further issue is that the active regional settings on our PRD servers will be set to United States and it would appear that any modification to the Belgium locales (i.e. nl-BE, fr-BE) are not persisted once you switch to United States as the
active setting.
The knock on effect of this is that for our PRD web-applications (which are active across many regions), we have to write code to override the OS information. .NET uses the OS info to populate its Culture information.
Could you confirm if the differences between 2008 and 2012 are the result of a bug or are the changes planned? Based on communication with some of our customers in Belgium, they are of the opinion that the 2008 (and Win 2003) settings are per their expectations.
I really do not what to have to handle these situations across our application landscape and am sure that other people with globalized applications will also hit problems.

Differences between assets and G/L accts

Differences between assets and G/L accts in the balance carried forward
Message no. MQ 555
Diagnosis
Differences occurred in the balance carried forward when comparing asset summary records and G/L accounts.
Procedure
Using program RFEWSBAL, select the accounts for which differences occurred. To do this, proceed as follows:
1. Changeover package: Active package
Phase: ANALYZE
Origin of change: AS
Proceed
1. Analyze the accounts containing errors using note 104567.
If the document number field contains the entry "W004", this means that although a difference exists in the balance carried forward, this difference was charged off at the key date. Following local currency changeover, the system adjusts the currency differences at the key date only, but not in the balance carried forward.
If the entry "W004" exists for all affected accounts, the status is set to warning instead of error. If the correction at key date described above proves sufficient, you can continue changing over the local currency without additional adjustments in the previous year.
However, SAP does recommend that you make corrections in the previous year in line with note 104567 since this ensures that the balance carried forward is also reconciled.

Hello,
There 2 t codes ABST and ABST2.
You have issue if ABST does not match.
ABST2 is as of today t code. Ideally they will match.
To fix the issue
execute AFAR
then execute AFAB repeat run dep.
Normally your will asset balance will match with GL

Exact difference between function and procedure

exact difference between function and procedure(real time diff.....not like return value, dml....) and function do some work at the same time that work also do procedure..why function

ranitB wrote:
1. Function is called Inline a query. A return value is must.
But, procedure may/may not contain a return value.Not true.
A function may be called in a query providing it meets certain limitations (no DDL, or transactional statements such as commit/rollback etc.).
A function does not have to be called from a query, it can be called from other PL/SQL code or from other external applications.
Regular functions must return a value, though pipelined functions do not...
SQL> CREATE OR REPLACE TYPE split_tbl IS TABLE OF VARCHAR2(32767);
2 /
Type created.
SQL> CREATE OR REPLACE FUNCTION split (p_list VARCHAR2, p_delim VARCHAR2:=' ') RETURN SPLIT_TBL PIPELINED IS
2      l_idx    PLS_INTEGER;
3      l_list   VARCHAR2(32767) := p_list;
4      l_value VARCHAR2(32767);
5    BEGIN
6      LOOP
7        l_idx := INSTR(l_list, p_delim);
8        IF l_idx > 0 THEN
9          PIPE ROW(SUBSTR(l_list, 1, l_idx-1));
10          l_list := SUBSTR(l_list, l_idx+LENGTH(p_delim));
11        ELSE
12          PIPE ROW(l_list);
13          EXIT;
14        END IF;
15      END LOOP;
16      RETURN;
17    END SPLIT;
18 /
Function created.
SQL> SELECT column_value
2 FROM TABLE(split('FRED,JIM,BOB,TED,MARK',','));
COLUMN_VALUE
FRED
JIM
BOB
TED
MARK... whilst the definition of the function shows a return type, the return statement inside the function simply returns, without a value. That's because the data is passed back through a special "pipeline", and you can write code to show that the data is available to a query as soon as it's piped, and before the function has completed (reached the return statement) if you like.
A procedure does not return a value (And no an OUT parameter is not a "returned" value, it's a writeable parameter, there's a difference)
2. There are some limitations in functions which is possbl through procedures.
Like - Oracle doesn't support DML in functions called in Select queries (using PRAGMA AUTONOMOUS_TRANSACTION will help).Not strictly true. and SQL query is considered to be DML, so a function could perform a query and then be used inside another query...
SQL> ed
Wrote file afiedt.buf
1 create or replace function f_dname(p_deptno in number) return varchar2 is
2    v_dname varchar2(10);
3 begin
4    select dname into v_dname
5    from   dept
6    where deptno = p_deptno;
7    return v_dname;
8* end;
SQL> /
Function created.
SQL> ed
Wrote file afiedt.buf
1* select empno, ename, f_dname(deptno) as dname from emp
SQL> /
     EMPNO ENAME      DNAME
      7369 SMITH      RESEARCH
      7499 ALLEN      SALES
      7521 WARD       SALES
      7566 JONES      RESEARCH
      7654 MARTIN     SALES
      7698 BLAKE      SALES
      7782 CLARK      ACCOUNTING
      7788 SCOTT      RESEARCH
      7839 KING       ACCOUNTING
      7844 TURNER     SALES
      7876 ADAMS      RESEARCH
      7900 JAMES      SALES
      7902 FORD       RESEARCH
      7934 MILLER     ACCOUNTING
14 rows selected.It's been discussed many times on the forum... my favourite here...
{message:id=1668675}
Edited by: BluShadow on 17-Sep-2012 09:22

Difference between getLocalName and getQName?

I am just wondering what's the difference between getLocalName and getQName in the Attribute interface (XML)?
Thank you!

don't cross post.
what do the javadocs tell you?
%The API javadoc isn't very helpful, if just says that they return the local name and the qualified name. For more information look at this W3C Document. It defines a qualified name as a namespace prefix and a local part.

Differences between regular and Japanese localized

Similar Messages

Maybe you are looking for