Use the following tests to validate report setup:

Use the tests below to validate report setup.

Validate DSSO

Note: 

LSF patches occasionally impact DSSO. If the connection to LBI worked previously and LSF updates have been applied, consider updating DSSO. Issues related to DSSO or service setup will commonly be indicated by an authentication error displayed on the screen when a user attempts to launch My Reports.

  • If the DSSO installation was successful on the LBI server, you should be able to access the following forms:

    http:// webserver:port /ssoconfig/SSOCfgInfoServlet

    http:// webserver:port /sso/SSOServlet

    where webserver:port is the HTTP transport port for the application server where the application and DSSO are deployed or, if you are using redirection through a web server, the web server port number.

    For more information, see the Distributed Single Sign-On Solution Installation Guide.

Validate OLEDB

  • Verify OLEDB setup.

    Access Start > All Programs > Lawson Software > Oledb Object Services > Lawson OLE DB Administrator.

    The UseSSOFactory field should be checked when the Crystal Server box at the bottom of the pane is checked. This checkbox is labelled "Apply for Windows Service Properties" in Oledb version 9.0.5

    The UseSSOFactory field should not be checked when the Crystal Enterprise Server box is not checked.

  • Validate OLEDB connections.

    In LBI there will be two datasources for the reports. Lawson Landmark maps the report to the Landmark dataarea and Lawson Classic maps to the S3 Enterprise Applications database. Make sure you can access these two datasources from the LBI server using Lawson OLEDB by executing a test query from Query Builder for Lawson OleDB Object Services.

  • Enable OLEDB logging.

    If you are troubleshooting a specific report, support will find an OLEDB log helpful. To enable logging, access the PC or server with OLEDB installed and access Start > All Programs > Lawson Software > Oledb Object Services > Lawson OLE DB Administrator. Logging does slow down processing, and the log file can get large, this option should be turned off when not in use.

Validate Landmark setup

Note: 

If you see an error indicating that a page does not exist or that the LBI link is invalid when launching My Reports, these steps will help in identifying the problem.

  • Verify the configuration parameters in Landmark.

    In the Landmark Rich Client, access Data Menu > dataarea > la > Business Classes > ConfigurationParameters.

    The My Reports link in Landmark concatenates the Configuration Parameter variables to construct the URL to access LBI.

  • Validate and export these values to a csv output for reference. Only the values in italics are specific to your system, the others should have the values shown.

    LBI_FSHOST_INT
    http://MyServer.MyCompany.com:9999
    LBI_LOCATION_EFS
    /efs/FSRemote?remtype=redirect&CMD=GETLIST&stylesheet=ersReports.xsl
    LBI_LOCATION_EFS_SOURCINGBUYER
    &list=sourcingbuyer
    LBI_LOCATION_EFS_CONTRACTMANAGER
    &list=contractmanager
    LBI_PARM_REMURL
    &remurl=
    LBI_RSHOST_INT
    http://MyServer.Mycompany.com:9999
    LBI_LOCATION_ERS
    /ers/ersLists.jsp?
    LBI_SERVICE_NAME
    LBI_DSSO (the LBI service shown in the LBI Configuration Administrator)

  • Verify the LBI service is defined as a Landmark service. One additional Configuration Parameter variable must be validated for single sign on (not required for the previous test).

    The LBI Service Name in the LBI Configuration Administrator and assigned in the Configuration Parameters should be a service in Landmark.

  • In the Landmark Rich Client, access Service Details.

  • Verify the Service field contains a value that is exactly the same as the LBI_SERVICE_NAME in Configuration Parameters.

    Service Type
    Form Based
    Service Protocol
    HTTP Only
    Login Scheme
    Same as service name.

  • Verify the Landmark ServiceURL pattern for the LBI service in Landmark.

    In the Landmark Rich Client, access Data Menu > gen > security > Business Classes > ServiceURLPattern.

    Verify the Service field contains a value that is exactly the same as the LBI_SERVICE_NAME in Configuration Parameters.

    Service Url Pattern
    1
    Value
    The LBI server name surrounded by period and asterisk .* characters. If the FQDN of the LBI server is http://MyServer.MyCompany.com:9999, the value in this field should be: .*MyServer.MyCompany.*

