Time-Dependency in the Accrual Engine versus Time-Independency of Purchase Order Data
Purchase Order Time-Independency
- Purchase orders are time-independent: All changes made by users (e.g., via transaction ME22N) are valid immediately for all times
- Changes overwrite the original value in the purchase order
- Users do not need to enter a date for when changes become valid
Accrual Object Time-Dependency
- Accrual objects in the Accrual Engine are time-dependent: Users must enter a date from which each change becomes valid
- Reason for time-dependency: Accrual objects generally represent contract-like data, and contracts can be time-dependent
Purchase Order Accruals Application
- Accrual objects can be created for purchase orders
- Changes to purchase order data trigger corresponding accrual object changes
- Example: Changing the net price in a purchase order item requires adjustment of the total amount to be accrued in the accrual subobject
Automatic Date Determination
- When users maintain purchase orders (e.g., transaction ME22N), they cannot enter a date for change validity
- The system automatically determines a reasonable datefrom which the change becomes valid in the accrual object
- This date determination logic is hard-coded in the system
1. Create or Delete PO Items
Events Influencing Accrual Amounts in the Accrual Engine for Purchase Orders:
Creation of the Purchase Order
- Customizing determination: The Purchase Order Accruals application customizing determines whether an accrual object will be created
- Status requirement: The purchase order must have a suitable status
- Time-independency: The new purchase order is created in the Accrual Engine as time-independent (table ACESOBJ)
Creation of a New Purchase Order Item
- Customizing determination: The Purchase Order Accruals application customizing determines whether an accrual subobject will be created
- Account assignment handling: For each account assignment given in a purchase order item, a separate accrual subobject will be created
- Accrual item creation: The customizing of the Purchase Order Accruals application determines:
- Which accrual items are created
- Which algorithms they use to calculate and post the periodic accrual amounts
- Technical validity period: The new purchase order item is created in the Accrual Engine to be technically valid all time: from 01.01.0001 until 31.12.9999 (table ACESOBJ_ITEM, fields LIFE_START_DATE and LIFE_END_DATE)
Deletion of an Existing Purchase Order Item
- Deletion restriction: Once a purchase order item is created and saved, it cannot be deleted
- Alternative action: Users can mark the item as to be deleted (EKPO-LOEKZ)
- Posted accruals constraint: If accruals have already been posted, the accrual subobject cannot be deleted any more
- Status change: The status of the accrual items of the corresponding accrual subobject will be set to Obsolete
- Accrual consequence: Accruals will be set to zero as a consequence in future fiscal periods
- Retroactive validity: This change is valid in the Accrual Engine for all time, including former periods
2. Change PO Item
Changes of an Existing Purchase Order Item That Affect Accruals
Accrual Method Dependency
- Algorithm-dependent impact: Whether changes in the purchase order affect accruals depends on the accrual method, that is, on the accrual calculation algorithm
- Customer-programmed algorithms: Since the algorithms can be programmed by the Customer, it is not possible to provide a complete list of changes that will affect the accruals
Three-Step Approach Impact
- Formula: Accruals = plan minus actual
- Change scope: All changes in the purchase order (item) that affect the planned costs will affect the accruals
Replicated Data from Purchase Order to Accrual Engine
Only few data are replicated by the system from the purchase order (item) into the Accrual Engine:
- Total planned costs
- Start of Life date and End of Life date: Determined during the replication; these dates determine the date interval between which the costs are planned to be accrued
Impact of Changes on Replicated Data
- Update trigger: Changes in the purchase order (item) that affect the replicated data will lead to an update in the accrual subobject
- Temporal validity: These changes are valid in the Accrual Engine for all time, that is, from 01.01.0001 until 31.12.9999 (table ACESOBJ_ITEM, fields LIFE_START_DATE and LIFE_END_DATE)
Changes of an Existing Purchase Order Item That Affect Accruals (Three-Step Approach)
Changing the Delivery Schedule
- Changing delivery date or quantity in existing entries
- Source: Transaction ME23N
- Impact: Affects the total planned costs and/or the life time
Creating a new entry in the delivery schedule (or deleting an existing one)
- Impact: Affects the total planned costs and/or the life time
Changing the Net Price in the Purchase Order Item
- Impact: Affects the total planned costs
Changing the Item Category of a PO Item
- Example: From Standard to Limit
- Consequence: Can lead to different accrual item types and methods
- Determination source: Due to the Customizing in IMG activity “Define Accrual Item Types and Methods for MM Purchase Order Items” (transaction ACEIMG)
- Reference: See separate slide for details
Adding a New Account Assignment
- Structural impact: Leads to a split of the accrual subobject into two subobjects
- New subobject creation: The new accrual subobject is created in the Accrual Engine to be technically valid all time, that is, from 01.01.0001 until 31.12.9999 (table ACESOBJ_ITEM, fields LIFE_START_DATE and LIFE_END_DATE)
Accrual Method PLN_LIND_P Overview
- Method name: Planned costs with linear distribution
- Functionality: This method distributes the total amount of the accrual subobject linearly between the Start of Life and End of Life date that is given in the accrual subobject
Changes Affecting Accruals
- Changes in Total Amount
- Impact: Changes in the purchase order that change the total amount of the purchase order item will lead to different accruals
- Example: Changing the net price of the purchase order item in transaction ME22N
- Changes in Service Period (Lean Services)
- Applicable scenario: The method PLN_LIND_P can be used for purchase order items that represent a Lean Service
- Date entry capability: In Lean Services, the user can enter a Start Date and End Date in the purchase order item between which the service is planned to be received from the supplier
- Date replication: These dates are replicated into the accrual subobject as Start of Life and End of Life
- Consequence: Changing the start or end date in the purchase order item in transaction ME22N will affect the accruals
Definition of Lean Services
- Identification criterion: Lean Services means that in the purchase order item, the field Product Type Group has the value 2.
3. Set Delivery Complete Indicator in PO Item
Overview of Delivery Complete Indicator
- Purpose: Setting the indicator Delivery Complete in the purchase order item signals that no further goods receipts or costs are expected
Goods Receipt and Accounting Posting
- Posting mechanism: If valuated goods receipts are posted for a purchase order item, these goods receipts post the costs in Accounting
- Accrual relevance: Since accruals are usually posted for costs that are expected for future fiscal periods, no accruals are required as soon as the last goods receipt was posted
Effect on Accrual Amounts
- Requirement: As soon as a user has set the indicator Delivery Complete in the purchase order item, the accrual amount for the future fiscal periods must be zero
- Note on timing: What “future” exactly means in this case will be explained
- Conditions for Accounting Posting
If the following conditions are met, the goods receipt will perform a posting in Accounting:
a) The indicator Goods receipt is true AND
b) The indicator GR non-valuated is false
- Cost posting: If the purchasing document item has an account assignment like cost center, then costs will be posted
Manual Setting of Delivery Complete Indicator
- User action: The indicator Deliv. Compl. (=Delivery Complete) in the purchase order item is set manually by a user
- Meaning: If it is set, then this means that no further goods receipt, that is, no further costs, is expected: No accruals are needed any more
Time-Independence of Delivery Complete Indicator
- User capability: In the purchase order item, a user can set the indicator Delivery Complete
- Time-independent characteristic: This indicator is time-independent
- Information limitation: The purchase order item does not store the information from which date onwards this indicator is valid
Accrual Calculation Effect
- Accrual amount requirement: For the accrual calculation, setting this final indicator means that the accrual amount must be = 0 after the posting date of the final goods receipt
- Pre-posting period accruals: Before this posting date, still goods receipts are expected – and as a consequence potentially accruals are required
For System Process to Achieve Zero Accruals After Delivery Complete is Set, please refer to the KBA 0003803785
4. Set Final Invoice Indicator in PO Item
Setting the Final Invoice Indicator in PO Items
- Scenario with No Valuated Goods Receipts: When no valuated goods receipts are posted for a purchase order item, supplier invoices directly post costs to Accounting.
- Purpose of Accruals: Accruals are typically posted for costs expected in future fiscal periods. Once the last invoice is posted, accruals are no longer needed.
- Setting the Final Invoice Indicator: The “Final Invoice” indicator in the purchase order item is set either:
- Manually by a user, or
- Automatically during posting of the final invoice
- Effect of Final Invoice Indicator: When the indicator is set, it signifies that:
- No further supplier invoices are expected
- No further costs are expected
- No accruals are needed anymore
- The accrual amount for all future fiscal periods must be reduced to zero
- The specific meaning of “future” in this context will be explained in subsequent documentation
- Functional Equivalence: The “Final Invoice” indicator (used when there are no valuated goods receipts) produces the same effect for accruals as the “Delivery Complete” indicator (used when there are valuated goods receipts) – both signal that no further accruals should be posted for the purchase order item.
Time-Independent Nature of Final Invoice Indicator
- Indicator Characteristics:
- A user can set the “Final Invoice” indicator in the purchase order item
- This indicator is time-independent
- The purchase order item does not store information about the date from which the indicator becomes valid
Effect on Accrual Calculation
- Accrual Amount Requirements:
- After the posting date of the final goods receipt, the accrual amount must equal zero
- Before this posting date, goods receipts may still be expected
- Consequently, accruals may still be required before the final goods receipt posting date
System Steps to Achieve Zero Accruals After Final Invoice Indicator is Set
Step 1: Replication into Accrual Engine
- During replication of the purchase order into the Accrual Engine
- If the “Final Invoice” indicator is true in the purchase order item
- The system changes the status of the accrual subobject to “Prematurely Finished” (status “F”)
Step 2: Saving the Posting Date
- The system saves the posting date of the final invoice in the accrual subobject
- This is stored in the field “Premature Finish Date”
- This approach ensures that after the posting date of the final invoice, posted accruals will be released
Step 3: Release Posting
- The next accrual posting run will perform a release posting
- This release posting results in an accruals balance of zero
Alternative Approach
If Three-Step Approach is Not Used:
- The used (customer-defined) accrual method must return zero as the accrual amount after the posting date of the final invoice
- This requirement must be considered in the source code of the customer-developed accrual method
Data Fields Updated
Lifecycle Status and Premature Finish Date:
- Both fields are filled when the “Final Invoice” indicator is set in the purchase order item
5. Change PO Item Category or Customizing
Changing the Item Category of a Purchase Order Item
Customizing Dependencies:
- The customizing that defines how a purchase order item is transferred into the Accrual Engine depends on:
- Purchasing document type
- Purchasing item category
- Other factors
Scenario:
- A user changes the item category of an existing purchase order item
- An accrual subobject already exists for this item
- A different customizing setting becomes relevant as a result
Potential Consequences: When the item category is changed, the accrual subobject may experience:
- Creation of new accrual items
- Deletion of existing accrual items (if no accrual postings exist yet)
- Marking of existing accrual items as obsolete (if accrual postings already exist)
- Updates to existing accrual items (for example, if only the accrual method changes)
User Impact and Recommendations
Potential Confusion:
- Changes to accrual items, especially creation of new items or existence of obsolete items, may confuse end users when they display the accrual subobject using transaction POACTREE03
Recommended Practice:
- In the Customizing activity “Define Accrual Item Types and Methods for MM Purchase Order Items” (viewcluster VC_TPOAC_PO_ACRTM)
- Use the same accrual item types for all entries in the section “Define accrual item type and method based on PO item”
- This approach avoids confusion
6. Set Block/Unblock Indicator in PO Item: KBA 0003803746
Source link