Incoterms in Quotation

Hi Experts:
System will auto input incoterms base on sold-to party when a quotation is created.
Can the setting be changed to base on ship-to party ??
Shwan

Hi there,
Incoterms are stored in VBKD business data table.
In quotation creation include SAPMV45A, it calls incoterms from VBKD-INCO1. If you want your incoterms to come from ship-to, then you need to read the VBPA table 1st, then go to PARVW = WE (ship-to). Then read the INCO1 in billing view.
Looks like its not a good idea to put this logic.
Basically why do you want to default incoterms from ship-to?
Defintion of incoterms is Incoterms specify certain internationally recognised procedures that the shipper and the receiving party must follow for the shipping transaction to be successfully completed. You do business with Sold-to. Not the ship-to.
Regards,
Sivanand

Similar Messages

Incoterms and TOP

Dear Sirs,
                  I need to remove or if possible make Incoterms and terms of payment non mandatory in the quotation and sales order how do i go about the same.. I would not like to use OVA2 ............I think SHD0 can be used here but I am not aware of how to go abt it ......could you also plsss tell me the efffect (SHD0) it will have in the system if changes are made.
Thank you for your time
Regards
Maddy

Making changes in quotation is okay but it is not advisable to have the same changes in sale order.   Still if you want to go for it, you can search the forum for transaction variants where lot of suggestions were given on this topic. Check one such thread
[SHD0    |SHD0]
thanks
G. Lakshmipathi

Print Freight Terms on quotation form

Hi ,
Customer requirement -Print Freight Terms on quotation form. Freight terms are Pre paid , Pre paid and Add, Collect, 3rd party.
How I can do this functionality, please help me in this business scenario.
Thanks,
vmr

Dear Malla readdy,
Incoterms will be maintained in customer master sales area data section inbilling view.
Here you maintain the Incoterms.If incoterms are not visible in your customer master, it might be in supress mode so make it optional in (OBD2).
Inco terms will be stored in KNVV - INC01
So co-ordinate with the technical consultant in order to fetch the data to out put form
Please revert if you have any further clarifications
Thanks&Regards
Raghu.k

Incoterms on RFQ

Dear All,
i have set incoterm in vendor master record, while using that vendor on RFQ creation i need to change the Incoterm.
System does not show incoterm on RFQ.
why and how i can do that.
Cheers

Hi,
Inco terms from vendor master will not automatically flow in RFQ.
you have to enter this manually only
Even in ME47 while maintaining the quotation it will not update
Regards
Ganesh

Error while creating a Quotation in dp81 with simulation

hi Guys,
My client has a simulation for an operative project. First a quotation was created through sales pricing in dp81. its rejected. now he wants to create another quotation with simulation. when the inputs are given its gives error as " The reference has already been completely copied or rejected". Can anyone explain why this is happening and what is the solution.

Hi,
This is might be due the completion rule of the item category of the inquiry.
Check first the item category of the inquiry sales document you are using. Second go to Tcode VOV7, completion rule field of the item category you are using should be empty in order to be able to create more than one quotation from dp81.
Regards

Error while creating a quotation in SD

i am creating a quotation referring an inquiry of type ZINO and the quotation type is ZQTO. while saving the doc i am getting a error
Pricing error: Mandatory condition ZQOE is missing.
I am not able to fix it kindly help asap.
Nikhil

Hi Nikhil,
U check for which condition type U have created condition record in VK11.
Also check for the table while creating condition record (fields in condition table)
Check once while manually entering the value for the condition in sales order, If it works.....create condition record for the same combination in VK11.
Regards,
Praveen.

Allow certain users to capture quotation after bid end date

Hi
Is it possible to allow certain users to be able to capture quotation on behalf of suppliers using surrogate bid after the end date has been reached but before the opening date? How would I do this?
Regards

Hi
As the end date and opening date are at the header level common to all bidders/vendors, we cannot manually capture quotation for specific suppliers using surrogate bidding. I dont think there is even a BADI for this.
Rgds
Reddy

Error while adding custom fields in ERP quotation

