Setups required for the Check Printing (MICR Font Registration and Extension of IBY_FD_EXTRACT_EXT_PUB

Setups required for the Check Printing (MICR Font Registration and Extension of IBY_FD_EXTRACT_EXT_PUB

PAGE-3

MICR Font Registration

·         Download the MICR code from online based on the requirement. I have downloaded ‘Free 3 of 9’ here.

·         Copy the ttf file downloaded into the ‘FONT’ folder of windows in the Drive where the XP is installed.

·         This font will be available in the MS word while creating RTF. Use this new font for the MICR format design on the template rtf.

Below are the Steps to register the font in the application

·         Go to Responsibility:  XML Publisher Administrator

Navigation: Home -> Administration

·         Go to Font Files tab and click on Create button.

Below page opens

Enter the below details

Font Name: MICR code

·         Upload the ‘micrenc.ttf’ file .

·         Click on Apply button.

The font file got created.

Create Font Mapping to above Font File

Navigation: Go to Font mapping TAB

·         Click on Create Font mapping Set button

Below page opens

Enter Details as follows

Mapping Name: MICR code

Mapping Code: MICR code

Type: FO to PDF

·         Click on apply and proceed further.

·         Below page opens

·         Click on Create Font mapping.

·         Below page opens. Enter details as follows,

Font Family: MICR Encoding

Style: Normal

Weight: Normal

Font Type: Truetype

Click on the ‘Continue’ button.

Below page opens

Enter the details as follows,

Font: MICR code

Click on the apply button.

The font Mapping is created.

Assign the font to the Templates

Navigation: Go to Templates TAB.

Search with the templates created so far

 XXX Check Format

• Click on the template link to open ‘RISO CAN Check Format’ as shown above.

Below page opens

• Click on the ‘Edit Configuration’

• Add the Font Mapping Set created ‘MICR code’
• Click on Apply           

Steps to Extend the standard XML to get additional details for check printing.

In order to extend the Standard xml of Check Printing we need modify the ‘IBY_FD_EXTRACT_EXT_PUB’ package.

The package allows custom elements to be created at following levels.

• Instruction

• Payment

• Document Payable

• Document Payable Line
• Payment Process Request

You cannot customize the package specification, but package body contains stubbed functions that you can customize. The five functions are as follows:

• FUNCTION Get_Ins_Ext_Agg(p_payment_instruction_id IN NUMBER) RETURN XMLTYPE

This function allows XML element to be introduced at instruction level and run only once for the instruction.

• FUNCTION Get_Pmt_Ext_Agg(p_payment_id IN NUMBER) RETURN XMLTYPE

This function allows XML element to be introduced at payment level and run once for each payment in the instruction.

• FUNCTION Get_Doc_Ext_Agg(p_document_payable_id IN NUMBER) RETURN XMLTYPE

This function allows XML element to be introduced at document payable level and run once for each document payable in the instruction.

• FUNCTION Get_Docline_Ext_Agg(p_document_payable_id IN NUMBER, p_line_number IN NUMBER) RETURN XMLTYPE

This function allows XML element to be introduced at document payable line level and run once for each document payable line in the instruction.

• FUNCTION Get_Ppr_Ext_Agg(p_payment_service_request_id IN NUMBER) RETURN XMLTYPE

This function allows XML element to be introduced at document payable level and run once for each payment process request.

Example using the Extensibility Utility Function

The following example shows how custom XML element ReferenceFormatCode is introduced at the payment instruction level.

The function Get_Ins_Ext_Agg in the IBY_FD_EXTRACT_EXT_PUB package is altered as shown, to build custom XML elements, that are included in the XML payment extract at the Payment Instruction level. The sample code that builds a new XML element ReferenceFormatCode using the payment_instruction_id is as follows:

PACKAGE : IBY_FD_EXTRACT_EXT_PUB

/*PAYMENT INSTRUCTION LEVEL*/

/*Before Change*/

FUNCTION Get_Ins_Ext_Agg(p_payment_instruction_id IN NUMBER)

RETURN XMLTYPE

IS

BEGIN

RETURN NULL;

END Get_Ins_Ext_Agg;

/*After Change */

FUNCTION Get_Ins_Ext_Agg(p_payment_instruction_id IN NUMBER)

RETURN XMLTYPE

IS

l_ins_ext_agg XMLTYPE;

BEGIN

SELECT XMLElement("ReferenceFormatCode", reference_format_code)

INTO l_ins_ext_agg

FROM iby_pay_instructions_all ipmtins

WHERE ipmtins.payment_instruction_id = p_payment_instruction_id;

RETURN l_ins_ext_agg;

END Get_Ins_Ext_Agg;

Similar customizations are carried out on the other customizable functions described above.