Customization Settings

Updated 3 days ago by Marco Kretschmann

Introduction

Important
Incorrect settings can have serious consequences. Please adjust these settings only in case of emergency and with utmost care!

Where can you find the Script?

  • Log in to Diligent Highbond
  • Open Robots
  • Open Robot & Downlaod Robot: Download will start automatically
  • Open the data Analytic_Suite.acl with a double click: ACL opens
  • In the directory tree on the left side you will find the _Customization_Settings

How do you edit the script?

Double click on _Customization_Settings and the data opens in the right area. You can then change it.


Add SAP-systems

How further SAP systems can be added is described in detail in the _Customization_Settings in the ACL project (default: from line 91):

COM +++ SAP SYSTEMS
COM ------------------------------------------------- 
COM * there can be defined multiple connection strings, by naming the variables v_DL_SAP_Source_Str_[SAP_System] and v_DL_SAP_SystemID_[SAP_System]

COM * where [SAP_System] is the value, that is chosen in parameter dTXT_TF13_SAP_System
COM * Please always fill in the value of the SystemID in the variable v_DL_SAP_SystemID_SAP
COM * Please note that the content of [SAP_System] needs also be availbale in Robots-Paramter dTXT_TF13_SAP_System in script __Run_AnalyticSuite (or __Run_AnalyticSuite_Desktop)

COM -> //PARAM dTXT_TF13_SAP_System C VALUES |SAP|SAPSystem2| SAP System

Download Monitor in the Results module

  1. Activate the Download Monitor: Set parameter Download Monitor to True:
  1. Before starting the Run: create a new table in the Results module. It's useful to create an individual Collection & Analysis and create the monitoring table in it
  2. After creating the table: open it and copy/note the last number from the URL shown above:
    1. That is the table-ID, it's needed for further processing
    2. Script _Customization_Settings: Set the variable V_Cust_Spec_MonitoringID with the table-ID as value
  3. Import the DummyUpload.xlsx (contains Dummy data) in the created table:
    1. Contains the necessary columns and a row with dummy data
    2. Necessary, as the Primary Key can only be set if there is data in the table:
      1. For each downloaded table, two data records are uploaded (start and end of the download). All important information is in the last data record (end of download), so the first data record should be overwritten with the second.
      2. The Primary Key must be defined: at the end of the download process, only one data record with all data is available.
  4. Open table Settings: For Primary key (optional), select the ID field and save the change
  5. Once the first run has been completed and the first real data has been uploaded, the dummy data can be removed

Analysis of Duplicate Payments and Credits

Implementation of R

First execution of AP_Dupl_Payments

  1. Customization Settings: activate False-Positive Detection and OneLine Result
    1. Set the variable v_AP_DuplPaym_OneLine to T
    2. Set the variable v_AP_Dupl_Paym_DoAI to T
COM +++ AP_DuplPayments + AR_Dupl_CreditNotes
COM ------------------------------------------------- 
COM * Flag if the one line result should be created

ASSIGN v_AP_DuplPaym_OneLine = "T"

COM ** AP_DuplPayments: Use AI for a better detecion of false-positives

COM *** First you need to enable the function
COM *** ASSIGN v_AP_Dupl_Paym_DoAI = T
ASSIGN v_AP_Dupl_Paym_DoAI = T
  1. If necessary, set a specific path for the pool: create variable v_AP_Dupl_Paym_AI_ExpPath and fill it with the chosen path
  2. Open TF_Import and go to the sheet FieldlistSelection: make sure that the following three columns in the event table AP_Dupl_Payments_OneLine are marked with X for the Results Upload:
    1. AI_Assessments
    2. AI_Potential
    3. AI_Meta_Information
  3. Activate and configure upload to Results (select New Collection)
  4. Create a Robot Task and execute it

ToDo's after the first execution

  1. Questionnaire: set it for the created Collection
    1. Name e.g. Detection of true or false duplicate payments
    2. Linked tables: Chose OneLine table and save
    3. Create a new question: Type Single Selection
      1. Question e.g. Is the record a true or false duplicate payment
      2. Add possible answers:
        1. True Duplicate Payment
        2. No Duplicate Payment
      3. Important: Change column display name to Manual Assessment
Important
It is crucial that at least 5 positive data records and at least 5 negative data records are marked before the next run! Otherwise the AI recognition will not work!
  1. Process data records: until the next Run of Duplicate Payment
    1. at least 5 positive data records (True Duplicate Payment)
    2. at least 5 negative data records (No Duplicate Payment)

Other versions (CCM)

  1. Create a Collection: open and copy the table-ID of OneLine Results Table
  2. TF_Import (Sheet SchedueledResultsUpload): also enter the ID for table AP_Dupl_Payments_OneLine
  3. Import the adjusted TF_Import in the Robot
  4. Change Upload to Results to Existing Tables
  5. Execute it again

Tax Code Analytics

The following parameters in the script GL_TaxCodeSample are important and mandatory (also see the next Code block):

  1. v_GL_TaxCodeSample_Size: 5
  2. v_GL_TaxCodeSample_Type: TOP
  3. v_GL_TaxCodeSample_Filter: 1 = 1
  4. v_GL_TaxCodeSample_Partner: T
COM +++  GL_TaxCodeSample
COM ------------------------------------------------- 
COM Number of Samples selected within each of Sales Tax Code   
ASSIGN v_GL_TaxCodeSample_Size = "5"

COM Type of Sample selection - "TOP" will select TOP of v_GL_TaxCodeSample_Size entries within each Salex Tax Code, "SAMPLE" will select random sample of v_GL_TaxCodeSample_Size entries within each Salex Tax Code.  
ASSIGN v_GL_TaxCodeSample_Type = "TOP"

COM Filter to Exclude Tax Codes from being selected. Example - v_GL_TaxCodeSample_Filter= " NOT MATCH(BSEG_MWSKZ 'AN' 'VN') "
ASSIGN v_GL_TaxCodeSample_Filter = " 1 = 1 "

COM Flague - Only one Partner per Tax Code should be Reported   
ASSIGN v_GL_TaxCodeSample_Partner = "T"

The purpose of the analysis is to select a sample from GL_BaseTable based on the values of BSEG_MWSKZ (tax code). The value of the parameter determines how many entries are selected in each existing data record code of BSEG_MWSKZ.

There are two methods for sample selection:

-          TOP

-          SAMPLE

Option TOP: the top N entries from each BSEG_MWSKZ are selected (N is the value of the variable v_GL_TaxCodeSample_Size). The data record is sorted in descending order according to the amount in reporting currency (BSEG_DMBTR).

Option SAMPLE: N entries are randomly selected from each BSEG_MWSKZ (N is the value of the variable v_GL_TaxCodeSample_Size). The selection is made using the Record Sample method.

Parameter v_GL_TaxCodeSample_Filter: enables additional filters for table GL_BaseTable before samples are generated. Default value 1 = 1 means that GL_BaseTable generated by default is used.

Parameter v_GL_TaxCodeSample_Partner = T: each sample selected is from a single partner. Otherwise, when using the TOP method, it is possible that samples are selected for the same partner (BSEG_LIFNR, BSEG_KUNNR).

How did we do?

Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)