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

Similar Messages

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.

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

Sale order- Pricing -Access Sequence

Hi Gurus,
While creating Sale order, the price is picked from the Pricing procedure and Condition records maintained.
In PR00- Material price and Customer-Material special price is maintained in VK11.
So the system picks Customer Material combination price and the same we can see in the Item level conditions-Analysis for pricing and can also see it fetched record from where.
So for this Client wants in the following way: POPUP MESSAGE
At Sale order Warning Message that Price is taken from Which List- Normal Price List or Special Price List for Customer and Material combination
Is there some way to do this?
Thanks in Advance.
Best Regards
Sri

Hi,
U have to take ABAPER HELP No doubt please use this input if tis use full .
User Exits For Price Determination
USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ)
This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document.
This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing.
This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA)
You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals.
This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_KZWI (module pool SAPMV61A, program MV61AFZB)
You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields.
This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_KOPF (module pool SAPMV61A, program MV61AFZB)
You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields.
This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_LEER (module pool SAPMV61A, program MV61AFZB)
You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields.
This user exit is also used in order processing.
USEREXIT_PRICING_CHECK (module pool SAPMV61, program MV61AFZA)
You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA)
In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA)
You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB)
This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB)
Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB)
In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
USEREXIT_XKOMV_ERGAENZEN_MANU (module pool SAPLV61A, program RV61AFZB)
You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB)
This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB)
This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA)
You can change the KONV fields for copied price components
With best regards,
venkataswamy.y

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

Excise CIN amounts not updated in TAX field in Sales Order Pricing

Hi,
I am not getting the Excise Amount [CIN] i.e BED + ECS + SHE Cess in Tax field of Sales Order Pricing Procedure. only Sales Tax amount is showing.
Plz let me know, where did I go wrong in the Configuration.
Thanx in advance.
with best regards
Jabbar

Abdul,
What you have said is correct with regards to condition record creation, excise rate picking and its calculation.
On clicking the "analysis" button in pricing screen (Sales item details --> condition -->) try to analyse for each condition type
we can resolve it
Check within the condition type whether you have entered condition category = D, it must be like this
Cond. class = D Taxes
Calculat.type = A Percentage
Cond.category = D Tax
In Pricing Procedure Activate "Statistical" Indicator, it will definitely appear in the tax field.
Regards
Sathya

Partner VN is not picking in sales order pricing

Hi
My client requirement is system has to calculate commission amount depend on the combination of sold to party and commission agent(created as vendor).
I defined one condition type by adding access sequence in that access sequence i have maintained one table which is having fields of VKORG, KUNNR, LIFNR. and i have maintained condition records with this combination,
And i maintained VN partner in CMR & it is coming into sales document header and item
Even thou system is not picking the condition value, in analysis system is not picking the vendor number (access not made)
can any body suggest me on this issue
regards
bvdv
Edited by: bvdv on Oct 14, 2008 3:13 PM

Vendor will not be automatically populated in the pricing stuctures. You will have to use exit USEREXIT_PRICING_PREPARE_TKOMK in program MV45AFZZ to fill the pricing communication structure.
Regards,
GSL.

Country of Delivering Plant is not showing in Sales Order Pricing Analysis

Hello All,
I have created a new condition table with the field Country of Delivering Plant (KOMK-WKCOU).
But in the sales order pricing analysis this field is not fetching the country of the plant (it is showing the Yellow color exclamation icon).
This is a standard field, I am not able to understand why it is not fetching this field.
I have used the same field for tax condtions in my previous projects as well, there it worked well.
Even I have activated the KOMK structure in SE11 also, but still the same problem.
Can anybody tell me how to resolve this issue.
Thanks & Regards,
Sreehari.

Rightly suggested by Shiva.
As plant determines at item level.
So, instead of KOMK-WKCOU, field should append in KOMP.
FYI, for checking any inconsistency in condition table, you can use TCode VK+C.
Regards
JP

Control Sales order Pricing Date with Delivery GI Date

Is it possible to have a control that ensures the Actual GI date in a delivery is not more than a number of days from the sales order pricing date?

Hi,
To have restriction in actual GI date in transaction VL01N . Please find the user exit for VL01N , you can use one which are marked as bold . Kindly take the help of abaper to put the validation or logic as required.
V02V0001   - Sales area determination for stock transport order
V02V0002   - User exit for storage location determination
V02V0003   - User exit for gate + matl staging area determination
V02V0004   - User Exit for Staging Area Determination (Item)
V50PSTAT - Delivery: Item Status Calculation
V50Q0001   - Delivery Monitor: User Exits for Filling Display Fields
V50R0001    - Collective processing for delivery creation
V50R0002    - Collective processing for delivery creation
V50R0004    - Calculation of Stock for POs for Shipping Due Date List
V50S0001    - User Exits for Delivery Processing
V53C0001    - Rough workload calculation in time per item
V53C0002    - W&S: RWE enhancement - shipping material type/time slot
V53W0001   - User exits for creating picking waves
VMDE0001 - Shipping Interface: Error Handling - Inbound IDoc
VMDE0002 - Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003 - Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004 - Shipping Interface: Message SDPACK (Packing, Inbound)
Hope this will help you to resolve your issue!!!!
Regards,
Krishna O

User exists sales order pricing

How to find out SALES ORDER PRICING USER EXISTS already predefined
Thanks
munna

Hi,
Check below link for all user Exists in SD.
https://wiki.sdn.sap.com/wiki/display/ERPLO/SDUserexits
User Exits for Price Determination
Routine      - Module pool or function group - Include - Description
USEREXIT_PRICING_PREPARE_TKOMK      SAPLV60A      RV60AFZZ      This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document. This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_PRICING_PREPARE_TKOMP      SAPLV60A      RV60AFZZ      This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing. This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_FIELD_MODIFICATION      SAPMV61A      MV61AFZA      You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals. This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_KZWI      SAPMV61A      MV61AFZB      You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields.
This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_KOPF      SAPMV61A      MV61AFZB      You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields.
This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_LEER      SAPMV61A      MV61AFZB      You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields.
This user exit is also used in order processing.
USEREXIT_PRICING_CHECK      SAPMV61      MV61AFZA      You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
USEREXIT_PRICING_RULE      SAPLV61A      RV61AFZA      In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
USEREXIT_CHANGE_PRICING_RULE      SAPMV61A      MV61AFZA      You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
USEREXIT_XKOMV_BEWERTEN_INIT      SAPLV61A      RV61AFZB      This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
USEREXIT_XKOMV_BEWERTEN_END      SAPLV61A      RV61AFZB      Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
USEREXIT_XKOMV_ERGAENZEN      SAPLV61A      RV61AFZB      In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
USEREXIT_XKOMV_ERGAENZEN_MANU      SAPLV61A      RV61AFZB      You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
USEREXIT_XKOMV_FUELLEN      SAPLV61A      RV61AFZB      This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
USEREXIT_XKOMV_FUELLEN_O_KONP      SAPLV61A      RV61AFZB      This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
USEREXIT_PRICING_COPY      SAPLV61A      RV61AFZA      You can change the KONV fields for copied price components.
Note: as of Release 4.6A, the display of the condition screen (screen 6201) has been converted from a full screen to a subscreen. The full screen is included in the SAPMV61A module pool, the subscreen, however, in program SAPLV69A. Therefore, instead of MV61AFZA and MV61AFZB, the user exits in LV69AFZZ should be used. For reference, see OSS note 313569.
Best regards,
Anupa

Sales Order Pricing User Exit Problem

Hi,
I am facing a problem related to coding in Sales Order pricing user exits. Scenario is as mentioned below:
Based on Material Entered and Sold To in Sales Order, auto determination of a manual pricing condition happens. For doing this, coding has been done in USEREXIT_PRICING_PREPARE_TKOMP by changing XKOMV table. Auto determination of the manual price is happening properly.
From Sales Overview Screen when user goes to the Conditions tab, Net Value is not getting calculated. When we navigate away to Schedule line tab and then come back to COnditions tab, Net Value is automatically getting calculated.
AM i missing something in the coding part? As the data is getting populated automatically I guess some piece of code needs to be triggered. Can anyone shed some light into this.
Thanks in advance,
thunderans.

