10 results found
-
Improvements on Custom Attributes in Bulk Add and CSV Upload
On Jul. 15, Corevist rolled out Custom Attributes and UOM with CSV Upload and Bulk Add in Cart/Quote. At this point, the feature is not very user friendly. Especially the need to enter attribute labels for every line.
We suggest the following ways to make it more user friendly and generic to other customers:
Add a “Add column” next to “Add row” button.
A dropdown list for all available attributes for the added columns
Users are able to enter just values in those columns
CSV template download contains all possible attributes.
User friendly display names and an extra level of…
1 vote -
Mass order upload
Some customers wish to place multiple orders at once based on data in a spreadsheet.
It would be great if Corevist could provide a file template to allow customers to fill out a spreadsheet and upload the order in a single transaction.3 votes -
Break up 'Attachment Enabled' to allow authorization of view or add
Requesting New/Separate Authorization Roles for Attachments in Quotes and Carts. We would like roles created so users can be limited in their attachment abilities.
1) authorization to add attachments in orders
2) authorization to view attachments in orders
3) authorization to add attachments in quotes
4) authorization to view attachments in quotes
4 votes -
Enter button on order submit
Some people have the habit of hitting the enter button after typing and as a user in the cart on the checkout screen, I will create the order before I am ready if I hit the enter button after typing in a PO number.
The suggestion is to disable the automatic submit of the Place Order button using the enter key.
If a user means to enter text in the notes, he is unable because the order has been submitted before he is ready because he did not actually click the "Place Order" button.
3 votes -
Require users to choose an order type without defaulting
When multiple order types are permitted within the cart, users should intentionally be required to choose rather than have a doc type defaulted.
Users will not normally think to change the order type as necessary and this can result in very costly problems for all parties involved when an order is created using the wrong order type.
3 votes -
Search for saved carts
Enhancements to the cart access (search/filter) - currently, user can do a "Find" to search for header data (date, sold to name, ship to name). Requesting to have search feature to see results of the search. Search to look for sold to name, ship to name, date, product models, and cart value.
Also requesting for a feature to "delete all empty item carts" (where cart only has a header and no items in it).
2 votes -
Ship to line field not large enough
When creating an order and selecting a line level ship-to address, the list of available partners isn't visible when you have orders that extend to the bottom of the page. A scroll bar to allow a user to navigate through the list of available address and a scroll bar within the ship-to field would allow a user to accurately select the appropriate address:
2 votes -
New custom cart attribute type
Promotion codes can be entered into the cart but having it as just a simple text field is not the best user experience.
The idea here is to establish a new custom cart attribute type. Currently, we have choices such as a date, number, text, long text, time, etc.
This would be a new type that would allow a user to type a value, press enter and type another and press enter and then remove.
https://app.screencast.com/oi1MVC6yNi0rT1 vote -
Automatic Product Proposal in the Shopping Cart
Tap into S/4's Intelligent Product Proposal and/or ECC's Dynamic Product Proposal from the Shopping Cart.
S/4 has an API that is available for this purpose in case this is to be delivered by the front-end team (https://api.sap.com/api/API_INTELLIGENTPRODUCTPROPOSAL_SRV/overview)
Otherwise both ECC and S/4 have function modules that can be called during SAP-side processing for shopping cart simulation.
3 votes -
Guest Browse/Checkout
Allow Unknown Customers (aka "unregistered users") to view the product catalog and create orders using standard SAP one-time-customer capability.
The client would need to set up a one-time sold-to against which all product catalog restrictions and pricing will be determined. The unknown customer must provide Sold-to Name, Street address, City/State/Zip, and Country in cart checkout.
We can discuss options for how this should work (ex. perhaps a Corevist logonid "Guest" with password "Guest" to browse the catalog w/o sharing of carts across guest sessions, the ability to override sold-to name/address details in the cart, a requirement for credit cards or…
3 votes
- Don't see your idea?