Maintain Pricing Procedure

Hi All,
In the pricing procedure maintain screen i.e. V/08 , what is the role of following three columns?
1) Condition Formula calculation Rule
2) Condition Formula for Basis
3) Sub Total column.
How can we use first two column (said above) for developing new routine. Also I would like to know the functionality of standard routine which are available in the pricing. - Kindly explain it with the example.
Thanks & Regards,
Savi

Subtotal:
u2022     The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
u2022     Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
u2022     If the same fields are used to store different condition amounts, the system totals the individual amounts.
u2022     These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
AltCty - Condition formula for alternative calculation type:
u2022     It is again a Routine that is written by ABAP Consultant.
u2022     It is an alternative formula for the condition type that can be used instead of standard formulas.
u2022     For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
u2022     Ex.: 950 0 Profit Margin 11.
u2022     So we assign 11 - Profit Margin.
u2022     If new routines are to be defined we follow the procedure given below.
u2022     Go to T.Code: VOFM. - Maintain Requirements & Formulas
u2022
u2022     Click on the "Formulas" and then on the "Condition Values".
u2022     We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
u2022     And we assign the application type.
AltCBV - Alternative formula for condition base value:
u2022     Formula for determining the condition basis as an alternative to the standard.
u2022     It is again a Routine that is written by ABAP Consultant.
u2022     It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
u2022     Ex.: Freight - KF00.
u2022     Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
u2022     In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
u2022     During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
u2022     Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
Regards,
Rajesh Banka

Similar Messages

How to maintain pricing procedure

Hello all,
I have the following problem:
I have three discount conditions and they shall be calculated like this:
Condition 1: Gross Value * % (that is working fine)
Condition 2: (Gross Value - Condition 1) * %
Here I figure the problem that the condition itself is specified as AFS Condition with alternative calculation routine 494 and I dont know how to change it in order to have calculated the condition from the Gross Value - Condtion 1. At the moment the condition gets calculated only from the Gross Value
Condition 3: (Gross Value - Condtition 1 - Condition 2) * % (that is also working fine)
Has anyone a clue I this could work? Condition 1 and 3 are header condition and not AFS specific but Condition 2 is AFS specific.
Thanks for you hrelp and answers
Bea

Hi Beate,
Try this way.
Set Condition 1, 2 & 3 as negative type conditions, as they is a Discount
Say your step 100 is Gross Values. Then;
Step 100 - Gross Value
Step 110 - Condition 1 - from Step 100 (i.e: Gross Value * % )
Step 120 - Sum of Step 100 to 110 (i.e: Gross Value - Condition 1)
Step 130 - Condition 2 - from Step 120 (i.e:Gross Value - Condition 1) * %
Step 140 - Sum of Step 120 to 130 (Gross Value - Condition 1 - Condition 2)
Step 150 - Condition 3 - from Step 140 (Gross Value - Condition 1 - Condition 2) * %
Then re-test it.
Best regards,
Anupa

Maintain CIN configuration & Pricing Procedure for Trading Company

Hi Experts,
Our client is a Trading Company. In this company...first they purchase finish goods and than sale it. They are not selling their material to the manufactures. They are not creating the excise invoice.
Please suggest us how to maintain CIN configuration & maintain Pricing Procedure for them.
Thanks in advance.
Regards,
Shatrughan

Hi,
Create 2 tax codes in T-code FTXP
1 for VAT, 2nd for CST
then you define 2 condition types in v/06,
ex:ZVAT,ZCST
place these 2 condition types in your pricing procedure in V/08
And in VK11 maintaine condition records.
Thank you,

Derivation of pricing procedure in rebate credit note

Hi friends!
We have unique issue related to settlement of rebate credit note for a rebate agreement document. The rebate condition records are not populating with correct condition types and there is different pricing procedure being derived in credit note document. My query is that where do we maintain pricing procedure for rebate credit note (VF03) and how do the pricing procedure determine for rebate credit note.
Thanks & regards,
Praveen.

