Pricing Upload : Overlapping Dates giving Internal error: T IVAKE F IVAKE_INSERT I MV130F0I

[former_member225253]

Hi SD / ABAP Experts

Greetings for the day ahead .

I have developed a custom program for Uploading Pricing using Function Module

RV_CONDITION_COPY and it is working fine except this one Observation / Inconsistency . User Uploads the records using a file and if User Provides Overlapping Dates for the same combination of key fields in A**** table , it is giving Internal error: T IVAKE F IVAKE_INSERT I MV130F0I . eg . for this same sales organisation , distribution channel , material combination overlapping dates were uploaded . screenshots for reference .

There are various posts on this error on forums , however i could not find a precise solution to handle this programmatically .Deleting records uploaded into tables KONP , KONH etc afterwards is not a solution for the requirement to take care of it temporiraly .

My Requirement is that the program executes the standard functionality regarding overlapping dates from File shown in screenshot below through Program :

and the Program should display the Condition Records without this error (

Internal error: T IVAKE F IVAKE_INSERT I MV130F0I ) for the records. How to achieve this through Program . Deleting records uploaded from tables is not a solution for the requirementas i have to upload mass records from file .

Is there some standard transaction which i can call in my custom program after the Function Module to fix the Overlapping Validity Dates Issue If the user uploads them or some other approach which can help achieve the objective .

Would be grateful for your Replies .

Thanks and Rgds ,

Devendra Singh

[former_member156446]

You need to use cl_reca_date_slices

[iyankannu_iyankannu]

Hi,

if you do the update to the existing Pricing condition, the standard application always delete the existing condition and create the New One, so you have pass the Delete data set first to delete the Old record and new date set to create the New Record. Please check the Function module ( RV_KONDITION_SICHERN_V13A ) In update task to analyse the execution in more details.

Because All the condition is posted via the above function module.

[iyankannu_iyankannu]

Hi,

if you do the update to the existing Pricing condition, the standard application always delete the existing condition and create the New One, so you have pass the Delete data set first to delete the Old record and new date set to create the New Record. Please check the Function module ( RV_KONDITION_SICHERN_V13A ) In update task to analyse the execution in more details.

Because All the condition is posted via the above function module.

[former_member225253]

Hi Avik ,

Thanks for the Reply . What would be the Logic to achieve this through Custom Program ?

Best Regards ,

Devendra Singh

[former_member365886]

Hi,

Is it not possible in your custom z=program to incorporate a validation rule so that overlapping dates if found then first delimit the existing pricing condition record,then upload the new record for the same key combination with new start date and end date?

Regards,

Avik