I am trying to add custom fields to ERP quotation. So picked up ERP_H and added view BTCUSTOMER_H/CustomerH to its views. I have added the relevant custom fields to BTCUSTOMER_H/CustomerH. Now when I try displaying this, I get the following error..
Context generation failed in view BTCUSTOMER_H/CustomerH of UI Component ERP_H
An exception has occurred Exception Class CX_BSP_WD_INCORRECT_IMPLEMENT - There is no node text 'BTAdminH' in controller ''.
Method: CL_BSP_WD_CONTROLLER=>DO_CONTEXT_NODE_BINDING
Source Text Row: 39
Initialization of view BTCUSTOMER_H/CustomerH of UI Component ERP_H failed
An exception has occurred Exception Class CX_BSP_WD_INCORRECT_IMPLEMENT - There is no node text 'BTAdminH' in controller ''.
Method: CL_BSP_WD_CONTROLLER=>DO_CONTEXT_NODE_BINDING
Source Text Row: 39
Cannot display view ERP_H/HeaderOverviewpage of UI Component ERP_H
An exception has occurred Exception Class CX_BSP_WD_INCORRECT_IMPLEMENT - There is no node text 'BTAdminH' in controller ''.
Method: CL_BSP_WD_CONTROLLER=>DO_CONTEXT_NODE_BINDING
Source Text Row: 39
Window ERP_H/MainWindow of UI Component ERP_H cannot be displayed
An exception has occurred Exception Class CX_BSP_WD_RUNTIME_ERROR - View BTCUSTOMER_H/CustomerH in component ERP_H could not be bound
Method: CL_BSP_WD_VIEW_CONTROLLER=>BIND_VIEW
Source Text Row: 165
I have no prior experiance in UI development. Could someone explain me this error and how to fix this?
Regards,
Amar.

closing this unresolved

Changing quantities in sales order with reference to quotation

Hi,
Quotation has been created for Product -- A, 10 quantities.
Sales order created with reference to quotation, system copies 10 quantity in sales order.
How do you restrict in sales order end user should not change quantities, system should not allow for changes by end user. If end user changes Qty system should give an "Error message", so that sales can not be saved.
Could you suggest solution ASAP.
Thanks in Advance.
Regards,
vamsi.

Normally You will have a warning message set for this. under class V1. if you want the error to be hard error then you would have to hard code it in a user exit under mv45afzz "userexit_save_document_prepare" where u can check if the quantities in the quote and sales order are different and create a hard error.
the other option which I am not sure if it is possible is to propose the eror in message class v4 which you can control thru customisation under SPRO>SD>message settings
reward points if it helps
regards
Biju

Restrict manual change in sales order with respect to quotation

Hi All,
The user use to create sales order with respect to quotation. The user can able to change pricing as well as some header and item fields. How can I restrict user for manual change in sales order expect some specific fields.
Thanks.

Hi Sunil,
It is possible through configuration better you can post in sd forums.
For the condition type settings , ensure that the manual entries is 'D'. it wont allow any changes in the order.
Regards,
Madhu.
Edited by: madhurao123 on Aug 1, 2011 1:08 PM

Free goods from Quotation to Contract to Sales Order

Hi SAP Gurus,
I have questions regarding Free Goods. This is the scenario.
Doc flow as:
Quotation 123
     Contract 456
           Sales Order (zmor) 789
           Sales order (zkal) 101
In the quotation 123 & contract 456, the quantity of the item is 50pcs. However, when creating sales order (zmor), if we input 50 pcs as the quantity, the free goods were not determined. What we did was, we lessen the quantity to 30pcs. From there, Free goods were now shown. And then we created another sales order (zkal) for the remaining 20 pcs.
Questions:
1.- why is it on the 1st sales order w/ same quantity(50pcs), free goods were not determined?
2.- i believe that in standard SAP, free goods were not determined in quotation or in contract. Is there a way to determine the free goods on those doc types?
3.- how about free goods determination in:
A. Stock transfer order
B. Product diversion
C. Consignments
D. Virtual return
I am really hoping for feedback on this. Thanks in advance!
Erza

Hi,
Free goods can only be supported on a 1:1 ratio. This means that an order item can lead to a free goods item. Agreements in the following form are not supported: u2018With material 1, material 2 and material 3 are free of chargeu2018 or u2018If material 1 and material 2 are ordered at the same time, then material 3 is free of chargeu2018.
- Free goods are not supported in combinations with material structures (for example, product selection, BOM, variants with BOM explosion).
- Free goods are only supported for sales orders with document category C (for example, not quotations).
- Free goods are not supported for deliveries without reference to a sales order.
- Free goods cannot be used in make-to-order production, third-party order processing and scheduling agreements.
Regards,
Saju.S

Control of Incoterms in creation of Shipment Costs