Dear Praveen
In rebates once you settle the amount from rebate agreement the credit memo request will be generated automatically.
With reference to the credit memo request number you go to the VF01 and raise the credit memo (g2).
Make sure that document pricing procedure should be same for credit memo req and credit memo and respective pricing procedure should be assigned in u201COVKKu201D .
Please try and let me know the status
Thanks&Regards
Raghu.k

Pricing procedure for order with reference from order

Dear Friends,
If I create a sales order with reference to another sales order of different type, the pricing procedure is copied too.
But I would to use another pricing procedure for second document
I found the oss note 14136 but this is for reference from invoce
I tried to create new data transfer routine for orders in copy from 51, but does not work
Can you help me??
thanks
best regards
GdA

> If I create a sales order with reference to another sales order of different type, the pricing procedure is copied too. But I would to use another pricing procedure for second document,
Based on my understanding of query.
You are looking for a different pricing procedure in second doc.
For instance, the PricProc for SalesDoc1 is ZPR001 and the PricProc for SalesDoc2 is ZPR002, in addition to that, you want SalesDoc1 to become reference doc for SalesDoc2.
For this, ZPR002 & ZPR001 should have common base price condition type and rest pricing can change.
And for maintaining different Pricing Procedure with similar combination of sales area for SalesDoc1 & SalesDoc2, maintain different document pricing procedure for both docs and maintain Pricing procedure accordingly..
Thanks & Regards
J Prakash

Relation between Tax procedure and Pricing procedure

Dear All,
I would like to get more clarity on Tax procedure, Pricing procedure.
a) Why do we have Tax procedure and assigned to Country?
b) If the tax procedure has been created and assigned to Country-IN (in FI module), then why do we need to create pricing procedure with same condition type for purchasing in MM module? We are even creating lot of pricing procedure for Sales in SD module.
Regards
Manivannan R

Hi
Tax
During SD document transactions, tax calculation procedure TAXUSX is only relevant to determine the tax liability accounts for output sales tax. Notice that in pricing procedure RVAXUS, the condition types XR1 - XR6 carry the tax rates and tax amounts - resulted from the external tax system calculation - which is posted to tax G/L accounts. However, the tax accounts are not specified in the pricing procedure but rather in the tax calculation procedure.
Tax codes are the link between pricing procedure and tax calculation procedure.
Pricing
The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
Which sub-totals appear during pricing
To what extent pricing can be processed manually
Which method the system uses to calculate percentage discounts and surcharges
Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
Example
Example of a Pricing Procedure
If a sales department processes sales orders for a variety of foreign customers, the department can group the customers by country or region. A pricing procedure can then be defined for each group of customers. Each procedure can include condition types that determine, for example, country-specific taxes. In sales order processing, you can specify pricing procedures for specific customers and for sales document types. The system automatically determines which procedure to use.
Pricing Procedures in the R/3 System
The standard system contains pre-defined pricing procedures, which contain frequently used condition types along with their corresponding access sequences. You can, of course, modify these procedures or create your own from scratch.
Creating and Maintaining Pricing Procedures
You create or maintain pricing procedures in Customizing for Sales. For more information on creating pricing procedures, see the online Implementation Guide for Sales and Distribution.
To reach the pricing procedure screen from SD Customizing:
1. Choose Basic Functions
2. ® Pricing ® Pricing control ® Define and assign pricing procedures.Select the transaction that you want to execute.

Explain the Pricing Procedure

Hi Friends
Explain how the pricing is determined for an item, starting from the sales order
Discuss the full cycle also make a mention on the Condition type controls, and Maintain pricing procedure controls.
Kindly explain it with an example.
Thanks

Pricing Procedure is indeed an heart of SD module, reason being if everything else is working fine, but price is not being calculated correctly, the purpose of billing fails.
An Overview of Determination & Configuration of Pricing Procedure is as follows:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Pricing Procedure --> Determine Pricing Procedure.
Step 5: Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

Re:Problem in Pricing Procedure Determination

Dear All,
I have a problem in Define Pricing Procedure Determination.
I am getting an error message " Condition Type BP04 is not in procedure ZBP04A A V".
The condition type has been copied from K007.
Access Sequence is BP04.
In Maintain Pricing Procedure, I have selected RVAA01 and copied it as ZBP04A.
Please let me know how to rectify this error.
Thanks,
Amba Prasanna

