Difference between Reboot and Shutdown in WinPE environment ???

Hi,
Whats are the difference's between Reboot and Shutdown in winpe environment ? and how it affects drivers mainly the drivers which needs to flush buffers on persistent media ? do they get chance to flush things and close gracefully ??
Thanks
Anant

Hello,
The Windows Desktop Perfmon and Diagnostic tools forum is to discuss performance monitor (perfmon), resource monitor (resmon), and task manager, focusing on HOW-TO, Errors/Problems, and usage scenarios.
Since your post is off-topic, I am moving it to the
off topic forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book:
Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Similar Messages

Difference between Reboot and Power OFF/ON

Hi Community,
in a forum a User is reporting serious problems after an update to the actual major release 10.6.5. He said if he boot the system in safe mode everything works as expected, after a reboot the same but after a power off and on again, the system is freezing after the login.
Now I'm searching for the difference between this two start methods, maybe we can isolate the problem a bit easier.
Thx & Bye Tom

Allan Eckert wrote:
If the operating system is running when the power button is used to stop the computer, this can do great harm to the disk by not allowing all of the data to be written to disk as it should be.
Yes I agree but this wasn't what I'm asking for. The question is why the system works fine as long as the User proceed a normal reboot and why it is broke after a shutdown. I don't believe that the User enforce a dirty shutdown after he boot the system in safe mode. But sure, if he boot the system after a shutdown, and the system is freezing, than he have to proceed a dirty shutdown. What else could he do?
Thx & Bye Tom

Difference between STOP and SHUTDOWN in MMC

Hi all,
When we see SAP MMC & right click the instance, we will get many options including STOP & SHUTDOWN.
Could you please tell me the difference between the two. If we click STOP, all the services like message server, dispatcher will be stopped, what will happen when we click SHUTDOWN?
Thanks & Regards,
Subbu.

difference:
STOP will stop SAP application and the database, SHUTDOWN will do OS stop.
so if we want to restart SAP then STOP, and if we want to restart/reboot OS then SHUTDOWN
SO, if you wanna stop OS , then always STOP the application and db first with option STOP and then OS stop using SHUTDOWN
Bhudev

Difference between idoc and rfc

what is the difference between idoc and rfc? when and where it is used? when there is idoc, why rfc vice versa?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model.
The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system
RFC
Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). 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.
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Differences between CAF and NWDS

Hi all,
I'm reading about CAF and I don't understand the differences between CAF and NWDS. In NWDS you can composite an aplication with services offered by other systems, so I don't understand what CAF offers.
Regards,