Prabhu: After filling in XKOMV structure, I am calling FM PRICING. On doing this, the Sales Pricing is getting calculated but even then net value of order at header i.e VBAK-NETWR is not getting populated when we are in Sales Overview screen. When, I am getting into Conditions tab and coming back to Sales Overview screen, Net value is getting populated correctly. This portion of everything not getting populated at the same time is bothering me. The pricing conditon that I am filling is a manual pricing condition.
I put a breakpoint after FM PRICING which correctly populates XKOMV structure. How do I properly update Order Net Value in Sales Overview screen wihtout having to navigate to any other tab?
Nicklas: I am looping at Order line within the user exit USEREXIT_PRICING_PREPARE_TKOMP and determining price. Once all line items are processed, I am using the FM PRICING for calculating Sales Prices.
J@Y: Request to send me a bit more details into your approach.

Need to create a sales order that does not create demand

Hi,
We need to create a no cost sales order - that does not create demand
In our current set-up when we try to create a no cost sales order with a material ( It Cat = Norm) we see demand being created in MD04
What configuration settings will allow us a deliverable order - that does not create demand (no MRP run?)
Thanks,
SM

Hello,
For this set of requirement i think the best option would be to configure a New Sales Order Type and a new Schedule Line Category. In VOV6, While you are defining a new Schedule line category in the transaction flow make sure to switch off the three check box.
Transfer of requirements / Begin assembly order from SD
Availability check for sales
Product allocation active
Then when we are assigning this newly defined Schedule line Category to Item category, make sure to leave the field of MRP Type as blank in VOV5.
Regards,
Sarthak

Block return sales orders or credit notes?

Hi,
Could someone please explain how I block return sales orders or credit notes?
Also is there a way of searching which sales order documet types have been used for credit notes?
Thanks

Hi Friend,
The billing block is comming from the tx. VOV8 -> choose the Order type -> billing
block -> you could set billing block here.
In Shipping column, there is also a field Delivery block where you could set delivery
block for the order type.
Or you could also set delivery block and billing block manually when you create the order.
You could check order type which is used as return or credit memo request by following way:
SE16 -> TVAK -> use selection criteria VBTYP = H and K
H Returns
K Credit memo request
Then excecute, you could get the order type you want.
Best regards,
Alex

Sales order number in not coming as a text in Accounting Document

Hi Friends,
Sales order number in not coming as a text in Accounting Document in INSTALLMENT BILLING PROCESS
is there any config missing for this doc number
Pl advise me
Raju

HI Prem,
Please understand my query.
In VF01 in accounting document we can see the text document field.
Here i need the Sales order number as a Text field.
But it is not coming over here
Pl advise me
Raju

Sales order stock does not exist error during PGI

dear sir,
we have two plants 1010 and 1020,we are using variant configuration for our finished goods
we want to make the sales orders in 1010 plant and we manufacture the machine in 1020 plant.
so we want to dispatch machine from 1020 plant (shipping point),eventhough we make sale order in 1010 plant.
but while doing PGI ,system shows one error message "Sales order stock does not exist" message 184,area M7.
if we see in MMBE stock of finished good is available in 1020(made 412 E movement)
how to resolve this
thanks and regards
srinivas pai

There can be two reasons for these kind of error
- Your sales doc while creating this order & your item category is marked with special stock indicator as E and after this order is created you have not reserved stocks in your plant against this order. This reservation can be done in tcode MB1B movement type 412 E.
- Let say, if it is reserved then check the same in tcode MMBE stocks reserved for your sales order.
Otherwise reservation you may have done properly with correct movement types with special stock indicator E. But while creating the your sales order with item category may not have been marked with special stock indicator E. In this case even though the system has stocks reserved for that order and that order when comes for PGI system doesn't sense.
In either of the case, you have to again do the process.
Hope it can assist you.
Thanks & Regards
JP

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

Similar Messages

Maybe you are looking for