hi Prasanna,
am getting an error message " Condition Type BP04 is not in procedure ZBP04A A V".
It means in the pricing procedure ZBP04A the condition type BP04 has not been maintained. So go to V/08, select conrtol data on the left side, click new entries and maintain this conditino type.
The condition type has been copied from K007.
You might have copied K007 but forgot to put it in the above mentioned pricing procedure.
Access Sequence is BP04.
Also make sure that for your condition type BP04, you have maintained the access also as BP04 in V/06, since you wanted it.
In Maintain Pricing Procedure, I have selected RVAA01 and copied it as ZBP04A.
This is fine, in OVKK- no error.
regards
sadhu kishore

Pricing procedure execution...

Hi Folks,
How SAP reads the pricing procedure..
Example
Con.Type      Requirement        Routine
ZSAA            601                     901
ZSAB            602                     902
Doubt 1: -Is system reads this pricing procedure line by line or coulmn by column?, In the debug we noticed it goes column by colmun? why?
Doubt 2: - I want to know the value found for ZSAA during the execution of 602 requirement. Example scenario is if ZSAA is more than 100$ don't execute ZSAB.

Pricing Procedure:
Determination of Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure through T.Code: OVKK. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
Configuration of Pricing Procedure:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka
Reward suitable points.

How to assign a pricing type to the pricing procedure ?

Business Scenario : When the prices change from the time the order is taken to the time the invoice is created, how can setup the system to handle the changes automatically ?
I would like to know How to create a pricing type and How to assign a pricing type to the pricing procedure so that I can use the 'new pricing document' function in the sales document and 'Update prices' on the condition screens in the Billing document.
Thanks for your input in advance.
Oscar

Hi !! Oscar,
1) For pricing type definition you would require the help of a developer.
2) However, most of the commonly occuring requirements are supplied with standard SAP.
You can assign a pricing type to pricing procedure as follows:-
IMG>S & D >Basic Functions>Pricing>Pricing Control>Define & Assign pricing procedures>Maintain pricing procedure> Here, locate your pricing procedure , in the fourth coloumn using the drop down list, you can assign a pricing type to the pricing procedure.
Now you can use the 'new pricing document' function in the sales document and 'Update prices' on the condition screens in the Billing document !
Regards,
PATHIK
Message was edited by:
Pathik Pandya

How to design a Pricing Procedure with both MWST and MWSI in it ?

Hi there.
My business requirement dictates that I can have both Tax inclusive(PR01/MWSI) and Tax Exclusive(PR00/MWST) items within a Single Sales Order.
I know that One pricing procedure can only be assigned to 1 Document Type. So,
Has anyone successfully created a Pricing Procedure that incorporates both the MWST and MWSI tax components ? If so, could you post a sample of the pricing procedure in order for me to understand how I should group the discounts/surcharges and reflect the Subtotals, as well as incorporate the MWST and MWSI all within a single Pricing Procedure ? I will also need to include the PR01 and PR00 conditions into the procedure too, right ?
Really really hope someone with the experience, can aid me on this. I cannot find any relevant materials on this matter, both in OSS Sapnotes and within this forum.
regards
Poo

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
Similarly in MM Module we have Pricing Schema.
Regards,
Rajesh Banka
Reward points if helpful.

Excise Pricing procedure for Stock Transport Order in MM with TAXINN

I am an SD guy running STO from manufacturing plant to sales depot
AND not able to create JEX proforma excise invoice from NL
to TEST my configuration, I created excise invoice in J1IS with respect to goods issue from NL from UB means configuration is ok
BUT base amount in J1IS is coming as zero because of missing excise conditions in MM STO pricing procedure
CAN anybody give me a sample EXCISE pricing procedure for STO
AND do i need to create records for the condition types in FV11 OR MEK1 please clarify
I know that calculation type 362 attached to BASB in TAXINN has something to do with this
I am able to see chapter ID in J1IS
And the relation between condition types in TAXINN and excise pricing procedure for STO
And I am able to create excise invoice in J1IG with zero excise values
I also maintained pricing procedure determination for JEX in OVKK that is document pricing procedure N pricing procedure JINSTOCK
I think my explanation is sufficient enough
please give A sample of TAXINN

