Unwanted Document Flow (VTAA)

[Former Member]

Hello experts,

We are working through our configuration in attempt to disable the document flow off contracts of deliveries, goods issue, and billing documents.  Through VTAA we have found the option "2" Create doc. flow records except for delivery/gi/billing doc, and we enabled the option.  Despite enabling it and confirming that we are pegged to the correct sales doc type and whatnot, the document flow table is still being updated with those documents when created.  Is there some other piece of configuration we need to examine to fix this?

UPDATE: Added a screenshot of the program SDVBFA21 which I found simulates what would need to be retroactively cleared from the document flow table based on the current configuration.  So that program confirms that the test deliveries/goods issues/billing document should be removed from the table, meaning our configuration profile is current per the requirement we are attempting to achieve, but I do not understand why they were ever added to the document flow table to begin with...

Appreciate any feedback!

Message was edited by: Kelby Rubenstein

[Lakshmipathi · Accepted solution]

In normal circumstances, for updating document flow, in copy control VTLA, there would be one check box "Update document flow" which would be checked in standard.  If you uncheck, then the subsequent documents would not be updated in VBFA table.  I am not sure on VTAA which field you were referring.  But, there will be serious implications if the subsequent documents are not updated in VBFA.

G. Lakshmipathi

[Former Member · Accepted solution]

Hello,

In VTAA at the item level you can alter the system decision to carry out doc flow all the way through to the billing document in the case of contracts.  We've elected to alter our system so that contracts only provide document flow to their sales orders, then the deliveries, goods issue, and billing document pegs to the sales order instead of all the way up to its contract.

After debugging on Friday, we discovered that the sales order is inheriting the incorrect document flow indicator (VBAP-UPFLU).  We are now trying to determine why this field is not inheriting what is configured, but we believe it may be due to user exits where the assignment of a contract is copying a lot of fields into the new sales document...

[venu_ch8 · Accepted solution]

Dear Kelby ,, thanks a lot for updating Root cause so just click on Correct answer on your post 

Thanks

venu

[Former Member · Accepted solution]

Thanks for all the help.  We found the custom user exit that was force-changing our field on the VBAP structure, and we confirmed that with proper correction the doc flow will be functioning as expected.

[venu_ch8]

Dear ..

once de activated in Copy control That document flow it wont update the document flow For further documents in future..But All ready created documents we can see in VBFA  Table

By the by you can run this program SDVBFA21 Delete Unwanted one

Even after that if you are able to find document flow Please do Debugging .

May be it will helpful ..

[Former Member]

Hi Venu,

Prior to running the program and taking the screenshot, we had already changed the configuration THEN created the documents.  It's still appending them to the document flow table, even now.  Could you point me in the direction of what programs we may need to debug to determine where the INSERT statement is going to the document flow table?

[venu_ch8]

Dear Kelby ...

please check this oss notes very helpful   50571   & 105515

Thanks a lot