Skip to main content

How to Default Descriptive Flexfield Data From Requisition Header To Requisition Line?

Issue : 

If we have set up additional information in a Descriptive Flexfield at the Requisition Header level, is it possible to automatically default these values down to the Line level, for example to the PO_REQ_DISTRIBUTIONS table?

Solution:

As the Requisitions form has blocks which simultaneously contain the current Requisition Header, Line and Distribution information, it is possible to reference Desc Flex Field columns across different blocks.

Please try the following method in a test instance:

1. Query the Requisition Header DFF definition.
    In this example we will assume that the data to be populated in the child row is
     in the ATTRIBUTE12 DFF column.

2. Responsibility: Purchasing Super User
    Navigation: Setup > Flexfields > Descriptive > Segments
      Click F11 and populate the Title field with "Requisition Distributions"
      Ctr+F11 to execute query
      Click Segments and get the relevant Segment, say ATTRIBUTE1
      Click Open
    Under the Validation Region, in the Default Type field choose "Field"
    In default value, enter 'PO_REQ_HDR.ATTRIBUTE12'

    Save your work, Freeze and Compile the Flexfield.

3. Retest the issue, please navigate to the distributions block of the requisitions form in order for the flex field to invoke the default values.

Note:

If the chosen column in the Distributions record (ATTRIBUTE1 in the above example) is set
up as 'Optional', then the default value will not be populated unless the User actually opens
the Descriptive Flexfield pop-up window in that Block.

You can force the default to be used by making ATTRIBUTE1 a Required Segment.

In the above case the Default is only used if the column is currently empty - a default
DFF value never overrides an earlier user-entered value.

Reference: How to Default Descriptive Flexfield Data From Requisition Header To Requisition Line? (Doc ID 1618008.1) 

Comments

Popular posts from this blog

Create Accounting for a Payment generates errors 95333 and 95359

Create Accounting for a Payment generates errors 95333 and 95359 Error: 95333: A conversion rate does not exist to convert USD to AUD for the conversion type Corporate and conversion date 20-MAR-09 for line -25. Please use the Daily Rates form in General Ledger to enter a conversion rate for these currencies, conversion date and conversion type. 95359: There is no accounted amount for the subledger journal entry line. Please inform your system administrator or support representative that: The source assigned to the accounting attribute Accounted Amount has no value for extract line number 88547. Please make sure the source assigned to the accounting attribute Accounted Amount has a valid value, or assign a different source to this accounting attribute. Solution: 1. Specify a conversion rate for the currencies and conversion date mentioned in the error message 95333 Navigation under the General Ledger responsibility: Setup > Currencies > Currency Rates Manager > Daily Rates ...

Public API’s for FA Transactions

Public API’s for FA Transactions So far Oracle FA is have all the good things except the lack on reporting.Oracle FA is now offer lot of public API's that can be used to interfacing with third party or Oracle application other modules. Here are some of transaction's API's:   Additions API if you have requirement to add assets directly via PL/SQL then use  FA_ADDITION_PUB.DO_ADDITION. If you have selected the Allow CIP Assets check box on the Book Controls window of a tax book when adding CIP assets using the Additions API, the this API automatically adds those CIP assets to that tax book at the same time that they are added to the corporate book. Adjustments API you can make cost adjustments to your assetsdirectly via PL/SQL using  FA_ADJUSTMENT_PUB.DO_ADJUSTMENT  for any  process adjustment. Detail can be found in appendix H) You can use this API if you have a custom interface that makes it difficult to use with the existing Oracle Assets interfaces for adjusti...

AP Table Relation Oracle Apps

AP Table Relation Oracle Apps ORACLE PAYABLE TABLE RELATION Source Table Dependent Table Condition AP_INVOICE_LINES_ALL AIL ZX_LINES_SUMMARY ZLS AIL.invoice_id = ZLS.trx_id and  ZLS.application_id  = 200 and  ZLS.entity_code  = 'AP_INVOICES' and  ZLS.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.summary_tax_line_id = ZLS.summary_tax_line_id AP_INVOICE_LINES_ALL AIL ZX_LINES ZL AIL.invoice_id = ZL.trx_id and  ZL.application_id  = 200 and  ZL.entity_code  = 'AP_INVOICES' and  ZL.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.line_number = ZL.trx_line_number AP_INVOICE_DISTRIBUTIONS_ALL AID ZX_REC_NREC_DIST ZD AID.invoice_id = ZD.trx_id and  ZD.application_id  = 200 and  ZD.entity_code  = 'AP_INVOICES' and  ZD.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and...