Access not made for condition type

we have a condition type ztax (Non Setoffable Tax) con. class as discount or surcharge. for this condition we created a access seq ztax having table one table with one field as tax code
requirement is, if user enters tax code this condition type should come automatically in PO.
in mek1, for different tax code we have maintained diff. tax %. but after entering the tax code, this condition type is not coming in PO.
if i check in analysis, system says"access not made (initialized field).
thanks
manoj gupta

hi sunitha
yes i have assigned the access seq ztax to this condition type. what next?
thanks & regards'
manoj gupta

Similar Messages

  • Requirements not fullfilled for Condition type - Pricing Procedure

    When I am doing the pricing procedure, the error thrown is "Requirements not fullfilled for Condition type". Can any one suggest how to fix this problem ?

    Hi Sunil,
         Please first of all check the condition type in Pricing Procedure. In condition type column check the requirement. Here conditon is,  once requirement is fulfilled which you have mentioned in the condition type then only it will be executed. Take a help of  ABAP'er regarding this requirement if it is customized requirement.
    We should know the purpose of requirement in condition type.
    Venkat.

  • Field is not known for condition accesses - While save sales order

    Hi Gurus..............
    I am getting error while i save my own sales order that Field is not known for condition accesses. Then the screen automatically come to SAP Easy Access screen
    Pl let me know
    Thanks in advance

    Hi Selvi,
    try this way, once you enter the required data for the sales order go to item conditions screen. Click the analysis button and see the conditions determined. You would find some of the condition deriving a value and some may not. It will give details as to how the records either determined or whats missing to determine. Make analysis for the conditions that you feel should have got determined by going to VK13 if everything is correct. Else try maintaining with VK11. Now it would tell you if any field/ condition table is missing which was initially constructed as part of the access sequence for this conditino type.
    regards
    sadhu kishore

  • Why not all billing documents are posted to CO-PA for condition types?

    Hello!
    I have following problem.
    In transaction KE4I I have configured several condition types to post for specific value fields.
    For some billing types it works but for some doesn't work.
    For all domestic invoices it works but for abroad invoices it doesn't work.
    Billing documents for abroad invoices are also posted to CO-PA but for another value fields, not for that I expect.
    Where is problem?
    I am waiting for help.
    Best regards
    Bogdan

    Hi.
    In both pricing procedures there are same condition types. The only difference was check box "Condition is used for statistics".
    After marking this check box it still doesn't work.
    There are placed the same condition types in all billing documents (domestic and abroad) . So I am supprised that for domestic billing documents field value in CO-PA is calculated for condition types placed in KE4I.
    But for abroad billing documents the same field value is not calculated for the same condition types placed in  KE4I.
    Where is a problem?
    I need help.
    Best regards
    Bogdan

  • Field KOMP-ZZPRCTR1 is not known for condition accesses"

    Hello friends,
    In a sales order if I put the material I got the error below.
    "Field KOMP-ZZPRCTR1 is not known for condition accesses"
    I am not able to incert that perticular material into sales order.
    Kindly suggest how to go ahead.
    Regards,
    Kunal

    Hi,
    You need to add the new field  ZZPRCTR1 in the KOMP structure using SYSTEM MODIFICATIONS
    Please check the system modifications for this
    http://www.sap-img.com/sap-sd/add-a-field-to-new-condition-table-in-pricing.htm
    regards,
    santosh

  • Access Not Made (Initialized Field)

    Hello Experts,
    I have come across a generic problem. I have defined a new field (material Type - MTART) in the field catalog and included the same in the new condition table (Country / Destination country / Material type / Cust tax cla / Material tax cla ). The condition table is included in the already defined access sequence. This access seuqnce is assigned to the tax conditn type ZWST.
    A condition record maintained for the conditon type ZWST for newly defined access. When I create a sales order, the ZWST condition type is not picking up the record maintained for this access. Error message  - 102 Access not made (Initialized field)
    Subsequently, thecondition value from the next access is picked up.
    Question - Did I miss any step during creation of a new field in the field catalog?
    Thanks in advance for your kind help. Be assured to get the full points if answered satisfactorily.

    Hi
    Error message - 102 Access not made (Initialized field)
    If you are getting this msg in a sales order in the analysis why a particular condition type value has not been picked
    Then this will not be a Error message and also not warning message
    There will be a yellow exclamatory mark
    Access not made (Initialized field)  conceptually means
    Suppose if you maintain a condition record say a condition type ZR00 for a sales org 1000 and DC 10 for a material X the price is Rs1000
    Now in sales order the value for ZR00 is not coming and the message is Access not made (Initialized field)
    This means that in  the sales order either sales org is not 1000 or DC is not 10
    Simply it means that condition record is maintained for sales org 1000 and DC 10 but your sales order is not created for those data
    hence the access is not executed because the initialized fields sales org 1000 and DC 10 is missing
    Hope you are getting my point
    If it is understood then you can analyze your sales order and solve your error
    Reply whether this input has been useful to you
    Regards
    Raja

  • Error 102 Access not made (initialized field) during pricing analysis in item level of Sales Order

    Hi SAP Experts,
    Good day!
    I am facing an issue in Pricing Analysis of a Sales Order Item level which is Error 102 Access not made (initialized field).
    Details for ZICT condition Type:
    Access Details:
    *ZINTER is originally used in billing and was decided to also use for order.
    There is no problem involved in billing.
    Please take note that I already found other discussions and an OSS Note regarding this issue and applied the suggested solution. But still I encounter an issue in the order created.
    After implementation of the proposed solution which is moving Material type(MARA-MTART) and Valuation Class(MBEW-BKLAS) to the corresponding fields TKOMP-MTART and TKOMP-ZZBKLAS.
    ZICT Condition Type details:
    Access details:
    As I mentioned above, I already followed steps in previous discussion.  It seems odd that there is still a problem. Can you please enlightnen me up and advice if there are things that I still  need to know.
    I am hoping for your response and help with this matter.
    *NOTE: The development Box that I am using is an ECC6 Upgrade development system

    Hi Please find the attached screenshot. Hopefully this will be of help.

  • Sales Order Pricing : Access Not Made (initilized field).

    Dear members,
    In my sales order for a condition type, I am getting message as access not made (Initialized field) and there is a yellow Exclamation mark on one of the field (field name is price group).
    I have a condition record maintained, But why I am getting this message.
    I have read some threads here and saw my access sequences and went down to table fields, all table fields are correct. (meaning The see komk fields are assigned to document fields).
    If this yellow mark comes, is it be configuration error or a data error ?
    please let me know. Thank you
    Madhu.

    Hi Madhu
    Go to the access sequence and check wheather sub-routines has been maintained.in the access sequence  or Exclusive box has been checked for any key combination. If it has been checked then remove that check box and then create the sales order. then there wont be any problem
    Regards
    Srinath

  • Unable to manually change the amount for condition type PB00

    Hi Gurus,
    My client is using ECC5.0.
    Here when I try to change the amount for condition type PB00 using transaction ME22N, I am not able to change the value. I donu2019t get any error, but as soon as I change the value and press Enter the system replaces my entered value with the original value.
    Confusing part is that I am able to change the amount of condition price PB00 manually using transaction ME22. I donu2019t have any such problems there.
    Also I am able to manually change the amount of condition type PBXX using ME22N.
    Only in the case of PB00, if I use ME22N to manually update the amount I am not able to change it.
    Kindly help me, to find a reason as to why this could be happening, and correcting if possible?
    Thanks in advance,
    Imran

    Hello Imram,
    The purpose of maintaining 2 condition types  ie PB00 and PBXX in  a pricing procedure is that PB00 is automatic gross price determination and PBXX is manually giving gross price.
    If you go to T.Code : M/06 and check the condition types, you can see that PB00 will be having an access sequence but not PBXX.
    So if you have to manually give the gross price, you have to use PBXX.
    Regards

  • Requirements are not fulfilled for condition EDI1

    Hi Gurus,
    We are trying to add (EDI1 confirmed qty) in the PO item conditions.
    We are using the standard PO schema which has these condition type. It has no access sequence attached to it and hence it is a manual entry.
    If we try to add that condition type in the PO it throws me the following error :
    "Requirements are not fulfilled for condition EDI1
    Message no. V1215"
    Kindly let me know what I have to maintain at the earliest.
    Best Regards,
    Ravi.

    You incorrectly filling item information with condition value. All quotation related pricing need to pass QUOTATION_CONDITIONS_IN table paramete of BAPI.
    Try it and the problem get solved.
    Cheers
    Nilesh Shete

  • Question for condition type

    I have a condition type that doesn't have an access sequense.
    The condition type is both header and item condition and I allow mannual changes.
    Though when I use it, I have the following problem.
    I want the user to enter manually the condtion type in header. There are case though where for a specific line the condition type should be changed. At that point I am not able to change the amount of the condition type since it is only in display mode.

    Dear Stilianos,
    As per my knowledge, you cant have a condition type for header as well as for item. In the sense you can make it so but, as you know header condition would be distributed proportionately at item level. Moreover, you wont be able to change the same at item level.
    As already told by our friend you can either have additional manual condition type for such cases or you can enter the same condition type for that specific item so that earlier price would be inactive.
    > For a specific reason the last item of the sales order that has a discount of 20% due to the condtion type set at header level, I want to make it 30%
    In this case, you can enter the same condition type with new value i.e. 30% for that specific item so that earlier discount i.e. 20% would be inactive.
    Or enter additional new manual condition type with the variation i.e. 10%
    Hope you get some inputs
    regards,
    Sagar

  • Requirements are not fulfilled for condition PI01

    Dear SD guru,
            When i create sales order,it prompt that 'Requirements are not fulfilled for condition PI01'.
              For the specifical requirement,i use the intercompany processing.I want two invoices in this sale document,onr for customer,the other for internal processing.So i need two condition types for two price,i use the condition type ZABC&PI01(for internal) in the pricing procedure.But,when i  create sales order under the configuration,it failed.
          How can i solve the problem?
    TKS!
    Edited by: stephen chow on Sep 8, 2008 9:35 AM

    We need to change the condition class from prices to other like discount or surcharge in the condition type.
    For ex: If it is shipment cost document got to goto T_06 select the required condition and change the condition class and do not select grouping conditions..
    Thanks,
    ratna
    Edited by: ratna edpi on Oct 24, 2008 6:04 PM.
    Edited by: ratna edpi on Oct 24, 2008 6:05 PM
    Edited by: ratna edpi on Oct 24, 2008 6:07 PM

  • Currency conversion issue for condition type

    Hello,
    I am creating two invoice document.
    1. Customs Invoice (ZCDS)
    2. Inter company invoice.(IVA)
    both the invoices should be similar. Same pricing procedure is used to create both the documents but in Customs invoice YUMU condition type is not getting converted whereas in IVA the condition type is getting converted. Can anyone tell me the possible reason for this?
      ZCDS
    IVA
    Regards,
    Jagjeet

    Hi Jagjeet,
    For IVA invoice type -(For condition type- YUMU)
    Below highlighted part of code is changing KSTEU from 'E' to 'C' for IVA invoice using std prog RVIVAUFT.
    For ZCDS Invoice Type -(For condition type- YUMU)
    Program RVIVAUFT is not called since ZCDS is not trigerried using Output type unlike IVA.
    Hence KSTEU is not getting updated from 'E' to 'C' in case of ZCDS.
    To solve your problem write code in User exit - userexit_pricing_copy to change  konv-ksteu to 'C' for YUMU condition type at runtime.This will definately solve your problem.This will ensure you get correct/same condition value for IVA and ZCDS...:)
    Regards,
    Vikas Mulay.

  • Authority check in for condition type

    Hi
    What do you mean by an authority check on condition type.. especially Pricing..
    There are authority check that are embedded as Reqt and AltCTy in the IMG at the pricing procedure level for different condition type.
    Could someone explain me what they are for..?
    Thanks
    Jac

    Hi,
        authority check is the std sap methodology of check the permitted authorisation values for every transaction  and every user.
    here in this example;authority object is used to maintain or change condition record for allowed condition types.
    scenario eg;if we maintain create value for user mukund for pr00 condition type ,system allows me only for creating .if we maintain change value for user sherin for condition type,system allows to change the values.
    net net i can create and u can change ,not visa-viz or any body else cannot do it.
    hope this is clear.if it helps  REWARD!!!!!!!

  • Restriction for condition type

    Hi,
    I want to restrict some users to do not change the basic price (PR00) in sale order (VA01/VA02), Plz let me know how I can do this.
    regards,
    sps.

    The objects concerned have to be:
    V_KOND_VEA Maintain condition: Auth. for use/appl./cond.type/table -- (Deals with condition records)
    V_KONH_VKO Condition: Authorization for Sales Organizations
    V_KONH_VKS Condition: Authorization for Condition Types
    But in the standard system VA02 has these objects set to No check in SU24. You may have to modify this to Check/maintain and then maintain the values in the users role. Like you can have:
    Object : V_KONH_VKS Condition: Authorization for Condition Types
    Condition Type: PR00
    Actvt : 03
    Thanks & Regards
    JP

Maybe you are looking for