cancel
Showing results for 
Search instead for 
Did you mean: 

Entry A V XXXX does not exist in T683 (check entry)

Former Member
0 Kudos

Hi friends,

I have deleted the pricing procedure entry(KALSM) in the VBAK table and when iam trying to insert the same the system triggers error "Entry A V XXXXdoes not exist in T683 (check entry)". The entry initially was showing up in the table and now not allowing to reinsert. Entry exists in T683 even then getting the same error.

I have checked all the customizing settings also.

Please Help.

Regards

Vamsi

Accepted Solutions (0)

Answers (2)

Answers (2)

jpfriends079
Active Contributor
0 Kudos

This is the standard system response, generally, it can be b'coz of missing pricing customizing after upgrade.

Each table of the R/3 system is assigned to a 'delivery class', which can be determined using transaction SE12 'Dictionary: Display table'.

The delivery class controls the transfer of data in the table for installations, upgrade, client copy and for transport between customer systems.

- Check whether the missing Customizing entries exist in the SAP standard Customizing client 000. If this is the case, copy it to the clients you use. In general, the transfer of a Customizing entry in the area of SD pricing/condition technique has to occur manually. The cause of this is a mixture of client-dependent and cross-client Customizing which prevents an automatic transport, for example, by means of 'Client copy acc. to transp. request' (transaction SCC1). For a detailed explanation of this problem, among other things, see the 'BC manual client copy' documentation, which you can access directly from transaction SCC1.

To reduce the manual maintenance effort, you can also use the comparison functions for certain Customizing settings such as the condition types or pricing procedures.

The corresponding release note describes, which Customizing setting is required to activate a new function itself. If the Customizing entries described here are also missing in client 000, contact SAP Support.

- Changes to SAP original Customizing entries in tables of delivery classes E, S, W should be avoided in general since these are lost during the upgrade/client copy. You can only restore the data by means of a manual subsequent maintenance. To avoid this constellation, we recommend to copy the required entries first (to the customer namespace) and then change them.

For other details check SAP Note 217012.

Thanks & Regards

JP

Former Member
0 Kudos

Hi

Actually this has occurred as the entry in the table was manually deleted. The pricing procedure does exists and we have been using the same from a very long time.

Now the issue is resolved, we have created a programme to update this filed in the VBAK table.

Regards

Vamsi.

Former Member
0 Kudos

Hi,

Please check the entry in V/08 whether the Pricing procedure available or not

Please re-create by deleting it and save

regards,

santosh