14. Which of the following are correct as of release SRM 4.0?
a) Customer-specific fields can be created for the shopping cart, purchase order, and contract documents in SRM.
b) The procurement card functionality in EBP can be implemented in the Classic and Extended Classic scenario.
c) ITS can now be utilized integrated with the Web Application Server 6.40. This can decrease the total cost of ownership (TCO).
d) Archiving documents is not supported in SRM.
ANSWER(S): A, C
Customer fields can be used in shopping carts, purchase orders, confirmations, invoices, and contracts at the header and item level, and for account assignment. Customer fields can be displayed in the standard interface or on a custom screen. A BADI is available for customer-defined sub screens.
In EBP, you can specify procurement card as the payment method when purchasing items. However, this functionality is only supported in the Standalone or Local implementation scenarios. The Classic and Extended Classic scenarios do not support this functionality. Some organizations have handled this limitation via development.
As of SAP NetWeaver '04, ITS is now available integrated with the NetWeaver component, SAP Web Application Server 6.40, as an Internet Communication Framework (ICF) service. The Integrated ITS runs on one machine, reducing the number of servers and decreases the total cost of ownership (TCO).
Archiving is a process to remove bulk or outdated data from your database that is no longer needed in your system. Many documents including the shopping cart, purchase order, confirmation and contracts can be archived in SRM. In SRM 4.0 the restoration of archived data is not yet possible.