Your Record to Report - Journal Entry Data Template

SAP ECC
Your Record to Report - Journal Entry Data Template

Your Record to Report - Journal Entry Data Template

This template provides a clear roadmap for collecting the necessary data to analyze and optimize your Record to Report - Journal Entry process. It outlines the essential attributes to collect, the critical activities to track, and practical guidance on extracting this information from SAP ECC. By following this template, you can ensure a robust dataset for uncovering inefficiencies and improving your financial reporting.
  • Recommended attributes for comprehensive analysis
  • Key journal entry activities to track
  • Practical data extraction guidance for SAP ECC
New to event logs? Learn how to create a process mining event log.

Record to Report - Journal Entry Attributes

These are the recommended data fields to include in your event log for comprehensive analysis of your Record to Report - Journal Entry process within SAP ECC.
5 Required 6 Recommended 8 Optional
Name Description
Activity Name
ActivityName
The name of the business activity or event that occurred at a specific point in the journal entry process.
Description

The Activity Name describes a specific step in the journal entry lifecycle, such as 'Journal Entry Created', 'Journal Entry Approved', or 'Journal Entry Posted'. This attribute is typically derived from multiple sources in SAP, including transaction codes (TCODE), change document logs (tables CDHDR and CDPOS), and document status fields.

Analyzing activities is the core of process mining. It allows for the visualization of process maps, calculation of transition times between steps, and identification of rework loops (e.g., 'Journal Entry Rejected' followed by 'Journal Entry Corrected'). This data is fundamental for dashboards related to cycle times, rework rates, and process variants.

Why it matters

It defines the steps in the process map, making it possible to visualize, analyze, and optimize the journal entry workflow.

Where to get

Derived from various sources, including transaction codes in BKPF (TCODE), document status, and workflow logs in tables like SWW_WI2OBJ, or change documents in CDHDR and CDPOS.

Examples
Journal Entry CreatedJournal Entry ApprovedJournal Entry RejectedJournal Entry Posted
Event Time
EventTime
The timestamp indicating when a specific activity or event occurred for the journal entry.
Description

Event Time provides the exact date and time for each activity in the journal entry process. This data is critical for calculating all time-based metrics, such as cycle times, processing durations, and delays between steps. The source of this timestamp varies depending on the activity; it can be the document creation date/time (CPUDT/CPUTM) or change timestamps from logs (CDHDR-UDATE/UTIME).

In analysis, Event Time is used to order events chronologically, forming the basis of the process map. It is essential for calculating all KPIs related to time, such as Average Journal Entry Cycle Time, Average Approval Time, and Time from Approval to Posting.

Why it matters

This timestamp is the foundation for all time-related analysis, enabling the calculation of cycle times, durations, and bottlenecks.

Where to get

Sourced from various fields depending on the activity, primarily creation timestamp (CPUDT, CPUTM) from BKPF or change document timestamps (UDATE, UTIME) from CDHDR.

Examples
2023-10-26T09:00:00Z2023-10-26T14:30:15Z2023-10-27T11:05:00Z
Journal Entry ID
JournalEntryId
The unique identifier for a financial accounting document, combining company code, document number, and fiscal year.
Description

The Journal Entry ID is the primary case identifier for tracking the lifecycle of a journal entry. It is a composite key, typically formed by concatenating the Company Code (BUKRS), Document Number (BELNR), and Fiscal Year (GJAHR) to ensure uniqueness across the entire SAP system.

In process analysis, this ID links all related activities, such as creation, parking, submission, approval, rejection, and posting. By tracing this identifier, we can construct the end-to-end journey of each journal entry, measure cycle times, and identify process deviations or bottlenecks for specific entries.

Why it matters

This is the essential key for tracking a journal entry from its creation to its final posting, enabling end-to-end process analysis and variant comparison.

Where to get

This is a derived attribute, typically a concatenation of fields from the BKPF table: Company Code (BUKRS), Document Number (BELNR), and Fiscal Year (GJAHR).

Examples
1000-1000000123-20232000-1900000456-20231000-1800000789-2024
Last Data Update
LastDataUpdate
The timestamp indicating when the data was last extracted or refreshed from the source system.
Description

