Outbound Transactions

This chapter covers the following topics:

Extensible Architecture

The Oracle e-Commerce Gateway provides two methods to add additional data elements that are not defined in Oracle E-Business Suite to EDI transactions:

Either method may be used separately, or both methods may be used together to customize a specific transaction to meet business needs. Descriptive flexfields may be used for both inbound and outbound transactions, while extensible architecture applies only to outbound transactions.

Most business needs for additional data can be accommodated by the use of descriptive flexfields. Use extensible architecture if data from an outside application must be merged with Oracle E-Business Suite data to create a single outbound transaction.

For complete information, see: Extensible e-Commerce Gateway Architecture, Oracle e-Commerce Gateway Implementation Manual.

Multiple Organizations and Outbound Transactions

Since Oracle e-Commerce Gateway allows you to associate Trading Partners with operating units linked to your responsibility through the Trading Partner Group setup, an outbound transaction can be extracted through the following concurrent programs depending on whether the Trading Partner of the transaction is associated with a single operating unit or multiple ones:

Running the Application Advice Outbound (ADVO) Extract Program

Use this transaction to acknowledge transaction errors for the following inbound transactions:

The respective inbound transactions write data regarding errors including the error message code, error message text and erroneous data to the application advice tables in the e-Commerce Gateway product. The processing errors are reported to the trading partner using the Application Advice transaction.

Prerequisite Setup in Oracle Purchasing and Oracle Payables

There is no prerequisite setup in Oracle Purchasing or Oracle Payables. However, Purchasing and Payables maintain application open interface audit reports.

Prerequisites

To run the Application Advice outbound extract program:

  1. Navigate to the Run e-Commerce Outbound Process window:

    • Process > Extract Program

    • In the Submit a New Request window, select Single Request to submit an individual request.

  2. In the Name field of the Run e-Commerce Outbound Process window, select OUT: Application Advice (824/APERAK) from the LOV.

  3. Select an operating unit from the LOV so that the concurrent program will extract data for the particular operating unit. If you have more than one operating unit linked to your responsibility, then you must specify each operating unit individually for the program in order to extract data for all the operating units.

  4. The Parameters window will open. Enter the following parameters as necessary:

    • Output File Name: Enter an output file name or accept the default.

    • Trading Partner Group: Enter the Trading Partner Group name.

    • Trading Partner: Enter the Trading Partner name.

    • Response to Document: Enter Response to Document to indicate which application advice messages to extract related to which inbound transactions.

    • Transaction Date From: Enter the date from which to extract transactions.

    • Transaction Date To: Enter the date to which to extract transactions.

    • External Reference 1: Enter the first external reference relevant for the document name. For example, enter ASN number for inbound Ship Notice / Manifest or invoice number for inbound invoices.

    • External Reference 2: Enter second external reference relevant for the document name. For example, enter shipment number for inbound Ship Notice / Manifest.

    • External Reference 3 - 6: Enter the next four external references relevant for the document name.

    • Debug Mode for ADVO: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:

      OFF: No debug information is generated.

      LOW: Summary debug information is written to the concurrent manager log file.

      MEDIUM: Medium level debug information is written to the concurrent manager log file.

      HIGH: High level debug information is written to the concurrent manager log file. (This option generates much information.)

  5. Enter any Schedule and Completion Options for the request.

  6. Choose Submit and make a note of the Request ID returned.

Note: For additional information, see:

Outbound Application Advice, Oracle e-Commerce Gateway Implementation Manual

Submitting a Request, Oracle E-Business Suite User's Guide

Viewing the Status of Concurrent Programs

Running the INTRASTAT Movement Statistics (MVSTO) Extract Program

Intrastat is the system for collecting statistics on the trade of goods between members of the European Union. Intrastat requires the reporting of movement statistics within a country. Extrastat is the collection of statistics on the trade of goods between members and nonmembers of the European Union. Statistics are reported to the material tax authorities of the respective countries.

Oracle e-Commerce Gateway supports these requirements by providing Intrastat and Extrastat messages for the automatic extraction and electronic processing of movement statistics.

Subsets of the EDIFACT Customs Declaration (CUSDEC) message are used to report material movement statistics. The CUSDEC subset INSTAT reports movement statistics within the European Union. The CUSDEC subset EXSTAT reports movement statistics outside the European Union.

As data is extracted from e-Commerce Gateway, only movement statistics with the status of Verify or Frozen are extracted. Once data is extracted, the e-Commerce Gateway sets the transaction status to EDI.

Note: Oracle e-Commerce Gateway extracts data from Oracle Purchasing, Oracle Inventory, and Oracle Order Management tables. However, you only need licenses to one of these applications to run the Movement Statistics program.

For more information on Intrastat, see:

Prerequisites

To run the INTRASTAT movement statistics (MVSTO) extract program:

  1. Navigate to the Run e-Commerce Outbound Process window:

    • Process > Extract Program

    • In the Submit a New Request window, select Single Request to submit an individual request.

  2. In the Name field of the Run e-Commerce Outbound Process window, select OUT: Movement Statistics (for INTRASTAT) from the LOV.

  3. Select an operating unit from the LOV so that the concurrent program will extract data for the particular operating unit. If you have more than one operating unit linked to your responsibility, then you must specify each operating unit individually for the program in order to extract data for all the operating units.

  4. The Parameters window will open. Enter the following parameters as necessary:

    • Output File Path: (Required) Specify and output file path or accept the default.

    • Output File Name: (Required) Enter an output file name or accept the default.

    • Legal Entity: (Required) The legal entity entered must match the setup for movement statistics parameters.

    • Zone Code: (Required) The zone code entered must match the economic zone associated with the legal entity in the movement statistics setup.

    • Stat Type: (Required) Enter INTRASTAT or EXTRASTAT.

    • Period Name: The period name must match the period associated with the legal entity in the movement statistics setup.

    • Movement Type: (Required) Enter the movement type: Arrival, Arrival Adjustment, Dispatch, or Dispatch Adjustment.

    • Include Address: (Required) Indicate whether to include the address in the transaction document.

    • Debug Mode for MVSTO: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:

      OFF: No debug information is generated.

      LOW: Summary debug information is written to the concurrent manager log file.

      MEDIUM: Medium level debug information is written to the concurrent manager log file.

      HIGH: High level debug information is written to the concurrent manager log file. (This option generates much information.)

  5. Enter any Schedule or Completion options for the request..

  6. Choose Submit and make a note of the Request ID.

Note: For additional information, see:

Movement Statistics (INTRASTAT), Oracle e-Commerce Gateway Implementation Manual

Movement Statistics, Oracle Purchasing User's Guide

Defining Economic Zones and Defining Movement Statistic Parameters, Oracle Inventory User's Guide

Submitting a Request, Oracle E-Business Suite User's Guide

Viewing the Status of Concurrent Programs

Running the Invoice Outbound (INO) Extract Program

Use this transaction to bill customers for goods sold and services rendered.

Prerequisite Setup in Oracle Receivables

Use Receivables to enter or adjust customer invoices.

You have the option of including credit memos and debit memos in this transaction. Or, you may generate them separately using the Credit Memo / Debit Memo Outbound transaction. See: Running the Credit Memo / Debit Memo (CDMO) Extract Program.

In addition to entering customer invoices manually, you may also use AutoInvoice feature of Receivables to import customer invoices from non-Oracle financial systems before executing this transaction.

Note: Descriptive flexfields may be needed for some data elements.

Prerequisites

To run the Invoice outbound extract program:

  1. Navigate to the Run e-Commerce Outbound Process window:

    • Process > Extract Program

    • In the Submit a New Request window, select Single Request to submit an individual request.

  2. In the Name field of the Run e-Commerce Outbound Process window, select OUT: Invoice (810/INVOIC) from the LOV.

  3. Select an operating unit from the LOV so that the concurrent program will extract data for the particular operating unit. If you have more than one operating unit linked to your responsibility, then you must specify each operating unit individually for the program in order to extract data for all the operating units.

  4. The Parameters window will open. Enter the following parameters as necessary:

    • Output File Name: Enter an output file name or accept the default.

    • Creation Date From: Enter the creation date from which to extract transactions.

    • Creation Date To: Enter the creation date to which to extract transactions.

    • Customer Name: Enter the bill-to customer name.

    • Customer Site Name: Enter the bill-to customer site name.

    • Document Type: Enter the document type: Credit Memo, Debit Memo, or Invoice.

    • Transaction Number: Enter a transaction (invoice) number.

    • Debug Mode for INO: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:

      OFF: No debug information is generated.

      LOW: Summary debug information is written to the concurrent manager log file.

      MEDIUM: Medium level debug information is written to the concurrent manager log file.

      HIGH: High level debug information is written to the concurrent manager log file. (This option generates much information.)

  5. Enter any Schedule or Completion Options for the request.

  6. Choose Submit and make a note of the Request ID returned.

