Skip Import and auto Activation feature for XI transports
[CMS] [CTS+] [PI] [XI]
Related:
- Problems with German language in XI systemsSymptom Instead of the correct language according to the user...
- PI CTC: Additional ccBPM cleanup required after system copySymptom After a SAP NetWeaver PI System Copy some ccBPM...
- FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP AdapterSymptom You are experiencing problems with the SAP XI 3.0...
- FAQ XI 3.0/ PI 7.0/ PI 7.1/ PI 7.11/ PI 7.2 RFC AdapterSymptom FAQ XI 3.0 RFC Adapter, PI 7.0 RFC Adapter,...
- PI CTC: New Java RFC destination for ccBPM monitorSymptom For ccBPM Monitoring a new Java RFC destination “BusinessProcessEngine_RFC”...
- Patch Process for SAPXIGUISymptom After deployment of new patch of only SAPXIGUI archive,...
- PI CTC: Downport PI Upgrade CTC TemplateSymptom The “PI System Upgrade” CTC Wizard Template is not...
- PI CTC: SSO configuration for PISymptom SSO Setup is not part of the default PI...
Symptom
Integration Directory:
———————-
After the re import of same transport request (CTS)/ tpz (file)/ transport order (CMS) into a XI system configured as a target system in the transport landscape then the user observes that there is no new changelist created after the import when navigated to changelist tab.
Other terms
XI, PI, CMS, CTS+
Reason and Prerequisites
Prerequisite:
-> Export a changelist / SWCV or directory objects based on the application either repository or directory from the system defined as source system in the transport landscape.
-> Import the transport request (CTS)/ tpz (file)/ transport order (CMS) into target XI system.
-> Re-import the same transport again.
Solution
Skip Import:
———–
Skip the import if the changelist or tpz is already part of the system.
AII Properties:
com.sap.aii. ibdir.core.transport.import.overwriteMode = [true|false]
[for directory]
com.sap.aii. ibrep.core.transport.import.overwriteMode = [true|false]
[for repository]
If this is true then an import will be allowed to overwrite former imports of the same content file/stream. If the value is false then the second import of the same transport file/stream will be ignored (without throwing an exception). The default is false (i.e., new behaviour).
Note:
-> In case of CTS+ if the abap transport request contains one or more changelists then the skip import is performed on each changelist level i.e., by checking if that changelist is already imported or not imported but not on the abap transport request.
-> In case of directory content imports if the import is skipped (based on above flag setting) then a new changelist for that import is not created in target system.
-> In case of repository imports the user will not find any significant difference if the above flag is either enabled or disabled and always gets a success result after import of same transport again and again but a performance optimization is done on the back end to complete the import in a short time.
Auto Activation:
—————-
Automatically activate the changelist created after the directory import.
AII Properties:
com.sap.aii.ibdir.core.transport.autoActivation.showFlag = [true|false]
[ only for Directory ]
Specifies whether the flag for the automatic activation of changelist in the directory should be shown
com.sap.aii.ibdir.core.transport.autoActivation.default = [true|false]
[ only for Directory ]
Specifies the default value for the automatic activation of changelist in the directory.
** The above two properties for skip import and auto activation can be overwritten by the user during file import in the UI by the help of a check box shown in the import dialog when the file is present on the server. In case of CMS or CTS import this will be used as per the flag setting in the ExchangeProfile.
Note:
-> If the automatic activation fails then the old behaviour is shown (import result: object in open changelist).
Valid Releases:
————–
NW2004s SP14 and subsequent SPs
XI 7.01 and subsequent SPs
PI 7.02 and subsequent SPs
PI 7.10 SP6 and subsequent releases and SPs