This attribute records the date and time of the most recent data pull from SAP ECC. It is a metadata field that is critical for understanding the freshness and currency of the data being analyzed.

In any process mining dashboard or analysis, knowing the last update time is crucial for users to trust the data and make informed decisions. It helps answer the question, 'How up-to-date is this information?'.

Why it matters

Informs users about the freshness of the data, ensuring they understand the time frame of the analysis and can trust the results.

Where to get

This is a metadata field generated and stored by the data extraction tool or ETL process at the time of data refresh.

Examples
2024-05-20T04:00:00Z2024-05-21T04:00:00Z2024-05-22T04:00:00Z
Source System
SourceSystem
The system from which the process data was extracted.
Description

This attribute identifies the origin of the data, which in this case is the specific SAP ECC instance. It is typically a static value added during the data extraction process.

While simple, this attribute is important in environments with multiple ERPs or data sources. It ensures data lineage is clear and allows for filtering or segmenting analysis by the system of origin.

Why it matters

Provides clear data lineage and is essential for tracking data quality, especially in environments with multiple source systems.

Where to get

This is typically a static value added during the data transformation process, identifying the specific SAP ECC instance (e.g., 'ECC_PROD_100').

Examples
SAP ECC EHP8ECC_FIN_PRODSAP_ERP_60
Company Code
CompanyCode
The organizational unit representing an independent legal entity for which financial statements are prepared.
Description

The Company Code is a fundamental organizational unit in SAP Financials. It represents a legally independent company and is a key field in the journal entry document header.

This attribute is essential for segmenting process analysis by legal entity. It allows for comparing process performance, compliance rates, and KPI results across different parts of the business. For example, it can help identify if approval delays or high reversal rates are specific to certain company codes.

Why it matters

Allows for filtering and comparing process performance across different legal entities or business units within the organization.

Where to get

Located in the document header table BKPF, field BUKRS.

Examples
10002000US01DE01
Document Type
DocumentType
A classification for accounting documents that controls how they are processed and stored.
Description

The Document Type distinguishes different kinds of business transactions, such as a general ledger entry (SA), vendor invoice (KR), or asset posting (AA). It is defined during system configuration and assigned to every journal entry.

This is a critical attribute for analysis as it allows for segmenting the process by the nature of the transaction. The 'Journal Entry Throughput by Type' dashboard and 'Average Cycle Time by Journal Entry Type' KPI depend directly on this field. It helps uncover if certain types of entries are more prone to delays, rework, or reversals.

Why it matters

Enables segmentation of analysis by transaction type, helping to identify if process issues are specific to certain types of journal entries.

Where to get

Located in the document header table BKPF, field BLART.

Examples
SAKRREAA
Is Reversed
IsReversed
A boolean flag indicating whether the journal entry has been reversed.
Description

This flag identifies journal entries that have been subsequently reversed by another accounting document. In SAP, a reversed document is linked to the reversal document, providing a clear audit trail.

This attribute is fundamental for the 'Journal Entry Reversal Analysis' dashboard and the 'Journal Entry Reversal Rate' KPI. It allows for isolating reversed entries to investigate the root causes, such as data entry errors or incorrect accounting treatments, with the goal of reducing the frequency of reversals.

Why it matters

Directly supports reversal analysis by flagging entries that were later undone, helping to identify root causes of errors and improve data integrity.

Where to get

Derived from the Reversal Document number field (STBLG) in the BKPF table. If STBLG is not empty, the flag is true.

Examples
truefalse
Posting Date
PostingDate
The date on which the transaction is recorded in the general ledger, affecting the financial period.
Description

The Posting Date determines the fiscal period in which the journal entry is accounted for. It is a critical date field from a financial and compliance perspective, as it must align with accounting period close schedules and regulations.

In process mining, this date is used to monitor compliance. The 'Compliance Adherence Monitoring' dashboard and 'Compliance Conformance Rate' KPI use this attribute to check if entries are posted within the correct period. It can also be used to analyze trends in journal entry volumes over time.

Why it matters

Crucial for financial reporting and compliance analysis, ensuring entries are posted in the correct accounting period.

Where to get

Located in the document header table BKPF, field BUDAT.

