Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Incompletion log for maintained text is not reset

Former Member
0 Kudos

A custom program is developed to add line item details for a contract(VA42 transaction) from an excel file.

My issue is, while adding text(long text description) for a line item to the transaction VA42(Change contract)by using SAVE_TEXT function module the <b>incompletion log is not deleted/reset for that particular line item.</b>

Is there a way i can reset/ delete the incompletion log for that particular line item using the custom program.

The incompletion log details are maintained in a standard table VBUV.

Could any one help me in solving this issue.

Thanks in Advance

Aswani.

7 REPLIES 7

Former Member
0 Kudos

Hi Aswani,

I'm not sure if SAVE_TEXT is the best way to create texts in SD> You can take a look at the following Function Modules -

RV_TEXT_COPY

SD_COMMIT_TEXT

RV_SALES_ACTIVITY_UPDATE

SD_SALES_ACTIVITY_SAVE

I shall try to get back with some more information on this.

Regards,

Anand Mandalika.

0 Kudos

Hi Anand,

I have gone through the Fumction module RV_TEXT_COPY. According to my understanding i think this is used when a sales document is created from other sales document.

Also the fucntion module RV_SALES_ACTIVITY_UPDATE is used to update the standard tables.

So, can we use RV_SALES_ACTIVITY_UPDATE FM to update the standard table VBUV for that particular line item.

If so could you please let me know how to use the function module.

Thanks in Advance,

Aswani.

0 Kudos

Hi Aswani,

Is there any reason that you are not using the BAPI to change the document (and add text)?

If you did this the incompletion log would be updated by the standard programs.

Cheers,

Brad

0 Kudos

Sorry, I didn't add BAPI: BAPI_SALESORDER_CHANGE.

This should be a simpler solution?

Brad

0 Kudos

Hi Brad,

I have tried using the BAPI_SALESORDER_CHANGE. The incompletion log is deleted only if the text is added along with the line item for a contract.

In my case the line items are already added and i need to populate the text for those line items.

In this case the BAPI_SALESORDER_CHANGE works similar to SAVE_TEXT function module.

I mean to say both the function modules add text to the line item but the incompletion log is not deleted for that line item.

Could you please let me know if i can achieve the same using the BAPI_SALESORDER_CHANGE function module or is there any way i can delete the entries from the table VBUV(Which stores the details of the incompletion log).

Thanks in Advance

Aswani

0 Kudos

Hi Aswani,

At least with the BAPI you are processing the sales order which gives you a chance to do some further processing.

In the userexit USEREXIT_SAVE_DOCUMENT of program SAPMV45A(it will get triggered when you call the BAPI) you have to an internal table for VBUV, its called XVBUV. You can directly manipulate the values of this internal table here (for example, you can delete the line which refers to text which SAP thinks is incomplete). These changes get updated in the database table VBUV. You can test this by putting a break point in USEREXIT_SAVE_DOCUMENT and then calling the BAPI to add the text. When you hit the break point, manually delete the XVBUV line which refers to your text and then continue. This should function correctly. You just need to code the logic into the userexit (being careful not to upset standard incompletion processing!!!).

Its been a while since I have done this, so if this doesn't work correctly, then try USEREXIT_SAVE_DOCUMENT_PREPARE. One of these userexits will achieve exactly what you are after.

Cheers,

Brad

0 Kudos

BTW - when using the BAPI it should actually update the completion log.

Have you checked for OSS notes?

If there are none, I suggest you implement the userexit fix and raise a note yourself.

This allows you to move forward with a solution that works today and then you can implement the note when SAP provide the fix (I expect that this would take some time).

Cheers,

Brad