Note: For additional information, see:

Outbound Invoice, Oracle e-Commerce Gateway Implementation Manual

Submitting a Request, Oracle E-Business Suite User's Guide

Viewing the Status of Concurrent Programs

Running the Credit Memo / Debit Memo (CDMO) Extract Program

Use this transaction to process credit and debit memos that are generated in Oracle Receivables. You can generate credit memos and debit memos in the transaction, or have them generated with the Invoice Outbound transaction. See: Running the Invoice Outbound (INO) Extract Program.

Prerequisite Setup in Oracle Receivables

Use Receivables to enter credit memos (to customer invoices) and debit memos.

Prerequisites

To run the Credit Memo / Debit Memo outbound extract program:

  1. Navigate to the Run e-Commerce Outbound Process window:

    • Process > Extract Program

    • In the Submit a New Request window, select Single Request to submit an individual request.

  2. In the Name field of the Run e-Commerce Outbound Process window, select OUT: Credit/Debit Memo (812) from the LOV.

  3. Select an operating unit from the LOV so that the concurrent program will extract data for the particular operating unit. If you have more than one operating unit linked to your responsibility, then you must specify each operating unit individually for the program in order to extract data for all the operating units.

  4. The Parameters window will open. Enter the following parameters as necessary:

    • Output File Name: Enter an output file name or accept the default.

    • Debug Level: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:

      OFF: No debug information is generated.

      LOW: Summary debug information is written to the concurrent manager log file.

      MEDIUM: Medium level debug information is written to the concurrent manager log file.

      HIGH: High level debug information is written to the concurrent manager log file. (This option generates much information.)

    • Customer Name: Enter the bill-to customer name.

    • Transaction Number: Enter the transaction number.

    • Creation Date From: Enter the creation date from which to extract transactions.

    • Creation Date To: Enter the creation date to which to extract transactions.

    • Site Name: Enter the bill-to customer site name.

    • Document Type: Enter the document type: Credit Memo or Debit Memo.

  5. Enter any Schedule or Completion Options for the request.

  6. Choose Submit and make a note of the Request ID returned.

Note: For additional information, see:

Outbound Credit Memo / Debit Memo, Oracle e-Commerce Gateway Implementation Manual

Submitting a Request, Oracle E-Business Suite User's Guide

Viewing the Status of Concurrent Programs

Running the Planning and Shipping Schedule (SSSO and SPSO) Extract Program

Use the planning schedule to communicate forecast requirements to your suppliers. The planning schedules may be comprised of both forecast and material release information including authorizations from the buyer to commit material and labor resources for a specific period. The planning schedule may be stated in daily, weekly, monthly, quarterly, or in any combination of periods.

Use the shipping schedule to communicate short-term firm requirements and shipping schedules to your suppliers. Shipping schedules are usually stated in daily buckets and are used to refine planning schedules in support of a Just-in-Time planning environment.

In addition to using e-Commerce Gateway to transmit your planning or shipping schedules, you may transmit the schedules using the Scheduler Workbench or AutoSchedule process in Oracle Supplier Scheduling. With the Scheduler Workbench, you select the schedules using the schedule ID. With AutoSchedule, all built and confirmed schedules designated for electronic transmission are sent if they were not previously sent.

Prerequisite Setup in Oracle E-Business Suite

Prerequisites

