What is difference between cash sale & rush order

what is difference between cash sale & rush order

Hi Prasanta,
{Reward points if you feel this is a satisfactory explanation}
Cash Sales:
In this type of order CS, as soon as you save the sales order the delivery is automatically created as same date and billing will also be generated at the same date as soon as you save the delivery document.
In a rush order, the customer picks up the goods immediately, or you deliver them on the same day as when the order was created. When you save the rush order, a delivery is automatically created in the standard system. Billing the rush order takes place as normal, after the delivery.
In the standard system, sales document type RO is saved for rush orders with immediate delivery type LF. Once the goods have been removed from storage, the goods are picked, and goods issue is posted. Once the billing documents are created (for example, in collective processing), invoice papers are printed and sent to the customer.
Rush Order:
In this type of Order RO , The delivery will be created as soon as you save the sales order. But you bill the customer later.
In cash sales, you can process an order for when the customer orders the goods, picks them up, and pays for them immediately. The delivery is processed at the same time as when the order is created and a cash invoice is printed immediately: billing is therefore related to the order, unlike rush and standard orders. Receivables are not created for the customer, as they are for rush and standard orders because the amount in the invoice is immediately posted to a cash account.
In the standard system, sales document type BV (CS) is saved for cash sales with immediate delivery type BV.
When the sales employee creates a cash sale, the system automatically proposes the current date as the date for delivery and billing. Once the order has been posted, a delivery with type BV is created immediately in the background and the system prints a document that is used as an invoice for the customer. The invoice papers are controlled with output type RD03, contained in the output determination procedure for order type CS.
This is a brief description that i have it with me...
Regards
AK

Similar Messages

Difference Between Cash Sale & Rush Order?

Hi.
What is the Difference between Cash Sale & Rush Order?Since both has immediate delivery ticked.
Regards,
Amol

Search the forum before posting such basic questions. Check these threads
[cash sale rush order |cash sale rush order]
[what is difference between cash sale & rush order |what is difference between cash sale & rush order]
thanks
G. Lakshmipathi

Difference Between Cahs Sales, Rush Order and Standard Order

Hi gurus,
I want to know whole configration for rush order and difference between 1. Rush order and cash sales. 2. cash sales and standard order.
Would u please help me for this...
Regards
Prashant.

Hi,
1) Cash sale : in this delivery automatically happen when you save the sales order. After that you have to give an invoice to the customer.
2) Rush order. Here also delivery automatically happen when you save the sales order. But the difference is you can send invoice after some time but the delivery should happen immidately.
If you goto any super market first, you pick up the item and then pay the bill and then you will get the bill, this process is cash sales.
Cash sales is order related billing whereas RO is delivery related.
Cash sales is not relevant for availability check as you will be picking the goods whereas RO is relevant for availability check.
Cash sales is also not relevant for credit management whereas RO is relevant credit management.
Cash sales uses RD03 as output which immediately prints the invoice whereas RO uses standard output RD00.
Cash sales has one time customer account group where as RO normally doesn't.
For cash sales order type is BV or CS and for RO it is RO
Cash sales triggers petty cash a/c where as in RO customers account is debited.
Delivery and settlement will be done immediately in cash sales where as in RO only delivery will be done immediatrly.
Rush Order/Cash Sales u2013
Rush orders and Cash sales are sales document types that are used in the sales from plant process or when the customer needs to pick their goods immediately from the warehouse.
In the sales document type, the following changes have to be made for rush order/cash sales u2013
a. order type u2013 RO/CS
b. shipping conditions u2013 immediately
c. immediate delivery u2013 X
d. lead time in days u2013 not to be specified
e. delivery type u2013 LF/BV
f. billing type u2013 F2/BV
g. item category u2013 TAN/BVN
h. schedule line category u2013 CP/CP
In case of rush orders and cash sales once the goods have been withdrawn from the warehouse, picking and posting goods issue can begin.
In case of rush orders, when you create the billing documents the system prints the invoice papers and sends them to the customer.
But in case of cash sales, an order related billing index is generated automatically. This updates the billing due list. Billing type BV is created, while the billing due list is being processed and the system does not print invoices during billing for a cash sale.
In cash sales when you save the order, the system automatically generates a cash receipt that can be given to the customer as an invoice and the goods are picked up from the warehouse immediately by the customer. You control the output with output type RD03, contained in the output determination procedure for order type CS.
Best Regards,
Amit

Cash Sale & Rush Order sale

Can anybody tell me how to perform the whole "CASH SALE" & "RUSH ORDER" process in sap step-by-step with proper transaction codes?
Edited by: Anil789 on Nov 18, 2010 1:27 AM

Please check the below thread:
Cash sales and Rush order
As for the transactions all follow the same cycle, order delivery and invoice. so VA01, VL01N and VF01
Thanks
Indranil

Error in cash sales / rush order process

Hi
i have created cash sales and rush order as delivery being created immediately but in my case its not creating i have done config i.e checked th box for immediate delivery but still getting error kindly help where am doing mistake .when am trying to do delivery separately in vl01n its giving error Copying is not poss.because an entry is missing in Table TVCPL: MSCS MVBV
Edited by: mukesh kumar on Mar 22, 2009 4:41 PM

Hi Mukesh
In t code VTLA copy control keys are missing to create delivery
Hence the error
Cash sale order type BV (if ECC 6.0) or CS if previous versions the delivery type is BV and the item category is BVN
In VTLA between BV order type to BV delivery type heder level controls have to be defined
At item level for the item category BVN controls have to be defined
Rush order type ROand the delivery type is LFand the item category is TAN
In VTLA between RO order type to LF delivery type heder level controls have to be defined
At item level for the item category TAN controls have to be defined
Then check your OVL2 settings also whether shipping point determination are properly maintained
Normally for cash sales order type SHIPPING CONDITIONS are maintained at order type in VOV8
For this SHIPPING CONDITIONS combination have you maintained proper shipping point determination in OVL2
This also please check
Normally in most of the cases SHIPPING CONDITIONS are maintained in Customer Master not in order types
But for Cash sale SHIPPING CONDITIONS are maintained in its order type in VOV8
If SHIPPING CONDITIONS are maintained order type in VOV8 then it has preference over what is maintained in customer master
Regards
Raja

Cash sale & rush order

Hi
No taxes on sales/purchase allowed for account 900030 1000, S3 is not allowed
Message no. FS217
1000 is my sales org
s3 is my tax code i have account 251050
where system is picking 900030
system time i am executing bv and so document in my system.
aditya

Go to T.Code: FS00 & enter G/L account 900030 & Company Code 1000, Enter in change mode à go to Control Data & maintain * in the field Tax category.
This should resolve your error.
Regards,
Rajesh Banka
Reward points if helpful.

What is the difference between a sales return or RMA ?

Please explain or give a link or documentation which explains the difference between a sales return and RMA.
thanks in advance,
hun

Hi Paul,
The link is very good. thank you very much for that.
Please correct me if my understanding of the link you send is wrong.
following is my understanding..
RMA is created for product/products that is / are sales retruns as well as for repair (complaint is created in case there is no need of a repair or sales return).
I also would like to know which module of R/3 handles the RMA process?
Whether it is S.D. or Service Management.
Suppose if there is no CRM and only R/3 is there. RMA is to be created is it handled in R/3 service mangement? Is it not possible to handle the Returns in S.D. only (suppose when we do not have a service center) by creating a return orderin R/3 S.D.. Please also tell me what is the difference between a return order and RMA?
thank you

Whats the difference between data in customer data management dashbord and customers under sales?

Hi,
In the navigator>sales i have a menu customers, there i can see accounts (customers) and contacts, however in the navigator>Customer data management under menu Customer data management dashboard i have organizations and persons. Whats the difference between the information shown in one place and in the other? Why is the information shown with different names in different menus?
thanks

Hi, The present project has the requirement to Delete the data from Sales Force objects.Have following set up: 1. Parent Objects2. Child Objects3. Cloud Data Synchronization tasks to delete these objects Parent and Child have LOOKUP relationships between them.Deleing data from Child objects did not give any error. Tried 2 scenarios to delete data from Parent object: Scenario 1: Tried to delete to data from PARENT first before deleting CHILD. Result: Failed Scenario 2: Tried to delete to data from PARENT after deleting CHILD. Result: Failed Error mesge received in both cases: "Error loading into target [SF_Object] : Error received from salesforce.com. Fields []. Status code [DUPLICATE_COMM_NICKNAME]. Message [Too many records to cascade delete or set null]." Kindly help to resolve this error and suggest a method to delete data from PARENT salesforce objects. Please feel free to ask for more inputs, if required.

What is difference between u2018credit exposureu2019 and u2018credit limitu2019?

Hi
What is difference between u2018credit exposureu2019 and u2018credit limitu2019?
What transaction I can used for to see these tow information?
best regard
francoise

Credit exposure is total AR and open sales values. Credit limit is used for block sales documents if the total exposure will exceed the credit limit. For Example:
Credit Limit : 600
   Open AR ( Customer Balance) : 100
   Customer Open Orders (Order Quantity have been confirmed, but no delivery document is created) : 100
   Open Delivery (Delivery has been created, but no billing ) : 100
   Open Billing (Billing is created, but has not release to Financial Accounting): 100
So far, the credit exposure is 400. If a new sales order is coming with value of 260, the sales order will be blocked, but the credit exposure is still 400.
Then if someone release the new sales order , then the credit exposure is 660.
Hope this is useful for you.
Flex Yang

