Detection Method: Manual Change to Payment Proposal
Use this detection method to find payment proposals to which manual changes have been made.
Note that exceptions in payment proposals are disregarded.
Logic
The execution procedure finds vendor payment proposals that have been manually changed by checking whether the run ID (field LAUFI
) and the run date (field LAUFD
) from table REGUP
exists in table REGUA
. If this is the case, then alerts are created for all vendors related to the run ID and run date. This detection method returns a score of 100.
The additional information procedure determines the users who changed the payment proposal (field UNAME
in table REGUA
) and calculates the risk amount, which is the sum of the manipulated payment proposals (field RBETR
in table REGUH
) aggregated by vendor.
The field WAERS
from table T001
is the currency key for the amount field RBETR
in table REGUH
. These two tables are joined at the company code (field BUKRS
in table T001
) and the paying company code of the payment proposal (field ZBUKR
in table REGUH
).
Investigation and Detection Object Types
Investigation Object Type:
FRA_VEND
(Vendor
)Detection Object Type:
FRA_VEPAY
(Payment Proposal
)
ERP Tables Used
REGUA
:Change of Payment Proposals: User and Time
REGUH
:Settlement Data from Payment Program
REGUP
:Processed Items from Payment Program
REGUHH
:REGUH Version Before the 'n'th Change
T001
:Company Codes
SAP HANA Procedures for Detection Methods
Procedure Category | Procedure Name | Procedure Type | Package |
|---|---|---|---|
Selection |
| SQLScript Procedure |
|
Execution |
| SQLScript Procedure |
|
Additional Information |
| SQLScript Procedure |
|
Detection Method Parameters
None
Alert Messages
Message ID FRA_INTERNAL_AUDIT
, message number 091, Payment proposal for vendor &1 was changed by &2