on 2024 Jan 26 3:42 PM
Hi,
We recently implemented the S4 Hana Advanced Bank Statements Reprocessing tool.
We are basically using the Fiori apps "Manage Bank Statements", "Reprocess Bank Statement Items" and "Manage Processing Rules".
We are having problems with rules not working and activating simple rules such as using the document number in the Note to Payee to clear an open item. We've defined a processing instruction using the Interpretation algorithm 20 "Document Number Search" but that does not seem to work.
We have also tried to set break points in the classes CL_FAR_FEB_ALGORITHMS and CL_FAR_FEB_OPEN_ITEM_FINDER but those do not get triggered.
Anybody can help figuring out why that rule/algorithm does not kick in in the Advanced Bank statement processing app?
Thanks,
Fred
Request clarification before answering.
Hi,
first of all, have you double checked in the app Reprocess Bank Statement Items, by navigating into those items which did not clear any invoices. What the application log says? (You navigate into it and switch in the tab section to "Log", just to make sure that the rule conditions really match the processing rules)
If you find a message that it matches the rule then of course debugging would be the next step. For that though I would set the break point at the class CL_FAR_BS_ITM_REPROC_DPC_EXT in the method EXECUTE_BS_POSTING_PROPOSAL.
That method is basically always the starting point for any rule which has been applied to a bank statement item. There should be a method named find_open_items -> this is where we search for open items. This class and this method though have been changed over time so I cannot tell at which release you are and where you find this method.
You got two options how to debug this. The easiest option would be to use the Reprocess Bank Statement Items app. You navigate into that item which was not set to completed with the document reference in the memoline. You set the breakpoint first in the class: CL_FAR_BS_ITM_REPROC_DPC_EXT in the method: FIND_OPEN_ITEMS (in case you do not reach that break point try to set a breakpoint in /IWBEP/IF_MGW_APPL_SRV_RUNTIME~EXECUTE_ACTION this method is basically the starting point for any call on the reprocess bank statement items app).
Now when you set up the break point you are good to go. Simply go to the Reprocess Bank Statement Items app and navigate to that item, open it and select the algorithm which you want to use in the "Processing Instruction" field and click on the button "Allocate Open Items". (see attached screenshot) Now you should reach the break point.
The other way to debug this is a more technical way. What I do is: I create a copy from the automated rule. Then my user has the the same rule as a manual rule. Now you can see in the URL the UUID of this processing rule (in the URL you should find something like "....C_ARPostingRule(PostingRuleUUID=guid'<UUID>....". Save this because you'll need it later. Now write down that bank statement item which has not been posted. What you need is basically the bank statement short ID and the bank statement item (number).
The bank statement short ID is the value which is saved in the database table FEBEP it's the field KUKEY. You can also find this by simply navigating in the app Reprocess Bank Statement Item and check the URL you should file something similar like this: ".....BankStatement-reprocessItems?sap-ui-tech-hint=UI5&/2475/5....."
Here the 2475 is the short ID and the 5 is basically telling us that his is the fifth item of that bank statement (field ESNUM on table FEBEP). Of course you could also just add these columns on the list report view and you do not need to navigate into the item but if you check the log anyway as I proposed you can do this in one step.
Now go to the backend and execute the following report: rfar_bs_apply_rule.
Here you are asked now to enter the UUID of your manual rule, just enter it without the dashes in between so change it from 563243-GLASD23-DSFF233... to 563243GLASD23DSFF233....
and in the concatenated BS Item Key field you enter your short id and bank statement item number by also adding the leading zeros, so in my example 2475/5 that would be changed to: 00002475/00005
The short ID has a length of 8 and the statement item number of 5.
You have to check that you find the right spot in the coding where the posting is parallelized to increase performance. As already mentioned we have developed over the past years and extended and changed the coding but you should find it.
Hope I could help you.
Best,
Edrilan Berisha
SAP S/4HANA Cloud Financials Development
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.