Dear All,
We calculate shipment costs (Through Transportation module in SD-Freight payment-Outwards) on calculation base A (Delivery) or B
(Delivery item) and do not want to calculate deliveries that have certain
Incoterms (for example, TOP-To Pay, where Customer makes payment to Transporter).
By default, the system always creates a subitem in the shipment cost
document for the corresponding calculation base for every delivery item or for every delivery involved.
We want to have Control over certain Incoterms where we don't pay to the customers. We want to restrict the users not to calculate Shipment Costs in TOP-To pay cases. Kindly help if any Userexits available for this scenario to handle.
Regards
Subrat

Hi,
I think we have a similar requirement. For FCA transports is the transport cost zero. We have created a seperate condition in the cost procedure as a condition class A ( discount or surcharge ) in T_06. This has an access sequence assigned which uses a 9xx condition table (T_03) with fields Service agent f.stage ( TDLNR ) and
Incoterms ( INCO1 ). This enables us to maintain condition records in TK12. So FCA is maintained with 100 % deduction and thus no costs.

User can not create the quotation in PCUI

Dear All,
User salesrep is not able to create the quotation in PCUI. When he select the quotation tab and click on create button one pop up appears but no quotation appears in it and he can not select it for creating the quotation.
I have checked the authorization objects for this user. Seems everything is ok from authorization point of view.
User has authorization to create, display and delete for quotation in object CRM_ORD_LP.
Please help me regarding this.
Regards
Pankaj Vispute

Hi,
Please check whether u have assign transaction type of quotation and iviews to salesrep user from Portal admin and related portal role to u r User.
Regards,
DD's

Unable to Create Quotations in Oracle Apps with named PL/SQL Block

Dear All,
I got struced while creating Qotations from the backend using oracle API in a Procedure.But the same API working fine in Anonymous block and creating Qutations in apps.But the in parameters are same in anonymous and named bolck.i have done Debugging also and its returning in parameter values.but quotations not created in apps.
I am sending the both scripts(named plsql and anonymous blocks) please anybody knows about this correct me where iam doing mistake.
*******anonymous bolck*********
DECLARE
X_ROWID VARCHAR2(200) :=NULL;
X_PO_HEADER_ID NUMBER :=NULL;
X_AGENT_ID NUMBER :=25;
X_TYPE_LOOKUP_CODE VARCHAR2(200) :='QUOTATION';
X_LAST_UPDATE_DATE DATE :=SYSDATE;
X_LAST_UPDATED_BY NUMBER :=1318;
X_SEGMENT1 VARCHAR2(200) :=2477;
X_SUMMARY_FLAG VARCHAR2(200) :='N';
X_ENABLED_FLAG VARCHAR2(200) :='Y';
X_SEGMENT2 VARCHAR2(200);
X_SEGMENT3 VARCHAR2(200);
X_SEGMENT4 VARCHAR2(200);
X_SEGMENT5 VARCHAR2(200);
X_START_DATE_ACTIVE DATE;
X_END_DATE_ACTIVE DATE;
X_LAST_UPDATE_LOGIN NUMBER :=45786;
X_CREATION_DATE DATE :=SYSDATE;
X_CREATED_BY NUMBER :=1318;
X_VENDOR_ID NUMBER :=5;
X_VENDOR_SITE_ID NUMBER :=6;
X_VENDOR_CONTACT_ID NUMBER :=181;
X_SHIP_TO_LOCATION_ID NUMBER :=204;
X_BILL_TO_LOCATION_ID NUMBER :=207;
X_TERMS_ID NUMBER :=10013;
X_SHIP_VIA_LOOKUP_CODE VARCHAR2(200) :='UPS';
X_FOB_LOOKUP_CODE VARCHAR2(200) :='Origin';
X_PAY_ON_CODE VARCHAR2(200);
X_FREIGHT_TERMS_LOOKUP_CODE VARCHAR2(200) :='Due';
X_STATUS_LOOKUP_CODE VARCHAR2(200) :='A';
X_CURRENCY_CODE VARCHAR2(200) :='USD';
X_RATE_TYPE VARCHAR2(200);
X_RATE_DATE DATE;
X_RATE NUMBER;
X_FROM_HEADER_ID NUMBER;
X_FROM_TYPE_LOOKUP_CODE VARCHAR2(200);
X_START_DATE DATE;
X_END_DATE DATE;
X_BLANKET_TOTAL_AMOUNT NUMBER;
X_AUTHORIZATION_STATUS VARCHAR2(200);
X_REVISION_NUM NUMBER;
X_REVISED_DATE DATE;
X_APPROVED_FLAG VARCHAR2(200);
X_APPROVED_DATE DATE;
X_AMOUNT_LIMIT NUMBER;
X_MIN_RELEASE_AMOUNT NUMBER;
X_NOTE_TO_AUTHORIZER VARCHAR2(200);
X_NOTE_TO_VENDOR VARCHAR2(200);
X_NOTE_TO_RECEIVER VARCHAR2(200);
X_PRINT_COUNT NUMBER;
X_PRINTED_DATE DATE;
X_VENDOR_ORDER_NUM VARCHAR2(200);
X_CONFIRMING_ORDER_FLAG VARCHAR2(200);
X_COMMENTS VARCHAR2(200);
X_REPLY_DATE DATE;
X_REPLY_METHOD_LOOKUP_CODE VARCHAR2(200);
X_RFQ_CLOSE_DATE DATE;
X_QUOTE_TYPE_LOOKUP_CODE VARCHAR2(200) :='CATALOG';
X_QUOTATION_CLASS_CODE VARCHAR2(200) :='CATALOG';
X_QUOTE_WARNING_DELAY_UNIT VARCHAR2(200);
X_QUOTE_WARNING_DELAY NUMBER :=7;
X_QUOTE_VENDOR_QUOTE_NUMBER VARCHAR2(200);
X_ACCEPTANCE_REQUIRED_FLAG VARCHAR2(200);
X_ACCEPTANCE_DUE_DATE DATE;
X_CLOSED_DATE DATE;
X_USER_HOLD_FLAG VARCHAR2(200);
X_APPROVAL_REQUIRED_FLAG VARCHAR2(200);
X_CANCEL_FLAG VARCHAR2(200);
X_FIRM_STATUS_LOOKUP_CODE VARCHAR2(200);
X_FIRM_DATE DATE;
X_FROZEN_FLAG VARCHAR2(200);
X_SUPPLY_AGREEMENT_FLAG VARCHAR2(200) :='L';
X_GLOBAL_AGREEMENT_FLAG VARCHAR2(200);
X_ATTRIBUTE_CATEGORY VARCHAR2(200);
X_ATTRIBUTE1 VARCHAR2(200);
X_ATTRIBUTE2 VARCHAR2(200);
X_ATTRIBUTE3 VARCHAR2(200);
X_ATTRIBUTE4 VARCHAR2(200);
X_ATTRIBUTE5 VARCHAR2(200);
X_ATTRIBUTE6 VARCHAR2(200);
X_ATTRIBUTE7 VARCHAR2(200);
X_ATTRIBUTE8 VARCHAR2(200);
X_ATTRIBUTE9 VARCHAR2(200);
X_ATTRIBUTE10 VARCHAR2(200);
X_ATTRIBUTE11 VARCHAR2(200);
X_ATTRIBUTE12 VARCHAR2(200);
X_ATTRIBUTE13 VARCHAR2(200);
X_ATTRIBUTE14 VARCHAR2(200);
X_ATTRIBUTE15 VARCHAR2(200);
X_CLOSED_CODE VARCHAR2(200);
X_USSGL_TRANSACTION_CODE VARCHAR2(200);
X_GOVERNMENT_CONTEXT VARCHAR2(200);
X_GLOBAL_ATTRIBUTE_CATEGORY VARCHAR2(200);
X_GLOBAL_ATTRIBUTE1 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE2 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE3 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE4 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE5 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE6 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE7 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE8 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE9 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE10 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE11 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE12 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE13 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE14 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE15 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE16 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE17 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE18 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE19 VARCHAR2(200);
X_GLOBAL_ATTRIBUTE20 VARCHAR2(200);
X_MANUAL BOOLEAN;
X_PRICE_UPDATE_TOLERANCE NUMBER;
P_SHIPPING_CONTROL VARCHAR2(200);
P_ENCUMBRANCE_REQUIRED_FLAG VARCHAR2(200);
BEGIN
APPS.PO_HEADERS_SV11.INSERT_PO(X_ROWID ,
X_PO_HEADER_ID ,
X_AGENT_ID ,
X_TYPE_LOOKUP_CODE ,
X_LAST_UPDATE_DATE ,
X_LAST_UPDATED_BY ,
X_SEGMENT1 ,
X_SUMMARY_FLAG ,
X_ENABLED_FLAG ,
X_SEGMENT2 ,
X_SEGMENT3 ,
X_SEGMENT4 ,
X_SEGMENT5 ,
X_START_DATE_ACTIVE ,
X_END_DATE_ACTIVE ,
X_LAST_UPDATE_LOGIN ,
X_CREATION_DATE ,
X_CREATED_BY ,
X_VENDOR_ID ,
X_VENDOR_SITE_ID ,
X_VENDOR_CONTACT_ID ,
X_SHIP_TO_LOCATION_ID ,
X_BILL_TO_LOCATION_ID ,
X_TERMS_ID ,
X_SHIP_VIA_LOOKUP_CODE ,
X_FOB_LOOKUP_CODE ,
X_PAY_ON_CODE ,
X_FREIGHT_TERMS_LOOKUP_CODE ,
X_STATUS_LOOKUP_CODE ,
X_CURRENCY_CODE ,
X_RATE_TYPE ,
X_RATE_DATE ,
X_RATE ,
X_FROM_HEADER_ID ,
X_FROM_TYPE_LOOKUP_CODE ,
X_START_DATE ,
X_END_DATE ,
X_BLANKET_TOTAL_AMOUNT ,
X_AUTHORIZATION_STATUS ,
X_REVISION_NUM ,
X_REVISED_DATE ,
X_APPROVED_FLAG ,
X_APPROVED_DATE ,
X_AMOUNT_LIMIT ,
X_MIN_RELEASE_AMOUNT ,
X_NOTE_TO_AUTHORIZER ,
X_NOTE_TO_VENDOR ,
X_NOTE_TO_RECEIVER ,
X_PRINT_COUNT ,
X_PRINTED_DATE ,
X_VENDOR_ORDER_NUM ,
X_CONFIRMING_ORDER_FLAG ,
X_COMMENTS ,
X_REPLY_DATE ,
X_REPLY_METHOD_LOOKUP_CODE ,
X_RFQ_CLOSE_DATE ,
X_QUOTE_TYPE_LOOKUP_CODE ,
X_QUOTATION_CLASS_CODE ,
X_QUOTE_WARNING_DELAY_UNIT ,
X_QUOTE_WARNING_DELAY ,
X_QUOTE_VENDOR_QUOTE_NUMBER ,
X_ACCEPTANCE_REQUIRED_FLAG ,
X_ACCEPTANCE_DUE_DATE ,
X_CLOSED_DATE ,
X_USER_HOLD_FLAG ,
X_APPROVAL_REQUIRED_FLAG ,
X_CANCEL_FLAG ,
X_FIRM_STATUS_LOOKUP_CODE ,
X_FIRM_DATE ,
X_FROZEN_FLAG ,
X_SUPPLY_AGREEMENT_FLAG ,
X_GLOBAL_AGREEMENT_FLAG ,
X_ATTRIBUTE_CATEGORY ,
X_ATTRIBUTE1 ,
X_ATTRIBUTE2 ,
X_ATTRIBUTE3 ,
X_ATTRIBUTE4 ,
X_ATTRIBUTE5 ,
X_ATTRIBUTE6 ,
X_ATTRIBUTE7 ,
X_ATTRIBUTE8 ,
X_ATTRIBUTE9 ,
X_ATTRIBUTE10 ,
X_ATTRIBUTE11 ,
X_ATTRIBUTE12 ,
X_ATTRIBUTE13 ,
X_ATTRIBUTE14 ,
X_ATTRIBUTE15 ,
X_CLOSED_CODE ,
X_USSGL_TRANSACTION_CODE ,
X_GOVERNMENT_CONTEXT ,
X_GLOBAL_ATTRIBUTE_CATEGORY ,
X_GLOBAL_ATTRIBUTE1 ,
X_GLOBAL_ATTRIBUTE2 ,
X_GLOBAL_ATTRIBUTE3 ,
X_GLOBAL_ATTRIBUTE4 ,
X_GLOBAL_ATTRIBUTE5 ,
X_GLOBAL_ATTRIBUTE6 ,
X_GLOBAL_ATTRIBUTE7 ,
X_GLOBAL_ATTRIBUTE8 ,
X_GLOBAL_ATTRIBUTE9 ,
X_GLOBAL_ATTRIBUTE10 ,
X_GLOBAL_ATTRIBUTE11 ,
X_GLOBAL_ATTRIBUTE12 ,
X_GLOBAL_ATTRIBUTE13 ,
X_GLOBAL_ATTRIBUTE14 ,
X_GLOBAL_ATTRIBUTE15 ,
X_GLOBAL_ATTRIBUTE16 ,
X_GLOBAL_ATTRIBUTE17 ,
X_GLOBAL_ATTRIBUTE18 ,
X_GLOBAL_ATTRIBUTE19 ,
X_GLOBAL_ATTRIBUTE20 ,
X_MANUAL ,
X_PRICE_UPDATE_TOLERANCE ,
P_SHIPPING_CONTROL ,
P_ENCUMBRANCE_REQUIRED_FLAG );
END;
***************************plsql named block****************
CREATE OR REPLACE Procedure p6(p_row_id IN OUT VARCHAR2
,p_po_header_id IN OUT NUMBER
,p_segment1 IN OUT VARCHAR2
,p_Type_Lookup_Code IN VARCHAR2
                         ,p_agent_id IN NUMBER
,p_vendor_id IN NUMBER
,p_vendor_site_id IN NUMBER
,p_Ship_To_Location_Id IN NUMBER
,p_Bill_To_Location_Id IN NUMBER
,p_terms_id IN NUMBER
,p_fob_lookup_code IN VARCHAR2
,p_Freight_Terms_Lookup_Code IN VARCHAR2
,p_Currency_Code IN VARCHAR2
--,p_Start_Date IN DATE
                         ,p_Quote_Type_Lookup_Code IN VARCHAR2
--,p_quote_warning_delay IN VARCHAR2
--,p_Vendor_Quote_Number IN VARCHAR2
,p_last_update_date IN DATE
,p_last_updated_by IN NUMBER
,p_last_update_login IN NUMBER
,p_creation_date IN DATE
,p_created_by IN NUMBER
,p_Ship_Via_Lookup_Code IN varchar2
                         ,p_Vendor_Contact_Id IN NUMBER
--,p_res_ship_via IN VARCHAR2
,p_Comments IN VARCHAR2
,P_Supply_Agreement_Flag IN VARCHAR2
,p_organization_id IN VARCHAR2
--,p_procurement_channel IN VARCHAR2
--,p_Manual IN BOOLEAN
--,p_return_status OUT VARCHAR2
,P_Authorization_Status IN VARCHAR2
                         -- ,p_error_msg OUT VARCHAR2
                    ,p_Summary_Flag in varchar2
                    ,p_Enabled_Flag in varchar2
                    ,p_Status_Lookup_Code in varchar2
                    ,p_Quotation_Class_Code in varchar2
                    ,p_Approval_Required_Flag in varchar2
                    --,X_shipping_control VARCHAR2 -- <INBOUND LOGISTICS FPJ>
--,X_encumbrance_required_flag VARCHAR2
                    ) AS
