Purchase order matching

The invoice must be matched to the purchase order manually.

  1. Click New on the Transaction Types tab in the Transactions (tfgld1101m000) session.
  2. Select API in the Transaction Type field.
  3. Click the Go to Details button for the API transaction type. Purchase Invoice Entry (tfacp2600m000) session.
  4. Select Invoice Related to Purchase Orders in the Invoice Type field.
  5. Select the business partner in the Business Partner field of the General section, invoice amount in the Amount field of the Amounts section.
  6. Click Actions > Matching > Match Order. The Match Purchase Order Lines (tfacp2541m000) session is displayed.
  7. Select the purchase order created for the complementary purchase price in the Order field.
  8. Press Tab. The application populates the data in the other fields of the invoice header.
  9. Click Save.
  10. Select Actions > Matching > Match Order. The Match Purchase Order Lines (tfacp2541m000) session is displayed.
  11. Select Views > Hide Completely Matched Order Lines to view all the documents including the completely matched orders.
  12. Select the (Change) Match check box of the original purchase order line, update the order line with the additional price.
  13. Click Match Selected Orders.
  14. Verify that the Invoice Status is updated to Matched and the Amount Unassigned is 0.00 in the Purchase Invoice Entry (tfacp2600m000)session.
  15. Specify the postings related to taxes on the Additional Costs tab.
  16. Click the Approve button to approve the purchase invoice and complete the matching process. The Invoice Status is updated to Approved.
  17. Review the entries generated in the Integration Transactions (tfgld4582m000) session.
  18. Verify that LN generates an additional transaction line in the Inventory Receipt Transactions (whina1512m000) session related to the price difference after the approval of complementary price invoice.
  19. Verify that the related price complement transaction is generated in the Inventory Variances (whina1516m000) session.