One of the data sources for One Exposure Hub (table FQM_FLOW) is a bank statement. In this article I tried to describe the logic by which to execute various operations with the Bank statement updates a table FQM_FLOW.

  • Manual entry (tr. ff67)/ download (FF_5) Bank statements.

Update the data in the table FQM_FLOW is performed when the bank statement input/load             with posting. In open FI 00002810 (OPEN_FI_PERFORM_00002810_E) triggers a method             call CL_FQM_ADAPTOR_BS=>PROCESS_ITEM2FQM. In this method, the filled dimensions           for the table FQM_FLOW.

The rules for filling these attributes are common for all flows:

FQM_FLOW-CERTAINTY_LEVEL = ‘ACTUAL’

FQM_FLOW-OWNER = ‘BS’

FQM_FLOW-ORIGIN_DOCUMENT_ID = RFEBKO-KUKEY.

FQM_FLOW-ORIGIN_TRANSACTION_ID = CONCATENATE RFEBKO-KUKEY FEBEP-                   ESNUM

The logical tree for creating flows:

In the metod CL_FQM_ADAPTOR_BS=>ON_SAVE_REQUESTED locate call BADI                           BADI_FQM_FLOW_ADJUST_CORE. In the metod                                                                             BADI_FQM_FLOW_ADJUST_CORE=>ADJUST_FLOWS possible to change flows before               save to the FQM_FLOW.

  • Posting 1-st area of bank statement (tr. FF67/FF_5/ FEB_BSPROC).

In this case, the system fills the field FQM_FLOW-DELETED = ‘X’ for all flow created for this           position of the bank statement. Filling the attribute DELETED is performed by the batch job             for the program FCLM_FLOW_BUILDER.

  • The reversal FI document of the first region of the Bank statement (tr. FB08).

In this case nothing happens. The value of ‘X’ in the attribute FQM_FLOW-DELETED not                cleared. I think that the bug is still not fixed SAP.

  • Deleting the Bank statement (progr. RFEBKA38).

In this case nothing happens. In my understanding in this case system needs to set the                   value of ‘X’ in the flows in FQM_FLOW which created on the basis of the deleted bank                     statement. I think that the bug is still not fixed SAP.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply