Show TOC

 Detection Method: Alternative Payee (Flip-Flop Payee) – Company-Code Specific

 

The detection method reads the master data changes of vendors and checks whether, within a given period of time:

  • A previous change of the field Alternative Payee exists for the same vendor, and

  • This change has been reversed by the current change.

These checks are made within a single company code.

If these conditions apply, then the method checks whether any invoices have been paid during the period of time in which the alternative payee was changed. The detection result is 50 for changes without payments and 100 for changes with payments. The risk value is the aggregated payment amount in the investigation currency.

Logic

The business logic is the same for both versions of the flip-flop payee detection method.

For each change in the incoming data table, the execution procedure checks whether a payment has taken place in the critical period (between the flip-flops of the alternative payee name). To make this check, the procedure joins the incoming data table with the database tables BSEG and BKPF and selects the company code, the vendor, the change date and time as well as the connected change date and time where the client equals the session client, the account type (KOART) equals K, the posting key (BSCHL) is 25 and the date on which the accounting document was entered (CPUDT) is greater than the connected change date as well as lower than the change date.

If the date on which the accounting document was entered is equal to the connected change date, then the time on which the accounting document was entered (CPUTM) must be greater than the connected change time.

If the date on which the accounting document was entered is equal to the change date, then the time on which the accounting document was entered must be lower than the change time. This selection leads to a table with all the changes with payments in the critical period.

To find all payee changes without payments, the procedure collects company code, vendor, change date, change time, connected change date, and connected change time from the incoming data table that are not in the first selection of the procedure.

The result is built by setting 100 as detection result for changes with payments and 50 for changes without payments and combining the table of the changes with payment with the table containing the changes without payments.

Investigation and Detection Object Types
  • Investigation object type: FRA_VMDCHG (Vendor Master Data Change)

  • Detection object type: FRA_VMDCHG (Vendor Master Data Change)

ERP Tables Used
  • CDHDR: Change document header

  • CDPOS: Change document items

  • BKPF: Accounting Document Header

  • BSEG: Accounting Document Segment

  • T001: Company Codes

SAP HANA Procedures for Detection Methods

Procedure Category

Procedure Name

Procedure Type

Package

Selection

PR_VENDOR_PAYEE_DATA_CHANGED_COMP_CODE_SELE

SQLScript Procedure

sap.hana-app.fra.suite.pur.dt.vendormasterchng.se

Execution

PR_VENDOR_PAYEE_DATA_CHANGED_COMP_CODE_EXEC

SQLScript Procedure

sap.hana-app.fra.suite.pur.dt.vendormasterchng.ex

Additional Information

PR_VENDOR_PAYEE_DATA_CHANGED_ADDINF

SQLScript Procedure

sap.hana-app.fra.suite.pur.dt.vendormasterchng.ai

Detection Method Parameters
  • REVIEW_PERIOD_IN_DAYS: Period in days in which changes to the alternative payee are to be sought.

Alert Messages

Message ID

Message Number

Message Text

FRA_INTERNAL_AUDIT

070

Time when the alternative payee was changed the last time: &1 &2

FRA_INTERNAL_AUDIT

071

The document number of the payment is &1