New
2019-12-13
21417
2
Calculation: Work with Production UoM
beas 9.3-003-024-000 / beas 9.3H-003-024-000
Beas > Zendesk id: 78975
Function/Area: Precalculation setup window
Working with different Production Unit and Inventory Unit

New: Now it's possible to 
- calculate a item in Inventory UoM or Production UoM
- Define Lot Size in Inventory and Production UoM
- Define Lot size and View by with decimal places. Example: Lot size = 1.522 kg


Example
Toothpaste 200 mg. Inventory UoM is Pcs and Production UoM is kg

In Tab Calculation it's possible to define Calculation Lot size in Inventory or Production UoM
artikel_edit.psr
 
Calculation Button 
You can define the Lot size in Production or Inventory UoM. Default is Production UoM

pk_new.psr

The "Display per" is in same unit as the Unit, which you define in "Lot Size" 
You can define Lot size and Display per with decimal places.
 

In Pre calculation the system displays all Lot sizes and View per information with the correct count of decimal places.
The view is in the unit in which you defined the Lot size in preview window.
The number in "view per" is the number in same UoM (Inventory UoM or production UoM)
pk_struktur.psr
 
 
If you create a new calculation from Sales AR / Calculation, you can define the unit in tab "Valuation"
pk_haupt_edit.psr
 
If you change to "Inventory UoM", the system automatically calculates the lot size based on Production UoM.
You can switch between both units every time without losing Lot size Information.

In Calculation there is a new yellow arrow left of lot size. If you click on it, you can change the lot size or UoM directly.


Example: Same calculation with "Pcs" as unit.

In Calculation > Scale Price the system displays the result in the same unit as defined in Lot size.
pk_haupt_staffelpreis.psr

Beas supports UoM Group for factor calculation between Inventory UoM and Production UoM. 
For this the UoM Group is defined in the item master data.
pk_material_s2.psr

 
But not changeable. Only in SAP Item Master Data window you can change the UoM Group.

Pre Calculation - Bill of Materials - Tab "Price"
New: Now the system displays the UoM, in which you have to define the Scale quantity.
The Unit is always the Inventory UoM of this Material.
pk_material.psr
  
 
Post calculation
The post calculation always uses Inventory Unit.
Past: It displayed the first entry in Production UoM with the quantity in Inventory UoM.  
New: Fixed. Now the system always displays the first entry quantity in Inventory UoM. 

 fert_naka_struktur.psr, fert_naka_soll_ist_struktur.psr

Beas\Administration\Makros and Crystal Report
2019-12-19
33424
2
Beas Bin location window - better refresh
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Administration\Makros and Crystal Report
Function/Area: Warehouse management - Open documents (Beas Bin Warehouse) - open entry

