You can use this detection method to find purchase orders to which an excessive number of changes have been made.
When a purchase order is created, a limited number of changes may be expected after the purchase order has been saved. If however the number of changes exceeds a defined limit, then the legitimacy of the changes that have been made needs to be verified.
This method detects those purchase orders in which a defined limit of changes was exceeded.
The execution procedure selects all purchase order numbers (PO
) from the Input Parameters table IT_PO_DETAIL
on an inner join with table CDHDR
on the purchase order number (OBJECTID
).
Then it counts the number of changes (NR_OF_CHANGES
) from table CDHDR
, field CHANGE_IND
for each distinct purchase order number, where the CHANGE_IND
does not have the attribute I
(I
= insert), the client (MANDT
) equals the session client, and the field OBJECTCLAS
has the attribute EINKBELEG
.
The THRESHOLD_CHANGES
input parameter specifies the minimum number of changes that must have been made. An alert is generated if the NR_OF_CHANGES
– the number of changes made to a purchase order – is greater than the parameter THRESHOLD_CHANGES
.
Investigation object type: FRA_PO
(Purchase Order
)
Detection object type: FRA_POHEAD
(Purchase Order Header
)
EKKO
: Purchasing Document Header
CDHDR
: Change Document Header
LFA1
: Vendor Master (General Section)
Procedure Category | Procedure Name | Procedure Type | Package |
---|---|---|---|
Selection |
| SQLScript Procedure |
|
Execution |
| SQLScript Procedure |
|
Additional Information |
| SQLScript Procedure |
|
THRESHOLD_CHANGES
: Limit on allowed number of changes (such as 5) on a purchase order.
Message ID FRA_INTERNAL_AUDIT
, message number 082; Purchase order &1 was changed &2 times within the purchasing process