To run the Planning and Shipping Schedule extract program:

  1. Navigate to the Run e-Commerce Outbound Process window:

    • Process > Extract Program

    • In the Submit a New Request window, select Single Request to submit an individual request.

  2. In the Name field of the Run e-Commerce Outbound Process window, select OUT: Planning Schedule (830/DELFOR) or OUT: Shipping Schedule (862/DELJIT) from the LOV.

  3. Select an operating unit from the LOV so that the concurrent program will extract data for the particular operating unit. If you have more than one operating unit linked to your responsibility, then you must specify each operating unit individually for the program in order to extract data for all the operating units.

  4. The Parameters window will open. Enter the following parameters as necessary:

    • Output File Name: Enter an output file name or accept the default.

    • Schedule ID: Enter the schedule ID.

    • ECE_DEBUG_MODE: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:

      OFF: No debug information is generated.

      LOW: Summary debug information is written to the concurrent manager log file.

      MEDIUM: Medium level debug information is written to the concurrent manager log file.

      HIGH: High level debug information is written to the concurrent manager log file. (This option generates much information.)

  5. Enter any Schedule and Completion Options for the request.

  6. Choose Submit and make a note of the Request ID returned.

Note: For additional information, see:

Outbound Planning Schedule, Oracle e-Commerce Gateway Implementation Manual

Outbound Shipping Schedule, Oracle e-Commerce Gateway Implementation Manual

Submitting a Request, Oracle E-Business Suite User's Guide

Viewing the Status of Concurrent Programs

Running the Purchase Order Outbound (POO) Extract Program

Use this transaction to procure goods and services from suppliers. Approved purchase orders (POs), including standard POs, planned orders, planned releases, blanket purchase agreement, and blanket releases can be extracted.

Note: This transaction is not used to convey PO change or acknowledgment information.

Procurement Card Information

The Outbound Purchase Order transaction includes procurement card information in the interface data file. This includes credit card type, credit card number, and expiration date.

You can attach text to the outbound Purchase Order and the Purchase Order Change Request transactions at the header, line, and shipment levels.

Prerequisite Setup in Oracle Purchasing

Use Purchasing to convert purchase requisitions to POs or to create new POs, planned orders, blanket purchase agreements or blanket releases. Use Purchasing to approve POs before transmitting them to your supplier.

You can attach text to the outbound Purchase Order and the Purchase Order Change Request transactions at the header, line, and shipment levels. See: Attachments.

Prior to approving any purchase orders, make sure that the Approve On option is set to Archive for all document types. Do this from Purchasing by navigating to Setup > Purchasing > Document Types.

Prerequisites

Note: Both the outbound Purchase Order and Purchase Order Change Request transactions allow attachments. See: Attachments.

To run the purchase order outbound extract program:

  1. Navigate to the Run e-Commerce Outbound Process window:

    • Process > Extract Program

    • In the Submit a New Request window, select Single Request to submit an individual request.

  2. In the Name field of the Run e-Commerce Outbound Process window, select OUT: Purchase Order (850/ORDERS) from the LOV.

  3. Select an operating unit from the LOV so that the concurrent program will extract data for the particular operating unit. If you have more than one operating unit linked to your responsibility, then you must specify each operating unit individually for the program in order to extract data for all the operating units.

  4. The Parameters window will open. Enter the following parameters as necessary:

    • Output File Name: Enter an output file name or accept the default.

    • PO Number From: Enter the PO number from which to extract transactions.

    • PO Number To: Enter the PO number to which to extract transactions.

    • Creation Date From: Enter the creation date from which to extract transactions.

    • Creation Date To: Enter the creation date to which to extract transactions.

    • PO Type: Enter the PO type: Blanket PO, Blanket Release, Planned PO, or Standard PO.

    • Supplier Name: Enter the supplier name.

    • Supplier Site Code: Enter the supplier site code.

    • Debug Mode for POO: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:

      OFF: No debug information is generated.

      LOW: Summary debug information is written to the concurrent manager log file.

      MEDIUM: Medium level debug information is written to the concurrent manager log file.

      HIGH: High level debug information is written to the concurrent manager log file. (This option generates much information.)

  5. Enter any Schedule or Completion Options for the request.

  6. Choose Submit and make a note of the Request ID returned.

Note: For additional information, see:

Outbound Purchase Order, Oracle e-Commerce Gateway Implementation Manual

Submitting a Request, Oracle E-Business Suite User's Guide

Viewing the Status of Concurrent Programs

Running the Outbound Purchase Order Change Request (POCO) Extract Program

Use this transaction to request a change to a previously submitted purchase order (PO). You may include changes for approved POs of the type standard POs, planned POs, planned releases, blanket purchase agreements, and blanket releases.

