Purchase Order Terms with Item Category “Limit” (Value B, EKPO-PSTYP = 1)
Delivery Schedule Issues:
- Only one entry exists in the delivery schedule, making accrual calculations based on the schedule meaningless
Date Limitations:
- No explicit start and end dates are available in the purchase order item for linearized distribution of the total amount
- System defaults used instead:
- Start date: Purchase order document date (EKKO-BEDAT)
- End date: The single delivery schedule entry date
Amount Valuation Issue:
- System uses purchase order item net value as the total accrual amount
- The expected value field (ESUH-COMMITMENT) would be more suitable
Customization Option:
- Use BAdI POAC_MMPO_2_ACE_TRANSFER or Enhancement Spot POAC_ACCR_OBJECT BAdIs for different accrual behavior
Purchase Order Terms with Item Category “Service” (Value D, EKPO-PSTYP = 9)
Delivery Schedule Issues:
- Only one entry exists in the delivery schedule, making accrual calculations based on the schedule meaningless
Date Availability Constraints:
- Start and end dates for linearization are only available:
- When business function PSM_USFED_PEROP_1 is active (public sector)
- In the Services tab of transaction ME23N (stored in tables ESLH and ESLL as ESLL-PER_SDATE and ESLL-PER_EDATE)
- These tables are currently not evaluated by the system
Default Dates Used:
- Start date: Purchase order document date (EKKO-BEDAT)
- End date: The single delivery schedule entry date
Customization Option:
- Use BAdI POAC_MMPO_2_ACE_TRANSFER or Enhancement Spot POAC_ACCR_OBJECT BAdIs for different accrual behavior
Source link