1 System Options
Import Management system options are either set to default values at the time of installation, or are configured manually in the UI by a system administrator. These system options control functionality related to the importing of goods into one or more countries, and are displayed in the Import Management section of the Merchandising System Options page. In order to use the importing functionality in Merchandising, you will need to set the Import Management flag to Yes (Y) during Initial System Configuration. For details on enabling importing functionality, see the "Import Management" section in the "Initial System Configuration" chapter of the Merchandising Implementation Guide. Details of all other import-related system options can be found below.
These system options should be configured based on the requirements/rules of your business. It is assumed most of these options will remain fixed unless a business practice is changed which necessitates a change.
| System Option | Optional? | Re-configuration Restricted? | Default Value | Description |
|---|---|---|---|---|
|
Import Management and Simplified Import Management |
No |
Yes |
Y |
See the "System Options Required During Initial System Configuration" section in the Merchandising Implementation Guide. |
|
Allocate Shipment Level Obligations Using |
See the "System Options Required During Initial System Configuration" section in the Merchandising Implementation Guide. |
|||
| Extend Transportation Input State | No | No | N | Indicates whether the transportation key values (that is, Vessel, Voyage/Flight, Estimated Departure Date, Order No., Item, Container, BL/AWB, Commercial Invoice) will remain in an extended input state or not. Valid values are Yes (Y) or No (N). When set to Yes (Y), the key value fields will remain editable after values have been provided, up until the transportation record is added to a customs entry or obligation. When set to No (N), the key value fields will be restricted from editing as soon as a value is provided and saved. If this value is changed, it will only impact the ability to edit key values on transportation records from that point forward. |
|
Letter of Credit |
||||
|
Type |
No |
No |
M |
Contains the default form type when creating a letter of credit. The form type determines the level of detail that will be sent to the issuing bank. Valid values include Master (M) where there is one letter of credit to many PO; Normal (N), where there is one letter of credit to on PO; Open (O), where no details are added and the amount is entered directly; or Revolving (R) which support multiple shipments and payments/drawdowns over a period of time, either from a single PO or Multiple POs. |
|
Form Type |
No |
No |
L |
Contains the default form type used when creating new letters of credit. The form type determines the level of detail that will be sent to the issuing bank. Valid values are Long (L) or Short (S). The long form contains item level details on a PO, whereas the short form is only at the PO level. |
|
Title Pass Location Type |
Yes |
No |
The title pass location is used to determine where the title for goods is passed from the supplier to the retailer. Examples include city, factory, or origin. Contains the default title pass options that will default onto purchase orders when created. Valid values for this system option are held under the FOBT code type. |
|
|
Expiration Days |
Yes |
No |
30 |
Indicates the default number of days after the latest ship date that a letter of credit will expire. |
|
Harmonized Tariff Schedules (HTS) |
||||
|
Tracking Level |
No |
S |
Indicates the level at which HTS is tracked - either by sourcing country (S) or manufacturing country (M). This value is set on initial installation and cannot be changed. If a value isn't provided on install, it will default to sourcing country. |
|
|
Update Items When Loading Data |
No |
Yes |
Y |
Indicates whether items should be automatically updated when new HTS information is uploaded. Valid values are Yes (Y) or No (N). |
|
Update Order/Items When Loading Data |
Yes |
Yes |
N |
Indicates whether order/items should be automatically updated when new HTS information is uploaded. Valid values are Yes (Y) or No (N). |
|
Effective Date on Purchase Order |
Yes |
Yes |
N |
Determines which purchase order date is used to determine if an HTS code is valid for a purchase order. The date defined here must fall within the effective date range on the HTS definition. Valid values are Written Date (W) or Not After Date (N). |
|
Warn when Orders Missing HTS |
N |
Indicates whether or not to display a warning message to the user when attempting to submit or approve an order where one or more items on the order are missing an HTS classification or they have an HTS classification that is not in Approved status. If it is set to No, no validation will be done to check for approved HTS codes on the order. If it is set to Yes, the validation will be done and a warning message will display to the user when submitting or approving the order when this issue occurs. Note that users will still be able to proceed with submitting or approving even with this issue. With either setting, it is important to have processes in place such that HTS codes are assigned prior to your import orders reaching customs to prevent delays. Valid values are Yes (Y) or No (N). |
||
There is also a system option that is not currently displayed in the system options page in Merchandising. This option will be defaulted on installation, but can be changed. However, for a cloud service implementation it will require assistance from the Oracle Cloud Operations team to make the update.
| System Option | Optional? | Re-configuration Restricted? | Default Value | Description |
|---|---|---|---|---|
|
Automatically Reapprove Updated Orders |
No |
See note above |
W |
Indicates whether approved orders that have HTS/item information updated should remain in approved status after the updates are applied or should be set back to worksheet status for review of cost impact based on the updates. |