Introduction
In this blog we will discuss about “serialization of AIF messages“. We will see what is this serialization and why it is required while resuming SLT replication.
Background
You are using the Central Finance scenario and for technical reasons you had to pause or deactivate the SLT replication into the Central Finance system. Or you plan to start replication with SLT initial load. Meanwhile many postings have accumulated in the source system for replication.
You want to activate the replication (again).
The AIF feature for serialization of AIF messages ensures that postings are processed in the right order in the Central Finance system.
For example, a clearing document is reset and reversed in the source system. These two steps are replicated to the Central Finance system as two separate transactions. The resetting must be processed first, otherwise the reversal runs into an error. The AIF serialization uses a time stamp set in the source system to determine the correct order. It ensures that the AIF message with the lower time stamp is processed successfully first.
Note : For non-SAP source systems this serialization is generally taken care in Magnitude or any other customer development. So, please confirm if you need to take care of serialization separately in the cFiN system ?
Caution
If many postings have accumulated in the source system, SLT may transfer the data in several packages using parallel jobs (depending on the configuration). Therefore, the two transactions may end up in different packages and be replicated out of order. If the second transaction is processed before the first has been transferred to AIF, the serialization cannot identify the predecessor.
To ensure correct serialization, the processing of AIF messages must be deactivated until the accumulated posting data has been transferred to AIF.
Process
The recommended procedure depends on the AIF Application Engine that is used for the affected AIF interface. To find out which application engine is used start transaction /aif/cust and go to Interface Development -> Additional Interface Properties -> Specify Interface Engine -> column ApplEngine.
Note: Application engine ‘XML, bgRFC runtime’ is supported starting with S/4HANA 2023, only.
ApplEngine = ‘XML’ or ‘Structured Persistence’:
In the Central Finance system, deactivate the AIF runtime configuration group that is used for the replication.
To identify the right runtime configuration group, go to the IMG of Central Finance at Central Finance: Target System Settings -> Set Up Systems -> Assign AIF Runtime Configuration Group to Replication Object (or start transaction SM30, enter view name V_CFIN_AIF_RT_CF and click the Display button).
To deactivate the configuration group, go to the SAP Menu at Cross-Application Components -> SAP Application Interface Framework -> Administration -> Configuration -> Runtime Configuration Group. Unset the “Runtime Cfg Active” flag and save the change.In the SLT server system, activate or resume the replication for the corresponding table. New AIF messages will be created by the replication with the status “in process”.Monitor the replication, either by checking the contents in the SLT logging table in the source system (number of entries should decrease) or the AIF monitor.In the Central Finance system, when the accumulated postings have been transferred, activate the AIF runtime configuration group again (see step 1).In the Central Finance system, execute ABAP report /AIF/PERS_RUN_EXECUTE. On the start screen of the report, set the option “Include runs in status New”
ApplEngine = ‘XML, bgRFC runtime’:
In the Central Finance system, deactivate the AIF processing for the bgRFC subprocesses that are used for the replication.
To identify the right bgRFC subprocesses, go to the IMG of Central Finance at Central Finance: Target System Settings -> Set Up Systems -> AIF Runtime Configuration -> Settings for bgRFC -> Assign Default bgRFC Subprocess to Replication Objects ( and Assign Specific bgRFC Subprocess for Accounting Interface, potentially ).
To deactivate the processing for a subprocess, use the activity ‘Activate Processing per Subprocess‘ in same customizing folder by creating a new entry for the process/subprocess entity and checking the ‘AIF bgRFC Processing Inactive Indicator’.In the SLT server system, activate or resume the replication for the corresponding table. New AIF messages will be created by the replication with the status “in process/waiting to be processed”.Monitor the replication, either by checking the contents in the SLT logging table in the source system (number of entries should decrease) or the AIF monitor.In the Central Finance system, when the accumulated postings have been transferred, activate the processing for the bgRFC subprocesses again (see steps 1 and 2) by either unchecking the inactive flag or removing the entry from the list.In the Central Finance system, execute ABAP report FINS_CFIN_AIF_BGRFC_RESTART and provide the affected subprocess(es).
Conclusion
Do take care of the above process to make sure that after any SLT pause/resume situation, documents are processed in the order in which they were posted in the source systems.
Feel free to reach out to me on Abhishek Singh | LinkedIn.
Please do provide your valuable feedbacks and if you have any questions, please contact me.
Supporting documentation and information
Please follow me on the forum for more SLT-cFiN related contents: abhishek_singh1404_195
Follow this space for related contents: SAP Landscape Transformation replication server | SAP | SAP Blogs
Introduction In this blog we will discuss about “serialization of AIF messages”. We will see what is this serialization and why it is required while resuming SLT replication. BackgroundYou are using the Central Finance scenario and for technical reasons you had to pause or deactivate the SLT replication into the Central Finance system. Or you plan to start replication with SLT initial load. Meanwhile many postings have accumulated in the source system for replication.You want to activate the replication (again).The AIF feature for serialization of AIF messages ensures that postings are processed in the right order in the Central Finance system.For example, a clearing document is reset and reversed in the source system. These two steps are replicated to the Central Finance system as two separate transactions. The resetting must be processed first, otherwise the reversal runs into an error. The AIF serialization uses a time stamp set in the source system to determine the correct order. It ensures that the AIF message with the lower time stamp is processed successfully first.Note : For non-SAP source systems this serialization is generally taken care in Magnitude or any other customer development. So, please confirm if you need to take care of serialization separately in the cFiN system ? Caution If many postings have accumulated in the source system, SLT may transfer the data in several packages using parallel jobs (depending on the configuration). Therefore, the two transactions may end up in different packages and be replicated out of order. If the second transaction is processed before the first has been transferred to AIF, the serialization cannot identify the predecessor.To ensure correct serialization, the processing of AIF messages must be deactivated until the accumulated posting data has been transferred to AIF. Process The recommended procedure depends on the AIF Application Engine that is used for the affected AIF interface. To find out which application engine is used start transaction /aif/cust and go to Interface Development -> Additional Interface Properties -> Specify Interface Engine -> column ApplEngine. Note: Application engine ‘XML, bgRFC runtime’ is supported starting with S/4HANA 2023, only. ApplEngine = ‘XML’ or ‘Structured Persistence’:In the Central Finance system, deactivate the AIF runtime configuration group that is used for the replication.To identify the right runtime configuration group, go to the IMG of Central Finance at Central Finance: Target System Settings -> Set Up Systems -> Assign AIF Runtime Configuration Group to Replication Object (or start transaction SM30, enter view name V_CFIN_AIF_RT_CF and click the Display button).To deactivate the configuration group, go to the SAP Menu at Cross-Application Components -> SAP Application Interface Framework -> Administration -> Configuration -> Runtime Configuration Group. Unset the “Runtime Cfg Active” flag and save the change.In the SLT server system, activate or resume the replication for the corresponding table. New AIF messages will be created by the replication with the status “in process”.Monitor the replication, either by checking the contents in the SLT logging table in the source system (number of entries should decrease) or the AIF monitor.In the Central Finance system, when the accumulated postings have been transferred, activate the AIF runtime configuration group again (see step 1).In the Central Finance system, execute ABAP report /AIF/PERS_RUN_EXECUTE. On the start screen of the report, set the option “Include runs in status New”ApplEngine = ‘XML, bgRFC runtime’:In the Central Finance system, deactivate the AIF processing for the bgRFC subprocesses that are used for the replication. To identify the right bgRFC subprocesses, go to the IMG of Central Finance at Central Finance: Target System Settings -> Set Up Systems -> AIF Runtime Configuration -> Settings for bgRFC -> Assign Default bgRFC Subprocess to Replication Objects ( and Assign Specific bgRFC Subprocess for Accounting Interface, potentially ).To deactivate the processing for a subprocess, use the activity ‘Activate Processing per Subprocess’ in same customizing folder by creating a new entry for the process/subprocess entity and checking the ‘AIF bgRFC Processing Inactive Indicator’.In the SLT server system, activate or resume the replication for the corresponding table. New AIF messages will be created by the replication with the status “in process/waiting to be processed”.Monitor the replication, either by checking the contents in the SLT logging table in the source system (number of entries should decrease) or the AIF monitor.In the Central Finance system, when the accumulated postings have been transferred, activate the processing for the bgRFC subprocesses again (see steps 1 and 2) by either unchecking the inactive flag or removing the entry from the list.In the Central Finance system, execute ABAP report FINS_CFIN_AIF_BGRFC_RESTART and provide the affected subprocess(es). Conclusion Do take care of the above process to make sure that after any SLT pause/resume situation, documents are processed in the order in which they were posted in the source systems. Feel free to reach out to me on Abhishek Singh | LinkedIn. Please do provide your valuable feedbacks and if you have any questions, please contact me. Supporting documentation and information Please follow me on the forum for more SLT-cFiN related contents: abhishek_singh1404_195Follow this space for related contents: SAP Landscape Transformation replication server | SAP | SAP Blogs Read More Technology Blogs by Members articles
#SAP
#SAPTechnologyblog
![Zugriff auf interne Tabellen mit Table Expressions [deutsch]](https://i3.ytimg.com/vi/vMECFG43-EI/hqdefault.jpg)
![Access to Internal Tables with Table Expressions [english]](https://i3.ytimg.com/vi/zTNLR27UMkA/hqdefault.jpg)
+ There are no comments
Add yours