Examples
2023-10-312023-11-302024-01-15
Transaction Code
TransactionCode
The SAP transaction code used to create or process the journal entry.
Description

The Transaction Code (T-Code) is a unique identifier for a specific function or program in SAP. For journal entries, it indicates how the entry was created, for example, manually (FB01, F-02), via parking (FV50), or through an automated interface.

This attribute is invaluable for the 'Manual Activity Optimization' dashboard. By analyzing the T-Code, we can distinguish between manual and automated activities, identify which manual processes are most time-consuming, and pinpoint opportunities for automation to reduce manual effort and improve efficiency.

Why it matters

Helps differentiate between manual and automated processes, identifying opportunities for automation and process standardization.

Where to get

Located in the document header table BKPF, field TCODE.

Examples
FB01F-02FV50FBD1
User
User
The SAP user ID of the person who created or changed the journal entry.
Description

This attribute captures the SAP username responsible for a given activity, such as creating, parking, or posting a document. It is sourced directly from the document header or change log tables.

Analyzing the User attribute is key to understanding team and individual performance. It supports the User Productivity dashboard by tracking activity volumes and processing times per user. It also helps identify who is involved in rework loops, reversals, or compliance deviations, enabling targeted training or process improvements.

Why it matters

Identifies the user responsible for each activity, enabling analysis of user performance, workload distribution, and rework patterns.

Where to get

Typically from the BKPF table (USNAM field for creator) or the CDHDR table (USERNAME field for changer).

Examples
ABROWNCJONESDSMITH
Approval Time
ApprovalTime
The time elapsed from when a journal entry is submitted for approval until it is either approved or rejected.
Description

This metric measures the duration of the approval sub-process, which is often a significant contributor to overall cycle time. It is calculated as the time difference between the 'Journal Entry Submitted' activity and the corresponding 'Journal Entry Approved' or 'Journal Entry Rejected' activity.

Approval Time is the core metric for the 'Journal Entry Approval Performance' dashboard and the 'Average Journal Entry Approval Time' KPI. Analyzing this duration helps identify bottlenecks in the approval workflow, measure the performance of approvers, and justify process changes like adjusting approval thresholds.

Why it matters

Quantifies the duration of the approval stage, helping to pinpoint and address delays in the review and approval workflow.

Where to get

Calculated by subtracting the timestamp of the 'Journal Entry Submitted' event from the 'Journal Entry Approved' or 'Journal Entry Rejected' event.

Examples
P1DT2HPT4H15MP3D
Cost Center
CostCenter
An organizational unit within a controlling area that represents a location where costs are incurred.
Description

The Cost Center is a key master data element from the Controlling (CO) module, often assigned at the journal entry line item level. It is used to track costs for a specific department, function, or location.

Including Cost Center allows for a more granular analysis of the journal entry process. It can help determine if certain departments generate more rework, have longer cycle times, or are responsible for a higher volume of manual entries. This enables a departmental view of process efficiency.

Why it matters

Enables analysis of process performance by department or functional area, helping to pinpoint localized inefficiencies.

Where to get

Located in the document line item table BSEG, field KOSTL.

Examples
4100CC_FINANCE_US10010101
Currency Key
CurrencyKey
The currency code for the amounts recorded in the journal entry.
Description

This attribute specifies the currency of the journal entry, such as USD, EUR, or JPY. It provides context for any financial amounts associated with the document.

While not always a primary analysis dimension, it is crucial for interpreting monetary values correctly. It can also be used to segment analysis in global organizations to see if processes differ for entries in foreign vs. local currencies.

Why it matters

Provides necessary context for all monetary values, ensuring accurate financial analysis and interpretation.

Where to get

Located in the document header table BKPF, field WAERS.

Examples
USDEURGBPJPY
Cycle Time
CycleTime
The total time elapsed from the creation of the first journal entry activity to the final posting activity.
Description

Cycle Time is a key performance indicator that measures the end-to-end duration of the journal entry process. It is calculated by taking the difference between the timestamp of the final posting event and the initial creation event for a single journal entry.

This calculated metric is the primary measure on the 'Journal Entry End-to-End Cycle Time' dashboard and the 'Average Journal Entry Cycle Time' KPI. It provides a high-level view of overall process efficiency and is used to track the impact of improvement initiatives over time.

