New
2019-08-16
27510
2
New property "item.x.dropdown.displayedvalue" for dw_x
beas 9.3H-002-069-000 / beas 9.3-002-069-000
Beas\Beas Script
In a dropdown field it's possible to insert a translation

1=red
2=blue
3=yellow 

and so on

In the past it was only possible to read the value (1..3), but not the text (red,blue,yellow)

New:
Now it's possible to read the "visible" text from a column.

<dw_1.[column].dropdown.displayvalue>
 
2019-07-10
25392
2
beas script sqlca object
beas 9.3-002-063-000 / beas 9.3H-002-063-000
Beas\MRP

beas script 


new object "sqlca"
This is the collection of all SQL commands and SQL properties for current SQL connection as "object"

This make the using of beas script more simple and quality will be better

New properties are
- udf: List of all beas UDF fields (MSSQL: u_[fieldname], HANA: U_beas_[fieldname],

- result: Result of last sql statement (Past: wert1, wert2...)

- concat (+ or || )

- getdate (getdate() or now())
 
- ishana (true/false)

100% compatibility to "old script variant"

2019-06-26
23507
2
MRP: working with MASS Data
beas 9.3-002-060-000 / beas 9.3H-002-060-000
Beas\MRP
New Analysis function



The MRP Analysis displays information on count and time from calculated table records.
If MRP is slow, you can analyze the calculation. You can see the count of records and time for calculation and start activities with which you can help to trigger faster performance.


 
For more information see our online help.
2019-07-23
13892
2
own report - other date areas
beas 9.3H-002-069-000 / beas 9.3-002-069-000
Beas\Production

In Own reports new time area available



fert_report_parameter.psr

To next 7 / 14 and 30 days
The date area is from past up to today + count of defined calendar days
Beas\Production\Factory data capture\Work Order Backflushing
2019-07-22
26316
2
Beas script: New properties
beas 9.3-002-068-000 / beas 9.3H-002-068-000
Beas\Production\Factory data capture\Work Order Backflushing

In the Development window you can see and use additional information


System - SAP

sys_editor_bscript.psr

<System.Localization>
Return the current localization (CINF.LawsSet)

Main fields from SAP setting
<System.sap.[setting]>

Example:
messagebox=Localization: <system.localozation>, SAP Version (Database): <system.sap.version>


 

Beas\Production\Workorder
2019-07-26
26170
2
Beas standalone: Progress bar freezes
beas 9.3-002-070-000 / beas 9.3H-002-070-000
Beas\Production\Workorder > Zendesk id: 88048

Bas standalone

Database test, work order refresh and other processes with long duration

Past: The progress bar freezes.
New: The progress bar will not freeze in the future.


 
2019-07-11
23719
2
QC: Reopening already released Samples
beas 9.3H-002-060-000 / beas 9.3-002-060-000
Beas\Quality Control > Zendesk id: 80085
Function: Releasing Samples in QC

Depending on QC inspection plan settings it is possible to set the "release" automatically or manually in samples. 
In QC Definition - Release you can define "Manually always". But this means: You can release this manually always. But the system change this sample to "Release" automatically, if all measurement positions are ok. 
It was not possible to reopen the Sample

 
NEW FUNCTIONALITY: 

Now it's possible to reopen a sample with "Opened manually"
qs_ftmessung_browse.psr
 
2019-06-18
23598
2
Attached document saved in wrong place - bmp folder (not an error)
beas 9.3H-002-054-000 / beas 9.3-002-054-000 / beas 9.3-002-060-000 / beas 9.3H-002-060-000
Beas\Quality Control > Zendesk id: 74973

The target path to save the attached documents is the one defined in the configuration wizard: Administration > Print and report setup > Folder for attachments.



 
2019-08-09
24528
2
Pool List - Healthy concept
beas 9.3H-002-064-000 / beas 9.3-002-064-000
Beas\Usability
The idea of the Pool list is to display the work for ONE worker for the next 1-2 days.
But many customers used the List as "administration list" or to display the work of all workers.
The Pool list is not the correct list for this purpose. It can get increasingly slow.

In Beas 9.3 PL 3 we will deliver a work list for Administration.

In the pool list we inserted different functions for correct usage.

1. If the time to open the list takes more than 5 seconds, we display some  information on how to use the list correctly with Link to the documentation.
2. In the Configuration wizard you can define which routing positions the worker can see (related to start date). By default this is the next 99 days.

bde_terminal_poolinfo.psr

1. Duration
If it takes too much time, you can see this warning message.
If you don't want to see it again, click on "do not show anymore".
If you want to see more information: Click on "** documentation **"


2. Dispatching Index:
New setting in configuration wizard: Dispatching Index: Quantity days consider


(setup: poolliste_kapanztag, default=99)

We will use this parameter to adjust the time range in which the calculation will be calculated for the open work orders. This will reduce this calculation time. 

 
Note:
If you don't work with APS forward calculation, it can be a risk to change the setting "Dispatching Index", as the date/time may be wrong inside the start date field of the routing position.


Beas\Usability\beas usability extension (B1UP)
2019-07-19
18901
2
B1UP -> access to beas placeholder
beas 9.3-002-065-000
Beas\Usability\beas usability extension (B1UP)

In beas placeholder defined with <fieldname>
in b1up placeholder defined with $[x]
It is possible to read fields from beas window too with $[x]

Syntax: $[BEAS:x]
Example: '$[BEAS:dw_1.item.itemcode.value]'
You can use beas Format functions, example format "dbstring" for SQL format
select "ItemName" from "OITM" where "ItemCode"=[BEAS:dw_1.item.itemcode.value,dbstring]
See Form, DataWindow, Items

 
Beas\Warehouse Management\Item Master Data
2019-08-08
24483
2
New "Work list"
beas 9.3H-003-000-000 / beas 9.3-003-000-000
Beas\Warehouse Management\Item Master Data
Function: New work list is available.

Past:
the Pool list was used as "Work list". But this was not the idea of the Pool list. This list is working only in terminal window and it's not possible to open linked document (Work order, Routing positions)
It's not a list to manage the work list.

New:
With Beas 9.3 PL 3 a new list called "Work list" is available.
- View of all open routing positions and parallel resources
- Part of basic license
- link (yellow arrow) to all linked documents and data (Item master data, work order, routing and so on)
- Pool planning 
- Use as Pool list inside SAP (part of basic license)
- manage many entries. 

This list is part of "own reports"

For all information see our documentation and the attached Video.


2019-07-31
25222
2
Item Master Data, Stock By Bin Location when using SAP Bin Warehouses
beas 9.3H-002-071-000 / beas 9.3-002-071-000
Beas\Warehouse Management\Item Master Data > Zendesk id: 86126
Item Master Data - Inventory Data 
by Bin location

Past: SAP Bin locations were not supported.

artikel_edit.psr
 
New: SAP Bin locations are supported.

 window: artikel_bestand_nach_lagerplatz.psr

Notes:
WMS Bin Location is not supported in this view.

2019-08-09
24627
2
SAP & WMS bin management: WO > Cancel Issue
beas 9.3-002-072-000 / beas 9.3H-002-072-000
Beas\WEB
Added support to SAP/WMS bin location at issue cancellation.

You can right-click, and the dropdown will display the location for the selected warehouse.
Also, if you enter the location manually, we check if it is a valid location.


window:  mw_storno_browse.psr
 
2019-07-03
24379
2
WEB Transfer Request
beas 9.3H-002-063-000 / beas 9.3H-002-063-000 / beas 9.3-002-062-000
Beas\WEB

 
 
 
2019-06-14
24368
2
WEB Interruption Start
beas 9.3-003-000-000 / beas 9.3H-002-060-000 / beas 9.3-002-060-000 / beas 9.3H-003-000-000
Beas\WEB

 
 
Fixed
2019-07-12
24880
1
Batch Split - The batch attribute updated as Sys number not the attribute value
beas 9.3-002-063-000 / beas 9.3H-002-062-000
Beas > Zendesk id: 86780

Batch split function


Past:

If you inserted an existing batch number on the right side, the system inserted the wrong information in field "Batch attribute1", "Batch attribute 2".


New

Fixed.


 mw_batchnum_splitt.psr
 

2019-06-28
24953
1
HANA, Material Issue, Syntax error U_beas_lck
beas 9.3H-002-061-000 / beas 9.3H-002-056-000
Beas > Zendesk id: 86776

There was  an error by clicking All Issue button on Material Issue window:



reservation_set_master.psr

This happened due to having one of the warehouses with this setting:
field type on "Purchase commission stock".



the error: 
(<empty>)(sql2ds2) Error while generating datastore. Error Code SQLSTATE = S1000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;260 invalid column name: U_BEAS_LCK: line 1 col 43 (at pos 42) select "WhsCode" from "OWHS" where ifnull(U_beas_lck,'')='K'

Now: This error is fixed.
2019-06-27
24881
1
Preceding entry/next entry not working on Personal Administration
beas 9.3H-002-060-000 / beas 9.3H-002-055-000
Beas > Zendesk id: 86756
This error was solved in TFS 24486 - Bug 24486: Work order position: Next entry SQL error 

2019-06-17
24675
1
Reservations, SQL error when creating Delivery/Invoice
beas 9.3H-002-055-000 / beas 9.3H-002-060-000
Beas > Zendesk id: 86352

error on Reservation - Delivery/Invoice process


SQL error when creating a Delivery document created from a sales order

Wrong Result:
- After Delivery/Invoice, the Warehouse Reservation still remains on the WO Position, causing other Deliveries being blocked due to existing reservations

(<empty>)(sql2ds2) Error while generating datastore. Error Code SQLSTATE = S1000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;383 invalid identifier: Line: line 1 col 739 (at pos 738) select "Line"."ItemCode"||'' as "ItemCode", coalesce("Line"."BaseRef",'') as "BaseRef",coalesce("Line"."BaseType",0) as "BaseT
SQL Statement:



Beas\Administration\Data Import and Export
2019-08-12
27854
1
DIH, Transaction Plan Lines, WORM not working, Serial Numbers not working
beas 9.3H-002-074-000 / beas 9.3-002-074-000
Beas\Administration\Data Import and Export > Zendesk id: 89844
Function: DIH - Import work order receipt

Past: Transaction Type "WORM" was not working.


Now: Fixed.


2019-07-19
22317
1
Barcode didn't change after import the work order position
beas 9.3-002-065-000 / beas 9.3H-002-065-000
Beas\Administration\Data Import and Export

Using the object ue_api_wo the new positions added to a WO doesn't get the right barcode


This error is easier to see using the DIH and importing a position with a position number diferent than 10


Beas\Administration\Makros and Crystal Report
2019-07-10
24901
1
Parameters fields in Macro window: Can't capture more than 25 characters
beas 9.3H-002-064-000 / beas 9.3-002-064-000
Beas\Administration\Makros and Crystal Report
Report Macro setup

Definition fields: 

Past:
The horizontal scroll in this field was not working.
It was only possible to insert ~25 letters

New:
Fixed.



 
report_makro_edit_page1.psr

Workaround:
It is enough to replace the .psr file from the current Version.
Beas\Administration\System Initialization
2019-08-16
25365
1
MRP, Fast input by keyboard does not update Qty fields
beas 9.3H-002-066-000 / beas 9.3-002-066-000
Beas\Administration\System Initialization

Steps:
1) Go to MRP Order Recommendation List
2) Go to Window Settings and enable fields 'Qty Purchase' and 'Qty Warehouse'

3) Click on 'Mode' and enter values into Qty Purchase fields into multiple lines by using the DOWN ARROW key (see gif below)
4) Create Purchase Request (beas mode)

Past:
Only lines where Qty Warehouse is filled correctly will be listed in Purchase Request.

New:
Value from Qty Purchase field has to be transferred correctly to Qty Warehouse field.
All lines with valid Qty Warehouse/Qty Purchase values have to be listed in Purchase Request.

mrp_view_masterrahmen.psr
2019-07-30
22967
1
Update Beas - stuck in Install reports and objects
beas 9.3-002-070-000 / beas 9.3H-002-070-000
Beas\Administration\System Initialization
There was a problem updating Beas.
The system took long to process, and it crashed occasionally. 
It stayed at "install reports and objects" message.


You can reproduce this error also by making a data check:


 
system_dbtest.psr
New: This is fixed, it takes less time and the system does not crash.

2019-07-22
25400
1
Beas error - in function of_menuload of object ue_beasgui
beas 9.3H-002-067-000 / beas 9.3-002-067-000
Beas\Administration\System Initialization > Zendesk id: 87397
If Beas is started together with B1up, the following error tends to appear (not reproducable on other systems):

Systemerror 39 Error accessing external object property menus at line 89 in function of_menuload of 

New:
The system continues to work in this error case without an error message.

Current plan: Next Beas 9.3 PL 2 Hotfix.
2019-08-16
25057
1
Systemvariable not filled anymore with actual windowname
beas 9.3-002-065-000 / beas 9.3H-002-066-000
Beas\Beas Script

Beas script


Past: We had the variable <sys_usereventfile>
with the name of datawindow name.
This is not working anymore.

New:
The variable returns the datawindow name again.

Attention:
Please use new names in future new Syntax:  <dw_1.dwname>



In Development tools you can see all properties



 
2019-07-26
26279
1
ue_reservation > receiptwo plandocument_line not deleted after receiptwo
beas 9.3H-002-069-000 / beas 9.3-002-069-000
Beas\Beas Script

This function does not delete entry in "BEAS_PLANDOCUMENT_LINE" after creation of the transaction:


declare=res=ue_reservation
res=planned=new=receiptwo

res=planned=addline=base_doctype=wo&
<tab>base_docentry=1329&
<tab>base_linenum=10&
<tab>base_linenum2=0&
<tab>itemcode=FP&
<tab>whscode=01&
<tab>quantity=1&
<tab>save

res=receiptwo
destroy=res


New
The system deletes the entry from table  "BEAS_PLANDOCUMENT_LINE"
2019-07-01
24946
1
WO Issue, event pre_issue
beas 9.3-002-060-000 / beas 9.3H-002-060-000 / beas 9.3-002-055-000 / beas 9.3H-002-055-000
Beas\Beas Script

When you cancel the event "pre_issue", the window closes itself and the previous window crashes, as well.


