• Purchase Requisition can be transfered into Purchase Agreement

    Ability to create a purchase agreement out of a purchase requisition - currently every purchase requisition leads in a purchase order after approval. It would be very helpful to decide if an approved requisition will be transfered to a purchase order or to a frame contract (=purchase agreement). Additionally - if this process is automated - it should be controlled over a flag on the puchase requsition. (similar to RFQ process, where you need to define the outcome)
  • Consolidate Requisitions and Planned Purchase Orders

    We would like to order goods (based on minumum stock) and manually requested goods from the same vendor. Therefor it's necessary to put them on the same purchase order (without any manually adjustments or losing any references). Consequently there should be a possibility to consolidate these two types to one purchase order. Or at least to add approved purchase requisition lines existing purchase orders.
  • Organization Wide Purchase Agreements

    Purchase Agreements should have the possibility to be valid for more than one legal entity. In reality a company negotiates contracts for the whole organization (all legal entities) or a region (a specific no of legal entities). Consequently they want to manage their agreements for more legal entities in one place. Of course it depends on the shared master data; e.g. payment terms, vendors, items,...
  • Consolidate Requisitions and Planned Purchase Orders

    We would like to order goods (based on minumum stock) and manually requested goods from the same vendor. Therefor it's necessary to put them on the same purchase order (without any manually adjustments or losing any references). Consequently there should be a possibility to consolidate these two types to one purchase order. Or at least to add approved purchase requisition lines existing purchase orders.
  • Organization Wide Purchase Agreements

    Purchase Agreements should have the possibility to be valid for more than one legal entity. In reality a company negotiates contracts for the whole organization (all legal entities) or a region (a specific no of legal entities). Consequently they want to manage their agreements for more legal entities in one place. Of course it depends on the shared master data; e.g. payment terms, vendors, items,...
  • Purchase Requisition can be transfered into Purchase Agreement

    Ability to create a purchase agreement out of a purchase requisition - currently every purchase requisition leads in a purchase order after approval. It would be very helpful to decide if an approved requisition will be transfered to a purchase order or to a frame contract (=purchase agreement). Additionally - if this process is automated - it should be controlled over a flag on the puchase requsition. (similar to RFQ process, where you need to define the outcome)
  • Responsible Person per Category Node

    In many companies category managers are responsible for procurement activities according their category; mostly controling actual vs budget and approving requisitions, orders and invoices. Therefor it's necessary to define a responsible employee per category and inherit this person to sub-categories. This employee should be available for assignments in all procurement related workflows. The definition of a responsible person should be available per category node and legal entity.
  • Drag and Drop for Attachements

    Instead of uploading a document through the "Browse" button, it would be very helpful to upload files just by drag and drop into a certain area in the document attachement screen.