If you are using Bank Account answer type without repeatable section, then you need to use supplier field mapping as "vendor.bankInfos". When using Bank Account as an answer type, you do not need to maintain individual mappings to the questions contained in the Bank Account answer type, but a single mapping just on Bank Account question. Bank Account answer type also works well within repeatable sections in case you have a business requirement to have multiple bank accounts from suppliers, which is often the case. ![]() When enabled, you will get Bank Account as an answer type for your external supplier facing questionnaire. When enabled it will surely enhance the supplier experience and at the same time buyer's supplier management team can relax as they can trust the system to validate critical supplier inputs. Introducing, bank component feature with country specific syntax validation and similarly tax component feature with country specific syntax validation. So let's see what has changed or rather how should you do it for your next customer. However, there is still room for improvement. Thankfully, SAP Ariba listened to it's customers and made available slew of features which makes this problem go away to an extent. Managing such number of field in external questionnaire is nothing short of a nightmare. ![]() Although we always had the limited ability to restrict the vendor responses by using validation expressions but the problem increases manifold when we have various tax and bank fields which differ for each country. ![]() Everyone who has ever worked with SLP knows the pain when vendor integration fails due to bad master data provided by the supplier.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |