Control Report for Delivered, Not Invoiced Goods or Services

This document describes how control reports are created in 'Control List. Print Delivered/Not Invoiced' (CAS515).

Outcome

You understand which tables and specific criteria M3 uses to select deliveries for the report.

Use the information in this document to verify the contents of the report as part of trouble-shooting and audits.

Purpose

The control report contains all non-invoiced deliveries of goods or services based on customer orders, service orders and purchase orders up to a user-defined To accounting date.

Contents

For each delivery, the report contains the recorded amount, accounting date, customer, order number and order line number, delivery number, order type, item number, warehouse, facility and transaction quantity in the basic unit of measure.

Source Transactions

Non-invoiced deliveries are represented by the following account entries in M3: SO10-951 (for service orders), OI10-951 (for customer orders), and PP10-951 (for purchase orders).

The basis for the SO10-951 account entries is created in the following situations:

  • Goods are reported as delivered to customers in 'Service Order. Complete Assignment' (SOS640).
  • An invoice proposal is approved in 'Rental Invoice Proposal. Update' (STS180). Account entries are created for the rental agreement.
  • An invoice proposal is approved in 'Leasing Invoice Proposal. Open' (LTS180). Account entries are created for the leasing agreement.

The basis for the OI10-951 account entries is created when you report delivery of goods to customers in 'Picking List. Report' (MWS420).

PP10-951 represents the net total value of the purchase order line. It is used for purchase orders that are connected to a customer order or service order with line type 2 (Direct delivery). The basis for the PP10-951 account entries is created in the following situations:

  • Goods are reported as received in 'Purchase Order. Receive Goods' (PPS300)
  • Goods receipts are deleted in 'Purchase Order. Display Line Trans' (PPS330).

The actual account entries are generated when you run 'Internal Account Entry. Create' (CAS950). The account entries are created in the table for internal account entries, CINACC. At the same time, M3 automatically populates the history table for delivered/not invoiced, CININD, with all account entries based on accounting rules SO10-951, OI10-951, and PP10-951. The information stored for each account entry in the history table is accounting number, sequence number, accounting event, and invoice matching date. As long as the delivery is not invoiced, the invoice matching date is 0.

Selection of Deliveries

When you print a report in (CAS515), M3 begins by selecting all records in the CININD table that have an invoice matching date of zero or a date after the To accounting date.

  1. A delivery is printed on the report when one of the following requirements is met: 1) the delivery has not been invoiced, and 2) the internal account entries have not yet been transferred to the general ledger. The CININD table is not updated, since the invoice matching date is still zero.

  2. If the delivery has been invoiced and the general ledger is updated, M3 searches for records with an invoice accounting date in the following three places:

    • Deliveries: Internal account entries in the CINACC table: OI10-951, SO10-951 and PP10-951
    • Invoices: Records without an invoice number in the table for customer order headers, ODHEAD (for OI20-951), and service order headers, SDHEAD (for SO20-951)
    • Proof of delivery: Records in the CINACC table: OI15-951.

    Based on the dates found in these three places, M3 sets the invoice matching date for the respective transaction in the CININD table by picking the highest date of the invoice accounting date from these three sources. The invoice matching date acts as a tag in the CININD table that indicates that the transaction has been invoiced. A delivery is then printed as a line on the report if it has an invoice matching date after the To accounting date.