Oracle Apps Adapter 6.0 | webMethods Oracle Applications Adapter Documentation | webMethods Oracle Applications Adapter 12.2.7 Predefined Transaction Services Documentation | Order Management Predefined Transaction Services | Query Advanced Shipping Notice Service
 
Query Advanced Shipping Notice Service
This service is in the WmOAOMG1227 package and has the following fully-qualified service name: shipping1227.queryOA.ASN:queryASN
This service queries for advanced shipping notices. Advanced Shipping Notice/Departure Shipping Notice (ASN/DSNO) automatically runs when there is confirmation of a shipment delivery for a sales order. The DSNO generates when delivery is ship-confirmed.
You can use the following parameters to query for DSNO data:
*CUSTOMER_NAME: Name of the customer who placed the sales order.
*CUSTOMER_NUMBER: Unique identifier for the customer.
*ORGANIZATION_NAME
*ORDER_NUMBER: Unique number assigned to the order when creating it.
*ORDER_DATE_FROM: Beginning date when the order was placed.
*ORDER_DATE_TO: Ending date when the order was placed.
*SHIP_SET_NAME: Line shipment set name.
*LINE_ACTUAL_SHIP_DATE_FROM: Beginning actual shipment date of the order line.
*LINE_ACTUAL_SHIP_DATE_TO: Ending actual shipment date of the order line.
*LINE_SCHEDULED_SHIP_DATE_FROM: Beginning scheduled shipment date of the order line.
*LINE_SCHEDULED_SHIP_DATE_TO: Ending scheduled shipment date of the order line.
*LINE_PROMISE_DATE_FROM: Beginning promised shipment date of the order line.
*LINE_PROMISE_DATE_TO: Ending promised shipment date of the order line.
*LINE_REQUEST_DATE_FROM: Beginning requested shipment date of the order line item.
*LINE_REQUEST_DATE_TO: Ending requested shipment date of the order line item.
While configuring the Query Advanced Shipping Notice service, a java.outOfMemory error can occur since the service generation API executes the query against the database. One workaround is to use a restricting condition in the query, that is, rownum = 1, so that the service configures successfully. After you configure this service, remove the restricting condition from your transaction definitions. You must also update the SQLOut parameters of the service’s transactionRecord in Software AG Designer and remove the restricting condition. (In this example, remove the rownum = 1 condition.)
Database Scripts
This service uses the same database scripts as the Send Advanced Shipping Notice service.
Note:
If you use this service but you do not use the Send Advanced Shipping Notice service, you should run the wm_disable_from_shipnotice.sql script to disable the triggers installed by the Send Advanced Shipping Notice service.
For a detailed description of these database scripts, see Send Advance Shipping Notice Service. For more information about using database scripts, see Database Scripts.
Supporting Transaction Definitions
This service uses the following transaction definition:
*queryASNTxn1227.txp
For information about using the transaction definition files to customize this service, see Transaction Definitions.
Flow Control
The main flow executes as follows:
*queryASNTxn queries for any Advanced Shipping Notice information matching the parameter values. The parameters are defined as the input to this service.
For more details on query services, see Using Query Services.
Business Document Structure
This service uses the same business document structure as the Send Advanced Shipping Notice service. For a detailed description of the business document structure, see Send Advance Shipping Notice Service.