Search Results update_attributes

Overview

JL_BR_SPED_PUB is an Oracle E-Business Suite public PL/SQL package owned by the APPS schema, classified as a PUB (public) API. It supports Brazilian localization requirements related to electronic invoicing and fiscal reporting under the SPED (Sistema Público de Escrituração Digital) framework. The package provides a defined interface for maintaining electronic invoice attributes on customer transactions, recording electronic invoice log entries, and resolving IBGE geographic codes associated with a location. Because the package is designated PUB, its procedures are intended for external invocation by other Oracle EBS components, forms, concurrent programs, or customer extensions rather than being restricted to internal use. The header comment indicates the source file is jlspedps.pls, last modified in the 12.1.1 code line, and the package continues to be documented in the ETRM 12.2.2 repository, confirming its relevance across both 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The package exposes three documented procedures:

• UPDATE_ATTRIBUTES — Updates electronic invoice attributes associated with a customer transaction. It records the electronic invoice web address, status, access key, and protocol against the specified customer transaction identifier. This is the procedure most directly associated with the search term "update_attributes," as it is the sole attribute-maintenance routine in the package.
• INSERT_LOG — Inserts an entry into the electronic invoice log for a given customer transaction. It captures the occurrence date, the electronic invoice status, and a message text, providing an audit trail of electronic invoicing events.
• GET_IBGE_CODES — Retrieves the IBGE (Instituto Brasileiro de Geografia e Estatística) codes for a supplied location identifier. It returns the state code, city code, and central bank code associated with that location, which are required for Brazilian fiscal and banking reporting formats.

All three procedures follow a consistent API convention, accepting an API version parameter with a default of 1.0, a commit flag defaulting to FND_API.G_FALSE, and returning standard X_RETURN_STATUS and X_MSG_DATA output parameters for error handling and message propagation.

Tables Accessed

The package reads and writes several tables through APPS synonyms:

• JL_BR_CUSTOMER_TRX_EXTS — Stores the Brazilian localization extension attributes for customer transactions; the primary target of UPDATE_ATTRIBUTES.
• JL_BR_EILOG and JL_BR_EILOG_S — Electronic invoice log table and its sequence, supporting INSERT_LOG.
• RA_CUSTOMER_TRX_ALL — The base receivables transaction table, providing transaction context.
• AR_PAYMENT_SCHEDULES_ALL — Payment schedule data associated with the transaction.
• HZ_LOCATIONS, HZ_GEOGRAPHY_IDENTIFIERS, and HZ_GEO_NAME_REFERENCES — Trading Community Architecture tables used by GET_IBGE_CODES to resolve location-based geographic codes.
• PLITBLM — A standard Oracle EBS error message repository table used for message lookup.

Usage Notes

JL_BR_SPED_PUB is typically invoked from Brazilian localization forms and concurrent programs that manage electronic invoicing for receivables transactions, and it may also be called from custom PL/SQL code extending the Brazilian SPED solution. Callers should supply a valid P_CUSTOMER_TRX_ID and pass FND_API.G_TRUE for the commit flag only when the calling process is prepared to commit the transaction. Because no other documented packages reference JL_BR_SPED_PUB, it functions as a leaf-level public API, and its X_RETURN_STATUS output should always be checked to confirm success before proceeding. The package is documented in both 12.1.1 and 12.2.2, so its interface remains consistent across these releases.