Pricing condition (CVD) in imports pricing are being non-inventorised

Dear Experts,
In import pricing procedures the Pricing condition CVD is going as non-inventory, can some explain me how this is controlled? Is there any configuration setting available for this CVD conditions?
Regards,
Praveen

Hi Praveen,
Pl check which condition type you are using for CVD in M/08 in the Account column check which account key you are assigned then go to OBCN and enter the same account key which was assigned in Pricing procedure of Import, then go details (lens button) at the left side on top the screen you can find the below entries there must be tick on which is the reason the CVD is going to material cost as it becomes No deductible.
Description Input acquisitn tax
Tax type 2 Input tax
Not deductible ticks remove
Posting Indic. 2 Separate line item
Regards
Shubham

Similar Messages

Condition types for import pricing

hi,
     the conditions types for import pricing procedure are not appearing.
please suggest all the notes from where i can take reference and create the condition types for import process.
please also suggest what are they?
with regards

Hi anitha,
In case of import purchase. u have to configure the conditions in pricing procedure. The condition types are as follows:
1)jcdb               basic customs
2)jcv1               CVD
3) jec1               ECS on CVD
4)jed1              cess on customs
5) j1cv                secess on cvd
6) jsdb               secess on customs
Go to the master note no 1032295 for recent budget changes.
award points if found useful
chintu

Condition record and import pricing procedure

hi sap gurus
i want to know abt condition record and import pricing procedure in detail can u pls help me

You use Condition Types as,
PB00 -- Gross Price
FRA1 -- Freight
FRB1 -- Freight (value)
RA01 -- Discount. etc.,
and in Import PO,
the Pricing Procedure has to be defined by including the CVD condition Type like
JCDB -- Basic customs duty
JCV1 -- CVD Percentage
JECV -- Edu Cess on CVD
J1CV -- SECess on CVD
JEDB -- ECess Basic customs etc.,
Then in J1ID, you have to maintain JCV1(CVD Percentage)
in Default values of TAXINN

Edited photos will save in edited photos will not save in photoshop are being saved in my pictures on hard drive. wants me to import edited are being saved in my pictures on hard drive. wants me to import edited photos from my hard drive in to photoshop.

edited photos will save in edited photos will not save in photoshop are being saved in my pictures on hard drive. wants me to import edited are being saved in my pictures on hard drive. wants me to import edited photos from my hard drive in to photoshop.

Use iPhoto. What's the problem with iPhoto import? It's a two clicks job. Select your device and click import.

Conditions types in Import Pricing

Hi All
What are the conditions types which are required in Import Pricing. What is process flow for Import Procurement
Regards
Jagadish

Hi,
The conditions for duties in import are;
JCDB IN:Basic Custom Duty 7% or 12%
JCV1 IN : CVD 14%
JECV IN : Ed Cess on CVD 2%
J1CV IN : H&SECess on CVD 1%
JEDB IN : Ed Cess on BCD 2%
JSDB IN : H&SECess on BCD 1%
JADC Addnl Duty of Custom 4%
The import process are
1) Create Vendors and give Order Currency (USD, JPY ,INR Etc) in XK01 for Local Vendor (INR) and Main vendor (USD, JPY Etc.)
2) Create Material Master and give appropriate Description Because Users should Identify Correct Material Or Activate Split valuation.
3) Create Import Purchase order for Import Vendor with separate Document type and purchasing group.
4) Mention Duty rates (CVD, Customs, Cess on CVD, cess on Customs, HSC on CVD,HSC on Customs and ADC) and Don't forget to mention Custom Vendor In Duty rates condition type.
5)MIRO Customs Invoice, you can Invoice in Vendor Currency as well as Indian Currency.
6) Receive the Material through MIGO, If you Correctly maintaining Customizing of Excise Duties at the Time of MIGO u can take credit for CVD, Cess on CVD, HSC on CVD and ADC and rest of all add to your material cost.
7) In MIGO you can Capture the Excise invoice and in J1IEX post the Excise invoice.
8) After Receiving the goods and Payment to the Customs raise a Invoice for Main Vendor
Regards,
Biju K