The problem was that we disabled the redraw before executing the event, and we must re-enable the redraw in case we cancel the process.

window: reservation_set_master.psr
2019-08-16
24967
1
Chinese Windows Settings don't work with special discount prices in the MRP
beas 9.3H-002-066-000 / beas 9.3-002-066-000
Beas\MRP > Zendesk id: 77491

China regional settings


 
Function: MRP - Price valuation

Past: If you worked with Price List - Period Discounts

 
the price valuation in MRP - Order was not working always correctly.


The system did not check the date with correct format.

New: Fixed.




2019-07-19
25295
1
HANA Version systemerror purchase blanked agreements MRP
beas 9.3H-002-066-000 / beas 9.3-002-066-000
Beas\MRP

This is a bug related with the MRP calculation in HANA version when you activate the purchase blanked agreements and execute a calculation you got a hard error

 

Calculate this scenario:


 window: 
mrp_browse.psr


2019-07-19
24524
1
Sales Blanket Agreements open quantity is not working properly in MRP
beas 9.3-002-066-000 / beas 9.3H-002-066-000
Beas\MRP > Zendesk id: 80293

If the periodicity of a blanket agreement is defined as "one-off" or "one time", 

when reaching the quantity we don't delete the agreement and we start again like in a repetitive agreement.

 
MRP window:

window: mrp_view_masterrahmen.psr
2019-07-16
25388
1
Preview window not working
beas 9.3-002-064-000 / beas 9.3H-002-064-000
Beas\MRP
Extras - Preview window


In this window you can see the picture of the current item entry.

Past:
It was not working since Beas 9.2 PL 5.

New:
Fixed.

 
2019-07-11
24494
1
MRP: Calculation Update not working with Summary by weeks
beas 9.3-002-062-000 / beas 9.3H-002-062-000
Beas\MRP

When the summary type is not detail, the calculation update cannot be re-computed, we explain this as "Restrictions" on the help:




Now the "Calculation Update" entry is hidden if the "Sum peggings" is not "Detail".

 
2019-08-16
26032
1
Report Scrap - SQL error HANA
beas 9.3-002-065-000 / beas 9.3H-002-066-000 / beas 9.3H-002-065-000
Beas\Production > Zendesk id: 87546
Reports production - Evaluation Scrap - Scrap Id - Multiple Choose
 

 system_multichoise.psr

Past (only HANA): 
You get follow error message:
Error while Display Report: Select Error: SQLSTATE = S1000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;260 invalid column name: ScrapDescription: line 1 col 22 (at pos 21)
SQL-Syntax:SELECT TOP 99999 ' ',"ScrapDescription","SCRAP_ID" from "BEAS_REASONFORSCRAP" order by "SCRAP_ID"

New:
Fixed.
2019-08-09
27812
1
BSL, Custom filters on Bindropdown
beas 9.3H-002-073-000 / beas 9.3-002-073-000
Beas\Production > Zendesk id: 85416

- internal -

2019-08-06
27773
1
Web 2.1, Batch Details, Status of Batches not correctly displayed
beas 9.3H-002-072-000 / beas 9.3-002-072-000
Beas\Production > Zendesk id: 88300
Function: Extended Batch editor in WebApps 2.1

Past: When we opened the extended batch editor, the batch status was not displayed correctly (or was empty):



New:
We have fixed the dropdown with the right status codes:
- 0 - Released
- 1 - Not Accessible
- 2 - Locked


 


2019-08-04
23434
1
Faster creation and refresh of WO
beas 9.3H-002-066-000 / beas 9.3-002-066-000
Beas\Production > Zendesk id: 77843
Function: In this version we improved the speed of refreshing a WO and created a new setting to speed up the creation of WO positions if working with lotsize.

1. Faster refresh
PAST: For Items that had a long BOM and many phantom Items inside, it could take very long to refresh a WO.
Now: The refresh process is optimized, so the refresh is much faster than before.

2. WO creation with defined lotsize in item
Past: If many WO positions had to be created, because of a small lotsize, the creation last very long. For each position the whole creation process
had to be processed.

Now: In Configuration wizard > production > create there is a setting "fast copy for lotsize". If this is activated, the system checks if the "fast copy" can be used.
If possible only the first position has to be created. All following positions are than only a copy from the first.




2019-07-31
27588
1
Resource - Transit time administration not working
beas 9.3H-002-071-000 / beas 9.3-002-071-000
Beas\Production
Function: Resource - Transit time in days was not working correctly.

Past:
- Dropdown not working.
- Manually inserted information not checked correctly.

stamm_arbplatz_uebgzeit
 
New:
- the system checks the manual input correctly; it is now compatible with HANA (lower/upper case check)
- better error handling
- dropdown working correctly

2019-07-30
26297
1
Receipt Items / Produced item cannot be linked at the same time
beas 9.3-002-069-000 / beas 9.3H-002-071-000
Beas\Production
Function: In the Backflush process the system didn't create a link to Documents, created for negative Bill of Material Positions.

New:
Now the system creates a link for the created receipt document, too.



In this example receipt document 2596 for negative BoM Position 10 (Item"RM")

In the Backend the system: write the information in Time Receipt table BEAS_ARBZEIT.PostInBoMDocEntry



2019-07-30
24482
1
Attendance > Personnel > New entry with a non-numeric ID HANA
beas 9.3H-002-060-000 / beas 9.3-002-060-000
Beas\Production
Problem when creating a new personnel with alphanumeric ID


Query error:
(select1234)Error in SQL rule:
SQLSTATE = 37000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] Syntax error or access violation;257 sql syntax error: line 1 col 71 (at pos 71) -1/257: 
select "NAME1", "NAME2", "NAME3" from "BEAS_PERS" where "PERS_ID" =

Attendance > Personnel > New entry with a non-numeric ID HANA
bde_personal_edit.src

2019-07-26
27506
1
Own report: Window settings not working
beas 9.3-002-069-000 / beas 9.3H-002-069-000
Beas\Production
Function: Own report
Creation of new report
Window settings

Past: Window settings were not working if template window was not opened.

New: Fixed.
Related to all "own reports".

 
fert_report_parameter.psr
2019-07-26
27587
1
Resource Dropdown displays wrong field
beas 9.3-002-070-000 / beas 9.3H-002-070-000
Beas\Production
Past: Resource dropdown displayed field "morder" on the right side. This field is the order for machine optimization.

New: Now this field is invisible.

 
2019-07-26
24475
1
Terminal, Login WO, Error 'this function may not called anymore. it is replaced by batch=fert'
beas 9.3H-002-069-000 / beas 9.3-002-069-000
Beas\Production > Zendesk id: 85774

If you made a customizing in Terminal - Logoff Window, the following error message appeared in the Terminal - Logon Window: 


(<empty>)this function may not called anymore. it is replaced by batch=fert....
program\fert_ftstmp_anmeldung.psr
mp_abmeldung.src:start_alloc_or_reservation():start_alloc_or_reservation

New: Fixed.


fert_ftstmp_anmeldung

Workaround: 
Delete file c:\program files\beas software\beas\program\fert_ftstmp_anmeldung.src or delete the text inside this file.
2019-07-25
26056
1
Macro Report: Translation not correct after changing language
beas 9.3-002-065-000 / beas 9.3H-002-067-000
Beas\Production
Start Beas in standalone mode (current language = English)
Change language to another language:

 
Print a report (work order, post calculation or what else)

