Scribd
Upload
304 views30 pages

Delivery Routines: Click To Edit Master Text Styles Second Level Third Level

Uploaded by

Cuong NC
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
304 views30 pages

Delivery Routines: Click To Edit Master Text Styles Second Level Third Level

Uploaded by

Cuong NC
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 30

Click to edit Master text styles

Delivery Routines
Second level
Third level
Objectives

• To understand the flow of a delivery advice.


• To understand the need for a delivery routine.
• To understand the steps to create a delivery routine.

2
Need For Delivery Routines

To display information that is not a part of the


APPLICATION.HANDOFF

3
Need For Delivery Routines

• When a Transaction is Authorized, Advice has to be generated


containing the details of the transaction.
• This Advice need to be send to Particular Address.
• In Globus delivery messages are produced at the authorization
stage.

4
APPLICATION.HANDOFF

This routine has 12 parameters passed.


Incoming Parameters :
Array1,Array2,Array3,Array4,Array5,Array6,
Array7,Array8,Array9,Mapping Key
Return Values :
Delivery Reference Id, Error Code

5
APPLICATION.HANDOFF

• Format of the Mapping key :


• MessageType.Application.Subclassification
Example : 900. LD.1
• Message Type : Should be a valid message type
defined in DE.MESSAGE
• Application : Should be a valid product defined
in EB.PRODUCT.
• Subclassification : One message type can have multiple
mapping records. In such a case
values here would be 1,2...etc

6
APPLICATION.HANDOFF

Array1 : Values in R.NEW


Array2 : Values in R.OLD
Array3 : Generic
Array4 : Generic
Array5 : History Record Values
Array6 : Local Reference Field Values
Array7 : Swift Message Related Details
Array 8 : Header
Array9 : User Defined Values
Array10 : User Defined Values

7
APPLICATION.HANDOFF

Third array in APPLICATION.HANDOFF should be generic and in the


following sequence
Example
ARRAY3<1> = ID.COMPANY (Company id)
ARRAY3<2> = ID.COMPANY (Company id)
ARRAY3<3> = "GB“ (Language)
ARRAY3<4> = "DEPARTMENT“ (Department)
ARRAY3<5> = ID.NEW (Record id)
ARRAY3<6> = R.NEW(INS.CUSTOMER.NO)
(Customer Number)

8
Pre-requirement

• The address of the CUSTOMER as conversant to GLOBUS should


exist in DE.ADDRESS.
• A main template should exist where this routine could be attached.
• Default record in DE.PRODUCT exists (like IN0010001.ALL.ALL)

9
Delivery Routines

Delivery routine must be passed with two arguments (Handoff details


and Error message).
Example
SUBROUTINE DEL.RTN(MAT HANDOFF.REC,ERR.MSG)
HANDOFF.REC is the dimensioned array that holds the Handoff
Details.
ERR.MSG is the parameter that holds the error details if any.

10
Example 1

Write a delivery routine that displays


Transaction is approved by :
<Account Officer Code>
the above message at the end of the delivery advices for the message
type 900 (FT).

11
SOLUTION

Delivery reference number which gets generated at the time of


authorization for the Transaction type AC is displayed below.

12
STEPS

First thing what we have to do is to define the additional details that is


not a part of Application.Handoff in DE.MESSAGE. The Steps are
as follows.
STEP 1:
Define the FieldName that has to hold the Account Officer Id in
DE.MESSAGE (900 ).

13
Solution 1

Create a record in DE.MESSAGE ID:900

14
Solution 1

STEP 2
Map the field to an appropriate array position in DE.O.HANDOFF. It is
advisable to use the 9th or the 10th array in DE.O.HANDOFF to
populate the new values. This example uses the 9.2 position in
DE.O.HANDOFF record.

15
Solution 1

Create a record in DE.MAPPING. ID : 900.FT.1

16
Solution 1

STEP 3
Write a routine that will
• Pick up the account officer for that specific Customer from the
Customer file.
• The Customer Id is available in the ‘2.1’ position of the handoff
record (DE.O.HANDOFF).
• Extract the id from the handoff record. Using this open the
Customer file and extract the Account Officer.
• Pass this extracted value to the handoff record (populate the value
in ‘9.2’ position of the record).

17
Solution 1

SUBROUTINE GET.ACCT.OFFICER(MAT HANDOFF.REC,ERR.MSG)


$INSERT I_COMMON
$INSERT I_EQUATE
$INSERT I_F.CUSTOMER
Y.CUS.ID = 0
R.CUS.REC = ‘’
FN.CUSTOMER = 'F.CUSTOMER'
F.CUSTOMER = ''
CALL OPF(FN.CUSTOMER,F.CUSTOMER)
Y.CUS.ID = HANDOFF.REC(2)<1>
CALL F.READ(FN.CUSTOMER,Y.CUS.ID,R.CUS.REC,F.CUSTOMER,ERR1)
HANDOFF.REC(9)<2> = R.CUS.REC<EB.CUS.ACCOUNT.OFFICER>
RETURN
END

18
Solution 1

STEP 4
Compile and Catalog the Subroutine and attach in the
BEFORE.AUTH.WRITE part of the main template

19
Solution 1

STEP 5
Attach the Subroutine in DE.MAPPING Record (field no :11)
prefixed with @ symbol

20
Solution 1

STEP 6:

Format the advice using DE.FORMAT.PRINT.

21
Solution 1

DE.FORMAT.PRINT ID : 900.1.1.GB

22
Solution 1

Step 7
Initiate the phantom. Use DE.MENU to initiate the phantom.
Step 8
Input a FT Transaction with AC Type and Authorize.
Step 9
Note down the Delivery reference id.

23
Solution 1

Step 12
Using the Delivery Reference Number open DE.O.HANDOFF and
check whether the value has been populated.
SEE.HANDOFF DeliveryReferenceID
(From the database prompt)
Step 13
Using the Delivery Reference Number open the DE.O.HEADER and
check the disposition field. The status of the disposition field has to be
‘FORMATTED’.

24
Solution 1

Step 14
The advice can be viewed by using the following application
DE.MM.PRINT.MSG.
DE.MM.PRINT.MSG Delivery Reference ID (From within T24).

25
WORK SHOP 1

Write a delivery routine that displays


Transaction is approved by :
<Account Officer Code>
the above message at the end of the delivery advices for the message
type 910 (FT).

26
WORK SHOP 2

Write a delivery routine that displays


“Now the new Working Balance in Account XXXXXXXX
is : <Working Balance> <currency>”
the above message at the end of the delivery advices for the message
type LD 320.

27
Summary

• A delivery routine is used to fetch data not available in the


APPLICATON.HANDOFF so that it can be displayed in the delivery
advice.
• A delivery routine needs to be attached to the DE.MAPPING
application.
• A delivery routine takes in 2 input parameters. A dimensioned array
that will hold the data in APPLICATION.HANDOFF and a variable
to return the error code.

28
Summary

• Use SEE.HANDOFF followed by the delivery reference id to


see the contents of the APPLICATION.HANDOFF.
• Use DE.MM.PRINT.MSG to view a delivery advice once it has
been generated.
• Use DE.MENU to start/stop delivery phantoms.

29
© 2006 Thesys Technologies. All rights reserved.

30

You might also like