Contracts getting saved but when it change VA42- it gives error message

[Former Member]

Hi Experts,

Any one encountered following error while contracts change VA42.

While Creating Contracts VA41- We are selecting Contract start date and end date for one year

If we save the Contract is getting saved and immediately we are getting Message Like u201C

u201CExpress document u201CUpdate was terminatedu201D Received from authoru201D

And if we go for VA42- change contract we are getting error like u201CSD document XXXXX is not in the database or has been archivedu201D

Message no. V1302

Diagnosis

You get this message in the following situations:

u2022 The SD document you have specified does not exist.

The document might have been archived.

u2022 The system did not find a document header (VBAK) for an individual sales requirement record (VBAK).

An inconsistency has occurred in the ERP system.

We tried changing Contract Profile Dates but no change u2026 facing the same Error.

Regards

Seegal

Edited by: Raga on Nov 19, 2010 5:22 AM

[Former Member]

Problem with Factory Calender.. issue resolved

Edited by: Raga on Nov 22, 2010 5:46 AM

[Lakshmipathi]

Check this thread where the same topic was discussed few days back only.

[sales documents missing from data base|]

Else check notes 575906, 398465 or 127462

thanks

G. Lakshmipathi

[Former Member]

Thanks for all your input... Issue has been resolved.

Actually problem with Factory calender. got resolved.

Regards,

Seegal

[Former Member]

HI

The main problem would be because of number ranges.

Please check the number ranges assigned to the contract.

May be the Number is overlapping because already a number exists with the number.

Try in changing the number range from and to intervals or in VBAK check the last number used for this number range and maintain this number in VN01 as Current number field.

regards

Prashanth

[Former Member]

hi,

please goto ST22 or SM13 You will get furthre analysis on the same.

i believesome parametsrs is missing for saving the document.

please check and confirm.

regards,

balajia

[Former Member]

Hi Balaji,

I did the same thing went to ST22 ...

how to correct the error

Probably the only way to eliminate the error is to correct the program.

-

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"MESSAGE_TYPE_X" " "

"SAPLPS_BAPI" or "LPS_BAPIF01"

"CHK_PRECOMMIT"

I am Checking for OSS notes

Regards,

Seegal