| Integration transactions |  |
| Integration transactions can be split in two: Integration transactions details Temporary details, such as status information Post integration transactions to general ledger on a regular basis Performance of the integration process will decrease when the table containing the temporary details contains too much data. This data will be deleted during the posting process. Therefore, the integration transactions must be posted to the general ledger on a regular basis using the Post Integration Transactions (tfgld4282m000) session. Performance aspects Effect on CPU: Yes Effect on database growth: Yes Archive and delete integration elements and transactions Timely archiving of integration elements and transactions to an archive company using the Archive / Delete Integration Elements and Integration Transactions (tfgld4283m000) session is recommended. Depending on the data sizes of the specific tables, integration elements must be removed from the production environment as soon as possible. Whether integration elements should also be archived depends on the users’ requirements. Performance aspects Effect on CPU: Not applicable Effect on database growth: Yes Related topics Integration transactions |