We have some packages that were backed out and were never backed in and is in committed status. What is the best practice?
When you have packages that were committed in backed out status, you can't do nothing more with those package.
As a result, only the element's source are at the level delivered by this package, the element's load have been keep at previous level because of the back out.
The best is to create a new package to deliver again the elements.
Generate element in place
Now, it is possible to back out a single element and you still back out a full package if you prefer.
If you delivered elements PGM1, PGM2 and PGM3 from DEV to environment PRD with a package PKG1 and want to Back out package PKG1 because PGM2 is in error; you can:
1 - Backout element PGM2 from Package PKG1
2 - Fix PGM2 into DEV
3 - Create a new package PKG2 for PGM2
4 - Execute package PKG2
1 - Backout Package PKG1 and do not want to Back in Package PKG1 for any reason
2 - Fix PGM2 + generate option copyback PGM1 and PGM 3 into DEV
3 - Create a new package PKG2 for PGM1, PGM2 and PGM3
1 - Backout Package PKG1
4 - Back in package PKG1
5 - Execute package PKG2
Now if you want to Back out a PKG1 while another PKG2 has been executed, you must:
1 - Backout Package PKG2
2 - Backout Package PKG1
In fact, you have to respect the packages chain and take in to account the status of a package.
Let me know if this clarify?
Thank you Ollivier. Your write-up is very helpful.
Thanks for your feedback.
I'm not aware of what customers use to do.
From a functional perspective, there is absolutely no difference. That is, the outputs introduced by the package were wrong and were corrected by a subsequent package. It doesn't matter whether the original package was backed out or backed in.
Maybe for documentation purposes it would be better to leave the original package backed out. This way its backout and backin dates better document the fact that it was a wrong package that had to be backed out.
Regards - Eduard
Hello Eduard. Thank you.