Before: If you resized the Beas bin window, the window flashed 2x.
If you clicked in a field (Bin location, Range, Quantity, the list in top flashed or was not visible.
.

Now:
Problem solved. View is stable.
bin_struktur_batchbooking.psr
Beas\Administration\System Initialization
2019-12-17
31694
2
Validation of "enable transaction notification" in General settings
beas 9.3-003-022-000 / beas 9.3H-003-022-000
Beas\Administration\System Initialization
Function/Area: General Settings

NEW: If Transaction Notification is not enabled, you should receive this alert and beas should not start:

 
2019-11-29
30661
2
Activity log missing in BOM structure
beas 9.3-003-021-000 / beas 9.3H-003-021-000
Beas\Administration\System Initialization > Zendesk id: 93094
Function/Area: Bill of materials structure

Past:
Open the Bill of Materials for an Item. 
On the extended tab, update the "Date to" field from a date to empty


 
and right cick on Activity Log. 

In the past you couldn't see a new record with the New Content Field displayed an empty field.


Window: system_aenderung_browse.psr

Now: You can see the record that was created.

 
2020-02-18
22189
2
Consider calculation MRP not working as described in the documentation
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\MRP > Zendesk id: 80730
Function/ Area: MRP

MRP ignored Breakdown flag calculation.

Example:
Precalculation with order- and stock-related item and phantom item

 
If you create a work order, the system inserts sub position for order-related item, but not stock-related item.

 
PAST:
In precalculation the system always performed the complete calculation.

NEW:
All material positions not related to stock-related assembly are displayed in the same way as in the past:
Order-related, linked to Calculation


But Material from storage-related items are related to item master data from this storage-related item. The system does not read any information from the precalculation
Example: RM_B is part of storage-related assembly

 
If stock is available for the storage-related item, the old variant ignored this
Now the system does not ignore this.

Example:
We create a work order for the storage related item
Result: Issue from Calculation and Receipt from work order 1386

 
Material RM_B
Now we see only the work order bill of material position
Nothing about the calculation, because it's stock related

 



Additional changes
-----------------------------------------

Calculation to work order
* Error in beas 9.3 PL 3 HF 0:
Order related sub structures not visible in work order structure view. Fixed. Workaround: Database test

* faster
Optimized many sql statements

* BoM Matchcode field not transfered from Calculation BoM to Work order. Fixed.


2020-02-18
20066
2
Enable UOM group at Work order BOM
beas 9.3H-003-021-000 / beas 9.3-003-021-000
Beas\Production > Zendesk id: 73622
Function/Area: Bill of Materials

Past: 
- Changing Unit: Didn't calculate factor
- "Per" didn't display correct decimal places

New:
- If you change UoM, the System calculates the Quantity and the factor automatically. 
  (only possible, if conversion factor is defined)
  The new Quantity is based on the current consumption unit.
- "Per" is displayed in consumption unit of assembly with correct decimal places.

Function/Area: Pre Calculation Bill of Material
Past: Fields not in same place as in Item Master data or Work order
New: 
- Fields on same place
- If you change UoM, the System calculates Quantity and the factor automatically 
  (only possible, if conversion factor is defined)
  The new Quantity is based on the current consumption unit.

Function/Area: Work order Bill of Materials

New:
It's possible to change the Unit of Measurement


If the UoM is changed, the program calculates the Quantity based on the new UoM

Example:

Conversion: 1 TPcs =1000 Pcs
Old Qty = 2000 Pcs

Change UoM to TPcs. The System display Quantity = 2 TPcs
If the Quantity in TPcs is changed, the system calculate the Consumption unit and from this the warehouse unit
If length/width/height, densitiy or item code self is changed, the base quantity is always the quantity in consumption unit and the system calculate always the quantity in the Bom unit and Warehouse unit

The Fixed quantity Surcharge and calculated scrap will be displayed in the same unit.

If different units are defined, the UoM Field is green.
if the Unit field does not have the focus and the mouse is over this field, the system displays all quantities in all UoMs

fert_ftstlpos_edit.psr


You can see this Input Unit only in
- Production Bill of Material edit window
- Production Bill of Material List Window



Considerations
- New work order from Master Data or Calculation:
  The system ignores the Input-Unit which you can define in Master Data > Bill of Materials, if the unit not defined in the Unit Group Definition
- In work order Bill of Mateiral you can choose only UoM if a UoM Group defined in item master data and you can only choose UoMs which are defined in this UoM Group.


 
This Input UoM is only changeable if no receipt/issue document exists on this position and only if the work order is changeable.
fert_ftstlpos_browse.psr

If you change the quantity with Beas script or import hub, the system overwrites the Input Unit with Consumption unit.
If you refresh the work order, the system overwrites the Input Unit with Consumption unit.

In Work order Bill of Materials you can activate the Input Unit via window settings. But this fields is not changeable.

 
 If you change the quantity in Consumption unit, the system overwrites the Input unit with Consumption unit.

 
DATABASE
This input unit are saved in new field: BEAS_FTSTL.INPUT_QTY, BEAS_FTSTL.INPUT_FACTOR, BEAS_FTSTL.INPUT_UNIT
Internal Beas does not use these fields. These are only information fields. 
IMPORT / DataIntegration Hub
Here it's not possible to choose these new fields.
BSL Beas Service Layer
The fields are available .
WorkorderBom/InputQuantity, InputUnit, InputFactor
Additional the objects: UnitGroup, UnitGroupLines and UoMConversion
VIEWS
The fields is not available.
Conversion Formula
The system checks the conversion.

From Input unit to Consumption Unit
If the conversion does not exist, the system searches for "From Consumption Unit" to "Input Unit" and calculates formula with 1:[formula]
If it does not exist, the system checks the Unit of Measurement in both variants and generates the correct formula.

 




Beas\Production\Configurator
2020-01-03
32908
2
Web Configurator error: Discount groups are considered at Sales order creation
beas 9.3-003-022-000 / beas 9.3H-003-022-000
Beas\Production\Configurator > Zendesk id: 96303
Function / Area: Web Product Configurator

After you confirm the cart, you create the sales order, but the "configurable could have special discounts", which should be applied when the order is created:




 
Before: The discounts groups were ignored. 

After: We read the discounts groups and we create the sales order by applying them the right discount percent (just percent discount is applied).
Beas\Sales\Precalculation
2019-12-30
28917
2
Scrap of Material % - new setting
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Sales\Precalculation > Zendesk id: 91798
In Routing position you can define "Scrap of Material"
This calculate a scrap for linked material positions

artikel_arbplanpos_edit .psr

Past:
It was not working in same way in all different places

New:
1. Fixed.
2. You 

Function/Area: Routing position with "Scrap of material %"
in combination with linked Material position to Routing position.

Different results in work order and precalculation
Current in analysis, which variant is working correctly.

New: We have a new parameter in the Configuration wizard to define the behavior of this field:

 
This parameter is a dropdown with three different types of behavior:
1. Linked Material only -> Just the linked materials are affected by the scrap %
2. From first to the last linked material -> All materials bellow any linked material are affected.
3. All materials are affected.

Examples:

[Example 01] Set configuration to "Linked Material only" and open precalculation:

(notice linked material only is affected)


[Example 02] Set configuration to "Bellow the last linked material" and open precalculation:

(notice all materials under the last linked material and liked materials are affected)


[Example 03] Set configuration to "All Materials" and open precalculation:

(notice all materials are affected)



2019-12-30
33536
2
BSL: Create Document - Better Error handling
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\System and Other
Function/Area: Creating document via BSL

Example:
#define ls_json
{
"DocNumber": 152,
"CardCode": "C40003",
"RetrievalDocument": true,
"DocumentLines": [
{
"ItemCode": "FP",
"WhsCode": "01",
"BaseType": "17",
"BaseDocEntry": 152,
"BaseLineNumber": 1,
"Quantity": 1,
},
],
}
#end
instance bsl b
b.post=SalesDelivery=<ls_json>
messagebox=<b.ret_code> <b.ret_text> <b.ret_value>
destroy=b

Past:
It displayed an error message: "Error in JSON..." without additional information and generated the document.

New:
It display error message with more details. 
In this example: () Error in Json String: Error:Expect key name with " but not found: (Pos 217..... ber": 1, "Qauntity": 1, <-- except key name after comma
and don't create the document.
2019-12-07
33532
2
View BEASV_WORKORDER_BOM very slow in large databases
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\System and Other
Function/Area: View BEASV_WORKORDER_BOM
The view BEASV_WORKORDER_BOM reads booked quantity for Bill of Materials directly from Table IGE1/IGN1. This is very slow in big database.

Past:
Very slow. B1UP Dashboard was too slow.

New:
Fast, in large database up to 20 times faster.

Example:
select QUANTITYBOOKED,* from "BEASV_WORKORDER_BOM" where DocEntry=1385 and QUANTITYBOOKED <> 0
Beas\Warehouse Management
2019-12-19
23994
2
WMS: Proposal PickList
beas 9.3H-003-025-000 / beas 9.3-003-025-000
Beas\Warehouse Management
Function: WMS Proposal Picking

PREREQUISITES: To ensure that complete functionality is working correctly, it is mandatory that "PmxSboNotificationListener" is running on the WMS side and "Common interface" from beas side is also running

NEW FUNCTIONALITY: Beas now is able to generate WMS proposal pickings.

Functionality is implemented inside "Material requirements" screen. For companies where WMS is installed a new button will appear:


 
Picking proposal generation in current version is working for a complete work order position and full quantitites.
Material requirements window can be opened from many diferent places and can also be opened for more than one work order position.
When proposal picking process is executed for several work order positions, the system will create proposal picking for all components displayed in the screen. But if any component is already generated, the process will be stopped and no proposal picking will be generated.

To be able to generate picking proposal is mandatoy that the user define a "WMS Production line" for the work order position:



To create Beas production line, please refer to WMS documentation of how to do this definition.

When user execute the "picking proposal" functionality WMS always will send and answer per each petition, the answer is saved in the protocol of the work order. If proposal picking is not created for any reason we will have a message like this.


 

If proposal is created without any issue, the result will be similar to this:



 
After the proposal picking is created in the system you have to follow the workflow defined in WMS.

LIMITATIONS: After the user finishes the picking process, WMS currently is not creating a BEAS reservation for the picked materials. This means that those materials can be consumed by any other process in the system. This logic will be implemented in future versions of WMS to generate this information in BEAS. When this functionality is finished, a reservation will be generated automatically for each picked material in the Defined production line for Beas.


 

Error/Messages codes:

wms001^WMS Production Line NOT defined for WO: <wo/pos>  -> Production is not defined for current work order position. You have to define this value inside tab "link" inside work order position master data

wms002^Proposal Picking is pending to be processed for WO: <wo/pos> --> The proposal picking was already sent to WMS but WMS still did not process this message. typically this error happen when "PmxSboNotificationListener" is not started on WMS server

wms003^Proposal Picking already exists for WO: <wo/pos> --> This happens when picking proposal is already created in WMS.

wms004^No pending lines to generate a picking proposal --> You try to generate a picking proposal but all lines are already created as proposal picking

wms005^Proposal Picking sent --> You have this message after beas send the petition to WMS to generate a picking proposal



BEASSCRIPT: New object "ue_produmex" is added to our documentation, this object is able to send the petition to generate a picking proposal from anywhere.
Beas\Warehouse Management\Routing
2019-12-13
33824
2
UoM - correct field names
beas 9.3H-003-024-000 / beas 9.3-003-024-000
Beas\Warehouse Management\Routing
Function/Area: Item Master Data

Past: Name of UoM was not correct.

New: We changed the naming:

Old

New

German

Spanish

Warehouse Unit

Inventory UoM

Lagereinheit

 Unidad de Inventario

Consumption Unit
Bom Unit

Production UoM

Produktionseinheit

 Unidad de producción

Warehouse Unit

Inventory Counting UoM

Inventur Zähleinheit

 Unidad de Inventario

Purchase Unit

Purchasing UoM

Einkaufeinheit

 Unidad de compras


artikel_edit.psr


Field "Fixed assets" 

Past: It was always changeable. 
Problem: If this was not allowed. the backend (SAP DI API) was working wrong. 
New: It is not changeable in this window. Please use SAP Item window to change this parameter.
 
Fixed
2020-02-18
33972
1
Manual receipt - "I-Version" field dropdown error
beas 9.3-003-022-000
Beas
Function/Area: Manual receipt / issue / transfer window
Dropdown on "I-Version" Field

Past: The window displayed the following error:
(400) Syntax error in select area. Field ItemVersion/Status not existing

New: Fixed.

mw_manuell_buchen.psr


Workaround

Insert follow customizing script behind this window

// ******* Event dw_1_item_version_p_click ********
global function dw_1_item_version_p_click 
dw_1.item.version.dropdown.format=select coalesce("BEAS_ITEM_VERSION"."Version",'') as IVersionId,"BEAS_ITEM_VERSION"."Status" as StatusId,case when coalesce("BEAS_ITEM_VERSION"."DESCRIPTION",'')='' then "OITM"."ItemName" else "BEAS_ITEM_VERSION"."DESCRIPTION" end as Description,coalesce("BEAS_ITEM_VERSION"."RevisionLevel",'') as Revision,coalesce("BEAS_ITEM_VERSION"."COLORID",0) as IVersionColor,"BEAS_ITEM_VERSION"."BITMAPNAME" as IVersionBitmap   FROM "OITM" LEFT OUTER JOIN "BEAS_ITEM_VERSION" on "BEAS_ITEM_VERSION"."ItemCode"="OITM"."ItemCode"  LEFT OUTER JOIN "BEAS_WST"  on "BEAS_WST"."WST_ID" ="OITM"."U_wst_id"  WHERE "OITM"."ItemCode" = <itemcode,dbstring>
end global



2020-01-07
33119
1
Web 2.1: WO goods issue - manual search for batches not working
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas
Function/Area: WebApps 2.1 > WO Goods Issue

Past: 
Manual search for batches was not working in this app.

Now: The app is reading/searching for the batch code.




Workaround 01: Search using the magnifying glass.
Workaround 02: Open the extended batch information and type/scan the code from there.
2019-12-23
34515
1
Batch calculation SQL error - Invalid number
beas 9.3-003-026-000 / beas 9.3H-003-026-000
Beas > Zendesk id: 99322
Function/Area: Batch Calculation

Before: calculation was not working due to SQL syntax Error during the following scenario:









Window pk_batchkalk.psr

New: Error is fixed.
2019-12-03
23722
1
BOM Batch change bug
beas 9.3-003-021-000 / beas 9.3H-003-020-000 / beas 9.3-003-020-000 / beas 9.3H-003-021-000
Beas > Zendesk id: 84427
Function/Area: BOM Batch

when you change between the sub menu "substitute" and "add", it shows many item lines that are not existing in the database at all. 

Before: The problem was caused by the related .psr file: Certain items were stored in the .psr file. 
Now: the psr is clean.

 
artikel_stlpos_batch_new.psr
artikel_stlpos_batch_auswahl.psr

2019-11-29
33230
1
BeasScript: ue_mrp=purchase request not working for production request
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas

Function: Beas script

ue_mrp=purchase_request not working for "productions request"

PAST: When using beasscript to create a "production request", the system is created a "purchase request" instead.

NEW: 

Add the following SCRIPT:

object=ue_mrp=purchase_request=typ=W<tab>itemcode=RM<tab>quantity=20


2020-02-18
22619
1
Beas Translation window: Portuguese language is not considered
beas 9.3H-003-023-000 / beas 9.3-003-023-000
Beas\Administration > Zendesk id: 81805
Function/Area: Translation system Beas

Past: Portuguese language was not supported. Beas always used the English translation.
New: Portoguese is not supported. The system uses "Portuguese (Brazil)" language.


 
Note 
Translation Portuguese (Brazil) is working (~80%), but not an official supported language.

In the Beas translation window it's possible to download PTG or to apply it. But in the background the system always uses the PTB as translation.
It is not possible to edit PTG. For all changes use PTB

system_spr_browse.psr 

Beas\Administration\Data Import and Export
2020-02-18
29548
1
DIH: Import WO position - System error when you try to import a WO Position into a WO without positions
beas 9.3H-003-022-000 / beas 9.3-003-022-000
Beas\Administration\Data Import and Export > Zendesk id: 91463
Function/Area: Data Integration Hub - Work Order position import

Past: If you try to import a WO Position into a WO without positions this error message appears:


Systemerror 39 Error accessing external object property itemcode at line 14 in function of_ftpos_line of object ue_fert_ftpos_aufloesen.
Object:  ue_fert_ftpos_aufloesen  Event:  of_ftpos_line Line 14


New: No more errors, the position is inserted correctly.
2019-12-12
32364
1
Data Integration Hub: Import Resources Error
beas 9.3-003-023-000 / beas 9.3H-003-023-000
Beas\Administration\Data Import and Export > Zendesk id: 95260
Function/Area: Data Integration Hub: Import Resource with Cost Center

Past:
It was not possible to import CostCenter in Resource.
Error message: Invalid column name 'KSTST_ID'

New:
Fixed.

import_fields_browse.psr, importkopf_edit.psr
 
2019-12-09
30810
1
DIH Error: WOIM transaction type is not working with batches
beas 9.3H-003-023-000 / beas 9.3-003-023-000
Beas\Administration\Data Import and Export > Zendesk id: 92814
Function/Area: Data Integration Hub

Transaction Plan Lines
Type "WOIM" = Work order issue document

import_fields_browse.psr


Past: 
1. Error handling not good. If work order / Pos was not existing or locked, the system didn't displayed an error message
2. DistNumber and SysNumber not supported. In past only BatchNum supported

New:
1. Better error handling. The system display better error messages
2. DistNumber and SysNumber for Serial/Batch numbers supported

 
Beas\Administration\Makros and Crystal Report
2020-01-15
33370
1
Print Documents/Reports: Parameter copies not working
beas 9.3-003-022-000 / beas 9.3H-003-022-000
Beas\Administration\Makros and Crystal Report
Beas can use the SAP Crystal viewer:
Since Beas 9.3 PL 3 this has been standard setting.

 
Past: But with new viewer the Property Copies were not working in Makro:


New: Problem Fixed.

Same problem in beas script
The Property "druckcopy" was not working
In beas script we created a new propoerty
printobject=crreport=copies=x
With this you can define the count of copies.

Example:
// set parameter manual
printobject=openreport=item_bom_onelevel.rpt
// set connection to the current database
printobject=connectioninfo
// Set Parameter
printobject=setvar=FromItemCode=RM
//printobject=setvar=ToItemCode=RM
printobject=setvar=Sprache=E
// call parameter-window (if needed)
printobject=parameter
// set the parameter to the formular
printobject=parameter_set
// copies
printobject=copies=2
// and save with popup-window
printobject=crreport=printout

Note:
beas script: Please use only the printobject=crreport=x commands. 
Old variants working too, but will going in "maintenance". 
2020-01-08
24905
1
Macro definition: number of copies doesn´t work
beas 9.3-003-022-000
Beas\Administration\Makros and Crystal Report > Zendesk id: 86875
Marko definition


 report_makrostep_output_edit

You've the possibility to define count of copies per script
Past:
This was not working with new crystal viewer
New:
Now it's working
Beas\Administration\System Initialization
2020-02-18
23779
1
Login to terminal over SAP is not possible - read wrong server value
beas 9.3-003-024-000
Beas\Administration\System Initialization > Zendesk id: 83761
Function/Area: Opening Beas Terminal from SAP


PAST: In Systems where the port was added to the servername, there was a problem when opening as Terminal window from Beas.
In that case the port number was not passed to the login mask. Login was only possible when adding the port number manually.

NOW: The port information is passed to the Terminal login, so login is possible without entering the port again.


2020-02-18
20856
1
Logon Screen Server Areas - unhide all advanced fields
beas 9.3-003-026-000 / beas 9.3H-003-026-000
Beas\Administration\System Initialization
Function/Area: Beas Logon Screen
It is possible to define "Server Areas"
or change password 

Currently it's not possible to work with different servers - or it's not described...


New: All "advanced" fields are hidden (If they are empty), click 10 times on "Server Connection Setup" to make the extra DB Options visible. 
 
2020-02-18
34433
1
Material Groups >Definition of Accounts not saved
beas 9.3H-003-026-000 / beas 9.3-003-026-000
Beas\Administration\System Initialization > Zendesk id: 98506
Function/Area: Material group > Surcharges tab
Activate check box in one entry
Click on Button "Details"

In this window you can define all Material group Details.

PAST:
Account settings were not saved.

New:
Account settings are saved.
F1 is working in this window.
basis_materialgruppe_zuschlag_edit.psr
 
2019-12-23
20712
1
BEAS_OINM, Inconsistencies in UserID/UserName
beas 9.3-003-026-000 / beas 9.3H-003-026-000
Beas\Administration\System Initialization > Zendesk id: 78530
Function/Area: Tables BEAS_OINM
Create manual transfer from one to another bin location in a Bbeas bin managed warehouse
This creates entries in Table BEAS_OINM (open transactions) and BEAS_WHSBINJOUNRAL (Bin transaction history)

Table BEAS_OINM, Column ErfTStamp, AndTSTamp: 
Past: User Name was saved.
New: User IDd (OUSR.USER_CODE) is saved.
Why: DSGVO: it's not allowed to save User Name

Table BEAS_OINM, new column PERS_ID
Table BEAS_WHSBINJOUNRAL, new column PERS_ID

New: In this column the current Personnel ID is saved.
2019-12-07
32687
1
Wrong barcode value in [BEASV_WORKORDER_ROUTING] view
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Administration\System Initialization > Zendesk id: 95973
Function/Area: SQL view [BEASV_WORKORDER_ROUTING] 
Past:
The field "Barcode" returned wrong value for parallel resources. 

New:
Fixed.

Example

 

select "Position","Barcode",* from "BEASV_WORKORDER_ROUTING" where "DocEntry"=1385 and "LineNumber"=10 and "LineNumber2"=10

Now you must see the correct barcode with "LineNumber3" inside the Barcode (last 3 digits)

 
2019-11-13
22149
1
Setup -> Production - 2 identical looking entries.
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Administration\System Initialization
Function/Area: Administration - Setup:

PAST:
"Production" menu item was available twice. 
we will move the Beas "production" inside SAP "production".


New:
Now both menu entries merged


2020-02-11
33459
1
Error copying templates in Pool Report window - HANA version
beas 9.3-003-025-000 / beas 9.3H-003-025-000
Beas\beas Customizing > Zendesk id: 96454
Function/Area: Pool report window - HANA version
Past: Copying templates in pool report windows was not working correctly.

1. Open pool report window > click on Boyum logo and select "Templates Administrate"

 

(Make sure there is at least one template record)

2. Click on copy button

 
 in the past we had this error:
(<empty>)(sql2ds2) Error while generating datastore. Error Code SQLSTATE = S0002
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] Base table not found;259 invalid table name: Could not find table/view beas_sys_template in schema AAPI_SBO: line 1 col 15 (at pos 14) select * from "beas_sys_template" where "template_id" in (N'te

Now: Error is not happening.
Beas\Beas Script\Customizing
2019-11-18
33139
1
Progress bar will not switch off after creation of WO
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Beas Script\Customizing
Function/Area: Work order - edit routing position:
close window
or 
customizing
create work order with script

Past:
At end you have the "save" in the progress bar
Inside SAP, the system freezes.

New:
The system deletes the word "save" in progress bar
and does not freeze.

Beas\MRP\Order Recomendation
2020-02-18
34429
1
MRP > Filter by Sales Order line 1 does not work
beas 9.3H-003-025-000 / beas 9.3-003-025-000
Beas\MRP\Order Recomendation > Zendesk id: 97675
Function/Area: MRP - Recommendation
Filter by Sales Order line not working only in the first line

Past:
If you selected line 1, all lines were displayed.

New:
Now the system only displays line 1 of the sales order and not all lines.

mrp_view_search.psr
2020-01-06
34294
1
MRP: Minimum Inventory is not being considered in total balance using the filter "Only Shortage"
beas 9.3-003-025-000 / beas 9.3H-003-025-000
Beas\MRP\Order Recomendation > Zendesk id: 98748
Function/Area: MRP

Past:
Balance considered Minimum Inventory incorrectly: The filter "Only Shortage" ignored Minimum Inventory.

mrp_view_masterrahmen.psr
 
BoM with more reservation than planned quantity was not displayed. 
This produced wrong Balance. 
Example: Row 6: Inflow/Outflow is 0, but reservation is 1.

 
New: Fixed.

Past:
Filter  "Only Storage" not working correct in all situations, special in case
- only minimum stock or 
- only requirements in past

New:
This cases fixed. 
In drop down the complete SQL Filter was defined
Now only the Keyword "Filter" + Number


 
2020-01-28
32936
1
Database test "Check table START" error - HANA
beas 9.3H-003-022-000
Beas\Production
Function/Area: Database test - HANA

Before: Error with pressing the Database test check table "Start" button.

 system_dbtest.psr

error:
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;308 column name already exists: statusID: line 1 col 46 (at pos 45): Call RENAME COLUMN "BEAS_SYS_SETUP"."statusid" TO "stat...

Now: Error is fixed.

Workarround: You can rename wrong tables to different names and than problem will be solved:

RENAME TABLE "BEAS_SYS_SETUP" TO "BEAS_SYS_SETUP_OLD"
RENAME TABLE "beas_sys_setup" TO "BEAS_SYS_SETUP"

RENAME TABLE "BEAS_SYNTAX_HISTORIE" TO "BEAS_SYNTAX_HISTORIE_OLD"
RENAME TABLE "beas_syntax_historie" TO "BEAS_SYNTAX_HISTORIE"

RENAME TABLE "BEAS_SYS_SPRACHEN" TO "BEAS_SYS_SPRACHEN_OLD"
RENAME TABLE "beas_sys_sprachen" TO "BEAS_SYS_SPRACHEN"

RENAME TABLE "BEAS_SPRACHENTEXTE" TO "BEAS_SPRACHENTEXTE_OLD"
RENAME TABLE "beas_sprachentexte" TO "BEAS_SPRACHENTEXTE"

2019-12-07
33240
1
WO Routing position - window settings not complete
beas 9.3H-003-021-000 / beas 9.3-003-021-000
Beas\Production
Function/Area: WO Routing position - Window settings

Past:
There were many fields without the correct description.
fert_arbplanpos_browse.psr

New:
Only fields with the correct description are visible in Window settings:

 
2019-12-07
33248
1
Error converting hours to minutes in quick input window (in combination with specific windows settings)
beas 9.3-003-022-000 / beas 9.3H-003-022-000
Beas\Production > Zendesk id: 96364
Function/Area: Error converting hours to minutes

PAST: When you typed duration in hours, the system was did not convert this value into the field "Duration Minutes" and the value for this field was 0.

NEW: When you fill field "Duration Hours", the system automatically fills the field "Duration minutes" with the correct value.


Window: fert_arbzeit_schnellerfassung.psr

Bug fixed.

Workaround TIP: You can manually replace file fert_arbzeit_schnellerfassung.psr from version problem is fixed.

Expected result: No error message should appear.
2019-12-07
32906
1
Time Receipt: "Shelf Life in Days" in serial numbers is not correct
beas 9.3H-003-021-000 / beas 9.3-003-021-000
Beas\Production > Zendesk id: 89587
Function/Area: Time Receipt

After you receive a batch/serial item produced in a WO with Time Receipt and if the "Shelf Life in Days" was set in the item master data, Beas set the batch "Expiration Date" to "Today + Shelf Life"

The correct result is setting the "Expiration Date" as "Time Receipt Date + Shelf Life" 
(Base date must be the date of the production and not the current day)

Example item with 7 days for the field "Shelf Life in Days"

Past:
After creating WO for this Item and creating a Time Receipt with a date in the past, the batch expiration was related to the current day.
- But only if you worked with serial number reservation.

New:
Fixed. The date will always be calculated in the correct form in all Setting combinations.

2019-11-29
31838
1
SQL Error during the close transaction process of QC
beas 9.3H-003-021-000 / beas 9.3-003-021-000
Beas\Production > Zendesk id: 93820
Function/Area: QC order list
1. Search only for one entry - in the list you see only one entry:

Windows: qs_qsfthaupt_browse.psr,  qs_transfer_header

2. Make the transfer and close the order with this process.

Before:
An SQL Error message was displayed.

New:
Solved. No error message appears.
2019-11-26
23394
1
WO goods issue or receipt miss informatiom in JE
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Production > Zendesk id: 83774
Function: WO Issue and Receipt now Save Work missing order info

PAST: When Beas created a goods issue or receipt linked to a WO, the system saved nothing in the journal entry generated by SAP.

NEW: Beas saves info in an SAP journal entry linked to goods issue or receipt document information related to the WO.




Window: mw_manuell_buchen.psr





2019-11-25
28275
1
Work order UoM in tooltip not working correctly
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Production
Function/Area: New work order position
Insert assembly with different UoM between  Warehouse unit and Consumption Unit
In UoM the factor between Units is not 1

 
In the work order position the system displays the unit in green.
This means: a unit factor is inside.
If you move the mouse over this field, the system displays a tooltip with information on the factor and the UoM.

fert_ftpos_edit.psr
 
Past:
Display was not correct if you changed quantity (example for new entry)

New:
Fixed.

2019-11-25
24637
1
Production time adminstration - column title not translated
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Production > Zendesk id: 85998
Function/Area:  Production time administration - first tab

fert_arbzeit_browse_alle.psr
 
Past: Column Time factor was always German (zeitfactor)
New: Fixed.


2019-11-13
20636
1
Production: POS_ID displayed instead of POS_TEXT in certain places
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Production
Function/Area: Work order with Stock related Assembly in BoM List. 
The BoM Number is alphanumeric.


Work order with same item as assembly



(optional) Sales order with same item



Beas Reservation system is active.

In work order with the finished good item you can create a cross reference.

Here you can choose the work order, which have the same item in BoM List


 
Past:
The system displayed internal Pos ID and not the visible Position text.

New:
Fixed. You can see the correct Position text.

Same in the Cross Reference List:
reservation_link_browse.psr, reservation_link_edit.psr

Link with Sales order: You see always the correct Line number (RDR1.VisLine +1)
(was working before too)

 
It is also possible to change the quantity from an existing reservation.
(was working before too)

 
2020-02-18
33493
1
APS calculation: when the "Use factor" has decimals
beas 9.3H-003-022-000 / beas 9.3-003-022-000
Beas\Production\APS > Zendesk id: 96502
Function: APS Calculation: "Use Factor" ignores decimals

PAST: In the APS calculation for operations, the system occasionally ignored decimal values defined in the "Use Factor" field, and calculated the result accordingly. 


Window: Fert_arbplanpos_edit.psr


Window: Fert_plan_tafel.psr

NEW: Beas applies the "Use Factor" field correctly.
Bug fixed.


Expected result: No error message should appear.
2020-02-18
33914
1
APS: varchar to datetime converting problem
beas 9.3H-003-022-000 / beas 9.3-003-022-000
Beas\Production\APS > Zendesk id: 97670
Function/Area: APS
In environments with a german SQL-server you could get this errormessage:

(**)Error while Read or Update DataStore: Select Error: SQLSTATE = 22008
[Microsoft][ODBC SQL Server Driver][SQL Server]Bei der Konvertierung eines varchar-Datentyps in einen datetime-Datentyp liegt der Wert außerhalb des gültigen Bereichs.
SQL-Syntax:select "BEAS_FTPOS"."BELNR_ID","BEAS_FTPOS"."DocEntry",...


fert_aps_browse.psr


Past:
There was a conversion for a date that could not be converted when SQL-server settings were set to German.

Now:
The conversion was changed to an international standard, so it will work without problems on German and English server settings.

Beas\Production\Configurator
2020-02-18
27527
1
Variant Configurator: Formulas based on Order/Order Line causing SQL error
beas 9.3-003-023-000 / beas 9.3H-003-023-000
Beas\Production\Configurator > Zendesk id: 88745
In Bill of Material position you can define Assignments (Formulas)
related to Order or Order line, example: Field FreeTxt

 
In sales order you can create the precalculation

  


Past: System displayed follow error message
Error in sql statement: (-1) SQLSTATE = 37000
[Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near the keyword 'and'./156: 
select FreeTxt from rdr1 where docentry= and linenum=
Current Window: Variant Production (program\caft_eval.psr) Function form_load-button redraw event getfocus

New: The system read the correct value from Sales order

Note: 
This is working only, if the Sales order is saved, because the variant system read the information from Database and not from current screen.

2020-02-18
34069
1
Configurator > Formulas: Error in parameter "cshortvariant"
beas 9.3H-003-022-000 / beas 9.3-003-022-000
Beas\Production\Configurator
Function/Area: Configurator > Edit formula
Choose "cshortvariant"
Past: Inserted wrong variable:
artikel_produktkonfigurator_detail.psr

New:
Fixed.
2019-12-17
32250
1
Web-Configurator Error: loading Item definition window iI the cross reference select field contained spaces
beas 9.3H-003-022-000 / beas 9.3-003-022-000
Beas\Production\Configurator > Zendesk id: 95538
Function/Area: Web Configurator

Before: iI the cross reference select field contained spaces, we executed an empty query.
After: We check if the field is really empty.

Workaround: Make the "Select" field empty if you are not using queries.


 
2019-12-07
33398
1
Inventory: "Delete" Button not visible
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Production\Configurator
Function/Area: Inventory 

Before:
Button "Delete" was not visible.

New:
The Button "Delete" is visible if 
- the Inventory status not booked or closed
- counting not started
mw_inventory_header_edit.psr
 
2019-12-05
32249
1
Web Configurator - Text field is not fully visible
beas 9.3-003-021-000 / beas 9.3H-003-021-000
Beas\Production\Configurator > Zendesk id: 95516
Function/Area: Web Configurator

Before: The field for this description was truncated at the moment of sending content to the web configurator.

After: We send the complete content.

additonally: We translate the new line character to html new line on the front-end


 
Beas\Production\Factory data capture
2019-11-25
20776
1
Previous operation sequence must be completed: Display correct Position text
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Production\Factory data capture
Function/Area: Work order with alphanumeric routing position numbers, all mandatory
Configuration wizard > Production > FDC > Logon/Logoff Rules > Previews operation sequ. must be completed.


 

In this example:
Position C is not closed
Try to start Position A (second position)

Past: 
Error Message appeared: The system displayed internal Pos ID and not the visible position text:

Preceding work sequence 10 needs to be complete first

New:
Preceding work sequence C needs to be complete first

fert_ftstmp_anmeldung.psr

 

Additional change

Past:
With Logon the system changed the status in table "beas_mde_status" for the current resource. 

New:
In the future we will not support this table:
update beas_mde_status set afobarcode=:ll_afonummer,change_id=2 where aplatz_id=:ls_aplatz_id;
Beas\Production\Factory data capture\Terminal
2020-02-18
33934
1
German messages in Terminal
beas 9.3-003-022-000 / beas 9.3H-003-022-000
Beas\Production\Factory data capture\Terminal > Zendesk id: 97824
Function/Area: Close terminal
Past: Title was always in Ggerman.

New: Fixed.

Beas\Production\Factory data capture\Work Order Backflushing
2020-01-06
14742
1
"Also post serial numbers" - setting manually deleted
beas 9.3H-003-025-000 / beas 9.3-003-025-000
Beas\Production\Factory data capture\Work Order Backflushing
Function/Area: Configuration wizard 
PATH: Configuration Wizard > production > material posting > Backflushing
- also post batches
- also post serial numbers

Past: it was possible to choose "manually".
But this option was only running together with the Backflushing 2009 variant which is not supported since beas 9.3 PL 0.

New:
Now it's not possible to choose "Manually" in either setting.
Window system_option_struktur.psr
Setting: fert_charge, fert_rserie
 
Beas\Production\Project
2019-12-05
19195
1
Projects: SAP Activities not linked to the ProjectCode at creation
beas 9.3-003-022-000 / beas 9.3H-003-022-000
Beas\Production\Project
Function/Area: Projects
Create new activity

Past: Project Code and Project Task were not inserted.
New: Fixed.

 
2019-11-25
32330
1
Project: Selection criteria "Active" does not work
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Production\Project > Zendesk id: 95402
Function/Area: Production > project > project

Past: Click on search button. "Active" field filter did not work properly.


 
prj_browse.psr

Now: Search filter button is working correctly.

Workaround: 

Replace only this psr file from current beas version.

 
2019-11-19
32584
1
Project Code is not transferred to Sub Positions when doing a WO Refresh
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Production\Project > Zendesk id: 95405
Function/Area: Work Orders

When we work with Project/Task, we fix the following cases:

If you insert a new BoM: We must insert the same Project/Activity as in Assemlby defined (parent position)
fert_ftpos_edit.psr
fert_ftstlpos_edit.psr


If we insert a BoM with order-related item, the same Project/Activity must be inside all sub positions, material positions, routing positions.
If we refresh a work order and in master data we changed the structure (new items with sub structure):
In all new generated routing positions/bom/work order positions and so on same project code/activity must be inside.

If we change project code/activity in wo position, the system asks if the system must insert this in all sub positions (check, if this is working correctly)

Beas\Production\Workorder
2020-02-18
19107
1
Pool Report: No results displayed when assigning two or more Resources in the Work Station Setting Wizard
beas 9.3-003-023-000 / beas 9.3H-003-023-000
Beas\Production\Workorder
Function/Area: Terminal Pool Report
Past: 
- Resource Filter by Station setting not working.
- Resource Filter for parallel resources not working.
New:
Fixed.

For all details on Pool report see

2020-02-18
16505
1
WO BoM: Link to Operation lost when using Phantom Assemblies
beas 9.3H-003-022-000 / beas 9.3-003-022-000
Beas\Production\Workorder
Function/Area: WO BoM
Past: Work Order Bill of materials Link to Operation was lost when using Phantom Assemblies.

New: Phantom assemblies on Master Data are linked to Operations.


Function/Area: Work order Bill of Materials

Past: When generating WO for an item, the links were lost
Now: The links are preserved and updated to the new Operations positions:


 
Calculation of correct linking is very complex. 
By default it's disabled
You can activate this with follow beas script: setsetup=phantom_extended='Y'

window: fert_stuktur_browse.psr
2020-02-18
32514
1
Work Order Structure: Setting 'Extended Status Display' not applied after using Search
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Production\Workorder > Zendesk id: 94977
Function/Area: Work order structure

Past: If you activate the "Extended status display" In the work order structure, after searching something using the search button (or reset a search using the search field at the bottom of the window), this information is not displayed any more.

New: We have fixed this wrong behavior.



2019-11-29
24096
1
P&L, Apply new Journal Entry logic only to affected SAP Versions
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Production\Workorder > Zendesk id: 81918
Function: P&L Accounts new journal entry applies only to 930160 version and following

PAST: Beas applied new journal entry logic for version 930100 and above.

NEW: Beas validates PL6 instead of PL0 version.

The problem is fixed.


2019-11-25
15248
1
Cancelled batch issues are still available for linking - New solution
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Production\Workorder
Function/Area: Work order with batch number managed assembly
Material with batch number managed material.

In Beas it is possible to link the batch number from material to a batch number from the assembly:
fert_allocation_batchsernum_list1_receipts.psr

Past:
The Link was not possible if the batch number was locked.
New:
The link is always possible. The System does not check status of Batch number.
 


2019-11-22
27846
1
Backlog Work order information in Journal entry row remarks
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Production\Workorder > Zendesk id: 89442
Function: Improved WIP Journal entry "Reference2" information

PAST: Beas saved values like "GK", "FIX", "VK" into "reference2" field in the WIP variance journal entry. These values are acronyms for German words that mean:
* Marginal Cost (GK)
* Fix cost (Fix)
* Full Cost (VK)

NEW: Beas saves values in the "Reference" field in the correct language:

* Marginal Cost
* Fix Cost
* Full Cost



 


2019-11-20
17568
1
Scrap in raw material does not restore quantity values
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Production\Workorder
Function/Area: Scrap in raw material

Past:
After swapping the routing from a parallel one with a scrap of material % for the original one without scrap %, the quantity for the raw material remained with the calculated for the last routing.

Now: The quantity is back to the right one.

fert_stuktur_browse.psr


fert_arbplanpos_edit_alternativ_edit.psr
2019-11-15
33085
1
WebApp 2.1 - Stock Transfer Request error in Quantity setting
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\Production\Workorder > Zendesk id: 96640
Function/Area: WebApps >Stock Transfer Request

Past:
In the Web APP Stock Transfer Request, for each line we checked the quantity available for the item in the source warehouse/location and didn't allow it to set more quantity than available

New: This was wrong, and this check has been removed.
Now you can request to transfer more units than available for the selected item.


 
Beas\Purchase\Goods receipt Purchase
2019-12-07
32686
1
Incoming goods - single row: vertical scroll in Batch field not working
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Purchase\Goods receipt Purchase > Zendesk id: 96084
Function/Area: Incoming goods
In Supplier Batch No. and the Batch field.

Past:
The vertical scroll was not working.
It was not possible to insert allowed count of characters

New: 
Fixed.

Window mw_wareneingang_edit.psr
2019-12-20
11612
1
Usability, QC Order window from Operation (at Time Receipt) jumps into the background
beas 9.3-003-026-000 / beas 9.3H-003-026-000
Beas\Quality Control > Zendesk id: 57406

If you define a QC inspection Plan, for a routing position, depending on the Configuration wizard options, a new window appears to complete the new QC Order created after the time receipt.


Before: After closing the time receipt, the new QC window appeared in the background.
After: The QC window stays in the foreground.


Window: fert_arbzeit_erfassen.psr
2019-12-19
32685
1
Resource - Calculation of marginal Cost Rate and full cost Rate is not working
beas 9.3-003-022-000 / beas 9.3H-003-022-000
Beas\Resources > Zendesk id: 96098
Function/Area: Resource > Cost Tab details

Past:
Summation of individual values did not work.

New:
This is fixed.

stamm_arbplatz_edit.psr
 
More details see Video

Beas\Service\Maintenance Orders
2020-02-13
32141
1
Maintenance Order - Error in Time receipt
beas 9.3-003-024-000 / beas 9.3H-003-024-000
Beas\Service\Maintenance Orders > Zendesk id: 95032
From the Maintenance order windows, depeding on your maintenance plan configuration, it is possible to create a Work Order and Time Receipts.

Before: At the moment of the "order time report" and after the "Time Receipts" opened, the field "Parallel Position"was filled with a wrong value.
After: You can report times without errors.


window: maintenance_plan_dateedit.psr
2019-12-07
33540
1
beas script: VBSCRIPT and JSCRIPT not working
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\System and Other
Function/Area: beas script
In beas script it is possible to insert VBS and JSCRIPT scripts

Past:
Since beas 9.3 PL 0 this was not working.

Example:

[vbs]
function dec2hex (s)
dec2hex=hex(s)
end function
[/vbs]
messagebox=<vbscript.dec2hex(255)>

New:
Now the script is working.
Beas\System and Other\Beas Service Layer
2019-12-16
33446
1
Beas Service Layer: Authorization not stable
beas 9.3H-003-020-000 / beas 9.3-003-024-000
Beas\System and Other\Beas Service Layer
Function/Area: Beas Service Layer - Login / GET command

Before: Authorization was not stable.
It returned results randomly 

Now: Fixed.


2019-11-29
33354
1
Production Time receipt: Dropdown not closing
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Usability
Function/Area: Production Time receipt - Field "Document"
Click dropdown

Before: If you click on a line, the dropdown list doesn't close. You must click on another place or esc.

After: the dropdown is closed after you select an option.
Window: fert_arbzeit_erfassen.psr
Beas\Warehouse Management
2019-12-30
23072
1
Wrong calculation of time in alternative resources with Scrap Factor
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Warehouse Management
Function/Area: Alternative resources with scrap factor

When you define a Scrap factor in a routing position this affects the alternative routing.
This means that if you swap to an alternative resource, the time should be calculated considering this factor.

Past:
Before this patch, was an error displaying the right planned time for the alternatives operation.

New: 
This problem is solved.


fert_stuktur_browse.psr



 
fert_arbplanpos_edit.psr


Beas\Warehouse Management\Bill Of Materials
2020-02-18
23782
1
BOM List Window - Beas Item search filtering problem
beas 9.3H-003-023-000 / beas 9.3-003-023-000
Beas\Warehouse Management\Bill Of Materials > Zendesk id: 84323
Function/Area: Inserting a new line in Bill of Materials


artikel_stlpos_browse.psr

PAST: When you added a new line, and pressed the TAB-key in the item field, a search window was opened. But this window was filtered by the item from the
previous row.

NOW: The search window opens, and shows the complete item list.

2019-11-29
12659
1
Copy/Insert Routings/BoM, SortID will remain NULL
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Warehouse Management\Bill Of Materials > Zendesk id: 58760
Function/Area: Item structure: copy-paste routings/bom
From the item structure you can copy/paste routings/bom, but if the target item is empty (it doesn't have bom/routing) then

Before: The field sort ID was not filled.
After: The field sort ID is filled.

Steps to reproduce:
1) Create a Item WITHOUT existing Routings/BoM
2) Go to Item Structure, select a Routing/BoM from a different Item and Copy Selection
3) Go to the new item and 'Copy Insert' the Routing/BoM

