PRIMAVERA ERP Integrator FAQs

To consume items in the work orders, follow these steps:

1. Create an internal request in Valuekeep (Internal Requests | Transactions | Internal Request), and identify the work order;
2. Approve the internal request in Valuekeep (Internal Requests | Transactions | Internal requests approval). When an internal request is approved, it will synchronize with ERP PRIMAVERA by creating an internal document. In Valuekeep, the “ExternalID” field of the internal request identifies the document generated in the ERP;
3. In the ERP, the internal document should be fulfilled through a stock issue document. The stock issue document, created when fully or partially fulfilling the internal document, should be configured with “traceability at source“;
4. When a stock issue is generated by fulfilling an internal document originated in Valuekeep, the stock issue will integrate in Valuekeep as an item entry.
   If the ERP stock issue lines contain repeated items, stock entries will be created for each repeated item.
   If the ERP stock issue lines contain different warehouses, stock entries will be created for each warehouse;
5. As soon as there is a stock receipt, it is possible to consume the items in the Work Orders.

An internal request can originate an internal document or an internal request in PRIMAVERA ERP. If it originates an internal document, it can be fulfilled by using the rows copy. If it originates an internal request, it can be fulfilled by using the rows copy or by processing the internal request.

Fulfilling the internal document or processing the internal request always generates a stock issue and the stock issue document must have the “traceability at source” option active. Only the items and quantities requested in the internal request are transitioned to EAM.

Additional information of the internal request is entered in the document’s observations field:

• The WO key and the item key, the location of the item or the request WO route;
• The request description;
• The request observations;
• The observations of each request line.