v_segment1 varchar2(50):=null;
v_po_header_id number:=null;
v_row_id varchar2(50):=null;
BEGIN
po_headers_sv11.insert_po(X_Rowid => v_row_id --VARCHAR2
,X_Po_Header_Id => v_po_header_id --NUMBER
,X_Agent_Id => p_agent_id --NUMBER
,X_Type_Lookup_Code => p_Type_Lookup_Code
,X_Segment1 => v_segment1 --VARCAHR2
,X_Summary_Flag => p_Summary_Flag
,X_Enabled_Flag => p_Enabled_Flag
,X_Vendor_Id => p_vendor_id --NUMBER
,X_Vendor_Site_Id => p_vendor_site_id --NUMBER
,X_Ship_To_Location_Id => p_Ship_To_Location_Id --NUMBER
,X_Bill_To_Location_Id => p_Bill_To_Location_Id --NUMBER
,X_Terms_Id => p_terms_id --NUMBER
,X_Fob_Lookup_Code => p_fob_lookup_code --VARCHAR
,X_Freight_Terms_Lookup_Code => p_Freight_Terms_Lookup_Code --VARCHAR
,X_Status_Lookup_Code => p_Status_Lookup_Code -- Active
,X_Currency_Code => p_Currency_Code --VARCHAR
,X_Start_Date =>NULL--p_start_date --DATE
,X_Reply_Date => NULL--p_Start_Date --DATE
,X_Quote_Type_Lookup_Code => p_Quote_Type_Lookup_Code --VARCHAR
,X_Quotation_Class_Code => p_Quotation_Class_Code
,X_Quote_Warning_Delay => NULL--p_quote_warning_delay --VARCHAR
,X_Quote_Vendor_Quote_Number => NULL--p_Vendor_Quote_Number --VARCHAR
,X_Approval_Required_Flag => p_Approval_Required_Flag
,X_Last_Update_Date => p_last_update_date --DATE
,X_Last_Updated_By => p_last_updated_by --NUMBER
,X_Segment2 => NULL
,X_Segment3 => NULL
,X_Segment4 => NULL
,X_Segment5 => NULL
,X_Start_Date_Active => NULL
,X_End_Date_Active => NULL
,X_Last_Update_Login => p_last_update_login --NUMBER
,X_Creation_Date => p_creation_date --DATE
,X_Created_By => p_created_by --NUMBER
,X_Vendor_Contact_Id => p_vendor_contact_id --NUMBER
,X_Ship_Via_Lookup_Code => p_Ship_Via_Lookup_Code
,X_Pay_On_Code => NULL
,X_Rate_Type => NULL
,X_Rate_Date => NULL
,X_Rate => NULL
,X_From_Header_Id => NULL
,X_From_Type_Lookup_Code => NULL
,X_End_Date => NULL
,X_Blanket_Total_Amount => NULL
,X_Authorization_Status => P_Authorization_Status
,X_Revision_Num => NULL
,X_Revised_Date => NULL
,X_Approved_Flag => NULL
,X_Approved_Date => NULL
,X_Amount_Limit => NULL
,X_Min_Release_Amount => NULL
,X_Note_To_Authorizer => NULL
,X_Note_To_Vendor => NULL
,X_Note_To_Receiver => NULL
,X_Print_Count => NULL
,X_Printed_Date => NULL
,X_Vendor_Order_Num => NULL
,X_Confirming_Order_Flag => NULL
,X_Comments => NULL
,X_Reply_Method_Lookup_Code => NULL
,X_Rfq_Close_Date => NULL
,X_Quote_Warning_Delay_Unit => NULL
,X_Acceptance_Required_Flag => NULL
,X_Acceptance_Due_Date => NULL
,X_Closed_Date => NULL
,X_User_Hold_Flag => NULL
,X_Cancel_Flag => 'N'
,X_Firm_Status_Lookup_Code => NULL
,X_Firm_Date => NULL
,X_Frozen_Flag => NULL
,X_Supply_Agreement_Flag => P_Supply_Agreement_Flag
,X_Global_Agreement_Flag => NULL
,X_Attribute_Category => NULL
,X_Attribute1 => NULL
,X_Attribute2 => NULL
,X_Attribute3 => p_organization_id
,X_Attribute4 => NULL
,X_Attribute5 => NULL
,X_Attribute6 => NULL
,X_Attribute7 => NULL
,X_Attribute8 => NULL
,X_Attribute9 => NULL
,X_Attribute10 => NULL
,X_Attribute11 => NULL
,X_Attribute12 => NULL
,X_Attribute13 => NULL
,X_Attribute14 => NULL
,X_Attribute15 => NULL
,X_Closed_Code => NULL
,X_Ussgl_Transaction_Code => NULL
,X_Government_Context => NULL
,X_Global_Attribute_Category => NULL
,X_Global_Attribute1 => NULL
,X_Global_Attribute2 => NULL
,X_Global_Attribute3 => NULL
,X_Global_Attribute4 => NULL
,X_Global_Attribute5 => NULL
,X_Global_Attribute6 => NULL
,X_Global_Attribute7 => NULL
,X_Global_Attribute8 => NULL
,X_Global_Attribute9 => NULL
,X_Global_Attribute10 => NULL
,X_Global_Attribute11 => NULL
,X_Global_Attribute12 => NULL
,X_Global_Attribute13 => NULL
,X_Global_Attribute14 => NULL
,X_Global_Attribute15 => NULL
,X_Global_Attribute16 => NULL
,X_Global_Attribute17 => NULL
,X_Global_Attribute18 => NULL
,X_Global_Attribute19 => NULL
,X_Global_Attribute20 => NULL
,X_Manual => NULL
,X_Price_Update_Tolerance => NULL
                         ,p_shipping_control=> NULL--X_shipping_control -- <INBOUND LOGISTICS FPJ>
,p_encumbrance_required_flag=> NULL--X_encumbrance_required_flag
                         commit;
dbms_output.put_line('agent_id:'||p_agent_id);
dbms_output.put_line('segment1:'||P_segment1);
dbms_output.put_line('SHIP_TO_LOCATION_ID:'||P_SHIP_TO_LOCATION_ID);
dbms_output.put_line('BILL_TO_LOCATION_ID:'||P_BILL_TO_LOCATION_ID);
dbms_output.put_line('VENDOR_SITE_ID:'||P_VENDOR_ID);
dbms_output.put_line('VENDOR_SITE_ID:'||P_VENDOR_SITE_ID);
dbms_output.put_line('SUPPLY_AGREEMENT_FLAG:'||P_SUPPLY_AGREEMENT_FLAG);
dbms_output.put_line('QUOTE_TYPE_LOOKUP_CODE:'||p_QUOTE_TYPE_LOOKUP_CODE);
dbms_output.put_line('FREIGHT_TERMS_LOOKUP_CODE:'||P_FREIGHT_TERMS_LOOKUP_CODE);
dbms_output.put_line('AUTHORIZATION_STATUS:'||P_AUTHORIZATION_STATUS);
dbms_output.put_line('ORGANIZATION_ID:'||p_ORGANIZATION_ID);
dbms_output.put_line('VENDOR_CONTACT_ID:'||P_VENDOR_CONTACT_ID);
dbms_output.put_line('Type_Lookup_Code:'||p_Type_Lookup_Code);
dbms_output.put_line('Summary_Flag:'||p_Summary_Flag);
dbms_output.put_line('Enabled_Flag:'||p_Enabled_Flag);
dbms_output.put_line('Comments:'||p_Comments);
dbms_output.put_line('Currency_Code:'||p_Currency_Code);
dbms_output.put_line('Authorization_Status:'||P_Authorization_Status);
dbms_output.put_line('Status_Lookup_Code:'||p_Status_Lookup_Code);
dbms_output.put_line('Quotation_Class_Code:'||p_Quotation_Class_Code);
dbms_output.put_line('Approval_Required_Flag:'||p_Approval_Required_Flag);
dbms_output.put_line('last_update_login:'||p_last_update_login);
dbms_output.put_line('created_by:'||p_created_by);
dbms_output.put_line('last_update_date:'||p_last_update_date);
dbms_output.put_line('Vendor_Contact_Id:'||p_Vendor_Contact_Id);
dbms_output.put_line('fob_lookup_code:'||p_fob_lookup_code);
EXCEPTION
WHEN OTHERS THEN
--p_return_status :='E';
--p_error_msg     :='ERROR during Insert in PO_HEADERS.'||CHR(10)||SQLERRM;
raise;
END p6;
Regards,
YellaGoud

What is your current Oracle user ?
show userTry to identify the table owner:
select owner from dba_tables where table_name='CE1LAOC';And add <table owner> as prefix to table name:
CREATE INDEX Z05 ON <table_owner>.CE1LAOC (MANDT, PALEDGER, BUKRS, PERIO, VRGAR, VKORG, HZDAT);

Using gross price instead of net price at Quotation

Hi,
I'm working at a company that just bought SAP ERP ECC 6.0. Our consultants told us that SAP only works with Net price in MM. It sounds a little bit weird for us, because here in Brazil we usually use Gross price in all our transactions.
Here in Brazil we have some taxes that are included in gross price and it's a hard work ask the final user to calculate the taxes out of SAP and input net Price in the system.
I read a little bit some documentation provided by SAP at Internet called SAP Library and I found an article titled:Entering a Quotation Against an RFQ
In this article says the following: " You enter the net price per unit in the Net price field. This price includes the vendor's normal discounts and surcharges only. Cash discounts (for prompt payment) and taxes (e.g. value-added tax) are calculated separately.
You enter the gross price in the Net price field, and maintain the conditions for the item. Then the system automatically replaces the entered gross price with the calculated net price (see Maintaining Conditions)."
As we can see, there are two ways to input the price. Gross price and Net price. I'd like to know if is there the possibility to configure the "mentioned conditions" for a group material and at the moment I type the gross price in Quotation the system automatically calculate the net price?
Our consultant told us that this procedure should be done for each item in quotation, in my opinion I guess that SAP can link the applicable taxes for the material based on its group material. If something like that is possible, our daily work will be simplified so much because the system will know the taxes that should be discounted for the material and calculate automatically the net price.
If this possibility exists, could you please tell me in technique terms (transactions) that should be set?
Another question is about Taxable Income, is there any place in SAP where I can configure the Taxable Income for a material or group material for the taxes set at "mentioned conditions"?
Thanks in advance,
Sorry about my English.
Best Regards,
Amorim, Rodrigo.

What you need is a new pricing procedure design to fit your requirements. The standard pricing procedure allows you to enter the net price. Then the gross price is calculated after taking into account the discounts, taxes etc. These discounts and taxes can be designed to determined automatically through material group also. So to achieve your requirement the pricing procedure has to be changed accordingly to calculate the net price from gross price entered. While this can be done, but all other impacts on pricing reports and accounting document posting with correce valuation price etc. have to be tested in detail.

Incoterms in Quotation

Similar Messages

Maybe you are looking for