Past:
The report was printed in the language which Beas was started in.

New:
The report uses the currently defined language.
Example: Changed from English to German:

 
 
2019-07-19
25230
1
Material Issue is not taking the quantities from the allocation warehouse
beas 9.3H-002-063-000 / beas 9.3-002-063-000
Beas\Production > Zendesk id: 86827

This is a critical error existing since Beas 9.3 PL 2


Past:
  • working with reservation
  • use function "allocation" to transfer items from default to allocation warehouse 
Function was not working.
The system created the transfer document to allocation warehouse, but the reservation was made to the source warehouse.
If you create the issue document, the system tried to use stock from default warehouse and not from the allocation warehouse.
Therefore, the wrong reservation caused further problems.

New:
Fixed.

2019-07-16
21698
1
PreAssign not working with 7000 lines and more
beas 9.3-002-063-000 / beas 9.3H-002-056-000 / beas 9.3H-002-061-000
Beas\Production > Zendesk id: 70453

There is a problem in allocation memory and memory drain at clicking the Pre-assign button for Items greater than 7000~



reservation_set_master.psr

We have improved the first query for this preassign, less memory loss with this new query.


We can see an increment on the CPU processing resources with previous queries. This increment was being processed for some time:




With the new approach: we can see that it is much faster.

 

 
 
2019-07-09
20306
1
Wrong Numbering in new WO with phantom items
beas 9.3H-002-062-000 / beas 9.3-002-062-000
Beas\Production
Function:
Creating a WO that has phantom Items with operations in the master data
...

PAST: When the work order was created, the numbering of the operations were wrong when the main Item included a phantom Item with operations
inside the phantom item.

NEW: If the Item includes a phantom item, both the BOM and the operations will be renumbered when the WO is created.


2019-06-28
24486
1
Work order position: Next entry SQL error
beas 9.3H-002-056-000 / beas 9.3H-002-060-000 / beas 9.3-002-060-000
Beas\Production
Function:

Work order Pos - go to previews / next position.
Only at work orders with more than one position.
fert_ftpos_edit.psr
 

