How to Get the PO Creation Date and Time in SAP

If you've ever tried to trace back the exact creation time of a Purchase Order (PO) in SAP, you've likely realized—it's not as straightforward as it should be. Sure, SAP gives us the date. But the time? That’s where things get tricky. Let’s walk through all the reliable ways (and a few workarounds) to get this done—with a bit of friendly commentary along the way.

Why SAP Doesn’t Store PO Creation Time (At Least Not Directly)

First, here's the kicker: SAP doesn’t store the PO creation *time* by default. It only stores the date in standard tables. This is often surprising—especially since you'd expect a transactional system as robust as SAP to log every second. But hey, it's been around since the ‘90s.So, if you’re looking for a field like “PO_CREATE_TIME,” spoiler alert: it doesn’t exist.

Primary Table and Field for PO Creation Date: EKKO-AEDAT vs EKKO-ERDAT

Here’s where you’ll find the creation date of a PO:
  • EKKO-ERDAT = Entry date / PO creation date
  • EKKO-AEDAT = Last change date
So, while AEDAT may reflect the date of the last change, the original creation date is stored in ERDAT.Use transaction SE16N to access table EKKO and search using your PO number to check ERDAT.Important tip: If you created the PO on 11.02.99 and never changed it, ERDAT and AEDAT will likely match.

Want the PO Time? Use ME23N and the Output Message Trick

Now, you’re probably wondering—“Okay, I’ve got the date, but where do I get the actual time?”Since SAP doesn’t log creation time in the main tables, here’s the workaround:
  1. Open the PO in ME23N.
  2. Click on the Messages tab.
  3. If a message output (like a print or email) was created at the time of PO creation, you’ll see a timestamp there.
This is your best proxy for PO creation time—assuming the message was generated automatically upon PO creation.

Use CDHDR/CDPOS Tables with Caution

You may have heard: “Just use CDHDR and CDPOS to get the creation log.”Not so fast.These tables are part of SAP’s change document mechanism, which logs changes—not creations. That means:
  • If there were no changes made post-creation, these tables won’t help.
  • If your organization uses user-exits or BADI implementations that trigger a change upon save, then you might get something here.
CDHDR is unreliable for original creation timestamp unless your SAP system custom-logs creations via enhancements.To use it:
  • Go to transaction SE16N
  • Enter table CDHDR
  • Filter using: 
    • Object class: EINKBELEG
    • Object value: Your PO number
    • Transaction code: ME21N

Alternative: Use EKAB for PO Release Dates

Another table worth checking is EKAB:
  • EKAB-AEDAT stores the date the PO was released, which is especially useful in approval workflows.
  • It doesn't show the time but helps you understand when the PO was finalized.
Use SE16N > EKAB > Input PO Number to retrieve this info.

Seeing the Creation Date in ME23N (Document Date)

Here’s a simple way to confirm the creation date without table digging:
  • Open ME23N.
  • Look at the top section where the PO number appears.
  • You'll see Document Date (MEPO_TOPLINE-BEDAT) — this is often auto-filled with the system date when the PO was created.
This field can be manually edited, though—so it’s not always 100% reliable.

Restricting PO Creation Date Changes in SAP

If you’re an admin or consultant trying to lock the document date so users can’t backdate it during PO creation, here’s your move:

Option 1: Use Screen Layout Customization

SPRO path: SPRO → IMG → Materials Management → Purchasing → Purchase Order → Screen Layout → Define Screen Layout at Document Level
  1. Choose the document type (e.g., NB for standard PO).
  2. Look under the “Deadline Monitoring” section.
  3. Set “Document Date” to Display.
Heads-up: Doing this may also lock the Delivery Date field.

Option 2: Restrict Past Dates Using Error Message

Another trick is to configure system messages to prevent past dates.
  • Use message number: 00 06 028
  • Set it as Error instead of Warning
This forces users to use the current date or a future date during PO creation.

Advanced Logging via User Exits or BADI

In highly audited environments, some companies customize SAP to log PO creation time using:
  • User-exits like EXIT_SAPMM06E_013
  • BADI implementations (e.g., ME_PROCESS_PO_CUST)
These can be configured to store the timestamp in a custom table or append structure.However, this requires ABAP development and is not part of SAP’s standard functionality.

Best Practice: Timestamp via Output Trigger or Workflow Logs

The most widely accepted approach to approximate PO creation time is using:
  • The output message timestamp (as discussed)
  • Workflow start time if the PO goes through release strategies
  • Application logs (SLG1) if configured
These won’t be precise to the millisecond but are usually accurate enough for reporting and audits.

FAQ Section

Q1: Can I see the PO creation time in standard SAP reports?

No, standard reports like ME2N, ME2L, etc., only show the creation date. For time, you’ll need to use one of the workarounds discussed.

Q2: Does SAP store the PO creator’s username?

Yes. You can find the creator’s user ID in the EKKO table field “ERNAM”.

Q3: Can I write a custom report to show PO creation date and time?

Yes, you can use ABAP to combine data from EKKO, CDHDR, and NAST (messages) to build a comprehensive PO log with estimated creation time.

Q4: Are there risks in locking the Document Date field?

Yes. If you set it to display-only, it may affect other date fields like Delivery Date. Always test in QA before moving to production.

Q5: How can I audit old POs if time wasn't logged?

If time wasn’t captured via output message or workflow, you’ll have to estimate using approval logs, release dates, or user activity via STAD.

Conclusion

Finding the exact creation time of a PO in SAP is a bit like detective work. The creation date is easy—check EKKO-ERDAT. But the time? You'll need to rely on output messages, workflow logs, or custom enhancements. If you're implementing a new SAP system, consider logging PO creation timestamps via user-exits for future clarity. For everyone else, the message tab in ME23N is your best bet.

Related:

Get help for your SAP MM problems
SAP MM Forums - Do you have a SAP MM Question?

SAP Material Management Books
SAP MM Books - Certification, Interview Questions and Configuration

SAP Materials Management Tips
SAP MM Configuration Tips and Materials Management Discussion Forum

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of 
www.erpgreat.com or the content authors.