Skip to main content

ReadSoft: How to use the ReadSoft "Custom project account generator" interface for project accounting validation

Article # 301723 - Page views: 113



Support Article

For customized project accounting validation solutions, the ReadSoft PROCESSIT Customization Workbench provides the Custom project account generator interface. This interface allows for source code to be entered and executed in place of the PROCESSIT default functionality. 

Screen Shot 2018-08-09 at 10.13.58 AM.png

When a user clicks the Validate button Screen Shot 2018-08-09 at 10.16.42 AM.png within the PROCESSIT Accounting Workbench, the system checks whether the Custom project account generator interface is active. If it is active, the corresponding code is executed.

Screen Shot 2018-08-09 at 10.14.10 AM.png

For this article, the source code EPS-ProjectAccountGenerator is used. This code can be downloaded here  and edited as necessary for individual implementations.

According to this code, there are two processing options:

  1. Use the APPS schema. If the value of the useAppsSchema parameter is true, the URL and user credentials are assigned by other trailing variables.
    Screen Shot 2018-08-09 at 10.14.26 AM.png
    If the value is false, the URL and user credentials will come from the built- in jdbc/D4_OEBS_APPS connection as defined by Weblogic.
    Screen Shot 2018-08-09 at 10.14.40 AM.png
  2. Use hard-coded test parameters. If the value of the useTestParameters variable is true, then variables that are ultimately passed to the project accounting package are statically assigned and are not passed in from the Accounting Workbench.
    Screen Shot 2018-08-09 at 10.14.50 AM.png

    During execution, if the APPS schema method is used, the returned ccId and concat_segs information is returned to PROCESSIT via the interface's response object.
    Screen Shot 2018-08-09 at 10.15.02 AM.png

    In addition, dbms_output is enabled so a thorough database tracing can be directed to the log4j log file. Tracing for this process is elevated to the debug level via a method call to aps.fnd_flex_workflow_apis:

         sql.execute('{call apps.fnd_flex_workflow_apis.debug_on}');

    The dbms_output text is written to the log4j log file via the printTrace method after the call to the xxd4_appps.xxd4_bpel_projectaccounting package.
    Screen Shot 2018-08-09 at 10.15.20 AM.png
    Screen Shot 2018-08-09 at 10.15.33 AM.png
    Additionally, the code uses setLog statements that are appended to the log4j file. One benefit of using this interface is that the dbms_output information from the package calls are also appended to the log4j file.Screen Shot 2018-08-09 at 10.15.51 AM.png

Keywords: Customisation

  • Was this article helpful?