New
2019-01-29
13388
2
F1-> always use English documentation
beas 9.3-001-002-000 / beas 9.3H-001-002-000
Beas\Administration

Online documentation F1


We close the German documentation and continue only with the English version.
In Parallel we are working on a better quality English variation.

New:
If you click on F1, beas always opens the English documentation 
Buttons "English" and "German" are deleted.
New Button "Reload" = reoload current page

window system_helphtml
 
Beas\Administration\Data Import and Export
2019-06-17
10868
2
Integration Hub import WO BOM
beas 9.3H-001-012-000 / beas 9.3H-001-004-000 / beas 9.3-001-012-000 / beas 9.3H-001-013-000
Beas\Administration\Data Import and Export
For better automatic processes it is now possible to import and synchronize work order, work order positions and work order - Bill of materials


 

Example:

In the old system you have all Item Information, Bill of Materials and Routing information.

You can import this with the integration hub

 

After this you can import work orders.

You define only the Assembly on top level. 
beas reads all Bill of materials and Routing information from imported master data.

 

It is not possible to import routing or Bill of materials for every work order separately.

import_workorder1

 

A third application can define the work orders inside beas. You can use this, if you have an external planning tool for production in stock.

import_workorder2

 

 

 

import_workorder3

 

Example: You must produce a machine and while producing you continue with the technical planing

Now you can import and synchronize the bill of material in the work order directly from the cad program.

 


Overview about all new import defintions

 

Area

Insert

Update

Work order header (BEAS_FTHAUPT)

 

Use this, if you want update the header information or if you want to create new work orders and you need for work order position only the item code and quantity.

Insert all header informations

Insert first work order position with Itemcode and quantity

beas explode bill of material, routing position and all order related sub assemblies.

 

Not possible:

base reference to other documents

other properties from work order line

 

You can change the work oder type, but you can't change the work order type related flags.  beas will ignore this

 

You can't define the document number (BEAS_FTHAUPT.BELNR_ID), only the order number (BEAS_FTHAUPT.AUFTRAG)

most of properties changeable

 

you can not change the created work order positions.

 

beas will ignore the property itemcode and quantity.

 

Work order position (BEAS_FTPOS)

 

Use this to import work order positions with extented position information.

You can define the Assembly, but beas use always the bom and routing information from item master data.

 

If you don't define a work order number, beas will create a new work order.

Add position to existing workorders

 

beas explode bill of material, routing position and all order related sub assemblies.

 

Create a new workorder, if you don't define a work order document (BELNR_ID=0)

 

Not possible:
Define additional information for work order header, if the system create a new work order.

 

Define linked information

It's not possible to update existing positions.

Bill of material (BEAS_FTSTL)

 

use this to synchronisate the BoM with external programs.

 

you can add and change bill of material position from existing work order positions.

Mandatory is the work order document number, work order position and bill of material position.

 

if you try to insert a exiting bom position, then beas make an update

 

beas don't explode order related assemblies.

you can't create multilevel work orders.

you can update every property from a existing bill of material position.

 

beas don't change existing sub position.

 

You can delete a bom, if you set the quantity to 0. You can delete only, if no related transaction or reservation exists.

Routing position

not possible

not possible

 



 

 

Follow fields mandatory

- document number, work order position number, bill of material - position number

- quantity

You can change entrys only, if changes are allowed and the work order position is not closed

 

Position number:

You've follow position numbers:

- the internal position number. If this is a new number or if it's 0, beas create a new position line

- if you don't set the Position text, beas set same number in Position text

- the internal position number don't define the sorting. You must define this separatly - see sorting

 

Position text:

- if you don't set this, beas insert the defined or generated internal Position Id

- you can define and change this every time

 

ItemCode

- Item Code is mandatory, item must existing

- the integration hub don't check additional rules

- if you change the item and related position or reservation or transactions existing, beas don't change anything

- if you insert a order related item, beas DON't create a order related sub position!

 

Delete Bill of material position

It's possible to delete an existing Bill of material position

beas need the fields: BELNR_ID,BELPOS_ID and POS_ID and Quantity=0

if any transaction is existing on this position, you can't delete this position

if reservation existing, beas delete the reservation

if this a order related assembly, beas delete all related sub positions.

if a deletion of sub position not possible, beas close all related sub positions.

 

Sorting (SortId)

define the Sorting inside the Bill of material position

You can define a positive number or you can define follow sorting rules

 

 

 

 

Sort Id

Description

-1

order by internal Position number. The system search by position, which is lower as the current position and higher as all other position, get this sortid, increment this with 1 and define this as sortid from current position

 

Example:

Pos 10 - Sort 10

Pos 20 - Sort 20

 

You insert Pos 15

 

Pos 10 - Sort 10

Pos 15 - Sort 11

Pos 20 - Sort 20

 

This is a fast variant, because beas must only insert Pos 15

But in other situation this can generate a problem

 

Example:

Pos 10 - Sort 1

Pos 20 - Sort 2

 

You insert Pos 15

 

Result

Pos 10 - Sort 1

Pos 20 - Sort 2

Pos 15 - Sort 2

 

In this case Pos 20 and Pos 15 have the same Sort id and it's not clear, which position is the first position.

-2

order by internal position number

 

In this case beas sort the complete bill of material position by internal position number

Problem: It must save every change from every bill of material position

 

Pos 10 - Sort 10

Pos 20 - Sort 20

Pos 30 - Sort 30

 

You insert Pos 15

 

Pos 10 - Sort 10

Pos 15 - Sort 20 <- insert

Pos 20 - Sort 30 <- update

Pos 30 - Sort 40 <- update

 

if you must insert 100 Position, then this concept produce lot of change requests. Don't use it for mass import

-3

order by Position text - alphanumeric

 

Example

Pos Text A10 Sort 10

Pos Text A20 Sort 20

Pos Text A50 Sort 30

 

You insert position with Pos Text = A30

Pos Text A10 Sort 10

Pos Text A20 Sort 20

Pos Text A30 Sort 20 <- insert

Pos Text A50 Sort 30 <- update

 

Attention: if you work with numbers, you've follow situation

 

Example

Pos Text 10 Sort 10

Pos Text 20 Sort 20

Pos Text 100 Sort 30

 

Insert Position Pos Text = 50, you've follow result (alphanumeric sorting)

 

Pos Text 10 Sort 10

Pos Text 100 Sort 20 <- update

Pos Text 20 Sort 30 <- update

Pos Text 50 Sort 40 <- insert

 

-4

order by Position text - converted by number

 

Example

Pos Text 10 Sort 10

Pos Text 20 Sort 20

Pos Text 100 Sort 30

 

You insert position with Pos Text = 50

Pos Text 10 Sort 10

Pos Text 20 Sort 20

Pos Text 50 Sort 30 <- insert

Pos Text 100 Sort 40 <- update

 

if you insert a position with alphanumeric position text, beas set this to first position

Example: insert position with text A001

 

Pos Text A001 Sort 10 <- insert

Pos Text 10 Sort 20 <- update

Pos Text 20 Sort 30 <- update

Pos Text 100 Sort 40 <- update

 

 

 

2019-01-29
7663
2
Integration hub: Import absence information
beas 9.3-001-006-000 / beas 9.3H-001-008-000
Beas\Administration\Data Import and Export

Integration hub

new: import absence information for personnel entry



you can import and update this information
Primary key for update is the personal id and the From date
window: importkopf_edit.psr



 
2019-01-29
12565
2
Data Integration Hub, BEAS_APL_WKZ, Field 'anteil' (Time Reservation %) is missing
beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\Administration\Data Import and Export > Zendesk id: 58954

Integration Hub - Import Routing - Parallel resource


importkopf_edit.psr

Past:
It was not possible to import field "Time Reservation"

New:
Now you can import this field
 
Past:
Field description was not clear in Integration hub - source- target link

New:
Now all fields are described in the correct way and you can select more fields:
 
 

2019-01-29
8405
2
integration hub - Source target link - Editor issue
beas 9.3-001-004-000 / beas 9.3H-001-004-000
Beas\Administration\Data Import and Export

In the integration hub you can link a source field with a target field



Additionally you can define a conversion script, if you cannot move the source information 1:1 to the target or if you need additional conditions

Past: It was only a simple text editor. Usability was not good
New: Now it is an extended editor. Usability is very good and a small assistant helps you to create the script



If you set the cursor in the Conversion editor, the editor will be active

For all features see our online documentation

Beas\Administration\License
2019-01-29
8709
2
More information on "no License case"
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Administration\License
If you start a function without valid license: 
PAST:  Message:
"You don´t have a valid license for this feature"

NEW: More information
You don´t have a valid license for this feature (Module: <modul>, Station: <station>, User: <user>)

Example
if you do not have an APS View license for your current station, you can see now your Module, Station and User


 
2019-01-29
12928
2
License Assignment in RDP Session, APS Gantt Viewer had problem with lower/upper case
beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\Administration\License
Past: we had a license problem especially in beas APS Gantt Viewer, which is station (session name) related.
The reason was a problem with lower/upper case 

New:
beas check is not case sensitive

Example:
Station name in the list = "SAP_beas"
Station name from System = SAP_Beas"

In the past the license was not working
New: now it is working properly



 
 
Beas\Administration\Setup
2019-01-29
12882
2
Windows Time Format; Setting up a custom format will cause errors in some beas windows
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Administration\Setup

Past:
Translation - Country setup available, but not working in actual windows versions

New: 
We deleted this button. Please use windows standard regional settings

window: system_spr_browse

Translation -> edit

Past: We had lots of tabs without a function
New:  Only "Language" and "Translation" are available
Completely with new english documentation


window: system_spr_edit 

Past:
if you had a ' letter in regional settings - times, you received an error message in different windows
"Error create object in wf_design_cols() for object releasedate. Error: Line 1 Column 199: incorrect syntax."

New:
Fixed. beas ignores the setting. For more information on compatibility to window regional settings see our documentation.

 

Beas\Administration\System Initialization
2019-01-29
10421
2
Information from the Data Check Message screen
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Administration\System Initialization

beas message system


Past: Button "Information" was available. If you clicked on it, beas opened an editor but did not save your entry.

New:
Idea of Information button: It displays additional information, if available. Idea is not to save own entries.

The Information button is now only visible if additional information exist. If you click on the button, you see only a message box with this additional information.

system_event_browse.psr
Beas\Administration\Utilities
2019-01-29
12006
2
GDPR - Archive Data Function
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Administration\Utilities

For GDPR rules you need the possibility to delete not used Data, especially human related data


for this we have our archive function

Database Test > Archive Data



New in this window:
You can delete Personnel related information like:
Absence
Attendance
Monthly Quota
Special shift

if you activate this option, you cannot choose "external target server", because we only have the delete function.

Note:
Please create a database backup before you execute any archive data function.

Using:
define the date in field "Only Date" 
beas will delete all entries older than this defined date. The chosen date must be older than 500 days.
2019-01-29
9634
2
New beasService
beas 9.3-001-003-000 / beas 9.3H-001-003-000
Beas\Administration\Utilities

New version of BeasServices is delivered.


This new version has been completely redesigned
Old beas Service was based on an external application named "pbniserv". This was not stable 
Now this application is removed and we implement our own "beasService.exe" program, which acts as a protective shield for the beas application

What problems have been solved:
- Problems with the SAP DI API produced crashes of the beas service
- Crystal Report could stop the beas service (e.g. unauthorized parameter query)
- If several MRP calculations were started one after the other, the memory was no longer released correctly and the system became unstable.
- Uncleanly programmed customization often led to crashes

The new shield monitors the beas application and restarts it if it crashes or stops responding.

Advantages of new BeasService:

* Much more stable than previous program, 
* No Crashes
* Based on Windows service technology (Standard)
* Easy and fast to install and to unistall

You can define properties of the service into same window:

Window: system_server_admin.psr

beasService.exe is a wrapper to execute beas in background, this application handles any exception thrown by beas. With this functionality beasService is always UP and RUNNING.
beasService is installed into system using windows tool "InstallUtil.exe" To install a service, you need admin rights. To handle this, "beas client Agent" does this operation; this is the reason why this application must be started to install the service.
 
Update information:
By Default, old installed services will not work by default with new BeasService.
If you want to replace old pbniserv with new beasService, you have 2 options:

Option 1: Uninstall old service and register new old, 
System will automatically install new logic.

Option 2: You can modify registry for you current service and then you can replace link to old
pbniserv program by new beasService.exe program. Both programs are located into same directory.
You have to modify entry "ImagePath" in the following way:







2019-01-29
13997
2
Framework/Beas-Editor Window: Problem/error in Object List
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\beas Customizing

in beas 9.3 PL 1 we've a new source editor


Problem:
You can't see values from an object from type "ue_datastorevalues". In old editor it was possible

New
if you exapand an ue_datastorevalues, you can see all fields and values from current line



Example
1. Open the Editor 
2. insert follow script
declare=lds=ue_datastorevalues
lds=select * from "BEAS_ME"
3. execute
4. expand area "Objects" - "lds"
 
2019-09-20
13836
2
New properties in workorder object
beas 9.3H-001-004-000 / beas 9.3-001-004-000
Beas\Beas Script

in work order object ue_api_wo we've follow new methodes and properties


declare=wo=ue_api_wo

Header Level

UDF's on header line

wo=udf5 
...
wo=udf15

Line Level 

All UDF's 
wo=line=udf5=...
...
wo=line=udf15=...

set quantity now in use unit

wo=line=quantity_ve
(related to field BEAS_FTPOS.MENGE_VERBRAUCH)
if you set the quantity, beas calculate automatically the quantity per stock unit. 

wo=setrow=x
define the internal row, which you want to change

wo=gotobelpos_id=x
go to the defined position (BEAS_FTPOS.BELPOS_ID) in the internal datastore
wo=line=gotobelpos_id=20
return values:
ret_code=-1 -> not found, 1=found
ret_linenum=internal linenum inside datastore
if beas find the entry in datastore, it set this as current line for all additional activities.

destroy=wo
declare=wo=ue_api_wo
// load workorder Nr 1240
wo=loadworkorder=1240
wo=line=gotobelpos_id=20
if <wo.ret_code> = 1 then
  messagebox=<wo.ret_linenum>
end if


wo=line=gotonewline
if current line is a new line, beas do nothing
if current not a new line, beas add a new line

wo=loadworkorder=1240
wo=line=gotonewline
wo=line=itemcode=A001
wo=line=quantity=10


Properties
<wo.line.rowcount>  return count of loaded lines
<wo.line.currentrow>  return the current row inside the loaded datastore
2019-01-29
12200
2
beas Script, global variable for StationName when using RDP
beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\Beas Script > Zendesk id: 57369

in beas script you have the following variable to return the name of computer


<system.computername>
return name of local computer
this function was available in beas 9.3, but not described

<system.stationname>
return the name of current session
local session: the computer name <system.computername>
rdp connection: the name of local computer (clientname)
rdp connection: if clientname not available - the user name

NEW: <system.stationnameex>
local session: the computer name
rdp connection: the name of local computer, if available. 
if not, beas returns the computer name


 
2018-09-20
8185
2
10803 - Preclose and Postclose event for beas_FTAPL (as beas_fthaupt and ftpos, we got the
beas 9.3-001-008-000 / beas 9.3H-001-008-000
Beas\Beas Script

New "Preclose" event for BOMs and Routings, when a bill of material or an operation is closed now system fire a new event "preclose". This event is only fired if previous status is open.



Window: fert_ftstlpos_edit.psr 

New option "Re-open", now BOMS and routing when status is closed you have option to "Re-open"

 
Additionally you can close and reopen a BOM or a position via beasscript. 

object=ue_api_wo=bom_close=20180067=10=20
object=ue_api_wo=bom_reopen=20180067=10=20
object=ue_api_wo=routing_close=20180067=10=20
object=ue_api_wo=routing_reopen=20180067=10=20


2018-11-21
12916
2
Rounding quantity production entry with external operations and conversion factor
beas 9.3H-001-010-000 / beas 9.3-001-013-000 / beas 9.3H-001-013-000
Beas\beas Standard

Now beas is managing rounding for external operation process.


In Unit of measure definiton you can now define the rounding and num decimals for this external operation process.



When you define a conversion factor with lot of decimals for an external operation, usually the result is also a decimal with several decimals. Now beas allows to round the result:




When you try to create a purchase order, the system applies the conversion factor, and then this system does the rounding process. We added a tooltip over field quantity to explain how beas is calculating the result.


 

2019-01-29
10906
2
MRP Scenario, Filtering criteria is limited to 255 characters
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\MRP\MRP Wizzard > Zendesk id: 55586
In MRP scenario the field size is limited to 255 characters in the marked fields

New:
New size is 2048 chars

2019-01-29
14024
2
MRP: calculate inflow and outflow from external table
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\MRP\MRP Wizzard > Zendesk id: 54280
Past:

it was possible to read inflow, outflow requests from an external table.
Definition was in the project file mrp.src.
But the usability was not good and not compatible with the current beas version.

New:
1. You can define this per MRP Scenario
2. You can define many more properties, for example: Warehouse, Item Version, Project, UDF's, Color, Bitmaps and lot of more
3. Breakdown is working
4. calculation of requirement date is working

You can define the sql statement in 
MRP Wizzard - Detail - Calculation - Own Table


 
For more information on this functionality see  Documentation

Attention:
we close the support for the SQL Definition in MRP.SRC. 
If you used it, you must define this SQL Statement in the MRP Wizard.
2019-01-29
14061
2
MRP Sales order filter
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\MRP\MRP Wizzard

MRP - Sales order Filter


PAST:
It was possible to define additional Filter for reading Sales Order:

mrp.src

function start

setvar=mrp_auftragfreigabe=select case when

 "RDR1"."U_myfield"='yes' then 1 else 0 end from "RDR1"

 where "DocEntry=[e_docentry] and "LineNum"=[e_linenum]

end

But this was not working stable and reduced the performance, if you'd many sales order lines


NEW:
Now we changed the usability
1. You can define this per MRP Scenario
2. It's faster as old solution
3. The usability is simple

What can you do with this function
- create MRP scenario only for one customer, one project or sales order specification (related to an UDF field)

Definition: MRP Wizzard - Detail - Sales - Sales Order Filter - Filter Sales Order SQL

If you click on the SQL Icon, you can define the filter in simple way

On left side you see the available tables, which you can use to define the filter
If you click on Execute, you can check the result directly

 
More Information and Examples about this Filter see our documentation

Attention:
we don't close the support of old solution next time
But please delete the entry in MRP.SRC and use the new functionality.
2019-01-29
13977
2
APS Planing: Create SQL Statements in simple way
beas 9.3-001-007-000 / beas 9.3H-001-007-000
Beas\Production\APS

In APS Planing window it's now simple to create SQL Filter and SQL Sort


The SQL Icon help you to create the sql statements
fert_xgantt_planing_edit
 
If you click on it, you can define the statement in the SQL Editor in simple way

You see only the available fields and with Double Click you can chose the fields.

 
2019-01-29
7916
2
Create APS View - make it simple
beas 9.3-001-004-000 / beas 9.3H-001-004-000
Beas\Production\APS
The generation of APS scenarios was improved.

In the past when you created a new scenario you always had to begin from scratch, e.g. you had to insert all parameters new.
Now you can either copy an existing scenario (via right-click menu) or create a new one  (Button "new schedule" or via right-click menu)
that is always derived from the default scenario.

 fert_xgantt_planing_browse.psr

Inside a scenario you now also have the possibility to generate new views based on default view, i.e. when you
create a new view, then it is copied from the default view.

 
fert_xgantt_view_browse.psr
Beas\Production\Configurator
2018-11-21
13274
2
License, Product Configurator (Single Sales User)
beas 9.3-001-005-000 / beas 9.3H-001-008-000
Beas\Production\Configurator > Zendesk id: 60950
Past:
The License configuration for beas product configurator and beas product configurator license were wrong

Definition:



Product Configurator
Product attributes, rules, formulas, tables; Assigned to items, BOMs, routings; Free definable variant/configuration structure single- or mutli-level based; Usable in SAP B1 quotation or sales orders to configure items; Integrated generation of calculation and/or work order data
This license is linked to beas basic License!


Product Configurator , limited for SAP B1 Quote and Sales Order
You can use this license without beas basic license.
Product attributes, rules, formulas, tables; Assigned to items, BOMs, routings; Free definable variant/configuration structure single- or mutli-level based; Usable in SAP B1 quotation or sales orders to configure items; Integrated generation of calculation and/or work order data


Past in license window:
Product configurator: you can choose the user. 
Product configurator, limited for SAP B1 Quote and Sales Order: it was not possible to choose user
Result: It was not possible to work in the correct way. But beas did not check the license inside sales order and sales quotation. All functions were available.

New in license window:
Product configurator: You cannot choose any user, because it is linked with basic license
Product configurator, limited for SAP B1 Quote and Sales Order: You can choose the user
Now you can define the license in correct way.
system_lic_useredit.psr
 
Past in Sales Order and Sales Quotation:
Every right click function was available. You don't need any license.
But if you tried to open a sub function you get the message: no license

New in Sales Order and Sales Quotation:
You can see every beas right click menu point only, if you have the license to use it.


 
If you do not have a beas basic license, only a "Product configurator, limited for SAP B1 Quote and Sales Order", you cannot open a work order
in this case you can see the menu point: Work Order: Display ... this window displays this work order position with routing plan and bill of materials
It is the same if you open Item History and make a double-click on a work order request.
Beas\Production\External production
2019-01-29
10756
2
Terminal desktop - Enable external operation process on desktop terminal
beas 9.3H-001-003-000 / beas 9.3-001-003-000
Beas\Production\External production

Enable external operation process on desktop terminal.

The following new apps for Desktop Solution are available:
A-External: Issue provision parts => opennewwindow=fert_external_delivery_browse.psr
B-External: Goods receipt => opennewwindow=fert_external_openorder_browse.psr
C-External: Provisions => opennewwindow=fert_external_owingspl_browse.psr



 


 

Attention: These apps are only available for Desktop solution, not for WEB Solution.

2019-01-29
10929
2
External production - enable a warehouse for external service receipt
beas 9.3-001-002-000 / beas 9.3H-001-008-000
Beas\Production\External production
Past:
When a purchase order was created related to an external operation, the selected warehouse to transfer the provisions (EXT at this Image) is the warehouse also used at the purchase order.
Consequently, the shipping address is that related to the warehouse in the purchase order.
 
 
General Overview
A new field will be created to define a different warehouse for the purchase order. This allows to define a shipping address, as well, for the incoming goods of the purchase order.
The field will be created at the next screens taking the default value from the primary warehouse of the external service item: 

  
Functions description
We have a new field "Purchase order on Warehouse" in Operation catalog, Routing position, Work order Routing position and Pre-calculation Routing position
arbeitsgangkatalog.htm, artikel_arbplanpos_edit, fert_arbplanpos_edit, pk_arbeitsgang_edit


The default value comes from the primary warehouse of the external service Item; when an item is selected
The system updates the incoming external warehouse to the default value.
The field dropdown shows the list of the warehouses available for the external service item.

 
The incoming external warehouse (PO whs) is a mandatory field
if it is empty (compatibility), the default value will be the primary warehouse of the External service

The address field is the address related to the incoming external warehouse (PO whs) and not the target warehouse.
beas considers multiple selection at the collective work order if multiple lines were defined, the system creates the purchase order grouping by the same supplier and same incoming external warehouse (PO whs)
When the purchase order or a draft is created, the incoming external warehouse (PO whs) is the warehouse at the purchase order line and the shipping address will still be the address field. 

 
 
2019-01-29
8188
2
10831 - External: Add Information about external process at Purchase order
beas 9.3-001-002-000
Beas\Production\External production
New options in the right click popup for purchase orders.
If the material is linked to an external operation, the right-click popup displays two new entries:
- (1) External process details: [material] (wo/position/routing)
- (2) External process details

(1) Open a new window with information for all External Services
(2) Open a new window with information for the selected line only




Purchase Order Item Information


 
 
This new window opens after you press any of the popup entries with the following information:

  • Work order number
  • Position number
  • Operation number
  • Itemcode producing
  • Item name
  • Quantity producing
  • Operation description
  • Operation resource
  • Work order delivey date
  • Sales order (if the work order position come from a sales order)
  • Customer
  • Project



 
Beas\Production\Factory data capture\Production Time
2018-11-21
8672
2
Production time Administration - Search function
beas 9.3-001-009-000 / beas 9.3H-001-009-000
Beas\Production\Factory data capture\Production Time
Production Time Administration

Past: There were buttons Forward/Backward 
Now: It is possible to define a filter for Date Area, Personnel, Resource, Work order, Item code or Project


 fert_arbzeit_browse_alle.psr
Beas\Production\Factory data capture\Terminal
2018-11-21
7196
2
(9823) Terminal inside beas: Only the current user can use it
beas 9.3-001-010-000 / beas 9.3H-001-010-000 / beas 9.3-001-011-000 / beas 9.3H-001-011-000
Beas\Production\Factory data capture\Terminal

In the past when you opened the terminal-window inside beas it was opened  as a window inside beas.
This caused some problems because the license and settings could be different according to the user who logged in inside the terminal window.
So beas could not decide correctly which functionality was available and so on.
Now a standalone terminal is opened to avoid these problems.



menu_terminal.psr


Beas\Production\Workorder
2019-01-29
10420
2
Usability in window resource - interruption
beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\Production\Workorder
Resource - Tab "Interruption"

New:
we renamed field "ID" to "Interruption Reason ID"

 

Same in the edit form


Past:
You can edit all information without any access rule
New:
You need access to "Resource"

Past:
F1 was not working
New:
F1 is working
2019-01-29
14365
2
Add Reservation -> Performance
beas 9.3-001-006-000 / beas 9.3H-001-006-000
Beas\Production\Workorder
Work order - Reservation
Add Reservation

Past:
Performance was not always satisfactory

New
The select * command replaced with better sql statement
Performance is better

HANA: 
SQL Update command not optimal. -> Fixed.

reservation_set_master
 
2019-01-29
13903
2
Work order bill of materials - activity log
beas 9.3-001-004-000 / beas 9.3H-001-004-000
Beas\Production\Workorder

Work order - Edit work order position

Tab Bill Of Material

Past:
It was not possible to get an overview about all changes in the bill of materials
in activity log you could only see activity log from current bill of materials line

New:
bill of materials list - activity log
You see every activity done on bill of materials

window fert_ftstlpos_browse.psr

bill of materials - edit window
You see only the activtiy log from current work order bill of material position (no changes)


More fields 
work order - bill of materials (List)

Past:
No overview about internal position number and sorting
New:
You can activate the columns Sorting and PosId
The field "Sorting" is changeable

 
2018-11-26
10861
2
Material Scrap Factor (%) for alternative resources
beas 9.3-001-008-000 / beas 9.3H-001-008-000 / beas 9.3H-001-013-000 / beas 9.3H-001-013-000
Beas\Production\Workorder

Material Scrap Factor (%) for alternative resources:


At the operation, users can define the Scrap of Material % if the general parameter was activated for it.

Field from the master data:



Field from the work order: (disable to modify at the WO):


 
When the general parameter is activated, the fields are displayed at the extended TAB of the operation master data or work order. The parameter is ”Scrap related to a certain operation”.


 
We Added a new field into Alternative master Data definition:



Window: artikel_arbplanpos_edit_alternativ_edit.psr

New logic is also added to precalculation window:



Window: pk_struktur.psr
Window: pk_arbplanpos_alternativ.psr

·         New field is only visible if the general parameter is activated (scrap related to a certain operation).

·         The new field will be available from the Alternative on the operation master data and from the work order screens.




Window: fert_arbplanpos_edit_alternativ_edit.psr


       Important: At the Work order, the scrap factor appears protected if we already have an alternative resource, as the scrap factor appears also for the main resource.  In case the user adds a new alternative at the work order, this field appears and enables to add the value.


 





2018-11-21
7855
2
Post Calculation with SQL Filter
beas 9.3H-001-009-000 / beas 9.3-001-009-000 / beas 9.3-001-012-000 / beas 9.3H-001-013-000
Beas\Production\Workorder
Post calculation mask has been changed:

1. Column "Project", ItemGroup, Material Group and Production 
Past: it was not possible to choose more than 1 entry
New: You can choose more entries, for example 4 different projects

2. Closed period
Past: it was only possible to choose one fix time period
New: Now you can define: today, last 1, 7, 14 or 30 days or fix time period

3. Filter SQL
You can define an own SQL Filter
This field is new.
Example: only work orders which have key word 'red' in udf1 field
You can define this filter with: and "BEAS_FTPOS"."UDF1"='red'

4. No result
Past: If beas does not find an entry, it displays only an "ok" message
New: You will see the message "no entry found"

5. If the definition is broken (only in error case):
Past: beas displayed only an ok message
Now: beas displays a correct error message "Definition is broken - create a new entry"
Additionally, a self-repair program is set up inside, and it attempts to repair the entry automatically.


postcalc_header_edit.psr

Old settings are running. We have 100% compatibility.
 
2019-01-29
10859
2
QC - Add SAP activities
beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\Quality Control
Added to the QC Order Edit window a new button to add "SAP Activities" linked with the current qc order

After press the "Acitivities" button, a new window is open with the list of SAP Activities linked with the qc order.
You can Edit or Create new Activities pressing the "Edit"/"New" buttons if you are inside SAP only.


qs_qsfthaupt_edit.psr
 


qc_activity_browse.psr

 
2018-11-21
7633
2
Available-to-promise / Capable-to-promise
beas 9.3-001-010-000 / beas 9.3H-001-013-000
Beas\Sales

The Capable-to-promise function is available now


SAP Business One - Sales order or Quotation
Right-click on a line with an Assembly

NEW:
Capable-to-promise Function

This function calculates the lead time for an assembly

Attention: This is a part of the APS Solution and it is only available if the customer has an APS License.
Beas\Sales\Precalculation
2019-01-29
9737
2
"One Step" Option flag in pre-calculation documents
beas 9.3-001-006-000 / beas 9.3H-001-006-000
Beas\Sales\Precalculation > Zendesk id: 52851

If you create a new calculation from Sales Order or from Pre-Calculation list


NEW:
the option "ONE LEVEL" is available

 This has the same functionality as Item - new calculation or batch calculation - "ONE LEVEL"

If this option is active, the calculation calculates only the first level of the item structure

Example:

Valuation = Price List 1
Item A have sub Item B with Material C.

Sub Item B : 9€
Material C : 10 €

Option "ONE LEVEL" is disabled
beas calculate

You see in Calculation
 |_ B
     |_ C

A = Material price C = 10 €

Option "ONE LEVEL" is enabled

You see only Assembly B, but not Material position C
Calculation:

A = Price from B = 9 €

Limitations
- you see only the total price in the calculation view for assemblies
- if you insert a material in an assembly: the calculation ignore this. It is a one-level calculation
- it is not possible to change this new flag in an existing pre-calculation
2019-01-29
14016
2
Compatibiltiy with MSSQL 2017
beas 9.3-001-005-000
Beas\System and Other

SAP 9.3 Pl 05 is compatible with MS SQL 2017


New
beas 9.3 PL 1 is compatible with MS SQL 2017 too
Beas\Usability\beas usability extension (B1UP)
2019-09-20
13630
2
Beas usability extension - Buttons
beas 9.3H-001-003-000 / beas 9.3-001-003-000
Beas\Usability\beas usability extension (B1UP)

Edit function buttons


changed 
"Collapse / expand" to
"Collapse / Expand"

window: sys_button_edit
 


2018-11-21
14968
2
Beas Usability Extension- Item placement tool - right-click menu
beas 9.3-001-009-000 / beas 9.3H-001-009-000
Beas\Usability\beas usability extension (B1UP)
Past: Menu entry "Edit Item Placement Tool" was not available if you clicked from outside the dw_1...dw_7 area
Now: You can always see this menu point.


 
 
Beas\Warehouse Management\Item Master Data
2018-10-09
9693
2
Batch changes not working for Separate BOM (Item version control)
beas 9.3-001-009-000 / beas 9.3H-001-009-000
Beas\Warehouse Management\Item Master Data > Zendesk id: 44842
Batch Changes now items with "Separate Bill of materials"
One item definition works with "Separate bill of material" when you define this property into an item since that moment you can generate different versions for this item and additionally you can define different BOMs for each version.


 
When you open window Bill of materials: the Batch changes. This window manages normal items and now additionally every separate BOM is also managed.


 
Window: artikel_stlpos_batch.psr

Now in the substitute tab a new column is added to show related version. If no info is inside the version column, it means that this is a standard BOM.
IMPORTANT: if a version has the same definition as standard item, then system will not duplicate information for each version - it will only show definition for standard BOM.

Additionally, improvements are also implemented into "Material: Batch changes"


 
Fixed
2019-07-19
15137
1
object=ue_reservation=planned=new=receiptwo return the same "pdocentry" always
beas 9.3H-001-010-000 / beas 9.3H-000-031-000 / beas 9.3-000-031-000 / beas 9.3-001-010-000
Beas
If you execute this in beas script you shouldn't get the same "pdocentry" always.
object=ue_reservation=planned=new=receiptwo
message=<pdocentry>
2019-01-29
13469
1
Resource window: Not possible to display dispatches
beas 9.3-001-002-000 / beas 9.3H-001-002-000 / beas 9.3-000-029-000 / beas 9.3H-000-029-000
Beas
Resource - Tab "all resources"
click "Dispatches"

Past: (only beas 9.3):
you get the error message:
(**)Error: don't find `beas_aplatz_aplatz_id` in datawindow program\stamm_arbplatz_browse.psr (command: beas_aplatz_aplatz_id:1.value, function ue_convert.of_item_beas

Reason:  Overloading from global function between the tabs wasnot working. 

Now: Fixed. 
Now the button is working properly.


stamm_arbplatz_browse.psr
2019-01-29
13012
1
Initial Stock: Import / Booking Button is not working
beas 9.3-001-000-000 / beas 9.3H-001-000-000 / beas 9.3-000-027-000 / beas 9.3H-000-027-000
Beas

Previous: In 9.3 version button "Booking" is doing nothing.


Now: Bug is fixed.


 Window: mw_inventory_header_stocktaking_browse.psr
Source: mw_inventory_header_stocktaking_browse.src



2019-01-29
13453
1
Work Order-Structure View (graphical) does not work properly
beas 9.3-001-003-000 / beas 9.3H-001-003-000
Beas > Zendesk id: 61419
Print Macro Definition:

Button "Test" executed the macro in this window
Problem: If you need information from current window, beas cannot find it in the macro definition window.

Example: Work order structure report (Work order structure window) not working, if you test this with the test button

New:
if you click on "Test" beas starts the macro from preview window (in this case work order structure window) and in this way it works.
report_makro_struktur
Beas\Administration\Data Import and Export
2019-01-29
12780
1
No possibility to Import stock of version-controlled items
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Administration\Data Import and Export > Zendesk id: 59552

Now Import process allows to import "version" field.



Window: mw_inventory_header_stocktaking_browse.psr

You can find detailed information on available fields and order into our documentation:


2019-01-29
13010
1
Data Integration Hub, BEAS_WKZ, Importing of field 'CardCode' not possible
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Administration\Data Import and Export > Zendesk id: 60722

Integration Hub - import Tools


Past:
It was not possible to import Supplier. beas display: No entry found in OCDR.Cardcode. beas checked wrong table. Correct table is "OCRD".

Now: Fixed.


window: importkopf_edit

window: import_defresultpreview
 
 
Workaround: Ask our support for replacing the file columninfo.psr
2019-01-29
13035
1
Integration Hub - search field not working
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Administration\Data Import and Export
Data Integration hub - overview

Past: the search field was not working

New: fixed.
beas checks the following fields : Type, Id and Description


window: importkopf_browse
 

2019-01-29
14116
1
Error (**)of_api_bom: Error write bom Data Integration Hub Bill of Materials Positions
beas 9.3-001-005-000 / beas 9.3H-001-005-000 / beas 9.3-000-030-000 / beas 9.3H-000-030-000
Beas\Administration\Data Import and Export > Zendesk id: 62962
Past: Using Data Integration Hub to import BOM (update existing bill of material positions) sometimes the system displayed the following error:

(sqlerr2627)Key fields Itemcode,Pos Id in line 1 need to be unambiguous. Values stored there are already in use.

Now: Bug fixed.

The problem occurred when the system tried to update the BOM list.

Workaround: You can delete existing BOM first, and then do the import.
2019-01-29
13058
1
Data Integration Hub, OITM, Field 'SalUnitMsr' is missing in Source/Target Linking
beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\Administration\Data Import and Export > Zendesk id: 60849
beas Integration hub

now it is possible to import the additional, following fields in item master data:

 
2019-01-29
11445
1
Data Integration Hub, Import 'Date of Hire'/'Date of Birth' into Personnel Master Data does not work for dates before 1991
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Administration\Data Import and Export > Zendesk id: 57110
Data Integration Hub
Import Personnel Master Data
Dates not working before 1991



Past: Import Preview - Result: Date field is empty

New:
beas imports all date information newer than 1991

 
Window: import_defresultpreview,importkopf_edit

Beas\Administration\License
2019-01-29
14286
1
terminal - maintenance order - license check
beas 9.3-001-006-000 / beas 9.3H-001-010-000
Beas\Administration\License

In Terminal the app "Maintenance order" is available

This app is a part of the license

Production Data Collection, Start, Interrupt, Completion, Finished Goods, Scrap


This is the same function as in SAP -> Service -> Maintenance order
But functionality is limited
- you cannot create new orders or delete orders
- you do not have access to work order structure view, you cannot edit bom details or routing details
- you do not have access to activity log or closed maintenance orders
- you do not have access to every SAP function, e.g. SAP Activity or Service Call
- You cannot change / edit documents, and only view is available

But all functions which you need for most workflows are available
- Create workorder, if not existing
- Time receipts in all variants
- Post out Material
- All interruption functions
- Status Maintenance order, close Order
and a lot more
maintenance_plan_dateedit.psr
 
2018-11-21
14179
1
License type in license window
beas 9.3-001-008-000 / beas 9.3H-001-008-000
Beas\Administration\License > Zendesk id: 63136
Past:
In different situations beas switched into DEMO Mode, for example open invoice existing, user working with on-demand license.

NEW:
Now the "License Type" is available. 
In field "License Type" you can see, which License Type is used, e.g."MAINTENANCE","ON DEMAND", "DEMO" etc.

system_lic_useredit.psr
 
Beas\Administration\Makros and Crystal Report
2019-09-20
14525
1
Boyum.Crystalviewer wrong behavior with empty parameters
beas 9.3-001-007-000 / beas 9.3-000-031-000 / beas 9.3H-000-031-000 / beas 9.3H-001-007-000
Beas\Administration\Makros and Crystal Report

Before: When new crystal reports viewer was active and we sent an "Empty" value to a parameter in any report, the system opened a window for the missing parameter. 



New: Now parameter window is not opened when a paremeter has an empty value.
2019-01-29
13075
1
Printing of beas-CR-reports not possible
beas 9.3-001-002-000 / beas 9.3H-001-002-000
Beas\Administration\Makros and Crystal Report
Previous: In beas version 9.3 in some installation reports are not printed correctly. 
This problem was reproducible only in HANA versions.

Now: A new version of Boyum.CrystalViewer is delivered and the bug is fixed.

There is one environment where problem is not solved: if you have SAP Business One x64 installed without a x32 bits installation then required libraries are different. To solve this issue, we can provide x64 libraries to do a workaround for this problem.

2019-01-29
14219
1
Systemerror 40 Mismatched ANY datatypes in expression: long, string at line 89 in function of_makro_print
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Administration\Makros and Crystal Report

Macro Print


Past:
If you defined an Orinetation in the printer setting, and you used the new Crystal viewer, you received the following error message

Systemerror 40 Mismatched ANY datatypes in expression: long, string at line 89 in function of_makro_print of object ue_reportobject. 

Now: Fixed.


 
 
2019-01-29
14221
1
Systemerror 2 Null object reference at line 48 in function of_cr_openreport of object ue_reportobject
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Administration\Makros and Crystal Report
Before: Sometimes system threw an exception when user tried to open a report. Error fired by system is:

Systemerror 2 Null object reference at line 48 in function of_cr_openreport of object ue_reportobject. Window:ue_reportobject Object:  ue_reportobject  Event:  of_cr_openreport Line 48 Windowtitle: Time Receipts Script-Function:    ..ct\workordermanagement.src:timerecordingend():timerecordingend 


Now: We added a validation to avoid this situation.
Beas\Administration\System Initialization
2019-07-08
14343
1
decimal-multiplication in beas-script
beas 9.3-001-006-000 / beas 9.3H-001-006-000
Beas\Administration\System Initialization
In beas script there is the possibility to declare variables of type decimal.

Script example:

dec lc_test
lc_test=3.5 * 3.5
message=result: <lc_test>


In this example the result must be 12.25.
Unfortunately in some virtual environments the decimal place was cut off
and a wrong result (9) was calculated.

Now beas checks if a decimal calculation works correct on the system.
If there are problems the expression is evaluated through an SQL statement.
In this case the expressions are limited to the ability of the SQL-Server.
2019-01-29
11086
1
POS_ID with different datatypes
beas 9.3-001-002-000 / beas 9.3H-001-003-000
Beas\Administration\System Initialization

The data type for fields "buchnr_id", "belnr_id", "belpos_id", "pos_id" in the table "BEAS_ARBZEIT" is now "LONG"



2018-10-04
15215
1
DI-API and UI-API connection troubles
beas 9.3-001-011-000 / beas 9.3H-001-011-000
Beas\Administration\System Initialization

UI-API and DI-API connection has been revised to improve error handling and connection methods.


Now in beas you can decide how you are going to connect to DI-API



1.- GetDICompany(Shared connection) --> This is connection method since SAP 2007 version. This method connect fast to SAP and additionally share memory between addons
2.- Context Cookie (Non shared connection) --> This is old connection method from SAP, it is little bit slow on connections and also do not share memory with other addons but it is little bit faster with objects operations.

Additionally the error message when UI-API cannot be reached was improved. No system will show following error message:

beas can't connect to SAP Business one.

Error Description: SAP Description of the problem

1.- Run SAP as an Administrator
2.- Check your SAP Business One License.
3.- beas addon is only runnning on 64 bits environments under this combination:
   a.- SAP Business One 64 Bits installed
   b.- SAP DI-API 64 Bit installed
   c.- SAP DI-API 32 Bit installed
   d.- SAP Business One 32 Bits NOT INSTALLED.

Details: Ole Exception description

Beas\Administration\Utilities
2019-01-29
12913
1
Debugger: edit SQL
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Administration\Utilities

In debug window you can see every executed sql command.

If you make a double-click on a sql line, beas opens the sql editor with this sql command.

Past:
Complex sql statements with tabs were not displayed completely

New
All sql commands are completely displayed in SQL Editor

Example
"Sales Order to Production Order"
Debug window Double click on sql line
SELECT "BEAS_FTHAUPT","....

Now you can see the complete sql statement.
(Attention: question marks inside this command. You cannot execute it)

 
2018-11-21
14353
1
Title/naming issue with "beas manage server"
beas 9.3-001-007-000 / beas 9.3H-001-007-000
Beas\Administration\Utilities

In integrated and extended menu the title of Beas Manage Server was wrong


Past: It had different names in different places, for example:
"Manage Server" or "Server" or "Server management"

New
Now we have the name"Beas Manage Server" in all places


 
2018-09-24
13433
1
beas common service: new dashboard and C# Converter
beas 9.3-001-007-000 / beas 9.3H-001-007-000
Beas\Administration\Utilities > Zendesk id: 61070
in beas manage server new incons inside



 open the documentation, in which the service is described
 open the administration tool for this service. 
common interface: the beas common dashboard
planned activities: window, in which you can define the planned activities (same as tab "planned activities")
web application server: open the application group administration window

 open the beas common test window

New: the beas common dashboard

(click on  in beas manage server window)

In this window you can see the functionality of the beas common service
additional you see the count of entries in the income stack (left side) and output stack (right side)

 
 open the view for input stack (Table BEAS_COMMON_INPUT) ans outpot stack (table BEAS_COMMON_OUTPUT)
 open the beas common test window

New:
You can define directly the count of archive entry for Input and output stack (field max. records)
The internal cleaning program delete only entries, which are marked as "closed" (BEAS_COMMON_OUTPUT.Closed=1)
Important: If your application is working with the BEAS_COMMON_OUTPUT, is must mark the entry with Closed=1

New: beas common test window
from beas manage server or beas common dashbaord you can open this with click on  

With this window you can
- test the common interface
- create scripts and convert this to C# SQL Statement



New is the integrated Assistant. This help you to generate the script for transaction, which you need.

Example: Purchase incoming goods
1. Choose command "SAP Transaction"
2. Choose operation "Purchase Incoming goods"
3. Click on ok 

 
now you can see the script in the test window


Click on the copy icon
beas copy this script in the clipboard as C# SQL Command
You can insert this in your application. If this is not C#, it's simple to change this

Example of created C# Script:


 
At end you must replace the place holder
example /* DocEntry from base document */ with the correct number or string variable
Don't delete the & marks. This are a part of beas script
 
Documentation

We changed the place of documentation
Past: beas script documentation
Now: Main documentation (F1)
2019-01-29
13931
1
beas Script, ue_api_wo=set=freeze not working correctly
beas 9.3-001-004-000 / beas 9.3H-001-004-000
Beas\beas Customizing > Zendesk id: 62523
Command 

object=ue_api_wo=set=fix=<documentnumber>=<positionnumbe>=<on/off> 

not working

New: Fixed

With this setting you can change the "start fix" setting in the routing position
2019-01-29
12180
1
Silexer - find window not closing
beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\beas Customizing

tools - extensions for clients -> open customizing window


open search form (Ctrl+ F) or the marked icons

 
now you can see the search window

 
Past:
if you closed the editor, beas did not close the search window. If you clicked on "Find Next", you received an error messsage

New:
if you close the editor, beas closes the search window, as well.

This is related to every window in which you can see this editor (silexer)
2019-01-29
10908
1
BeasScript: ue_reservation object does not create WIP journal entries
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\beas Customizing
Past: Beasscript object ue_reservation generated goods receipt documents with a wrong price and also journal information were not ok.

Now: Journal entry information generated by ue_reservation object is same information generated by beas windows.

Example:


 
2019-01-29
14235
1
Assistant - new time receipt creates wrong syntax
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\beas Customizing

beas script assistant

(only available together with beas usability package)
See https://youtu.be/mNujRw9fSDo

With the assistant you can geneate script fragments, for example create work order time



Past: the generated script was not correct
New: Fixed. The generated script is now correct for using


2018-11-21
14333
1
Customization code not visible in beas standalone
beas 9.3-001-009-000 / beas 9.3H-001-009-000
Beas\beas Customizing > Zendesk id: 63308
Past:
Sometimes when users tried to open customization code, window was empty.

Problem was related to the encoding of the customization file.

Now: The system is able to open customization information without an issue.


 
2018-09-20
14292
1
windowevent click button - executed 2 times
beas 9.3-001-007-000 / beas 9.3H-001-007-000
Beas\beas Customizing

Before: WindowEvent  Click was fired twice



Now: bug fixed, for compatibility purposes a new event was created and this event was fired twice.

Window: fert_arbzeit_erfassen.psr
Beas\Financials\Business Performance
2019-01-29
12888
1
Business Performance: Statement Cycles doesn't refresh after add a new item
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Financials\Business Performance
Business Performance - Master Data - Statement cycles

Past:
synchronisation between the list- and edit view was not working
example: if you inserted a new statement cycle and closed the edit window, you couldn't see this in the list of statemtent cycles

New: 
Fixed



 

Past: 
The field "Start fiscal year" was not mandatory. If this field was empty, the error message was not clear
New:
Now the field is a mandatory field

window: bab_abrid_edit.psr
2019-01-29
12903
1
Business Performance: Settlement structure > SQL error after click on tab "Columns"
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Financials\Business Performance

This error is only reproducable when debug log is opened


Previous: we have the following error:
(<empty>)Error DROPDOWN field: Values (art)SQLSTATE = 37000
[Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near the keyword ' 
DataWindow: program\bab_struktur_list_def_col.psr
SQL Syntax:
Disable test: Insert follow text in sql statement: /*qcDontCheck*/

Now: Bug fixed
 
window: bab_struktur_list_def_col.psr


2018-11-21
14752
1
Business Performance/Absorption Cost: Stock Revaluation
beas 9.3-001
Beas\Financials\Business Performance > Zendesk id: 60200
Past:
In Business Performance/Absorption Cost, the Result-Windows for "Stock Revaluation" and "Stock Revaluation (Revert)" would not filter the actual Month/Year data lines correctly.

Now: This is fixed.
Beas\Human Resources\Personell
2019-01-29
12517
1
Personnel edit: problem with extended access definitions
beas 9.3-001-003-000 / beas 9.3H-001-003-000 / beas 9.3-000-030-000 / beas 9.3H-000-030-000 / beas 9.2-005-051-000 / beas 9.2H-005-051-000
Beas\Human Resources\Personell > Zendesk id: 58991

In beas you can define the extented user rights

Past: This was not working


 

New/Fixed:


You can Personal  Master Data – Edit Personal Master Data 


 

with 


You need follow access 

  • Personell â€“ Full 

  • Personell User rights â€“ if you want to change extented access rules 

Or 

  • Personell â€“ Read 

  • Additional Access definition in User rights 

 


You can define this with Personal Master Data – Button "User rights” 
for all users which access = “read” 

2019-01-29
12672
1
HANA error, MRP, Date of Requirement is not calculated correctly when an operation with processing time 0 exists.
beas 9.3H-000-028-000 / beas 9.3H-001-001-000 / beas 9.2H-005-052-000
Beas\MRP > Zendesk id: 58546

Problem is that the preparation dates for the operations are not being taken into account on the MRP calculation.


The Requirement  Date on the MRP ORder recommendation:

 window: mrp_view_detail.psr

is not the same as the date of the start working date from the Work order:

 
The problem is that There was a bad query handling the times

The problem is when the first operation  has processing time:

 

2018-09-24
14373
1
Error in Collective Purchase Order from a merge Work Order
beas 9.3-001-006-000 / beas 9.3H-001-006-000
Beas\MRP > Zendesk id: 63022

Before: When a "Merge" wo is created field "abgkz" into table "BEAS_FTAPL" was filled wrong, this error generates a problem into external operations.


Now: Bug fixed, When a Merge WO is created field "abgkz" if filled with default value "N".



Window: mrp_planed_workorder_browse.psr
Beas\MRP\Order Recomendation
2019-09-27
8443
1
UDF definition in MRP not working as described in the documentation
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\MRP\Order Recomendation > Zendesk id: 49599
Function: UDFs in MRP.

Past:
It was possible to define UDF fields in the project file MRP.SRC. Additionally, it was possible to define this in MRP Wizard - but only for view. Neither variants were very stable.

New:
The UDF setting is in a new place:

 

For more information on this see documentation

Compatibility Information

The setting used to be in area "VIEW" - "UDF". We have moved this and changed the functionality. Please check if the syntax of definition is correct. 

In MRP.SRC it was possible to define up to 3 UDF's. In future we will not support this. The new concept does exactly the same.
2019-01-29
12997
1
MRP view: Alternative items error
beas 9.3-001-002-000 / beas 9.3H-001-002-000
Beas\MRP\Order Recomendation

If you open MRP view details and select one purchase item with "Alternative items defined", then if you open "Alternative tab" and do a right-click over the alternative item you got an error.


(**)Error: don't find `art` in datawindow program\mrp_view_bestellen.psr (command: art.value, function ue_convert.of_item_beas

This function is only available for workorders (we check this before opening the popup menu but we need to be in the "inflow outflow" tab).

After this patch, prior to check if the selected line is a workorder position, we check that the selected tab is "Inflow/Outflow".


 mrp_view_masterrahmen.psr 
2019-01-29
13198
1
HANA: Order recommendation: missing linking in work order to reserve invoice
beas 9.3H-000-027-000 / beas 9.3H-001-001-000
Beas\MRP\Order Recomendation
MRP - Order recommendation -> infow/outflow area - right-click

mrp_view_masterrahmen.psr

Past: 
There is an error when we try to create a work order from the MRP. using the reserve invoice

[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] Syntax error or access violation;257 sql syntax error: line 1 col 45 (at pos 45) -1/257:
select "DocNum" from "OINV" where "DocEntry"=xxx

Now: this error is fxed due to a bad HANA query conversion

(only HANA Version)

Attention: the complete reservation system for reserved invoice together with Work order for: Reservation Invoice is not working.
Currently beas copies only the reference information in the info field
We will fix this in beas 9.3 PL 1 
2019-01-29
13915
1
Purchase order creation without delivery date
beas 9.3H-001-004-000 / beas 9.3-001-004-000
Beas\MRP\Order Recomendation

Order Recommendation Window


A new validation was added to check if the delivery date is empty.

mrp_view_masterrahmen.psr

Before: If the delivery date was empty and we created the order, then the new document came with a wrong delivery date consequently.
After: If the delivery date is empty you receive an error message to prevent the process to go without a valid delivery date equal or greater than today.
2019-01-29
13946
1
MRP: Windowsettings not working with templates
beas 9.3-001-004-000 / beas 9.3H-001-004-000
Beas\MRP\Order Recomendation

In MRP Order Recommendation you can change the view of lists with Window settings.


Additional you can define templates
For every template you can define own window settings

Past:
This was working in the item list, but not in Inflow/Outflow area and not on right window.

New:
Now beas use always the template related window settings.

2019-01-29
12870
1
MRP, Total Inflow of Sub-Assembly not correct when manually increasing the Qty of a WO Sub-Position
beas 9.3-001
Beas\MRP\Order Recomendation > Zendesk id: 60031
Example:


Bill of materials: 1 Pcs
Sub-assembly order related: 1 Pcs
Saldo is 0, inflow and outflow neutrally.  We do not see this in inflow or outflow and in the requirement list it is grey.

 
But if you change the quantity from order related sub-assembly, there is another situation: the quantity is not for main assembly, it is for the stock. 

 
Example: Bill of materials = 1, but we produce 10. 9 is for the stock
in beas only one "inflow" column is available, but in this case we have the following situation:
1 Pcs = neutrally, 9 = Income

beas displays this situation in the following way

item list:
Inflow: include the quantity for the stock, in this case "9" and increase the inflow quantity from 5 to 14
requirement list Inflow: Do not display the neutrally quantity, display only the stock related quantity = 9


 mrp_view_masterrahmen.psr
2019-01-29
13327
1
Order recommendation balance - wrong value
beas 9.3-001-003-000 / beas 9.3H-001-003-000
Beas\MRP\Order Recomendation > Zendesk id: 61140
Previous: into last version of beas fields Saldo and requirements showed information with a wrong format

mrp_view_artikel.psr

Now: Bug fixed - the format of these fields is correct.

Changes (HANA and MSSQL)

In beas Unit of Measure you can define the count of decimal places, which is NOT a rounding function

Example:
Number of decimal: 2
Value: 1.234401
beas calculate with 1.234401 and display 1.23

beas has different rounding systems. But this has nothing to do with the view.
In the latest version of beas we used the "Rounding for scheduling" to round the results. This, however, is not correct in this place and we deleted this functionality
For more information on rounding system see our online help

 
2019-01-29
13366
1
HANA, MRP, Filtering for field 'DIN' creates an SQL error
beas 9.3H-001-001-000 / beas 9.3H-000-028-000
Beas\MRP\Order Recomendation > Zendesk id: 61213
MRP Order recomendation  (only HANA)
Button Filter 


past: SQL error when filtering by DIN fieldname on the MRP order recomendation filter search

General error;260 invalid column name: OITM.U_DIN: line 1 col 6593 (at pos 6592)

new: fixed.

2019-01-29
13842
1
MRP > Order Recommendation: Error when manually entering a price
beas 9.3H-001-004-000 / beas 9.3-001-004-000
Beas\MRP\Order Recomendation > Zendesk id: 61936
In the order recomendation window, if you change the price field in the main list but have not selected the tab order, you get the following error message:

(**)set value price: only object from type column as the property value!

After this patch no more errors happen whatever tab is selected:
mrp_view_masterrahmen.psr
mrp_view_artikel.psr
2019-01-29
12691
1
Warehouse column is shown twice and has an unknown suffix
beas 9.3-001-005-000
Beas\MRP\Order Recomendation

Old:


MRP - Order Recomendation 
We had the column "Warehouse Stock" appearing 2 times but with different functionalities.

1. the complete stock
2. stock - reservations

New Names
Warehouse Stock (no changes)
Warehouse Stock available (changed)

First field is visible in standard
Second field: You can see this only if you activate this in window settings.

mrp_view_masterrahmen.psr

Compatibility information:
If you do not see the new description, you must open the window settings and must click on Button "Default"
 

2018-10-24
13432
1
Order recommendation -> tab "Current income" -> column "Quantity": value "0" is displayed for SAP Purchase Requests
beas 9.3-001-003-000 / beas 9.3H-001-009-000
Beas\MRP\Order Recomendation > Zendesk id: 61325
In the Order Recommendation list there was a problem with the right quantity for an SAP Purchase request.

In the "inflow/outflow" tab the quantity was shown right, but in tab "Current income" > column "Quantity" the value "0" was always displayed.

mrp_view_artikel.psr, mrp_view_planed.psr
 
2018-10-12
14547
1
MRP error
beas 9.3-001-006-000 / beas 9.3H-001-006-000 / beas 9.2-005-055-000
Beas\MRP\Order Recomendation

you can create a Purchase Blanket Agreement




In configuration wizard - pre-calculation you can activate "blanked agreement consider"
This affects MRP, as well.

 

in MRP you can work with pre-assign
1. open order recommendation
1. click on mode
2. click pre-assign




Past: 
In this case you received the error message:

Systemerror 40 Mismatched Any datatype in expression: string, long at line 126 in function of_vorbelegen

New:
Fixed

Workaround
if it is possible, disable "Blanked agreement consider"

 
Beas\MRP\Purchase Request
2019-01-11
14101
1
MRP - Calculating purchase request in HANA
beas 9.3H-001-009-000 / beas 9.3H-001-009-000 / beas 9.3H-001-009-000
Beas\MRP\Purchase Request
In the HANA version of beas it was not possible to select purchase requests; the selection was not shown.
Therefore, the purchase requests could not be considered in the calculation.
Now the selection is shown and if it is checked, then purchase requests will be calculated in MRP.


 
2019-01-29
13383
1
Master/Slave Operation, Linking is lost after creating the WO
beas 9.3-001-002-000 / beas 9.3H-001-002-000
Beas\Production > Zendesk id: 60746
With "Renumber BOM and routing" activated in Config Wizard, and an operation linked to the other we used to lose this link after creating a WO.


ex. Item Structure

ex. after create the WO the linking is lost

fert_ftpos_edit.psr

NEW:
This wrong behaviour has been fixed.
2019-01-29
12704
1
Material Issue, Record in BEAS_PLANDOCUMENT is deleted after 'All Issue' but still allows to create new Records in BEAS_PLANDOCUMENT_LINE
beas 9.3-000-029-000 / beas 9.3H-000-029-000 / beas 9.3-001-002-000 / beas 9.3H-001-002-000
Beas\Production > Zendesk id: 57163
In some special cases there was a problem in the "material issue" window --> when two people
started the window at the same time (not necessarily the same workorder): 
The two users got the same document number and positions from one
or the other and the figures got lost or were wrong.

This Problem is fixed now.




reservation_set_source.psr
2018-11-21
14655
1
Work order can be deleted inspite of linked and released/closed qc-order
beas 9.3H-001-009-000 / beas 9.3-001-009-000
Beas\Production > Zendesk id: 63012
Before: The problem was that you could delete a work order with a linked QC order, when the system is not supposed to allow that.
Now: The work order cannot be deleted if it has a QC Order linked. 

window: fert_fthaupt_edit.psr

1. Create an assembly with a Routing position which has a qc-plan assigned.


 

2. Configuration Wizard. Quality Control > Production > Create QC Order automatically when: Production Create


3. Create workorder for the assembly defined on step 1



4. Check the created qc-order and do the measurements so that the qc-order is released and finished.
 

 
5. Delete the workorder by pressing the button "Delete".


 
2019-09-20
13606
1
production start/end time -> change capacity in resource
beas 9.3H-001-003-000 / beas 9.3-001-003-000
Beas\Production\APS
In configuration wizard you can define production start from time / end time
This setting does not determine a shifts start/end


 

Past:
since beas 9.2 PL5 beas has been using this start/end time to calculate the shift start/end time for a resource but only if you change the time in the configuration wizard 

Now:
beas ignores this while calculation the shift start/end time
window: stamm_arbplatz_edit
 
Performance:
Optimized calculation. On some server the calculation is faster if you start this more than one time.
2019-07-19
12942
1
APS - calculation type: "forward" with overlapped routing position is not working properly.
beas 9.3H-000-028-000 / beas 9.3-000-028-000 / beas 9.3-001-002-000 / beas 9.2H-005-053-001 / beas 9.3H-001-008-000 / beas 9.3-001-008-000 / beas 9.2-005-053-001
Beas\Production\APS > Zendesk id: 59557
APS - calculation type forward with overlapped routing position is not working correct.

We describe this with follow example:

the first routing position must have another resource 
and the parallel position must have another resource too

see this example:
Both have only in pos 40 and 50 same same resource. First resource is different.


 
to check this, we need a time area, in which we don't have any time reservations for coshed resources

Overlapping is "Parallel" in both work order positions
disable all idle times, transit times in routing position and resources

Check calculation methode "Forward"
activate "delete completely" and "Reset start date"

 
Calculate forward in APS

Result
resource 1600 -> first work order pos 10 and then pos 20

Pos 10 Routing 40 + 50: start parallel
Pos 20 Routing 40 + 50: Pos 40 can't start directly. Start date is later - after pos 10/40. But pos 20/50 start BEFORE pos 20/40. This is correct. 

Parallel in beas means only: the first possible start time is parallel.
This is correct and we don't changed anything.


 
Other situation if you work with Overlapping
Same example, but insert 1 hour overlapping in pos 20/40
Calculate this in the APS List again (not in another way)


PAST:
in past it was working in same way as "parallel". But this is not correct.
New:
In this situation the first possible start date for 20/50 is the real start from pos 20/40 + 1 hour. It can't start BEFORE.


 
No changes in backward calculation, because this calculation type is working in complete other way. 

2019-01-29
12851
1
APS, Resources without Resource Limit, Limits will be considered for the current day
beas 9.3-001-004-000 / beas 9.3H-001-004-000
Beas\Production\APS > Zendesk id: 59390

After calculating a resource with limitless capacity, the current day was not calculated well.


Before: we did not check the "capacity limit" flag for the current day

After: we check the flag also for the current day


fert_plan_tafel.psr
2019-01-29
12852
1
APS, Window APS Scheduling pops up in front of the APS Scenario List after closing Gantt Viewer
beas 9.3-001-003-000 / beas 9.3H-001-003-000
Beas\Production\APS
Before:
if you opened the APS View and then the Gantt view and closed the Gantt view, the "APS Scheduling List" became the focus and not the APS View

Now:
After closing the APS Gantt the APS List window (In this example, the window with title: "APS Standard") becomes the focus.
window: fert_xgantt_planing_browse, fert_aps_browse
2019-01-29
12481
1
APS: consideration of time receipts by "Reported amounts" works improperly
beas 9.3-001-003-000 / beas 9.3H-001-003-000
Beas\Production\APS > Zendesk id: 58872
In the gantt-viewer you can move the resources visually in the time (from left to right)
After you select the calculation type (Tab setup > calculation type) and if your calculation type is configured to consider the time receipts by "Reported amounts" then:

before: the time receipts were considered as time always
after: the time receipts are considered by time/amount depending on the setup of calculation time 

2019-01-29
13805
1
APS: edit calculation step SQL error
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Production\APS > Zendesk id: 62080
APS Calculation Type

Past:
If you deleted an additional step, you received the following error message:

Error while Read or Update DataStore: SQLSTATE = 07001
[Microsoft][ODBC SQL Server Driver]COUNT field incorrect or syntax error
No changes made to database.
DELETE FROM "beas_xgantt_methode_step" WHERE "methode_id" = ? AND "step_id" = ? 
SQL-Syntax:DELETE FROM "beas_xgantt_methode_step" WHERE "methode_id" = ? AND "step_id" = ? 

Now: Fixed.

system_option_struktur.psr


2019-01-29
14291
1
Error when deleting a view in an APS scheduling - HANA only
beas 9.3H-001-005-000
Beas\Production\APS
Past: When you deleted a view in an APS Scheduling the view was deleted
but you received an additional error message saying that something could not be deleted.

Now: the deletion works correctly.

fert_xgantt_view_browse.psr
fert_xgantt_view_edit.psr
2019-01-29
7915
1
APS View not existing - open new entry -> not working
beas 9.3-001-003-000 / beas 9.3H-001-003-000
Beas\Production\APS
APS View

Past:
if in the View definition the Description was not defined, you could not see or choose this view in APS List
fert_aps_browse.psr

if the view in the APS scenario was not defined, then the APS List was not correct. APS Gannt view did not work correctly.

New: 
1. In Scenario definition - View the field Description is mandatory 

fert_xgantt_view_edit.psr
 
2. if you open the APS View and the View was not defined, beas displays an error message and opens the Scenario definition - tab "view". 

2019-01-29
13608
1
APS not working correctly if you have a different database time zone
beas 9.3-001-008-000 / beas 9.3H-001-003-000
Beas\Production\APS

After this patch we checked if all time calculations and visualizations are based on the company time and not in the local computer time.


In the next image, before this patch, you can see the orange vertical line represents the current time (-1- my local machine), but the company time is one hour less -2-)
Now: we fixed all graphical displays, and fixed the calculation to be based on (2) the company time instead of the local machine time.

2019-01-29
13430
1
APS Undo function working with select *
beas 9.3-001-003-000 / beas 9.3-001-004-000 / beas 9.3H-001-004-000
Beas\Production\APS
When working in APS-Gantt view, and operations are moved, or workorders are recalculated, the system stores pieces of undo-information.
We have made some improvements to store these information a little faster. 


fert_plantafel.psr
 
2019-01-29
13645
1
APS: Incorrect overlapping calculation
beas 9.3-001-004-000 / beas 9.3H-001-004-000 / beas 9.2-005-052-000 / beas 9.2H-005-052-000
Beas\Production\APS

Inside the APS Browser in combination with method "Delete only selected orders" if you recalculate a work order position with more than one position, it deletes the time reservation for all positions. 

This leads to a bad calculation and the visual overlapping in case of any resource for the calculate position is being used in other positions.

After this patch we delete the time reservation for the selected position and sub assemblies only.

fert_plan_tafel.psr
2019-01-29
13893
1
Change log entries for workorder status changes in APS
beas 9.3-001-006-000 / beas 9.3H-001-006-000
Beas\Production\APS

Work order changelog has been improved to add more information.

Now system save every APS action related with work orders.


Window: fert_aps_browse.psr

Now we have new entries linked to Workorder level and also linked to work order position.


Window: system_aenderung_browse.psr

Beas\Production\Configurator
2019-07-19
13695
1
HANA, Product Configurator, SQL error in Price Formula
beas 9.3-001-003-000 / beas 9.3H-000-030-000 / beas 9.3-000-030-000 / beas 9.2-005-051-000 / beas 9.2H-005-054-000
Beas\Production\Configurator > Zendesk id: 60276

Conifguration wizzard - price formulas


in parameter - tab price it's possible to insert a sql statement

Past: beas executed this command complete in lower case
special on HANA side this created lot of problems or sql errors

New:
beas execute this statement without converting in lower case


windows: artikel_produktkonfigurator,artikel_produktkonfigurator_detail, prd_links2
 
2019-01-29
12995
1
(hana) Production > Generate Variants > Variables: Dropdown error
beas 9.3H-001-000-000
Beas\Production\Configurator

(ddw03)Error in Dropdown Datastore: SQLSTATE = 37000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] Syntax error or access violation;257 sql syntax error: incorrect syntax near ")": line 1 col 76 (at pos 76) (select verweis,bezeichnung from beas_caft_verweis) UNION ALL (select '','') (Error: Entry not found)


