Oracle Cloud: CNPJ, LRU, Location and Inventory Organization in FDC

Registering a CNPJ on the Legal Reporting Unit (LRU) is only one part of Brazilian fiscal setup. The Inventory Organization (IO), its Location Address and the effective legal associations must also be consistent.

How the records relate

Legal Entity
  └── Legal Reporting Unit (LRU)
       ├── CNPJ Registration
       ├── Associated Inventory Organization
       └── Associated Inventory/Ship-to Location
Inventory Organization ─── Location Address
Location ─── Inventory Organization (when applicable)

This diagram is conceptual, not a universal one-to-one rule. Oracle documents the IO-to-LRU association for ship-from and Location-to-LRU association for ship-to in internal transfers.

A simple example: two warehouses

1. Practical example

When Warehouse A transfers goods to Warehouse B, Oracle needs to know:

• Which CNPJ identifies the sender on the fiscal document?
• Which CNPJ identifies the recipient?

What does each record represent?

An IO is not itself a CNPJ, and a Location is not an LRU. They are separate records that must be associated as required by the transaction.

How does Oracle identify sender and receiver?

For internal transfers, the official Oracle 26D documentation defines two separate mappings:

SENDER (Ship-From)
Inventory Organization of Warehouse A
                   |
                   v
            LRU of Branch A
                   |
                   v
                CNPJ A

RECEIVER (Ship-To)
Destination Location of Warehouse B
                   |
                   v
            LRU of Branch B
                   |
                   v
                CNPJ B

• Ship-From: in Manage Associated Business Entities, select the ship-from Legal Entity and LRU, then create an Inventory organization association for the correct IO. For internal transfers and supplier returns, Oracle uses this configuration to default the ship-from LRU on Update Fiscal Attributes.
• Ship-To: for internal transfers, select the destination Legal Entity and LRU, then create a Ship-from or to location association for the destination Location. The ship-to location is captured on Edit Shipment.

In short, Oracle uses the source IO to determine the source LRU and the destination Location to determine the destination LRU for these specific fiscal shipment processes. An individual LRU is not necessarily required for every IO.

How does this affect FDC?

The cited Oracle procedure primarily describes LRU determination during Fiscal Document Generation (FDG). It does not establish that these associations alone guarantee CNPJ selection in Fiscal Document Capture (FDC).

In FDC, open Create Fiscal Document and search Receiver Taxpayer ID for the expected CNPJ. A visible result confirms the taxpayer identifier can be found in that lookup, not that the entire fiscal flow will succeed. If absent, review the registration, effective dates, relevant associations, transaction context and user access.

Setup checklist

1. Verify Legal Entity, LRU and effective dates.
2. In Manage Registrations, confirm Brazilian CNPJ jurisdiction, code, number, identifying registration and validity.
3. In Manage Inventory Organizations, check the entity, status and Location Address.
4. In Manage Locations, check address, status, effective dates and the related Inventory Organization when applicable.
5. In Manage Associated Business Entities, select the Legal Entity/LRU scope and create the association types required by the transaction.
6. Test the FDC lookup and an actual representative document.

Fictional example

SQL 1 — Duplicate CNPJ across LRUs

Finds currently effective registrations shared by different LRUs; LRU status is calculated from effective dates.

WITH base AS (
 SELECT DISTINCT e.establishment_id lru_id, e.name lru_name,
 REGEXP_REPLACE(r.registration_number,'[^0-9]','') cnpj,
 e.effective_from,e.effective_to
 FROM xle_etb_profiles e, xle_registrations r, xle_jurisdictions_b j
 WHERE r.source_table='XLE_ETB_PROFILES'
 AND r.source_id=e.establishment_id
 AND r.jurisdiction_id=j.jurisdiction_id
 AND UPPER(j.registration_code_etb) LIKE '%CNPJ%'
 AND TRUNC(SYSDATE) BETWEEN NVL(TRUNC(r.effective_from),TRUNC(SYSDATE))
 AND NVL(TRUNC(r.effective_to),TRUNC(SYSDATE))
)
SELECT b.cnpj,b.lru_id,b.lru_name,
 CASE WHEN TRUNC(SYSDATE) BETWEEN
 NVL(TRUNC(b.effective_from),TRUNC(SYSDATE))
 AND NVL(TRUNC(b.effective_to),TRUNC(SYSDATE))
 THEN 'ACTIVE' ELSE 'INACTIVE' END lru_status,
 COUNT(*) OVER(PARTITION BY b.cnpj) qtd_lrus
FROM base b
WHERE b.cnpj IN (
 SELECT cnpj FROM base WHERE cnpj IS NOT NULL
 GROUP BY cnpj HAVING COUNT(DISTINCT lru_id)>1
)
ORDER BY b.cnpj,b.lru_name;

SQL 2 — IO and Location associations by LRU

Create an optional text parameter P_CNPJ in BI Publisher. This query lists effective fiscal associations and the Inventory Organization assigned to a Location when applicable.

WITH lru AS (
 SELECT DISTINCT e.establishment_id lru_id,e.name lru_name,
 REGEXP_REPLACE(r.registration_number,'[^0-9]','') cnpj
 FROM xle_etb_profiles e, xle_registrations r, xle_jurisdictions_b j
 WHERE r.source_table='XLE_ETB_PROFILES'
 AND r.source_id=e.establishment_id
 AND r.jurisdiction_id=j.jurisdiction_id
 AND UPPER(j.registration_code_etb) LIKE '%CNPJ%'
 AND TRUNC(SYSDATE) BETWEEN NVL(TRUNC(r.effective_from),TRUNC(SYSDATE))
 AND NVL(TRUNC(r.effective_to),TRUNC(SYSDATE))
)
SELECT l.lru_name,l.cnpj,a.entity_type,a.context,
 a.entity_name,a.entity_id,
 io.organization_code io_code,
 loc.location_code,
 loc.inventory_organization_id location_io_id,
 a.effective_from,a.effective_to
FROM lru l, xle_associations_v a,
 inv_org_parameters io, hr_locations_all_f_vl loc
WHERE a.legal_construct_id=l.lru_id
 AND io.organization_id(+)=CASE WHEN a.entity_type='INVENTORY_ORGANIZATION'
 THEN a.entity_id END
 AND loc.location_id(+)=CASE WHEN a.entity_type IN
 ('INVENTORY_LOCATION','SHIP_TO_LOCATION','BILL_TO_LOCATION')
 THEN a.entity_id END
 AND (loc.location_id IS NULL OR TRUNC(SYSDATE) BETWEEN
 loc.effective_start_date AND loc.effective_end_date)
 AND a.entity_type IN ('INVENTORY_ORGANIZATION','INVENTORY_LOCATION',
 'SHIP_TO_LOCATION','BILL_TO_LOCATION')
 AND TRUNC(SYSDATE) BETWEEN NVL(TRUNC(a.effective_from),TRUNC(SYSDATE))
 AND NVL(TRUNC(a.effective_to),TRUNC(SYSDATE))
 AND (:P_CNPJ IS NULL OR l.cnpj=REGEXP_REPLACE(:P_CNPJ,'[^0-9]',''))
ORDER BY l.cnpj,l.lru_name,a.entity_type,a.entity_name;

LRUs without associations do not appear. The IO’s own Location Address must be checked separately. Association types represent different business purposes.

Functional verification in FDC

Open Fiscal Document Capture → Create Fiscal Document → Receiver Taxpayer ID. Search for the CNPJ and verify the associated legal entity. If it is absent, inspect the registration, dates, location, associations, BU and security. Lookup visibility alone does not guarantee successful XML processing, taxation or accounting.

Important considerations

A duplicate CNPJ across LRUs should be investigated but is not necessarily an error. Consider effective dates, association types and the underlying fiscal transaction before making changes.

Avoid publishing real tax IDs, addresses or production screenshots. Validate changes before touching production.

References

• Oracle — Define Ship-From and Ship-To Legal Reporting Units
• Oracle — XLE_ASSOCIATIONS_V
• Oracle — XLE_REGISTRATIONS
• Oracle — HR_LOCATIONS_ALL_F_VL