Administration > Utility programs > Server management introduction > Server management > Planned activities tab > Examples of activities - robinfeng/beashelp GitHub Wiki

Configuration of Server management

Server management Introduction
Server Management Administration tab Protocol Planned activities tab Examples of activities E-Mail tab Extended tab Distributed server landscapes Troubleshooting

In the server management the following task are available by default:

serverevents liste

Each task has its own description

serverevents beschreibung

Task Description Calculate MRP Computes all calculations, which were activated for automatic computation. Calculate Batch-PreCalculation Computes all batch pre-calculations, which are enabled for automatic computation See Batch-calculation Calculate Pool (full) Computes the resource pool including the active pool (1x daily) Calculate Pool (refresh) Computes the resource pool, but leaves pool 1 unchanged Database-Check Performs a data check and records the existing data integrity problems. This is the same check, which is performed after a program update. Stop beas service At least once a day the server service on the Windows Task Manager should be at to restart The beas service must be terminated first. Please wait at least 10 minutes between exit and restart. Refresh planned time of resource Calculates the time available the resources and resource groups. This is normally done online, but it should be recalculated from time to time. TriggerDailyEvent (Event System: Event daylyevent "and Milestone-Check) In events daily messages can be created, based on this event.

Script- Examples Script

object=ue_mrp=server All MRP runs which have been selected for automatic calculation are calculated tools=runbeas=batchcalc=1 Batch precalculation with the specified number x is automatically calculated.

Script Description Compute MRP object=ue_mrp=server Compute all recommendation reports marked for automatic calculation Pre-calculation tools=runbeas=batchcalc=1 Batch-pre-calculation with the given number is calculated Computation of lead time and material requirement setvar=is_itemcode_from= setvar=is_itemcode_to=zz setvar=is_itempropertie= setvar=is_save_leadtime=true setvar=is_save_material=true setvar=is_save_resource=true object=ue_mrp=resourcenplanung

Computes material and resource requirement and the lead time per production lot size (oitm.leadtime)

Information is saved in tables beas_oitm_material and beas_oitm_resourcen. It can be used as basis for MRP - rough planning.

The function can be called-up manually via item structure list. Calculate expiration date // 10.12.13 M.Heigl

// batch number destroy=lds declare=lds=ue_datastorevalues lds=select obtn.itemcode+'' as itemcode,obtn.sysnumber+0 as sysnumber,isnull(obtn.mnfdate,getdate()) as mnfdate,oitm.u_haltbark+0 as haltbark from OBTN inner join oitm on oitm.itemcode=obtn.itemcode inner join obtq on obtq.itemcode=obtn.itemcode and obtq.sysnumber=obtn.sysnumber where obtq.quantity>0 and obtn.mnfdate is not null and oitm.u_haltbark>0 for ll_loop=1 to <lds.rowcount> lds.setrow=<ll_loop> setvar=ld_date=%workday(<lds.mnfdate>,<lds.haltbark>) sql=update obtn set expdate=<ld_date,dbdate> where itemcode=N'<lds.itemcode>' and sysnumber=<lds.sysnumber> next destroy=lds

// serial number declare=lds=ue_datastorevalues lds=select osrn.itemcode+'' as itemcode,osrn.sysnumber+0 as sysnumber,isnull(osrn.mnfdate,getdate()) as mnfdate,oitm.u_haltbark+0 as haltbark from OSRN inner join oitm on oitm.itemcode=osrn.itemcode inner join osrq on osrq.itemcode=osrn.itemcode and osrq.sysnumber=osrn.sysnumber where osrq.quantity>0 and osrn.mnfdate is not null and oitm.u_haltbark>0 for ll_loop=1 to <lds.rowcount> lds.setrow=<ll_loop> setvar=ld_date=%workday(<lds.mnfdate>,<lds.haltbark>) sql=update osrn set expdate=<ld_date,dbdate> where itemcode=N'<lds.itemcode>' and sysnumber=<lds.sysnumber> next destroy=lds

Calculates the expiration date for all batches and serial numbers, which are currently in stock

beas starting paramter "task=" With this parameter a stored activity is executed directly and beas is closed down afterwards. see access parameters

Restart: Elaborate calculation functions use up a lot of memory, which in some cases is not released. For this reason, a server task that restarts beas must be stored:

// End Applikction app=close

Configure the service to start automatically after the service was ended. Windows-services - "Properties of beas Service" for "first", "second" and "third" error: "restart service", Reset error counter after "1" days.

Log file beas reads c:\xampp\apache\logs\error.log-file. Only the first 30 lines are read in. In general, this file should be deleted regularly, calling beas-server administration the file is deleted automatically.

返回 主页