Hi Yoga,
Here u not need to do VL10b.just follow this steps and try.
In PO,Document type is UB and Item Category is U.
After creating PO,In MB!B with reference that PO number and using movt type 541
then u can see that stock in Transit.Now u do GR with respect to PO number.
Thanks & Regards
Suresh.
> Hello MM Gurus,
>
> I am doing Stock transport order between 2 plants
> under same company code.
> I have maintained all the required settings.Following
> is the process flow.
>
> 1.Creation of Purchase order with document type
> UB.(ME21N)
> 2.Creation of outbound delivery with respect to
> Purchase order.(VL10B)
> 3.Post Goods Issue from the supplying plant. (VL02N)
> 4.Creation of Excise Invoice in supplying plant.
> (J1IS)
> 5.Goods receipt at the receiving plant.(MIGO)
>
> While I am doing Goods receipt in the receiving
> plant, system is giving an error
> message "Maintain Vendor for the Excise Invoice" -
> Message no. 4F185.
> Why this message is coming and how to resolve this?
>
> Thanks & Regards
> Yoga

HOW CAN APPLY FREE GOOD 4 PRICING PROCEDURE?

TELL ME SIR HOW CAN APPY FREE GOOD 4 PRICING PROCEDURE?

Hi Pradeep
1.Run trans. VBN2 to first create master record for free goods as follows:
Enter following information in selection screen:
- Free goods type: NA00
- Sales org, distribution channel, customer # and execute.
Now in next screen create the record as follows:
- First select the exclusive button and verify that you are in exclusive view.
(that is if you want exclusive)
- Material#, Min qty - Say 34 cartons. (check in what units you want to manage)
From: 34 cartons
unit of measure:
Free goods: 12 Pcs
Unit of measure: Pcs
Calcualtion type: 1 or try the other options
Deliver control: Blank or any of the other options suitable to you.
Now save and exit.
Now run VA01 for 34 cartons and press enter. The system will automatically propose the free goods
item at no additional charge. Try higher order qtys and see if the free goods qty are scaling up.
If not adjust the calculation parameters in the master record screen
It should be transaction VBN1. Sorry for the error.
VBN2 is to change the record. VBN1 creates it.
If you want to give free goods to some of the customers than
1. create a customer group say 99 for FREE GOODS
In Free Goods Menu:
2. add a feild catalog for CUSTOMER GROUP
3. create a condition table (free goods) say 555 only for customer group
4. create a sequence say FREE with condition table 555
5. create a condition type say FREE with
6. maintain pricing procedure say ZFREE with condition type FREE
Now assign:
7. Active Free goods Determination or Assign with your sales organisation this procedure ZFREE
8. Create free goods determination with transaction code /nvbn1 for FREE with Key Csuomer Group
99 for exclusive
Give customer Group say 99 and from 34 to 34 free 12
Thanks
G. Lakshmipathi

Import pricing procedure

Hi,
I am in Import scenario,
in this case my client is not availing any credit(ie CENVAT credits from Excise). But I wanted to maintain Cost,Insurance,freight,Landing cost,basic duty 14%,Ed cess 2%,HEd cess 1%,Customs Ed cess 2%,Customs HEd cess 1%,Additional duty of customs 4% in PO so that I can carry out the Invoice Verification for it.
So which and where condition types should I maintain for the same.
Please give the detailed procedure if possible.
Thanks in advance.
Regards,
Goraksh.
Edited by: goraksh dhikale on Oct 21, 2008 10:57 AM

IMPORT PROCESS
in ur pricing u have to create following
JCDB IN: Basic Custom Duty
JCV1 IN : CVD
JECV IN : Ed Cess on CVD
J1CV IN : H&SECess on CVD
JEDB IN : Ed Cess on BCD
JSDB IN : H&SECess on BCD
JADC Additional Duty of Custom
JCV1, JECV, J1CV and JADC will go to Excise MODVAT Accounts and JCDB, JEDB and JSDB will get loaded on inventory.
In M/06, for all above conditions, keep following controls;
Cond. class A (Discount or surcharge) Plus/minus A (Positive)
Calculat.type A (Percentage)
Cond.category B (Delivery costs)
Activate "Currency Conversion" and "Accrual"
now for setoff
maintain the following conditions in excise default settings.
JCV1, JECV, JADC
path: spro>logistic general >tax on goods movements>india >basic settings>determination of excise duty >maintain excise defaults >
along with ur taxprocedure maintain these conditons in the specified fields
JCV1 in CVD condition field.
JECV in ECS conditon field.
JADC in ACD conditon field.
in case of secess on CVD, no need to maintain.
it is hardcodded in the standard
Vendor in GR 2 (Entry always possible)
Import scenario
1.Create material master of import goods.
2.Create vendor master record of import vendor and Customs clearing vendor.
3.Maintain CIN settings.
4.Maintain J1id.
5.Maintain Pricing procedure SAP standard JIMPOR..,maintain required conditions..JCDB,JCV1...
6.Assign the schema to respective import vendor in Purchasing view of VMR.
7.Create import PO ,check in conditions of JCDB, JCV1 the customs clearing vendor(Indian vendor) and percentage is assigned..This can be done by In condition tab select condtion then click on display,then enter.
Save the PO.
8.MIRO --Capture Bill Of Entry.(Commercial Invoice No.,).Customs clearing first .Here CVD will b converted to BED.
9.Capture Excisse invoice--j1iex.
10.MIGO.
12.Post Excise Invoice.
13.MIRO...Payment to vendor(import vendor)
regards
kunal

Import Pricing Procedure-Assesable Value

Dear All,
we already having import pricing procedure, now we are adding the assesable value condition in the pricing procedure JASS is the condition which added. All customs duty is calculated properly but at the end we have the conditon of actual price which is basic price + taxes which is not coming properly. after adding the assesable value the actual price is copying the value of assesable value. actual price is statistical and in sub total column 'S - Copy values to KOMP-EFFWR (effective value)' is there. what is the reason it is not calculating the acutal price correctly?
Thanks in advance
Ramakant

hi
check following
in ur pricing u have to create following
JCDB IN: Basic Custom Duty
JCV1 IN : CVD
JECV IN : Ed Cess on CVD
J1CV IN : H&SECess on CVD
JEDB IN : Ed Cess on BCD
JSDB IN : H&SECess on BCD
JADC Additional Duty of Custom
JCV1, JECV, J1CV and JADC will go to Excise MODVAT Accounts and JCDB, JEDB and JSDB will get loaded on inventory.
In M/06, for all above conditions, keep following controls;
Cond. class A (Discount or surcharge) Plus/minus A (Positive)
Calculat.type A (Percentage)
Cond.category B (Delivery costs)
Activate "Currency Conversion" and "Accrual"
Now for setoff
maintain the following conditions in excise default settings.
JCV1, JECV, JADC
path: spro>logistic general >tax on goods movements>India >basic settings>determination of excise duty >maintain excise defaults >
along with ur tax procedure maintain these conditions in the specified fields
JCV1 in CVD condition field.
JECV in ECS condition field.
JADC in ACD condition field.
in case of SECess on CVD, no need to maintain.
it is hardcode in the standard
Vendor in GR 2 (Entry always possible)
Import scenario
1.Create material master of import goods.
2. Create vendor master record of import vendor and Customs clearing vendor.
3. Maintain CIN settings.
4. Maintain J1id.
5. Maintain Pricing procedure SAP standard JIMPOR.., maintain required conditions..JCDB, JCV1...
6.Assign the schema to respective import vendor in purchasing view of VMR.
7. Create import PO, check in conditions of JCDB, JCV1 the customs clearing vendor(Indian vendor) and percentage is assigned. This can be done by In condition tab select condtion then click on display, then enter.
Save the PO.
8. MIRO --Capture Bill Of Entry.(Commercial Invoice No.,).Customs clearing first .Here CVD will b converted to BED.
9. Capture Excises invoice--D.
10.MIGO.
12.Post Excise Invoice.
13.MIRO...Payment to vendor(import vendor)

Maintain Pricing Procedure

Similar Messages

Maybe you are looking for