There are three system level profile options you must set. These affect all e-Commerce Gateway transactions:
Outbound directory.
Inbound directory.
Allow Split Words in Attachment.
There are other transaction level profile options.
Enable / disable each transaction.
Address derivation precedence.
Attachment segment size.
Enabling header-level attachments.
Enabling line-level attachments.
Enabling inventory line attachments.
Enabling master item attachments.
Note: There may be more profile options in other Oracle Applications products that affect e-Commerce Gateway. These products include: Purchasing, Inventory, Order Entry / Shipping, Payables, Receivables, Supplier Scheduling, and Planning.
This section lists system level profile options used in Oracle e-Commerce Gateway. Please note that each profile option is classified with a profile category. For more profile category information, seeOracle Applications System Administrator's Guide - Maintenance.
Indicate the directory where inbound interface data files are expected. This value must match the actual directory on disk and that designated in the INIT.ORA file.
Indicate the directory where outbound interface data files are written. This value must match the actual directory on disk and that designated in the INIT.ORA file.
Note: For the e-Commerce Gateway, you must create inbound and outbound directories on your server, and then specify them in the INIT.ORA file and in the "ECE: Inbound directory" and "ECE: Outbound file path" profile options, respectively. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.
An attachment is usually plain text used as a note.
If you allow words to be split in an attachment, a new line begins within a word. If you do not allow words to be split, the new line is created after a space or a punctuation mark, not within a word. Thus, if you do not allow words to be split, some segment sizes fall below the attachment segment size, and vice versa.
New lines are created once the current line reaches the attachment segment size. For further information, refer to attachment segment size profile options for individual transactions.
Each transaction has a common set of profile options. For purposes of brevity, each type is documented below. For complete documentation, see: Oracle e-Commerce Gateway Profile Options, Oracle e-Commerce Gateway Implementation Manual.
Each of the profile options below lists the variable <transaction_code>. For a listing of the transaction codes used below, see: EDI Transaction Support.
Indicates whether the transaction is enabled at the site level. The default is Yes.
Applies to inbound transactions only. Determines the precedence by which trading partner addresses are derived.
When inbound EDI transactions are imported into Oracle Applications, the unique business site address must be established before the transaction can be processed. Each trading partner must have a unique address.
A trading partner is a site, such as a plant, a warehouse, a bank branch, or some other business unit. A trading partner is not necessarily a company; one company can have several sites.
The correct address can be obtained from three categories of components. They have unique address ids, location code/translator codes, location names, and physical addresses. These addresses are verified and validated as transactions are processed.
When you set this profile option using the Transaction Profiles window, you must select from the following values:
LOC (Default)- Address components and/or location code combination
The address is derived from the combination of location code and address components. If there is only one value provided, either location code or address components, the address will be derived based on the provided value. If both location code and address components are provided, then it will be based on the combination of both.
Note: If no address is found for both location code and address components or if the populated address components and location code do not match, then a message "Unable to derive ship to address" will appear.
If both location code and physical address are provided, then it will derive address through location code and compare it with that derived through physical address.
LTC - Location code/translator code combination
A trading partner must be set up first so that the address can be derived.
LPA - Location code/physical address/party details combination
The correct address is derived through the combination of location code, customer name, customer number, and address components. If there is only a partial set of values provided, the address will be derived based on the provided values.
Note: This feature is available only for address type "CUSTOMER".
You must set up each inbound transaction to derive the correct address.
The following profile options apply only to the Purchase Order Outbound (POO) and Purchase Order Change Request Outbound (POCO) transactions:
Enables the header attachment for the transaction. The default is No.
Enables the line attachment for the transaction. The default is No.
Enables the master item attachment for the transaction. The default is No.
Enables the inventory item attachment for the transaction. The default is No.
Enables the shipment attachment for the transaction. The default is No.
Sets the attachment segment size for the transaction. Attachments can be split into segments to accommodate their insertion into the interface data file. The segment size is expressed in bytes. The default is 400.
Additional Information: For more information, see:
Profile Options, Oracle e-Commerce Gateway Implementation Manual