Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this page is to clarify the understanding of SAP Business Planning and Consolidation, version for Microsoft  (BPC MS) script logic and provide an overview on ways to troubleshoot issues.

Overview

  • Script Logic allows you to define formulas to perform calculations & data conversions using BPC dimension members and data (i.e. Rate*Price, Rate*Expense, Increase by 10%, Move Data to Finance). 
  • Customers can have many different logic scripts (or calculations) occurring within their model (application set). 
  • They can be run automatically (Default.LGF), via Data Manager or with the Script Logic Debugger located in the BPC Administration client.
  • The Default.LGF file is a special logic file that will get executed on every data input/send from an input template (EPM Add-in / Web) or when you choose “Yes” to the “Run Default Logic” prompt from a Data Manager package (i.e. Import)
  • Script logic files are stored as text files within the operating system or Netweaver File System and there two files for each script logic
    • LGF - ASCII logic File used to create/edit logic calculations and is accessed through Script Logic editor in the Administration Console
    • LGX - ASCII logic eXecution (or compiled) file, created by BPC when you validate and save logic file
      • Performing a "Validate and Save", replaces all *INCLUDE and *SELECT statements with compiled/validated results in your LGX file

Structure

Script logic has three main areas. They are:

Debugging Approaches

  • Try to identify which logic syntax is not working
  • All script logic is custom written, but uses standard BPC proprietary keywords. For a full listing of the key words please see: Script Logic Help
  • Business rules executed via a stored procedure are also run via script logic (i.e. *RUN_STORED_PROCEDURE = SPRUNCALCACCOUNT([%APP%],[%CATEGORY_SET%],[%GROUPMBRS%],[%SCOPETABLE%], [%LOGTABLE%])
  • *XDIM_MAXMEMBERS statement is the key for memory errors
    • Syntax: *XDIM_MAXMEMBERS {dimension}= {max number of members}
    • i.e. *XDIM_MAXMEMBERS Entity = 50 (Only 50 entities will be selected at a time)
  • Look at the follow key items
    • Logic files (LGF/LGX) & any logic library files (LGL/LGT)

    • Logic files stored in following location:

      • ..\BPC\Data\Webfolders\<ENVIRONMENT_NAME>\ADMINAPP\<MODEL_NAME>\

    • Logic library files stored in following location:

      • ..\BPC\Data\Webfolders\<APPSET_NAME>\ SYSTEMLIBRARY\LOGIC LIBRARY\

    • Get logic files called by *INCLUDE, *SYSLIB &*RUNLOGIC statements:

      • i.e. *INCLUDE FXTrans.LGF

      • *SYSLIB SYSTEM_LIBRARY.LGL

      • *RUNLOGIC YTDACTUAL.LGF

    • Logic run via a Data Manager (DM) package generates logic log file and are stored in the following location:

      • ..\BPC\Data\Webfolders\<ENVIRONMENT_NAME>\<MODEL_NAME>\PRIVATEPUBLICATIONS\<USER_NAME>\TempFiles

      • In example below, the debug logic file when it is run from Data Manager is named
        • i.e. Debuglogic_<Random Sequence Number>_<Random Number>.LOG
      • Note: If the Default.LGF is executed from a data send, then the log file is named: Debuglogic.log and stored in the same folder mentioned above without the random numbers in the name.

Related Content

Related Documents

Related SAP Notes/KBAs

__________________________________________________________________________________________________________

Use this structure to help you compose your contributions for WIKI and at the same time will ensure spelling and grammar.

  • No labels