PAST: SQL Error
SQL Error:SQLSTATE = 37000 [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '<'.

NEW: Fixed.



Expected result: No error message should appear.
2019-08-02
25302
1
Overlapping for parallel operation with setting "Parallel fix"
beas 9.3-002-064-000
Beas\Production\APS
Function: APS calculation


PAST: The "limit fix" setting was introduced to define a fix overlapping.
Therefore, if overlapping is set to one hour, the subsequent operation will start exactly one hour later.
This setting did not work for operations with an "overlap limit" set to parallel.

NEW: The "limit fix" is now working with parallel operations too.
This means if the "overlap limit" is set to parallel, the system will always search for times where both operations can start exactly at the same time.



Example:

Work order with 
- same start date
- first operation has different resource and overlapping = prallel
  (In first Work order Position = i001, in second i001-1)
- second operation (the parallel operation) has same resource


 
Standard solution:
Parallel means: earliest start of second operation is same as from first operation
In this picture you can see
First operation from both work order positions have same start time (different resource)
Second operation:
First work order Position start in parallel with first operation - it's parallel
Second work order Position the parallel resource can start later, because earlier the resource is not available

 
If the new option "Overlap limit (fix)" is activated

 
We see follow result:
In second work order position the first operation can start only, if the parallel operation (second operation can start too
In this case after second operation from first work order position
Parallel = ALWAYS parallel

 

Limitation
This is only working with max. 1 parallel routing position 

Operation 1+2 = Parallel/Overlapping, Operation 3+4 normal -> ok
Operation 1+2+3 = Parallel/Overlapping, 4 normal -> not working
Operation 1+2 and 3+4 Parallel/Overlapping -> ok
2019-07-26
27492
1
APS, Transit Time between Resources only considered at Backward Scheduling
beas 9.3H-002-071-000 / beas 9.3-002-071-000
Beas\Production\APS > Zendesk id: 88840

In Resource you can define a transit time per target resource.



stamm_arbplatz_uebgzeit.psr

Past:
The APS ignored this setting in forward calculation.

New:
Fixed. Transit time is now calculated correctly for forward and backward calculations.


 


2019-07-10
20638
1
MS SQL - APS List, Tables locked Customer Fravi/EasyOne
beas 9.3-002-063-000 / beas 9.3H-002-064-000
Beas\Production\APS > Zendesk id: 78427
Function:
Improve performance for these lists.


bde_terminal_poolinfo.psr


fert_aps_browse.psr


PAST: In the SQL statement of these windows many tables are linked. This can lead to a low retrieval of data.

NEW: The statements now use "with (nolock)" that makes the retrival faster and prevents tablelocking.
This changes only affects MSSQL. On HANA there is no such parameter nor is it necessary.
The problem is fixed. / Bug fixed. / Function is working properly.

Workaround TIP: Try adding a new field and...

Expected result: No error message should appear.
Beas\Production\Configurator
2019-08-07
24671
1
Web Configurator, Captions of Parameters are not displayed
beas 9.3-002-072-000 / beas 9.3H-002-073-000
Beas\Production\Configurator
If you don't define a caption for a parameter/input/dd, we will use the parameter's name as caption.



 

2019-07-19
24898
1
Mandatory Parameter in Product Configurator in combination with visibility rules is not working
beas 9.3-002-064-000 / beas 9.3H-002-064-000
Beas\Production\Configurator

In the Configuration wizard you can define the Parameter as mandatory.



Past:
If a visibility rule was inside, it was not possible to define this field as mandatory.
New:
It is possible to define visibility rules in combination with mandatory.
New definition:
It's only mandatory if check box activated and 
- the visibility rule returns true or 
- visibility rule is empty
Example:
Color is mandatory and only visible if radio_model is 1111
Here defined with DW Script command: if(rule,1,0)

 
TEST:

In configurator radio_model=1112

 
Result: Status is complete, because Color is not visible.

No change radio_model to 1111, "Color Mandatory" not defined

 
Result: Status is Draft, because mandatory field is visible.
 
If there is no visibility rule inside parameter "Color mandatory", the Status is always draft, if no value defined in this parameter.

prd_links2.psr, artikel_produktkonfigurator_detail.psr
 
Beas\Production\Factory data capture\Production Time
2019-07-19
19936
1
Down arrow key is not saving the partial quantity reported in quick input window
beas 9.3H-002-066-000 / beas 9.3-002-066-000
Beas\Production\Factory data capture\Production Time > Zendesk id: 77302

After pressing KeyUp/Down when editing a record, the changes were not executed in the right order.



window: fert_arbzeit_schnellerfassung.psr
 
Example Personnel entry
 
Barcode


Beas\Production\Factory data capture\Terminal
2019-07-26
25266
1
Beas Terminal Collective issue for production error HANA)
beas 9.3-002-070-000 / beas 9.3H-002-070-000
Beas\Production\Factory data capture\Terminal > Zendesk id: 87732
App "Collective issue" not working since beas 9.3 PL 2 HF 1 
(only HANA)

reservation_set_master.psr

Beas displayed an error message.

New: Fixed.

Workaround: None.
2019-07-26
25073
1
Login to terminal with keyboard does not work properly
beas 9.3-002-065-000 / beas 9.3H-002-065-000
Beas\Production\Factory data capture\Terminal > Zendesk id: 87058
Function: Terminal window
Login - Logout


 
If you try to make a login with same card number, it is not working. 

Current workaround:
insert wrong number, enter -> insert correct number.
2019-07-24
26181
1
HANA, Pool Report, SQL error when sorting/filter for columns Shortage/Operation Sequence
beas 9.3-002-068-000 / beas 9.3H-002-070-000
Beas\Production\Factory data capture\Terminal > Zendesk id: 88511

- PRIVAT - 

right click not working
Beas\Production\Factory data capture\Work Order Backflushing
2019-07-26
26171
1
Work Order Backflushing: Error in "Italy" localization
beas 9.3-002-068-000 / beas 9.3H-002-068-000
Beas\Production\Factory data capture\Work Order Backflushing > Zendesk id: 88530

Notes for SAP 9.3 PL 10

Italy localization

Function: Work order receipt / backflush
The system displays the following error message:

(wipjrnl35401)Error WIP accounting (costs depending on calculation schema) 38038 / 10
Costs depending on calculation schema could not be accounted because of wrong settings oder wrong values.
Error message: Error add document (-10) 256000511 - "VAT Allocation Date" is mandatory field. Enter a date., ReturnCode:-10

Reason is a new field in SAP - Journal Entries

Related to SAP Note:

Copy from Notes:

SAP intends to provide a patch or patches to solve the problem described. The section References below lists the relevant patches once they become available, and the Related Info content of relevant patches available in the SAP Support Portal, show this SAP Note. Be aware that these references can only be set at patch release date. SAP delivers patches only for selected releases at its own discretion, based on the business impact and the complexity of the implementation.
To allow for this requirement, the following changes are available in SAP Business One and SAP Business One, version for SAP HANA, in the Italy localization:
VAT Allocation Date
The field VAT Allocation Date is available for the following marketing documents, journal records and payments:
Journal Entry (follow the path Main Menu → Modules tab → Financials → Journal Entry)
Journal Voucher Entry (follow the path Main Menu → Modules tab → Financials → Journal Vouchers → Add Journal Entry to New Voucher)
A/R Down Payment Invoice, on the Accounting tab (follow the path Main Menu → Modules tab → Sales - A/R → A/R Down Payment Invoice)
A/R Invoice, on the Accounting tab (follow the path Main Menu → Modules tab → Sales - A/R → A/R Down Payment Invoice)
A/R Invoice + Payment, on the Accounting tab (follow the path Main Menu → Modules tab → Sales - A/R → A/R Invoice + Payment)
A/R Credit Memo, on the Accounting tab (follow the path Main Menu → Modules tab → Sales - A/R → A/R Credit Memo)
A/R Reserve Invoice, on the Accounting tab (follow the path Main Menu → Modules tab → Sales - A/R → A/R Reserve Invoice)
Document Generation Wizard, in step 2 of 8 when selecting A/R Invoice as the Target Document (follow the path Main Menu → Modules tab → Sales - A/R → Document Generation Wizard)
A/P Down Payment Invoice, on the Accounting tab (follow the path Main Menu → Modules tab → Purchasing - A/P → A/P Down Payment Invoice)
A/P Invoice, on the Accounting tab (follow the path Main Menu → Modules tab → Purchasing - A/P → A/P Invoice)
A/P Credit Memo, on the Accounting tab (follow the path Main Menu → Modules tab → Purchasing - A/P → A/P Credit Memo)
A/P Reserve Invoice, on the Accounting tab (follow the path Main Menu → Modules tab → Purchasing - A/P → A/P Reserve Invoice)
Incoming Payments (follow the path Main Menu → Modules tab → Banking → Incoming Payments → Incoming Payments)
Outgoing Payments (follow the path Main Menu → Modules tab → Banking → Outgoing Payments → Outgoing Payments)
VAT Allocation Date is completed by default with the Document Date for A/R documents, incoming payments, journal records and documents created by the Document Generation Wizard. VAT Allocation Date is blank by default for A/P documents and outgoing payments. VAT Allocation Date is amendable, even after invoices added.
VAT Allocation Date is a mandatory field for completion, with a corresponding error message if not completed. The VAT Allocation Date cannot be more than 15 days before the Posting Date of a document, payment or journal record. VAT Allocation Date and Posting Date of a document, payment or journal record must be in the same year.
Update information
When upgrading from a version of SAP Business One that does not feature VAT Allocation Dates to a version of SAP Business One that does feature VAT Allocation Dates, then VAT Allocation Date is automatically completed with the document Posting Date.


Related to Beas, the following areas:
- Time Receipt with Time Types and Account definition behind the Time TypeB- Cancellation or changes from Time Receipts
- Close work order / Clear Wip Account
- WIP Entries based on Calculation schema

New: 
We save  Vat Date in the created journal entry.
Date is same as the document date

Only if localization = IT and SAP Version is 9.3 PL 10 or newer



 
Example:
Calculation schema based journal entries

 
Beas\Production\Post calculation
2019-07-19
20382
1
Print postcalculation empty report
beas 9.3-002-065-000 / beas 9.3H-002-067-000
Beas\Production\Post calculation > Zendesk id: 77187
Post calculation - Report (Preview)  - Post calculation


 

Past
System asked for Full / Marginal Cost
New:
It us current setting


Lanugage German not working

Past:
With German language setting all field descriptions are empty in the report.

New:
Fixed.

Report for Planned/Actual Cost not working
Past:
If you made a print or preview for the current post calculation, the system asked 2x for parameter and displayed an empty report.

New:
Fixed. It displays the post calculation Report.

Attention:
A report for Planned/Actual Calculation does not exist.
The Report for "Actual Calculation" is displayed.

Window:
fert_naka_struktur.psr
fert_naka_soll_ist_struktur.psr

Report:
postcalculation1.rpt
Beas\Production\Sales order to Production order
2019-07-19
25100
1
SO2WO Error with SCM
beas 9.3H-002-064-000 / beas 9.3-002-064-000
Beas\Production\Sales order to Production order
Past: We had SQL errors on opening the "Storage-related" tab inside Sales Order to Production Order window.



window: fert_kdauftrag_zu_fertauftrag_bgrp.psr

The problem was related to SCM Scenario. 
The SCM scenario consists on having these tables installed on your schema:

 
The error was related to concat for strings, on mssql "||" brings problems , on HANA || is ok, this is why we created "<sqlca.concat>" that replaces this operators on HANA and MSSQL according on which is the correct one for each system.

Now: This window opens correctly having the SCM scenario installed.
 
Beas\Production\Workorder
2019-08-16
25310
1
Personnel calendar does not show all - Missing in the bottom - Screen resolution.
beas 9.3H-002-065-000 / beas 9.3-002-065-000
Beas\Production\Workorder > Zendesk id: 87797
Function: Personnel entry
Tab Shift model, Special shift, Attendance and Absence

Past:
If the window was displayed large, the calendar view was no longer displayed completely.

New:
Fixed.
bde_personal_rglarbzeiten, bde_personal_schichtp_browse, bde_personal_anwesenheit,bde_personal_abwzeit_browse
 
2019-07-26
24624
1
Issue window - batch related item more than one time
beas 9.3H-002-070-000 / beas 9.3-002-070-000
Beas\Production\Workorder > Zendesk id: 86351
We solved two errors in this ticket (both related with a bad calculation about the available quantity) for the selected item:

1. For normal items, when a reservation is involved and we've selected quantity more than one time (planned quantity) and the sum of the quantity is greater than the reserved quantity for one on the planned line, the available quantity for the next time that the same item appeared was not correct. This is not a problem if you have enough quantity, but you may not be able to select the material for other positions (even if you have enough stock).

2. For batch/serial items:
2.1. For serial items, if you select a serial (planned) it shouldn't be available to be selected in other positions when you select the same material.
2.2. For batches, the error is similar as in the first case (normal items) but per batches, even if the ticket was reported because when you select the whole quantity for a batch, the batch was still in the list available for other positions.


You need to do three basic tests (for normal item, serial, batches) and additional to try combinations with reservation and quantities:

Test 1:  /* normal items :: Quantity not well calculated */
// Example: 
//          1.- Create a WO with 2 positions (same material normal)
//          2.- Do a reservation for the first WO Position 10 pcs
//          At this moment Stock = 100 for RM on WHS 01
//          3.- Open MultiIssue window 
//          3.1.- Select wo first position                 (Available must be = 100)
//          3.2.- Select wo second position                (Available must be = 90 because there is 10 pcs reserved for other position)
//          3.3.- Assign 10 unit planned to the first WO   (Available must be = 90) (if you move to the second position, available must be 90 also)
//          3.4.- Assign 10 unit planned to the first WO   (Available must be = 80)
//          3.3.- Move to the second WO Position           (Available must be = 80) | before available is other quantity
//
//          Repeat the test with quantities greater and lower than the planned quantity
//
//         1.- do a reservation    2.- Open MultiIssue Window                  3.- Check Available field
//          WO/10/10    RM      Reserved 10             Planned 10 + Planned 10 (same warehouse)    (Available = 80)
//          WO/20/10    RM      Reserved  0                                                         (Available = 80) [before not right]
//

(The gif is too big and it's not completed but it will give you an idea about the right values)

window: reservation_set_master.psr


Test 2: /* serial items :: Serials Reserved/Planned for other positions must be not available here*/
// Example: 
//          1.- Create a WO with 2 positions (same material serial managed)
//          2.- Assing 1 unit planned to the first WO
//          3.- Select the second WO Position and check that the previously selected serial is not available to be selected againg
//
//          Repeat the test with reservation, allocation and so on...
//





Test 3: /* batch items :: Batches Reserved/Planned for other positions must be not available here*/
// Example: 
//          1.- Create a WO with 2 positions (same material batch managed)
//          2.- Assing 1 unit planned to the first WO
//          3.- Select the second WO Position and check that the previously selected batch quantity available is right or even the batch is no longer available to be selected againg 
//
//          Repeat the test with quantities, reservation, allocation and so on...
//
(The gif is too big and it's not completed but it will give you an idea about the right values)
Window: reservation_set_master.psr
2019-07-26
24970
1
Wrong position of field bin location
beas 9.3H-002-071-000 / beas 9.3-002-071-000
Beas\Production\Workorder

To reproduce this issue you have to follow these steps:


1. Open work order list+.
2. Click on new work order.
3. Click on new position.
4. Write one item with standard warehouse = bin manage warehouse and now you can reproduce the error:


fert_ftpos_edit.psr 

New: Fixed.
Correct place for bincode field is in area "Extended"

 

2019-07-26
24907
1
Edit BOM Qty in WO
beas 9.3-002-069-000 / beas 9.3H-002-069-000
Beas\Production\Workorder > Zendesk id: 86816
Function: Work order - edit Bill of Materials
Change Quantity

Past: The system didn't save the calculated Total Quantity.

New: Fixed.

fert_ftstlpos_browse.psr
2019-07-25
25265
1
Precalculation takes wrong cost price when raw material has a special price.
beas 9.3H-002-071-000 / beas 9.3-002-065-000
Beas\Production\Workorder > Zendesk id: 85249

Pre Calculation - Customer Special Price not working correctly together with Item Unit Group.


Past:
Precalculation - Prices wrong, if you defined Special prices with Unit Groups.

 

New:
We support Special Price List only if the Unit in special price list is the same as Warehouse Unit, and only if Item Price Unit and WareHouse Price Unit arethe same. If there is a difference between Price- and Warehouse Unit and a unit is defined in the price list, the system will ignore the special price list.

 
 

In SAP Period and Volume Discount and Special Prices for Business Partners you can deactivate the Price list or can define a Date area

Past:
The precalculation ignored this information

New
The precalculation check the infromation

Window: pk_struktur.psr, pk_material.psr
2019-07-19
24484
1
Info in Allocation window
beas 9.3H-002-065-000 / beas 9.3-002-065-000
Beas\Production\Workorder > Zendesk id: 82550
Function: Infofield in allocations

PAST: Beas displayed only the word "Allocation" in the field info. Therefore, after the allocation process, in the journal of entries it was not possible to see for which WO the material was allocated.

 

NEW: All WO are now inserted in the information field.
Restriction: If You select many WOs for allocation and the size of the field does not fit to insert all information, then only "Allocation" will be inserted.

See Inventory Transfer -> Remarks

 
2019-07-19
25056
1
Issue/Reservation/Allocation, Qty of column 'Allocation Warehouse' not calculated correctly
beas 9.3-002-063-000 / beas 9.3H-002-063-000
Beas\Production\Workorder
Function: Reservation window - Column Allocation warehouse.


reservation_set_master.psr

Past:
The value inside this column was wrong (view error).

New:
Fixed.
 

2019-07-19
24213
1
Beas Alternative Material: Not Working in Separate Bill of Materials with i-version
beas 9.3H-002-063-000 / beas 9.3-002-063-000
Beas\Production\Workorder > Zendesk id: 84869
The Beas alternative material was not working in the work order structure when the item has separate bill of materials.

window: fert_stuktur_browse.psr


For example, item structure used in the preview window:

 
2019-07-15
23809
1
Wrong date in combination with Hungarian date format
beas 9.3-002-064-000 / beas 9.3H-002-065-000
Beas\Production\Workorder > Zendesk id: 84009

Creating work order - Date format wrong, if Windows Date format has Hungarian format.



In this case  the date in created work orders is wrong.

This error was related to every date field which calendar drop down icon
 
Now: Problem fixed.

fert_fthaupt_edit.psr
2019-07-01
14929
1
WO Structure, Information on who created/modified a WO is not displayed
beas 9.3-002-060-000 / beas 9.3H-002-060-000
Beas\Production\Workorder
Function:

beas standalone
work order strucuture view

fert_stuktur_browse.psr

PAST: Beas displayed create and change user
But if a change user was not existing, it displayed nothing.

NEW: Beas displays only the creation user, if no change user existing and both, if the work order position was changed.

2019-06-28
24215
1
SAP Alternative Item Not Working in WO
beas 9.3H-002-060-000 / beas 9.3-002-060-000
Beas\Production\Workorder > Zendesk id: 84869
SAP Alternative Item is not working in WO if there is no reverse link.

Example to reproduce the problem:
1. Go to SAP item master data 
2. Right-click -> Alternative material
3. See window below:  

 
5. You cannot see the alternative item in item structure - Check the window below.

 
6. Create a WO - In here you can see the there is an alternative raw material 
7. Chose the alternative raw material by right-clicking.

 

8. Problem:   You cannot switch back to the original raw material and the alternative sign is gone away. Check window below:



I think the dropdown is working, but the visibility of icon is not.

REMARK!!!  IF THE SAP ALTERNATIVE HAS THE "REVERSE LINK" THEN IT'S WORKING CORRECTLY IN WO AS BEAS ALTERNATIVE DOES.

If you display alternative Material
a) don't display the alternative double (example: if reserve is existing)
b) don't display current item

2019-07-26
26078
1
Goods receipt Purchase: Not possible to receipt more then one batch for one purchase order line
beas 9.3H-002-067-000
Beas\Purchase > Zendesk id: 82929
Function: Beas - Goods receipt Purchase

Not possible to receipt more then one batch for one purchase order line

Example:
Order 1, line 1, Item A (batch related)

Goods receipt for order 1
insert line 1 two times for different batches

 
Past: The following error message was displayed:
(WGZZ08) Delivery could not be created : (-5002) Invalid value  [PDN1.BaseLine][line: 1]
Current Window: Goods receipt Purchase (program\mw_goodsreceiptpo_edit.psr) 

Same problem on WEB APP, new and old solution.

NEW: Fixed

Workaround
create 2 documents
Beas\Purchase\Goods receipt Purchase
2019-08-09
27526
1
PO incoming goods: Same base line with different Bin warehouse must work
beas 9.3H-002-073-000 / beas 9.3-002-073-000
Beas\Purchase\Goods receipt Purchase

Current limitation in Beas:


Incoming goods window (or WEB APP)
Batch related item
Receipt on SAP Bin managed warehouse with 2 different batches on same (or different) binlocation

This combination is currently not supported.
The following error message appears:

 (WGZZ08) Delivery could not be created : (-10) 1470000341 - Fully allocate item "yyy" to bin locations in warehouse "xx"

Workaround:
Create 2 documents.


mw_goodsreceiptpo_edit.psr
2019-07-30
25153
1
Goods Receipt Purchase, Warehouse of Provision Parts not assigned correctly
beas 9.3-002-071-000
Beas\Purchase\Goods receipt Purchase > Zendesk id: 86124
Based on:
Steps:
0) Config Wizard


