DEFAULT CREDIT VALUE DATE

Hi guys,
how can we retrieve programmatically, the default credit value date.
The reason for it is when we are handling inward payments, we want to ensure that when value date received in incoming MT103 is prior to default to default credit value date, we want to force debit value date = credit value date = default credit value date. If value date received in MT103 is later than default credit value date, we want to ensure that debit value date = credit value date.
For this we need to be able to retrieve the default credit value date in a variable and compare it with the value date received in the MT103. (the routine would be handled in a inward ft version) (below an extract of the info relating to default value dates from FT Docs.)
If there is a fancier way to do it, please let me know.
thx

----
Using CUT.OFF.TIME and CUT.OFF.RULE the default debit value date on outgoing FT transactions is derived as follows:
•
If the transaction is entered before the time specified in CUT.OFF.TIME (for the debit currency) and CUT.OFF.RULE is set to 0, then the debit value date will be that working day, if CUT.OFF.RULE is set to1, then the debit value date will be next working day.
•
If the transaction is entered after the time specified in CUT.OFF.TIME (for the debit currency) and CUT.OFF.RULE is set to 0, then the debit value date will be the next working day. If CUT.OFF.RULE is set to 1, then the debit value date will be the next working day +1 working day.
•
If neither the debit or credit value date have been entered on an outgoing funds transfer and the default debit value date is after the

Hi
crazy one:
1. prepare OFS message with your FT data
2. use OFS.GLOBUS.MANAGER in VALIDATE mode with this OFS message
3. parse the response, retrieve CREDIT.VALUE.DATE
4. enjoy :))

Thanks Guys for your input.
@JPB : I will be usiung this mainly for handling incoming FT that should be conveted to outward payhments. (correspondent Banking) do you have any documentation on this function? I can give it a shot.
@VK: It sounds a long shot :) but I'll be giving it a shot. Can you please give me a simple example to build upon?
Many thanks guys!!!

Hi
Something like:

1. Choose OFS.SOURCE with SOURCE.TYPE = 'GLOBUS'

2. Form OFS MESSAGE based on R.NEW, like:

3. Call:

ofs_msg will contain OFS reply after this call.

Success:

FT16nnnnnnnn//1,TRANSACTION.TYPE:1:1=IT,DEBIT.ACCT.NO:1:1=nnnnnnnnnnnnn,CURRENCY.MKT.DR:1:1=1,DEBIT.CURRENCY:1:1=USD,DEBIT.VALUE.DATE:1:1=2016nnnn,DEBIT.THEIR.REF:1:1=nnnnnnnn nnnnnnn,CREDIT.ACCT.NO:1:1=nnnnnnnnnnnnnnn,CURRENCY.MKT.CR:1:1=1,CREDIT.CURRENCY:1:1=USD,CREDIT.AMOUNT:1:1=nnnnn.nn,CREDIT.VALUE.DATE:1:1=nnnnnnnn,PROCESSING.DATE:1:1=nnnnnnnn,ACCT.WITH.BANK:1:1=...

Error:

FT16nnnnnnnn//-1/NO,OVERRIDE:1:1=Unauthorised overdraft...

Hi VK,
I successfully coded your solution, it gives me the expected result. Thanks a lot.
I have an issue however. when I apply this default value date (I set it in the DE.I.MT103 local routine), it gives me an override CREDIT.VALUE.DATE NE TO DEFAULT OR DEBIT.VALUE.DATE NE TO DEFAULT (depending on the incoming value date and sending time of the incoming MT103).
which makes it IHLD instead of INAU.
My version GTS is in mode 3.
I tried to customize the OVERRIDE record for these two errors but it doesnt seem to have any effect.
Below a copy of my Override msg for both these OVERRIDE records:

OVERRIDE.KEY...... CR.VAL.DATE.CUT.OFF

---

1. 1. 1 L CREDIT VALUE DATE BEFORE DEFAULT
1. 1. 2 L KREDITVALUTA LIEGT VOR DEFAULT
2. 1 TYPE........... Auto
12 NUMERIC.ID........ O-10161
14. 1 APPLICATION.... *
31. 1 OFS.SOURCE..... SWIFTIN FOR INCOMING SWIFT MSG
32. 1 APP.VERSION.... FUNDS.TRANSFER FUNDS.TRANSFER
42 SYSTEM............ YES

OVERRIDE.KEY...... DR.VAL.GT

---

1. 1. 1 L DEBIT VALUE GREATER THAN TODAY
1. 1. 2 L SOLLVALUTA GRÖßER ALS HEUTE
12 NUMERIC.ID........ O-10296
14. 1 APPLICATION.... *
31. 1 OFS.SOURCE..... SWIFTIN FOR INCOMING SWIFT MSG
32. 1 APP.VERSION.... FUNDS.TRANSFER FUNDS.TRANSFER
42 SYSTEM............ YES

Can you point out if there's sthg I'm not doing or doing wrong!

Many thanks,

Hi,
You can try to set GTS.CONTROL to 1 (Errors on HLD / Approve Overrides).

I did this initially but it accept ALL overrides without discrimination :) (including those for insufficient funds).
Since we're heading toward STP setting, it's important to selectively accept overrides

Then create an INPUT routine for your VERSION that will check the contents of OVERRIDE field; if you find there something else - CALL STORE.END.ERROR.

I will try this

Hi VK,
I tried the solution to set ETEXT @ input routine level.
however, I'm not confortable @ setting GTS in mode 1 as it means that we have to check for certain conditions and set it to HLD (god knows how many scenarios we yet to encounter). especially we're handling money here and we don't know what we don't know :)

I'm more confortable at setting the GTS to 3 and selectively accepting overrides. I only want to auto accept overrides relating to value dates, all the rest should be put IHLD.
Can you suggest a way to reach this plz?

Hi
I'm not aware of any correct way to accept overrides programmatically...
What's wrong about having GTS.CONTROL = 1 and issue the error for everything but value date-related ones?

You got a point!
haven't thought about blocking everything but :)
I was more about leaving everything go straight and blocking items such us insufficient funds, post restrict, ...
but this way makes sense.
Also, is there any way to search about overrides by ID rather than parsin the Text.
Thanks,

Hi
you don't need to parse the text - there's override @ID along with the text (but you see the text only in T24; try to LIST the file)