Difference between Blanket sales agreement and pricing agreement

Hi guys
I wasted hours the other day trying to get a blanket sales agreement number in the 'agreement' field on order management. Just to learn that there's two types of agreements in OM and it seems like there's some sort of overlap.
Can someone please give me a few functional tips of key indicators of when to use which.
Similarities between Blanket & Pricing agreements:
- Both can fix payment terms
- Both can have new pricing implications (set a new price other than existing pricelists)
Differences between blanket & pricing agreements:
I tried to read the manual for OM and Pricing but the pricing agreement was a bit short of a nice introduction explaining what it was. I was hoping it would read something like this: You go to your customer, you agree the following and therefore you need a pricing agreement.
Thanks!

Ah,
It struck me that hte most obvious difference is that sales agreements track the amount/qty of releases against that agreement. So the whole release process is some functionality that sales agreements can do that price agreements can not do.
So I'm wondering what can you achieve with a pricing agreement that you cannot achieve with a sales agreement?

Similar Messages

Difference between Gross sales Proceeds and Receivables

Hi
Can anyone advise diff between gross sales proceeds and Receivables in A/R.
Is gross sales proceeds is subset of Receivables?
Many Thanks.

Gross proceeds of sales" means the value proceeding or accruing from the sale of goods and/or for services rendered, without any deduction on account of the cost of property sold, the cost of materials used, labor costs, interest, discount paid, delivery costs, taxes, or any other expense whatsoever paid or accrued and without any deduction on account of losses.
while accounts receivalbes include the sales you made to a customer including cost of sales, revenues, aind all other charges you can think of for sellinf off a product to a cutomer.
Please reward points if helpfull.
Thanks

Difference between Delivery, Sales order and Shipment

Hi
I would like to know difference between sales document, delivery document and shipment.
When is the delivery created? What data will it have?

Hi
Sales Documents 
Sales-related business transactions are recorded in the system as sales documents. These are grouped into four categories:
Pre-sales documents: inquiries and quotations
Sales orders
Outline agreements, such as contracts and scheduling agreements
Customer problems and complaints, leading to free-of-charge deliveries and credit memo requests
If your particular business processes require it, you can process deliveries and billing documents directly from a sales document. In addition, some sales documents, such as cash sales and rush orders automatically trigger the creation of subsequent delivery and billing documents.
Basic Functions Within Sales Order Processing
During sales order processing, the system carries out basic functions, such as:
Monitoring sales transactions
Checking for availability
Transferring requirements to materials planning (MRP)
Delivery scheduling
Calculating pricing and taxes
Checking credit limits
Creating printed or electronically transmitted documents (confirmations and so on)
Delivery Processing
In its role as central object of the goods issue process, the outbound delivery supports all shipping activities including picking, packing, transportation and goods issue. During the outbound delivery process, shipping-planning information is recorded, status of shipping activities is monitored and data accumulated during shipping processing is documented. When the outbound delivery is created, the shipping activities, such as picking or delivery scheduling, are initiated, and data that is generated during shipping processing is included in the delivery.
Range of Functions
An outbound delivery can be created as follows:
With reference to a sales order
With reference to a stock transport order
With reference to a subcontract order
Shipping 
Shipping is an important part of the logistics chain in which guaranteed customer service and distribution planning support play major roles.
In shipping processing, all delivery procedure decisions can be made at the start of the process by
Taking into account general business agreements with your customer
Recording special material requests
Defining shipping conditions in the sales order
The result is an efficient and largely automatic shipping process in which manual changes are only necessary under certain circumstances.
Integration
The Shipping component is integrated under the Logistics Execution component. Shipping is a subsequent activity of the Sales component.
Range of Functions
The shipping module supports the following functions, which include but are not limited to:
Deadline monitoring for reference documents due for shipment (sales orders and purchase orders, for instance)
Creating and processing outbound deliveries
Planning and monitoring of worklists for shipping activities
Monitoring material availability and processing outstanding orders
Monitoring the warehouse's capacity situation
Picking (with optional link to the Warehouse Management system)
Packing deliveries
Information support for transportation planning
Support of foreign trade requirements
Printing and transmitting shipping documents
Processing goods issue
Controlling using overviews of
 o Deliveries currently in process
 o Activities that still are to be carried out
 o Possible bottlenecks

Difference between tax determination procedure and pricing procedure....

Hi,
What is the use of Tax determination procedure when we maintain tax condition types in pricing procedure.(and condition records will pick the correct tax rates).
My question is that, can we trigger an o/p tax without maintaining a tax procedure at document type level?If yes then what is the basic use of tax determination procedure in SAP?

Tax procedure is being used in the Country Version India Add-On and requires to maintain additional data in the Excise Rate Maintenance transaction, J1ID. Each of the excise duties in the tax Procedure Tax procedure has its own condition types, and each condition type is assigned to a formula in the standard SAP. This formula instructs the system to calculate the excise duty using the data that have been maintained in the Excise Rate Maintenance transaction.
FTXP for a country is determine from TAX procedure assign to the country.
[Entering content frame formula-based excise determination (LO)|http://help.sap.com/saphelp_470/helpdata/pt/e6/2adbdec6974f4c9f35d732b108d09e/content.htm]
[Formula-Based Excise Determination|http://help.sap.com/saphelp_47x200/helpdata/de/20/53bfce14ff11d4b5b1006094b9ec21/content.htm]
[Condition-Based Excise Determination|http://help.sap.com/saphelp_470/helpdata/ru/08/34bc3cdc322866e10000000a114084/content.htm]
Thanks & Regards
JP

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

"difference between sales order and scheduling agreement "

hi,
i want to know difference between sales order and scheduling agreement and where use scheduling agreement & where sales order ?
please help
amit

Hi Amit,
Its not hard to find this info at help.sap.com
Sales Order
Definition: Request from a customer to a company to deliver a defined quantity of products or provide a service at a certain time. The sales area that accepts the inquiry is responsible for completing the agreement.
Scheduling Agreements
Purpose
A customer scheduling agreement is an outline agreement with the customer containing delivery quantities and dates. These are then entered as schedule lines in a delivery schedule. You can either create schedule lines when you create the scheduling agreement or you can create them later.
You fulfill a scheduling agreement by creating the deliveries in the schedule as they become due. You process deliveries for a scheduling agreement in exactly the same way as you process a normal delivery. After you have carried out the delivery, the system updates the Delivered quantity field in the scheduling agreement item with the delivery quantity. The following graphic shows the document flow for scheduling agreements.
Integration
You would use this component if you had outline agreements with the customer that contained future delivery quantities of materials that would be sent at certain times within a fixed time period.
If you work with scheduling agreements for the component supplier industry you also need to choose the "Electronic Data Interchange" (EDI) component.

Difference between Olant sale and Depot sale

What is the basic difference between plant sale and depot sale? is there any difference with respect to their confighration part?

Hi !
With regards to your query, as per the business requirements of a company a company can have depots and plants for retail sales , and sales directly to customers from manufacturing plants.
For this there can be different codes for depots locations and plants and different storage locations respectively.
Also pricing may vary both for raw materials and FG, since manufacturing might be carried out under a contract agreement,scheduling agreement etc and retail sales may be at standard market rates.
Thus the pricing procedures would vary.
The norms for customer account groups and credit exposure would also vary.
Plz reward points if helpful.
Rgds,
Shamik.

Difference between SAP 4.7 and ECC 5.0

hi frnds
.what is the difference between SAP 4.7 and ECC 5.0?
regards

Hi,
Following are the basic differences as far as MM Module is concerned
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
Goods receipt
Goods issue
Transfer posting
Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
107: Goods receipt to valuated goods receipt blocked stock
109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with u201CNon-Hierarchyu201D display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer Between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location
Regards
Priyanka.P
AWARD IF HELPFULL

What is the difference between trade promotion management and campaign?

Hello all,
I want a clear clarification shows the difference between trade promotion management and campaign management
Regards
Jacopo Francois

Hi,
1)Campaign Management, Here Market do the Mass camapaign in the specific sales area regarding theire Products and Brands (Aware ness of new Products or rebuilding the Brand image ) by spending some Budget.
2) In Trade Promotion, Market makes the Trade agreement ( To sell the Particular Products ) with the Particular BP ( Like Distributor/Whole saler ) by giving the Trade promotional discounts, if he sells will get the TPM discount with in the planned period .
Basically Campaign is using Mass advertise and TPM is to be targetting to the Particular BP to sell theire prodcuts by offering promotional discount.
Regards
Naren..

What'z the difference between the Commercial Invoices and

What'z the difference between the Commercial Invoices and
Invoices/Excise Invoices? Also I understand that we can combine 2~3
invoices and can create one commercial invoice? If it is possible, how
to create the same?
cheers
shalsa007....

Hello,
A commercial invoice is a bill for the goods from the seller to the buyer. Commercial invoices are utilized by customs officials to determine the value of the goods in order to assess customs duties and taxes.
In general there is no standard form for a commercial invoice although they tend to contain many of the following features:
     seller's contact information
     buyer's contact information
     consignee's contact information (if it is different from the buyers)
     invoice date
     a unique invoice number
     sales terms (usually in incoterm format)
     payment terms
     currency of sale
     full quantities and description of merchandise (Generally this includes unit price and total price. Product descriptions should be consistent with the buyer's purchase order. Including the Harmonized System commodity codes can be helpful, especially in countries that are WTO members.)
Excise invoice Original for Buyer copy, whether prices are inclusive or exclusive of excise duty.
The invoice in which the Excise duties are included.
As per Indian tax system, Excise duty (16%) is payable by each manufacturing unit on the value of manufactured goods / on the value added. The manufacturing plant is supposed to submit an excise duty report on fortnightly / monthly basis. Various registers (RG1, RG23A, RG23C, PLA) are maintained for that purpose, which record all the transactions including movement of goods, cenvat credit available and cash balance available.
In SAP, we use transaction j1id for configuration and j1iin, j2i7, j1i5, j2i5, j2i6, j1ip for creating, extracting and printing excise invoice.
*Please reward if this helps**
Regards
AK

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

What is the difference between Condition Type PB00 and PBXX

Hallow all,
Can anybody please explain, What is the Difference between Condition type PB00 and PBXX in Materials Management Pricing?
And also please explain control or Application of both on Price determination ??
Thanks in Advance !!!!!

Hi,
PB00 condition type is used for automatic pricing in PO
PBXX condition type is used for manual pricing in PO
In Pricing access sequence play a vital role . If you need pricing automatic in the PO, you have use of Access Sequences and Schema Group of Vendor.You can see the difference in both standard condition type PB00 and PBXX, where as PB00 is assigned to Access sequence(0002)but in case of PBXX no access sequense assigned.
Regards,
Biju K

The differences between XI 3.0 and Xi 4.0

Could you please some one explain me the differences between XI 3.0 and Xi 4.0.
Thanks in advance
Regards,
Ranjith

Hi,
honestly, a forum is not the medium for this.
I'd recommend you read the release notes, the new/deprecated features list, and check out the online release training
all found under www.service.sap.com for which you need an S-user
else, get in touch with your SAP Account team, and request that a pre-sales consultant come and demo (sell) the solution to you.
regards,
H

Difference between SAP/APO/DP and the SAP/CRM solution for forecasting

Hi,
Can you please help me identifying the main differences between SAP/APO/DP and the SAP/CRM solution for forecasting? Advantages and disadvantages?
Thanks a lot

Hi LCD777,
Forecasting at DP & CRM are altogether at different entities. CRM involves webbased data transfer mechanism tool whereas DP is database/livecache driven tool.
In CRM, you dont get optimised solution of forecasting out of it whereas in DP you can get as much as
optimised solution & flexibility as per your requirements.
DP is majorly a forecasting tool where in huge statistical method functionalities are embedded in
whereas CRM is majorly a transactional tool wherein it involves gathering of forecast data and executing it.
Typically, CRM will be integrated with DP containing GATP environment & ECC so that DP will plan for forecast data, ECC system drives sales order data & GATP calls for availability check and finally
the forecast execution& transactions will be controlled by CRM
Regards
R. Senthil Mareeswaran.

Any real difference between a 1.83 and 2.0 MacBook Pro?

Hi all,
I have recently bought a MacBook Pro 1.83 GHz model. It was on sale at my local computer store and I thought it was a good find, as it was brand new and was selling for £1099, a £300 saving on the 2.0 GHz model. Before I start using it, I just wanted to know if anyone knew if there was a real performance difference between the two and should I have paid the extra £300 to get the 2.0 GHz machine?
I only ask this, as I know that over time Apple sometimes tweak the machine to improve it and (after talking with someone at Apple), I've been told that there have been 5 or 6 changes to the inner workings (or revisions as they called them), and I wondered if this changed the performance or if it was just minor improvements regarding heat and noise and so on.
To finish, does anyone have any speculation as if this is a good time to buy a MacBook Pro with the introduction of the Core 2 Duo chips in the new iMacs?
Many thanks.
MacBook Pro Mac OS X (10.4.7) 1.83GHz Core Duo / 512MB / 80GB

So what you are saying is that the 170 MHZ difference between the 1.83 and the 2.0 is noticeable, but the 160 MHZ difference between the 2.0 and the 2.16 is not?
I thought we were passed the marketing gimmicks and the clock speed race, but I guess not.
Clock speed doesn't tell you anything about the performance of a CPU. Intel almost ran themselves into the ground by trying to pump up their clock speeds and feeding that tripe to the masses. AMD focused on a solid architecture that created a robust chip. As a result AMD took the lead in performance and stability.
Intel's greatest achievement to date has been the PIII Coppermine. So good was this architecture that they have gone back to it. The Centrinos are based off the Coppermines as are the dual cores.
The point of the story is that clock speed means nothing. Save your cash and put it to better use by getting a 7200 rpm drive or more RAM.

Difference between Blanket sales agreement and pricing agreement

Similar Messages

Maybe you are looking for