Search Results get_max_zip_size

Overview

APPS.PO_COMMUNICATION_PVT is a private PL/SQL package within the Oracle E-Business Suite Purchasing (PO) module. Its principal business function is to assemble, format, and distribute outbound purchasing documents — purchase orders, releases, and related communications — including the generation of XML payloads, email notifications, and fax/print transmissions. The package operates as the communication and document-assembly engine behind Oracle Purchasing's supplier-facing output, and it is classified as a PVT (private) API, meaning it is not intended as a supported public integration interface and may change without notice between releases.

In EBS 12.1.1 and 12.2.2 the object is documented as VALID under the APPS schema, with both a package specification and a package body present. It depends on SYS and STANDARD, and is referenced extensively by other purchasing packages and XML generators.

Key Procedures and Functions

The documented ETRM metadata records 128 procedures and functions. Representative members include:

• NAME — a general-purpose utility member used within the package's internal processing.
• PO_COMMUNICATION_PROFILE — resolves the purchasing communication profile, driving which output medium and settings apply to a document.
• IS_PON_PRINTING_ENABLED — returns whether PO number printing is enabled for the document.
• USER_HAS_ACCESS_TC — validates whether the current user has access under the relevant terms and conditions / trading community context.
• STORE_BLOB — persists binary large object content, typically an assembled XML or attachment payload.
• ZIP_ATTACH — packages attachments into a ZIP archive for transmission.
• SET_ZIP_ERROR_CODE / GET_ZIP_ERROR_CODE — setters and getters for ZIP processing error status.
• GET_MAX_ZIP_SIZE — returns the maximum permitted ZIP size.
• CHECK_FOR_ATTACHMENTS — determines whether a document carries attachments.
• Address and contact getters — GETSHIPCONTNAME, GETSHIPCONTPHONE, GETSHIPCONTEMAIL, GETDELIVERCONTNAME, GETDELIVERCONTPHONE, GETDELIVERCONTEMAIL, GETSHIPCUSTNAME, GETTOWNORCITY, GETSTATEORPROVINCE, and GETPOSTALCODE — extract ship-to and deliver-to contact and address data for document output.

Tables Accessed

The package reads and writes through APPS synonyms. Key tables include:

• FND_ATTACHED_DOCUMENTS, FND_ATTACHED_DOCUMENTS_S, FND_ATTACHMENT_FUNCTIONS, FND_DOCUMENTS, FND_DOCUMENTS_LONG_TEXT, FND_DOCUMENTS_TL, FND_DOCUMENT_CATEGORIES, FND_DOC_CATEGORY_USAGES, and FND_LOBS — the attachment and document management substrate used by STORE_BLOB, ZIP_ATTACH, and CHECK_FOR_ATTACHMENTS.
• FND_PROFILE_OPTION_VALUES — profile option resolution for communication settings.
• FND_LANGUAGES, FND_TERRITORIES_TL — language and territory descriptions for formatted output.
• FND_NEW_MESSAGES — message retrieval.
• FINANCIALS_SYSTEM_PARAMETERS — ledger/system-level defaults.
• HR_ALL_ORGANIZATION_UNITS — organization data for ship-to and deliver-to resolution.

Usage Notes

PO_COMMUNICATION_PVT is invoked indirectly rather than called directly by end users. It is referenced by 18 other packages, notably the XML generation group — PO_HEADERS_XML, PO_LINES_XML, PO_LINE_LOCATIONS_XML, PO_RELEASE_XML, PO_DISTRIBUTION_XML, and their archive counterparts — which produce the XML document payloads. It is also referenced by PO_REQAPPROVAL_INIT1, PO_WF_PO_NOTIFICATION (the workflow notification layer that emails or faxes purchasing documents), PO_HEADERS_CHANGE_PRINT, and PO_XML_UTILS_GRP. Communication is typically triggered when a buyer approves a purchase order or release, when a document is printed, or when a workflow notification is dispatched. Because the package is private, customizations should not call it directly; integrators should rely on the documented public purchasing APIs and let the standard communication workflow invoke this package.