What is difference between Reconciliation Account and Revenue account.?`

What is difference between Reconciliation Account and Revenue account.?
Where does it effects after a sales order , delivery doc. or billing doc.?

Hello Mukesh the comments givan by Amol and Siva kumar are correct.
Here I am telling you how these accouts arer wrking in sales order and at billing and delivery.
Our reconsilation account is reconsile with customer that why when you create the sales order you are mentioning the customer at this time reconsiation account works.
Whenever you doing any posting there is an accounting entry is mae in accounts book right .
At the time of Delivery and billing both the accounts are affected as per the accounting rule .
I hpoe this will you help you
Regards
ravi

What are differences between the target tablespace and the source tablespac

The IMPDP command create so manay errors. But the EXAMPLE tablespace is transported to the target database successfully. It seems that the transported tablespace is no difference with the source tablespace.
Why create so many errors?
How to avoid these errors?
What are differences between the target tablespace and the source tablespace?
Is this datapump action really successfull?
Thw following is the log output:
[oracle@hostp ~]$ impdp system/oracle dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Import: Release 10.2.0.1.0 - Production on Sunday, 28 September, 2008 18:08:31
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Master table "SYSTEM"."SYS_IMPORT_TABLESPACE_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_TABLESPACE_01": system/******** dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Processing object type TABLE_EXPORT/TABLE/TABLE
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "OE"."CUSTOMERS" ("CUSTOMER_ID" NUMBER(6,0), "CUST_FIRST_NAME" VARCHAR2(20) CONSTRAINT "CUST_FNAME_NN" NOT NULL ENABLE, "CUST_LAST_NAME" VARCHAR2(20) CONSTRAINT "CUST_LNAME_NN" NOT NULL ENABLE, "CUST_ADDRESS" "OE"."CUST_ADDRESS_TYP" , "PHONE_NUMBERS" "OE"."PHONE_LIST_TYP" , "NLS_LANGUAGE" VARCHAR2(3), "NLS_TERRITORY" VARCHAR2(30), "CREDIT_LIMIT" NUMBER(9,2), "CUST_EMAIL" VARCHAR2(30), "ACCOUNT_MGR_ID" NU
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "IX"."ORDERS_QUEUETABLE" ("Q_NAME" VARCHAR2(30), "MSGID" RAW(16), "CORRID" VARCHAR2(128), "PRIORITY" NUMBER, "STATE" NUMBER, "DELAY" TIMESTAMP (6), "EXPIRATION" NUMBER, "TIME_MANAGER_INFO" TIMESTAMP (6), "LOCAL_ORDER_NO" NUMBER, "CHAIN_NO" NUMBER, "CSCN" NUMBER, "DSCN" NUMBER, "ENQ_TIME" TIMESTAMP (6), "ENQ_UID" VARCHAR2(30), "ENQ_TID" VARCHAR2(30), "DEQ_TIME" TIMESTAMP (6), "DEQ_UID" VARCHAR2(30), "DEQ_
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "SH"."CUSTOMERS" 9.850 MB 55500 rows
. . imported "SH"."SUPPLEMENTARY_DEMOGRAPHICS" 695.9 KB 4500 rows
. . imported "OE"."PRODUCT_DESCRIPTIONS" 2.379 MB 8640 rows
. . imported "SH"."SALES":"SALES_Q4_2001" 2.257 MB 69749 rows
. . imported "SH"."SALES":"SALES_Q1_1999" 2.070 MB 64186 rows
. . imported "SH"."SALES":"SALES_Q3_2001" 2.129 MB 65769 rows
. . imported "SH"."SALES":"SALES_Q1_2000" 2.011 MB 62197 rows
. . imported "SH"."SALES":"SALES_Q1_2001" 1.964 MB 60608 rows
. . imported "SH"."SALES":"SALES_Q2_2001" 2.050 MB 63292 rows
. . imported "SH"."SALES":"SALES_Q3_1999" 2.166 MB 67138 rows
Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "EXAM_03"
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_LNAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_EMAIL_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"PM"."PRINTMEDIA_PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_CREDIT_LIMIT_MAX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_ID_MIN" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"PM"."PRINTMEDIA__PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type CONSTRAINT:"IX"."SYS_C005192" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUSTOMERS_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_LNAME_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_EMAIL_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"PM"."PRINTMEDIA_PK" creation failed
Processing object type TABLE_EXPORT/TABLE/COMMENT
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39112: Dependent object type REF_CONSTRAINT:"OE"."CUSTOMERS_ACCOUNT_MANAGER_FK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39083: Object type REF_CONSTRAINT failed to create with error:
ORA-00942: table or view does not exist
Failing sql is:
ALTER TABLE "OE"."ORDERS" ADD CONSTRAINT "ORDERS_CUSTOMER_ID_FK" FOREIGN KEY ("CUSTOMER_ID") REFERENCES "OE"."CUSTOMERS" ("CUSTOMER_ID") ON DELETE SET NULL ENABLE
ORA-39112: Dependent object type REF_CONSTRAINT:"PM"."PRINTMEDIA_FK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/TRIGGER
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
Processing object type TABLE_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUST_UPPER_NAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_UPPER_NAME_IX" creation failed
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCACT_INSTANCE
ORA-39112: Dependent object type PROCACT_INSTANCE skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39083: Object type PROCACT_INSTANCE failed to create with error:
ORA-01403: no data found
ORA-01403: no data found
Failing sql is:
BEGIN
SYS.DBMS_AQ_IMP_INTERNAL.IMPORT_SIGNATURE_TABLE('AQ$_ORDERS_QUEUETABLE_G');COMMIT; END;
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCDEPOBJ
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_V" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_N" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_R" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_E" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Job "SYSTEM"."SYS_IMPORT_TABLESPACE_01" completed with 63 error(s) at 18:09:14

Short of trying to then reverse-engineer the objects that are in the dump file (I believe Data Pump export files contain some XML representations of DDL in addition to various binary bits, making it potentially possible to try to scan the dump file for the object definitions), I would tend to assume that the export didn't include those type definitions.
Since it looks like you're trying to set up the sample schemas, is there a reason that you wouldn't just run the sample schema setup scripts on the destination database? Why are you using Data Pump in the first place?
Justin

Difference between delivery related and order related billing

Hello Friends,
Kindly explain the difference between delivery related and order related billing with an example. Thanks

The billing relevance is controlled by item category of material, which u have assigned to sales document type.
For example
1.item category TAN
Billing relevance is A- Standard-Delivery-related billing document
So in standard order of material which has to get delivered, we will bill it on its delivery. So billing relevance is delivery related billing.
2.BVN
In cash sales item category is BVN whose billing relevance is Relevant for order-related billing - status acc.to order qty.
So here we will bill the customer from sales order only, no need to go to delivery.
DONT FORGT TO REWARD POINTS IF THIS ANSWER SATISFIES YOU.
Thanks
Tushar
SAP SD, SAP BI
09822984340

What is difference between cross divison & normal division in sd

what is difference between cross divison & normal division in sd,....

generally used for sharing of condition record -division-00
in img we will maintain say for div 10 ref div 00
div 12 ref div is 00
that means we are maintaining condition record for 00 and these are also valid for div 10 and 12
cross div - another concept.--
all sales doc (ex.sales order) are created with in one sales area , in case the material ordered by sold to party belongs to diff div of sales area , then how sysytem respond i.e it should accept that material or not.
if we set cross divvion in sales doc config then in sales order system accept material other than sales area div of order. i.e we can enter material belongs to diff div in order. for that we have activate item division in VOV8

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

In mail, what is difference between deleted and discarded mail

In settings, mail, what is difference between deleted mail and discarded mail? My google account on iPad does not remove mail that I have deleted from account using other devices. My other devices and google accounts don't have this issue. I've checked settings for account and can not isolate the cause. I'm considering deleting account from iPad and then adding it back in to see if that removes the 1000+ emails that have accumulated. I don't usually use iPad for email which is why they are mostly unread on iPad.

this might help to understand
Collection Classes
Often we have to deal with a set or group of objects, or values. Collection Classes are important structures that have a number of methods that allow objects to be added, retrieved, or removed from such collections.
Objects can be grouped in a collection like sets, lists, stacks, or queues.
A set is an unordered collection of elements, from which any item may be removed.
A list is an ordered collection of elements, from which any item may be removed.
A stack is a restrictive form of list that obeys a last-in-first-out (LIFO) rule.
e.g.     a stack of plates stored after being washed, then used again.
A queue is also a restrictive form of list that obeys a first-in-first-out (FIFO) rule.
e.g.     a queue at a bus-stop, where the first bus to join the queue is the first one to leave.
An important Java Collection class is the Vector class:
     java.util.Vector
This vector class is a simple list of objects, which can be referenced by an index starting from 0 (similar to arrays). The components of a vector must be objects.
i.e. Vector: object0 object1 object2�lastObject .. spare
capacity                         ( size - 1)
So, a vector can grow as more objects are added. The size of a vector is how many objects are in the vector. The capacity is how many objects can be stored in the vector before it needs to expand again. When it needs to expand it normally doubles its capacity. The default capacity is 10.
e.g.     Vector v1;          // declare v1 as a Vector object
     v1 = new Vector();     // create a Vector instance

What is difference between cash sale & rush order

Similar Messages

Maybe you are looking for