1) Item Structure

2) Item Master Setup

3) Item BoM

4) Create a Purchase Order for the Main Assembly (here SP02_PROV)
5) Go to Purchase > Goods Receipt Purchase and follow the process

Result: Warehouse is not picked up correctly

 
Expected Result: Warehouse defined in BoM should be selected, if no Warehouse in BoM then Default Warehouse
Past: It used the warehouse from Item Mater Data
New: It is using the warehouse from Bill of Material



mw_wareneingang_beistellung.psr


Attention: 
This function is part of single incomig goods receipt and this window is in maintenance
2019-07-26
24423
1
QC Order, Search field 'Type' shows wrong information in the Dropdown
beas 9.3H-002-070-000 / beas 9.3-002-069-000
Beas\Quality Control
QC Order - Type field

Past: In QC Plan - Search it was possible to choose the type but the dropdown contained wrong information.

 
Reason: In this type of search mask only one dropdown is possible.
We will change this limitation in one of next versions

New:
It is not possible to create filter by button "Search". 
qs_qsfthaupt_browse.psr
 
Workaround:
Use right-mouse click ...


2019-07-17
14985
1
QC Windows open in the background after doing a Time Receipt
beas 9.3H-002-066-000 / beas 9.3-002-064-000
Beas\Quality Control > Zendesk id: 63864
Configuration wizzard - activate QC - order open Flag


Routing position with a QC order 

 
Past:
QC Window open in the background after doing a Time Receipt.
New:
Now the QC order window is in forground

window: fert_arbzeit_erfassen.psr
 
2019-07-05
23746
1
QC Samples - Search not working
beas 9.3-002-060-000 / beas 9.3H-002-056-000 / beas 9.3-002-056-000 / beas 9.3H-002-060-000
Beas\Quality Control
Function: Quality Control - Samples

Past:
Button "Search" --> There was a flag "Closed"  which was not working.

New:
The list shows by default only open entries. If you uncheck the "only open", both, open and closed samples are shown.


 
qs_qsftmessung_report.psr
 
2019-06-27
24143
1
QC Order Batch block error
beas 9.3H-002-061-000
Beas\Quality Control > Zendesk id: 84691

Error on clicking on Batch Block button

qs_qsfthaupt_edit.psr
error:
<empty>)Error executing Procedure: SQLSTATE = S1000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;260 invalid column name: DISTNUMBER: line 1 col 69 (at pos 68): Call update "OBTN" set "Status"='1' where "ItemCode"=N...

- open a QC order with batch item
and click on Batch Block button
Beas\Sales\Precalculation
2019-08-12
24410
1
Precalculation, Setup Times in Subassemblies divided by Qty of Parent Item
beas 9.3H-002-073-000 / beas 9.3-002-073-000
Beas\Sales\Precalculation > Zendesk id: 84810

The setup time must be applied one time per lot size only and it doesn't depend on the number of produced items.


There were two errors:
  1 . When changing the number of units to produce (View per...) we multipled the time (T/Min) per the new amount to produce. This was incorrect because we set up machine 1 time only (we need to exclude the setup time from this multiplication and add it to the result).
  2 . Internally we were dividing the setup time to the quantity produced in the parent.


pk_struktur.psr
2019-07-25
20470
1
Wrong routing-position in precalculation window
beas 9.3H-002-050-000 / beas 9.3H-002-069-000 / beas 9.3-002-050-000 / beas 9.3-002-069-000
Beas\Sales\Precalculation > Zendesk id: 71526
Function:

Precalculation, displaying link from BOM to operation.

window: pk_struktur.psr

PAST: The link from a BOM position to an operation was wrong if the operation sequence was changed from the default value to an own value.
In that case the original (internal) number was shown. Additionally, when you opened the BOM position, the displayed routing link was also incorrect.
When changing the id in the routing position, then the link in the bom was not updated. Same when the id changed when using drag'n drop.

NEW: Fixed. The link from BOM to operation will now be updated in all cases.


2019-07-11
24340
1
Wrong behaviour of calculation schema - result fields in Configuration wizard
beas 9.3-002-064-000 / beas 9.3H-002-064-000
Beas\Sales\Precalculation > Zendesk id: 84687

Configuration wizard  > Calculation > Calculation schema:

You can define up to 10 names for saving result:


In calculation schema object you can define the name.

Past: Only Material surcharge and production surcharge were visible, but not customized settings.
New: It is working correctly. You can choose every name, which you defined in the Configuration wizard.

pk_typen_edit.psr

Pre calculation > calculation schema area > edit entry:

Before: All settings were loaded from database.
New: Now it is using internal setup cache. The window opens a little faster.

 
pk_gesamtkosten.psr
 
In debug window (level 2) you can see the effect: when opening the window the first time, it's reading the setup without access to the database.

 
If you open the window the second time, the system does not read it from the database again.

 

Beas\Service\Maintenance Orders
2019-07-10
25326
1
Maintenance Plan, Order of fields
beas 9.3H-002-064-000 / beas 9.3-002-064-000
Beas\Service\Maintenance Orders > Zendesk id: 86514

Maintenance Plan window


maintenance_plan_edit.psr

Past:
The key "TAB" did not switch to the correct next field.

New:
Order of fields is correct.
2019-07-26
27473
1
System error uploading a debug of a time receipt to the portal
beas 9.3H-002-069-000 / beas 9.3-002-069-000
Beas\System and Other

Debug window upload:      


Past:
In certain situations the following error message appeared:

Systemerror 2 Null object reference at line 50 in function wf_upload of object w_beas_debug.

Window:w_beas_debug

Object:  w_beas_debug  Event:  wf_upload Line 50


New: Fixed.
2019-07-09
22885
1
Right-mouse click on title - search by number fields not working
beas 9.3H-002-063-000 / beas 9.3-002-063-000
Beas\System and Other > Zendesk id: 79573

Click on the title of number fields with a yellow arrow:

 

fert_kdauftrag_zu_fertauftrag.psr

Past:
There was only "equal to", but not "bigger" or "smaller".
(related only to windows with the complete list loaded, for example "Sales order to Production order")

New:
Now you can choose "bigger" and "smaller", as well.
Beas\Usability\beas usability extension (B1UP)
2019-08-09
27763
1
Beas usability extensions - validation with beas UF - block event malfunction
beas 9.3-002-073-000 / beas 9.3H-002-073-000
Beas\Usability\beas usability extension (B1UP) > Zendesk id: 89178
1. Go to item master data - I-version.
2. Open Beas usability extensions - item placement tool - add new row for UDF1 for example.
3. Open Beas usability extensions - add validation configuration with the configuration below, 
important is the Beas-UF validation



Past:
In this case updating the form should not be possible when UDF value is not "1234". Yet, it is still possible.  Message is going to pop up but block event does not seem to work, updating the form is possible.

New:
Problem solved.
The system blocks the event.
2019-07-26
25996
1
B1UX - delete data in overview: SQL error
beas 9.3H-002-067-000 / beas 9.3-002-067-000
Beas\Usability\beas usability extension (B1UP)
SQL query problem:

1. Open workorder - right mouse click - B1UX overview


2. Try to delete any row
 
Window sys_trigger_browse.psr

Now: Fixed.

2019-07-19
20703
1
Beas Usability Extension, Import on HANA not working
beas 9.3-002-066-000
Beas\Usability\beas usability extension (B1UP) > Zendesk id: 78262
Function: Beas Usability Extension, 
Import on HANA not working.

window: sys_trigger_browse
2019-07-16
25227
1
HANA Syntax Error: Beas Usability Extension at Validation Edit
beas 9.3H-002-067-000 / beas 9.3-002-067-000
Beas\Usability\beas usability extension (B1UP) > Zendesk id: 80837
This is a bug related with a Syntax error in HANA version when attempting to open a validation in Beas usability extension function.


We had the situation in Beas Usability Extension Overview when you tried to "edit" any row:



2. Edit the Validation line and the system reports the following error:




window: sys_button_edit.psr

Beas\Warehouse Management
2019-07-19
24884
1
BSL, e_bindropdownbsl Customizations not applied to dropdown fields
beas 9.3-002-063-000
Beas\Warehouse Management > Zendesk id: 85416
Function: Manual Receipt - 
Choose Bin Location

With Beas 9.3 PL 2 we support SAP Bin management. With this new function we support another customization. 

Now you must use a BSL command and not a SQL command to define the Dropdown. For more details see our documentation.

Past:
Function was not working.

New:
Function is working.


Workaround:
1. Open Beas software\beas\program\binmanagement.src
2. Change line 19 from

if <var:e_bindropdown> <> "" or <e_bindropdownbsl> <> "" then
  return success
end if

to
if <e_bindropdownbsl> <> "" then
  return success
end if
2019-07-17
25476
1
Item change event after rowfocus change
beas 9.3-002-066-000 / beas 9.3H-002-066-000
Beas\Warehouse Management

If you change a field and click on cursor up/down in a multiline edit window, the following order of events are found in beas script and beas usability:


itemchange
rowfocuschange
itemchanged <- here most of scripts inside

Problem:
The new line has the focus. If you check the entry, you must check first, in which line the user changed anything. Currently you can see this in variable <dwo-row>. But if you forget to check this, the result is wrong.


New:
The system executes the events in the following order:
itemchange -> itemchanged - rowfocuschange

If you cancel the process in itemchanged (for example in beas script or usability package), the system cancels the rowfocus process.


2019-07-17
25995
1
Systemerror 2 Null object reference at line 60 in function of_resizechild of object ue_beasgui.
beas 9.3H-002-065-000 / beas 9.3-002-065-000
Beas\Warehouse Management

The following system error message is displayed randomly:


Systemerror 2 Null object reference at line 60 in function of_resizechild of object ue_beasgui.
Window:ue_beasgui

New: Fixed.
2019-07-16
25355
1
Error production - Stock transfer
beas 9.3-002-064-000 / beas 9.3H-002-064-000
Beas\Warehouse Management > Zendesk id: 87011

You can create a transfer document related to a work order.


mw_manuell_buchen.psr

In the following workflow the program was working wrong.

1. Create transfer for a work order position (Bill of Material = 0).
2. Don't close the window.
3. Create a transfer document in same window, which is not related to a work order.

Past:
In this case the system linked the document to the last work order.

New:
Fixed.

Effects:
Only visual effects. No effects to valuations or other processes
2019-08-09
24837
1
Terminal picking list app cannot do a delivery with multibranch
beas 9.3H-002-063-000
Beas\WEB
Past: The delivery for multi-branches database was not working because the branch was not sent to the SAP delivery document.

New: Now it is possible to create a Delivery from a Sales order based on Reservations.
shipping_delivery_header.psr
2019-08-09
21857
1
WEB APP Transfer
beas 9.3H-002-073-000 / beas 9.3-002-073-000
Beas\WEB

Stock transfer web app

The items will be limited to items with stock in the selected source warehouse.

2019-08-09
27809
1
WEB2.1 - Warehouse stock - does not work properly
beas 9.3H-002-074-000 / beas 9.3-002-074-000
Beas\WEB > Zendesk id: 88908
Warehouse Stock app:

Past:
Page "Inventory" was empty if you choose a Bin managed warehouse.

New: Fixed.
2019-07-16
24117
1
Web 2.1 - create own app SQL error
beas 9.3-002-065-000 / beas 9.3H-002-065-000 / beas 9.3H-002-054-000
Beas\WEB > Zendesk id: 84726

WEB APP Development window (only HANA)



 
 
Produce error while updating

**^Error while Display Report: SQLSTATE = S1000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General 
error;260 invalid column name: statusId

Fixed.

Error:
Can't set field benzingkey in datawindow dw_1 (program\webwindow_edit.psr).

Fixed