Why it matters

Measures the overall end-to-end efficiency of the process, providing a key metric for identifying bottlenecks and tracking improvements.

Where to get

Calculated by subtracting the timestamp of the first event from the timestamp of the last event for each case (JournalEntryId).

Examples
P2DT3H15MPT8H30MP5D
Is Parked
IsParked
A boolean flag indicating if the journal entry was saved as a parked document before being posted.
Description

Parking a document allows a user to save an incomplete journal entry without it affecting financial balances. It can then be completed or reviewed by another user before posting. This flag identifies entries that have gone through a parking step.

Analyzing this attribute helps understand the usage of the parking feature. It can reveal if parking is used as an informal review step, potentially causing delays. It supports analysis of the end-to-end cycle time, distinguishing between entries that are posted directly versus those that are parked first.

Why it matters

Identifies entries that use the parking feature, which can be a source of delay or an indicator of an informal review process.

Where to get

Derived from the document status field (BSTAT) in table BKPF. A 'V' indicates a parked document.

Examples
truefalse
Is Rework
IsRework
A boolean flag indicating if a journal entry has undergone a rework loop, such as being rejected and then corrected.
Description

This flag identifies cases that have deviated from the 'happy path' and required corrective action. It is typically set to true if a sequence of activities like 'Journal Entry Rejected' followed by 'Journal Entry Corrected' is observed for a given journal entry.

This attribute is essential for calculating the 'Journal Entry Rework Rate' KPI and for analysis on the 'Rework and Rejection Rate' dashboard. It helps quantify the extent of inefficiency in the process and provides a basis for investigating the root causes of rework, such as unclear requirements or insufficient documentation.

Why it matters

Flags entries that required correction, enabling the quantification of rework and analysis of its root causes to improve first-time-right rates.

Where to get

This is a calculated attribute, derived by analyzing the sequence of activities for a case. A rework loop is identified if a rejection or correction activity occurs.

Examples
truefalse
Reversal Reason
ReversalReason
A code indicating the reason why a journal entry was reversed.
Description

When a document is reversed, SAP allows the user to specify a reason code. This code provides structured information about why the reversal was necessary, for example, incorrect posting date or data entry error.

This attribute is a key input for the 'Journal Entry Reversal Analysis' dashboard. By analyzing the most common reversal reasons, organizations can identify systemic issues in their processes or training gaps, and take targeted actions to prevent future errors and reduce the reversal rate.

Why it matters

Provides direct insight into why reversals happen, enabling targeted root cause analysis to reduce future errors.

Where to get

Located in the document header table BKPF, field STGRD.

Examples
010205
Total Document Amount
TotalDocumentAmount
The total value of the journal entry in the document currency.
Description

This attribute represents the total financial value of the journal entry. It is typically calculated by summing the absolute values of all debit or credit line items associated with the document.

Analyzing the process by financial value can reveal important patterns. For instance, high-value entries may follow a different, more stringent approval path. This attribute can be used to filter or segment analysis to see if cycle times, rejection rates, or approval delays correlate with the entry's amount.

Why it matters

Allows for financial impact analysis, such as correlating processing times or rejection rates with the monetary value of journal entries.

Where to get

This is a calculated field, derived by aggregating the amount field (WRBTR or DMBTR) from all line items in the BSEG table for a given journal entry.

Examples
1500.0025000.75125.50
Required Recommended Optional

Record to Report - Journal Entry Activities

These are the key process steps and milestones to capture in your event log for accurate process discovery and optimization of journal entries.
5 Recommended 9 Optional
Activity Description
Journal Entry Approved
This activity marks the final approval of a journal entry within a workflow, making it eligible for posting. This event is captured from the workflow log when the final 'release' or 'approve' step is completed.
Why it matters

This is a key milestone that concludes the approval process. The duration leading up to this activity is a critical KPI for approval efficiency, and the time from this event to posting measures post-approval lag.

Where to get

Inferred from the completion timestamp of the final approval step in the SAP Business Workflow log. This is the last approval action before the document is posted or made ready for posting.

Capture

Identify final 'release' or 'approve' step completion in workflow logs.

