Nope, Let's skip download at initial stage.
Surprised? Yes, It's rare tick.
We will also upload the same before starting note implementation as it would be the mandatory prerequisite. Most of the basis peoples would do the same (even myself) until I found an weird scenario due to some CI mistakes.
Assume, I got vulnerability/CVE fix for one SAP Note - Basis 758 - Affects all Support Package.
Assume, SAP released with two CIs
SAP notes requires TCI only for specific SPs only.
Say
CI 1 - Basis 758 - SP 1 - SP 2 -> Only Correction Instructions exist - TCI not applicable/required for this SPs. No download option available for TCI.
CI 2 - Basis 758 - SP 3 - SP4 -> Correction Instructions as well as TCI exists. We can download TCI file.
My Basis version 758 SP2.
In this case, TCI file not required but I have downloaded TCI file by mistake asusual (all basis peoples) and uploaded since we won't have any specific information in Note descriptions usually.
Only way to catch - By seeing CI when downloading TCI file only. I missed the same. I noticed this later but before note implementation.
Only way to catch - By seeing CI when downloading TCI file only. I missed the same. I noticed this later but before note implementation.
✨TCI Component Prerequisites checks were released with ≠ (Not equal to) SP5 Import prerequisite condition instead of providing SP 3- SP 4 correct condition.
This resulted in situation that TCI file is applicable to import even when it's not required/applicable to our SP2 release.
Usually, These kind of ≠ (Not equal to) conditions valid if TCI files requires for all SPs till Resolution SP - Say SP1 - SP4 then we can have ≠ SP5 condition for TCI since SAP would have released resolution/fix on SP5. Note would be in "Cannot be Implemented" status.
I have raised case to SAP. SAP changed TCI condition to SP3 - SP4 instead of ≠SP4 and released in shorter span of time.
Anyhow there is no impact since we shouldn't import TCI files manually for SAP Notes via SPAM. We just found this CI mistakes.
This resulted in situation that TCI file is applicable to import even when it's not required/applicable to our SP2 release.
Usually, These kind of ≠ (Not equal to) conditions valid if TCI files requires for all SPs till Resolution SP - Say SP1 - SP4 then we can have ≠ SP5 condition for TCI since SAP would have released resolution/fix on SP5. Note would be in "Cannot be Implemented" status.
I have raised case to SAP. SAP changed TCI condition to SP3 - SP4 instead of ≠SP4 and released in shorter span of time.
Anyhow there is no impact since we shouldn't import TCI files manually for SAP Notes via SPAM. We just found this CI mistakes.
We will definitely get error "Transport TN835 or TN872: The transport based correction XXX of SAP Note is not available" if we didn't upload TCI file. It will show TCI file name as well.
Although it's good practice to crosscheck and upload TCI file prior to note implementation, we will get surprised with these kind of rare scenarios.
Do check TCI CIs and keep ready with download -> Just start implementation of note -> let note fail with "TCI not available" error -> Upload the same in system -> Retry Note Implementation.
Do check TCI CIs and keep ready with download -> Just start implementation of note -> let note fail with "TCI not available" error -> Upload the same in system -> Retry Note Implementation.
Note 2499947 - TN835 or TN872:The transport based correction of SAP Note is not available vers12
💫 It's not an error - It's an indirect hint that SNOTE specifies which TCI file actually required for the system to upload.
Let's welcome this error !
Thanks for visiting !!!
No comments:
Post a Comment