Please note that the generated output file contains information for the entire purchase orders, not just the data for the fields that were changed on the purchase order.

Supported changes by this transaction include:

Cancelling a PO at the header level cancels every line associated with the PO. New lines are appended to the end; old line numbers are not reused.

To maintain shipment data integrity, all shipment information associated with a PO line are sent to the supplier, even if changes were made to only one shipment.

Note: Check with the trading partner to verify their ability to process any type of change.

Procurement Card Information

The Outbound Purchase Order Change Request transaction includes procurement card information in the interface data file. This includes credit card type, credit card number, and expiration date.

You can attach text to the outbound Purchase Order and the Purchase Order Change Request transactions at the header, line, and shipment levels.

Prerequisite Setup in Oracle Purchasing

Use Purchasing to change an existing purchase order or blanket purchase agreement. You may cancel a line, add a line, change the line price or quantity, change the ship-to location, or shipment date or quantity.

You can attach text to the outbound Purchase Order and the Purchase Order Change Request transactions at the header, line, and shipment levels. See: Attachments.

If your Purchasing system option is set to Archive on Approval, you must reapprove changed POs before transmitting them to your supplier.

Prerequisites

Note: Both the outbound Purchase Order and Purchase Order Change Request transactions allow attachments. See: Attachments.

To run the Purchase Order Change extract program:

  1. Navigate to the Run e-Commerce Outbound Process window:

    • Process > Extract Program

    • In the Submit a New Request window, select Single Request to submit an individual request.

  2. In the Name field of the Run e-Commerce Outbound Process window, select OUT: Purchase Order Change (860/ORDCHG) from the LOV.

  3. Select an operating unit from the LOV so that the concurrent program will extract data for the particular operating unit. If you have more than one operating unit linked to your responsibility, then you must specify each operating unit individually for the program in order to extract data for all the operating units.

  4. The Parameters window will open. Enter the following parameters as necessary:

    • Output File Name: Enter an output file name or accept the default.

    • PO Number From: Enter the PO number from which to extract transactions.

    • PO Number To: Enter the PO number to which to extract transactions.

    • Revision Date From: Enter the revision date from which to extract transactions.

    • Revision Date To: Enter the revision date to which to extract transactions.

    • PO Type: Enter the PO type: Blanket PO, Blanket Release, Planned PO, or Standard PO.

    • Supplier Name: Enter the supplier name.

    • Supplier Site Code: Enter the supplier site code.

    • Debug Mode for POCO: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:

      OFF: No debug information is generated.

      LOW: Summary debug information is written to the concurrent manager log file.

      MEDIUM: Medium level debug information is written to the concurrent manager log file.

      HIGH: High level debug information is written to the concurrent manager log file. (This option generates much information.)

  5. Enter and Schedule and Completion Options for the request..

  6. Choose Submit and make a note of the Request ID returned.

Note: For additional information, see:

Outbound Purchase Order Change Request, Oracle e-Commerce Gateway Implementation Manual

Submitting a Request, Oracle E-Business Suite User's Guide

Viewing the Status of Concurrent Programs

Running the Purchase Order Acknowledgment Outbound (POAO) Extract Program

Use this transaction to export customer purchase orders acknowledgment from your Oracle Order Management system.

Prerequisite Setup in Oracle Order Management

The required Order Management setup steps for the purchase order acknowledgments are the following:

  1. Define Customers and Customer Sites in Order Management/Oracle Receivables.

  2. Define Order Types in Order Management.

  3. Define items and appropriate customer items in Oracle Inventory.

Prerequisites

To run the Purchase Order Acknowledgment Outbound extract program:

  1. Navigate to the Run e-Commerce Outbound Process window:

    • Process > Extract Program

    • In the Submit a New Request window, select Single Request to submit an individual request.

  2. In the Name field of the Run e-Commerce Outbound Process window, select OUT: Purchase Order Acknowledgments (855/ORDRSP) from the LOV.

  3. Select an operating unit from the LOV so that the concurrent program will extract data for the particular operating unit. If you have more than one operating unit linked to your responsibility, then you must specify each operating unit individually for the program in order to extract data for all the operating units.

  4. The Parameters window will open. Enter the following parameters as necessary:

    • File Name: Enter an output file name or accept the default.

    • Debug Mode: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:

      OFF: No debug information is generated.

      LOW: Summary debug information is written to the concurrent manager log file.

      MEDIUM: Medium level debug information is written to the concurrent manager log file.

      HIGH: High level debug information is written to the concurrent manager log file. (This option generates much information.)

    • Customer Number: Enter the customer number.

    • Customer Name: Enter the customer name.

    • Sales Order Reference From: Enter the sales order reference number from which to extract transactions.

    • Sales Order Reference To: Enter the sales order reference number to which extract transactions.

    • Sales Order Number From: Enter the sales order number from which to extract transactions.

    • Sales Order Number To: Enter the sales order number to which to extract transactions.

    • Purchase Order Number From: Enter the purchase order number from which to extract transactions.

    • Purchase Order Number To: Enter the purchase order number to which to extract transactions.

    • Date From: Enter the date from which to extract transactions.

    • Date To: Enter the date to which to extract transactions.

  5. Enter any Schedule or Completion Options for the request..

  6. Choose Submit and make a note of the Request ID returned.

Note: For additional information, see:

Oracle e-Commerce Gateway Implementation Guide

Outbound Purchase Order Acknowledgments, Oracle e-Commerce Gateway Implementation Guide

Submitting a Request, Oracle E-Business Suite User's Guide

Viewing the Status of Concurrent Programs

Running the Purchase Order Change Acknowledgment Outbound (POCAO) Extract Program

Use this transaction to export customer purchase order change acknowledgment from your Oracle Order Management system.

Prerequisite Setup in Oracle Order Management

The required Order Management setup steps for the purchase order change acknowledgments are the following:

  1. Define Customers and Customer Sites in Order Management/Oracle Receivables.

  2. Define Order Types in Order Management.

  3. Define Items and appropriate customer items in Oracle Inventory.

Prerequisites

To run the PO Change Acknowledgment Outbound extract program:

  1. Navigate to the Run e-Commerce Outbound Process window:

    • Process > Extract Program

    • In the Submit a New Request window, select Single Request to submit an individual request.

  2. In the Name field of the Run e-Commerce Outbound Process window, select OUT: Purchase Order Change Acknowledgments (865/ORDRSP) from the LOV.

  3. Select an operating unit from the LOV so that the concurrent program will extract data for the particular operating unit. If you have more than one operating unit linked to your responsibility, then you must specify each operating unit individually for the program in order to extract data for all the operating units.

  4. The Parameters window will open. Enter the following parameters as necessary:

    • File Name: Enter an output file name or accept the default.

    • Debug Mode: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:

      OFF: No debug information is generated.

      LOW: Summary debug information is written to the concurrent manager log file.

      MEDIUM: Medium level debug information is written to the concurrent manager log file.

      HIGH: High level debug information is written to the concurrent manager log file. (This option generates much information.)

    • Customer Number: Enter the customer number.

    • Customer Name: Enter the customer name.

    • Sales Order Reference From: Enter the sales order reference number from which to extract transactions.

    • Sales Order Reference To: Enter the sales order reference number to which extract transactions.

    • Sales Order Number From: Enter the sales order number from which to extract transactions.

    • Sales Order Number To: Enter the sales order number to which to extract transactions.

    • Purchase Order Number From: Enter the purchase order number from which to extract transactions.

    • Purchase Order Number To: Enter the purchase order number to which to extract transactions.

    • Date From: Enter the date from which to extract transactions.

    • Date To: Enter the date to which to extract transactions.

  5. Enter any Schedule or Completion Options for the request.

  6. Choose Submit and make a note of the Request ID returned.

Note: For additional information, see:

Oracle e-Commerce Gateway Implementation Guide

Outbound Purchase Order Change Acknowledgments, Oracle e-Commerce Gateway Implementation Guide

Submitting a Request, Oracle E-Business Suite User's Guide

Viewing the Status of Concurrent Programs

Running the Ship Notice/Manifest Outbound (DSNO) Extract Program

Use this transaction to list the contents of a shipment including trip and delivery data such as carrier, parties involved with the shipment, container, order; product data such as description, physical characteristics, type of packaging, lot and serial numbers; and allowances and charges.

This transaction is initiated by the Oracle Shipping Execution application or by Oracle e-Commerce Gateway if necessary.

