TM transactional documents do have numbers, which are typically drawn from an internal number range. This number range is finite, and the status should be monitored.
This note describes how to monitor the current status using the report RSNUMHOT.
I...
TM offers the possibility to use text schemas to maintain and propagate texts from predecessor documents. Dragos did a great job describing important parts here.
So far it was problematic to define a text schema for item based text determination. So ...
Enhancing the text determination explanations by Dragos here, I wanted to share some insights on top of that focusing on texts coming from ERP documents.
In my example I will define a text Type TM_D1 which takes over the Delivery Note Text from a Pu...
Using party role codes / partner functions is a not so exotic use case, e.g. the entry for a certain function might be needed.
There is something special to consider:
The role codes / partner functions are actually language specific. E.g. when logg...
In TM we have customers of all sizes and document structures, this includes documents with a lot of items. I mean, in the 4-5 digits space...
There are some important settings affecting the UI performance in such a scenario, and this is the focus of...
thanks for sharing, I think you should always follow the retrieve-approach instead of BOPF-selects to include possible transactional changes. As far as I know there is also a way to adapt planning settings transactionally (e.g. planning horizon), I w...
In that exact example this might be an actual useful differentiation, if intended: sales_order_header refers to Sales Order, while sales_document_header includes Sales Order and Scheduling Agreements...
;-)
