Area
|
Good performance
|
Maximum *1)
|
Maximum of Bill of Materials Entries by Position or work order
Attention:
If you work with Phantom items, the count of BoM Entries is the sum of all BoM Positions of all Phantom items.
|
|
< 500
|
5 000
|
Routing positions per assembly or Work order
|
< 500
|
5 000
|
Sub structure: max. Levels
|
< 20
|
20
|
TIP: If you need more Positions, you can split them to several work orders.
|
|
< 50
|
500
|
The number is related to "active" Bill of Materials Position.
This number is related to "per MRP Scenario".
Example:
If you have 1 000 000 open BoM Entries for the next 12 months, but in your scenario you must calculate only next 2 weeks ~50 000 entries, it runs without problems.
If you've too many entries, the MRP can crash. In this case you can change activate the calculation by block, example read next 10 000 entries, calculate, read next 10 000 entries.
You can activate this for existing MRP scenarios with the following command:
update "BEAS_MRP_PLANUNG" set FTSTLBlock = 10000
if you create new MRP scenarios, you must execute the SQL statement again.
|
|
< 10 000
|
50 000
|
APS Calculation / Scenario:
Max 2000 Work order position and max. 10 000 active routing positions and bill of material positions.
Workaround: Create different scenarios
|
|
< 1 000
|
10 000
|
Count actual running routing position
|
< 50
|
500
|
Count of open sales order
|
< 500
|
5 000
|
Sum of all Demands (Work order, Sales order, Purchase order)
TIP: You can reduce the count with
- Split between long- and short time planning.
- Activate the summary function for the complete scenario or for all items that do not need detailed information.
|
|
< 50 000
|
500 000
|
Check if you need a new item for every Variant.
In Beas it is possible to create a work order from a Calculation, by Variant or by Configuration without creating master data previously.
Work with Item Version:
You can define Versions of an item without creating a new Item Master Data.
|
|
< 10 000
|
100 000
|
If you need a warehouse by customer or external warehouse, you can work with Bin Management and can define a Bin Location for every Customer.
|
|
< 20
|
100
|
Count of Business Partners
|
< 10 000
|
200 000
|
Count of parallel users
|
< 100
|
500
|
Currently max. 99 price lists are supported.
If you have more then 99 price lists, use only price list 1–99 inside Beas valuation.
|
|
99
|
99
|
TIP: If performance is not satisfactory, you can install more than one WEB service.
Beas WEB APP Version 1.0: Limit is 20 / Service.
|
|
< 20
|
50
|
With an extensive number of transactions inside SAP Business One or in SAP Business One over Beas, SAP Business One may lose performance. This may cause database locks for up to some minutes.
If you work with WEB APP Terminal Version 1, the system creates the transaction serial (Beas common service – asynchronous process). This helps reducing problems.
Solution for WEB APP Terminal Version 2.1 is in the pipeline.
|
|
< 10
|
20
|
Recommendation based on the internal functioning of SAP Business One:
As the high number of transactions may cause the system to slow down gradually, it is important to clean up the database every year with the SAP Business One Tools.
|
|
< 1 000
|
10 000
|
Beas use SAP Business One for every transaction (receipt, issue, purchase order and so on)
SAP Business One allows for handling a maximum of 10 000 rows.
|
|
< 1000
|
10 000
|
Max. Database Size
|
< 20 GB
|
100 GB
|
 MRP Computation time
Where calculation is performed, the computer should meet the following minimum requirement:
| o | Adequate processing power |
| o | Make sure that a minimum number of parallel services are running. A parallel running database service. for example may block the memory. |
| • | Large number of items in the database: |
If the database contains a large number of items, the number of items to be displayed should be limited.
| o | Display only purchase products, only in-house production, or only some of the items properties. |
| o | Display only items with planned inflow or outflow, or inventory shortfall (check for minimum inventory). This is set up in the scheduling scenario – planning. |
| • | A lot of peggings: A lot of peggings create a lot of records. This may adversely affect the computation time. To speed up the calculation, try to summarize daily, weekly or monthly. This can be defined in the MRP scenario, but also on item level. |
| • | The calculation of lead time for assemblies is computationally intensive. Work with the replenishment lead time instead. This might be a little more inaccurate, but it reduces the computation time significantly. See Detail – compute lead time for assemblies. |
| • | Forecasts: Forecasts can be computed using gross calculation. This computation is less exact, but faster and is sufficiently accurate for long-term planning. See Detail – gross calculation |
|
|
|
|