Supply User Manual ENG -> 4. Procurement -> 4.1 Orders, Purchases and Reporting.
Orders, Purchases and Reporting.
This chapter covers the different types of orders available in UniField, as well as each different stage of sourcing and procurement. The process will start as an expression of needs, and this may be followed by procurement, sourcing from stock, loan, which may involve both internal (via synchronization) and external partners.
It is essential to understand how product orders and procurement are processed in UniField, as an order line may pass through several different stages until the product reaches its final destination. All these stages, up to the point of product reception, are covered in depth in this chapter.
This chapter also covers the relationship between projects and coordination and the role which the synchronization can play in the order flows between them.
This chapter is introducing gradually the different functionalities of UniField needed in procurement, starting with Internal Requests, continuing with the Orders Sourcing Tool before to focus on Field Orders and Purchase Orders. As these functionalities are highly interconnected within UniField, it was not possible to keep them completely separated; reason why some functionalities such as Field Orders and Purchase Orders are already introduced before their dedicated learning units.
As of UF7.0 (released in January 2018), documents used in procurement (Internal Requests -IR-, Field Orders -FO- and Purchase Orders -PO-) can be processed at header level (for the whole document) or at line level (for specific items in the document). This is a major change that has been introduced in UniField to allow -among others- partial sourcing and partial confirmation of orders.
Throughout this chapter, you will find many acronyms. They are mostly used to shorten English words but can be used in the English manual or the French manual (i.e. you may find the acronym PO in the French version of the manual). In the below table, you find the main acronyms used in this chapter with their meaning.
French acronyms, such as the names of the documents in French in a less extend, are barely used. English acronyms and documents names are usually preferred. In the software, references of documents are often built with the English acronyms of the documents (e.g. 18/IR00019, 18/HQ/MW101/FO00033, 18/HQ/MW101/PO00045…), independently of the language in which the software is used.
The language in which UniField is developed is English. The software is then translated in French. That’s the reason why, even if you are connected in French, you could still find some English terminology (on screens, in messages,) while working on UniField. The translation of the software in French is a work in process and some improvements are still needed on this side.
