Error message - 102 Access not made (Initialized field)

[former_member185462]

Hello,

We have condition type which have been in long use and there is no change done to condition type ie no new field catalogue added.

Condition record exists,but condition is not determined.

On the analysis screen,Error message - 102 Access not made (Initialized field)

On the field value is not determined,it is in yellow colour.

This happens in production system,no issues with quality.

No new transport is moved related to pricing structure.

Thanks,

MP

[VeselinaPeykova · Accepted solution]

pradeepmani please, instead of retelling what you see on the screen - just upload the screenshots!

It is hard enough to troubleshoot a problem with no access to the system, no knowledge about the configuration and development, no clue about master data and transactional data and no idea what field is not filled in what kind of documents...

For already created invoices released to accounting the conditions cannot be changed (of course), but the determination analysis runs as a simulation of pricing type 'B' as explained in 363212 - "Pricing analysis" mode of operation.

If you have not read the note already, I strongly recommend that you do - it will help you understand the concept and will answer some of the questions that you seem to have.

Still, for the main problem (the condition is not determined because of initial values in KOMK/KOMP) - if you are struggling with finding out how the komk/komp value was filled before the problem started to occur - why don't you debug by following the guide that I already suggested?

You have a test case in QAS where the value is filled correctly, you can debug it and see how it works.

You have cases where this KOMK/KOMP field is not filled in PRD, you can still debug it without posting any documents.
You should be able to perform the troubleshooting on your own or with the assistance of an ABAP developer.

[former_member185462 · Accepted solution]

error-pricing.png

screen shots on analysis of 2 Invoice is attached.

Pricing got determined for old own,but for new one it is not determined.

When you closely note there is yellow indicator for both.

[VeselinaPeykova · Accepted solution]

pradeepmani you are hiding the most important part of the analysis screenshot - what is the field that is not determined.

And there is no outcome posted of the suggested troubleshooting (the debugging steps).

Please, follow the advice that I have given so far and perform the investigation with the help of an ABAP colleague (I suppose that showing the actual data is a security concern in your case).

I cannot help you further, sorry.

[former_member185462]

It is a Z-field which is added to pricing structures.

The field gets picked based on Z-Table (Combination of Plant+Shipping point=Zfield)

Since the entry in Z-Table was removed it was showing access not made (initialized error)

After maintaining the value,it was resolved.

Only surprise factor was even though saved Invoice document(A/c ng document generated),it was showing condition record found and in pricing analysis part it showed condition record found ,but initialization message was there and showed pricing error,it means even for successful documents also if we click analysis (Display mode) it will once again check for values.

[VeselinaPeykova]

It is a bit difficult to tell what can be the reason without access to your system, but if configuration and development has not changed the logic of determining this field, then the first thing that I would check is whether the master data was changed or if the data in the order was modified by the user.

For example, if the determination of the condition depends on price group (KONDA) - check if the field is with initial value in the sales order. It could be that the user manually changed it for some reason, or that the customer master data was modified.

Or you can have customer hierarchy used in pricing and somebody changed the hierarchy assignments, for example you rely on HIENR04 for pricing, but the partners are not determined, then the pricing condition determination will also fail.

It is also possible that some fields are set or cleared by custom coding. Just because a recently imported transport request is not directly related to pricing, it does not mean that it cannot affect it.

It is also possible to determine, set or clear the value of specific pricing fields via Data Determination in the Access. I have used this technique a few times exactly for increased flexibility in pricing - e.g. I can have a statistical condition with condition validity that sets a different material tax classification or a different price list type that is used in another condition type positioned after this statistical one.

As a start, check what is the field that is with initial value and how it was determined before the problem started to occur. Then try to create an order (without saving it, of course) and check if the field is determined correctly. This might help you dismiss the theory that the users modified manually the document before saving (I assume that before doing this you have checked the master data for changes).

If still no luck - you can always debug (yes, in PRD there is a bit more complicated to request approval for debugging a specific issue, but if you cannot find the root cause via other techniques, they will probably let you do this). In this case refer to this excellent debugging guide: Pricing Programs and their logic – Help for debugging.

[former_member185462]

I checked for old orders and Invoice for which condition record was determined earlier for the same table combination,even accounting documents were generated for those.

Now when i checked analysis part of old Invoice,it shows condition record determined for step number.But still the the value in mentioned against the filed is initial (Yellow Icon),I am surprised in spite condition getting determined,i could see condition record is determined against the condition type.Why should it show like this for already determined ones.