This blog talks about Cross-System Process Control (CSPC) – why is it important, high level Implementation steps and more onto troubleshooting the CPCS token issues.

When using Central Payment in a Central Finance scenario, you run payment and clearing activities in the Central Finance system. Invoices are replicated from a source system to the Central Finance system via SLT and technically cleared in the source system. Thus the entire processes are not confined to one system, making it complex for the dependent process (post Invoice), challenging the integrity in distributed systems.

Few challenges are:

• The actual clearing status of an invoice is not available in the source system. It is only available in the Central Finance system.
• Business processes that depend on the actual clearing status of invoices in the source system may be impacted.
• The mechanisms that are used to lock and validate the clearing status in a standalone system cannot be used in a cross-system scenario

This is where the framework for controlling cross system process are required to allow the smooth and consistent flow of business processes.

How CSPC works

CSPC is mandatory for CPAY, it controls FI invoices, SD invoices, MM invoices, and down payment requests by issuing a virtual token to control whether a system is permitted to execute certain process steps for a particular object. After activation of Central Payment and CSPC, token is created automatically for each new item and can only be active in one system at a time. Without token, process steps involving the item cannot be performed. This ensures that only one system at a time can execute a process step involving the item.

Token Understanding

There are two phases to create token for the open items.

• Create tokens for the AP/AR items which are created before CSPC activation: It belongs to the CSPC initialization phase, CSPC initialization report and CSPC token fix report can be used in this case to create the initial token with the token counter 0.
• Ongoing create tokens for the AP/AR items after CSPC activation: It is the normal ongoing creating token phase, the token will be created along with the document creation and its initial token counter will be from 1

Table: CFIN_CSPC_TOKEN

CSPC Token Transfer Data are written in Table CFIN_CSPC_TOKEN in source & target table.

1. When system working smooth, the Transfer counter should be same in both the source & Target system.

2. For the historical open items, the tokens are created with transfer counter 0 for both the system via Initialisation report.

3. When the token are created through online replication and document is successfully transferred from source to target, Transfer counter should be 1 in both the system.

4. Incase of reversal, token will be 2 in source & Target.

5.Difference in the Transfer counter will result in an error message in the token correction report – FINS_CFIN_CPAYCSPC_F

Implementation Steps

I .Central Finance System

1. Set up RFC Connections for Cross-System Process Control
2. Configure Remote Systems for Cross-System Process Control

II. Source system

1. Set up RFC Connections for Cross-System Process Control
2. Configure Remote Systems for Cross-System Process Control

If you cannot find CSPC relevant IMG activities in your source, you can use below alternative approach to do the configurations:

• Set Up RFC Connections for Cross-System Process Control via transaction SM59.
• Configure Remote Systems for Cross-System Process Control in the view cluster ‘VC_CSPC_LSYS’ via transaction SM34.

Historical Item Handling

Central Finance System

1. Run the CSPC initialization program FINS_CFIN_CPAYCSPC_I to create token for the historical open AP/AR item. Without token, payment or clearing cannot be done for these items. IMG path: CFINIMG under Central Finance: Target System Settings,  Central Payment  Cross-System Process Control for Central Payment)
2. Go to the activity Initialization Status Monitorand check the processing results by package. IMG path: in transaction CFINIMG, under Central Finance: Target System Settings  Central Payment  Cross-System Process Control for Central Payment

Troubleshoot

Error: Cross-System Process Control prevents the payment for Invoice xxxxxxx & xxxxxxx; see long text. Message class: FIN_CFIN_CSPC_CPAY – CSPC: Central Payment Message Class

Resolution: If token error occurs during payment or clearing the invoices you can run token correction report to fix token error. Run token initialization report to create tokens for these invoices, and then they could be paid/cleared in CFIN system.

Execute transaction code: FINS_CFIN_CPAYCSPC_F

Error: Request for CPAY ECQCLNT 300 100019000021222022001 denied due to 1 pending replications Message no. FIN_CSPC_FRW006.

Resolution: This kind of issue occurs in token correction report for the invoices which are created while CSPC is active but TRWPR function modules are not registered correctly, as a consequence token cannot be transferred to CFIN system during the replication. This mean token transfer counter in source system is greater than  CFIN system (refer to above Token number assignment understanding). CSPC consider the invoice as blocked in AIF and raise the message when you run token correction report, however there is no invoice blocked in AIF actually, this is the reason token correction report cannot handle this issue.

Check if TRWPR function modules are registered correctly?. If not run Program RFINS_CFIN_TRWPR_REGISTRATION.

Result should look like below

After the TRWPR function modules are registered correctly, this kind of issue will not occur for new invoices. Refer to next resolution steps if problem persist.

Error: A predecessor exists with MSGGUID 005056A3CF4F1EDCBEEBAA7B5B6AC889 in AIF interface /FINCF/AC_DOC/2.  Message no. FIN_CFIN_CSPC_CPAY015

Resolution: Check if TRWPR function modules are registered correctly, If not follow step no. 2.

If TRWPR FM is active, check the CSPC_TOKEN in both source and target systems in table CFIN_CSPC_TOKEN.  Transfer counter in source and CFIN system should both be 0 after running the token initialization or fixing report.  If the token transfer counter is 1 in source system, and the transfer counter is 0 in target system, it mean token transfer data being written in source system doesn’t reach the target system with replicated Fi transactions and target system’s CSPC token information is not updated with posting. In AIF message (Interface /FINCF AC_DOC), table SRC_DATA-CSPC_TOKEN is empty.

Next step is to analyse your GUID for CFIN_CSPC table using the program FINS_CFIN_AIF_ANALYZE to check if table CFIN_CSPC registered in the table structure.

If CSPC table is not generated, Error lies in SLT config. Check the settins I SLT for Migration object CFI_ACCHD_R/L. The functionality for transferring CSPC requires includsion of table CFIN_CSPC_TOKEN in replication. Follow Note 2985804

Post SLT fix, result should be

While CSPC is very handy and ensure cross control, it is equally important to take care of few critical things: perquisite notes in both source & target, follow the implementation/activation sequence  and proper handling of Historical items for token generation.

Pls keep in mind that above troubleshoot will help avoid the future occurrence of errors however token fixing report cannot fix already posted/replicated document issue. There is no right way to fix this issue. If you have to fix these disordered data, a workaround from technical perspective is to change DB table CSPC_TOKEN of the source system from transfer counter 1 to 0 (refer initial Token explanation)