Introduction

You can import self costs and other data from StoreHouse 5 to r keeper_7 online. This requires Feature Server coupled with interactive reports. Therefore, before setting up the import you need to install and launch the following:

i_Guid={D54BA83D-EA0F-4ADC-834D-70C336259F6D}
instance_name=171848
MasterServer=1

Manager Station Settings

To enable the import, you need a properly established connection with MS SQL and interactive reports, and an installed WebAPI 2 server connected to StoreHouse 5.

  1. Go to  Extensions > Database.
    1. If you see the following error message: Invalid Object Name PLG_OBJECTS

    2. Open the MS SQL browser and execute the script:

      CREATE VIEW [dbo].[PLG_OBJECTS] AS
SELECT
GUIDSTRING
,CODE
,NAME
,ALTNAME
,STATUS
FROM dbo.RESTAURANTS
WHERE (STATUS = 3)

      The error message should disappear.

  2. Right-click the ALLCONST section and select the Create New Database Group. Rename it as you wish

  3. Right-click the group and create a new database

  4. Staying the group menu, click on the database in the right-hand menu and fill in the fields:
    1. Name
    2. Specify the data for connecting to the WebAPI 2 server in the Basic section:
      1. Login — StoreHouse user name

      2. Password — StoreHouse user password

        A StoreHouse user must have a password

      3. Connection string — network connection data for WebAPI in the IP:PORT format, for example: localhost:9797
    3. In the Other section:
      1. Check the SH5 box​
      2. Fill in the Params Date Begin and Params Date End
    4. In the StoreHouse Import Parameters section

      1. Enter the import data parameters in the Currency and Group goods fields​

        The currency and group goods can only be selected if the connection to the StoreHouse server is successful

      2. There is no need to fill in the SH Location field

      3. If a special inventory is performed in StoreHouse, check the Special accounting and Count in units of measurement "for expenses" boxes

    5. Click Save 

  5. The connection has been set, now you need to check it. Right-click the database in the left-hand menu and select Checking DB Connection...

    • ​If the connection is set correctly, the following message will appear:

    • If the connection is set incorrectly, the following message will appear:

  6. Now, link the object to the newly created database in the left-hand list. In order to do so, right-click the right-hand field and select the Add New Object.

    Click Add and save the changes.

  7. Open StoreHouse 5 and make sure that there is at least one department in the counterparties. If there is none, create one.
    To do this, open Dictionaries > Counterparties > Departments.

    If there are no enterprises, create one.

  8. In the manager station, go to Menu > Menu Classifications and copy the GUID of the classification you are planning to use. The classification should have nested categories.

    1. Stop the Feature Server and open its configuration file —  IRReportsFSPrj.ini.

    2. Add the following line into the [FS_ADDITIONAL] block:

      SH4_Class={B07330CD-D17E-4151-AC2F-DE341C163C7D}

    3. And insert the classification's copied GUID after the = symbol. If there is no [FS_ADDITIONAL] section, add one

    4. Save the file and launch the Feature Server

  9. Go to  Options > Head Office > Restaurants and right-click the restaurant that needs to be linked with StoreHouse. Select item Actions > SH restaurant editor.

  10. Select the required categories. In the Store House 4 field of their properties, select the unit from which the department will be downloaded.
    Do not pay attention to the field name, everything will operate properly.

  11. If the classifications are visible but there is no selection of departments, make sure that:
    • There are departments in the StoreHouse 5 database. There should be at least one.
    • If there are departments in StoreHouse, then there should be a department list in the SQL database base_name_STAT_SH4_SHIFTS_FOODCOST in table STAT_SH4_SHIFTS_CORR. The department TYPECORR field should equal 0.
    • If there are no records with TYPECORR=0 in the SQL database, clear the Feature Server log folder, change the StoreHouse database connection name and click Save. Therefore, FS should request data from StoreHouse 5 once again.
  12. Save and close the manager's station.

  13. Add the following text at the end of the configuration file of the interactive report plugin RK7MAN\plugins\SchRepPluginClient\ini:

    [PLG_ACC]
use_accounts = 1
[PLG_PLAN]
use_plan_params = 1
[PLG_SH]
use_sh_params = 1
  14. Save the changes and launch the manager station.

Import Launch

Launch the following servers:

  • UCS Common
  • Feature
  • WebAPI 2
  • StoreHouse 5

And open the manager station.

If all settings are correct, Feature Server will start loading the data from StoreHouse 5 to r_keeper 7 for the selected period:

If the Feature Server log has the Date Invoice Load lines, then it is functioning properly.

You can recalculate the StoreHouse data by opening Interactive Reports (IR) > Reports on safety > System Operations and clicking Recalculate SH Data.

Feature Server Upgrade

If your installed interactive report plugin and Feature Server are outdated, it is recommended to upgrade them. Early FS versions require that the FS and SQL be installed on the same computer but this is not obligatory for version 1.36.

In order to update the Feature Server and plugin:

  1. Download the latest version from the FTP server  ftp://ftp.ucs.ru/rk7/other/IR_reports/
  2. Unpack the archive in a convenient location. Copy and replace all files in the installed FS folder. There is no configuration file in the archive, so the existing settings will not get lost.
  3. Close the manager station and copy the archive's contents from the plugins folder to the manager station's plugins folder.
  4. Launch FS and the manager station.

Troubleshooting

Issue: after upgrading r_keeper to version 7.6.5.459, Feature reports do not work.

Reason: STAT_SH4_SHIFTS_CORR table is not filled.

Solution: upgrade Feature Server to version 1.39.1.7 or later.


  • No labels