We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-acct] Electronic Bank Statement - Measure Hit Rate

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from wnash7658 on May 6 at 5:45 PM
This would be a good KPI actually. I think maybe a SQVI query and review these tables:-

FEBKO : Electronic Bank Statement Header Records
FEBEP : Electronic Bank Statement Line Items
FEBRE : Reference record for electronic bank statement line item
FEBCL : Clearing data for an electronic bank statement line item

Regards,


Waza

---------------Original Message---------------
From: Reinier_Baai
Sent: Wednesday, April 30, 2014 6:25 AM
Subject: Electronic Bank Statement - Measure Hit Rate

For some time we are making use of the Electronic Bank Statement functionality within SAP.

Through t-code FF.5 we are uploading electronic bank statements in SWIFT MT940 with field 86 structured format.

In order to have incoming payments processed automatically we have defined algorithm XBLNR number interval.

Statement line items which require further processing are processed further through t-code FEBAN.

Currently we are evaluating our processes and would like to measure the hit rate of automatic processing of statements (preferably for a longer period in time).

Is there any possibility to retrieve hit rate information (e.g. number of statement line items & number of fully automatic processed statement line items & hit rate %) out of SAP?

 
Reply to this email to post your response.
 
__.____._
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
  
Copyright © 2014 Ziff Davis, LLC. and message author.
Ziff Davis, LLC. 28 E 28th Street New York, NY 10016
wnash7658  

IT/IS Professional/Admin/Staff
35 achievements
 
Mark as helpful
View this online
Ask a new question
 
In the Spotlight
Have a technical question? Need to find IT solutions? Ask your peers in the Toolbox for IT community.

_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language