Pricing Condition type in a Sales area

Hello All,
Please let me know how can I find the condition types used for pricing by the customers in a particular sales area? I know the link is in some config table like T683 T683s T683v but please tell me the exact table link..
Thanks a lot!
Reward pts for useful answers.

Have u tried this table
Communications Table SD -> CO/Projects (S008)

Pricing Conditions and how the pricing date is determined

Hi all,
Small question, i ahve some pricing conditions that use the Serives Rendered date and others that use the Pricing Date from an order, how is the condition decided on what date it uses?
Hope i have expplained this ok, if not and you need more info let me know.
Regards
Steve

Hi
There is a difference between Service Rendered Data and Pricing Date.
Normally Freight Conditions are maintained on Service Rendered Date so the freight will be picked on the basis of date on which the Actual Delivery done, whereas Pricing date is used for other conditions so that price will be based on the date on which the document created and the Pricing Date maintained in that.
In the same way there is a Billing Date which came in Invoice so price will be based on the date of Invoicing.
If you maintain the record in VK11 and test a cycle you will be able to find the difference easily.
Regards
Amitesh

To make the Pricing Condition types inactive in Pricing Procedure

Hi Experts,
I am facing a senario where, in a sales order, pricing procedure, if one of the pricing condition type does not exist, then two other condition types (even though they are determined by condition records), should be either made inactive or should not appear in the pricing procedure.
Example: If I have 3 condition types in Pricing Proc say
YYY1, YYY2, YYY3, then the scenarios are
a. If one of the condition types YYY1 is not determined, then, YYY2 and YYY3 should not be either determined in the sales order or should be made inactive. This same logic applies to both YYY2 and YYY3.
b. If all three condition types are determined in Pricing Proc of the sales order, then, the price should be considered.
If it was just YYY1 then, I could have done it in VOFM by writing a routine and assigning it to YYY2 and YYY3 in pricing proc. However, the scenario is to check the other condition types as well and make YYY1 inactive if any of the other condition type does not exist. Both condition types are determined after YYY1 which is another difficulty.
I tried creating a dummy condition type and assigning it to Pricing Proc (at the end of Pricing Proc). For this dummy condition I put in a pricing requirement which checks for all three condition types and if one does not exist, then it make other conitions inactive.
However, this does not work in VA02 and VA03 as XKOMV is either not getting filled up or even if is getting filled, it is not having the condition type. It some times has condition records, and sometimes not... (not very sure why)
So, I was thinking of using user exit for the same. However, I was unable to find a suitable user exit for the same where KONV table can be read or XKOMV can be filled.
Can you please suggest if any user exit can be used for this or if we can implement it in a different way?
Regards,
Mukund S

Hi,
I think you can use condition exclusion functionality to select best pricing condition from a set of conditions in pricing. You can compare conditions in many ways.
I believe you can plot a solution with little research. The below link is for your reference.
[http://help.sap.com/saphelp_40b/helpdata/fr/93/743483546011d1a7020000e829fd11/content.htm]

Pricing condition in Billing document (Pricing Date)

Hi Gurus,
I have a sales order which is created on 10.01.2012, the pricing date in the sales order is the same (10.01.2012). The Delivery was created on 22.02.2012 and Actual GI date is also 22.02.2012.
Now when I am creating the billing document, the pricing condition value is showing as '0'. I checked the pricing analysis and found that the validity of the base price condition Z001 was from 10.01.2012 till 14.01.2012 in the sales order.
As the Actual Goods Issue date is taking as the 'Billing date' as well as 'Pricing Date' , the system is not able to find a valid condition type as on 22.02.2012 (GI date). The pricing type in copying control of Delivery to Billing is 'C - Copy manual pricing elements and redetermine the others'.
So I would like to know your opinion on the following.
1) Can I create the billing document using VF01, manually change the pricing date as 10.01.2012 and do the price update using rule C? Will it fetch the price based on the pricing date?
OR
2) Maintain the condition type Z001 for the GI date and do the billing?
Please let me know which is the best way to adopt?
Regards,
SAM

