Creating DFF for DM and Invoice Link

Use Case Description: In ZATCA Integration, its required to reference the original invoice if you are
creating a debit note (in Fusion, there is no direct link between these two transactions) so, as
workaround we created a DFF in the debit note page to include the original invoice
 To minimize the error entry and false linking, we made the selection as LOV and applied 2
conditions on the Value Set.

1. Frist, we have Created the Flexfield (DFF) that will contain 2 Segments under name
(transaction)

2. We created 2 fields inside the "Related ST Invoice" with display type as Text Box
3. Added the two fields "AR Transaction Number" and "Reason of DM"

4. The Conditions will be applied on the "AR Transaction Number"

> Click on edit > attach a value set for the Transaction Number (to bring all the AR
invoices) > display as LOV

5. Click on View Value set > to add the condition SQL statement
 6. Write down the SQL Statement (from clause):

(SELECT
T.TRX_NUMBER, T.BILL_TO_CUSTOMER_ID
FROM
RA_CUSTOMER_TRX_ALL T, RA_CUST_TRX_TYPES_ALL Y, HZ_CUST_ACCOUNTS C
WHERE
C.CUST_ACCOUNT_ID = T.BILL_TO_CUSTOMER_ID
AND Y.CUST_TRX_TYPE_SEQ_ID = T.CUST_TRX_TYPE_SEQ_ID
AND Y.TYPE ='INV' )

o Where Clause:

BILL_TO_CUSTOMER_ID =:{PARAMETER.BillToCustomerId}

o Order by Clause:

trx_number DESC
 To check the available binding parameters that are allowed to be used within the SQL
statement for DM page

Note: if you made any change to the value set

setup, you need to re-deploy the value set

7. To re-deploy the value set, Select and

click on Deploy Flexfield

Additional step-up for the Descriptive

Flexfields (DFF)

To minimize the number of data entry errors further, we used the page composer tool to make
the following changes in the DFF properties:
Rendered: the DFF will only appear if the transaction type is equal to Debit Memo

Required: the DFF will only be required if the transaction type is equal to Debit Memo

#{bindings.TrxClass.inputValue == 'DM' ? true : false}