BUSINESS PROCESS DESIGN DOCUMENT BUSINESS PROCESS: HOST TO HOST
Document Identification DOCUMENT DETAILS Program Name
Track
Business Scenario
Host to Host
Finance
Host to Host
Track Lead –
Track Lead – SAP
Process Owner -
NA Process Number
Process Name
Host to Host Indian Standard Chartered Bank
Document History AUTHORS & PARTICIPANTS Role
Name
Business System Analyst Process Owner Business Unit Process Owner Consultant Workshop Participant
REVISION HISTORY Date
Document Version
Document Revision Description
Author
01 REVIEWED AND APPROVED B Y Name
Title
<>
Business System Analyst
<>
Project Process Owner
Date
Approved
1 BBP Electronic Electronic Bank Statement v 1.0
TABLE OF CONTENT DOCUMENT IDENTIFICATION ................................................................................................................................. 1 DOCUMENT HISTORY ................................................................................................................................................. 1 1
PROCESS DESCRIPTION .................................................................................................................................... 3
BANK ACCOUNTS IN SCOPE ............................................................................................................................. 4
4
OUT OF SCOPE...................................................................................................................................................... 4
5
BANK SPECIFIC REQUIREMENTS AND SPECIFICATIONS ....................................................................... 4
6
PROCESS STEP DETAILED REQUIREMENT AND SOLUTION ................................................................. 5
6.1
DIFFERENT BUSINESS TRANSACTIONS: CURRENT AND PROPOSED SOLUTION ..................................... 6
6.2
KEY CHANGES FOR ADOPTION TO STANDARD ................................................................................................. 6
Presently the business is sending the payment request to Bank via manual upload of DME file. Business is running the SAP program F110 to generate this DME file and authorized person from business is uploading this DME file to the bank server via manual upload.
Presently the business is doing the bank reconciliation on the spread sheet first and then uploading the bank statement manually through ZFF67 (Coping the bank statement data in up loadable format) for clearing. Doing this the system automatically makes the postings to the bank account and bank clearing account along with the payment clearing, Also they are using option of creating batch input session and run it for the same. Going forward the y are planning to have automatic BRS using EBS MT940
2 Proposed Solution
As proposed, we are moving with the option of Host 2 Host connectivity with bank, which sends the outgoing electronic file in the form of SAP standard IDOC directly after running the payment run to the bank site without any manual intervention.(For detailed process step please refer PARA 5). The current process of sending the DME file will be stopped once the new process is in place for SAP standard IDOC. For this we will be designing the standard SAP idoc in SCB bank specific requirement
AS proposed we are moving the option of Host 2 Host connectivity with bank, via which we will be getting the inbound file in the form of MT940 directly in our SAP server without any manual intervention ((For detailed process step please refer PARA 5).
We will be using the Standard SAP IDOC for outgoing communication with bank
3 BBP Electronic Bank Statement v 1.0
3 Bank Accounts in Scope Excel containing the list of Bank Accounts in scope is attached
.
SCB scope.xlsx
4 Out of Scope Reversal process will be out of scope Attach xls file(APP Not configured.xlsx) of bank will be out of scope as there is APP configured
APP Not configured SCB.xlsx
5 Bank Specific Requirements and Specifications Attach file provided by SCB has been modified as per their requirement.
Payment_Order_IDO C_Specifications.pdf
Below modification has been done to meet the SCB specific IDOC on the basis of three payment metho d.
IDOC configuration has been done for 3 payment methods (Cheque, demand draft and Bank transfer).All are for domestic payments only.
Exit EXIT_SAPLIEDP_002 is being used for fields not getting updated in standard IDoc. One new Z table has been introduced ZFITR_FINIDOC
Invalid special characters have been maintained in the Z table ZFITR Config
For employee vendor, middle name is not getting updated in vendor master. This issue needs to be sorted out as cheque will get printed without middle name.
SWIFT Code needs to be maintained in the House Banks
Business is maintaining the IFSC code in the SWIFT code field in the vendor master record. For bank transfer cases SCB needs this in bank number field to achieve this we have used the Exit EXIT_SAPLIEDP_002 so that business need not to change their existing practice
4 BBP Electronic Bank Statement v 1.0
Payment instruction key PA needs to be maintained in all vendor masters in future
Business needs to maintained the check lot in case of check payment, so that check number should be there in each and every bank transaction, which will help in auto BRS. o
Caution :-- In the absence of check number in payment program due to non maintenance of check lot via F110 no idoc will be triggered to bank automatically.
6 Process Step Detailed Requirement and Solution
PAYMENT IDOC SCENARIO:- For F110 payment Request an IDOC will be triggered from SAP which will come to SAP PI, we will encrypt this using the certificate and send it using XI adapter over HTTPS to Bank. In this case 1-1 mapping would be required and for that we would require XSD from Bank to map IDOC to receiver message type.
FILE LEVEL ACKNOWLEDGEMETN FROM BANKS:- Once request is received by Bank - It will decrypt the message and send us acknowledgement whether received or not, through mail notification.
PROCESS LEVEL ACKNOWLEDGEMENT:- Bank will send second acknowledgement which will have transactional acknowledgement that is which transaction was rejected and not processed, through mail notification
BANK STATEMENT IN MT940 FORMAT :- In case of MT940, a scenario can be configured here using the XI adapter to the file and download to a location from which this can be uploaded in to SAP through T code FF_5 as a scheduled job as per the business requirement as daily / weekly or monthly.( Business decision is required on this)
Flow
Out flow In flow for File level notification In Flow for transaction level notification
In flow
Bank
File Format
Solution
Customization / Data flow.
Customization Mapping of Idoc as per SCB india specification using user exit through ABAP.
SCB
IDOC
Standard
IDOC to PI encryption - Bank
SCB
Mail Notification
Standard
No Customization
Standard Mail
SCB
Mail Notification
Standard
No Customization
Standard Mail
Bank to PI - PI to ECC directory
Automatic background scheduling of EBS ( FF_5) , weekly or daily as per business requirement
SCB
MT940
Standard
5 BBP Electronic Bank Statement v 1.0
6.1
DIFFERENT BUSINESS TRANSACTIONS: CURRENT AND PROPOSED SOLUTION
S.No Business Scnerio
1
Payment run from SAP Payment Media Error handling File level notification BRS
2 3 4 5
Current Practice
Proposed Practice
F110
F110
DME Mail in Outlook Mail in Outlook Manual upload in SAP
Standard SAP IDOC Mail in Outlook Mail in Outlook Auto via scheduled job
. 6.2
KEY CHANGES FOR ADOPTION TO STANDARD
User awareness and discipline needs to be maintained If the same is followed manual clearing would be reduced to the minimum level.
SWIFT Code needs to maintained in the House Banks Payment instruction key PA needs to be maintained in all vendor masters in future Business needs to maintained the check lot in case of check payment, so that check number should be there in each and every bank transaction, without this IDOC of check payment method will not move to bank and will be having in RED status Caution :-- In the absence of check number in payment program due to non maintenance of check lot via F110 no IDOC will be triggered to bank automatically
6 BBP Electronic Bank Statement v 1.0
6.3
INTEGRATION POINTS
Integration Process flow will be as under Forward Flow :-
to SCB Bank
.
7 BBP Electronic Bank Statement v 1.0
Inward Flow :-- SCB to MT940 File coming into SAP PI through XI adapter. A bypass scenario is created in PI where the file would be saved in a shared folder between SAP PI and SAP ECC. Then from this folder file would be picked by program in SAP ECC and uploaded automatically
6 Authorization Various Roles identified for the authorization management are as follows: AUTHORIZATIONS S.No.
Manual Uploading of file through ZFF67 and then clearing
Bank file directly uploaded in SAP through host to host connectivity with bank.File will be processed automatically and only unprocessed items needs to be manually post processed.
Automation of bank reconciliation process.
NA
Payment Run
Manual Uploading of file to the bank server
Payment file in standard SAP idoc format will be directly uploaded in bank server via Host 2 Host without any manual intervention
Automation of payment run
NA
9 BBP Electronic Bank Statement v 1.0
8 Appendix RELATED /REFERENCED DOCUMENTS Document Name
