on ‎2025 Jan 20 9:44 AM
Hello NetWeaver ABAP basis community,
during a CTS transport import (done by STMS_IMPORT), there is the step "Report and screen generation" (example of steps during import is here) which starts to compile the imported objects.
We like to disable this step per transport, per system whatever is possible. Does anybody know if/how this could be possible ?
Thanks & best regards,
Matthias
I darkly remember a option in SAINT/SPAM where it was possible to set somewhat like "always", "as SAP requests", "never" but this seems not available in STMS for "regular" (no SPAM/SAINT) transports.
Request clarification before answering.
I'm not sure but you may try the transport profile parameter BLOCK_LOAD_GENERATION (file DIR_TRANS/bin/TP_<domain>.PFL). Its possible values are LOCKED and DELAYED. It affects the whole system. It's described in the SAP note 1899663 - ABAP loads with errors following import during routine operations.
I understand this parameter is used in case the kernel detects that the ABAP Load needs to be regenerated, but it's not clear whether it's used when the concerned program is executed/loaded or when the generation is forced (especially in the case the program is transported).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks a lot. That is at least a way to try
It seems to be a way to minimize the import duration in phase "move nametab" as no one else could trigger a JIT compile blocking the import "move nametab".
There is a predecessor note 2868400 - ABAP program load generation locks during transport
We will try and see if import times will decrease then I'll report the findings
| User | Count |
|---|---|
| 11 | |
| 6 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.