4.2 AXF_CONFIGS Table

Use the AXF_CONFIGS table to enable the AXF solution on various E-Business Suite Forms. This table allows a fine level of granularity when selecting which Forms are AXF-enabled, up to the Data Block level.

Form events are invoked automatically when an action is performed on an E-Business Suite Form. The AXF_CUSTOM.pll makes all events available, such as POST-INSERT, for customization. You can decide which events to use, and how and when to use them.

When an action occurs, the customized code launches the specified solution and command configured for the event. In the case where the same form is being reused, such as Invoice Entry and Invoice Query, FORMFUNCTION and DATABLOCKNAME together uniquely identify each Form.

Note:

You can enable all datablocks on a form rather than a specific datablock, by specifying AXF_DEFAULT for the DATABLOCKNAME parameter. This allows AXF to be notified whenever a POST-INSERT event occurs for the form, regardless of its datablock. Note, however, that setting the DATABLOCKNAME parameter to AXF_DEFAULT enables specified ZOOM or SPECIAL commands on all screens related to the form. (ZOOM and SPECIAL commands are set in the AXF_COMMANDS Table.)

4.2.1 Column Description

Table 4-1 Column Description for AXF_CONFIGS Table

Column Name Description Data Type

FORMID

Specifies the primary key of the table.

Number

FORMFUNCTION

Distinguishes each E-Business Suite Form based on the form's functionality.

Varchar2 (100 byte)

SOLUTIONENDPOINT

Specifies a URL to AXF.

Varchar2 (1000 byte)

ENTITYNAME

Used by the attachment functionality as a unique name, which links attachments to the correct Forms.

Varchar2 (100 byte)

LOGENABLED

Enables or disables the log for the specified form. Specify one of the following:

  • 1/TRUE/YES

  • 0/FALSE/NO

Varchar2 (10 byte)

DATABLOCKNAME

Specify the data block on the form to be enabled.

Note that you can also specify AXF_DEFAULT to enable all data blocks on the form.

A Form may be reused by E-Business Suite (for example, Invoice Entry and Invoice Query); the FORMFUNCTION and DATABLOCKNAME together uniquely identify each form.

Varchar2 (100 byte)

4.2.2 Example Implementation

This example defines that the entire Invoices Form is AXF-enabled. (Without the first row, the INV_SUM_FOLDER Data Block of the Invoices Form would be enabled.)

Table 4-2 Example AXF_CONFIGS Table

FORMID FORMFUNCTION SOLUTIONENDPOINT ENTITYNAME LOG ENABLED DATABLOCKNAME

1

AP_APXINWKB

http://<ApplicationServerName>:<SOA Port>/axf-ws/AxfSolutionMediatorService

AP_INVOICES

YES

AXF_DEFAULT

2

AP_APXINWKB_SUMMARY_VIEW

http://<ApplicationServerName>:<SOA Port>/axf-ws/AxfSolutionMediatorService

AP_INVOICES

YES

INV_SUM_FOLDER

6

AP_APXINWKB_BATCHES

http://<ApplicationServerName>:<SOA Port>/axf-ws/AxfSolutionMediatorService

AP_INVOICES

YES

INV_SUM_FOLDER

4.2.3 Enabling E-Business Suite Logging

To enable logging for a particular Form function, set the LOGENABLED field to either 1, YES or TRUE and the file is created in the UTL_FILE_DIR folder. Consult with your DBA to verify that the UTL_FILE_DIR folder is available and accessible. Log files are named Username_MASTER_LOG.txt, and continue to grow as items are appended.