past: when doing a right-click on the cross reference field on the variables window, an error came up
now: error is fixed; it was related to a bad HANA syntax

window: caft_var_browse.psr
2019-01-29
14217
1
Systemerror 36 Name not found accessing external object property checkinhalt (HANA)
beas 9.3-001
Beas\Production\Configurator
Systemerror 36 Name not found accessing external object property checkinhalt at line 25 in function of_setparameter_editwindow

This error does not exist anymore in beas 9.3H-001
2019-01-29
12715
1
Product Configurator: Pictures in Radiobox list do not appear
beas 9.3-000-028-000 / beas 9.3H-000-028-000 / beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\Production\Configurator

Configurator - Radio Box


Past:
If you chose "form of output" = "Picture in Title, Title large"
beas did not display the picture.
Additionally, the different settings were not working.
Long text and Text 1 were not displayed.

New:
The setting "form of output" for selection is not available.
Picture, Long text, Text 1 and all other are working correctly for selections.
This setting is deleted in all object types, because it was not reasonable. 


 
 
window: prd_links2, artikel_produktkonfigurator_detail
 
 
2019-01-29
14359
1
Configurator - check price sql - wrong
beas 9.3-001-006-000 / beas 9.3H-001-006-000
Beas\Production\Configurator
Product Configurator



Double-Click on a parameter
Tab "Price"

Past:
if you inserted an sql statement and clicked on "check", beas did not execute the SQL Statement
(only in this window. It was working in the configurator itself)

Now: Fixed

artikel_produktkonfigurator_detail.psr
 
 
2018-10-12
10468
1
Product Configurator: Window of External Configurator does not work correctly
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Production\Configurator

External configurator window was not working properly. When creating a new configuration, the system was not refreshing Configurator ID in the right way.


Bug is fixed into next release of Beas.

Workaround: There is one possibility to avoid error before we release the new version:

1- Create new configuration
2. Before you click on "Bill of materials" or "routing" you have to close header window and reopen. In this way, system refreshes ID in the right way and then you can assign information without problems.


Window: config_header_browse.psr
Window: config_header_edit.psr


2018-10-04
13968
1
Product Configurator, 'variant.pos_text' is not available, 'produktconfiguration' does not return any value
beas 9.3-001-005-000
Beas\Production\Configurator > Zendesk id: 62395
in item master data, bill of material and routing position you can insert scripts, with which you can modify the bill of material and routing position


Some properties didn't work:

Variable <productconfigurator> was not working. Fixed
Property <pos_text> was not working. Fixed
Property <udf5> ...<udf15> not working. Fixed 

HANA: <rdr1.xxx>,<itemcode.xxx>, <bom_itemcode.xxx>, <ordr.xxxx> not working. Fixed

Documentation not complete. Fixed.

 

Beas\Production\External production
2019-01-29
13983
1
Summarized Purchase Order SQl error with "Only shortage" function
beas 9.3-001-005-000 / beas 9.3H-001-009-000
Beas\Production\External production > Zendesk id: 62645

Only HANA Version


Past
External productions
Summarized Purchase Order
Right Mouse-Click
Only shortage

The following error code appeared:
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] Syntax error or access violation;257 sql syntax error: incorrect syntax near ".": line 1 col 3707 (at pos 3707)
SQL-Syntax:SELECT TOP 99999 "BEAS_FTHAUPT"."BELNR_ID" , "BEAS_FTHAUPT"."AUFTRAG" , "BEAS_FTPOS"."ItemCode" , 

Now: Fixed.

window fert_external_toorder_browse.psr

If you use beas 9.3 PL 0 and need a correction, you can ask for the PSR file. By replacing this, you can fix this error.
2019-01-29
11940
1
External production: Label currency in wrong place
beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\Production\External production
If we change the currency in the dropdown (or we had selected other currency in the wo operation sequence) then additionally to the total price in the selected currency we display the total amount in the local currency, as well.

fert_external_toorder_browse.psr


(1) All amounts are in the selected currency (USD)
(2) We display the total amount in the local currency (EUR)

 


The conversion from the selected currency to the local currency was not displayed in the post calculation (but we were using the right converted value for all calculations)
fert_naka_soll_ist_struktur.psr
Beas\Production\Factory data capture\Production Time
2019-01-29
13527
1
Terminal, App Logoff WO, Manual Input of the Barcode brings up errormessage
beas 9.3-001-002-000 / beas 9.3H-001-002-000
Beas\Production\Factory data capture\Production Time > Zendesk id: 61251

If you entered the barcode manually in the Terminal Application Logoff WO to do a logoff, the barcode did not work (The only way was using the dropdown)


Now this is fixed but if you are working with parallel resources simultaneously, and you enter the barcode manually, you need to specify the right resource manually after enter the barcode.

This is because the same barcode can be associated with several resources (parallel resources for the same position)

fert_ftstmp_abmeldung.psr
2019-01-29
14189
1
Edit Time Receipt - Work order Position not locked
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Production\Factory data capture\Production Time
Work order - Routing position - edit existing time receipt

Past:
After opening an existing time receipt it was possible to change the Position
Fixed
fert_arbzeit_erfassen

New:
Fixed. It is not allowed to change the work order position number

 

Deletion:
It was not possible to delete an entry. You receive a "datawindow not updatetable" message. 
New: Fixed.
Beas\Production\Factory data capture\Terminal
2019-01-29
12996
1
Terminal login with integrated keyboard error
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Production\Factory data capture\Terminal > Zendesk id: 60747

Terminal - Keyboard Icon


menu_terminal.psr

Past:
it was not possible to choose an entry via visual keyboard
You receive an error message:

It is not possible to set field cardnumber in datawindow dw_3 (...)

Now: fixed

Position:
Past:
the keyboard was not in the middle of the window
Now
the keyboard is always in the middle of the terminal screen

2019-01-29
13678
1
Logoff within pool list: SQL-error
beas 9.3H-001-003-000
Beas\Production\Factory data capture\Terminal > Zendesk id: 61825
past: Error when logging off an operation inside the pool list window:

(select1234)Error in SQL rule:
SQLSTATE = S1000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;260 invalid column name: BARCODE: line 1 col 14 (at pos 13) -1/260:
select top 1 barcode from beas_ftstmp where belnr_id=186 and belpos_id=20 and pos_id=10 and pers_id=N'1'

now: Error fixed, Bad HANA fieldname syntax

window name: bde_terminal_poolinfo.psr
2019-01-29
13682
1
Multi-logon within pool list: invalid name of function or procedure
beas 9.3H-001-005-000 / beas 9.3-001-005-000
Beas\Production\Factory data capture\Terminal

HANA Version - Setting FDC - Pool Report - Direct on and logoff is active

-> Terminal --> App "Pool list"


past
: There are some  errors when  login multiple orders at the pool report window

(<empty>)Error executing Procedure: SQLSTATE = 37000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] Syntax error or access violation;257 sql syntax error: incorrect syntax near "1": line 3 col 23 (at pos 61): Call create procedure #beastmp_153355
AS
execute beas...

(<empty>)Error executing Procedure: SQLSTATE = S1000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;328 invalid name of function or procedure: #BEASTMP_153355: line 1 col 17 (at pos 16): Call drop procedure #beastmp_153355...

now: The error is fixed, The execution of a stored procedure was not propperly on HANA syntax



window: bde_terminal_poolinfo.psr

Beas\Production\Factory data capture\Work Order Backflushing
2019-07-19
13854
1
Receipt from Production, Negative Price is calculated when BoM has a Position with a negative Qty
beas 9.3-001-009-000 / beas 9.3H-001-009-000 / beas 9.2H-005-055-000 / beas 9.2-005-055-000
Beas\Production\Factory data capture\Work Order Backflushing > Zendesk id: 59395

We had a problem when we did a good receipt for a produced material and the bom contain an item with negative quantity and the valuation method is (L="Working Plan cost, Material real cost").

In this conditions the calculated price for the produce material is wrong (This error was introduced recently after a modification in PL5 only)


fert_stuktur_browse.psr
2018-10-12
15019
1
Pre-assignment process does not work with i-version and none administration items
beas 9.3-001-010-000 / beas 9.3H-001-010-000
Beas\Production\Factory data capture\Work Order Backflushing > Zendesk id: 64108

When you have activated the reservation system and your produced item depends on a sub-assembly that is managed by versions, then after you produce the sub-assembly the quantity is automatically reserved for the main item.


This is right, but the reservation does not contain the version produced and this leads to an error when you try to do an issue of this material because we try to pre-assign the reservation which does not contain any version.



fert_arbzeit_erfassen.psr 
Beas\Production\Project
2019-01-29
12915
1
Project module: usability in edit task
beas 9.3-001-002-000 / beas 9.3H-001-002-000
Beas\Production\Project

Project - Tab "Task" - New task



1.  Catalog Change
Past
if you created a new task and changed the task catalog, beas displayed a German error message
New:
beas saves the entry (this is mandatory) and then inserts the information from catalog

2. Entry blocked
Past
if you changed anything in the task and a linked work order existed and changes blocked in work order (this is normal, because any changes are executed by project), you received the error message "entry blocked..."

New
Now changes are allowed on project side. Synchronisation is working

3. Entry empty
Past
if you created a new task, clicked on "Add" without closing the form and clicked on "tab task" again, the form was empty
New:
beas displays the correct task

Past
if you changed the catalog entry, the field "Position" was empty. 
New: Fixed. beas does not delete the position information

 

window: prj_line_edit.psr
Beas\Production\Sales order to Production order
2019-01-29
12906
1
SO2WO, No entries in 'Order Related' Tab will be shown if Reservation System is not active
beas 9.3-001-002-000 / beas 9.3H-001-002-000
Beas\Production\Sales order to Production order > Zendesk id: 60540
If in the system the reservation system was deactivated,
Configuration Wizard > Production > Reservation


then in the SalesOrder to work order window in the order related tab, no or only a few entries where shown.

 fert_kdauftrag_zu_fertauftrag.psr

This problem is fixed and the order related sales orders will be shown.
2018-10-12
14664
1
Window: Sales Order to Production Order, Tab "Storage-related" - calculation mistake
beas 9.3-001-009-000 / beas 9.3H-001-009-000
Beas\Production\Sales order to Production order
The Sales order to Production order window has two tabs to filter denpending onthe item type (Order Related/Storage Related)

The second tab should display all storage-related orders and invoices

before: The sales reservation invoices were included in the list and the sum of the ordered quantity.
after: The sales reservation invoices are excluded from the list and the sum of the ordered quantity.



 fert_kdauftrag_zu_fertauftrag.psr
2019-01-29
12798
1
Tool Master Data, Dropdown in UDFs not working
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Production\Tools > Zendesk id: 60109

In Configuration wizard - Master Data - Tool . UDF 1..4 you can define a dropdown for this field




Past: beas ignored this in the tool window
New: fixed. The dropdown is working in correct form
window: stamm_wkz_edit.psr


 
Beas\Production\Workorder
2019-10-01
10463
1
work order - Error with Multi branch
beas 9.3H-001-013-000 / beas 9.3-001-013-000
Beas\Production\Workorder > Zendesk id: 51706

This error only happen if you're working with Multi branch, you get a Journal entry message error after create a transaction stock, Beas display a message error:

 "Slip could not be created " [-5002] ,


This error come because the branch id wasn't filled by beas in some places while the SAP document was being created.
After this patch, we set the branch id and the error message is gone (and all documents are created in the right way).




 reservation_set_master.psr
2019-09-20
14207
1
Systemerror 39 Error accessing external object property anfzeit (HANA)
beas 9.3-001
Beas\Production\Workorder
Systemerror 39 Error accessing external object property anfzeit at line 195 in function of_retrieve_visible_entrys of object ue_fert_struktur_browse.

This error does not exist in beas 9.3H PL1 anymore
2019-09-20
14213
1
Systemerror 39 Error accessing external object property docdate (HANA)
beas 9.3-001
Beas\Production\Workorder
Error message:

Systemerror 39 Error accessing external object property docdate at line 389 in function of_issuewo of object ue_reservation.

Error is not reproducable in beas 9.3H-001
2019-09-20
14215
1
Systemerror 2 Null object reference at line 185 in function of_fthaupt (HANA)
beas 9.3-001
Beas\Production\Workorder
Error message:

Systemerror 2 Null object reference at line 185 in function of_fthaupt_add of object ue_fert_ftpos_aufloesen.

Error not reproducible in beas 9.3 PL 1
2019-09-20
14223
1
Systemerror 39 Error accessing external object property menge at line 87 in function of_materialcalculate_strukturpos (HANA)
beas 9.3-001
Beas\Production\Workorder
Error message:

Systemerror 39 Error accessing external object property menge at line 87 in function of_materialcalculate_strukturpos of object ue_xgantt_workorder

This error does not exist in beas 9.3H PL1 any more
2019-09-20
14227
1
Systemerror 39 Error accessing external object property docdate at line 389
beas 9.3H-001-005-000 / beas 9.3-001-005-000
Beas\Production\Workorder
Before: sometimes when user tried to create an issue document for a specific material, systems gave the following error message:

Systemerror 39 Error accessing external object property docdate at line 389 in function of_issuewo of object ue_reservation. Window:ue_reservation Object:  ue_reservation  

Now: Bug fixed, error is fired in a proper way.



Window: reservation_set_master.psr
2019-01-29
9242
1
Phantom items: version number does not appear
beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\Production\Workorder

Now in the table BEAS_FTAPL and BEAS_FTSTL we have a new field:


column=BEAS_FTAPL=SCHEINBAUGRUPPE_VERSION=nvarchar(20)
column=BEAS_FTSTL=SCHEINBAUGRUPPE_VERSION=nvarchar(20)

We save the version of the Phantom Item in this field
2019-01-29
8736
1
Phantom Assembly with Alternative Materials: Switching to Alternative Material does not work as intended
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Production\Workorder > Zendesk id: 51514

In the work orders window the icon to select an alternative material sometimes does not appear (if the bom field "closed" is null)

Also, if you clicked in the empty space used by the icon for an item without alternatives, then the popup menu was displayed with the same item,

After this patch, we fix both bugs:
1. The icon is displayed always if the item has alternative items
2. Nothing happens if you click on the empty space where the alternative icon was 

fert_strucktur_browse.psr
2019-01-29
12881
1
WO, Refresh, SortID/POS_TEXT in BEAS_FTAPL not updated correctly
beas 9.3-001-002-000 / beas 9.3H-001-002-000
Beas\Production\Workorder > Zendesk id: 60073

1) Create a Item Structure like this:

 
2) Create a WO for that item


3. Open the WO Position and click "Refresh"


before: (a) BOM: Wrong "POS_TEXT" (b) OPERATIONS: Wrong "Sort_id" (duplicated)
after: (a) BOM: "POS_TEXT" is the same as before (b) OPERATIONS: Sort Ids were regenerated (it should not be duplicated)

 You can check the pos_text/sortid using these queries:

select pos_text,sortid, * from beas_ftapl where belnr_id=XXXX and belpos_id=YYYY;
select pos_text,sortid, * from beas_ftstl where belnr_id=XXXX and belpos_id=YYYY


2019-01-29
12500
1
Pool Report works only with backward calculation
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Production\Workorder > Zendesk id: 58733
In beas 9.3 the pool function was only working with backward calculation

If you had an APS license and caclulated a work order forward, beas did not recalculate the pool information for this work order.


 
negative effect:
In Pool structure report and in terminal - 


negative effects: Pool structure view and Terminal - pool report the dates were not always correct. 
if you changed the routing plan (insert/delete position) in existing work order, beas did not insert the information in the pool list.

Workaround: if you have this situation in beas 9.3 PL 0 and older:
start "Pooling. Scheduling" function

 
new in beas 9.3 PL 1
now beas calculates the pool list with forward and backward calculation.

2019-01-29
12664
1
Error message after cancellation of goods issue booking
beas 9.3-001-002-000 / beas 9.3H-001-002-000
Beas\Production\Workorder

After an issue cancellation you can get the error "beasedit12301" although the cancellation was done correctly.


We tried to refresh the window but the window was closed after the cancellation was done.

Now: this bug is fixed.

mw_storno_browse.psr


mw_storno_browse.psr
2019-01-29
12935
1
work order bill of material: pos_text in routing pos field
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Production\Workorder

Work order position - bill of materials

Field "Routing Position"
(if not available: activate this in window settings)

Past: In dropdown only the Position ID was available, but no Position Text
New: Now you see only the Position text


 
Example:
Go to Work order > Routing Position
Change the Routing Position information


go back to bill of materials
now you see the correct Position Text and not the internal Routing ID

 
2019-01-29
12683
1
WO Position, Tab Extended, Dropdown for WIP/Variance Accounts returns only '?' if one of the Accounts has no AcctName
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Production\Workorder > Zendesk id: 59293
Work order position
Tab Extented
Dropdown for WIP/Variance Accounts return 

Past: if an account entry had no name (OACT.AccountName=NULL), there was only a question mark and not the dropdown list
New: Fixed. beas always displays the complete account list

window: fert_ftpos_edit.psr
2019-01-29
13841
1
HANA, Item Structure, Cut/Copy/Insert of multiple rows not working
beas 9.3H-001-005-000 / beas 9.3-001-005-000
Beas\Production\Workorder > Zendesk id: 61758

Item Master Data (HANA)


Multiple selection using CTRL+Click did not work

If you selected more than one line using this method, only the first selected line was included in the selection and all others were unselected. This is fixed now and all selected lines are deleted.

artikel_struktur_browse.psr

2019-01-29
13587
1
Work order position - create link to Pre-Invoice
beas 9.3-001-004-000 / beas 9.3H-001-004-000
Beas\Production\Workorder

There are several issues in this ticket related to Cross Reference


1st Issue:
past: nothing happened when clicking on the Document Dropdown inside the Cross Reference Window (reservation_link_edit.psr )
The main idea is that when we select Production or Sales order or Reserve, the dropdown should show all documents related to the Item of the position.
now : it is fixed, the problem was that the query involved was not the correct one

 

2nd Issue  
past: in the MRP Order Recommendation: previously you could not create a workorder with a link related to it. Now it is possible. The problem was related to bad queries and wrongly assigned fields.

window: mrp_view_workorder.psr

 
2019-01-29
13845
1
Reservation Window, SQL Filter in Templates are not working
beas 9.3-001-004-000 / beas 9.3H-001-004-000
Beas\Production\Workorder > Zendesk id: 61875

Reservation list - Templates


reservation_set_master.psr

it was possible to define filter/sort definition, but beas ignored this

This is not possible, because no SQL Statement is behind the window.

New:
now it's not possible to change the sorting /filter in the template definition

 
2019-01-29
14186
1
negative BOM-positions with different currencies of last purchase price: wrong assignment of currencies in goods receipt
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Production\Workorder > Zendesk id: 63172
Before: WO receipt function for negative lines sometimes set wrong currency to lines.
This problem was related to a wrong line numbering and the system set the currency of next line instead of the current line.
This error was reproducible only for time receipt process with negative lines linked to the current operation.



Window: reservation_set_master.psr
Window: fert_arbzeit_erfassen.psr

Now: Bug fixed. System applies right price and currency to each line.




2019-01-29
13102
1
Work order Priority - using
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Production\Workorder
Production - Priority window


 window: basis_prioritaeten_browse.psr

1. Past: Window settings were not available. Now Window settings and Template are available.
    (attention: you cannot insert own fields or UDF in Priority table)

2. Past: it was possible to delete every entry
   New: You can delete a priority only if this priority is not used in an open work order

3. Column "default" was visible, but without function. New: Now it's deleted.
2019-01-29
13117
1
Workorder Priority "Immediately" not working
beas 9.3-001-000-000
Beas\Production\Workorder

In Priority you can define "Immediately." This means: You can start every routing position every time and it is always in the actual pool.


Past: It did not work.
New: Fixed


window: basis_prioritaeten_browse
2019-01-29
13121
1
Pooling, Scheduling - usability
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Production\Workorder

Changed Pooling, Scheduling window


Title:
Past: Pooling
New: Pooling, Scheduling (same as in Menu)

Buttons:
Past: Cancel and then Start
New: Correct order: Start and then Cancel

window: fert_pool_batch
 
2019-01-29
13126
1
Order Reccomendation - mode "pre-assign": It is not possible to create a purchase request
beas 9.3H-001-005-000
Beas\Production\Workorder > Zendesk id: 60943

Only in HANA


Before: when you opened the order recomendation in "pre-assign" mode and click "Purchase Request" you got a sql  error.

Now: no more hana error

mrp_view_masterrahmen.psr
2019-01-29
12762
1
Work order BoM, “position re-activate” function is missing
beas 9.3-001-000-000 / beas 9.3H-001-001-000 / beas 9.3-000-027-000 / beas 9.3H-000-027-000
Beas\Production\Workorder > Zendesk id: 59651

Previous: Option "Position re-activate" was missing into last version


Now: Bug fixed, 

Window: fert_ftstlpos_edit.psr


2019-01-29
11465
1
Sub-assembly in WO is updated despite the field "Change allow" is disabled
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Production\Workorder
Logic for flag "Change allow" is review into system and now works in a proper way.


 Window: fert_ftpos_edit.psr

In previous versions when a subassembly has this flag disabled then you can refresh parent item and then also subassemble is refreshed.
Now flag "Change allow" can be modified only at top level position, into subassemblies flag is hidden:




IMPORTANT: When you upgrade beas from an old version to last one system will validate existing open work orders and will update field "CanModifyWO" of table BEAS_FTPOS of each subassemble to assign value of parent item.



2018-11-29
14767
1
work order deletion - activity log
beas 9.3-001-009-000 / beas 9.3H-001-009-000 / beas 9.3H-001-010-000
Beas\Production\Workorder
If you delete a work order an entry in the activity log will be inserted now.
In the past some entries in the database were not deleted. This is fixed now, as well.


 fert_stuktur_browse.psr
2018-11-21
14570
1
Reopening work order is not possible
beas 9.3-001-007-000 / beas 9.3H-001-007-000
Beas\Production\Workorder
Before: If you reopened a closed document, window did not refresh new options automatically. Therefore, the WO position could not be closed after reopening it was only possible by reopening the window itself.

Now: Bug fixed, after position is reopened, the system refreshes current window and also parent window to have the right menu options.

Window: fert_ftpos_edit.psr


2018-11-21
14225
1
Systemerror 1 Divide by zero at line 105 in function of_ftpos of object ue_pk2fert.
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Production\Workorder

Work order from Pre-Calculation


if a phantom assembly inside the pre-calculation and the quantity of phantom assembly = 0 and you created a work order from this pre-calculation

PAST
You received the following error message:
Systemerror 1 Divide by zero at line 105 in function of_ftpos of object ue_pk2fert. Window:ue_pk2fert Object:  ue_pk2fert  Event:  of_ftpos Line 105

NEW:
Error fixed. beas ignores this phantom item and the sub structure of this item if quantity = 0.

fert_fthaupt_edit.psr
2018-10-17
12498
1
Pool Report, Sorting by Start Date not working properly
beas 9.3-001-010-000 / beas 9.3H-001-010-000
Beas\Production\Workorder
Terminal -> Button "Pool Report" 

window: bde_terminal_poolinfo.psr

Click on Button "Sort"

Past: there was no chance to sort by Start Date 
now: The sort by Start Date is now available
2018-10-17
12663
1
Cancelled batch issues are still available for linking serial/batch
beas 9.3-001
Beas\Production\Workorder > Zendesk id: 56891
The solution is under revision again.
Further information: Ticket 15248

In the past if you linked serial numbers to the batches of  the BOM, all used batches where shown, even if one batch was canceled.
Now only the available batches are displayed.


fert_allocation_batchsernum_list1_receipts.psr
fert_allocation_batchsernum_list3_selection.psr

For further Information on linking serials see:
http://www.beascloud.net/docs/help/online_eng/index.html?fert_allocation_batchsernum_list1.htm


2018-09-21
14193
1
Multiple receipt - Pricing
beas 9.3-001-007-000 / beas 9.3-001-008-000
Beas\Production\Workorder

Logic to calculate price for negative positions were improved.

  • If parameter "Manual price" is active in production type definition then fields to define manual price are visible only for negative postions not for parent item

  • Manual negative price now read "Currency" information in the right way.

 
  • When no price is defined for a negative position system calculate price base on parameter "price_negativ_bom"
Beas\Purchase\Goods receipt Purchase
2019-01-29
12544
1
beas Goods Receipt Purchase (multiple), Error 'no base-Entry found (...)' when manually typing in the Order Number
beas 9.2-005-051-000 / beas 9.3-000-028-000 / beas 9.3-001-003-000 / beas 9.3H-001-003-000 / beas 9.3-000-029-000 / beas 9.3H-000-029-000 / beas 9.2H-005-053-001
Beas\Purchase\Goods receipt Purchase > Zendesk id: 58697
In follow situation you'd an error

1) Set 'Goods Receipt Purchase' to 'Multiple' in Configuration Wizard

2) Create a PO in SAP
3) Go to 'Goods Receipt Purchase', enter the Order Number manually (by typing it in the field)
mw_goodsreceiptpo_edit.psr

4) Enter all the necessary information, add the line and click 'Goods Receipt'

Past: 
beas display follow error message
(**)no base-Entry found in ue_reservation.of_incomminggoods for base-doctype=, base-docentry 996, base-line 1

Fixed.
2019-07-19
13856
1
Hana error, Selecting a Blockage Reason in a Sample causes other Samples (from other QC Orders) to also get the status 'locked'
beas 9.2H-005-053-000 / beas 9.3H-001-004-000
Beas\Quality Control > Zendesk id: 62027
After we check if the samples can be released, in HANA all samples are blocked in fact all data are reset.

The error was affecting HANA only
After this patch, only the affected sample is modified.


2019-07-19
14861
1
Electronic signature of QC Orders doesn't work in HANA
beas 9.3H-001-009-000
Beas\Quality Control > Zendesk id: 64341


before: The problem is that there is an SQL error when releasing a QC Order
Quality Control  > QC orders > Activate Release Checkbox


 

This QC Order needs to have a QC inspection plan that has electronic signature to it.

 

The error is coming when we click on the release checkbox, this error triggers before opening the "Electronic Signature" window

window: bde_pers_sign.psr
 
The error is:
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;339 invalid number: [6930] attribute value is not a number -1/339: 
select "DisplayName",ifnull("WEBPWD_DateTo",now()),"WEBPWD" from "BEAS_PERS" where "PERS_ID"=33


now: we fixed this error adding the correct format to the parameters on PERS_ID field
2019-01-29
14302
1
Scrollbar doesn't go down automatically in measurement samples window (qs_qsftpos_edit)
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Quality Control > Zendesk id: 63233
QC Order - Input per Sample - Measurement ->

Past:
Cursor outside visible area if you choose line with Arrow up/down



Now Fixed. Cursor always in visible area
qs_qsftpos_edit.psr
2019-01-29
13060
1
QC, Assignment of the Batch Number not possible in a manually created QC Order
beas 9.3-001-002-000 / beas 9.3H-001-002-000
Beas\Quality Control > Zendesk id: 60636
Manually created QC Orders for a batch managed item, left the field "Batch" empty and the related dropdown was empty.

After this patch, the field is filled with the batch selected manually at the moment the qc order was created and if you click in the dd the same batch is displayed (only the batch).

qs_qsfthaupt_edit.psr
2019-01-29
13105
1
Creation of Goods Return Document does not work properly
beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\Quality Control > Zendesk id: 59916
Previous: Purchase goods return document type did not work in the right way in QC transfer window. 

Window: qs_transfer_header.psr

Now: Bug fixed
2018-11-21
14609
1
Wrong translation in QC
beas 9.3-001-009-000 / beas 9.3H-001-009-000
Beas\Quality Control
Quality Control order - Measurement Sample - Documents - report Confirmation 
Past: Title was not translated. 
New: Now the Title is correctly translated. Correct word is "Confirmation"

qs_qsartikelattachment_confirm.psr
 

2018-11-21
14647
1
QC, Copying an Inspection Plan does not allow to enter more than 20 chars (fieldsize is 50)
beas 9.3-001-007-000 / beas 9.3H-001-007-000
Beas\Quality Control > Zendesk id: 63854

QC Inspection plan - Copy

An Inspection plan key can have 50 chars.

Past: the function "copy" allowed only 20 characters
New: now you can create a copy with 50 characters in key id

qs_qsartikelhaupt_browse.psr, qs_qsartikelhaupt_edit.psr

If you work with beas 9.3 PL 0, it is enough to replace only the PSR file. Please ask our support.
 
Beas\Resources\Resource Capacity
2019-01-29
13671
1
Parallel Resources, Calculated Time in 'Dispatches' list not correct
beas 9.3-001-004-000 / beas 9.3H-001-004-000
Beas\Resources\Resource Capacity > Zendesk id: 60976
Time in 'Dispatches' for parallel resources is displayed in a wrong format.

Before the time was always divided by 60 for parallel resources (only display). 
Now: the time is displayed correctly.


stamm_arbplatz_einlastung_kom.psr.psr
2019-01-29
14203
1
Error : Divide by zero of_start_optimized
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Resources\Resource Capacity

work order - routing - alternative routing position with optimization



Past:

if you inserted "0" in use factor and recalculated the work order (example, calculate in APS or change any time related routing information)

Systemerror 1 Divide by zero at line 112 in function of_start_optimized of object ue_fert_kapa. Window:ue_fert_kapa Object:  ue_fert_kapa  Event:  of_start_optimized Line 112 

New:

Fixed. beas calculates always with 1 in this situation
 
2018-10-25
13470
1
Column "time" not displayed in window "dispatches"
beas 9.3-001
Beas\Resources\Resource Capacity
The column "time" is calculated by the APS. If the window does not show values in some lines, then the
work order was not included in the APS scenario.


 stamm_arbplatz_einlastung_kom.psr
Beas\Sales\Precalculation
2019-10-08
28917
1
Wrong calculation of the operation scraps in precalculation window
beas 9.3-001-HF
Beas\Sales\Precalculation > Zendesk id: 91798

Routing position with "Scrap of material %"

in combination with linked Material position to Routing position

Different results in work order and pre calculation
Current in analyse, which variant is working correct
2019-09-20
13635
1
Calculation copy function with belnr_id > 32000 : generate negative document numbers
beas 9.3H-000-030-000 / beas 9.3-000-030-000 / beas 9.3H-001-003-000 / beas 9.2H-005-053-000 / beas 9.3-001-003-000 / beas 9.2-005-051-000
Beas\Sales\Precalculation

if you have more then 32000 calculations in your system, beas create wrong document numbers, if you copy a calculation inside a SAP Sales order


It inserted a negative number in the calculation field

 
Fixed.

No workarounds. 
2019-09-20
14205
1
Error: Systemerror 2 line 314 in wf_keycode
beas 9.3H-001-005-000 / beas 9.3-001-005-000
Beas\System and Other

If you clicked a key, when clicking the window to close


Past:
The following error message may have appeared:

Systemerror 2 Null object reference at line 314 in function wf_keycode of object w_beas_edit. Window:w_beas_edit Object:  w_beas_edit  Event:  wf_keycode Line 314 

New
Fixed

Information:
It was not possible to reproduce this error
2019-07-19
13858
1
Windows open slow on MSSQL
beas 9.3-001-004-000 / beas 9.3H-001-004-000 / beas 9.3-000-031-000
Beas\System and Other
On some systems it took a long time from a click on a menu item until a beas window opened.

Example:
For some installations, this process took up to 20 seconds.
Only beas 9.3 PL 0


This problem is solved in these builds.
  • Beas 9.3-000-031
  • Beas 9.3-001-004
  • Beas 9.3H-001-004 

2019-01-29
13964
1
Framework-Problem: addnewobject
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\System and Other

beas script command ue_tab.createnewobject


past: not creating a rectangle outside a column field

Example Script
etab=addnewobject=kalk=lot_flag=column=userfield10=nextlinefrom=avgprice_1
etab=addnewobject=kalk=lot_flag_t=text=Fixed Lot Size=nextlinefrom=avgprice_1_t
etab=addnewobject=kalk=lot_item=column=userfield11=nextlinefrom=lot_flag
etab=addnewobject=kalk=lot_item_t=text=Master Item for Lot Size=nextlinefrom=lot_flag_t



New: problem fixed. beas creates the rectangle in correct way


New:
you can create a checkbox directly with value Y/N
etab=addnewobject=kalk=lot_flag=checkbox=userfield10=nextlinefrom=avgprice_1

2019-01-29
13876
1
Update datastore with primary key
beas 9.3-001-004-000 / beas 9.3H-001-004-000
Beas\System and Other

in beas script you have the object


ue_datastorevalues

with this object you can read and save data

Past:
For updating beas you created a where condition about all fields
New:
Now you can define the primary key and beas creates a where condition only with the primay key

For example (please only on test database) we are working on table BEAS_EVENT
1. Create an Event


now you can create a beas script (in debug window)

// Declare the object
declare=lds=ue_datastorevalues
// Define the Table name for Update
lds.updatetable=BEAS_EVENT
// Read Data
lds=select * from "BEAS_EVENT"
// change entry in first line
lds.description=changed by datastore 1
// save changes
lds.update
destroy=lds


 
Primary key is not defined
if you check the execute sql statement in debug window, you will see the following sql statement

MSSQL

UPDATE "BEAS_EVENT_SETUP" SET "description" = ? 
WHERE "event_id" = ? AND "description" = ?

(for info: from framework generated sql statements you cannot see the arguments. You can see only question marks)

In this case the sql statements is correct, but in HANA beas does not check the event_id. In the where condition you can only see the changed fields

UPDATE "BEAS_EVENT_SETUP" SET "description" = ? 
WHERE "description" = ?

In other situation beas deleted all entries and inserted all entries. This can be very slow.

NEW:
Now you can define the primary key
In this case the primary key is EVENT_ID

// Declare the object
declare=lds=ue_datastorevalues
// Define the Table name and Primary for Update
lds.updatetable=BEAS_EVENT,EVENT_ID
// Read Data
lds=select * from "BEAS_EVENT"
// change entry in first line
lds.description=changed by datastore 1
// save changes
lds.update
destroy=lds

beas creates the following sql statement

UPDATE "BEAS_EVENT_SETUP" SET "description" = ? 
WHERE "event_id" = ?

This is stable in HANA too and beas does not delete it with the Delete/Insert command

If you need more then one Primary key, you can define this in the following way


// get last work order position
long ll_belnr_id,ll_belpos_id
select top 1 "BELNR_ID","BELPOS_ID" into :ll_belnr_id,:ll_belpos_id from "BEAS_FTPOS" order by "BELNR_ID" desc
// Declare the object
declare=lds=ue_datastorevalues
// Define the Table name and Primary for Update
lds.updatetable=BEAS_FTPOS,BELNR_ID,BELPOS_ID
// Read Data
lds=select (fieldfrom="BEAS_FTPOS") from "BEAS_FTPOS" where "BELNR_ID"=<ll_belnr_id> and "BELPOS_ID"=<ll_belpos_id>
// change entry in first line
lds.udf1=changed by datastore 1
lds.udf2=2
lds.udf3=3
// save changes
lds.update
destroy=lds

MSSQL without primary key
UPDATE "BEAS_FTPOS" SET "udf1" = ?, "udf2" = ?, "udf3" = ?  WHERE "belnr_id" = ? AND "belpos_id" = ? AND "udf1" = ? AND "udf2" = ? AND "udf3" = ?

HANA and MSSQL with primary key
UPDATE "BEAS_FTPOS" SET "udf1" = ?, "udf2" = ?, "udf3" = ?  WHERE "belnr_id" = ? AND "belpos_id" = ? 

HANA without Primary key
UPDATE "BEAS_FTPOS" SET "udf1" = ?, "udf2" = ?, "udf3" = ?  WHERE "udf1" = ? AND "udf2" = ? AND "udf3" = ?
This can kill the values in your table ...!



Attention:
Please do not write data directly in beas or sap tables with Update, Insert or Datastore functions. Only do so if you want to change UDF's.
2018-11-28
14812
1
HANA, Define 'None default' template does not work
beas 9.3-001-009-000 / beas 9.3H-001-009-000
Beas\System and Other > Zendesk id: 61228

Template administration

(example item list - beas icon)

Past: Click on "Activation Default" or "Delete Default" returned only an sql error in HANA Version
Error executing Procedure: SQLSTATE = S1000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;260 invalid column name: STANDARDTEMPLATE

New: Fixed

 system_template_browse
2018-11-21
14886
1
Template - unselect default template - translation wrong
beas 9.3-001-009-000 / beas 9.3H-001-009-000
Beas\System and Other
Template Administration

Renamed buttons:
Past: Button "Default" and "Non Default"
New: "Activate Default" and "Delete Default definition"

system_template_browse

With these buttons you can define a template as default template. If active, the system default template is disabled.
You can use this if you do not want to allow a user to see all entries

With "Delete Default definition" it is possible to delete this Default Template Definition.
2019-01-29
12941
1
Right-click Menus; Window will open outside the active window on a different screen
beas 9.3-001-009-000 / beas 9.3H-001-009-000
Beas\Usability > Zendesk id: 60708

Position of context menu was improved when you work with more than 1 monitor.


In the previous version if you work with 2 monitors and you show context menu from second monitor system was always trying to show context menu to left direction, this situation sometimes shows the context menu into first monitor.

Now context menu is always shown in the right screen


Beas\Usability\beas usability extension (B1UP)
2019-01-29
14077
1
you can't disable beas usability package
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Usability\beas usability extension (B1UP)

With Crtl + Doublecklick in a beas edit form, beas open the item placement tool window


Past: 
beas did it always and ignored the setting "use beas usability extension"

New:
if this is disabled, beas open the beas own customizing solition
2019-01-29
13840
1
HANA, Validation Configuration, SQL error when trying to add an entry
beas 9.3H-001-004-000 / beas 9.3H-000-030-000
Beas\Usability\beas usability extension (B1UP) > Zendesk id: 61815
beas usability extenstions (BETA)
New Validation

past: There is an SQL error adding a validation configuration inside any beas window:

(**)Error while Display Report: SQLSTATE = S1000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;260 invalid column name: USERS
No changes made to database.
INSERT INTO "BEAS_SYS_SOURCE" ( "ADDONNAME", "AddOnID", "ACTIVATED", "GROUPID", "SortId", "COLORID", "DESCRIPTION", "CreatedBy", "LASTCHANGE", "WINDOWNAME", "OBJECTTYP", "OBJECT1",..DB-Error:260

Error is that one field is not on HANA syntax, "USERS" need to be  "Users"


window: sys_trigger_edit.psr

Now: error is fixed. 
2018-09-25
14705
1
beas Usability Extension, Script called from B1UP cannot be executed, no beas Version found
beas 9.3-001-009-000 / beas 9.3H-001-009-000
Beas\Usability\beas usability extension (B1UP) > Zendesk id: 63982

Executebeasscript command for B1UP was not working, users always receive following error:


Not able to connect to beas: BeasNotFound (please note you need Beas 9.2 or higer to function)


This bug is now fixed. Problem was in beas side because identifier for internal beaswindow was wrong.

Beas\Warehouse Management
2019-09-20
13041
1
Batch tracing hard error
beas 9.3H-001-003-000
Beas\Warehouse Management > Zendesk id: 60729

The batch tracing display window will fail in hana if the document is originated by a QC Transfer.


This error is hana reproducible only due to the hana engine and the number/string differentiation in queries.

mw_tracing_master.psr
 


2019-01-29
13233
1
Open documents: wrong warehouse and bincode are chosen
beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\Warehouse Management > Zendesk id: 60742

If the same bin location exists across two or more warehouses, then the warehouse area could be selected in a wrong way for batch and serial managed items.


before: we searched the "Range" based in the "Bin Location" only
after: The "Range" depends on "Bin Location" and "Warehouse"


bin_struktur.psr 
2019-01-29
13437
1
Reserved quantities can be booked manually
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Warehouse Management > Zendesk id: 61381
There was a problem in the past when issuing a batch controlled Item manually.
If you had a batch that had a reserved quantity, and another batch also existed,
then it was possible to issue more than the remaining quantity.

Example:
here we have a batch controlled item which has two batches with an Inventory of 10 and 20.
In the second batch there are already 15 reserved.
Past: If you selected the second batch it was possible to issue for example a quantity of 10 because
the system took also the free amount of the other batch into account.
mw_manuell_buchen.psr

Now: the behavior is changed and it is only possible to issue the remaining amount of a batch. In this example 5 (20-15).
If you try to issue more, you will get an error message.

 
Beas\Warehouse Management\Bill Of Materials
2019-09-20
7228
1
(10939) Alternative items not working correctly
beas 9.3-001-009-000 / beas 9.3H-001-009-000
Beas\Warehouse Management\Bill Of Materials > Zendesk id: 46617

In the MRP window you can replace an item by the alternative one but if the original item has a scrap percent, the remaining quantity is wrong.


After this patch, we calculate the total remaining quantity (scrap included) and we set the quantity to a fix quantity with 0 scrap. (Refreshed the field "totalqty_in_whsunit)


2019-01-29
12875
1
Export BoM to excel - stop beas
beas 9.3H-001-001-000 / beas 9.3H-000-028-000
Beas\Warehouse Management\Bill Of Materials > Zendesk id: 60448

Bill Of MAterials - open master data for one record - click on Bill of materials - right-click and genereate an excel report.


past: there was an error when trying to generate an excel report from the Bill of materials window.

Systemerror 15 Error calling external function ws_addXInterval at line 21 in function of_do_static_x_markup of object n_dwr_field.
Window:n_dwr_field
Object:  n_dwr_field  Event:  of_do_static_x_markup Line 21

New: The error is fixed. Apparently there is a problem with DLL in charge of generating these reports.

(only HANA Version)
2019-01-29
13828
1
Tab BoM activity log empty
beas 9.3-001-004-000 / beas 9.3H-001-004-000
Beas\Warehouse Management\Bill Of Materials > Zendesk id: 62185

Bill of materials - List of positions


Past: If you deleted all lines, it was not possible to show the activity log.  The list was empty.

New: If you delete all lines, it is possible to display the activity log.


artikel_stlpos_browse.psr
Beas\Warehouse Management\Inventory Reports
2019-01-29
13045
1
Button reservation List does nothing
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Warehouse Management\Inventory Reports

In "Inventory history" window we had a button named "Reservation List".
This button displayed the list of reservations in the previous versions. The functionality is included now in a tab of the same window. This makes this button unnecessary from now on.


Now button is removed from that window:
Window: artikel_teilekonto.psr
 
Beas\Warehouse Management\Inventory Transactions
2019-01-29
14197
1
Error HANA Bachtnum tracer "qcdocentry"
beas 9.3-001
Beas\Warehouse Management\Inventory Transactions
Past: Systemerror 37 Type mismatch accessing external object property qcdocentry at line 136 in function of_tracer_documents of object ue_chargenbuchung

New: Error was fixed in TFS 13041
2018-09-11
14387
1
Manual receipt in production: decimals in conversion factor in item master data are not considered
beas 9.3-001-006-000 / beas 9.3H-001-006-000
Beas\Warehouse Management\Inventory Transactions > Zendesk id: 63461

Conversion between Quantity (Stock unit) and Conv. Unit was wrong in follow situation

Configuration wizzard - master data - item - display - item master - spec. weight by item is active

 
Item have different Units in warehouse and consumption unit, example Pcs and kg

and in spec. weight a weight with decimal places is inside

and in formula "densitiy" isinside

 on both side...
 
 
 
manual transfer function

Past: beas calculate 4 : 2 and not 4 : 2.5. Result in Conv. Unit was wrong
New: now beas calculate correct and display Conv Unit correct, in this case 1.6 kg


mw_manuell_buchen.psr

 
Beas\Warehouse Management\Inventory Transactions\batch transfer, split
2019-01-29
14282
1
Error Batch Status makes a batch split
beas 9.3-001-006-000 / beas 9.3H-001-006-000
Beas\Warehouse Management\Inventory Transactions\batch transfer, split

Previous: Batch split process always created new batch as "released" status"


Now: Bug is fixed, system creates new batches with status defined into "Status To" field



Window: mw_batchnum_splitt.psr
2019-01-29
14043
1
Batch Split With Bin Locations
beas 9.3-001-006-000 / beas 9.3H-001-006-000
Beas\Warehouse Management\Inventory Transactions\batch transfer, split > Zendesk id: 62886

Before: Batch split process was not working fine for Bin locations, into field "Quantity" value was 0 and then system does not allow to generat splitted documents


Window:mw_batchnum_splitt.psr

Now: Bug fixed, system calculates quantity in the right way and system allows you to generate splitt process for bin locations
 
2019-01-29
14060
1
New Item Button not working in Batch split window
beas 9.3-001-005-000 / beas 9.3H-001-005-000
Beas\Warehouse Management\Inventory Transactions\batch transfer, split
Previous: Sometimes after clicking on button "New Item" into batch split window, dropdowns for Itemcode, warehouse, bin location and Batch do not work.

Window: mw_batchnum_splitt.psr

Now: Bug fixed, after New item button is clicked, every dropdown has the combobox defined in the right way.

Workaround: You can implement a workaround to avoid this situation: in the click event for new item you can add following beasscript code:

function dw_master_item_button_newitem_click

dw_2.reset

dw_1.item.itemcode.protect=0
dw_1.item.whsbatch.protect=0
dw_1.item.whsfrom.protect=0
dw_1.item.whsbinfrom.protect=0
dw_1.item.iversionfrom.protect=0
dw_1.item.whsbatch.value=
dw_1.item.whsbinfrom.value=
dw_1.item.iversionfrom.value=
dw_1.item.qtyfrom.setnull
dw_1.item.qtyto.setnull
dw_1.item.subserialfrom.setnull
dw_1.item.intrserialfrom.setnull
dw_1.item.indatefrom.setnull
dw_1.item.prddatefrom.setnull
dw_1.item.expdatefrom.setnull
dw_1.item.notesfrom.setnull
dw_1.item.subserialto.setnull
dw_1.item.intrserialto.setnull
dw_1.item.indateto.setnull
dw_1.item.prddatto.setnull
dw_1.item.expdateto.setnull
dw_1.item.notesto.setnull
dw_1.item.whsbatchto.setnull
settext=t_rest=
settext=t_qty=
dw_1.item.whsbinfrom.visible=0
dw_1.item.itemname.setnull
dw_1.item.itemcode.setnull
setvar=dd:distnumber=

end function


2018-10-12
14504
1
Batch split - History Button not working
beas 9.3-001-006-000 / beas 9.3H-001-006-000
Beas\Warehouse Management\Inventory Transactions\batch transfer, split

Batch split - right-click - History batch transfer was empty. 


New: Fixed.

mw_batchnum_transfer_historie

Help F1 not working in List view and Detail window

New:
Created documentation and inserted new link
F1 is working now


 
mw_batchnum_transfer_historie_detail
Beas\Warehouse Management\Inventory Transactions\reservation list
2019-01-29
12695
1
Golden arrow in reservation list window does not lead to work order document
beas 9.3-001-000-000 / beas 9.3H-001-000-000
Beas\Warehouse Management\Inventory Transactions\reservation list

Golden arrow for SAP document was not working in reservation list window.


Window: reservation_browse.psr

Now: Bug is fixed - system opens SAP document.
2018-10-12
14555
1
Reservation List -> No entries will show up
beas 9.3-001-008-000 / beas 9.3H-001-008-000
Beas\Warehouse Management\Inventory Transactions\reservation list
in the past if you selected some entries in the reservation (1) and then opened the reservation list (2), the list (3) was empty.
Now the list (3) shows all reservations related to the selected entries from (1)

 

reservation_browse.psr
Beas\Warehouse Management\Item Master Data
2019-01-29
13203
1
New item: Button order wrong
beas 9.3-001-001-000 / beas 9.3H-001-001-000
Beas\Warehouse Management\Item Master Data
beas - item report - create new item

order of buttons wrong:

now changed. The "Create" Button is now on left side

artikel_new 


2019-01-29
13443
1
Inventory History: wrong display of Quarter
beas 9.3H-001-002-000 / beas 9.3-001-002-000
Beas\Warehouse Management\Item Master Data > Zendesk id: 60711

past: there is an error on the Quarter sector when you open the Inventory History window, It is not being shown propperly, just "#0" on the month part


now; error is not shown anymore


artikel_teleikonto.psr
2018-11-21
14585
1
Error in dropdown view: Item Master data > Purchase tab
beas 9.3-001-007-000 / beas 9.3H-001-007-000
Beas\Warehouse Management\Item Master Data > Zendesk id: 63558

Item Master Data - Preferred vendor


Past:
Dropdown was not working correctly, only the cardcode was visible.
If you changed in configuration wizzard - external production - choose vendor, then beas used this setting for the item master data, as well. 

New:
Dropdown is working correctly. You always see all Vendors. This is not related to any setting.

 
In sub-window - Preffered vendor you see the dropdown icon on which you can choose the vendorF1 is working now in the sub-window


 
 
Beas\Warehouse Management\Routing
2019-09-20
13542
1
Master Data Routing position -> cannot insert new position
beas 9.3-001-003-000 / beas 9.3H-001-003-000
Beas\Warehouse Management\Routing

Master Data > Routing 


If you select a routing and try to add a new entry, you get an error because the "POS_ID" field is empty.

After this patch this has been solved.

artikel_arbplanpos_browse.psr
2018-12-21
12660
1
Copy/Insert Routings, Tools/Parallel/Alternative positions are not considered
beas 9.3-001-009-000 / beas 9.3H-001-009-000
Beas\Warehouse Management\Routing > Zendesk id: 59333
If you use the function "copy selection" in the item structure window and the selected row is a routing with tools, parallel and/or alternative rows then these position are not considered and they are not copied

artikel_struktur_browse.psr


Other problem we fixed is related with the drag'n'drop functionality, when you drag a routing (which is expanded) then all the subposition are not deleted (visually only) from the old position

before: after you drag the expanded routing, all subposition are left there
after: all subposition are deleted from the window
artikel_struktur_browse.psr
2018-10-02
15296
1
routing master data doesn't take the values from operation catalog and the time setup is mandatory HANA
beas 9.3-001-013-000 / beas 9.3H-001-013-000
Beas\Warehouse Management\Routing > Zendesk id: 65248
Routing -> Edit Routing -> Tab Routing-> insert new position -> choose operation

Past:
you become error message:


2018-09-26
14768
1
Web app: repeat print doesn't work
beas 9.3-001-008-000 / beas 9.3H-001-008-000
Beas\WEB > Zendesk id: 58830

Currently we have two different objects to deal with printer "ue_htmlprint" and "ue_htmlserver", and the second one was the only working with "repeat print" functionality in the right way.


We fix this, and now all application using the "ue_htmlprint" object have the same functions than the others.

After an application using the "ue_htmlprint" like "Transfer" print something then you could go to the setup>repeat print and replay the printing command.


 
2019-01-29
12586
1
webapp logon/logoff order - wrong pos id
beas 9.3-001-001-000 / beas 9.3-001-003-000 / beas 9.3H-001-003-000
Beas\WEB\Apps

Fixed the reference to the work order position id (Now it displays the "pos_text" while we work internally with the "pos_id")

wo_logonlogoff.src
2019-01-29
12846
1
Web Apps, Allocation, Next Page/Previous Page buttons not working
beas 9.3-001-000-000 / beas 9.3-001-003-000 / beas 9.3H-001-003-000
Beas\WEB\Apps > Zendesk id: 60348

Web App Allocation


If you select a work order position instead of selecting the material directly by using a barcode, the list of materials is displayed.

When the list of materials is greater than the maximum number of record per page, then several controls are displayed to go to the first/prior/next/last record.

before: the navigational controls did not work
after: the navigational controls work fine

2018-10-24
13677
1
WebApp, Issue for Production, Only default Warehouse is considered when manually entering the Batch Numbers
beas 9.3-001-003-000 / beas 9.3H-001-003-000 / beas 9.3-001-008-000 / beas 9.3H-001-008-000
Beas\WEB\Apps > Zendesk id: 61289

If you select a batch/serial item managed and enter the batch/serial number manually (without use the search icon) then the right warehouse is not displayed.


After this patch, when you write the serial/batch we load the first warehouse for this batch/serial number with enough quantity