Most events from workordermanagement / stockmanagement were not working on WEB / BeasServiceLayer side.
Reason: The operation was based on a completely different logic.
With Beas 2020.05 we created documentation for the functionality.
Additionally, support will be added to this in all transactions with a defined concept.
Problem:
It is not possible to deliver 100% compatibility.
The system will check the "old" event name, as well, and try to deliver all old variable names.
Example
Old syntax:
workordermanagement.src
fucntion receipt
// Variable e_belnr_id,e_belpos_id,e_pos_id
end function
New syntax
workordermanagement.src
function ReceiptLine
// Variable WoDocEntry,WoLineNumber,WoLineNumber2
// BUT function receipt with e_belnr_id and so on is working too
end function
What is changed:
- the script is executed in a sandbox
- all changed variables are only visible inside the sandbox, but you can see all variables outside it
- userevents have the exact same functionality in all different booking processes
(before: different functionality always causing errors)
Compatibility to old variant is > 95%
|