4) Check the Tables BEAS_APL and BEAS_STL

 
Result:
SortID will remain NULL for all new positions you insert.

Expected Result:
SortID should get created automatically.
Beas\Warehouse Management\Inventory Transactions
2020-02-18
32510
1
External Operation: Work Order Position gets closed automatically on Goods Receipt
beas 9.3H-003-024-000 / beas 9.3-003-023-000
Beas\Warehouse Management\Inventory Transactions > Zendesk id: 95132
Function: External Operation. Get closed automatically on goods receipt

Environment: Parameter: fert_abg=A


parameter: ext_openprovwindow = D


PAST: When user generated a goods receipt from external operation, the system closed the WO and parameter  "Close Assembly automatically" was ignored.



NEW: Beas read parameter "Close Assembly automatically" and close or stop process based on this parameter.
The problem is fixed.

Workaround: You can replace fert_external_openorder_edit.src from the last version.

Expected result: Work order must be closed or kept opened based on defined parameter.
2019-11-29
32133
1
Bin Booking, Transactions based on SAP Bin Locations not possible if multiple Batches are located in the same Bin Location
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Warehouse Management\Inventory Transactions > Zendesk id: 89781
Function: Issue for SAP BIN warehouses now allows merging of several batches in the same Bin Location.

PAST: When you tried to allocate several batches in the same SAP bin location, Beas generated the following error message:

error    ret=(-10) 1470000341 - Fully allocate item "MAT04" to bin locations in warehouse "11"
109    error    base_doctype=wo

NEW: Beas allows to generate this type of transaction without any problem.



Window: Reservation_set_master.psr

WORKARROUND: Only possibility is to generate 1 document per batch. It means that if user detecs 2 batches in same location, then user has to generate 2 separate documents (1 per each batch number). 

Bug fixed.


2019-11-29
19656
1
Batch Tracing Window: missing "inventory posting" Document type name
beas 9.3H-003-022-000 / beas 9.3-003-022-000
Beas\Warehouse Management\Inventory Transactions
New: Added the "Inventory Posting" service document type to the batch tracing window.


mw_tracing_master.psr

Beas\Warehouse Management\Inventory Transactions\batch calculation
2020-02-18
34182
1
HANA, Batch Calculation, SQL errors
beas 9.3-003-023-000 / beas 9.3H-003-023-000
Beas\Warehouse Management\Inventory Transactions\batch calculation > Zendesk id: 98490
Function/Area: Batch calculation
Filter by ItemGroup 

pk_batchkalk_edit.psr

Past:
In HANA this produced the following error message:
(sql2ds2) Error while generating datastore. Error Code SQLSTATE = S1000
[SAP AG][LIBODBCHDB32 DLL][HDBODBC32] General error;328 invalid name of function or procedure: CONVERT: line 1 col 803 (at pos 802) select ..

New:
Fixed.

Workaround

Insert filter in "Filter SQL"
Example:
 and CAST(`OITM`.`ItmsGrpCod` as varchar(10)) in ('01')
Beas\Warehouse Management\Item Management
2020-01-06
34225
1
Bin Booking: Serial Numbers are not displayed
beas 9.3-003-025-000 / beas 9.3H-003-025-000
Beas\Warehouse Management\Item Management > Zendesk id: 98552
Function/Area: Inventory > Open documents - Only beas 9.3 PL 3

Before: Serial Numbers were not displayed, only the internal System number.
Now: Fixed.

bin_struktur_batchbooking.psr
 
Workaround: no.
2019-12-23
27910
1
Journal of entries > Personnel Number is Blank and DisplayName shows the SAP User Name
beas 9.3H-003-026-000 / beas 9.3-003-026-000
Beas\Warehouse Management\Item Management > Zendesk id: 87395
Function/Area: Item Journal of entries
Entries for Beas Bin transaction
(Transfer from on to another bin in same Beas Bin Warehosue)

Past: Personnel name was not displayed.
New: The Personnel name will be displayed for all documents created with Beas 9.3 PL 3 HF 1 or later.


 
mw_buchen_journal_master_batch.psr

Same in batch tracing report

mw_tracing_master.psr