Use Oracle Order Management to enter and maintain customer orders. Alternately, Order Management's Order Import open interface can be used to import customer orders from non-Oracle order management systems and EDI transactions.

After the customer order is entered, use Order Management to book, approve, and then use Shipping Execution to schedule shipments. During the shipment preparation process, inventory is released, pick slips are printed, shipping documents are prepared, and the shipment is confirmed.

Prerequisite Setup in Oracle Shipping Execution

Once the delivery is ship confirmed and the pick up stop is closed a DSNO is automatically generated. A DSNO may be manually generated by choosing a stop that has already been closed. A delivery may be a truck load containing x number of items in y number of boxes defined and in z number of pallets.

After the pick up stop is closed, the shipping process initiates the transaction through the Oracle e-Commerce Gateway. This transaction is event-driven by the shipping process; it is not driven by a scheduled concurrent manager request.

Oracle e-Commerce Gateway can be used to reinitiate the process, if necessary. This section documents how to extract the transaction again as needed.

Note: Descriptive flexfields may be needed for some data elements.

Prerequisites

To run the Ship Notice/Manifest Outbound extract program:

Note: Performing this procedure from e-Commerce Gateway is only necessary if you need to extract the shipment notice again.

  1. Navigate to the Run e-Commerce Outbound Process window:

    • Process > Extract Program

    • In the Submit a New Request window, select Single Request to submit an individual request.

  2. In the Name field of the Run e-Commerce Outbound Process window, select OUT: Ship Notice/Manifest (856/DESADV) from the LOV.

  3. Select an operating unit from the LOV so that the concurrent program will extract data for the particular operating unit. If you have more than one operating unit linked to your responsibility, then you must specify each operating unit individually for the program in order to extract data for all the operating units.

  4. The Parameters window will open. Enter the following parameters as necessary:

    • Trip: Enter the trip identifier.

    • Trip Stop: Enter the trip stop identifier.

  5. Enter any Schedule or Completion Options for the request.

  6. Choose Submit and make a note of the Request ID returned.

Note: For additional information, see:

Outbound Invoice, Oracle e-Commerce Gateway Implementation Manual

Submitting a Request, Oracle E-Business Suite User's Guide

Viewing the Status of Concurrent Program

Running the Payment Outbound Transaction Using Generic Outbound Engine

The payment outbound transaction uses generic outbound engine to electronically make a payment, or make a payment and send a remittance advice to your creditors.

The payment portion of this transaction is a request to your financial institution to perform cash application to relieve your account and to pay your payee's account.

The remittance advice portion of this transaction contains the payment distribution by invoice. It may be sent directly to the payee, through a financial institution, or through a third party. In addition, you may use Oracle Payables to print your remittance advice.

Payments made using electronic funds transfer (EFT) may be processed through EDI if your EDI translator has the means to download the payment data from Payables to tape for delivery to the payee's bank.

Prerequisite Set Up in Oracle Payables

Use Payables to enable the payer and payee site.

Use the Payment Workbench to enter and approve invoices, and to release invoice holds. Use Oracle Payments to select invoices for payment, create a payment instruction, and submit the EDI payment transaction. This transaction is event-driven and integrated with the standard Payables payment process. It cannot be initiated through Oracle e-Commerce Gateway. However, you must use Oracle e-Commerce Gateway to set up the trading partner and enable the transaction.

This payment outbound transaction is launched by Payment process if the value for the Electronic Processing Channel in the Payment Process Profile setup page is set to Oracle e-Commerce Gateway. The EDI format definitions in the previous release are upgraded into payment process profiles with the electronic processing channel set appropriately.

Prerequisites

To run the payment outbound transaction:

Note: For additional information, see:

Outbound Payment Order / Remittance Advice, Oracle e-Commerce Gateway Implementation Manual

Attachments

You can attach text to the outbound Purchase Order and the Purchase Order Change Request transactions at the header, line, and shipment levels.

Attachments can be stored as short text (up to 2 Kilobytes) or long text (up to 2 Gigabytes) of data. Each attachment can be split into segments (or records).

Segment size is set using the POO Attachment Segment Size and/or the POCO Attachment Segment Size profile options. The default for both profile options is 400 bytes.

For additional information, see: Oracle e-Commerce Gateway Profile Options.