Hello,
If you have necessary authorization to change the Pricing Date in Invoice, please go ahead.
Change the Pricing date in Invoice, go to Conditions tab & update the Pricing. System will fetch Condition Records as on that date.
Hope this helps,
Thanks,
Jignesh Mehta

Middleware-Pricing condition error while downloading pricing objects

Dear all,
I am encountering an error after i replicated the pricing objects from R/3 to CRM. Below is the description of that error as seen in T-code SLG1
There is no entry in the object directory (TADIR) for R3TR TTYP /1CR/RCBCUS503_T
Please provide me with some pointers to resolve this issue.
Thanks & Regards
Yogesh

Hi Yogesh,
I am facing exactly the same problem,
How did you solve it?
Any comments gurus?

FM SD_SALESDOCUMENT_CREATE - pricing condition problem

Hello,
I hope someone could help me on this one:
First of all, my SAP version is 4.6c.
I've been developing a program that will create a sales contract using FM SD_SALESDOCUMENT_CREATE. Overall, the sales contract is being created successfully.
However, in the item pricing, the pricing condition that I need to create is being duplicated. I understand that in the pricing procedure the particular condition is being inserted automatically. The problem is, instead of the FM updating the default inserted pricing condition, it's inserting the one being passed.
I've already done a little research through the forums. I've tried [this|SD_SALESDOCUMENT_CREATE with Pricing Condition; suggestion where I create first the document then update it using SD_SALESDOCUMENT_CHANGE. There is also [this suggestion|SD_SALESDOCUMENT_CREATE - Duplicate sales conditions; that sets the field LOGIC_SWITCH-COND_HANDL, but my version does not have that field.
Finally, there's [this suggestion|http://www.sapfans.com/forums/viewtopic.php?f=13&t=218865&start=0&st=0&sk=t&sd=a] that sets the field LOGIC_SWITCH-PRICING to a particular value. I tried the initially suggested value of 'G' - Copy pricing elements unchanged and redetermine taxes. The duplicate condition no longer occurs, but other pricing conditions were removed. Using other values resulted in either the contract creation failing, or the condition value not updating.
So, please please can anyone help with my problem? Thank you in advance.

SALES_CONDITIONS_IN
            ITM_NUMBER                     000010
            COND_ST_NO                     020
            COND_COUNT                     01
            COND_TYPE                      YB05
            COND_VALUE                                           10.000000000
            CURRENCY                       TWD
SALES_CONDITIONS_INX
           ITM_NUMBER                     000010
           COND_ST_NO                     020
           COND_COUNT                     01
           COND_TYPE                      YB05
           UPDATEFLAG                     U
           COND_VALUE                     X
           CURRENCY                       X
IF the condition is being inserted automatically,you must update it.
some import parameters are obligatory,including COND_ST_NO COND_COUNT.

Purchase Order Pricing Condition and Withholding Tax

Hi
We have investigated Extended Withholding Tax functionality, which appears to be FI specific.
The problem is that we want to have the Purchase Order pricing conditions reflect that some amount is being withheld for tax purposes.
At invoice time, the vendor would invoice for the entire amount (i guess) (ie. 100$) but we would pay the vendor only 80$ and 20$ would go to a withholding tax account...or something like this would happen ...
I have some pricing config knowledge...but limited
Can anyone tell me
a) if this is possible?
b) any hints on how to go about this?
Also noticed a 'withholding tax code' field on MEK1 - Create Condition Records. .... which appears as display only depending on how i configure my condition type - haven't figured out how to use this field or what is means...
Thank-you !!!

Hi,
If you are using the standard PO Print then check in M/08 and check for that Condition Type whether Print Indicator is "X"? If it is is Z-Print Program then take help of ABAPer.

Pricing condition deletion in CRM

