Merge / Parallel Development Streams (Continued)
|Destination portal web service port|| In order for Transport Expresso to perform conflict analysis for portals objects it requires a web service to enable it to read the object version information.
This is the port used by the web service for this purpose.
|Transport target for merge requests|| This sets the transport target for merge requests created by Transport Expresso allowing merge transports to be handled via a different transport route if required.
If not set the default value from TMS will be used.
|Base DATE for portal conflict analysis|| For portals objects that have never been imported this is the base date for checking if any local changes have been made. If a change has been made after this date the object is considered to have been amended for conflict analysis purposes.
Once an object has been imported into a system this import date / time is used for conflict analysis checks.
|Base TIME for portal conflict analysis||Base time used in conjunction with the base date in the above process.|
|Conflict analysis for portal objects||Check to activate conflict analysis functionality for portals systems.|
|Merge Size||Select whether you want one merge transport for every originating transport (1:1), a big one with everything (Consolidated) or one per import run (By Import Run)|
|Merge Path||Select which path the transport forms for the merges will be created. Leave it blank if you want to create them manually.|
|Merge Type||Select which Type you want Merge Transport Form to be allocated to. If not set, the merge will get the type of the first transport merged.|
|Merge Group||Select which Group you want for the Merge Transport Form to be allocated to. If not set, the merge will get the group of the first transport merged.|
|Stop on BW post-processing error||This option controls whether TE Merge process will stop or continue when BW postprocessing fails|
|Merge Task||Select which Task the Transport Form should be associated with. If not set, the merge will get the task of every transport merged.|
|On Error||Controls whether TE Merge will stop, continue or skip any other errors encountered during TE Merge process.|
|For 1:1 merges automatically copy over transport form manual step details||Check if you want Manual Steps to be added in the Merge Transport Form in 1:1 merge scenario; it not relevant to the Consolidated Merge scenario.|
|Unconditional Modes||These options allow you to apply various unconditional modes to all transport requests imported into this target system.|
|Pre-import logical command|| Transport Expresso supports transporting between SAP systems that do not share common underlying transport directories.
Before importing a transport request, Transport Expresso checks whether the required transport files are available and, if not, automatically copies the files to the target transport directory.
If further import pre-processing is required, you may use this option to invoke an SAP logical command (transaction SM69) to call your own script before the import is performed. You can choose whether the script is invoked on the domain controller or the target SAP system.
|Post-import logical command|| This option is similar to the previous option. It allows for a logical command to be called after a transport request has been imported into a target system.
This option might be used for copying transport logs that were created by the import process back to the transport directories of the source SAP development system.
Thanks for your feedback.