Previous Next JavaScript must be enabled to correctly display this content

## 1.2 Maintenance in OBEDX

This section describes the specific maintenances needed for Oracle Banking Electronic Data Exchange for Corporates to integrate the same with Oracle Banking Payments.

1. Modify Integration preferences

   Go to Electronic Data Exchange→Maintenance→Integration Preferences → View Integration Preferences.

   For Transaction Category: “Payment”, there will be two entries for “Payments” as day 0, one for handoff and other for parsing.

   OBEDX integrates with OBPM via SFTP and File-API for handoffs requests for file uploads. Modify the existing maintenance for handoff to add relevant details.

   For SFTP Below are the mandatory entries for handoff maintenance that need to be updated

   1. FTP Host - Host IP
   2. FTP Port - Host Port
   3. FTP Username - Valid user for accessing host
   4. FTP Password - Valid password for accessing host
   5. FTP File Path - Path on which handoff request file will be placed
   6. Response File Path- Path from which handoff response file will be downloaded

   For File and API Below are the mandatory entries for handoff maintenance that need to be updated

   1. FTP Host - Host IP
   2. FTP Port - Host Port
   3. FTP Username - Valid user for accessing host
   4. FTP Password - Valid password for accessing host
   5. Response File Path- Path from which handoff response file will be downloaded

   Apart from above mentioned entries,yYou can also modify any other details as required for integrations with OBPM for your installation.

2. Reopen ‘EDXOutgoingInternal' & ‘EDXIncomingInternal’ channels in Channel Maintenance and update the ‘Folder Path’ field. The folder path given should be created in the Network area

   Note:

   ‘EDXOutgoingInternal’ & ‘EDXIncomingInternal’ channels are created as a part of Day0 setup and should not be deleted as they are used for the integration between OBEDX and OBPM.
3. Handoff file to OBPM is sent in pain.001.001.06 format & response file is received in pain.002.001.06 format, hence 2 Formats Identifiers ‘PAIN001V6’ of type Handoff & ‘PAIN002V6’ of type Handoff Response is created as a part of Day0 setup and is advised not to delete/modify them.
4. Handoff file to OBPM is sent in pain.001.001.09 format & response file is received in pain.002.001.10 format, hence 2 Formats Identifiers ‘PAIN001V9’ of type Handoff & ‘PAIN002V10’ of type Handoff Response is created as a part of Day0 setup and is advised not to delete/modify them.
5. Handoff files to OBPM are sent in a specific file naming convention, hence ‘EdxHandoffPayments’ filename template is created as a part of Day0 and is advised not to delete/modify.

6. Note:

   Details of pre-configured ‘EdxHandoffPayments’ file name template is as follows:

   Field Name | Description
   --- | ---
   Free Field 1 | Rename Field- HandoffName Constant Value - EDX
   Format Identifier | Alphanumeric with Special Char
   Transaction Name | Alphanumeric with Special Char
   Free Field 2 | Rename Field- Response Constant Constant Value - PAIN002V6
   Date and Timestamp | DDMMYYHHMMSS
   File Extension | xml

7. Three Response files from OBPM are received in a specific file naming convention, hence ‘PaymentsHandoffResponse’ filename template is created as a part of Day0 and is advised not to delete.

   Note:

   Details of pre-configured ‘EdxHandoffPayments’ file name template is as follows :

   Field Name | Description
   --- | ---
   Free Field 1 | Rename Field- HandoffName Constant Value - EDX
   Free Field 2 | Rename Field-HandOffConstant Constant Value - PAIN001V6
   Transaction Name | Alphanumeric with Special Char
   Format Identifier | Alphanumeric with Special Char
   Free Field 3 | Rename Field-Timestamp Alphanumeric with Special Char
   File Extension | XML

8. 3 Preconfigured Correlation rules for Payments are provided as a part of Day0 and is advised not to delete/modify.

   FileLevelCorrelationRule is created at File Level on Message Id.

   BatchLevelCorrelationRule is created at Batch Level on Payment Info Id.

   RecordLevelCorrelationRule is created at Record Level on Transaction Reference Number.

Parent topic: Integration Guide