Note: In BIN - BIN Transactions, which created with older beas version, the system can't display the Personnel Id. This information is not saved

See Video
Beas\Warehouse Management\Item Master Data
2020-02-18
34159
1
Material Group - Cross reference error
beas 9.3H-003-026-000 / beas 9.3-003-026-000
Beas\Warehouse Management\Item Master Data > Zendesk id: 98487
Function/Area: Material Group >Cross Reference

Open Material Group --> right click Cross Reference / click on Reference button:

 
Past:
In Cross Reference window, right-click and select the option "edit" and Beas sends this error:

[Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '='./102: 
select count(*)   from "OSRN" where "ItemCode"=
Current Window: Item master data for 3965&A (program\artikel_edit.psr) Function 


Now:
The window shows the correct menu entry "Edit".


basis_materialgruppe_browse.psr

by clicking on Edit, you open the item master data for that specific Item.
 


2020-01-07
33478
1
beas script: DataStore - problem with update
beas 9.3H-003-020-000 / beas 9.3-003-021-000
Beas\Warehouse Management\Item Master Data
Function/Area: beas script
object ue_datasatorevalues

Past:
If you created a datastore and made an update on the window without destroying the datastore before, the system made an update on datastore, as well.
This can produce trouble, especially if no update properties were defined.

New:
The datastore accepts only commands which have the object in prefix.

Example
instance datastore d
d.select=...  // executed in datastore object
d.update    // executed in datastore object
update      // not executed

2020-01-07
33479
1
Item Master Data: SQL error when creating new ItemCode
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Warehouse Management\Item Master Data > Zendesk id: 97290
Function: Item Master Data - creating New ItemCode 
Problem: Wrong validation

PAST: If user tried to create a new item, and type an itemcode, the system showed a red error message.

NEW: Now the error message is removed. This error is not locking the application and you can continue working without any other additional problems.

Bug fixed.

Workaround: You can manually modify file sbo_150.src, you have to add this:

windowevent itemchanged 5

object=ue_artikelstamm=numbercheck=<item 5>
if <return> n= -1 then
   item=5=value=<char 32>
   return failure
end if

// JDG :: 20180112 :: iTicket 10964 - Item name modification: Block if purchase request exists
select count(*) from "BEAS_STL"  where "ART1_ID"=<item.5.value,dbstring>
if <wert1> n= 0 then
select count(*) from "BEAS_FTPOS" where "ItemCode"=<item.5.value,dbstring>
end if
if <wert1> n= 0 then
select count(*) from "BEAS_FTSTL" where "ART1_ID"=<item.5.value,dbstring>
end if
if <wert1> n= 0 then
select count(*) from "BEAS_MRP_ORDER" where "ItemCode"=<item.5.value,dbstring>
end if
if <wert1> n> 0 then
  messagebox=beasmeldung$bomexists$Für diesen Artikel existiert eine Stückliste, ein Arbeitsplan oder andere Verlinkungen. Bei Änderung der Artikelnummer werden die verlinkten Daten nicht angepasst.
end if


return no action
end event

Expected result: No error message should appear.
2019-11-29
27921
1
Authorizations: Button "Beas Rights" not displayed, overlaps with buttons created by other AddOns
beas 9.3H-003-021-000 / beas 9.3-003-021-000
Beas\Warehouse Management\Item Master Data
Function/Area: Authorizations

Before: The button "Beas Rights" was not displayed, overlaps with buttons were created by other AddOns.

Now: We have this functionality in the right-click menu.
Window: Administration > General Authorizations
 
2019-11-29
28721
1
Item Master Data: Search in "Manufacturer" dropdown field not working
beas 9.3H-003-020-000 / beas 9.3-003-020-000
Beas\Warehouse Management\Item Master Data > Zendesk id: 91289

Function/Area: Item Master Data > "Manufacturer" field dropdown


Before: The dropdown search was not working well when some of the fields where hidden

Now: This is fixed.

Window artikel_edit.psr

Beas\Warehouse Management\Item Structure
2020-01-06
34129
1
Sub-Assembly - Separate Bill of Materials shows wrong routing
beas 9.3-003-025-000 / beas 9.3H-003-025-000
Beas\Warehouse Management\Item Structure > Zendesk id: 97863
Function/Area: Separate BoM for Item versions in sub-assembly
In SAP Sales order you can define an Item Version:


In the Item you can define different item versions and can define separate Bill of Materials List for every version


In Bill of Materials Header you can define a Routing plan


Past:
MRP, CTP and ATP ignored the  Routing plan defined in the BoM header, and always used the routing plan with the same ID as the Item itself.

New:
Now MRP, CTP and ATP are working correctly.
atp_view.psr, 

mrp_view_resource.psr
 
In Item Structure view the system displayed wrong Routing position in sub structure, if you worked with Item Version control and separate BoM
New: Fixed.
artikel_struktur_browse.psr
 
Beas\Warehouse Management\Routing
2020-01-07
7699
1
Wrong column name shown in Routing plan
beas 9.3H-003-022-000 / beas 9.3-003-022-000
Beas\Warehouse Management\Routing > Zendesk id: 49003

In the Configuration wizard we can define the time types:


 

We must show the same names in:


Operation catalog: Checked and working

Resource Master Data: Checked and working



WO Operation: checked and working

 
PreCalculation: Operation


Routing position browser / windows settings / editor


 

 
 
 



2019-12-30
24019
1
BOM quantity wrong when scrap is in both BOM and routing
beas 9.3-003-021-000 / beas 9.3H-003-021-000
Beas\Warehouse Management\Routing

In Bill of Materials you can define a Scrap factor in %
artikel_stlpos_edit.psr

Past: 
1. What was wrong with the scrap calculation is the combination of both "BoM Scrap" and "Routing Mat Scrap".
   When both are defined, the scrap is calculated separately based on the quantity, but this is not correct.
2. The Calculation method was different in PreCalculation, MRP and WorkOrder
We had the following variants:
Quantity * ( Scrap % )  
Scrap = Quantity / ( 1 - Scrap%/100 ) (example: used in calculation of routing position)

New:
The Material Scrap % in Routing position always uses this formula (same as past)
Quantity * Scrap = Quantity / ( 1 - Scrap%/100 )

The formula for Material Scrap defined in Bill of Materials can be defined in the Configuration wizard.
You can select between two methods to calculate the BoM Scrap.
Scrap = Quantity * ( Scrap % )  
Scrap = Quantity / ( 1 - Scrap%/100 ) 

Default is first option (same function as in the past). In this way you will not lose compatibility to older versions.


Example:

Setting: Quantity * ( Scrap %)
Routing Material Scrap: Only linked material position



 
 
Position 10:   1 Pcs + (1 Pcs / 100 * 5) =  1.05
Position 20:   1 Pcs + (1 Pcs / 100 * 10) = 1.1 Pcs
Position 30:   1 Pcs + (1 Pcs / 100 * 10) = 1.1 Pcs
     Only with Routing Scrap: 1 / (1 - (10% /100) ) = 1.1111
     With Material Scrap: 1.1111 * (10 : 100 * 10) = 1.2222

In work order you can see the exact same result:

and same in post calculation

In MRP  
 
Note: Item Structure view export does not support scrap information.



Fixed Error in MRP
If you had an item with item version and no Routing position was linked in the linked BoM, you got the following error message in MRP calculation:
08:24:48 (**) Error while Read or Update DataStore: Select Error: SQLSTATE = 37000
[Microsoft][ODBC SQL Server Driver][SQL Server]The data types nvarchar and text are incompatible in the equal to operator.
DataWindow: d_mrp_stl_scrap

Problem is Fixed.


2019-11-29
24620
1
Field name replacement for "Processing" time to Mach+Labor time in parallel/alternative resource
beas 9.3-003-021-000 / beas 9.3H-003-021-000
Beas\Warehouse Management\Routing
Function/Area: Routing (Catalog, Routing plan, Work order Routing plan, PreCalculation Routing) -> Parallel and Alternative Resource

Past: 
Description in edit form was "Processing"
New:
Description in edit form is same as in list form: "Masch+Labor Time/unit"


artikel_arbplanpos_edit_alternativ_edit.psr, artikel_arbplanpos_edit_parallel_edit.psr, pk_arbplanpos_alternativ.psr,
pk_arbplanpos_parallel.psr, stamm_ag_edit_parallel_edit.psr, fert_arbplanpos_edit_parallel_edit.psr
2020-01-07
34090
1
Error selection of the resource in 2.1 WebApps Time Receipt
beas 9.3-003-025-000 / beas 9.3H-003-025-000
Beas\WEB > Zendesk id: 97241
Function/Area: WebApps Terminal 2.1: Time Receipt

Before: The advanced search for resource is displaying wrong column titles and content.

Fixed: Resources > advanced search > titles and content
Now: If the selected resource (typed manually) doesn't exist, it falls back to the default one (selected in the routing position)





2019-12-13
33455
1
Web 2.1: Variables (e_docnum, DocNumber) not available when printing
beas 9.3H-003-023-000 / beas 9.3-003-023-000
Beas\WEB > Zendesk id: 96760
Function/Area: Print setup (WEB APP Version 2.1)


Past:
- "Script" was not working
- Support variables (before: only print variables)
 

 - DocNumber, DocEntry and other Variables not available in every document

New:
- All errors fixed
- New: Print script with Script Editor

- The following variables are available in all apps that can create an SAP transaction:

- Better documentation with good examples

Not supported:
Time receipt, Backflush
We working on additional functionalities

2019-11-15
32246
1
Web Apps 2.1, WO Start, Time Receipt for Parallel Operation not linked correctly
beas 9.3-003-020-000 / beas 9.3H-003-020-000
Beas\WEB > Zendesk id: 95214
Function/Area: WO Start and Time Receipt webapps in WebApps 2.1

Past:
When you use the BSL to start/stop a WO with a parallel resource, the work was initiated in the parent instead of the selected parallel resource.

Now:
This is fixed and the start/stop are done in the selected parallel resource.

Since the web apps "WO Start" and "WO Stop" are using BSL you can check the right behaviour using these apps.