I hope you will check if there is water in the pool before you jump from a springboard.
Honestly, you have to do some homework before you start. And this homework is at least reading the big docu SAP Library - Introduction to Data Archiving (CA-ARC)
Already the thickness of this docu can give you the impression that archiving is not just a single transaction which is just running by itself.
of course you need to do some customizing, archiving is not a transaction to make an entry error invisible, archiving is used to KEEP oboslete data for audits etc. outside the production data base.
Archiving is a process, archiving needs a project as it is not just a technical activity. you need a sense for the data, for your processes, for the legal requirements.
the link you referenced had itself mentioned an OSS note.
Instead of asking this question you could have checked this OSS note and would have found the answer yourself.
Apropos OSS notes, from my point of view are the OSS notes one pillar of archiving. It is essential to have your programs up to date before you start archiving to avoid any unrepairable surprise.