Noteworthy with Orgasoft.NET and Hypersoft

item master data

Up to now, the required item master data has been created directly in each system. The transfer of such information has so far been limited to units that can be transferred from Orgasoft.NET to the Hypersoft item master. In this context, Hypersoft can also be used to create items. Some fields in the Hypersoft item master are blocked or hidden, for example those for the Hypersoft supplier master. Example view of the item master with activated Orgasoft.NET integration, in which, among other things, the order variants in Hypersoft are hidden:

Allergens, ingredients, etc...

Together with Signum, we are pursuing the possibilities of digitising this information from suppliers and possibly transferring it to Hypersoft. This is not supported at present or in the short term.

Hypersoft cash bookings

All cash register entries are uploaded to Orgasoft.NET for statistical evaluation without goods movement with the daily closing.

Units and inventory data initial workflow

Inventory handling...

The moment an existing item on the Hypersoft side is linked to an item from Signum, the following situations can occur.

Inventory management was in Hypersoft
Inventory management was in Signum
Inventory management was on both sides

As Orgasoft.NET is the leading system in terms of stock levels, an inventory must be carried out before the items are linked in Orgasoft.NET so that all stocks are available there. These recorded stocks are then transferred there during connection and synchronisation with Hypersoft and existing stocks in Hypersoft are automatically removed. The existing inventories are logged for later research.

The transfer of stocks from Orgasoft.NET always flows into the storage location of the item, so the stocks in the points of sale are set to 0 (zero). Depending on the workflow, you can then populate or book it.

If the old stocks in Hypersoft are only mathematical and have no historical relevance, it is better to remove them with the zero setting, as you do not need a log. Read here how to zero the stock levels before connecting the item masters.

The process for transferring all stocks from Orgasoft.NET can be repeated as required. This may be necessary if the procedure could not be followed when connecting the item masters.

Further documentation: Transfer stocks from Orgasoft.NET

Units...

Before stocks can be synchronised automatically, the unit for the respective item must have been reconciled in both systems! The program conveniently supports the unit adjustment when connecting the articles by transferring them from Orgasoft.NET and converting them in Hypersoft (also in existing recipes).

Both when you start working with Orgasoft.NET and Hypersoft together and in day-to-day operations, you do not have to pay any particular attention to the synchronisation of inventory data. A control entry in Hypersoft that leads to stock changes (standard) also transmits these to Orgasoft.NET.

All stock changes due to cash bookings are separated into their components and uploaded to Orgasoft.NET at an adjustable interval. The recipes for this are maintained in Hypersoft. Of course, with suitable items, "recipes" can also be treated as items in Orgasoft, thereby dispensing with a recipe calculation in Hypersoft (convenience items, other methods).

Hypersoft recipes and inventory service...

The Hypersoft inventory service works as usual with all functions, as do the availability items.

EK/DEK for stock transfer and goods movements from Orgasoft.NET / Signum

When transferring the current stock of a base item, which always takes place when an item is transferred from Orgasoft.NET to Hypersoft, the DEK, KEK, VEK and LEK are transferred once from Signum and overwrite the previous values in Hypersoft.

Further documentation: Purchase prices in the hypersoft system

From this point onwards, the DEK is always recalculated each time the goods movements are transferred from Orgasoft.NET, taking into account the saved goods movements or stocks and the new goods movements.

Calculation formula and example:

Already booked quantities times the stored DEK plus new goods movement times EK of the movement, divided by already booked movement plus new goods movement.

((QuantityAltWE * DEK ) + (QuantityWE * EKSignum)) / (QuantityAltWE + QuantityWE)

Example: 100 * 5.00- + 50 * 4.50 / 150 = 4.83

In addition, the purchase price from the goods movement is always saved in Hypersoft as LEK (last purchase price).

Disposition monitor

You can use the Hypersoft MRP Monitor together with Orgasoft.NET and benefit from real-time stock control with re-bookings and work instructions. Of course, the options for supplier orders are not calculated with the MRP monitor but are handled exclusively in Orgasoft.NET.

Hypersoft supplier base

The Hypersoft supplier master cannot be used with Orgasoft.NET, you use Orgasoft.NET for this.

Hypersoft order centre

In the order centre, the items linked to Orgasoft.NET are hidden for orders and goods receipts. Transfers to points of sale and to loss remain possible in Hypersoft.

Goods receipts and chargebacks...

Stock changes such as goods receipts or back postings in Hypersoft are not supported with the Orgasoft.NET integration.

Goods receipts in Orgasoft.NET...

The goods receipts in Orgasoft.NET are posted to the storage location of the item in Hypersoft. This applies both to the standard main warehouse and to items that are stored directly at a point of sale.

Loss postings from Hypersoft to Orgasoft.NET

Loss postings from the order centre...

All loss postings from the order centre are uploaded to Orgasoft.NET with the standard, adjustable interval.

Further documentation: Call-up interval in minutes

Loss postings on Hypersoft POS/mPOS...

If a loss reason is assigned an abbreviation for the export, these bookings are transferred separately from the POS and mPOS to Orgasoft.NET after the daily closing. It is then a so-called G data record that is transferred with a so-called incident abbreviation. These postings can then be analysed separately in Signum. Example of export settings for losses:

Orgasoft.NET stock changes

Goods receipts, return deliveries, various inventory changes...

All goods receipts / return deliveries / stock changes at Orgasoft.NET are downloaded from Orgasoft.NET at an adjustable interval and booked into Hypersoft.

Further documentation: Call-up interval in minutes

Inventories from Orgasoft.NET...

All inventories in Orgasoft.NET are transferred to Hypersoft as inventory changes.

Control registration

All loss postings from a control entry are uploaded to Orgasoft.NET at an adjustable interval.

Further documentation: Call-up interval in minutes

Standard controller acquisition supported...

Hypersoft control entry with the standard overwriting of local stocks (full synchronisation) is also synchronised with Orgasoft.NET in the standard system. However, generally pay attention to the "pitfalls in practice" with controller versions. For example, start here and click on links to related topics: Post the recorded stocks for processing

Further documentation: Set up Signum Orgasoft.NET connection

Back to the parent page: Hypersoft & Signum Orgasoft.NET co-operation