VAS handling in MM (AFS 6.3 functionality) - knowledge sharing

Hello All,

Being on ASF 6.4 since end of last year we plan to use VAS handling in MM
later this year. During the implementation project we are facing a
significant no. of challenges.
Well, I know that some addition features will come with AFS 6.5.
Despite of, I would like to know if there is any other AFS customer out
there who has looked into this topic or even is using it already today.
It would we great if we could share our experience in this group. Ideally,
we can consolidate our lesson learned and provide constructive feedback to
AFS to further improve this function to better meet common business
requirements.
Remark: Please find below some ideas for improvements we have identified so
far.
• Mass data maintenance for vendor master is missing VAS fields
•  IDoc for vendor master creation is missing VAS fields (See screen
shot below for the VAS fields in vendor master)
• VAS data long text is not supported in sales order Idoc
• Customer master mass change function does not support VAS fields
• In Purchase order transactions ME21n, ME22n easy manual
maintenance screens for VAS codes similar to sales order (3 Tabs) is missing
(covered by AFS 6.5 in a different way)
• IDoc for customer master does not have the VAS fields (similar to
the vendor master Idoc)
• Currently, if the VAS data in PO is not from condition records,
then a PO change triggers an update termination
• Ideally, VAS data in PO should not be considered as master data.
It should be considered as transactional data, and allow for changes in PO
(for stand alone POs only)

• For TPO and PTO processes, the VAS changes made in SO should be
updated/copied to the account assigned PO without the use of texts (if PO
exists). The use of texts should be avoided (the copy function should be, if
possible , with configurable rules)

Many thanks in advance,
Klaus