Validate LBI setup

  • Make sure the Sourcing Buyer and Contract Manager Lists have been created in LBI.

    Assign users to lists. User groups or custom groups are frequently used to simplify user assignment. Users must be assigned to reports and lists after loading solution packs.

  • In LBI, access Report Administration > My Reports > report Lists

    There should two lists with the following filters.

  • Review the sourcingbuyer list:

    Join
    And
    Type
    Sourcing
    Operator
    Equal To
    Value
    1

  • Review the contractmanager list:

    Join
    And
    Type
    Contract Management
    Operator
    Equal To
    Value
    1

  • Make sure the Lawson Landmark and Lawson Classic datasources have been created in LBI.

    When setting up datasources, verify the connection information using a direct connection in Lawson OLEDB.

  • Verify the Lawson Landmark datasource.

    Verify Data Source
    Lawson Landmark
    Type
    Lawson Landmark Connection
    Data Area
    Not required. A data area will default, but you can specify it.
    User Name, Password
    User and password are not required. If not included here, the user will have to login when they run a report using the datasource.
    IOS Communication Protocol
    http or use https if required.

  • Verify the Lawson Classic datasource.

    Verify Data Source
    Lawson Classic
    Type
    Lawson Data Connection
    Data Area
    Not required. A data area will default from the Lawson Portal.
    User Name, Password
    User and password are not required. If not included here, the user will have to login when they run a report using the datasource.
    IOS Communication Protocol
    Select the appropriate connection.
    Test Saved Connection
    Can be used to validate the data connection (for Classic type data source only).

  • Make sure the Reports.zip report solution pack has been loaded from the S3 Supply Chain Management Applications built with Landmark deliverable into LBI.

    The reports.zip file is in the LASRCDIR/dataarea/reports/Procurement directory.

  • To load a solution pack, select Load Solution Pack on the Reporting Services Administration form.

  • From the Solution Pack Detail form select Apply Solution Pack to create and deploy the reports into LBI.

  • Make sure users have been assigned to reports and lists in LBI.

    Each report must be updated with the users allowed to access it. If a user in not assigned the report will not appear in the report list even if they have access to the list.

Validate reports from LBI

Note: 

If multiple reports fail, are the failing reports related to the Classic or Landmark environment? If only one type of report is failing it may indicate that the application database is not currently available. Test the connection using OLEDB and if that fails contact the administrator.

  • To test OLEDB access to database. In LBI, access Report Administration.

  • Go to a failing report and access Report Detail.

  • In the left panel, select from Datasource and identify any override datasource the report is using.

  • From the LBI server desktop select: Start > Lawson Software > Oledb Object Services > Lawson Querybuilder to launch OLEDB and test the connection used in the report datasource.

    If Then
    You cannot launch OLEDB. Reinstall the latest version of OLEDB, if the error persists contact support.
    You are able to enter the connect information, login and password but OLEDB fails to connect, the database is currently not available. Verify login and check with an administrator.
    You are able to login to the database through OLEDB, but cannot view tables. This is most likely related to a Landmark environment and may be a build/deployment issue. Review the related build/deploy logs for errors and check with an administrator.

  • To test if the report runs In Crystal, launch Crystal Reports on the LBI server. Note the version information in Help > About, and then open the problem report from the LBI report repository directory and save it to a new file for testing.

  • Open the new copy of the report.

  • From the Crystal Report menu, select Database > Verify Database.

  • Assign the datasource information to the test report and select finish to save.

    There may be a series of parameter prompts presented as the new datasource information is saved. Assign valid values to the first parameter form. If additional parameter forms appear after that simply select OK. Each series of parameters represents a command that is being updated with the new daasource.

    If Then
    You receive and error related to access or authentication. Verify login information, user access and server availability.
    You receive and error indicating a failure during generation of schema information for the command. Verify that the latest reports have been loaded. This often indicates the report query does not match the fields available in the database.

  • After the message "The database is up to date" appears, select OK and save the updated test report.

  • Execute the report.

    If Then
    The report completes normally, but continues to fail in LBI. Contact support.
    Report completes normally but no data is returned or the report fails. Collect error information, OLEDB log information, version information (for Crystal and OLEDB) and contact support.

Verify Connection

Note: 

After you have completed the Landmark, LBI, and Report Validation you should be able to test the My Reports link and reports from the presented list.

  • Test the My Reports menu link from Sourcing Buyer.

  • Verify correct reports appear.

    The list of reports available in Strategic Sourcing is available in the Strategic Sourcing User Guide. The list of reports available in Contract Management is available in the Contract Management User Guide.

  • Verify that both Landmark and S3 Enterprise Applications reports run:

    Supplier Listing is a Landmark report that lists records from the Landmark supplier table

    Commodity Spend By Vendor is an S3 report that lists spend from the S3 Enterprise Applications MAINVDTL file