Report Rule on payement Advice

Hi.  I foud the following information that should help you -

Yes, in IFS Cloud / IFS Applications, you can automatically transfer PDFs generated in the Report Archive into Docman and connect them to business objects so they are directly accessible from pages like Supplier Payment Analysis.

There are two main approaches to set this up: Method 1 (Report Rule Engine — Recommended) and Method 2 (Event Action on PDF_REPORT_CREATED).

Prerequisites

1. Enable Object Connection on Target Page:

   • Go to Object Connections in IFS.

   • Ensure that the Logical Unit (LU) representing the payment record on Supplier Payment Analysis (e.g., OrderLedgerItem, PaymentOrder, or PaymentProposal) has DocReferenceObject enabled so the Attachments / Documents panel is active on that screen.

2. Confirm Docman Setup:

   • Ensure a Document Class (e.g., FINANCE or PAYADVICE) exists in Docman with proper repository access for generated reports.

Method 1: Using IFS Report Rules (Recommended)

The Report Rule Engine provides a built-in, no-code way to capture report outputs and attach them to Docman.

1. Navigate to Report Rules in IFS.

2. Create a new rule for Report ID: UNIFORM_PAYMENT_ADVICE_REP (or PAYMENT_ADVICE_REP).

3. Add a new Action:

   • Action Type: Create Document / Archive to Docman.

   • Doc Class: Select your document class (e.g., FINANCE).

   • Target LU Name: Specify the target Logical Unit (e.g., OrderLedgerItem or PaymentOrder).

   • Key Ref (Object Keys): Map XML parameters from the payment advice report payload to the key reference format expected by the target LU (e.g., COMPANY=10^PAYMENT_ID=1001^...).

4. Set the rule to Active and save.

Method 2: Using Custom Event Action (PDF_REPORT_CREATED)

If dynamic logic or custom key extraction is required, you can use the standard system event:

1. Navigate to Custom Events / Event Actions.

2. Create an action for the system event PDF_REPORT_CREATED.

3. Add conditions so the event only fires when REPORT_ID matches your payment advice report ID (UNIFORM_PAYMENT_ADVICE_REP / PAYMENT_ADVICE_REP).

4. Set the action to Execute PL/SQL Block:

   • Use IFS standard Docman APIs (Doc_Title_API.Create_New_Document_, Doc_Reference_Object_API.Create_New_Reference_, and Pdf_Archive_API) to extract the PDF binary stream from the Report Archive, upload it as a new document revision in Docman, and link it to the payment record key.

How it Works for Users

Once configured:

1. When a payment proposal or order is validated, the Payment Advice PDF generates in the Report Archive as normal.

2. The Report Rule or Event Action automatically checks the PDF into Docman and links it to the payment record.

3. Users navigating to Supplier Payment Analysis can open the Attachments / Docman panel on the record to view or download the Payment Advice PDF directly.

Please advise if there are any questions.  Thanks!  Jane

Thank you ​@Jane Perry , but the question was how to add PaymentPerCurrency to the ConnectedLU 

Hi.  Sorry about that!  How can you add PaymentPerCurrency to the ConnectedLU?  Let me know if this helps -

In IFS Cloud / IFS Applications, adding a Connected LU (Logical Unit) like PaymentPerCurrency to a Report Rule allows the Report Rule engine to retrieve attributes and contextual data from PaymentPerCurrency that may not be directly available in the report's default XML structure. This enables you to drive conditional actions (such as email distribution, printing rules, or archive properties) based on currency-specific payment details.

Step-by-Step Guide: Adding PaymentPerCurrency as a Connected LU

1. Navigate to Report Rules

• Go to Solution Manager > Operational Reporting > Report Rules (or search for Report Rules in the Navigator).

2. Select or Create the Payment Advice Report Rule

• Locate the Report Rule configured for your Payment Advice report ID (e.g., UNIFORM_PAYMENT_ADVICE_REP, PAYMENT_ADVICE_REP, or PRINT_CHECK_REP).

• If one does not exist yet, create a new Report Rule header for the applicable Report ID and specify the Rule Priority.

3. Add PaymentPerCurrency to Connected LUs

• In the Report Rule details, go to the Connected LUs tab/section.

• Click New / Add.

• In the LU Name field, select or enter: PaymentPerCurrency.

