[Home] [Help]
112: add a matching rule to Lockbox functionality.
113: If for example you need to match matching numbers and date passed to
114: Lockbox with numbers and dates in your own custom tables
115: custom_table.custom_number and custom_table.custom_date, instead of
116: or in addition to standard matching options, you can use this feature.
117: Or you can use this feature to match with other numbers and dates in
118: the existing Receivables tables, as the need arises.
119:
120: This procedure expects a row in the AR_LOOKUPS table with lookup_type
120: This procedure expects a row in the AR_LOOKUPS table with lookup_type
121: = 'ARLPLB_MATCHING_OPTION' and valid values for other columns required
122: for the customized option.
123: The master program arp_process_lockbox will fetch that row and if it
124: finds it to be one of the non-standard (NOT built in core AR), it will
125: pass the control to this procedure with the corresponding lookup_code
126: in your database.
127: The procedure should return a string that Dynamic SQL can use to open and
128: parse a cursor. You need to create this SQL string to replace the string
307:
308: Points to note :-
309: -----------------
310: 1. If custom code do not want to resolve any particular matching_numbers from the
311: data file, they can just be simply ignored and it will be processed, as standard
312: lockbox matching number. Anyway if some matching number is to ignored by the
313: custom code, it should already be a invoice number, else will be reported as
314: invalid number by,lockbox validation.
315: