EAP: Some questions and answers to help Understand Documentation Association Rules

(Doc ID 2321991.1)

Last updated on NOVEMBER 03, 2017

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Goal

Q1 :  Why the order of the rules makes a difference and give an example?

Q2 :  Is it correct that the Rules are doing association based on PO and PO Line?  Or is it only based on PO?  And if it is PO and PO Line, then how do the User Criteria work?

Q3 : Regarding User Criteria for rules Equal, Equal Sum and Sum UP ToDocument Association rules Sum Up To,

Equal and Equal Sum come delivered with User Criteria.  For example, Rule “Equal” comes delivered with three User Criteria.As per understanding that User Criteria logic is applied only if the rule is User Criteria.  Is this correct? in which case we can remove the User Criteria for rules Equal, Equal Sum and Sum UP To?

Q4 : Regarding Voucher and Receiver fields for rule User Criteria

Are the Voucher and Receiver fields used if the rule is User Criteria?  If we leave these fields blank for rule User Criteria would we get the same result as with them populated with delivered values?

Q5 : Manual Association versus automated Document Association

Its been observed that field PROCESS_INSTANCE on table  PS_VCHR_RECV_MTCH is updated with the instance number if the association is via automated Document Association, and field ALGTHM_BEHAVIOR is populated with the pertinent association rule, e.g. EQSM.

Its also been observed that field PROCESS_INSTANCE has a value of zero if a receipt is manually associated, and in this case field ALGTHM_BEHAVIOR contains value USER. 
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms