How to Integarate Customer SAP R/3 System with Bank System via Automated way

There are two ways Customer and Bank Integration can be done and those are follows,

1. ABAP Package  ( File Extraction (CSV,TXT File Format) )
2. ABAP+PI Package ( IDOC Processing via PI Server- IDOC Basic Type : PEXR2002  and Message Type : PAYEXT )

1. ABAP Package:

• ABAPER will develop Z Report, where customer finance need to provide input’s and execute, so that Bank Specification format file will get extracted and same file will be placed in Bank FTP Server Location.
• If Bank contains only SFTP server not FTP then customer will purchase External software to push File to bank end.
• Even Bank has some sort of software kit, they will install in customer landscape to push file to Bank SFTP Location but this approach will be discussed with Bank only.

Pro’s:

• File Encryption can be done using Bank external software.
• Payments Batching can be done in File level.
• User visibility will be there and duplication payments can’t be extracted using Z Report.

Cons:

• Monitoring won’t be there.
• SSL  Security  won’t be there.
• Once File Successfully reached to bank then Customer won’t get  Acknowledgement from Bank end using this medium.

Flow:

          Z REPORT –>Extract File in Application Server –> Encrypt File Application Server –> Push File into Bank FTP Server. 

ABAP FTP Program for your References:

1. Automatic Payment: ( F110  Payment Transaction)

                                  Z Report will be looks like as follows,

2. Manual Payment: ( F-53/F-58/F-48  Payment Transaction)

                                      Z Report will be looks like as follows,

2. ABAP+PI Package

Automatic Payments:

• ABAPER will do Enhancement for Standard SAP F110 Transaction to accommodate Bank IDOC Specification to trigger IDOC at Customer R/3 Level.
• IDOC Can be process from Customer R/3 to Customer PI as following ways,

                          1. Trigger IDOC Immediately.  ( Using this methodology Customer Approvers need to approve each payment in Bank Portal )

                          2. Collective IDOC. ( Here Payment method wise batching can be done, so Approvers can approve Bulk Payments at one time)

Flow:

              Customer F110 standard Transaction –> Customer PI –> BANK PI –>Bank Portal.

Manual Payments:

• ABAPER will develop Z Report, where Customer finance team need to provide input’s and execute, so that Bank Specification format Idoc will be triggered in Customer R/3 Environment.
• IDOC Can be process from Customer R/3 to Customer PI as following ways,

                            1. Trigger IDOC Immediately.  ( Using this methodology Customer Approvers needto approve each payment in Bank Portal )

                            2. Collective IDOC. ( Here Payment method wise batching can be done, so Approvers can approve Bulk Payments at one time)

Note:

    Normally Collective Idoc can be pushed using WE14 Transaction and Program: RSEOUT00

Flow:
         Customer Z REPORT –>Trigger IDOC –>Customer PI –>Bank PI –>Bank Portal.

Pro’s:

• Monitoring will be there.
• User visibility will be high.
• File Tracking can be done.
• Message Level Security will be there.
• SSL  Security  will be there.
• Once File Successfully reached to bank then Customer will get Acknowledgement from Bank end.
• Encryption can be done using Customer PI Level using Inbuilt SAP Encryption Module.

Cons:

• Once SSL Certificate Date Expired then Need to inject New one.
• Rare case File stuck in PI Level due to Network connection broken or Internet connection down time then Customer PI team need to Release those file in Queue level.