Fixed
Beas
2019-01-29
11664
1
Human Resources, Personnel, Review the creation of Master Data (and the auto linking process from SAP HR Master Data)
beas 9.2-005-043-000 / beas 9.2H-005-043-000 / beas 9.3-000-016 / beas 9.2H-005-048-000
Beas
beas has the possibility to import human resources with the data integration hub. In this import it is possible
to reference to an entry that exists in the SAP table for employes (empid). If there is no reference, beas trys to find
a reference automatically, or generates an new entry if there is no entry on SAP side.
to reference to an entry that exists in the SAP table for employes (empid). If there is no reference, beas trys to find
a reference automatically, or generates an new entry if there is no entry on SAP side.
If the import file contained records with same name and/or reference it could happen, that more than one entry on beas side
was linked to the same record in SAP.
Editing or copying data in personell administration could also lead into wrong links to the SAP table.
was linked to the same record in SAP.
Editing or copying data in personell administration could also lead into wrong links to the SAP table.
All this problems are solved now and it is not possible anymore that more than one record on beas is linked to the corresponding SAP table.
bde_personal_edit.psr
2019-01-23
12479
1
Maximizing of beas windows is not working in SAP 9.3
beas 9.3-000-022-000 / beas 9.3H-000-022-000 / beas 9.2-005-048-000 / beas 9.2H-005-048-000
Beas > Zendesk id: 58697
only beas 9.3 PL 0 BETA
Past:
if you maximized a beas window inside SAP, only the Window border was maximized, but not the window itself.
New: Fixed.
2019-01-22
12061
1
Material Issue, Creation/Deletion of entries in BEAS_PLANDOCUMENT and BEAS_PLANDOCUMENT_LINE
beas 9.2-005-046-000 / beas 9.2H-005-046-000 / beas 9.3-000-019-000 / beas 9.3H-000-019-000
Beas > Zendesk id: 57163
Past:
In the "material issue" window there could be a problem in some special cases, when two people
start the window at the same time (it need not be the same workorder).
start the window at the same time (it need not be the same workorder).
Then it could happen that two users got the same document number and positions from one
or the other got lost or were wrong.
or the other got lost or were wrong.
Now: This Problem is fixed.
reservation_set_source.psr
2019-01-22
12574
1
HANA, Inventory, Initial Stock/Annual Inventory Count/Regular Inventory, Forms broken & SQL error
beas 9.2H-005-048-000
Beas
QLSTATE = S1000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;339 invalid number: not a valid number string 'Template' -1/339:
select count(*) from beas_inventory_header where inventorytyp=1 and coalesce('Template',0)=1
past: SQL error when creating a new record on the initial stock window;
also when adding more columns to the initial stock, annual Inventory count and Regular inventory, those columns were not displayed.
also when adding more columns to the initial stock, annual Inventory count and Regular inventory, those columns were not displayed.
now: error fixed, SQL query updated on with the correct HANA syntax, and now those windows keep the columns added to them
mw_inventory_header_browse.psr
2019-01-22
12489
1
reservation / material issue - HANA
beas 9.2H-005-047-000
Beas
(<empty>)(sql2ds2) Error while generating datastore. Error Code SQLSTATE = S1000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;260 invalid column name: R.BATCHNUM: line 1 col 1103 (at pos 1102)
past:
An error came up when opening a reservation window or a Material Issue window inside the work orders window.
An error came up when opening a reservation window or a Material Issue window inside the work orders window.
Now: this is fixed; BAD query fieldname
2018-12-17
12065
1
Creating PO from Material Requirements screen will insert the wrong Delivery Date in the PO
beas 9.2-005-047-000 / beas 9.3-000-019-000 / beas 9.3H-000-019-000
Beas > Zendesk id: 58129
Past: When you create a purchase order, it could happen, depending on the window settings for date, that the delivery date that was inserted was wrong.
Now: this issue is fixed, and the correct date will be taken
reservation_set_source.psr
2018-12-17
12136
1
WebApps, wo_logonlogoff, Setup DataWindow does not have update capability
beas 9.3-000-018-000 / beas 9.3H-000-018-000 / beas 9.2-005-046-000 / beas 9.2H-005-046-000
Beas > Zendesk id: 58361
The windows to edit the web apps and the setup for the web apps become read only after update the length of one of the fields.
After this the windows are update-able again.
2018-12-17
12148
1
beas installer installed a wrong "beas on the web" link
beas 9.2-005-046 / beas 9.2H-005-046 / beas 9.3-000-018 / beas 9.3H-000-018
Beas
PAST:
If you installed beas on the client, the installer inserted an additional link:"beas on the web"
The link behind was wrong
NOW:
In future beas don't insert this link, and the old link will be deleted
2018-12-17
12291
1
Product configurator: If you don't click on prices/result the prices are not calculated
beas 9.3-000-019-000 / beas 9.3H-000-019-000 / beas 9.2-005-046-005 / beas 9.2H-005-046-005
Beas > Zendesk id: 46153
Product configurator
Before than this modification if you don't click on prices/result then the prices were not calculated
2018-12-17
12485
1
Product configurator: on HANA environment, when you click on button "test" you get following error message: (pk0035) not enough lines in product
beas 9.3-000-019 / beas 9.3H-000-019 / beas 9.2-005-047-000 / beas 9.2H-005-047-000
Beas > Zendesk id: 58957
Environment: This error applies only to HANA versions
Previous: Sometimes in the productConfigurator module, when you click on button "test" you get following error message:(pk0035) not enough lines in product configurator coding or title line missing,
Now: Bug fixed, this problem is related of how HANA is retrieven record of table beas_oitm_produktkonfigurator, by default we don't have an order by defined in the query and SAP HANA not always was sending records ordered by primary key.
We add internally an explicit order by and now program is working in the right way.
2018-12-17
12502
1
Cancellation of an allocation does not work fine
beas 9.3-000-020-000 / beas 9.3H-000-020-000 / beas 9.2-005-047-005 / beas 9.2H-005-047-005
Beas > Zendesk id: 58622
The cancellation of allocation for normal items was an error and system did it twice into the "beas_reservation_line" table.
After this patch the quantity is discounted one time only.
In the animation, you can see that we had 25 pcs allocated for rm01 and after cancel 1 pcs then the allocated quantity is updated to 24 (before this patch was 23).
mw_manuell_buchen.psr
2018-12-17
11987
1
Configurator: Short and Long Description will not updated after the first time.
beas 9.3-000-019-000 / beas 9.3H-000-019-000 / beas 9.2-005-046-005 / beas 9.2H-005-046-005
Beas
If you create a new configuration, the Short and Long Description was updated only the first time.
After this modification, if you back to the options and do any changes the Brief Description and Description are updated again.
prd_links2.psr
2018-12-17
12321
1
BeasScript: Error accesing ProjectCode
beas 9.2-005-047 / beas 9.2H-005-047 / beas 9.3-000-019 / beas 9.3H-000-019
Beas
Previous: If we create a receipt document via beasScript and accounts defined for the item has a project assigned then we had following error:
(**)Type mismatch accessing external object property projectcode at line 816 in function of_receiptwo of object ue_reservation. /
Now: This bug is fixed and system is setting right project code information
2018-12-17
12023
1
db.ini, BEAS_CAFT_VARIANTE creating a new database
beas 9.2-005-046-000 / beas 9.2H-005-046-000
Beas
only beas 9.2 PL 5 Build 35- 45
if you create a new database, you have follow error message
Error executing Procedure: SQLSTATE = S0021
[Microsoft][ODBC SQL Server Driver][SQL Server]Column names in each table must be unique. Column name 'ManualChanged' in table 'BEAS_CAFT_VARIANTE' is specified more than once.: Exec create table dbo.BEAS_CAFT_VARIANTE (
[VARIANTE] ...
[Microsoft][ODBC SQL Server Driver][SQL Server]Column names in each table must be unique. Column name 'ManualChanged' in table 'BEAS_CAFT_VARIANTE' is specified more than once.: Exec create table dbo.BEAS_CAFT_VARIANTE (
[VARIANTE] ...
Fixed.
Workaround:
open
c:\program files (x86)\beas software\beas\program\db.ini with administration right in notepad or other text editor
Search for "ManualCanched"
You see the definition from table "BEAS_CAFT_VARIANTE"
The definition "ManualChaged" is existing 2 times. Please delete one of both lines and start database test again
table=BEAS_CAFT_VARIANTE
column=BEAS_CAFT_VARIANTE=VARIANTE=int not null
column=BEAS_CAFT_VARIANTE=Parameter=char(50) not null
column=BEAS_CAFT_VARIANTE=ManualChanged=int
column=BEAS_CAFT_VARIANTE=ParameterType=char(1)
column=BEAS_CAFT_VARIANTE=BEZEICHNUNG=varchar(512)
column=BEAS_CAFT_VARIANTE=INHALT=text
column=BEAS_CAFT_VARIANTE=ManualChanged=int
primary=BEAS_CAFT_VARIANTE=VARIANTE,Parameter
2018-06-27
12633
1
If P&L account parameter was activated for production document, cost center is not transferred into journal entries of the production goods receipt document.
beas 9.2-005-048-000 / beas 9.2H-005-048-000
Beas
Only affect DB where P&L account at production order document was activated.
After you do a manual good receipt of a finished good then the cost center of the material which was receipted can be found in the goods issue document but unfortunately not in the journal booking.
After this patch the distribution rule is filled into the journal entry.
2018-06-22
12508
1
Product Configurator - Problem with variable type definition
beas 9.3-000-021-000 / beas 9.3H-000-021-000 / beas 9.2H-005-047-000
Beas > Zendesk id: 58956
Formula in Configurator
if a placeholder not defined, you can have problem
MSSQL:
[myParameter] + 1 create sql statement '' + 1, Result = 1
In HANA you become an error message
Problem:
if a parameter is empty, beas don't know, if this a string or number
you've different posibilities now
1. Convert this to a number
[myParameter,#0] +1
[myParameter,dbnum(3)] + 1
2. Declare the parameter as Number
in both variants beas replace the parameter with 0 and not with empty string and then it's working in HANA too.
Generel it's good, if you define the type of a parameter, because the automatic declaration is not always clear.
0 or number = Number
empty or not number = String
empty or not number = String
Example
You define a description with
[myparameter] + 'hello world'
if myparameter is empty or a string, then you don't have a problem
but is myparameter is a number, you create a sql error
if you define myparameter as a string or you insert the format information "[myparameter,dbstring]" or you use the format
'[myparameter]', then you don't have a problem. But a clear definition is always mandatory.
Beas\Production\Factory data capture\Work Order Backflushing
2018-06-22
11092
1
Reservation: Using the “All pre-assign” button, and automatic batch selection parameter, system allows reserving quantity that is already assigned for items managed by batch.
beas 9.3-000-019-000 / beas 9.3H-000-019-000 / beas 9.2-005-046-005 / beas 9.2H-005-048-000
Beas\Production\Factory data capture\Work Order Backflushing > Zendesk id: 55975
Reservation: Using the “All pre-assigned†button, and automatic batch selection parameter, system allows reserving quantity that is already assigned for items managed by batch.
If you press the button "All pre-assign" and automatic batch selection parameter was activated, then the system allows reserving already reserved positions for the same batch..
So it´s possible for the user to reserve same batch on several work order.
Now is fixed.
