3. SKN Messages

Oracle FLEXCUBE facilitates the outgoing and incoming payments with SKN network. SKN networks dispatches and processes Incoming Credit Payment, Return of Incoming Credit Payment, Outgoing Credit Payment and Return of Outgoing Credit Payment messages.

This chapter contains the following section:

• Section 3.1, "Details for SKN Interface "

3.1 Details for SKN Interface

This section contains the following topics:

• Section 3.1.1, "Maintaining External System"
• Section 3.1.2, "Maintaining SKN Interface Details"
• Section 3.1.3, "Maintaining SKN Messages"
• Section 3.1.4, "Processing Incoming SKN Messages"
• Section 3.1.5, "Processing Outgoing SKN Messages"

You need to maintain the following details for this interface:

• Details of External System
• Details of the Interface
• Interface Parameterization
• Interface Translation

3.1.1 Maintaining External System

You need to specify the external system connected to the interface by using the ‘External System Maintenance’ screen. You can invoke the ‘External System Maintenance’ screen by typing ‘GWDEXSYS’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.

In this screen, you can specify the following details:

External System

Specify ‘SKN’ as the external system.

For more details refer Maintaining External System(s) Details section of Generic Interface User Manual

3.1.2 Maintaining SKN Interface Details

Generic Interface (GI) provides a facility to define format details and properties associated to interface file.You can maintain format details and properties associated with SKN interface file in the ‘Interface Definition’ screen. You can invoke this screen by typing ‘GIDIFTDF’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.

The following details are maintained for PCSKNSIN interface here:

External System

Specify ‘BIS’ as external system.

Interface code

Specify interface code as ‘PCSKNSIN’.

Interface Type

Select Incoming as interface type from the adjoining drop-down list.

File Path

Specify the directory path of the incoming files to be processed.

File Name

Specify the file name as per network.

Frequency Type

Select Multiple times in a day as the frequency type from the adjoining drop-down list.

Incoming File Mask

Select ‘Start With File Name’ as the incoming file mask from the adjoining drop-down list.

The interface details and the external system details are maintained using the Interface Definition Details and External System Maintenance screens. For more details refer Specifying Interface Definition Details section of Generic Interface User Manual.

3.1.3 Maintaining SKN Messages

The following table specifies the various message types and the corresponding transaction code of SKN Network:

Serial No	Network (from Product)	Message Type (Outgoing/ Incoming)	Payment /Collection	Product Type(from Product Category)	Message Name	Message Description
1	SKN	Incoming	Cus­tomer	Incoming Credit Payment	S01	This is an incoming SKN Payment message for the Customer. The message type received in the message will be “BMSKN01” based on which the product type will be identified. Mapping between the message type and the corre­sponding Pay­ment product has to be pro­vided based on which the trans­action will be created.
2	SKN	Incoming	Cus­tomer	Return of Outgoing Credit Payment	S03	The message is the return of “Outgoing credit payment”. The first 16 characters of the “Remarks field” in the message con­tain the Refer­ence number based on which the transaction will be identi­fied.
3	SKN	Outgoing	Pay­ment	Outgoing Credit	S05	This message will be gener­ated for the “Outgoing Pay­ment” transac­tion using the SKN product
4	SKN	Outgoing	Pay­ment	Return of Incoming Credit	S07	This message will be gener­ated when the authorizer rejects the Incoming credit Payment

3.1.4 Processing Incoming SKN Messages

The interface PCSKNSINC uploads the incoming payment files through SKN networks. The incoming files uploaded in the ASCII format is placed in a specified folder and the path is mapped to GI maintenance.

Steps involved in File processing of Incoming SKN Message:.

• When the file is uploaded, the network type is identified based on the file type.
• The file is parsed as per the message format and is uploaded in the GI interface table.
• From the interface table new program unit is written to call the PC service using the data available in the GI interface table.
• The SKN file is identified with SKN file extension.
• The interface job is triggered manually to initiate manual processing.
• After the file processing and data processing, incoming job PC_PRCSINMSG is executed from the job browser screen (CSSJOBBR)
• After job execution, system processes the data from the GI upload table and creates Incoming payment contracts
• During the data process stage the transaction will be rejected for the following cases:
  • Corrupted input file
  • Invalid record (e.g. account number missing)
  • Account number field will be checked for the presence of any special characters, if found then the transaction will be rejected.
  • TRN code is incorrect or blank.

3.1.5 Processing Outgoing SKN Messages

The interface PCSKNOUT uploads the outgoing payment files through SKN networks. The outgoing files uploaded in the ASCII format is placed in a specified folder and the path is mapped to GI maintenance.

Steps involved in File processing of Outgoing SKN Message:

• The cut-off time maintained is validated for the network in order to check if the current time is within the cut-off time.
• All the outgoing payment contracts generated today along with the contracts generated after the cut-off time in the previous day is selected.
• All the fields required for the file will be inserted into the GI upload interface table.
• The PC_OUTFILE_PATH parameter is inserted in CSTB_PARAM table.
• The outgoing file is placed in the path based on the path specified in the parameter.