Event type inferred
Journal Entry Parked
This activity marks the initial creation of a journal entry in a preliminary state, before it is officially posted to the general ledger. This is captured explicitly in SAP when a user saves a document using a parking transaction, setting the document status to 'parked'.
Why it matters

This is a critical start event for processes involving review and approval. Analyzing the time between parking and posting helps identify delays in the pre-posting and approval phases.

Where to get

This event is identified from the document header table BKPF. A document is considered parked when it is created with a status BKPF-BSTAT = 'V'. The event timestamp is the creation date and time, BKPF-CPUDT and BKPF-CPUTM.

Capture

Identify document creation in BKPF where BKPF-BSTAT is 'V'.

Event type explicit
Journal Entry Posted
This is the central activity where the journal entry is officially recorded in the general ledger, impacting financial statements. This event is captured explicitly when the document status is set to 'posted' and a posting date is assigned.
Why it matters

This is the most important milestone, signifying the successful processing of a journal entry. The end-to-end cycle time is often measured up to this point, and it is a key event for financial closing analysis.

Where to get

Identified when a document in the BKPF table has a posting date (BKPF-BUDAT). For parked documents, this corresponds to the moment the status BKPF-BSTAT changes from 'V' to blank. The timestamp of the posting is the entry date BKPF-CPUDT.

Capture

Identify when BKPF-BSTAT changes from 'V' to blank, or for direct postings, the creation event.

Event type explicit
Journal Entry Reversal Processed
This activity marks the reversal of a previously posted journal entry. A reversal is a new accounting document that cancels out the original entry.
Why it matters

This is a critical event for measuring data quality and process accuracy. A high rate of reversals points to systemic issues in the initial data entry or approval stages, and each reversal represents rework.

Where to get

This event is identified in the original document's header (BKPF table). When a document is reversed, SAP populates the reversal document number (BKPF-STBLG) and reversal reason (BKPF-STGRD). The event timestamp is the posting date of the new reversal document.

Capture

Identify when BKPF-STBLG is populated on the original document; timestamp is the posting date of the reversal document.

Event type explicit
Journal Entry Submitted
This activity signifies that a parked journal entry has been finalized by its creator and is now ready for review and approval. It is typically captured by the initiation of an SAP Business Workflow task associated with the parked document.
Why it matters

This marks the handoff from the creator to the approver, starting the clock for approval cycle time KPIs. It is a key milestone for measuring the efficiency of the approval workflow.

Where to get

Inferred from the start time of the approval workflow instance linked to the financial document object. This requires analyzing workflow log tables like SWW_WI2OBJ to find the workflow started for the specific company code, document number, and fiscal year.

Capture

Identify workflow start event for the parked document object.

Event type inferred
Cross-Company Posting Identified
A calculated activity that flags a journal entry affecting more than one company code. This is determined by analyzing the line items of a single financial document.
Why it matters

Cross-company transactions can have more complex processing and approval requirements. Identifying them allows for separate analysis of their cycle times and process paths to find unique bottlenecks.

Where to get

Calculated by examining the line item table BSEG for a given document number (BELNR). If the line items contain more than one distinct company code (BSEG-BUKRS), the entry is a cross-company posting.

Capture

Check if multiple unique values of BSEG-BUKRS exist for a single BKPF-BELNR.

Event type calculated
Documentation Attached
This activity represents a user attaching supporting documents, such as invoices or spreadsheets, to the journal entry. This event is not explicitly logged as a standard accounting event and is typically inferred by checking for the creation of attachments linked to the accounting document object.
Why it matters

Tracking this activity helps verify compliance with policies requiring documentation. Delays in attaching documents can be a root cause for prolonged approval cycles.

Where to get

This is difficult to capture reliably as a timestamped event. It can potentially be inferred by analyzing the Generic Object Services (GOS) attachment tables, such as SOOD, and linking the attachment creation timestamp to the journal entry object key.

Capture

Infer from creation timestamp of linked objects in GOS tables (e.g., SOOD).

Event type inferred
Journal Entry Changes Requested
Represents a point in the workflow where an approver has reviewed the journal entry and sent it back to the creator for correction. This event is captured from workflow logs indicating a 'rejection' or 'send back' user decision.
Why it matters

