This appendix covers the following topics:
During implementation, you can set values for profile options at various levels to specify how the Oracle Landed Cost Management application controls access to and processes data. The system administrator sets and updates profile values. For more information see, Setting User Profile Options in the Oracle Applications System Administrator's - Maintenance Guide.
These profile options are unique to Oracle Landed Cost Management.
You can set the profile options described in this section in any order and at any level as indicated in the profile option tables:
Site (S)
Application (A)
Responsibility (R)
User (U)
In addition, most of the profile options have been provided with default values.
INL: Allow Simulations for Approved Purchase Orders
The profile determines whether landed cost simulations can be created or updated for approved purchase orders.
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
| Yes or No | No | Managing Simulated Landed cost | S |
INL: Allow to Copy and Cancel Completed Shipments
For the completed shipments, based on the action that you select on the Shipments Workbench page, this profile option enables you to:
Cancel a shipment
Copy a shipment and then cancel it
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
| Yes or No | No | Managing Landed Cost as a Pre-Receiving Application | S, A, R, and U |
INL: Allow Updates to Completed Shipments
This profile determines whether you can make changes to completed shipments.
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
| Yes or No | No | Managing Landed Cost as a Pre-Receiving Application Managing Landed Cost as a Service |
S |
INL: Default Currency Code for QP Charges Generation
This profile option is used in Oracle Advanced Pricing integration with Oracle Landed Cost Management.
This profile option defines the base currency used when integrating to Oracle Advanced Pricing. All the shipment line amounts are converted to this currency and the currency conversion type indicated in the profile options.
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
| All available currency codes | Blank | Integration with Oracle Advanced Pricing Generate Charges process |
S |
INL: Default Currency Conversion Type for QP Charges Generation
This profile option is used in Oracle Advanced Pricing integration with Oracle Landed Cost Management.
This profile option defines the currency conversion type used when integrating to Oracle Advanced Pricing. All the shipment line amounts are converted to this currency and the currency conversion type indicated in the profile options.
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
| All available currency conversion types | Blank | Integration with Oracle Advanced Pricing Generate Charges process |
S |
INL: Default Shipment Type for Open Interface
The system uses this profile option to determine the Shipment Type the Landed Cost Management shipment headers are created with, in the Managing Landed Cost as a Service flow, where Landed Cost Management shipments are automatically created for the receipts.
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
| All available shipment types | Blank | Managing Landed Cost as a Service | S |
This system uses this profile option to restrict the purchase order shipments to be integrated with Oracle Landed Cost Management based on item categories.
The system uses this profile option to define the category set used to extend the logic used during the purchase order approval process. If the profile option is enabled, the LCM calculation flag is set for items belonging to this category set.
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
| All available category sets | Blank | Managing Simulated Landed Cost Managing Landed Cost as a Pre-Receiving Application Managing Landed Cost as a Service |
S |
INL: Number of Days Filter for Landed Cost Analysis
The system uses this profile option as the default number of days filter for the Landed Cost Analysis page.
Note: If Oracle Information Discovery is installed and licensed in your environment, then refer to the Oracle E-Business Suite Information Discovery Integration and System Administration Guide for detailed information about the Information Discovery enhancements to the product.
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
| Any number | 28 | Landed Cost Analysis page | S |
INL: Number of Days Filter for Monitor Daily Operations
The system uses this profile option as the default number of days filter for the Monitor Daily Operations page.
Note: If Oracle Information Discovery is installed and licensed in your environment, then refer to the Oracle E-Business Suite Information Discovery Integration and System Administration Guide for detailed information about the Information Discovery enhancements to the product.
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
| Any number | 28 | Monitoring Daily Operations page | S |
Use this profile to indicate the class defined for each unit associated with "quantity" cost factors. The system uses this profile to determine the class used for the “quantity” allocation basis. This profile, along with the weight (INL: Weight UOM Class) and volume (INL: Volume UOM Class) profiles drive the Oracle Landed Cost Management UOM conversions for the Generate Charges and Calculate processes.
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
| All available classes | Blank | Generate Charges and Calculate processes. Managing Landed Cost as a Pre-Receiving Application and Managing Landed Cost as a Service |
S |
INL: Re-Prorate Change Invoice Amounts
Use this profile to indicate how charge invoice amounts that were automatically prorated in Oracle Payables (through Invoice matching of freight and miscellaneous charges to receipt lines) are reallocated in Oracle Landed Management. These charge line amounts are used in determining the actual landed cost of a shipment. Values are:
Blank (Not defined)
All cost factor amounts of an invoice (irrespective if their amounts were automatically prorated or manually entered) are summarized across all shipments and then reallocated using the allocation basis from the cost factor setup.
Across all Shipments
All cost factor amounts of an invoice that were automatically allocated in Oracle Payables are summarized before recalculating the cost factor amount matched to the shipment lines.
Note: Oracle Landed Cost Management does not apply any reallocation for those charge amounts that are manually entered in Oracle Payables.
By Purchase Order
The charge distribution lines of an invoice that are matched against receipt lines that belong to the same purchase order are summarized and then, the matched amount of each line is recalculated considering the allocation basis of the cost factor
This summarization process happens for each purchase order.
Note: Oracle Landed Cost Management does not apply any reallocation for those charge amounts that are manually entered in Oracle Payables.
By Shipment
The charge distribution lines of an invoice that are matched against receipt lines that belong to the same landed cost shipment are summarized and then, the matched amount of each line is recalculated considering the allocation basis of the cost factor.
This summarization process happens for each landed cost shipment
Note: Oracle Landed Cost Management does not apply any reallocation for those charge amounts that are manually entered in Oracle Payables.
Note: You can write your own code within the Matches Interface Hook INL_CUSTOM_PUB.Set_MatchesIntHook so that the Matches Interface Import concurrent program can generate charge lines using a different method than what is provided in the INL: Re-Prorate Charge Invoice Amounts profile option.
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
|
Blank (Not defined)
Note: If you do not set a value for this profile option, then all cost factor amounts of an invoice (irrespective if their amounts were automatically prorated or manually entered) are summarized across all shipments and then reallocated using the allocation basis from the cost factor setup. |
Matches Interface Import concurrent program. Calculating and Importing Actual Landed Cost for a Shipment Managing Landed Cost as a Pre-Receiving Application and Managing Landed Cost as a Service |
S |
Use this profile to indicate the class defined for each unit associated with "volume" cost factors. The system uses this profile to determine the class used for the “volume” allocation basis. This profile, along with the quantity (INL: Quantity UOM Class) and weight (INL: Weight UOM Class) profiles drive the Oracle Landed Cost Management UOM conversions for the Generate Charges and Calculate processes.
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
| All available classes | Blank | Generate Charges and Calculate processes. Managing Landed Cost as a Pre-Receiving Application and Managing Landed Cost as a Service |
S |
Use this profile to indicate the class defined for each unit associated with "weight" cost factors. The system uses this profile to determine the class used for the “weight” allocation basis. This profile, along with the quantity (INL: Quantity UOM Class) and volume (INL: Volume UOM Class) profiles drive the Oracle Landed Cost Management UOM conversions for the Generate Charges and Calculate processes.
| LOV Values | Default Value | Where Used | Supported Levels |
|---|---|---|---|
| All available classes | Blank | Generate Charges and Calculate processes. Managing Landed Cost as a Pre-Receiving Application and Managing Landed Cost as a Service |
S |