Purchase Order Reporting date

[Former Member]

All, My understanding is that for PO's the Document date is used for reporting (like for Invoices). While this works fine for Invoices, the Document date for PO's does not provide in my opinion the true depiction of spend (should be on the basis of Delivery date for PO's)

Especially in the Direct world where the delivery date is far more important than the date on which the Scheduling Agreement is created (for example). Even for Indirect, I would argue that the Delivery date provides superior reporting than the document date..

Does anyone else have this requirement and if so, how are you handling it? Any inputs will be appreciated.

Thanks - Nikhil

[Former Member · Accepted solution]

Hi Nikhil,

Without questioning your business requirement here, this may be of help.

BKPF- BUDAT/AEDAT (posting date or changed date) is used for invoices, and EKKO-BEDAT "Purchasing Document Date" is used for POs.

Technically you can change

You can change what date field maps to 0Calday etc in the transformations

There is also the possibility in the data source properties in the SPM user interface:

Administration -> Analysis administration -> application properties -> data sources -> click on the data source (query) in question to then change what characteristics refer to what time characteristics.

Hope this helps

Kind regards,

Neil

[Former Member · Accepted solution]

Hi Neil

Thanks for your response.

Actually, the problem is that the Delivery dates (which are at the scheduled delivery line item level) do not come to SPM per my understanding. Hence the problem is more that the extractor has to be significantly modified in the first place. Is your client using Purchase Order reporting in SPM? If so, dont they need to see the delivery date?

Cheers - Nikhil