Hi,
CAF is a Frame work for developing Composite Applications.
CAF consists of two parts: design time and run time.
NWDS provides design time development support.Simply, NWDS is the IDE based on Eclipse.
CAF Server that is Composite Environment Server provides the run time for composite applications.
You can go through the help doc for [Composite Environment |http://help.sap.com/saphelp_nwce10/helpdata/en/45/ff9fc1d8986c06e10000000a1553f6/frameset.htm]so that you can understand easily.
Sampath

Differences between rfc and ale/idoc.

hi ..
       will u please send the differences between rfc and ale/idoc's.

Hi,
Please reward with points if helpful................
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Means of creating and operating distributed applications.
The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
Application Link Enabling comprises the following three layers:
application services
distribution services
communication services
Two Development Models
     Distribution using BAPIs
     Distribution using Message type
The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
Defining message types and IDoc types:
If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
Writing ABAP code:
         Outbound Processing
           Inbound Processing
You can find information on other ALE functions under:
                               Master Data Distribution
                              Communicating with Non-R/3 Systems
1. The Remote Function Call facility allows you to call an R/3 Function module on a remote machine.
2. To communicate between two R/3 Systems and also with an External System. External Application program also can call these function module for integration.
3. RFC or sRFC - Synchronous RFC
                 aRFC - Asynchronous RFC
                  tRFC - Transactional RFC
                  qRFC - Queued RFC (I.e. Serialization of tRFC)
Types of RFC Call
Synchronous
CALL FUNCTION Func Destination Dest
CALL FUNCTION func DESTINATION 'NONE' ...
CALL FUNCTION func DESTINATION BACK' ...
Asynchronous
CALL FUNCTION func STARTING NEW TASK taskname
PERFORMING form ON END OF TASK
RECEIVE RESULTS FROM FUNCTION func
Thanks
sivaparvathi

Differences between jdk and jre

can anybody explain the differences between jdk and jvm. and relation between jdk, jre and jvm.
thanks

Hi,
JDK- Java Development Kit contains compiler and other appliction development tools. with this tool you can compile as well as run your application
JRE-Java runtime Environment where Java applications are exceuted .You can only run your application here but you cant develop and compile.
JVM-Java Virtual Machine Its interpretor which interprets and then executes you coded after it is compile ( to byte code) by Java Compiler.

Can someone explain the difference between TIER_WEB and TIER_WEBDEV

Hi All,
We have two sets of values in Context file as below.
<TIER_ADWEB oa_var="s_isAdWeb">NO</TIER_ADWEB>
<TIER_ADFORMS oa_var="s_isAdForms">NO</TIER_ADFORMS>
<TIER_ADFORMSDEV oa_var="s_isAdFormsDev">NO</TIER_ADFORMSDEV>
<TIER_ADWEBDEV oa_var="s_isAdWebDev">NO</TIER_ADWEBDEV>
Could you explain the difference between
TIER_WEB and TIER_WEBDEV
and
TIER_ADFORMS and TIER_ADFORMSDEV

These values in a shared APPL_TOP system. Pl see ML Doc 745580.1 (Apply Patches in a Shared Application Tier File System Environment) for an explanation.Not necessarily in Shared APPL_TOP, even in traditional multi-node installation you will find these values in the application context file.
I never came across any document which describes the difference between TIER_WEBDEV and TIER_WEB, I just can say that these variables always have the same value.

Difference between BI and BW 3.5

10 basic difference between BI and BW 3.5

Hi the following documentation will be helpful to you,
Regards,
SUbha
Pls grant me points if helpful
This documentation provides you with a starting point for administration and optimal maintenance of the Enterprise Data Warehousing IT scenario. It contains business-intelligence-specific information for various tasks, lists the relevant tools and functions, and provides links to the more detailed documentation that you need to carry out the tasks.
The Enterprise Data Warehousing IT scenario supports you in setting up and managing a data warehouse in a company-wide environment. It allows you to integrate, transform, consolidate, clean up, store, and stage data of any origin (SAP and non-SAP sources), or age (historic and up-to-date), to be analyzed and interpreted. It provides flexible structures and layers so that you can react quickly to business developments. It also allows businesses to report in real time and improve the design time and runtime of BI models and processes.
For more information, see Enterprise Data Warehousing.
Administration of this IT scenario is part of the Running the Enterprise Data Warehouse scenario variant. Therefore the tasks described below refer to this scenario variant.
Integration
Enterprise Data Warehousing provides data for the following IT scenarios:
IT Scenario
Description
Information About IT Scenario Administration
Enterprise Reporting, Query and Analysis
This IT scenario shows how business experts can use the reporting and analysis tools available in SAP NetWeaver Business Intelligence (BI) to provide BI information customized for the different categories of user within your company.
Enterprise Reporting, Query, and Analysis
Business Planning and Analytical Services
This IT scenario includes processes that collect data from InfoProviders, queries, or other BI objects, convert them using various methods, and write back new information to BI objects (such as InfoObjects or DataStore objects).
Business Planning and Analytical Services
Tasks
In most cases, running an enterprise data warehouse involves general tasks for managing the Application Server for ABAP (AS ABAP) and the Application Server for Java (AS Java), as well as scenario-specific tasks. For more information, see:
●     AS ABAP (Application Server for ABAP)
●     AS Java (Application Server for Java)
●     Enterprise Data Warehousing: Preparation for EDW Processes
●     Enterprise Data Warehousing: Tasks Performed Regularly
●     Enterprise Data Warehousing: Tasks on Demand
●     Enterprise Data Warehousing: Saving and Recovering Data
For information about the general administration of BI systems, see BI (Business Intelligence).

Difference between Finsta and MT940

hi friends,
can anyone explain the difference between finsta and MT940. and how r they delivered into sap..the entire process from the bank.
cheers
charlie

Hi Charlie
FINSTA is the name of the bank statement IDOC used within SAP environment. Some banks provide FINSTA-IDOCs as well, but you should verify the specification from the bank carefully, hence some country specific informations are stored in text fields. The process code in the partner profile (WE20) is FINS. The system process the bank statements then automically based on the configuration.
MT940 is an official S.W.I.F.T. message. Hence the SWIFT specification is quite wide and open, all banks have defined an own MT940 "dialect". SAP has defined an SAP MT940 specified format as well. You should import those ASCII-Files with transaction code FF.5 and post with FEBP.
Kind regards
Simon

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.

What is the difference between tkprof and explainplan

Hi,
what is the difference between tkprof and explainplan.

Execution Plans and the EXPLAIN PLAN Statement
Before the database server can execute a SQL statement, Oracle must first parse the statement and develop an execution plan. The execution plan is a task list of sorts that decomposes a potentially complex SQL operation into a series of basic data access operations. For example, a query against the dept table might have an execution plan that consists of an index lookup on the deptno index, followed by a table access by ROWID.
The EXPLAIN PLAN statement allows you to submit a SQL statement to Oracle and have the database prepare the execution plan for the statement without actually executing it. The execution plan is made available to you in the form of rows inserted into a special table called a plan table. You may query the rows in the plan table using ordinary SELECT statements in order to see the steps of the execution plan for the statement you explained. You may keep multiple execution plans in the plan table by assigning each a unique statement_id. Or you may choose to delete the rows from the plan table after you are finished looking at the execution plan. You can also roll back an EXPLAIN PLAN statement in order to remove the execution plan from the plan table.
The EXPLAIN PLAN statement runs very quickly, even if the statement being explained is a query that might run for hours. This is because the statement is simply parsed and its execution plan saved into the plan table. The actual statement is never executed by EXPLAIN PLAN. Along these same lines, if the statement being explained includes bind variables, the variables never need to actually be bound. The values that would be bound are not relevant since the statement is not actually executed.
You don’t need any special system privileges in order to use the EXPLAIN PLAN statement. However, you do need to have INSERT privileges on the plan table, and you must have sufficient privileges to execute the statement you are trying to explain. The one difference is that in order to explain a statement that involves views, you must have privileges on all of the tables that make up the view. If you don’t, you’ll get an “ORA-01039: insufficient privileges on underlying objects of the view” error.
The columns that make up the plan table are as follows:
Name Null? Type
STATEMENT_ID VARCHAR2(30)
TIMESTAMP DATE
REMARKS VARCHAR2(80)
OPERATION VARCHAR2(30)
OPTIONS VARCHAR2(30)
OBJECT_NODE VARCHAR2(128)
OBJECT_OWNER VARCHAR2(30)
OBJECT_NAME VARCHAR2(30)
OBJECT_INSTANCE NUMBER(38)
OBJECT_TYPE VARCHAR2(30)
OPTIMIZER VARCHAR2(255)
SEARCH_COLUMNS NUMBER
ID NUMBER(38)
PARENT_ID NUMBER(38)
POSITION NUMBER(38)
COST NUMBER(38)
CARDINALITY NUMBER(38)
BYTES NUMBER(38)
OTHER_TAG VARCHAR2(255)
PARTITION_START VARCHAR2(255)
PARTITION_STOP VARCHAR2(255)
PARTITION_ID NUMBER(38)
OTHER LONG
DISTRIBUTION VARCHAR2(30)
There are other ways to view execution plans besides issuing the EXPLAIN PLAN statement and querying the plan table. SQL*Plus can automatically display an execution plan after each statement is executed. Also, there are many GUI tools available that allow you to click on a SQL statement in the shared pool and view its execution plan. In addition, TKPROF can optionally include execution plans in its reports as well.
Trace Files and the TKPROF Utility
TKPROF is a utility that you invoke at the operating system level in order to analyze SQL trace files and generate reports that present the trace information in a readable form. Although the details of how you invoke TKPROF vary from one platform to the next, Oracle Corporation provides TKPROF with all releases of the database and the basic functionality is the same on all platforms.
The term trace file may be a bit confusing. More recent releases of the database offer a product called Oracle Trace Collection Services. Also, Net8 is capable of generating trace files. SQL trace files are entirely different. SQL trace is a facility that you enable or disable for individual database sessions or for the entire instance as a whole. When SQL trace is enabled for a database session, the Oracle server process handling that session writes detailed information about all database calls and operations to a trace file. Special database events may be set in order to cause Oracle to write even more specific information—such as the values of bind variables—into the trace file.
SQL trace files are text files that, strictly speaking, are human readable. However, they are extremely verbose, repetitive, and cryptic. For example, if an application opens a cursor and fetches 1000 rows from the cursor one row at a time, there will be over 1000 separate entries in the trace file.
TKPROF is a program that you invoke at the operating system command prompt in order to reformat the trace file into a format that is much easier to comprehend. Each SQL statement is displayed in the report, along with counts of how many times it was parsed, executed, and fetched. CPU time, elapsed time, logical reads, physical reads, and rows processed are also reported, along with information about recursion level and misses in the library cache. TKPROF can also optionally include the execution plan for each SQL statement in the report, along with counts of how many rows were processed at each step of the execution plan.
The SQL statements can be listed in a TKPROF report in the order of how much resource they used, if desired. Also, recursive SQL statements issued by the SYS user to manage the data dictionary can be included or excluded, and TKPROF can write SQL statements from the traced session into a spool file.
How EXPLAIN PLAN and TKPROF Aid in the Application Tuning Process
EXPLAIN PLAN and TKPROF are valuable tools in the tuning process. Tuning at the application level typically yields the most dramatic results, and these two tools can help with the tuning in many different ways.
EXPLAIN PLAN and TKPROF allow you to proactively tune an application while it is in development. It is relatively easy to enable SQL trace, run an application in a test environment, run TKPROF on the trace file, and review the output to determine if application or schema changes are called for. EXPLAIN PLAN is handy for evaluating individual SQL statements.
By reviewing execution plans, you can also validate the scalability of an application. If the database operations are dependent upon full table scans of tables that could grow quite large, then there may be scalability problems ahead. On the other hand, if large tables are accessed via selective indexes, then scalability may not be a problem.
EXPLAIN PLAN and TKPROF may also be used in an existing production environment in order to zero in on resource intensive operations and get insights into how the code may be optimized. TKPROF can further be used to quantify the resources required by specific database operations or application functions.
EXPLAIN PLAN is also handy for estimating resource requirements in advance. Suppose you have an ad hoc reporting request against a very large database. Running queries through EXPLAIN PLAN will let you determine in advance if the queries are feasible or if they will be resource intensive and will take unacceptably long to run.

What's the difference between trace and log in XI?

Hi all,
On both J2EE and ABAP, there are both tracing and logging functionalities. Can anyone explain me the difference between trace and logging?
Regards,
Hui

From SAP Notes
Log file:
A log file contains generally intelligible information for system administrators. The information is sorted by categories and is used for system monitoring. Problem sources or critical information about the status of the system are logged in this file. If error messages occur, you can determine the software component that has caused the error using the location. If the log message does not provide enough details to eliminate the problem, you can find more detailed information about the error in the trace file.
The log file is located in the file system under
"/usr/sap/[SID]/[instance]/j2ee/cluster/server[N]/log/applications.[n].log" for every N server node.
Access the file with the log viewer service of the J2EE visual administrator or with the standalone log viewer.
Trace file:
A trace file contains detailed information for developers. This information can be very cryptic and extensive. It is sorted by location, which means by software packages in the Java environment, for example, "com.sap.aii.af". The trace file is used to analyze runtime errors. By setting a specific trace level for specific locations, you can analyze the behavior of individual code segments on class and method level. The file should be analyzed by SAP developers or experienced administrators.
The trace file is located in the file system under
"/usr/sap/[SID]/[instance]/j2ee/cluster/server[N]/log/defaultTrace.[x].trc" for each N server node.
Access the file with the log viewer service of the J2EE visual administrator or with the standalone log viewer.
Regards,
Prateek

Whats the difference between ALL and FIRST in Multi Inserting

SQL> Drop Table Sales;
Table dropped.
SQL> Drop Table Accounts;
Table dropped.
SQL> Drop Table Research;
Table dropped.
SQL> Create Table Sales As Select * From Emp;
Table created.
SQL> Create Table Accounts As Select * From Emp;
Table created.
SQL> Create Table Research As Select * From Emp;
Table created.
SQL> Truncate Table Sales;
Table truncated.
SQL> Truncate Table Accounts;
Table truncated.
SQL> Truncate Table Research;
Table truncated.
SQL> Select * From Sales;
no rows selected
SQL> Select * From Accounts;
no rows selected
SQL> Select * From Research;
no rows selected
SQL> Insert All
2 When Deptno=10 Then
3 Into Sales (Empno,Ename,Job,Mgr,Hiredate,Sal,Comm,DeptNo)
4 When Deptno=20 Then
5 Into Accounts (Empno,Ename,Job,Mgr,Hiredate,Sal,Comm,DeptNo)
6 When Deptno=30 Then
7 Into Research (Empno,Ename,Job,Mgr,Hiredate,Sal,Comm,DeptNo)
8 Select * From Emp
9 .
SQL> /
16 rows created.
SQL> Select * From Sales;
    EMPNO ENAME      JOB             MGR HIREDATE        SAL      COMM    DEPTNO
     7782 CLARK      MANAGER        7839 09-JUN-81       100                  10
     7839 KING       PRESIDENT           17-NOV-81       100                  10
     7934 MILLER     CLERK          7782 23-JAN-82       100                  10
     7999 ABCDEFGH   JOB            7839 09-FEB-06       100         0        10
4 rows selected.
SQL> Select * From Accounts;
    EMPNO ENAME      JOB             MGR HIREDATE        SAL      COMM    DEPTNO
     7901 SMITH      CLERK          7902 17-DEC-80       100                  20
     7566 JONES      MANAGER        7839 02-APR-81       100                  20
     7788 SCOTT      ANALYST        7566 19-APR-87       100                  20
     7876 ADAMS      CLERK          7788 23-MAY-87       100                  20
     7902 FORD       ANALYST        7566 03-DEC-81       100                  20
      123                                                                     20
6 rows selected.
SQL> Select * From Research;
    EMPNO ENAME      JOB             MGR HIREDATE        SAL      COMM    DEPTNO
     7499 ALLEN      SALESMAN       7698 20-FEB-81       100       300        30
     7521 WARD       SALESMAN       7698 22-FEB-81       100       500        30
     7654 MARTIN     SALESMAN       7698 28-SEP-81       100      1400        30
     7698 BLAKE      MANAGER        7839 01-MAY-81       100                  30
     7844 TURNER     SALESMAN       7698 08-SEP-81       100         0        30
     7900 JAMES      MANAGER        7698 03-DEC-81       100                  30
6 rows selected.
SQL> Truncate Table Sales;
Table truncated.
SQL> Truncate Table Accounts;
Table truncated.
SQL> Truncate Table Research;
Table truncated.
SQL> Insert First
2 When Deptno=10 Then
3 Into Sales (Empno,Ename,Job,Mgr,Hiredate,Sal,Comm,DeptNo)
4 When Deptno=20 Then
5 Into Accounts (Empno,Ename,Job,Mgr,Hiredate,Sal,Comm,DeptNo)
6 When Deptno=30 Then
7 Into Research (Empno,Ename,Job,Mgr,Hiredate,Sal,Comm,DeptNo)
8 Select * From Emp
9 /
16 rows created.
SQL> Select * From Sales;
    EMPNO ENAME      JOB             MGR HIREDATE        SAL      COMM    DEPTNO
     7782 CLARK      MANAGER        7839 09-JUN-81       100                  10
     7839 KING       PRESIDENT           17-NOV-81       100                  10
     7934 MILLER     CLERK          7782 23-JAN-82       100                  10
     7999 ABCDEFGH   JOB            7839 09-FEB-06       100         0        10
4 rows selected.
SQL> Select * From Accounts;
    EMPNO ENAME      JOB             MGR HIREDATE        SAL      COMM    DEPTNO
     7901 SMITH      CLERK          7902 17-DEC-80       100                  20
     7566 JONES      MANAGER        7839 02-APR-81       100                  20
     7788 SCOTT      ANALYST        7566 19-APR-87       100                  20
     7876 ADAMS      CLERK          7788 23-MAY-87       100                  20
     7902 FORD       ANALYST        7566 03-DEC-81       100                  20
      123                                                                     20
6 rows selected.
SQL> Select * From Research;
    EMPNO ENAME      JOB             MGR HIREDATE        SAL      COMM    DEPTNO
     7499 ALLEN      SALESMAN       7698 20-FEB-81       100       300        30
     7521 WARD       SALESMAN       7698 22-FEB-81       100       500        30
     7654 MARTIN     SALESMAN       7698 28-SEP-81       100      1400        30
     7698 BLAKE      MANAGER        7839 01-MAY-81       100                  30
     7844 TURNER     SALESMAN       7698 08-SEP-81       100         0        30
     7900 JAMES      MANAGER        7698 03-DEC-81       100                  30
6 rows selected.Both inserting insert the same records then whats the difference between ALL and FIRST clause in multi insert DML
Khurram Siddiqui
[email protected]

Hello
From the docs:
ALL
If you specify ALL, then Oracle evaluates each WHEN clause regardless of the results of the evaluation of any other WHEN clause. For each WHEN clause whose condition evaluates to true, Oracle executes the corresponding INTO clause list.
FIRST
If you specify FIRST, then Oracle evaluates each WHEN clause in the order in which it appears in the statement. For the first WHEN clause that evaluates to true, Oracle executes the corresponding INTO clause and skips subsequent WHEN clauses for the given row.
ELSE clause
For a given row, if no WHEN clause evaluates to true:
* If you have specified an ELSE clause, then Oracle executes the INTO clause list associated with the ELSE clause.
* If you did not specify an else clause, then Oracle takes no action for that row.
See Also:
"Multitable Inserts: Examples"
Restrictions on Multitable Inserts
* You can perform multitable inserts only on tables, not on views or materialized views.
* You cannot perform a multitable insert into a remote table.
* You cannot specify a table collection expression when performing a multitable insert.
* In a multitable insert, all of the insert_into_clauses cannot combine to specify more than 999 target columns.
* Multitable inserts are not parallelized in a Real Application Clusters environment, or if any target table is index organized, or if any target table has a bitmap index defined on it.
* Plan stability is not supported for multitable insert statements.
* The subquery of the multitable insert statement cannot use a sequence.
So given this the following example shows the difference:
SQL> CREATE TABLE dt_test_insert_base as select rownum id from dba_objects where rownum <=20
2 /
Table created.
SQL> CREATE TABLE dt_test_insert_1 (id number)
2 /
Table created.
SQL> CREATE TABLE dt_test_insert_2 (id number)
2 /
Table created.
SQL>
SQL> INSERT ALL
2     WHEN rownum <=15 THEN
3             INTO dt_test_insert_1 (id)
4     WHEN rownum >=10 THEN
5             INTO dt_test_insert_2 (id)
6 SELECT
7     ID
8 FROM
9     dt_test_insert_base
10 /
26 rows created.
SQL>
SQL> SELECT * from dt_test_insert_1
2 /
        ID
         1
         2
         3
         4
         5
         6
         7
         8
         9
        10
        11
        12
        13
        14
        15
15 rows selected.
SQL> SELECT * from dt_test_insert_2
2 /
        ID
        10
        11
        12
        13
        14
        15
        16
        17
        18
        19
        20
11 rows selected.
SQL>
SQL> TRUNCATE TABLE dt_test_insert_1
2 /
Table truncated.
SQL> TRUNCATE TABLE dt_test_insert_2
2 /
Table truncated.
SQL>
SQL> INSERT FIRST
2     WHEN rownum <=15 THEN
3             INTO dt_test_insert_1 (id)
4     WHEN rownum >=10 THEN --This condition is ignored until the value of id is > 15
5             INTO dt_test_insert_2 (id)
6 SELECT
7     ID
8 FROM
9     dt_test_insert_base
10 /
20 rows created.
SQL> SELECT * from dt_test_insert_1
2 /
        ID
         1
         2
         3
         4
         5
         6
         7
         8
         9
        10
        11
        12
        13
        14
        15
15 rows selected.
SQL> SELECT * from dt_test_insert_2
2 /
        ID
        16
        17
        18
        19
        20HTH
David

Difference between configurable and non configurable finished goods master

Hi
Pl explain the difference between configurable and non configurable finished goods master data.
Thanks
kamala

Hi,
Configurable material are used when you have a large number of combination of parts that go into a product. It means different combinations of the parts for same material. If you maintain a unique material code for each combination , you require a large number of material numbers. KMAT is used in such a case where you maintain just one generic product code. You assign class to this material having all variant characteristics.
A super BOM is maintained for such a material consisting of all possible alternatives. A super routing is also maintained consisting of all possible operations that could be used.
Typically configurable material is used in Made To Order (MTO) environment. However frequently ordered configurations may be planned with a material variant which needs to have a material master record. Thus Material variants may have stock and value. Depending upon characteristic values chosen at sales order entry Sales Order BOM is created. Routing operations are also chosen depending upon which BOM components are assigned to them.
Non configurable materials are like finish, semi finish materials having fixed BOM. A separate/single BOM exits for every finish material.
Revert back for more info.
thanks and regards,
Man

Difference between Reboot and Shutdown in WinPE environment ???

Similar Messages

Maybe you are looking for