Symptom
Purchase order item was created and transferred to the accrual engine as purchase order accruals object.
But when running accrual job, the period accrual amount calculation is fully posted, regardless of accrual rule defined in customizing.
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Environment
SAP S/4HANA Cloud Public Edition
Cause
The G/L account assigned in the section ‘account assignment’ is a Balance Sheet Account.
It causes the invoice or good receipts of the purchase order not considered as the actual cost by accrual engine, so the period accrual amount calculation is not expected.
Resolution
It is possible to exclude such Purchase Orders from Accrual Engine with below implementations.
NOTE: After BADI implementation, job ‘Purchase Order Accruals - Transfer Purchase Orders to Accrual Engine’ needs to be executed for PO concerned.
- For PO not existing in Accrual Engine, it will never be created as an accrual object.
- For PO already in Accrual Engine but with no accrual/deferral posting, corresponding accrual object items will be deleted.
- For PO already existing in accrual engine and with accrual/deferral posting, corresponding accrual object items will be obsolete.
Option 1: Enhance the BADI POAC_ACCRUAL_OBJECT_ITEMS in app Custom Logic.
then clear the OUT_ACCRUALOBJECTITEMS if it meets the criteria.
Option 2: Enhance the BADI POAC_PO_ITEM_CLASSIFICATION in app Custom Logic.
Change OUT_ACCRUALCLASSIFICATION value for example ‘99999’ which is not configured in SSCUI 102505 - Define Accrual Item Types and Methods for MM Purchase Order Items:
Keywords
Purchase Order Accrual, Accrual Engine, account assignment, accrual object, exclude. , KBA , FI-GL-GL-POA-2CL , Purchase Order Accruals (Public Cloud) , Problem