New
Beas\Production\Workorder
2019-03-29
20415
2
Better memory allocation at Work Order creation and refresh
beas 9.3H-002-015-000 / beas 9.3-002-015-000 / beas 9.3H-001-033-000 / beas 9.3-001-033-000
Beas\Production\Workorder > Zendesk id: 77843

Attempting to release memory after / while creating a work order

The app memory consumption shouldn't increase in an uncontrolled way.


Fixed
Beas\Administration\System Initialization
2019-07-19
17717
1
BEAS_COMMON, deletion of old records not working
beas 9.3-002-015-000 / beas 9.3-001-033-000 / beas 9.3H-002-015-000 / beas 9.3H-001-033-000
Beas\Administration\System Initialization > Zendesk id: 70733
beas common service

PAST: delete output and input table was not working correctly.

NEW: Problem fixed. Every 120 second Beas calls the function which deletes the related entries.

Window: system_common_dashboard
2019-11-11
19341
1
beas Script, dw_1.column.default does not work when using the defined fieldname
beas 9.3H-001-031-000 / beas 9.3H-002-013-000 / beas 9.3-001-031-000 / beas 9.3-002-013-000
Beas\Beas Script > Zendesk id: 74984
Function:

beas script
create new columns with 

create or 
etab.createnewobject

The following script adds a column in a tab area

etab=addnewobject=stamm=myfield=column=userfield1=nextlinefrom=anzls
etab=addnewobject=stamm=myfield_t=text=My Test Field=nextlinefrom=anzls_t
etab=redraw

PAST: 
This produced an error.

setitem=myfield=test1

but this was working
setitem=userfield1=test1


NEW: Both variants are working.

setitem=myfield=test1
and
setitem=userfield1=test1

Information:
In beas 9.3 PL 02 you can use the create function to insert new columns in a tab area in a simple way. See our beas script documentation
Beas\Human Resources\Report Attendace
2019-05-02
15017
1
Report monthly work time NOT saving Window settings changes
beas 9.3-002-014-000 / beas 9.3-001-032-000 / beas 9.3H-001-032-000 / beas 9.3H-002-014-000
Beas\Human Resources\Report Attendace > Zendesk id: 63986
Function:
In area attendance we have the report "monthly work time". In this report it is possible to change the displayed information with "Window settings"

window: bde_personal_report_arbeitszeit.psr

PAST: You could change the settings, and the report was displayed according to the settings.  But when re-opening the report, all the settings were lost.

NEW: Now all the settings are stored correctly, and so the report is shown correctly.


2019-07-19
16340
1
The sub-assemblies cross reference NOT working correctly
beas 9.3-002-014-000 / beas 9.3H-001-032-000 / beas 9.3H-002-014-000 / beas 9.3-001-032-000
Beas\Production > Zendesk id: 67242
Function: Manual reservation on Work order Level

In this example work order position 20 was reserved for Bill of Materials Position 10 BoM 30 (Material 08150001_000)

 

PAST: If you made the receipt in Work order position 20 for fully planned quantity, beas did not create the stock reservation for the linked Bill of materials position.

NEW: Error Fixed. beas creates the Stock reservation correctly.

2019-07-19
20468
1
Parallel resources not working in Production Time Receipt window
beas 9.3H-002-015-000 / beas 9.3-001-033-000 / beas 9.3H-001-033-000 / beas 9.3-002-015-000
Beas\Production > Zendesk id: 78331
Function:

In beas you can define parallel resources


In time receipt you can choose the parallel resource

 
Window: fert_arbzeit_erfassen

PAST: Beas ignored the information about parallel position and inserted time receipt in main routing position

NEW: error fixed

It was working correctly in function
- Create time receipt from work order structure window directly on parallel resource position 
- Terminal - time Receipt Start / Stop 

It is possible to fix error with replacing file fert_arbzeit_erfassen.src 
2019-07-19
20469
1
Insert WO in pool not working
beas 9.3H-002-015-000 / beas 9.3-001-033-000 / beas 9.3H-001-033-000 / beas 9.3-002-015-000
Beas\Production
Function:

Beas calculates pools automatically if you create a work order, work order position, or if you change anything in a routing position:



PAST: This was not working during capacity planning recalculation.

NEW: fixed. 

Workaround:
- Pool calculation was working with Pooling, Scheduling
- After time receipt - calculate next Pool


 
2019-05-02
19556
1
Time Receipt: Primary Key Error
beas 9.3-002-014-000 / beas 9.3-001-031-000 / beas 9.3H-001-031-000 / beas 9.3H-002-014-000
Beas\Production > Zendesk id: 76183
Function:

Time Receipt

fert_arbzeit_erfassen.psr
 

PAST: if many users were creating a number of time receipt simultaneously, the following SQL error message would appear:
"SQL error on Time Receipts, Violation of PRIMARY KEY constraint 'PK__BEAS_ARB__B8A9D1CECA4EAAB6'"
In this case beas did not save the time receipt entry.

NEW: 
1. the system tries to minimize the problem 
2. if this is not possible (example > 10 time receipts in same second) the system tries it to save up to 3 times with the new internal number

Problem is solved.


2019-05-02
17949
1
APS does not calculate the correct times after 12:00PM
beas 9.3-002-019-000 / beas 9.3-001-031-000 / beas 9.3H-001-031-000 / beas 9.3-002-006-000 / beas 9.3H-002-019-000
Beas\Production\APS > Zendesk id: 71629
Past:
At a work order with a resource allocation not 100% (or quantity  not 1), the calculation in APS was not correct.
When doing a forward planning in APS, the planned time for the actual day was not correct and the total planned time (if the operation had to
be split to more than one day) differed from the amount of time actually needed for completing the operation.

Now:
Now this error is fixed. The total planned time is not higher than the needed time any more and the actual day is calculated correctly.

Remark:
When resource allocation is not 100%, the time for the operation is calculated as follows:
1. Remaining capacity = capacity for the day - times already used by other WO's
2. maximum X% (e.g. 50% in example) of this capacity will be used for the operation. 



 


stamm_arbplatz_planung.psr


Example for calculation  when the recaource allocation is less than 100%
Assumption:
- WO with 4 Positions
- Same Item but different deliverydates
- Processingtime is 10 hrs. per position (10 Pc * 60 minutes processing)
- resource allocation is set to 50%
- the capacity of resource "1010" is 24 Hrs.



 


 
Explanation:
1)
- resource has 15 hrs. left for  the day (9-24)
- 1. WO gets 50% 7,5 hr's
- for the next day only 2,5 Hrs. are needed, so the resource is assigned from 0-5
2)
- now for the 13.03 there are left 7,5 hr's of capacity
- 2. WO gets also 50% of the capacity of the next 15 hrs.
- for the 14.03 there are now 21,5 hrs. left
- WO gets 2,5 hrs. , so it can end at 5:00

3)
- at 13.03 there is no more capacity left (2*7,5 hrs for the 2 prev. positions)
- so WO starts at 14.03
- remaining capacity is 19 hrs. (24 - 2 * 2,5)
- so WO gets 10 hrs between 0:00-20:00

4)
- there is no capacity at 13.03 so start is at 14.03
- the remaining capacity for the 14.03 is now 9 hrs (24 - 2,5 -2,5 - 10)
- the WO gets this 9 hrs. at the 14.03
- now there is one 1 hr. processing time left for the WO
- this has now to be assigned at 15.03.
- As we have 50% utilisation the time is planned from 0:00 - 02:00




Beas\Production\Configurator
2019-05-02
16413
1
Configurator: Formula Active in Routing
beas 9.3H-002-023-000 / beas 9.3-002-023-000 / beas 9.3-001-032-000 / beas 9.3H-002-014-000
Beas\Production\Configurator
Function:

In routing position you can define a formula for operation active / not active

 
 

PAST: 
This works for creation of work order, but not in Pre calculation and Item Creation in flexible way

NEW: 

Pre Calculation
beas 9.3 PL 2: The Routing position will be transferred always to Pre Calculation and define this as active or not active
beas 9.3 PL 1: The Routing position will be transferred only, if this an active routing position

Work order:
if you define result "N" in the formula, the System don't insert the routing Position in the Work order. 
If you activate  Configuration wizzard - Production - Create - Apply inactive work order sequence

Item Createn (Pre Calculation)
beas 9.3 PL 2: if you define result "N" in the formula, the System don't insert the routing Position in the Work order. If you activate  the new setting: Configuration wizzard - Production - Product Configurator - Apply inactive work order sequence
beas 9.3 PL 1: The Routing position will be transferred only, if this an active routing position

Attention: 
In beas 9.3 PL 2 you have additional the possibility to define Yes|No values. See this picture

2019-02-27
20310
1
HANA, Product Configurator, Creation of New Items not possible due to Syntax Error
beas 9.3H-001-033-000 / beas 9.3H-002-015-000
Beas\Production\Configurator > Zendesk id: 78206
Function:

Configurations - Product Configurator
Here it is possible to create a new Item with the "Item create" button



PAST: beas displayed only an OK message in the HANA Version
Unable to end SQL transaction
select count ( *) FROM "OITM" WHERE "ItemCode" like '0004070-03020-005' + '%'


NEW: Fixed

Beas\Production\Workorder
2019-11-11
19691
1
WIP Balancing, 9.3 P/L Booking Logic
beas 9.3-001-031-000
Beas\Production\Workorder > Zendesk id: 77169
Function: Wrong WIP balance for old WO


PAST: With the last version of beas, if Profit & loss accounts is active, Beas generates new journal entries. The problem is that if we try to close a WO created with the previous version, the created journal information is not correct.
Important: this problem is only reproducible with an old WO that was closed with the last version.

NEW: beas creates journal information correctly.

Bug fixed.

Workaround TIP: You can downgrade Beas version to close opened work orders and then install new version to continue working without issues.

Expected result: No error message should appear.
2019-05-02
18806
1
Negative BOM Receipt Document is not linked to the Time Receipt
beas 9.3-002-011-000 / beas 9.3-001-030-000 / beas 9.3H-001-030-000 / beas 9.3H-002-011-000
Beas\Production\Workorder > Zendesk id: 74410
Function: Time receipt with Negative BOM

PAST: beas did not link negative BOM to created time receipts.



NEW: beas generates the right link to created receipt.
Bug fixed.

2019-05-02
15875
1
(jourerr1001) Error during journal entry add process. Error: (-5002) Invalid number of rows
beas 9.3H-001-025-000 / beas 9.3H-001-020-000 / beas 9.3-001-030-000 / beas 9.3-001-020-000 / beas 9.3-001-025-000 / beas 9.3-002-001-000 / beas 9.3H-002-001-000
Beas\Production\Workorder > Zendesk id: 66668

Environment: This problem is reproducable only with SAP 9.3 PL6 version (or higher). Additionally parameter "Accounting with balance Sheet Accounts and Profit & Loss Accounts" must be active.



Each time a Goods issue or goods receipt linked with a work order is generated, the system shows the following error message:
(jourerr1001) Error during journal entry adding process. Error: (-5002) Invalid number of rows 
Current Window: issue (program\reservation_set_master.psr) Function 
ret=(-5002) Invalid number of rows 
base_doctype=wo
belnr_id=1000084
belpos_id=10
source=ue_reservation.of_issuewo_updatejournalentry
saperrorid=(-5002) Invalid number of rows 

The reason for this error is that from 9.3 PL6 version SAP does not allow to modify existing journal entries (in previous version this functionality was available)
SAP explains this modification in this note:
https://launchpad.support.sap.com/#/notes/2699119

Internally, we generated an article to clarify this situation:
https://support.boyum-it.com/hc/en-us/articles/360011021893-Incompatibility-with-SAP-9-3-PL06-when-using-Profit-Loss-Accounts-on-Production-Order-Documents

As a workaround in the beas application we have developed the following functionality:

When a goods issue or goods receipt is created in the system linked to a work order, SAP generates a journal entry with information related to stock transaction (Without profit & loss accounts information). To solve this we need to do the following:

1. Create a new journal entry as cancellation of a created SAP journal entry.
2. Create a new journal entry with the original information and also add profit & loss accounts.
3. Link this new journal entry in beas and remove old links to previous journal entry.

2019-05-02
19588
1
SAP alternative material does not work in new beas version
beas 9.3-002-014-000 / beas 9.3H-001-031-000 / beas 9.3-001-031-000 / beas 9.3H-002-014-000
Beas\Production\Workorder > Zendesk id: 76376
Past:
If any item had alternative items defined in SAP, clicking in the alternative icon in the WO structure did not display anything before this patch.

Now: Problem is fixed.


 

 
Beas\System and Other\Framework
2019-03-05
19842
1
Product configurator reduce time loading large script
beas 9.3-001-031-000 / beas 9.3H-001-031-000
Beas\System and Other\Framework > Zendesk id: 70762

New beas script command 


#include=<filename>

with this command you can load files in which you defined own global functions

test.src
global function hello
messagebox=hello world
end global


#include=test.src
hello()

-> display messagebox with "hello world"

This function can load a large file in short time
Example: If you need many functions for configurator, you can use this command. It can load over 5000 functions in less than 100 ms on a fast machine.
Beas\Warehouse Management
2019-11-11
19733
1
Error: making stock transactions from beas into an SAP bin location warehouse
beas 9.3-001-031-000 / beas 9.3H-001-031-000
Beas\Warehouse Management > Zendesk id: 75804
Function:

Manual receipt and Manual issue on an SAP WareHouse with Serial- or batch-managed item
mw_manuell_buchen
 

PAST: beas displayed only an error message:
"SerialAndBatchNumbersBaseLine"; specify a valid "SerialAndBatchNumbersBaseLine"

NEW: Fixed.
Beas\Warehouse Management\Item Master Data
2019-05-02
16124
1
Item master data: change of geometrical values in "Purchasing data" are copied to "Sales data"
beas 9.3H-002-013-000 / beas 9.3H-001-031-000
Beas\Warehouse Management\Item Master Data > Zendesk id: 67334
Function:

Item Master Data - Purchasing Data - Changing Dimension fields (Length, Width, Height, Volume)

 

PAST: if you changed one of these fields, beas changed this in Sales Data Tab too. This was wrong functioning.

NEW: beas does not change anything in Sales Data Tab if you change one of these fields.
New button ">>" right of field "Length". If you click on it, beas copies all Dimension information to Sales Data Tab.
In this way it is working in the same way as SAP Item Master Data Window.