4. Define Key Mappings

• Map the key fields from the report context/parent LU to the corresponding keys in PaymentPerCurrency:

  • Company (COMPANY) $\rightarrow$ Report Parameter / Context COMPANY

  • Automatic Payment Type (AUTOMATIC_PAYMENT_TYPE) $\rightarrow$ Payment Type (e.g., SUPPLIERPAYMENT)

  • Order ID / Payment ID (ORDER_ID or PAYMENT_ID) $\rightarrow$ Matching Payment Order / Proposal ID

  • Currency (CURRENCY) $\rightarrow$ Matching Currency Code

• Note: Correct key mapping ensures the Report Rule engine fetches the exact PaymentPerCurrency record matching the payment transaction being processed.

5. Utilize Attributes in Conditions & Actions

• Once saved, attributes from PaymentPerCurrency (such as CURRENCY, CURR_AMOUNT, PAYMENT_DATE, etc.) can be referenced in your Report Rule:

  • Conditions: Evaluate properties using syntax like [ConnectedLU:PaymentPerCurrency/CURRENCY] = 'USD'.

  • Actions: Use expressions to set dynamic email recipients, printer selection, or distribution properties based on the connected LU values.

Alternative / Customization Options

If you need the PaymentPerCurrency data present inside the Report Layout (RD) or XML result tree (rather than just evaluating rules for routing/emailing):

• Custom Fields / Report Extension: Attach a custom field or custom logical unit reference to the underlying entity or update the Report Data Package (*_RPI / RDF) so that PaymentPerCurrency details are populated directly into the report XML.

Thanks!  Jane

​@Jane Perry , thank you, but the AI response is completly wrong. as i have shown in my screenshot, there is no PaymentPerCurrency  so we can not connect the report rule to.

Have you tried your solution on your environment please?

Hi.  I continued this search and found the following -

The ability to add PaymentPerCurrency as a Connected LU in the Payment Advice Report Rule depends on whether the LU is exposed through the report's data source and supported by the report framework. Based on the information currently available, we cannot confirm that PaymentPerCurrency is available as a standard Connected LU for Payment Advice reports. If it is not available in the Connected LU list, this would typically indicate a product limitation and may require a customization or enhancement request.

If you would like to enter an enhancement request, you can use all of or part of the following -

Enhancement Request: Expose PaymentPerCurrency as a Connected LU in Payment Advice Report Rules

Title:
Expose PaymentPerCurrency as a Connected LU for Payment Advice Report Rules

Product Area:
Finance → Payments → Payment Advice Reporting

Business Requirement:
Customers need access to payment-level currency information when configuring Payment Advice Report Rules. Currently, PaymentPerCurrency is not available as a Connected LU, which limits the ability to retrieve and present currency-specific payment details within Payment Advice report layouts.Current Limitation:
When creating or modifying Report Rules for Payment Advice reports, users can only select from the Connected LUs exposed by the report framework. PaymentPerCurrency is not currently available, preventing access to data maintained at the payment-per-currency level and restricting reporting flexibility. Based on available information, PaymentPerCurrency does not appear to be exposed as a standard Connected LU for Payment Advice reporting.
Requested Enhancement:
Make PaymentPerCurrency available as a Connected LU within the Payment Advice Report Rule framework.

This would allow report designers to:

• Access currency-specific payment information directly from Report Rules.
• Add currency-related attributes to Payment Advice layouts without customization.
• Create more detailed and flexible customer payment remittance documents.
• Reduce the need for report modifications, custom fields, or custom development.

Business Value:

• Improves standard reporting capabilities.
• Reduces implementation and maintenance costs.
• Supports organizations operating in multiple currencies.
• Enables more comprehensive Payment Advice documents using standard functionality.
• Improves customer communication by providing clearer payment details.

Expected Result:
When configuring a Report Rule for a Payment Advice report, administrators should be able to select PaymentPerCurrency as a Connected LU and access its available attributes for report layout and data retrieval purposes.

Workaround Today:
Customers may need to explore customizations or report modifications to expose the required currency-specific payment information, increasing implementation effort and upgrade maintenance.

Priority Justification:
Medium to High. This enhancement would provide additional reporting flexibility with minimal user impact on existing functionality while addressing a common requirement for customers operating in multi-currency environments.

I hope this helps.  Thanks!  Jane