Hello!
We're trying to delete pricing condition using CRMXIF_CONDITION_SEL_DELETE, but we are able to delete only a number of condition records at once.
I've read the documentation for this FM, but i still can't understand how to delete particulary one pricing condition from condition table.
Can anybody help me?
Tnank you!

Hi,
I used function module 'CRMXIF_CONDITION_SEL_DELETE' to delete condition records. Below is the sample code,
Data: ls_data           TYPE bapi_ct_sel_opt_msg,
       lt_range          TYPE TABLE OF bapi_ct_cond_rec_sel_range,
       ls_range          TYPE bapi_ct_cond_rec_sel_range,
       lt_return         TYPE bapirets,
       lt_ret            TYPE bapiret2.
    ls_data-object_representation   = 'E'.
    ls_data-sel_opt-ct_application = 'CRM'.
    ls_data-sel_opt-object_task     = 'D'.
      ls_range-fieldname    = 'ZZOPPORTUNITY_GUID'.
      ls_range-r_sign       = 'I'.
      ls_range-r_option     = 'EQ'.
      ls_range-r_value_low = lv_guid.
      APPEND ls_range TO lt_range.
      ls_range-fieldname    = 'KSCHL'.
      ls_range-r_sign       = 'I'.
      ls_range-r_option     = 'EQ'.
      ls_range-r_value_low = 'ZZNE'.    "cond type
      APPEND ls_range TO lt_range.
      ls_data-sel_opt-range = lt_range.
CALL FUNCTION 'CRMXIF_CONDITION_SEL_DELETE'
      EXPORTING
        data   = ls_data
      IMPORTING
        return = lt_return.
* Committing the transaction
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      IMPORTING
        return = lt_ret.
Regards,
Arun

Implement pricing conditions GAU1 and GAU2

Dear All,
I want to implement pricing procedure for precious metals.
Anyone who has implemeneted the procedure at their end please guide me towards the same .
In PO I am getting following error in condition type GAU1 Inactive status as "X" and message as " Inactive via formulae of incorrect "
Please help
Thanks
Garima

Actually i haven't worked on metal prices...but once i had faced same type of error in my freight condition types...SAP responded with some solutions which i am posting...please see whether these are useful or not:
(1) Condition row is inactive
The condition type (group condition or item condition) is listed with or without a pricing result in the condition row on the condition screen for the subitem. However, the condition value is ignored. On the condition details screen (double-click on the condition row), an indicator is set for 'Inactive'.
(1.1) Inactive indicator 'A condition exclusion item'
You have selected an exclusion procedure at subitem level for your freight cost price determination schema. The condition type with inactive status 'A' was excluded using this procedure in favor of another condition type (set as inactive).
Check: In favor of which condition type or condition exclusion group was the condition type in question excluded?
=> Use Customizing transaction T_32 to determine the condition exclusion group to which the relevant condition type was assigned and use Customizing transaction TOK8 to determine the exclusion procedure assigned to the price determination schema.
(1.2) 'K - Inactive due to calculation basis/shipping material type'
An automatically determined or manually created condition type is set as inactive (inactive indicator 'K'), even though a valid condition record was found according to the analysis.
Check 1: Do all handling units in the subitems belong to a 'material group for packaging materials' that is assigned to this particular packaging material type in Customizing? The calculation base of the condition type refers to handling units (calculation bases C, E or F) and, in Customizing (transaction T_06), a packaging material type (synonym: shipping material type field T685A-VHART) was specified for the condition type?
=> Material numbers are assigned to 'material groups for packaging materials' in the material master (transaction MM02). 'Material groups for packaging materials' are assigned to packaging material types in Customizing: Transaction VHZU or IMG -> Logistics General -> Handling Unit Management -> Basics -> Define Allowed Packaging Materials
Check 2: Was a valid condition record for this condition type found in all subitems for the calculation base used?
=> Extend the condition pricing data (transaction TK11) so that valid condition records can be found for all subitems. If necessary, use a price 0.
Check 3: Was the condition type only created manually for individual subitems?
=> Usually, manual conditions must be created for the calculation base in all subitems, with the value 0 if necessary. If changes were also permitted at header level for an item condition (in Customizing transaction T_06), you can automatically create identical entries in all subitems of the calculation base by creating the condition at header level. You can then adjust these templates (with the value 0 if required) at subitem level.
Notes: For background information and options for 'Inactive K', see also note 318775. For the system response in the case of manual changes to freight conditions, see consulting note 773038.
(1.3) Inactive 'L - Condition exclusion header or inactive at header level'
The condition type could not be evaluated as a group condition or was excluded as part of a header exclusion because of another condition type.
Check 1: Could the condition group be evaluated at all?
=> On the condition screen of the header conditions (enter '=kkon' in the command field), check whether different subgroups have been created for the condition type. If this is the case, several condition rows will be displayed for the same condition type. Also check the Check the scale input values in the individual condition display (double-click on the condition row).
Since neither the price determination analysis nor the condition record display is available at header level, you must check the price table for the condition type using a subitem: Is there also a valid scale level for each scale input value? The lowest scale level is often missing in from-scales and the highest conceivable scale level is often missing in to-scales. For example, a to-scale of 'to 30 TO' cannot evaluate any shipments with 31 tons. You therefore need to extend this scale to 'to 99999 TO'.
Check 2: Did you select an exclusion procedure for your freight cost price determination schema at header level?
=> Use Customizing transaction TOK8 to check whether the indicator 'A - header exclusion' was entered in the relevant column for the exclusion procedure that is assigned to the price determination schema. If this is the case, the group condition inactive status 'L' may have been excluded in favor of another group condition type using this exclusion (set as inactive).
Use Customizing transaction T_32 to determine the condition exclusion group to which the condition type in question was assigned and use Customizing transaction TOK8 to determine the condition type or condition exclusion group in favor of which the group condition type in question could have been excluded.
Check 3: Are you using your own scale or condition formula for a multi-dimensional group condition?
=> You may try to analyze the import parameter KOMK or KOMP for a group condition in this formula. However, these parameters are not filled in group processing: '...The components komk and komp are initial during processing of group conditions...' ('i - Formulas' button on the 'Scales for Conditions' detailed screen in Customizing transaction T_06).
The inactive indicator KINAK is set by default to 'T' for group processing (inactive at header level) and is converted to the more general 'L' by the subsequent price determination.
(1.4) 'X - Inactive via formulae or incorrect'
If an error occurs during processing of multi-dimensional conditions (for example, during conversion to scale units or in a customer-specific formulas for scale bases), the condition is usually set to inactive status 'X'.
Check: Are all formulas used in connection with this condition (condition base formula, scale base formula, condition value formula) error-free?
(1.5) 'Y - Inactive because of subsequent price'
According to the price determination logic in SD, there can only ever be one valid price in a pricing procedure. All other conditions are surcharges or discounts in some shape or form. Accordingly, the last, valid pricing condition (valid condition record and not equal to zero) always applies. All pricing conditions in the schema with a lower level number are set to inactive status 'Y inactive because of subsequent price'.
Check: If the required pricing condition was unintentionally set to inactive status 'Y' by a subsequent pricing condition, you must decide (using an exclusion procedure, if required) which of the pricing conditions is varied. All pricing conditions with inactive indicator 'Y' are included in the exclusion procedure.
Regards,
Indranil

Configuration enabling goods receipt of purchasing pricing condition

Hi Gurus,
a) If I check the "Accruals" flag for a pricing condition, then only, that pricing condition will create a delivery costs goods receipt, while we receive the purchase order having that condition type......is it correct?
b) Is any other configuration change critical for a condition type to generate it's goods receipt?
Thanks,
Kumar

Hi Kumar,
Just check your condition type in tcode M/06 whether all the below mentioned parameters are correct..
In control data 1 -
Cond. class - A (Discount or surcharge)
Calculat.type - A (Percentage)
Cond.category - B (Delivery costs)
Plus/minus - A (Positive)
Thanks

Pricing condition (CVD) in imports pricing are being non-inventorised

Similar Messages

Maybe you are looking for