This activity is essential for identifying rework loops, which are a primary source of inefficiency and process deviation. High frequency of this event indicates issues with entry quality or unclear requirements.

Where to get

This event is inferred from the timestamp of a specific user decision step in the SAP Business Workflow log that corresponds to a 'reject' or 'send for correction' action.

Capture

Identify 'rejection' or 'rework' decision timestamp in workflow logs.

Event type inferred
Journal Entry Corrected
This activity indicates that the original creator has modified a parked journal entry after it was sent back for changes. It is inferred by detecting changes to the document after a 'Changes Requested' event.
Why it matters

Tracking corrections helps quantify the effort spent on rework. The time between a change request and the correction highlights delays in resolving issues with submitted entries.

Where to get

Inferred by analyzing change document logs (tables CDHDR and CDPOS) for the parked document. A change recorded after a rejection event in the workflow signifies a correction has been made. The timestamp is from the CDHDR table.

Capture

Identify change log entry in CDHDR/CDPOS after a rejection event.

Event type inferred
Journal Entry Created
Represents the creation of a journal entry that is posted directly, without a preceding parking step. This is captured when a document is created in SAP using a direct posting transaction.
Why it matters

This activity serves as an alternative starting point for simpler journal entry processes that do not require an approval workflow. It helps differentiate between simple, direct postings and more complex, parked entries.

Where to get

This event corresponds to document creation in the BKPF table where the document status BKPF-BSTAT is blank (posted). The event timestamp is the creation date, BKPF-CPUDT. For these documents, 'Created' and 'Posted' events occur simultaneously.

Capture

Identify document creation in BKPF where BKPF-BSTAT is blank.

Event type explicit
Journal Entry Line Item Cleared
This activity represents the reconciliation of an open-item managed G/L account line item, such as a bank clearing account. It occurs when a line item is matched against another, closing it out.
Why it matters

For processes like bank reconciliation, the time to clear items is a crucial KPI. This activity helps analyze the efficiency of reconciliation and month-end closing procedures.

Where to get

This event is captured from the line item table BSEG. When a line item is cleared, the clearing date (BSEG-AUGDT) and clearing document (BSEG-AUGBL) fields are populated. The timestamp of the event is the clearing date.

Capture

Identify when the clearing date (BSEG-AUGDT) is populated for a line item.

Event type explicit
Journal Entry Rejected
This activity signifies the final rejection of a journal entry, after which it will not be posted. This is typically a terminal status in an approval workflow, leading to the eventual deletion of the parked document.
Why it matters

Tracking rejections is crucial for quality management. Analyzing the reasons and frequency of rejections helps improve the first-time-right rate of journal entries.

Where to get

This is an outcome captured from the SAP Business Workflow log, representing a final 'reject' user decision that terminates the process. The parked document may subsequently be deleted.

Capture

Identify terminal 'reject' status in the workflow log for the document.

Event type inferred
Manual Entry Identified
This activity identifies if a journal entry was created through a manual online transaction versus an automated interface or batch process. This is not a user action but a calculated attribute of the entry, derived from system data.
Why it matters

Distinguishing between manual and automated entries is key to targeted process improvement. Manual processes are often the focus for standardization and automation initiatives.

Where to get

This is calculated by analyzing fields in the document header table BKPF. Transaction codes (BKPF-TCODE) like 'FB01', 'FB50', or 'FV50' indicate manual entry, whereas other T-codes or specific batch input names (BKPF-AWKEY) suggest automation.

Capture

Derive from BKPF-TCODE or other source system indicators in the document header.

Event type calculated
Parked Journal Entry Deleted
Represents the deletion of a parked journal entry that was never posted. This can occur after a rejection or if the entry was created in error.
Why it matters

This activity marks an unsuccessful end to the process. Analyzing why parked documents are deleted can reveal issues such as duplicate entries or process misunderstandings.

Where to get

This event is captured when the status of a parked document in the BKPF table is changed. The status field BKPF-BSTAT is updated to 'Z' (Parked document deleted). The change timestamp can be found in the document change logs (CDHDR).

Capture

Identify when BKPF-BSTAT is updated to 'Z'.

Event type explicit
Recommended Optional

Extraction Guides

How to get your data from SAP ECC