Split Delivery Detail API

Standard API to Split the Delivery detail:



Auto create Delivery

Auto Create a delivery for a Delivery Detail.

Find the delivery detail id from the booked sales order line and pass as a parameter.

Sample script to Auto create deliveries:

Script to verify the script:


Oracle Trading Community Architecture (TCA)

Oracle Trading Community Architecture (TCA)

Oracle Trading Community Architecture (TCA) is a data model that allows you to manage complex information about the parties, or customers, who belong to your commercial community, including organizations, locations, and the network of hierarchical relationships among them using the TCA registry.

TCA registry is the single source of trading community information for Oracle E-Business Suite applications which provide user interfaces, batch data entry functionality, and other features to view, create, and update Registry information.

TCA key entities:

Parties:  Parties are the entities of type person/organization that enter into a business relationship

Party Sites: Addresses of the parties

Customers: Parties with whom you have a selling relationship

Customer Accounts: The business relationships between you and your customers

Customer Account Sites: Address of the party used in the case of customer accounts

Locations: Geo-spatial points, usually defined by an address

Contacts: People who have a contact or employment relationship with an organization or person

Contact Points: Means of contact, for example, phone and e-mail address

Process Flow:

This diagram shows the process flow for managing, searching, creating, and updating customer information.

R12 Trading Community Architecture:

Includes following new trading entities:

  • Bank and Bank Branches
  • Customers
  • Suppliers

TCA-Bank and Bank Branches:

The TCA tables used by Cash Management for modeling Banks and Bank Branches are listed below:

Three key CE tables now as:

    • CE_BANK_ACCOUNTS for bank accounts
    • CE_BANK_ACCT_USES_ALL for account uses by Operating Units & Legal Entities
    • CE_GL_ACCOUNTS_CCID for bank account use accounting data


The word “Customer” is the combination of both the “Party layer” and the “Account layer”.

  • Party layer exists independent of any selling or buying relationship.
  • Customer Account layer exists in the context of a Party and only when a selling      relationship exists.
  • The Party Layer captures intrinsic truths about a person or organization.
  • The Account Layer captures the details describing the Party’s financial relationship with the implementing organization.
  • The Account Layer cannot exist without the Party Layer.


Following are the three new AP tables’ technical details for R12 Supplier in TCA. They have the links to TCA tables which are listed below.


TCA ER-Diagram:



reference: www.docs.oracle.com

Related posts:

Debugging Shipping API’s

Debugging Shipping API’s:

Debugging Shipping API:

In some cases the API’s may not be successful might be because of setup issues or code issues.
In such cases calling the shipping debugger package(WHS_DEBUG_SV) in the wrapper file will result in the creation of a detailed debug log file based on the various debug profiles setup for shipping module  .
The steps given below will show the step by step approach to generate debug log file during the call to Shipping Public API’s.

Add the following lines into the Wrapper file  before making a call to the shipping:

 Sample API Code with Debug ON:


Set the Profiles
OM: Debug Level – set to 5
      INV: Debug Level – set to 10
      WSH: Debug Enabled – set to Yes
      WSH: Debug Level – set to Statement
      WSH: Debug Log Directory – set to a valid writeable directory path

Execute the shipping action via API

Navigate  to the respective directories specified using the profile
“WSH: Debug Log Directory”

Obtain the Debug

Referred from Oracle Metalink.


Ship Confirm using WSH_DELIVERIES_PUB.Delivery_Action

Ship Confirm Delivery using WSH_DELIVERIES_PUB.Delivery_Action

Specific Parameters:

p_action_code(Required) => action to be performed on Delivery

p_delivery_id (Required)  => delivery id on which the action is performed

p_trip_name    =>  Trip identifier for assignment of trip to delivery

p_asg_pickup_loc_code => Stop location code for pickup assignment

p_asg_pickup_dep_date => Stop location departure date for pickup assignment

p_asg_dropoff_loc_code=> Stop location code for dropoff assignment

p_asg_dropoff_dep_date=> Stop location departure date for dropoff assignment

p_sc_action_flag             => Ship Confirm option – S, B, T, A, C. Used p_sc_intransit_flag         => Ship Confirm set in-transit flag.

p_sc_close_trip_flag      => Ship Confirm close trip flag.

p_sc_create_bol_flag     => Ship Confirm create Bill of Lading flag

p_sc_stage_del_flag       => Ship Confirm create delivery for stage quantity flag

p_sc_trip_ship_method  => Ship Confirm trip ship method.

p_wv_override_flag       => Override flag for weight volume calculations.

x_trip_name                   => Name of autocreated trip.

Sample Code to Ship Confirm the Delivery: