Search Results chv_shipping

Overview

ECE_SSSO_HEADERS_V is a private view owned by the APPS schema in Oracle E-Business Suite, defined within the e-Commerce Gateway (EC) product. Its documented purpose is to extract header information for the outbound Shipping Schedule transaction, identified as 862/DELJIT in the ANSI X12 and EDIFACT standards respectively. The view is registered in ETRM with the display name "Shipping Schedule Header View" and is categorized under the business entity CHV_SHIPPING with an active lifecycle status. It serves as the header-level source for the outbound 862 mapping, supplying the trading partner context, document identity, translator configuration, schedule horizon, and supplier/organization references required before line-level Shipping Schedule data is assembled.

Underlying Base Objects

The view is defined over a set of CHV synonyms — CHV_SCHEDULE_HEADERS, CHV_ITEM_ORDERS, CHV_CUM_PERIODS, and CHV_ORG_OPTIONS — together with ECE_TP_HEADERS and ECE_TP_DETAILS, which carry the trading partner and translator configuration. It joins HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL for organization names, HR_LOCATIONS, MTL_PARAMETERS, PO_VENDORS, and PO_VENDOR_SITES for supplier and site context, and calls FND_GLOBAL, HR_GENERAL, and HR_SECURITY for session and security predicates. CHV_SCHEDULE_HEADERS supplies the schedule identity and horizon; ECE_TP_DETAILS supplies the TEST_FLAG and TRANSLATOR_CODE values; ECE_TP_HEADERS supplies the partner description and descriptive flexfield attributes.

Key Columns

• TEST_FLAG — sourced from ECE_TP_DETAILS; the column most directly relevant to the search term. It distinguishes test-mode translator runs from production transmissions for the selected trading partner detail.
• COMMUNICATION_METHOD — NVL of CSH.COMMUNICATION_CODE, defaulting to 'NONE'.
• DOCUMENT_ID / DOCUMENT_TYPE / DOCUMENT_CODE — constants 'SSSO' and 'SSS' plus CSH.SCHEDULE_NUM, identifying the outbound document.
• TP_TRANSLATOR_CODE, TP_LOCATION_CODE_EXT, TP_DESCRIPTION — trading partner and translator identification.
• SCHEDULE_HORIZON_START / SCHEDULE_HORIZON_END — the planning horizon carried on the schedule header.
• SCHEDULE_NUMBER_REVISION — derived as RTRIM(SCHEDULE_NUM) concatenated with SCHEDULE_REVISION (NVL to 0).
• ORGANIZATION_ID, VENDOR_ID, VENDOR_SITE_ID, SCHEDULE_ID, SCHEDULE_TYPE, SCHEDULE_SUBTYPE, SCHEDULE_STATUS — core header identifiers and status flags.
• TPH_ATTRIBUTE1..15 and TPD_ATTRIBUTE1..5 — descriptive flexfield attributes from ECE_TP_HEADERS and ECE_TP_DETAILS.

Common Use Cases and Queries

Because the view surfaces TEST_FLAG from the trading partner details, it is commonly queried when validating whether an 862 Shipping Schedule will be processed in test mode before go-live, and when troubleshooting why an outbound schedule was or was not transmitted. A typical diagnostic query is:

SELECT SCHEDULE_NUMBER_REVISION, DOCUMENT_CODE, TP_DESCRIPTION,
       TP_TRANSLATOR_CODE, TEST_FLAG, COMMUNICATION_METHOD,
       SCHEDULE_STATUS, SCHEDULE_HORIZON_START, SCHEDULE_HORIZON_END
FROM   APPS.ECE_SSSO_HEADERS_V
WHERE  VENDOR_ID = :p_vendor_id
AND    ORGANIZATION_ID = :p_org_id;

To list all partners configured in test mode:

SELECT TP_DESCRIPTION, TP_LOCATION_CODE_EXT, TEST_FLAG
FROM   APPS.ECE_SSSO_HEADERS_V
WHERE  TEST_FLAG = 'Y';

Note that the view is marked private in the repository, so it should be treated as an internal object of the e-Commerce Gateway extraction logic rather than a supported public interface. Querying it directly is appropriate for diagnostics and data validation, while production integrations should use the standard outbound transaction programs that consume this view.