LACLS Fiscal ISV Integrations For Brazil

Oracle Financials Cloud
Latin America Cloud Local Solution

Brazil – ISVs Integrations
Version 24
Dec 2022
DISCLAIMER:
This guide may contain screen shots and output reports to facilitate the user comprehension about the topic.
The content represents a fictitious sample. Any similarity to actual persons, living or dead, or company
names, active or inactive, is purely coincidental and not intended in any manner.
1
TABLE OF CONTENTS
TABLE OF CONTENTS ................................................................................................................................ 2
REVISION HISTORY .................................................................................................................................... 7
OVERVIEW ................................................................................................................................................ 10
BEST PRACTICES ...................................................................................................................................... 11
NT2020.006 .......................................................................................................................................... 11
IMPORTATION / EXPORTATION PROCESS ...................................................................................... 11
IMPORTATION: ................................................................................................................................ 11
EXPORTATION: ................................................................................................................................. 11
ADDRESS OF CUSTOMER OR SUPPLY: ......................................................................................... 12
<NATOP> TAG - SEFAZ ....................................................................................................................... 13
<INFCPL> TAG - SEFAZ ....................................................................................................................... 13
<CEAN> TAG - SEFAZ .......................................................................................................................... 14
<TERM_ID> - FDG EXTRACTOR ......................................................................................................... 14
<DHEMI> AND <DHSAIENT> TAGS - SEFAZ .................................................................................... 17
<IE> AND <IEST> TAGS - SEFAZ ........................................................................................................ 18
<REFNFP> GROUP - SEFAZ ................................................................................................................ 18
MASS PROCESSING ............................................................................................................................. 19
LEGAL MESSAGE CODE ........................................................................................................................... 21
EXPORTATION PROCESS .................................................................................................................... 21
WITHHOLDING TAX TOTAL AMOUNT .............................................................................................. 25
TAXPAYER MESSAGE CODE ................................................................................................................... 28
XML AUTHORIZATION ........................................................................................................................ 28
DEFINE ITEM CATALOG .......................................................................................................................... 31
ITEM CATALOG: LACLS_CAT_CHARGES .......................................................................................... 31
SETUP - ITEM CATALOG: LACLS_CAT_CHARGES ...................................................................... 32
ITEM CATALOG: LACLS_SERVICE_CODE ......................................................................................... 37
SETUP - ITEM CATALOG: LACLS_SERVICE_CODE ...................................................................... 38
ITEM CATALOG: LACLS_NCM_SERVICE_CODE .............................................................................. 41
SETUP - ITEM CATALOG: LACLS_NCM_SERVICE_CODE .......................................................... 42
ITEM CATALOG: LACLS_BR_ITEM_ORIGIN .................................................................................... 47
2
SETUP - ITEM CATALOG: LACLS_BR_ITEM_ORIGIN ................................................................. 49
ITEM CATALOG: LACLS_BR_ITEM_TYPE ......................................................................................... 52
SETUP - ITEM CATALOG: LACLS_BR_ITEM_TYPE ..................................................................... 53
ITEM CATALOG: LACLS_BR_CEST_CODE ........................................................................................ 56
SETUP - ITEM CATALOG: LACLS_BR_CEST_CODE ..................................................................... 56
ITEM CATALOG: LACLS_BR_REINF_SERVICE_CODE ..................................................................... 59
SETUP - ITEM CATALOG: LACLS_BR_REINF_SERVICE_CODE ................................................. 61
ITEM CATALOG: LACLS_BR_FCI_NUMBER ..................................................................................... 65
SETUP - ITEM CATALOG: LACLS_BR_FCI_NUMBER .................................................................. 65
ITEM CATALOG: LACLS_BR_ANVISA_CODE ................................................................................... 68
SETUP - ITEM CATALOG: LACLS_BR_ANVISA_CODE ................................................................ 68
ITEM CATALOG: LACLS_BR_ESP_VEHICLE ..................................................................................... 70
SETUP - ITEM CATALOG: LACLS_BR_ESP_VEHICLE .................................................................. 71
ITEM CATALOG: LACLS_BR_CBARRA ............................................................................................... 74
SETUP - ITEM CATALOG: LACLS_BR_CBARRA ........................................................................... 75
ITEM CATALOG: LACLS_BR_CBARRA_TRIB .................................................................................... 78
SETUP - ITEM CATALOG: LACLS_BR_CBARRA_TRIB ................................................................. 78
ITEM CATALOG: LACLS_BR_NBS_CODE .......................................................................................... 82
SETUP - ITEM CATALOG: LACLS_BR_NBS_CODE ...................................................................... 82
DEFINE TAX TYPE LOOKUP – LACLS CONFIGURATION .................................................................... 86
SETUP LOOKUP FOR ANP CODE - JGBR_FD_FUEL_PRODUCT_CODE ........................................... 88
VALUE SET ................................................................................................................................................. 90
ISV_BRA_SET ........................................................................................................................................ 90
ISVCLS_BRA_INVOICE_TYPES ........................................................................................................... 92
ISVCLS_BRA_INVOICE_TYPES_AR .................................................................................................... 95
LACLS_BR_ISV_TAX_CREDIT_TYPES ................................................................................................ 98
LACLS_BR_YES_NO............................................................................................................................ 101
LACLS_BR_ISV_RPS_CHECKBOX ..................................................................................................... 104
LACLS_BR_CST_VALUE_SET (OBSOLETE) ..................................................................................... 107
FLEXFIELDS CONFIGURATION ............................................................................................................. 108
DFF – RECEIVABLES TRANSACTIONS - HEADER .......................................................................... 108
DFF – RECEIVABLES – BATCH SOURCES ....................................................................................... 125
3
DFF – RECEIVABLES – TRANSACTION TYPES ............................................................................... 131
DFF - PAYABLES INVOICES - HEADER ............................................................................................ 136
DFF - PAYABLES INVOICES - LINES ................................................................................................ 147
DFF - PAYABLES INVOICES INTERFACE - HEADER ...................................................................... 154
DFF - PAYABLES INVOICE INTERFACE - LINES ............................................................................. 163
DFF - ASSET CATEGORY.................................................................................................................... 169
DFF – BOOK CONTROLS ................................................................................................................... 174
DFF – FA LOCATIONS ........................................................................................................................ 179
DFF – FDG – UPDATE FISCAL ATTRIBUTES ................................................................................... 183
MANAGE LOOKUPS ............................................................................................................................... 188
ISVCLS_BRA_INVOICE_TYPES ......................................................................................................... 188
ISVCLS_BRA_INVOICE_TYPES_AR .................................................................................................. 191
LACLS_BR_ISV_ITEM_DEFAULT ...................................................................................................... 193
LACLS_BR_ISV_TAX_CREDIT_TYP ES .............................................................................................. 195
LACLS_BR_YES_NO............................................................................................................................ 197
RELEASE THE REPORTS IN THE CLOUD ENVIRONMENT ................................................................ 199
OBSOLETED REPORTS ....................................................................................................................... 199
RELEASE THE REPORTS..................................................................................................................... 199
BI PUBLISHER REPOSITORY - REPORTS......................................................................................... 201
GENERATING THE REPORTS ................................................................................................................ 214
LACLS_CHARTOFACCOUNTS (CHART OF ACCOUNTS) ............................................................... 215
REPORT PARAMETERS .................................................................................................................. 215
FREQUENTLY ASKED QUESTIONS ............................................................................................... 215
LACLS_EXTRACTAPSPEDDATA_INCREMENTAL (FDC/AP INVOICES EXTRACT DATA) .......... 217
LACLS_EXTRACTARSPEDDATA_INCREMENTAL (AR INVOICES / SHIPMENT EXTRACT DATA)
.............................................................................................................................................................. 219
LACLS_RECEIVABLES3PARTYPROCESSINGSTATUS (AR INVOICES ANALYTIC REPORT) ....... 221
4
LACLS_SPEDINVBLOCOH (INV TRANSACTIONS – SPED BLOCO H) .......................................... 223
LACLS_EXTRACTSPEDASSETDEPRN (SPED BLOCOS F120/F130 AND CIAP BLOCO G) ........ 225
LACLS_EXTRACTTAXES ..................................................................................................................... 229
LACLS_EXTRACTFINANCIALAPPOINTMENT (APONTAMENTO FINANCEIRO) ........................ 231
LACLS_POSEARCH ............................................................................................................................. 233
LACLS_EXTRACTSPEDINVBLOCOK (INV TRANSACTIONS – SPED BLOCO K) .......................... 236
LACLS_BR_TAXAUTHORITYSUPPLIERDETAILSDATA ................................................................... 238
LACLS_EXTRACTTAXWITHHOLDINGDATA .................................................................................... 240
LACLS_EXTRACTARMOD21 .............................................................................................................. 242
LACLS_NFSESUBSTITUTEREPORT ................................................................................................... 244
LACLS_EXTRACTDFFSETUPDETAILS ............................................................................................... 246
5
LACLS_RUNNINGPROCESSES........................................................................................................... 248
LACLS_MANAGEINVOICEMOD21 ................................................................................................... 250
FILES IN UCM ......................................................................................................................................... 252
ROLE CONTENT_ADMINISTRATON_CUSTOM .............................................................................. 252
PAYLOAD EXAMPLES ......................................................................................................................... 255
INTEGRATION NFSE X AP ..................................................................................................................... 257
WS FIELDS MAPPING ........................................................................................................................ 258
REQUEST PAYLOAD EXAMPLE......................................................................................................... 262
CUSTOM: RTV SCENARIO ..................................................................................................................... 264
CMK CUSTOM ..................................................................................................................................... 264
REQUIRED SETUPS ............................................................................................................................ 265
FDG – RTV FISCAL DOCUMENT ISSUING ...................................................................................... 265
6
REVISION HISTORY
This document will continue to evolve as existing sections change and new information is added. All
updates are logged below:
Date Version Notes

01-Oct-2018 1 Document Creation
20-Dec-2018 2 Document Update
20-Mar-2020 3 New Lookup Type and new field in AP_INVOICES Descriptive Flexfield for comply
with F100 Government layout (EFD Contribuições)
30-Mar-2020 4 Update extractors for LACLS ISV
28-Aug-2020 5 1) Review pre-requisites setup – The Brazil Common Setup was removed from
this document.
2) Include LACLS definition for item catalogs setup: Freight, Service Codes and
NCM Codes
3) New setup in Tax Type lookup for identify what tax will be send to third party
in AP Extractor
4) New Lookup Type for comply with F100 Government layout (EFD
Contribuições) for outbound transactions
Review topics: “Value Set”, “FlexFields” and “Manage Common Lookups”
10-Set-2020 6 This document version has:
1) Include LACLS definition for item catalogs setup: Item Origin and Item Type
2) New attribute in AP Flexfield for consider Access Key for fiscal document
inserted in Open Interface using WS
3) Updated Asset Depreciation Extractor
4) New LACLS_ExtractTaxes extractor for display tax setup information
5) New LACLS_ExtractFinancialAppointment extractor to display details about
“fatura” payment – project “NDD-Frete”
1 Included how third party get information dynamically using WS.
16-Oct-2020 7 This document version has:
1) Changed definition of flexfield ISVCLS_BRA_INVOICE_TYPES from header
(ap_invoices) to lines (ap_invoice_lines)
Changed list of values of lookup: ISVCLS_BRA_INVOICE_TYPES to attend table
SPED Table 4.3.7 – Tabela Base de Cálculo do Crédito
1) New lookup for defined default item for goods or services
2) Obsolete LACLS_AP_XMLReport Extractor. Must be used
LACLS_ExtractApSpedData_Incremental Extractor
3) New parameters in LACLS_ExtractApSpedData_Incremental Extractor
New LACLS_PoSearch Extractor
14-Jan-2021 9 This document version has:
1) Include LACLS definition for CEST catalog setup
2) Include LACLS definition for REINF catalog setup
3) Modification attribute name in ISV_INVOICE_TYPE flexfield in lines of
Payables
4) Include Descriptive Flexfield Definition in Payable Open Interface tables
(header and lines)
5) New parameters in Asset Depreciation Extractor
6) Include validation in LE parameter of LACLS_ExtractApSpedData_Incremental
Extractor for considering only Brazil country
7) New LACLS_BR_TaxAuthoritySupplierDetailsData Extractor
7
New LACLS_SpedInvBlocoK Extractor
1) New attribute for identify tax credit type (acquisition or depreciation) in
Asset extractor
Include shipment transactions in AR extractor
19-Mar-2021 11 This document version has:
Include new DFF to attend a NFSe Substitute
16-Apr-2021 12 This document version has:
1) New attribute in AP Invoice Lines for identify if line must be bookkeeping
2) New LACLS_ExtractTaxWithholdingData extractor
3) New parameter “Model” in LACLS_ExtractApSpedData_Incremental
extractor
4) Include Best Practices topic in this document
5) New LACLS_ExtractArMod21 extractor
6) New LACLS_NFSeSubstituteReport report
7) New Parameters in LACLS_ChartOfAccounts extractor
8) Include LACLS definition for LACLS_BR_FCI_NUMBER catalog setup
9) Include LACLS definition for LACLS_BR_ANVISA_CODE catalog setup
10) Include JGBR_FD_FUEL_PRODUCT_CODE lookup setup for ANP Codes
11) New Descriptive Flexfield to comply with “natOp” in FDG
New Descriptive Flexfield to FA_BOOK_CONTROLS level and reference document
of pre-requisition for asset tax recovery
18-Jun-2021 13 This document version has:
1) Implemented Enhancement Requests in
LACLS_ExtractArSpedData_Incremental extractor for comply with recall
scenarios.
2) New group in LACLS_ExtractApSpedData_Incremental extractor for show
Comments in fiscal document.
3) New setup in for INVOICE_TYPE DFF, unifying with LACLS_BR_REMITTANCE .
4) New parameter “CNPJ Num” in LACLS_ExtractSpedAssetDeprn extractor
New parameter “CNPJ Num” and new group for comply with SPED blocks: K230,
K235, K250 and K255 in LACLS_SpedInvBlocoK extractor
16-Jul-2021 14 This document version has:
1) New parameters and fields in LACLS_ExtractTaxWithholdingData extractor
New group in LACLS_ExtractApSpedData_Incremental extractor for show: State,
City and IBGE Code about Ship To information in CTe, when this document entry
by Payables.
30-Jul-2021 15 This document version has:
1) New procedure to define Inbound Service Code
New template for Legal Message Codes in the Exportation Process
31-Aug-2021 16 This document version has:
1) Include DFF setup in FA_LOCATIONS
DFFs in AR transactions for Model 21 was obsoleted.
08-Sep-2021 17 This document version has:
Include LACLS_BR_ISV_RPS_CHECKBOX Value Set setup
17-Sep-2021 18 This document version has:
1) Included Legal Message “LACLS_BR_LEGAL_MSG_WTH_TAX” for comply
with withholding tax total amount
Included new session “<cEAN> tag – SEFAZ” with best practice about filling GTIN
code in ERP Cloud.
1) Include in LACLS_ExtractApSpedData_Incremental extrator:
8
• New parameters: GL_DATE and LRU
• New document type: RETAINAGE TYPE
• New group: Q_ORG_IDNTFS for show IE and IM Organization data
2) Include in LACLS_ExtractArSpedData_Incremental extractor:
• New group: Q_ORG_IDNTFS for show IE and IM Organization data
3) Include in LACLS_BR_TaxAuthoritySupplierDetailsData extractor:
New group: G_TAXPAYERS_IDNTFS
1) Definition about possible setup variations for TERM_ID integration in FDG
extractor
2) Definition of Fiscal Document Issuing Date in FDG extractor for generate
SEFAZ tags: <dhEmi> and <dhSaiEnt> for scenarios: goods and services
3) New LACLS_ExtractDFFSetupDetails extractor
4) Include LACLS definition for LACLS_BR_ESP_VEHICLE catalog setup
5) Include LACLS definition for LACLS_BR_CBARRA and LACLS_BR_CBARRA_TRIB
catalogs setup for comply with NT2020.005 V1.20
6) Definition about message text: LACLS_BR_AUT_XML for store data CNPJ or
CPF of responsible to download SEFAZ XML
7) Definition CNPJ or CPF of rural producer in NF reference
8) Include best practice for Exportation flow: Commercial Unit and Taxable Unit
in Exportation with Drawback and address definition of Foreign
customer/supplier
9) Definition of FIRST_PARTY_IE and FIRST_PARTY_IE_SHIP_TO when Company
has ICMS-ST withholding
10) Include new topic “Files in UCM”, about create custom role for rename or
delete file
11) Include new topic “Integration NFSe x AP”
12) Include new topic about custom “RTV scenario”
14-Apr-2022 21 This document version has:
1) Modify catalog LACLS_BR_ITEM_TYPE, used in SPED Fiscal, include string “-
ItemType” in category code field, because “00” code is used in NCM tag in
issuing fiscal document. LACLS Fiscal extractors (AR, AP, Block K and Model
21) will be modified for ignore strings after “-”. So, no will impact in fiscal
integrations with ISV Third Party.
2) Changing mapping about Customers/Suppliers Address in
Exportation/Importation Process - topic: “Address of Customer or Supply”
3) Included new session “Mass Processing” in topic: Best Practice
4) New LACLS_ManageInvoiceMod21 Report
5) New LACLS_RunningProcesses extractor
23-Sep-22 22 1) Include explanation about Item Origin
2) New parameters and explanation about extractor:
LACLS_ExtractSpedAssetDeprn
3) Update Templates and Data Models folder for extractors used by Fiscal
Partner ISV
4) Include WS ScheduleProcess information for mass processing
03-Nov-22 23 Modify “<TERM_ID> - FDG Extractor” topic, considering withholding taxes in
Model 55 as “net amount” in “parcela/duplicata”
16-Dec-22 24 1) Obsolete Value Set: LACLS_BR_CST_VALUE_SET
2) Update topic: “Custom: RTV Scenario”
3) Include LACLS definition for LACLS_BR_NBS_CODE catalog setup
9
OVERVIEW
This document describes how to configure features that are required to work rightly with Brazilian fiscal
partners that are responsible to be comply with regulations of the tax authorities. This document also
describes how to install, configure and execute extractors created to attend Third-Party Fiscal Solutions
requirements.
Some texts were extracted from Configuring Fiscal Documents for Brazil document as many common
configurations serves both Fiscal Documents for Brazil and tax obligations delivered by fiscal partners.
IMPORTANT:
Brazil Common Setup was removed from this document. Please see document: Recommended
Approach to Setup Oracle ERP Cloud focusing Brazilian Taxes attachment in My Oracle Support -
DocID: Latin America Cloud Local Solution for Brazil (Doc ID 2291252.1) for more details.
10
BEST PRACTICES
This topic contains the best practices for ERP Cloud integration with ISV Third Party, including details about
issuing or entry fiscal document.
NT2020.006
About this NT, we have two new fields in FDG issue fiscal document, as below:
• tpPag: When the NT2020.06 is released in SEFAZ environment, the fixed value “99” in this tag,
will be required filled a description tag too. Therefore, it’s necessary filled <xPag> tag with fixed
value “A determinar”.
NOTE:
In release 21C of FDG, will be released the enhancement that will allow the user to select the
payment type, with all SEFAZ options. The ISV Third Party will must to change the fixed value
for read a new tag in FDG extractor, for filled this tag in SEFAZ XML.
• indIntermed: This tag is not in FDG roadmap. The ISV Third Party must send fixed value “0” in
SEFAZ XML.
IMPORTATION / EXPORTATION PROCESS
IMPORTATION:
Import process must be handled by a Foreign Trade third party, that will be send this
information to Fiscal third party, responsible to generate SEFAZ XML for issuing the fiscal
document. After document SEFAZ approved, the Fiscal third party must send the XML
into UCM for load by FDC process.
EXPORTATION:
For the Exportation process, please, verify “Managing Fiscal Documents for
Miscellaneous Purpose” attachment document in My Oracle Support - DocID:
2335507.1 - Order to Cash for Brazil and “Legal Message Code for Exportation Process”
topic in this document.
11
For this flow, when Company has Drawback information, it’s necessary must have
Foreign Trade third party, that will be send this information to Fiscal third party,
responsible to generate SEFAZ XML for issuing the fiscal document.
Exportation processes allow UOM Code different between Commercial Unit and Taxable
Unit. In this case, if Company has tax calculation in issuing foreign transactions, must
control inventory in Taxable Unit Code. SEFAZ defined a file with Taxable Unit and NCM.
For more details, please verify link:
http://www.nfe.fazenda.gov.br/PORTAl/exibirArquivo.aspx?conteudo=we6y2AfzKCo=
ADDRESS OF CUSTOMER OR SUPPLY:
For importation or exportation processes, the address structure of Customers or

Suppliers must be the correct address, considering the Country structure. This is
necessary, for when communicate with a supplier or customer, the registration in the
ERP Cloud is correct and in the SEFAZ layout, the foreign country code is required,
according to the IBGE table. Only City and State fields must be sent with values:
EXTERIOR and EX.
So, the Fiscal Third-Party must have a derivation when receiving an XML in the FDG, as
follows:
• Exportation → When country in tag <SHIP_TO_PARTY_SITE_COUNTRY> is

different of “BR” or <TRX_FD_TYPE_DETERMINANT> tag equal “EXPORT”, must
be replace the tags, as example bellow:
Tag FDG XML Original Tag FDG XML Derivate Tag SEFAZ
layout
<SHIP_TO_PARTY_SITE_CITY>SAN <SHIP_TO_PARTY_SITE_CITY>EXTERIOR xMun
DIEGO</SHIP_TO_PARTY_SITE_CITY> </SHIP_TO_PARTY_SITE_CITY>
<SHIP_TO_PARTY_SITE_STATE>CA <SHIP_TO_PARTY_SITE_STATE>EX UF
</SHIP_TO_PARTY_SITE_STATE> </SHIP_TO_PARTY_SITE_STATE>
<SHIP_TO_PARTY_SITE_CITY_CODE/> <SHIP_TO_PARTY_SITE_CITY_CODE>9999999 cMun
</SHIP_TO_PARTY_SITE_CITY_CODE>
• Importation → When country in tag <SHIP_TO_PARTY_SITE_COUNTRY> is

different of “BR” and CFOP starting in "3" (consider 4 last positions
in <TRX_BUSINESS_CATEGORY> tag), must be replace the tags, as example
bellow:
12
Tag FDG XML Original Tag FDG XML Derivate Tag SEFAZ
layout
<FIRST_PARTY_CITY>SAN <FIRST_PARTY_CITY>EXTERIOR xMun
DIEGO</FIRST_PARTY_CITY> </FIRST_PARTY_CITY>
<FIRST_PARTY_STATE>CA <FIRST_PARTY_STATE>EX UF
</FIRST_PARTY_STATE> </FIRST_PARTY_STATE>
<FIRST_PARTY_CITY_CODE/> <FIRST_PARTY_CITY_CODE>9999999 cMun
</FIRST_PARTY_CITY_CODE>
<NATOP> TAG - SEFAZ
For specific cases when CFOP description is not enough to comply with <natOp> tag in SEFAZ XML, for
example: CFOP 5949-Outras Saidas, must verify if Fiscal third party solution will attend the project.
Another alternative would be the customization in FDG layout to show DFF attribute
(LACLS_BR_NAT_OP) setup. Details about this setup are in “FlexFields Configuration” topic in this
document.
NOTE:
Customizations in the FDG extractor are the responsibility/maintenance of the project/customer.
<INFCPL> TAG - SEFAZ
Nowadays, FDC capture fiscal document process does not consider tag <infCpl> of XML SEFAZ. In this
moment, if the information is relevant for Business requirement, you most customize the CMK process
to capture this tag.
The AP fiscal extractor is showing the comments information in fiscal document.
NOTE:
Customizations in the CMK processes are the responsibility/maintenance of the project/customer.
13
<CEAN> TAG - SEFAZ
According to NT 2021.003 v 1.00 published by the government the completion of the GTIN field become
mandatory in NF-e when the product marketed has a barcode with GTIN and when they do not have it
have to be filled with the information "SEM GTIN".
The information of GTIN today is already considered in the layout of the FDG through the tag
PRODUCT_GTIN_CODE but in the registration of this code in the ERP Cloud is of a number format of 14
positions so for the products marketed that do not have barcodes with GTIN the user must register the
value "0000000000000000" (14 zeros) for the fiscal partner to make the conversion to "SEM GTIN".
The configuration will result something like this:
<TERM_ID> - FDG EXTRACTOR
Since 21C release, FDG extractor has a tag <TERM_ID> for identify the payment condition used in sales
transaction.
Fiscal Third-Party must recover the details about TERM_ID setup in customer environment for calculate
the schedule amount and schedule date for filled <cobr>.<dup> group in SEFAZ layout.
Table RA_TERMS_LINES store schedule details information, considering the three possibilities for setup,
as:
Scenario 1: In this scenario, is defined the percentage of the value and the days quantity for schedules
generate.
14
Scenario 2: In this scenario, is defined the day of month and the month ahead quantity for schedules
generate.
Scenario 3: In this scenario, is defined the complete date for schedules generate.
15
IMPORTANT: For more details about this setup, please verify Receivables documentation.
For fulfillment SEFAZ layout, Fiscal Third-Party must calculate the schedule amount and schedule date,
as below:
LAYOUT SEFAZ SCENARIO 1 SCENARIO 2 SCENARIO 3

<nDup> SEQUENCE_NUM SEQUENCE_NUM SEQUENCE_NUM
<dVenc> Add the days put in DUE_DAYS Must consider: Must consider the date put in
column, in date informed in 1) day informed in DUE_DATE column
TRX_DATE column DUE_DAY_OF_MONTH column
2) add months quantity put in
DUE_MONTHS_FORWAR column,
in date informed in TRX_DATE
column
<vDup> Apply the percentage entered Apply the percentage entered in Apply the percentage entered in
in the RELATIVE_AMOUNT the RELATIVE_AMOUNT column the RELATIVE_AMOUNT column
column on the total amount of on the total amount of the on the total amount of the
the document – discount – document – discount – document – discount –
withholding taxes (this is withholding taxes (this is optional withholding taxes (this is optional
optional by Company) by Company) by Company)
For generate <vDup> tag, it’s necessary:
1) Subtract discount amount (<TRADING_DISCOUNT> tag).

2) Subtract withholding taxes (<TAX_AMT> tag) calculated in fiscal document (model 55). This is
optional by Company (branch CNPJ) and must be controlled by fiscal partner.
16
IMPORTANT:
• If Company (branch CNPJ) do option by disregard withholding taxes in <vDup> tag, these
taxes value will affect all fiscal documents generate for this CNPJ. Fiscal partner must
consider total amount - withholding taxes.
• If Company (branch CNPJ) do not option by disregard withholding taxes in <vDup> tag
and fiscal document have these taxes calculated, fiscal partner must consider only total
amount.
• When Company (branch CNPJ) do option to disregard withholding taxes, fiscal partner
must consider all withholding taxes calculated in fiscal document for subtract of total
amount.
• For identify if taxes are withholding, these must have Tax Reporting Code:
LACLS_BR_WHT_TYPE in Tax setup with text: WH, for example:
<TAX_REPORTING_CODES>
<REPORTING_TYPE_CODE>LACLS_BR_WHT_TYPE</REPORTING_TYPE_CODE>
<REP_CODE_TAX_RATE_RULE/>
<REP_CODE_APPL_RULE/>
<REP_CODE_FORMULA_RULE/>
<REP_CODE_TAX_RATE/>
<REP_CODE_TAX>WH</REP_CODE_TAX>
<REP_CODE_TAX_STATUS/>
</TAX_REPORTING_CODES>
<DHEMI> AND <DHSAIENT> TAGS - SEFAZ
For generate tags: <dhEmi> and <dhSaiEnt> in SEFAZ layout, Fiscal Third Party must considerer tag
<FISCAL_DOC_DATE> in FDG layout. This tag is populated with date and hour of XML generated by FDG.
Tag <TRX_DATE> refers to transaction date, informed in Shipment or Receivables modules.
For generate service fiscal document, by default must used tag <FISCAL_DOC_DATE> in FDG layout. Some
municipalities allow the generation of fiscal document with a retroactive date. In this case, can be use tag
<TRX_DATE>, because this tag refers to transaction date, informed in Shipment or Receivables modules.
17
<IE> AND <IEST> TAGS - SEFAZ
FDG extractor has FIRST_PARTY_IE tag. This field contain Company IE Registration Number by physical
address when Company is ICMS Contributor.
FDG extractor has FIRST_PARTY_IE_SHIP_TO tag. This field must contain Company IE Registration
Number for other states when fiscal document has ICMS-ST. In this scenario, Company haven’t physical
address, but have an IE Registration Number where issuing fiscal document.
For example: Company has physical address is SP but has another IE Registration Number in RJ. So, when
Company issuing a fiscal document to RJ with ICMS-ST withholding, the fiscal document must have ICMS
and ICMS-ST. In this case, the fiscal party ISV must consider FIRST_PARTY_IE in tag <IE> layout SEFAZ and
FIRST_PARTY_IE_SHIP_TO in tag <IEST> layout SEFAZ, when the fiscal document has ICMS-ST tax
calculated.
In cases where fiscal document haven’t ICMS-ST tax calculated, is not necessary send the
FIRST_PARTY_IE_SHIP_TO in tag <IEST> layout SEFAZ.
<REFNFP> GROUP - SEFAZ
This group in SEFAZ layout has information about NF referenced, model 55.
For use rural producer reference, model 04, it’s necessary inform model 1 or 1A in list of value of
“Reference Model” field, in FDG. The Fiscal Third-Party must do derivation for send model 04 in SEFAZ
layout.
When rural producer reference has CPF, that has length is 11, it’s necessary inform, before CPF number,
the string “CPF”, for example: “CPF12345678901”. In FDG, “Reference Issuer Taxpayer Identifier” field
must have 14 positions. The Fiscal Third-Party must ignore the “CPF” string, send to SEFAZ only
numbers.
In FDG, Fiscal Update Attributes, it’s possible informed data in “Reference Information” as below:
18
MASS PROCESSING
To avoid problems with mass processing in ERP Cloud, considering execution of simultaneous jobs, it is
necessary to control how many jobs are running and the maximum limit allowed in each customer's
environment, before submitting new jobs.
For this, Localizations Team released “LACLS_RunningProcesses” extractor that return job quantity
running in customer's environment.
Each customer has a specific job quantity, available for execution simultaneous. So, it’s necessary
request this information to Oracle CSM responsible by project. It’s important has this quantity as setup,
considering customer and environment: test, hom, prod.
As default, we can define the minimum limit is 5 (it’s need setup too) jobs for submit new jobs, for
example: If customer environment support 50 jobs simultaneous and, the quantity jobs RUNNING
returned in LACLS_RunningProcesses extractor is:
• Less than 45, you can submit new jobs.

• Greater than 45 or equal 45, you need control the submission of new jobs.
19
The time interval for submit LACLS_RunningProcesses extract again, when has need control because get
the maximum simultaneous quantity, can be 1 minute. This time value needs setup because can be
changed by customer requirement.
20
LEGAL MESSAGE CODE
Legal Message Codes are usually defined by user for fill the legal information in the issuing fiscal
document, for example: suspension or exemption about the tax.
These messages are be shown in FDG extractor with “Record Type” tag equal “6”.
EXPORTATION PROCESS
For Direct Exportation Process, when the Company haven’t Trading Partner for issuing the fiscal
document, it’s possible to use the FDG.
So, it’s necessary define a Template of Legal Message Code to fill the specific exportation information, to
comply with the SEFAZ layout (group <exporta>), as below:
Then, for each tag in SEFAZ layout, you must define in FDG template as below:
1) Navigate to Setup and Maintenance
2) In Task icon, search for “Manage Fiscal Attribute Templates for Brazil”
3) Click on “Manage Fiscal Attribute Templates for Brazil” link. It provides the functionality to
create the templates for use in FDG.
4) Click on Create button and enter with the information as the follow:
Create Fiscal Attribute Defaults
Attribute Template LACLS_BR_EXPORTATION
Start Date *filled automatically with actual date
Enabled Y
End Date
21
Header Information
Industry Type
Purchase Contract
Statement of Commitment
5) In “Associated Legal Messages” section, you must create the values as below:
Legal Message Code Legal Message Text
LACLS_BR_UF_SAIDA_PAIS
LACLS_BR_LOC_EXPORTA
LACLS_BR_LOC_DESPACHO
6) Click on “Save and Close” button
In the “Additional Legal Information” UI in FDG, you must to select LACLS_BR_EXPORTATION in List Of
Value (LOV) of “Attribute Template” field.
In “Additional Information” tab, the “Legal Message Code” are be filled automatically and you must put
the information about the fiscal document in “Legal Message Text” field, as below:
22
Table show the mapping between SEFAZ layout tags and the Legal Message Codes in Template:
SEFAZ layout tag Legal Message Code Legal Message Text
UFSaidaPais LACLS_BR_UF_SAIDA_PAIS *fill with information by company,

according SEFAZ layout validation
xLocExporta LACLS_BR_LOC_EXPORTA * fill with information by company,

xLocDespacho LACLS_BR_LOC_DESPACHO * fill with information by company,

In the FDG XML, this information is shown in <FISCAL_DOC_HEADER_DETAILS> group, when

<RECORD_TYPE> field equal 6, as example:
23
IMPORTANT:
In the exportation document, it’s possible have others Legal Message Codes defined by user. In this
case, the Third-Party ISV must do not consider these three Legal Messages Codes
(LACLS_BR_UF_SAIDA_PAIS, LACLS_BR_LOC_EXPORTA and LACLS_BR_LOC_DESPACHO) for fill Legal
Message in SEFAZ layout (group: <infAdic>).
These three Legal Messages Codes (LACLS_BR_UF_SAIDA_PAIS, LACLS_BR_LOC_EXPORTA and

LACLS_BR_LOC_DESPACHO) are specifically for fill the group: <exporta> in the SEFAZ layout
NOTE:
For Indirect Exportation Process there are no fields mapped in the FDG to supply tags of the group:
<detExport> in the SEFAZ layout. In this case, the foreign trade partner is needed to complement this
information.
24
WITHHOLDING TAX TOTAL AMOUNT
It’s necessary to show the total amount for each withholding tax in “Additional Information” section in
DANFE of NFe (model 55) fiscal document, you must setup the legal message for identify it and the fiscal
Third Party must group the withholding tax calculated in fiscal document. Details about this solution are
be in this topic.
Here is an example the withholding tax calculated in fiscal document and what the fiscal Third Party
must be do for validate in SEFAZ:
NFe Number Line Number WHT Tax Code WHT Tax amount (line)
123 1 IR R$100,00
123 1 ISS R$ 50,00
123 1 INSS R$ 70,00
123 2 IR R$200,00
123 2 ISS R$ 80,00
123 2 INSS R$ 150,00
In <infAdic> section of DANFE must appear: “Vl Retenção IR/ISS/INSS: 300,00/130,00/220,00”
This fiscal requirement as based in some Laws or Normative Instruction (IN), for example:
• INSS → 9th paragraph of article 47 of Normative Instruction 971-2009

• PCC → 10th paragraph of article 1th of Normative Instruction 459-2004
• IR → interpretation of the general rules of the Income Tax Regulation
So, you must create the legal message code “LACLS_BR_LEGAL_MSG_WTH_TAX” in transactions for the
fiscal Third Party can do the grouping of withholding tax calculated in fiscal document and concatenated
with this legal message.
It’s recommended create a FDG template as below:
2) In Task icon, search for “Manage Fiscal Attribute Templates for Brazil”
3) Click on “Manage Fiscal Attribute Templates for Brazil” link. It provides the functionality to
create the templates for use in FDG.
25
Create Fiscal Attribute Defaults
Attribute Template LACLS_BR_WHT_TAX
Start Date *filled automatically with actual date
Enabled Y
End Date
Header Information
Industry Type
Purchase Contract
Statement of Commitment
5) In “Associated Legal Messages” section, you must create the values as below:
Legal Message Code Legal Message Text
LACLS_BR_LEGAL_MSG_WTH_TAX Vl Retenção
6) Click on “Save and Close” button
26
In the “Additional Legal Information” UI in FDG, you must to select LACLS_BR_WHT_TAX in List Of Value
(LOV) of “Attribute Template” field.
In “Additional Information” tab, the “Legal Message Code” are be filled automatically, as below:

So, the fiscal Third Party must considerer in FDG XML, the text: “LACLS_BR_LEGAL_MSG_WTH_TAX” in
<HEADER_DETAIL_ATTRIBUTE2> when <RECORD_TYPE> equal 6 in <FISCAL_DOC_HEADER_DETAILS>.
Get text in <HEADER_DETAIL_ATTRIBUTE3> and concatenated with grouping withholding tax calculated
in fiscal document.
For details about configuration withholding taxes, see document: Recommended Approach to Setup
Oracle ERP Cloud focusing Brazilian Taxes attachment in My Oracle Support - DocID: Latin America
Cloud Local Solution for Brazil (Doc ID 2291252.1).
27
TAXPAYER MESSAGE CODE
Taxpayer Message Codes are usually defined by user for fill the additional information in the issuing
fiscal document.
These messages are be shown in FDG extractor with “Record Type” tag equal “7”.
XML AUTHORIZATION
For generate information about CNPJ or CPF that has authorization for access SEFAZ XML, it’s necessary
define a Template of Taxpayer Message Code to fill the specific group in SEFAZ layout (group <autXML>),
as below:
This group allow until 10 CNPJ or CPF numbers. Then, for each number, you must insert a new line and
inform code equal to “LACLS_BR_AUT_XML” in “Sequence” field. CNPJ or CPF number must be informed
in “Information of Taxpayer Interest” field.
In “Additional Taxpayer Information” tab, put the information as example:
28
29
IMPORTANT:
In the fiscal document, it’s possible have others Taxpayer Message Codes defined by user. In this case,
the Third-Party ISV must do not consider these three Taxpayer Messages Code: LACLS_BR_AUT_XML
for fill Taxpayer Message in SEFAZ layout (group: <infAdic>).
This Taxpayer Message Code: LACLS_BR_AUT_XML is specifically for fill the group: <autXML> in the
SEFAZ layout
30
DEFINE ITEM CATALOG
For comply with ISV integration, some item catalogs must be defined. More details about each item
catalog are below.
ITEM CATALOG: LACLS_CAT_CHARGES
This catalog must be created for consider freight amount in issuing of fiscal document.
In FDG manual, has explanation about the creation of catalog and categories for comply with this scenario.
As well, has the setup of freight item as non-shippable. Please see topic 4 in document:
ManagingFiscalDocumentsforSaleShipments.pdf in My Oracle Support – DocID: Order to Cash for Brazil
(Doc ID 2335507.1)
LACLS objective is only defined the names/codes of catalogs and categories for integration with third
party.
In this scenario, for each item line must be a freight, insurance and others amount related, associated by
field: Shipment Set in OM (Order Management), considering new tag: SHIP_SET_NAME in FDG extractor.
For example:
item qtd unit amount shipment set Catalog Category

Item 1 AAA 10 100.00 AAASET
Item 2 BBB 15 200.00 BBBSET
Item 3 FRT1 1 50.00 AAASET LACLS_CAT_CHARGES LACLS_FREIGHT
Item 4 SEG1 1 80.00 AAASET LACLS_CAT_CHARGES LACLS_INSURANCE
Item 5 MISC1 1 70.00 AAASET LACLS_CAT_CHARGES LACLS_OTHERS
Item 6 FRT2 1 60.00 BBBSET LACLS_CAT_CHARGES LACLS_FREIGHT
Third party must:
1) Validate if item shippable has at least one related item non-shippable for the Shipment Set.
2) Validate if item non-shippable has at least one related item shippable for the Shipment Set.
3) Validate if the same Shipment set of the item shippable haven’t relation with another item
shippable.
For both cases above, the integration must be shown an error in FDG.
4) Sum tax basis amount for item shippable and ALL lines of item non-shippable (same “Shipment
Set”). This calculation is applied to all taxes in the fiscal document.
5) Sum tax amount for item shippable and ALL lines of item non-shippable (same “Shipment Set”).
This calculation is applied to all taxes in the fiscal document.
31
IMPORTANT:
1) For freight discounts, already exists a core solution in FDG and isn’t necessary define LACLS
Catalog and Categories for this scenario.
2) The BIP has a limitation about file size.

If the XML generate was bigger than BIP maximum size, the recommendation is to use the
“bursting” resource, for generate several files.
Example in Sales Order:
shipment line Discount Base ICMS IPI Base PIS Base COFINS
item qty amount set amount Amount ICMS Rate Amount Base IPI Rate Amount PIS Rate Amount COFINS Rate Amount
Item
1 AAA 10 100.00 AAASET 1000.00 100.00 900.00 0.10 90.00 900.00 0.12 108.00 900.00 0.03 27.00 900.00 0.02 18.00
Item
2 BBB 15 200.00 BBBSET 3000.00 220.00 2780.00 0.10 278.00 2780.00 0.08 222.40 2780.00 0.03 83.40 2780.00 0.02 55.60
Item
3 FRT1 1 50.00 AAASET 50.00 0.10 5.00 50.00 0.12 6.00 50.00 0.03 1.50 50.00 0.02 1.00
Item
4 SEG1 1 80.00 AAASET 80.00 0.10 8.00 80.00 0.12 9.60 80.00 0.03 2.40 80.00 0.02 1.60
Item
5 MISC1 1 70.00 AAASET 70.00 0.10 7.00 70.00 0.12 8.40 70.00 0.03 2.10 70.00 0.02 1.40
Item
6 FRT1 1 60.00 BBBSET 60.00 0.10 6.00 60.00 0.08 6.00 60.00 0.03 6.00 60.00 0.02 6.00
IMPORTANT: All Tax Rate applied in Shippable Item, must be applied in No-shippable items too.
Example in Invoice:
line Freight Discount Insurance Other Base ICMS IPI PIS Base COFINS
item qty amount amount Amount Amount Amount Amount ICMS Rate Amount Base IPI Rate Amount Base PIS Rate Amount COFINS Rate Amount
Item
1 AAA 10 100.00 1000.00 50.00 100.00 80.00 70.00 1100.00 0.10 110.00 1100.00 0.12 132.00 1100.00 0.03 33.00 1100.00 0.02 22.00
Item
2 BBB 15 200.00 3000.00 60.00 220.00 0.00 0.00 2840.00 0.10 284.00 2840.00 0.08 228.40 2840.00 0.03 89.40 2840.00 0.02 61.60
SETUP - ITEM CATALOG: LACLS_CAT_CHARGES
For to do this setup you must:
1) Navigate to Product Management
2) Navigate to Product Information Management
32
3) Navigate to Task: Manage Catalogs
Create Catalog
Functional Area
* Catalog Name LACLS_CAT_CHARGES
* Catalog Code LACLS_CAT_CHARGES
* Description LACLS Catalog Charges for Freight
* Controlled At Master Level
* Start Date 8/31/20
End Date
Assign items to leaf level Selected

categories only
Allow multiple item category No selected

assignments
Public Selected
33
5) Click on “Save and Continue” button. The screen below is showed.
6) Select the category LACLS_CAT_CHARGES in Category Name and click on “+” for create the
categories: LACLS_FREIGHT, LACLS_INSURANCE and LACLS_OTHERS, as below:
Create Category LACLS_FREIGHT
* Category Name LACLS_FREIGHT
* Category Code LACLS_FREIGHT
* Description LACLS Freight
*Start Date 8/31/20
End Date
Restrict Category to item No selected

assignment only
Create Category LACLS_INSURANCE
* Category Name LACLS_INSURANCE
* Category Code LACLS_INSURANCE
* Description LACLS Insurance
*Start Date 8/31/20
34
End Date

assignment only
Create Category LACLS_OTHERS
* Category Name LACLS_OTHERS
* Category Code LACLS_OTHERS
* Description LACLS Others
*Start Date 8/31/20
End Date

assignment only
7) Click on OK button for create the category
8) Select the category create above and associate the item no-shippable for each category. In
section Details, click for include an item:
35
9) Click on Search Item and select the corresponding item, as below:
10) Click on OK button. The screen below is showed:
11) Click on “Save and Close” button.
12) Repeat steps 7 and 8 for the other categories.
36
ITEM CATALOG: LACLS_SERVICE_CODE
This catalog is used only for generate services fiscal document in ERP Cloud, when FDG is activated. If the
company won’t use the FDG, the catalog can be unique. In other words, all codes can be defined in the
LACLS_NCM_SERVICE_CODE.
It’s necessary create two catalogs, as below:
Catalog Comments
LACLS_SERVICE_CODE Contain services outbound codes (FDG and AR). Details in this topic.
LACLS_NCM_SERVICE_CODE Contain goods for outbound and inbound NCM codes (FDG/AR and
FDC) and services inbound codes (AP). Details in the next topic.
FDG accept only numbers in field “Product Fiscal Classification”. Brazilian Fiscal requirements that
company must have especial characters in the Service Codes. For this reason, it’s recommended to define
a special LACLS Service Code for outbound processes and associated in each item that will be sale in the
ERP Cloud.
For service fiscal document, the field “Product Fiscal Classification” is automatically filled with
“00000000”, refers to NCM information default configured in Task: “Manage Country Default Controls”.
When the fiscal document generated contain the item associated to catalog LACLS_SERVICE_CODE, the
third party must get information about: CNAE, Service List Code, City Taxing Code and Nature of Operation
in field Category Code of Item Catalog. This information must to separate with “|”, for example:
49300201|1104|11.04.01 / 834|1.
City Taxing Code can be sent to third party with special characters (“.”, “/”, “-“, etc.), according City Tax
Authority layout.
In FDG XML file, the catalog LACLS_SERVICE_CODE information is in the group:

OTHER_PROCUCT_CLASSIFICATIONS, that contain the tags CATEGORY_SET_NAME and CATEGORY_CODE,
as below:
For generate goods fiscal document, configure Catalog Item: LACLS_NCM_SERVICE_CODE. Details in the
next topic.
37
SETUP - ITEM CATALOG: LACLS_SERVICE_CODE
Create Catalog
Functional Area
* Catalog Name LACLS_SERVICE_CODE
* Catalog Code LACLS_SERVICE_CODE
* Description LACLS Service Codes
* Controlled At Organization Level
End Date

categories only

assignments
Public Selected
38
6) Select the category LACLS_SERVICE_CODE in Category Name and click on “+” for create the
categories, for example:
Create Category 49300201|1104|11.04.01/834|1
* Category Name 49300201|1104|11.04.01/834|1
* Category Code 49300201|1104|11.04.01/834|1
* Description Prefeitura Sao Paulo
* You can put any description for identify the category
*Start Date 8/31/20
End Date

assignment only
IMPORTANT: Create a new category for each City Taxing Code
39
8) Select the category create above and associate the item for each category. In section Details,
click for include an item:
40
ITEM CATALOG: LACLS_NCM_SERVICE_CODE
This catalog is used for generating goods fiscal document outbound and for capture the goods and services
fiscal document inbound in ERP Cloud, as below:
• Goods Fiscal Document - Outbound:

1) For goods fiscal document, the field “Product Fiscal Classification” is automatically filled with
the NCM configurated in item Catalog.
• Goods and Services Fiscal Document - Inbound:

1) For goods and services fiscal document inbound, the field “Product Fiscal Classification” is
automatically filled with the NCM configurated in item Catalog.
2) For goods fiscal document inbound, FDC use the list of value of field “Product Fiscal
Classification” for capture the NCM in Supplier XML file.
3) When no have service item in fiscal document inbound, you must select a value in the field
“Product Fiscal Classification” manually. The list of value shown in this field, is configurated in
Item Catalog: LACLS_NCM_SERVICE_CODE.
Inbound Process can be define with a Brazilian federal law code (Lei Complementar No.116)
plus pipe ‘|’ the CNAE code it is not relevant for P2P. There is no need to set the service
regional code, only if the company needs it and, in this case, it can be set it.
Check example for Service Code 101 in the table below:
41
LACLS_NCM_SERVICE_CODE
Category Name Category Code Description

|101| |101| 101-Systems analysis and development (Análise e desenvolvimento de
sistemas)
|101|01010121-3| |101|01010121-3| |101|01.01.01.2.1-3|-Barueri Systems analysis and development
(Análise e desenvolvimento de sistemas)
|101|2660| |101|2660| |101|2660|-Sao Paulo Systems analysis and development (Análise e
desenvolvimento de sistemas)
|101|010101| |101|010101| |101|01.01.01|-Rio de Janeiro Systems analysis and development
(Análise e desenvolvimento de sistemas)
Important: If company needs to define inbound for regional service code. It is necessary to
define catalog controlled by Organization Level. Otherwise the catalog can be at Master
Level.
Link of federal service code: http://sped.rfb.gov.br/pagina/show/1601
For Outbound Process you must register the codes comply with Business Requirement, for
example: CNAE, Service List Code, City Taxing Code and Nature of Operation. This information
must to separate with “|”, as: 49300201|1104|11.04.01 / 834|1.
IMPORTANT: The “|” identify the information position at the field structure, as below:
CNAE Before the first “|”
Service List Code Between first and second “|”
City Taxing Code Between second and third “|”
Nature of Operation After the last “|”
If the Business Requirement not use some information in table above (for example: CNAE),
you must configure considering CNAE as null in the field structure. For example:
|1104|11.04.01 / 834|1.
You must configure the Item Catalog: LACLS_NCM_SERVICE_CODE in field “Primary Inventory
Category Set – Section: Fiscal Classification Default” on Task: “Manage Country Default
Controls” for enable the list of value in field “Product Fiscal Classification”.
SETUP - ITEM CATALOG: LACLS_NCM_SERVICE_CODE
42
Create Catalog
Functional Area
* Catalog Name LACLS_NCM_SERVICE_CODE
* Catalog Code LACLS_NCM_SERVICE_CODE
* Description LACLS NCM Service Codes
End Date

categories only

assignments
Public Selected
43
6) After creating the catalog, you must create a category 00000000 (please see the next step – 7).
This category 00000000 is used in service transactions. After creating the category, you must
modify the catalog, informing “Default Category” field as below:
7) Select the category LACLS_NCM_SERVICE_CODE in Category Name and click on “+” for create
the categories, for example:
Create Category 49300201|1104|11.04.01/834|2
* Category Name 49300201|1104|11.04.01/834|2
* Category Code 49300201|1104|11.04.01/834|2
* Description Prefeitura Sao Paulo
*Start Date 8/31/20
End Date

assignment only
44
IMPORTANT: Create a new category for each City Taxing Code
Create Category 85171211
* Category Name 85171211
* Category Code 85171211
* Description AP.RADIOTEL.,PORTÁTIL EX:WALKIE/HANDLE-TALKIE
*Start Date 8/31/20
End Date

assignment only
IMPORTANT: Create a new category for each NCM Code
45
46
ITEM CATALOG: LACLS_BR_ITEM_ORIGIN
This catalog is used for identifying item origin, according to Brazil Government for SPED fiscal obligation,
in issuing fiscal document.
When Company has sales item with different origins, you must have setup one item for each origin. For
example: “item A” can be origin national or imported. Then you must create “item A-National” and “item
A-Imported” and associate the respective origin for them.
For item origin of supplier XML, in FDC entrance, you have two options, as below:
• Option 1: Create an inventory item with supplier item origin (informed in catalog) and use
“Trading Partner Items” in Item setup, for relate supplier item with Company inventory item.
Please, see more details in link: https://docs.oracle.com/en/cloud/saas/supply-chain-
management/22c/fapim/create-and-edit-trading-partner-items.html#s20064203
UI Example:
• Option 2: Use item origin of supplier XML (tag: <imposto>.<ICMS>.<ICMSxx>.<orig>). This option
requires a custom in CMK for capture Supplier XML tag. Details about this custom, please see
topic: Oracle Cloud CMK Setup to optimize Fiscal Document information in DocID: Latin America
Cloud Local Solution for Brazil (Doc ID 2291252.1)
This information is shown in LACLS_ExtractApSpedData_Incremental extractor in:

<G_INVOICES>.<G_LINES>.<G_TAXES>.<FDC_ATTRIBUTE1> tag.
For import fiscal document (CFOP equal 3), item origin of supplier XML is not changed when
imported by Company.
For national fiscal document (CFOP different 3), item origin of supplier XML is not changed when
imported by Company, except for two origins as below:
47
Item origin in Supplier XML Item origin in Company
1 2
(Estrangeira - Importação direta, exceto a indicada no (Estrangeira - Adquirida no mercado interno, exceto a
código 6) indicada no código 7)
6 7
(Estrangeira - Importação direta, sem similar nacional, (Estrangeira - Adquirida no mercado interno, sem similar
constante em lista de Resolução Camex e gás natural) nacional, constante em lista de Resolução Camex e gás
natural)
IMPORTANT: When <FDC_ATTRIBUTE1> tag is filled (only ICMS tax), Fiscal Partner must consider
this tag and ignore item origin catalog information.
Table below shows the valid codes for item origin:
0 0 Nacional, exceto as indicadas nos códigos 3 a 5
1 1 Estrangeira - Importação direta, exceto a indicada no

código 6
2 2 Estrangeira - Adquirida no mercado interno, exceto a

indicada no código 7
3 3 Nacional, mercadoria ou bem com Conteúdo de

Importação superior a 40%
4 4 Nacional, cuja produção tenha sido feita em conformidade

com os processos produtivos básicos de que tratam o
Decreto-Lei nº 288/1967 , e as Leis nºs 8.248/1991,
8.387/1991, 10.176/2001 e 11.484/2007
5 5 Nacional, mercadoria ou bem com Conteúdo de

Importação inferior ou igual a 40%
6 6 Estrangeira - Importação direta, sem similar nacional,

constante em lista de Resolução Camex e gás natural
7 7 Estrangeira - Adquirida no mercado interno, sem similar

nacional, constante em lista de Resolução Camex e gás
natural
8 8 Nacional, mercadoria ou bem com Conteudo de Importacao

superior a 70%
48
SETUP - ITEM CATALOG: LACLS_BR_ITEM_ORIGIN
Create Catalog
Functional Area
* Catalog Name LACLS_BR_ITEM_ORIGIN
* Catalog Code LACLS_BR_ITEM_ORIGIN
* Description LACLS Item Origin
* Start Date 1/1/20
End Date

categories only

assignments
Public Selected
49
6) Select the category LACLS_BR_ITEM_ORIGIN in Category Name and click on “+” for create the
Create Category 0
* Category Name 0
* Category Code 0
* Description Nacional, exceto as indicadas nos códigos 3 a 5
*Start Date 1/1/20
End Date

assignment only
50
51
ITEM CATALOG: LACLS_BR_ITEM_TYPE
This catalog is used for identifying item type, according to Brazil Government for SPED fiscal obligation.
When Company needs to use “00” NCM code in fiscal document issuing, it’s necessary change codes in
this catalog, concatenating “-ItemType” after category code existing. For example: "00-ItemType".
Categories codes in this catalog are no used in fiscal document issuing. It’s used only SPED Fiscal. So, fiscal
extractors LACLS (AR, AP, Block K and Model 21) must be changed for shown the first positions, before
“-” character. Fiscal integration with ISV Third Party no will have impacts with the change in categories
codes of this catalog.
You can’t change categories codes in catalog existent. So, you must inactive the actual catalog, filling End
Date field and change Catalog Code and Name for: LACLS_BR_ITEM_TYPE_OBSOLETE. After this, you must
create a new catalog: LACLS_BR_ITEM_TYPE as below:
Table below shows the valid codes:
00 00 Mercadoria para Revenda

00-ItemType 00-ItemType
01 01 Matéria-Prima
02 02 Embalagem
03 03 Produto em Processo
04 04 Produto Acabado
05 05 Subproduto
06 06 Produto Intermediário
07 07 Material de Uso e Consumo

08 08 Ativo Imobilizado
52
09 09 Serviços
10 10 Outros insumos
99 99 Outras
SETUP - ITEM CATALOG: LACLS_BR_ITEM_TYPE
Create Catalog
Functional Area
* Catalog Name LACLS_BR_ITEM_TYPE
* Catalog Code LACLS_BR_ITEM_TYPE
* Description LACLS Item Type
* Start Date 1/1/20
End Date

categories only
53
assignments
Public Selected
6) Select the category LACLS_BR_ITEM_TYPE in Category Name and click on “+” for create the
Create Category 00
00-ItemType
* Category Name 00
00-ItemType
* Category Code 00
00-ItemType
* Description Mercadoria para Revenda
*Start Date 1/1/20
54
End Date

assignment only
55
ITEM CATALOG: LACLS_BR_CEST_CODE
This catalog is used for identifying CEST codes in operations that have Tributary Substitution.
These codes are defined by Government and you must set upped the codes according Company
requirement.
Table below shows some valid codes:
0900300 0900300 Reatores para lâmpadas ou tubos de descargas
0600605 0600605 Óleo diesel B S10 (mistura obrigatória)
SETUP - ITEM CATALOG: LACLS_BR_CEST_CODE
Create Catalog
Functional Area
* Catalog Name LACLS_BR_CEST_CODE
56
* Catalog Code LACLS_BR_CEST_CODE
* Description LACLS CEST Code
* Start Date 1/1/21
End Date

categories only

assignments
Public Selected
6) Select the category LACLS_BR_CEST_CODE in Category Name and click on “+” for create the
57
* Description Óleo diesel B S10 (mistura obrigatória)
*Start Date 1/1/21
End Date

assignment only
58
ITEM CATALOG: LACLS_BR_REINF_SERVICE_CODE
This catalog is used for identifying REINF service codes (Tabela de Serviços Prestados mediante cessão de
mão de obra/Empreitada).
These codes are defined by Government and you must set upped the codes according Company
requirement.
Table below shows valid codes:
59
100000001 100000001 Limpeza, conservação ou zeladoria
100000002 100000002 Vigilância ou segurança
100000003 100000003 Construção civil
100000004 100000004 Serviços de natureza rural
100000005 100000005 Digitação
100000006 100000006 Preparação de dados para processamento
100000007 100000007 Acabamento
100000008 100000008 Embalagem
100000009 100000009 Acondicionamento
100000010 100000010 Cobrança
100000011 100000011 Coleta ou reciclagem de lixo ou de resíduos
100000012 100000012 Copa
100000013 100000013 Hotelaria
100000014 100000014 Corte ou ligação de serviços públicos
100000015 100000015 Distribuição
100000016 100000016 Treinamento e ensino
100000017 100000017 Entrega de contas e de documentos
100000018 100000018 Ligação de medidores
100000019 100000019 Leitura de medidores
60
100000020 100000020 Manutenção de instalações, de máquinas ou de
equipamentos
100000021 100000021 Montagem
100000022 100000022 Operação de máquinas, de equipamentos e de veículos
100000023 100000023 Operação de pedágio ou de terminal de transporte
100000024 100000024 Operação de transporte de passageiros
100000025 100000025 Portaria, recepção ou ascensorista
100000026 100000026 Recepção, triagem ou movimentação de materiais
100000027 100000027 Promoção de vendas ou de eventos
100000028 100000028 Secretaria e expediente
100000029 100000029 Saúde
100000030 100000030 Telefonia ou telemarketing
100000031 100000031 Trabalho temporário na forma da Lei nº 6.019, de janeiro

de 1974
SETUP - ITEM CATALOG: LACLS_BR_REINF_SERVICE_CODE
61
Create Catalog
Functional Area
* Catalog Name LACLS_BR_REINF_SERVICE_CODE
* Catalog Code LACLS_BR_REINF_SERVICE_CODE
* Description LACLS REINF Service Code
* Start Date 1/1/21
End Date

categories only

assignments
Public Selected
62
6) Select the category LACLS_BR_REINF_SERVICE_CODE in Category Name and click on “+” for
create the categories, for example:
* Description Limpeza, conservação ou zeladoria
*Start Date 1/1/21
End Date

assignment only
63
64
ITEM CATALOG: LACLS_BR_FCI_NUMBER
This catalog is used for identifying FCI Number in products that have this information.
These numbers have 36 characters and are defined by State Government (Secretaria da Fazenda da
Estado).
Table below shows an example:
B01F70AF-10BF-4B1F-848C-65FF57F616FE B01F70AF-10BF-4B1F-848C-65FF57F616FE B01F70AF-10BF-4B1F-848C-65FF57F616FE
SETUP - ITEM CATALOG: LACLS_BR_FCI_NUMBER
Create Catalog
Functional Area
* Catalog Name LACLS_BR_FCI_NUMBER
* Catalog Code LACLS_BR_FCI_NUMBER
* Description FCI number
65
Default Category
* Start Date 1/1/21
End Date

categories only

assignments
Public Selected
6) Select the category LACLS_BR_FCI_NUMBER in Category Name and click on “+” for create the
Create Category B01F70AF-10BF-4B1F-848C-65FF57F616FE
* Category Name B01F70AF-10BF-4B1F-848C-65FF57F616FE
* Category Code B01F70AF-10BF-4B1F-848C-65FF57F616FE
66
* Description B01F70AF-10BF-4B1F-848C-65FF57F616FE
*Start Date 1/1/21
End Date

assignment only
9) Click on Search Item and select the corresponding item
67
ITEM CATALOG: LACLS_BR_ANVISA_CODE
This catalog is used for identifying ANVISA Code, used in medicine products.
These codes have 13 characters and are defined by Government.
1256800410029 1256800410029 500 MG COM CT BL AL PLAS TRANS X 500
SETUP - ITEM CATALOG: LACLS_BR_ANVISA_CODE
Create Catalog
Functional Area
* Catalog Name LACLS_BR_ANVISA_CODE
* Catalog Code LACLS_BR_ANVISA_CODE
* Description ANVISA Codes
Default Category
68
* Start Date 1/1/21
End Date

categories only

assignments
Public Selected
6) Select the category LACLS_BR_ANVISA_CODE in Category Name and click on “+” for create the
* Description 500 MG COM CT BL AL PLAS TRANS X 500
*Start Date 1/1/21
69
End Date

assignment only
ITEM CATALOG: LACLS_BR_ESP_VEHICLE
This catalog is used for identifying Vehicle Specie Code (RENAVAM Table), used in sales of new vehicle.
These codes have 1 character and are defined by Government. In ERP Cloud must be setup “Code-
Description” and Third-Party ISV must use only the first character for send code to Government.
Table below has an example about setup:
70
1-PASSAGEIRO 1-PASSAGEIRO PASSAGEIRO
2-CARGA 2-CARGA CARGA
3-MISTO 3-MISTO MISTO
4-CORRIDA 4-CORRIDA CORRIDA
5-TRACAO 5-TRACAO TRACAO
6-ESPECIAL 6-ESPECIAL ESPECIAL
SETUP - ITEM CATALOG: LACLS_BR_ESP_VEHICLE
Create Catalog
Functional Area
* Catalog Name LACLS_BR_ESP_VEHICLE
* Catalog Code LACLS_BR_ESP_VEHICLE
* Description Vehicle Specie Code (RENAVAM Table)
71
Default Category
* Start Date 1/1/21
End Date

categories only

assignments
Public Selected
6) Select the category LACLS_BR_ESP_VEHICLE in Category Name and click on “+” for create the
Create Category 1-PASSAGEIRO
72
* Category Name 1-PASSAGEIRO
* Category Code 1-PASSAGEIRO
* Description PASSAGEIRO
*Start Date 1/1/21
End Date

assignment only
73
ITEM CATALOG: LACLS_BR_CBARRA
This catalog is used for identifying item barcode for comply with NT2020.005 V1.20 – tag <cBarra> in
SEFAZ layout. Can be filled when Barcode is different to GTIN default. Must have length minimum 3 and
length maximum 30.
74
SETUP - ITEM CATALOG: LACLS_BR_CBARRA
Create Catalog
Functional Area
* Catalog Name LACLS_BR_CBARRA
* Catalog Code LACLS_BR_CBARRA
* Description Barcode different to GTIN default
Default Category
* Start Date 1/1/21
End Date

categories only

assignments
Public Selected
75
6) Select the category LACLS_BR_CBARRA in Category Name and click on “+” for create the
Create Category
* Category Name *fill with barcode item, according SEFAZ layout validation
* Category Code *fill with barcode item, according SEFAZ layout validation
* Description Barcode description
*Start Date 1/1/21
End Date

assignment only
76
77
ITEM CATALOG: LACLS_BR_CBARRA_TRIB
This catalog is used for identifying item barcode of taxable unit for comply with NT2020.005 V1.20 – tag
<cBarraTrib> in SEFAZ layout. Can be filled when Barcode of taxable unit is different to GTIN default. Must
have length minimum 3 and length maximum 30.
SETUP - ITEM CATALOG: LACLS_BR_CBARRA_TRIB
Create Catalog
Functional Area
* Catalog Name LACLS_BR_CBARRA_TRIB
* Catalog Code LACLS_BR_CBARRA_TRIB
* Description Barcode of taxable unit different to GTIN default
78
Default Category
* Start Date 1/1/21
End Date

categories only

assignments
Public Selected
6) Select the category LACLS_BR_CBARRA_TRIB in Category Name and click on “+” for create the
79
Create Category
* Category Name *fill with barcode item, according SEFAZ layout validation
* Category Code *fill with barcode item, according SEFAZ layout validation
* Description Barcode description
*Start Date 1/1/21
End Date

assignment only
80
81
ITEM CATALOG: LACLS_BR_NBS_CODE
This catalog is used for identifying “Brazilian Nomenclature of Services” (NBS), used in service items.
These codes have 9 characters and are defined by Government, as published in:
http://nbs.economia.gov.br/pt.html link.
1.0107.10.00 1.0107.10.00 Serviços de vidraçaria
SETUP - ITEM CATALOG: LACLS_BR_NBS_CODE
Create Catalog
Functional Area
* Catalog Name LACLS_BR_NBS_CODE
* Catalog Code LACLS_BR_NBS_CODE
* Description Nomenclatura Brasileira de Serviços
Default Category
82
* Start Date 1/1/00
End Date

categories only
Allow multiple item category Selected

assignments
Public Selected
6) Select the category LACLS_BR_NBS_CODE in Category Name and click on “+” for create the
Create Category
* Category Name *fill with NBS Code, according Government definitions.
83
* Category Code *fill with NBS Code, according Government definitions.
* Description *fill with NBS Description, according Government definitions.
*Start Date 1/1/00
End Date

assignment only
84
9) Click on Search Item and select the corresponding item:
12) Repeat steps for create the other categories.
85
DEFINE TAX TYPE LOOKUP – LACLS CONFIGURATION
This topic refers to how configure lookup codes (LACLS) in lookup: ZX_TAX_TYPE_CATEGORY for comply
with Brazil taxes.
Lookup: ZX_TAX_TYPE_CATEGORY has lookup codes “core” (filled by seed data). These codes are
initialized by “ORA” and field “tag” is not enabled for edit.
For comply with Brazil taxes, new lookups codes are created in this lookup. For more details see section
“Brazilian Tax Type” in document: Recommended Approach to Setup Oracle ERP Cloud focusing
Brazilian Taxes attachment in My Oracle Support - DocID: Latin America Cloud Local Solution for Brazil
(Doc ID 2291252.1). Please, see column “tag” in table of lookup code to understand the explanation
below.
Integration taxes Payables AP Extractor logic:
1) Not consider report only tax

2) Not consider cost tax
3) If document tax has a “pair” for recuperation tax, the document tax mustn’t consider. Only
recuperation tax will be shown in extractor
The solution definition for comply with the rule above is to use field “tag” of lookup for defined what tax
must be shown in extractor:
Lookup Code Field Tag Comments

– start with
ORA Is null It’s shows if not have the same code in field “tag”, for the lookup code
that starts with “LACLS”
LACLS Is null It’s NOT considered in AP extractor
LACLS LACLS_ISV It’s considered in AP extractor
LACLS Refers to tax It’s must be used for identifying recuperation tax versus document tax.
type “ORA” For example:
Lookup Code: LACLS_PIS_RECUP → Tag: ORA_PIS
In this case, when XML has ORA_PIS tax, but exists tax rule setup for
LACLS_PIS_RECUP, then only LACLS_PIS_RECUP will be consider in AP
Extractor.
For complete the setup, you must:
2) Search for Manage Tax Lookup Codes
86
3) Click on Manage Tax Lookup Codes link. It provides the functionality to create the Tax Lookup
Codes.
4) In Search region area, find for ZX_TAX_TYPE_CATEGORY in Lookup Type field
5) Go to Search Results region area and click on correspondent lookup type
6) Go to “Financial Generic Lookup Type” region area and find “LACLS” in field Lookup Code
7) Find the lookup codes “_RECUP” and filled the tag field with correspondent tax that start with
ORA. For example: Lookup Code = LACLS_ICMS_RECUP – Tag = ORA_ICMS
8) Find the lookup codes for tax that be displayed in AP extractor and filled the tag field with
“LACLS_ISV”. For example: Lookup Code = LACLS_ISS_WT – Tag = LACLS_ISV
87
SETUP LOOKUP FOR ANP CODE - JGBR_FD_FUEL_PRODUCT_CODE
For fuel products, it’s necessary to include ANP Codes in lookup: JGBR_FD_FUEL_PRODUCT_CODE.
After this setup, the codes filled in lookup are available in FDG fiscal attributes for issuing fiscal
document.
For complete the setup, you must:
2) Search for Manage Standard Lookups
3) Click on Manage Standard Lookups link.
4) In Search region area, find for JGBR_FD_FUEL_PRODUCT_CODE in Lookup Type field
5) Go to Search Results region area and click on correspondent lookup type
6) Go to Lookup Codes region area and click on add (+) button for include ANP Codes
Enter the information as example below:
Lookup Codes
Below you can put the information for classify the invoice line eligible for F100 in each field of the
lookup structure, for example:
Lookup Code Enabled Start Date End Date Meaning Description

420105001 Y 01/01/19 420105001 ÓLEO DIESEL A S10
.
7) Click on Save and Close button
88
89
VALUE SET
Value Sets are created for define the field type in Flexfield Descriptive Segment.
ISV_BRA_SET
ISVCLS_BRA_SET is a common Value Set, used in “ISV Additional information” Descriptive Context, for
define the Flexfield segment as CHARACTER (150).
Creating Value Sets:
1. Navigate to Setup and Maintenance
2. Search for Manage Value Sets
3. Click on Manage Value Sets link. It provides the functionality to create the Value Sets.
4. Go to Search Results region area and click on New icon to define the Value Set
5. Enter the information as the follow:
Value Set Code ISVCLS_BRA_SET
Description ISV Value Set for Integration Purposes
Module Receivables
Validation Type Format Only
Value Data Type Character
Definition
* Value Subtype Text
* Maximun Length 150
Minimun Value
Maximun Value
90
Uppercase only
Zero fill
6. Click on Save and Close button
91
ISVCLS_BRA_INVOICE_TYPES
ISVCLS_BRA_INVOICE_TYPES Value Set is filled with values put in ISVCLS_BRA_INVOICE_TYPES Lookup

Common.
Is used for identifying lines of “no fiscal documents” in Oracle Payables, that will be sent to Government
in the EFD obligation: Bloco F100 in inbound transactions.
Value Set Code ISVCLS_BRA_INVOICE_TYPES
Description Invoice Line Types for F100 - Inbound Transactions
Module Payables
Validation Type Table
Security enabled N
Data Security Resource Name
Definition
* FROM Clause FND_LOOKUP_VALUES
Value Attributes Table Alias
Value Column Name MEANING
Description Column Name
92
ID Column Name LOOKUP_CODE
Enabled Flag Column Name
Start Date Column Name
End Date Column Name
WHERE Clause LOOKUP_TYPE= 'ISVCLS_BRA_INVOICE_TYPES' and language =

USERENV('LANG') AND TRUNC(SYSDATE) BETWEEN
START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE)
AND ENABLED_FLAG = 'Y'
ORDER BY Clause LOOKUP_CODE
93
94
ISVCLS_BRA_INVOICE_TYPES_AR
ISVCLS_BRA_INVOICE_TYPES_AR Value Set is filled with values put in ISVCLS_BRA_INVOICE_TYPES_AR

Lookup Common.
Is used for identify “no fiscal documents” in Oracle Receivables that will be sent to Government in the
EFD obligation: Bloco F100 in outbound transactions.
Value Set Code ISVCLS_BRA_INVOICE_TYPES_AR
Description Invoice Types for F100 - Outbound Transactions
Module Receivables
Security enabled N
Definition
* FROM Clause fnd_lookup_values
Value Column Name meaning
95
ID Column Name lookup_code
WHERE Clause lookup_type = 'ISVCLS_BRA_INVOICE_TYPES_AR' AND

language = USERENV('LANG') AND TRUNC(SYSDATE) BETWEEN
START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE,SYSDATE)
ORDER BY Clause meaning
96
97
LACLS_BR_ISV_TAX_CREDIT_TYPES
LACLS_BR_ISV_TAX_CREDIT_TYPES Value Set is filled with values put in

LACLS_BR_ISV_TAX_CREDIT_TYPES Lookup.
Is used for identifying tax credit types of Assets that will be sent to Government in the EFD obligation:
Bloco F120 and F130.
Value Set Code LACLS_BR_ISV_TAX_CREDIT_TYPES
Description Tax Credit Types
Module Assets
Security enabled N
Definition
98
WHERE Clause lookup_type = 'LACLS_BR_ISV_TAX_CREDIT_TYPES' AND

language = USERENV('LANG') AND TRUNC(SYSDATE) BETWEEN
99
100
LACLS_BR_YES_NO
LACLS_BR_YES_NO Value Set is filled with values put in LACLS_BR_YES_NO Lookup.
Is used for identifying with Y/N options in Descriptive Flexfields that needs this information.
Value Set Code LACLS_BR_YES_NO
Description LACLS Yes/No
Module Functional Setup Manager
Security enabled N
Definition
101
WHERE Clause lookup_type = 'LACLS_BR_YES_NO' AND language =

102
103
LACLS_BR_ISV_RPS_CHECKBOX
Creating Value Sets for NFSe Substitute:
3. Click on Manage Value Sets link. It provides the functionality to create the Value Sets
Value Set Code LACLS_BR_ISV_RPS_CHECKBOX
Description ISV Value Set for NFSe Replacement Purposes
Security enabled N
Definition
* FROM Clause FND_LOOKUP_VALUES
Value Column Name LOOKUP_CODE
Value Column Type VARCHAR2
Value Column Length 30
Description Column Name MEANING
104
ID Column Name LOOKUP_CODE
WHERE Clause lookup_type = 'LACLS_BR_YES_NO' AND language =

ORDER BY Clause LOOKUP_CODE
105
106
LACLS_BR_CST_VALUE_SET (OBSOLETE)
Since 22C version of ERP Cloud, was delivered a new value set: ORA_JGBR_FDG_CST_CODES, then this
value set: LACLS_BR_CST_VALUE_SET was obsoleted.
107
FLEXFIELDS CONFIGURATION
Given the dynamic characteristic of some legal information the ISVCLS use the Descriptive Flexfield (DFF)
concepts to configure the tax authority requirements. One highlight point that needs to keep in mind is
that the flexfield name must define according to the LACLS guidelines.
ISVCLS integration with Fiscal Third Party requires setup the following Descriptive Flexfields:
DFF – RECEIVABLES TRANSACTIONS - HEADER
The additional fields in Receivables Transactions must define for follow scenarios:
• Create billing without Fiscal Document Generator (FDG)
• Create Fiscal Document Services Substitute (NFSe-Substituta) with FDG
• Create billing for Fiscal Document Model 21 without using FDG -- This definition was obsoleted
new procedure is described in Latin America Cloud Local Solution for Brazil (Doc ID 2291252.1)
link Oracle Cloud Fiscal Solution Path.
• Create Fiscal Document Services with more than one line services and using FDG
This step will only be requirement if the company has one of scenarios above.
Setting up the Receivables Transactions DFF:
1. Go to Setup and Maintenance
2. Search for Manage Descriptive Flexfields
3. Click on Manage Descriptive Flexfields link
4. On the field Flexfield Code inform RA_CUSTOMER_TRX and press Search button
5. On Search Results area, select the line “Transactions” in column “Name” and Press Edit icon
6. To create a context specific for “ISV Additional Information”, press Manage Contexts button
IMPORTANT: This setup is necessary only one time. After creation, the Context "ISV Additional
Information" will be showing for selection, in moment of new segments creation in Descriptive
Flexfield.
a. On Search Results area press Create icon
108
b. Create a Context entering each information as follow:
Create Context
Display Name ISV Additional Information
Context Code ISVCLS_BRA
API Name IsvAdditionalInformation
*this name will be generated automatically
Description Additional Information for ISVs Integration

purposes
Enabled Yes
c. Click on button Save and Close, for save the context created
d. Click on button Save and Close again, for return to page: “Edit Descriptive Flexfield:
Transactions”
109
7. Creating the segments to store additional information as DFF in Receivables Transaction header:
8. Choose “ISV Additional Information” in Context field.
The following additional field must be define to attend the scenarios:

- Billing without Fiscal Document Generator (FDG)
- Billing for Fiscal Document Model 21 without using FDG: the attribute must be updated by
ISV as value equal to ‘APPROVED”. This definition was obsoleted new procedure is
described in Latin America Cloud Local Solution for Brazil (Doc ID 2291252.1) link Oracle
Cloud Fiscal Solution Path.
Note: More information about update DFF click on the link

https://docs.oracle.com/en/cloud/saas/financials/21a/oeswf/business-object-
services.html#erpobjectdescriptiveflexfieldupdateservice-d16567e35504
Example references can be get from Doc ID 2193597.1 and Doc ID 2610751.1 available at My
Oracle Support
SEQUENCE 10 - “External Processing Status”
Name ISVCLS_STATUS
IMPORTANT:
You must enter the name exactly as above

since that will use to identify this additional
information.
Code ISVCLS_STATUS
API Name isvclsStatus
Description External Process Status
Enabled Yes
110
Data Type Character
Table Column You can choose any column available. For

example: ATTRIBUTE2
Value Set ISVCLS_BRA_SET
Range Type
Required N
Default Type
Prompt External Process Status (Status de

Processamento Externo)
Note: You can inform the Portuguese

description
Display Type Text Box
Display Size 30
Display Height
Ready-only Y
Definition Help Text
Instruction Help Text This field is updated by fiscal partner with fiscal
document status (Este campo é atualizado pelo
parceiro fiscal com o status do documento)

description.
BI Enabled Y
BI Label
111
The following additional field must be defined to attend the scenarios:
- Billing for Fiscal Document Model 21 without using FDG: the attribute must be updated by
ISV with HASCODE created by “LACLS_ExtractArMod21”. This definition was obsoleted new
procedure is described in Latin America Cloud Local Solution for Brazil (Doc ID 2291252.1)
Note: More information about update DFF click on the link

https://docs.oracle.com/en/cloud/saas/financials/21a/oeswf/business-object-
services.html#erpobjectdescriptiveflexfieldupdateservice-d16567e35504
Example references can be get from Doc ID 2193597.1 and Doc ID 2610751.1 available at My
Oracle Support
SEQUENCE 20 - “External Process Descriptive”
Name ISVCLS_DESCRIPTIVE
IMPORTANT:

information.
Code ISVCLS_DESCRIPTIVE
API Name isvclsDescriptive
Description External Process Status Descriptive
Enabled Yes
Data Type Character

example: ATTRIBUTE3
112
Range Type
Required N
Default Type
Prompt External Process Status Descriptive (Descrição

do Status Processo Externo)

description.
Display Size 150
Display Height 3
Ready-only Y
Instruction Help Text This field is updated by fiscal partner with fiscal
document status description (Este campo é
atualizado pelo parceiro fiscal com a descrição
do status do documento)

description.
BI Enabled Y
BI Label
The following additional field must defined to attend the scenarios:

- Billing for Fiscal Document Model 21 without using FDG -- This definition was obsoleted new
procedure is described in Latin America Cloud Local Solution for Brazil (Doc ID 2291252.1)
- Billing Fiscal Document Services with more than one line services and using FDG
113
SEQUENCE 30 - “Access Key or Hash Code”
Name LACLS_ACCESS_KEY_NUMBER
IMPORTANT:

information.
Code LACLS_ACCESS_KEY_NUMBER
API Name laclsAccessKeyNumber
Description Access Key (Applied to Others Processes) or

Hash Code (Applied to Model 21)
Enabled Yes
Data Type Character

example: ATTRIBUTE1
Range Type
Required N
Default Type
Prompt Access Key or Hash Code(Chave de Acesso ou

Código Hash)

description.
114
Display Size 30
Display Height
Ready-only Y
Instruction Help Text This field is updated by fiscal partner with the
fiscal document services access key or hash
code for model 21 (Este campo é atualizado
pelo parceiro fiscal informando a chave da
NFSe ou o Código Hash do Modelo 21)

description.
BI Enabled Y
BI Label

- Billing Fiscal Document Services Substitute (NFSe-Substituta) with FDG
SEQUENCE 40 - “NFSe Substitute Flag”
Name LACLS_BR_ISV_RPS_CHECKBOX
IMPORTANT:

information.
Code LACLS_BR_ISV_RPS_CHECKBOX
API Name laclsBrIsvRpsFlag
115
Description NFSe Substitute
Enabled Yes
Data Type Character

example: ATTRIBUTE4
Value Set LACLS_BR_ISV_RPS_CHECKBOX
Range Type
Required N
Default Type
Prompt NFSe Substitute (NFSe Substituta)

description.
Display Type Check Box
Display Size
Display Height
Ready-only
Checked Value Y
Unchecked Value N
Instruction Help Text Enable this field to start NFSe Substitute

scenario (Ativar este campo para executar o
cenário de NFSe-Substituta)
116
description.
BI Enabled Y
BI Label
Billing Fiscal Document Services Substitute (NFSe-Substituta) with FDG
SEQUENCE 50 - “RPS Number”
Name LACLS_BR_ISV_RPS_NUMBER
IMPORTANT:

information.
Code LACLS_BR_ISV_RPS_NUMBER
API Name laclsBrIsvRpsNumber
Description RPS Number
Enabled Yes
Data Type Character

example: ATTRIBUTE5
117
Range Type
Required N
Default Type
Prompt RPS Number (Número da RPS)

description.
Display Size 15
Display Height
Ready-only
Instruction Help Text Inform the RPS Number that will be

Substituteed (Informe o Número da RPS que
será substituida)

description.
BI Enabled Y
BI Label
118
SEQUENCE 60 - “RPS Series”
Name LACLS_BR_ISV_RPS_SERIES
IMPORTANT:

information.
Code LACLS_BR_ISV_RPS_SERIES
API Name laclsBrIsvRpsSeries
Description RPS Series
Enabled Yes
Data Type Character

example: ATTRIBUTE6
Range Type
Required N
Default Type
Prompt RPS Series (Série da RPS)

description.
119
Display Size 5
Display Height
Ready-only
Instruction Help Text Inform the RPS Series that will Substitute
(Informe a Série da RPS que será substituida)

description.
BI Enabled Y
BI Label
120
SEQUENCE 70 - “RPS Type”
Name LACLS_BR_ISV_RPS_TYPE
IMPORTANT:

information.
Code LACLS_BR_ISV_RPS_TYPE
API Name laclsBrIsvRpsType
Description RPS Type
Enabled Yes
Data Type Character

example: ATTRIBUTE7
Range Type
Required N
Default Type
Prompt RPS Type (Tipo da RPS)

description.
121
Display Size 5
Display Height
Ready-only
Instruction Help Text Inform the RPS Type that will Substitute
(Informe o Tipo da RPS que será substituida)

description.
BI Enabled Y
BI Label
11. When the follow page appears, click on Deploy Flexfield button
122
12. The following page will be displayed. Click on OK button to finish the setup.
Entering the AR Document for the Transactions:
1. Go to Home
2. Access Receivables module
3. Choose Billing functionality
4. In the main transaction page, find or create the Transaction that needs to store theses
information created above in Descriptive Flexfields
5. Choose Show More option
6. Choose Miscellaneous option
7. It will send the navigation to other page where the User can access the Flexfield information.
Click on the Additional Information tab option and choose “ISV Additional Information” in
Context Value.
123
8. Put information in fields of “ISV Additional Information”
124
DFF – RECEIVABLES – BATCH SOURCES
It is necessary create an additional information to identify the Model for Transaction’s Source.
IMPORTANT:
1) Model information is required for the transaction is showed in AR Extractor.
2) Attributes Serie and Subserie was obsolete of ISV Descriptive Flexfield. You must configure core
attribute for inform Serie and Subserie. Details in this topic.
Setting up the Receivables Batch Sources DFF:
4. On the field Flexfield Code inform RA_BATCH_SOURCES and press Search button
5. On Search Results area, select the line “Transaction Source” in column “Name” and Press Edit
icon
Flexfield.
Create Context
125
purposes
Enabled Yes
Transaction Source”
7. Creating the segments to store additional information as DFF in Receivables Batch Source:
SEQUENCE 1 - “Serie” - OBSOLETED
SEQUENCE 2 - “SubSerie” - OBSOLETED
SEQUENCE 3 - “Modelo”
Name ISV_MODEL
IMPORTANT:
126
since it is used to identify this additional
information.
Code ISV_MODEL
API Name isvModel
Description ISV Fiscal Document Model
Enabled Y
Data Type Character

example: ATTRIBUTE3
Range Type
Required N
Default Type
Prompt Modelo
Display Size 10
Display Height
Ready-only
127
Entering the Receivables setup for the Batch Sources:
128
1. Go to Home
2. Access Setup and Maintenance -> Financial -> Customer Billing
3. Choose Manage Transaction Sources Task
4. In the main Batch Source page, find or create the batch source that needs to store theses
information created above in Descriptive Flexfields.
Context Value.
For inform Serie and SubSerie in core attributes, you must be select a batch source that has the field:
Regional Information populated with: Batch Sources for Brazil. Then Serie and Subseries fields will be
appearing.
In this example, the screen shows setup Source: “BR Interest”, but you have filled the information in all
Sources for integrated with third party fiscal:
1. Go to Home
3. Choose Manage Transaction Sources Task
4. In the main Batch Source page, find or create the batch source that needs to store theses
information created above in Descriptive Flexfields core
Click on the Additional Information tab option and choose “Batch Sources for Brazil” in Regional
Information field.
129
6. Put information in fields: “Serie” and “SubSerie”
130
DFF – RECEIVABLES – TRANSACTION TYPES
It is necessary create an additional information to identify in receivables transaction types, the scenarios
below:
• No Fiscal Document - Invoice Type (used for identifying invoice eligible for “Bloco F100 SPED”)
Setting up the Receivables Transaction Types DFF:
4. On the field Flexfield Code inform RA_CUST_TRX_TYPES and press Search button
5. On Search Results area, select the line “Transaction Types” in column “Name” and Press Edit
icon
Flexfield.
WARNING:
Because the “LACLS Informações Bancárias do Brasil” solution, that use Descriptive Flexfield
in this same table, the Context "ISV Additional Information" will be obsoleted.
You need configure ISV_INVOICE_TYPE Descriptive Flexfield in the Context:

LACLS_BR_REMITTANCE
Create Context - OBSOLETED
131

purposes
Enabled Yes
Context: “LACLS Informações Bancárias do Brasil”
Create Context
Display Name LACLS Informações Bancárias do Brasil
Context Code LACLS_BR_REMITTANCE
API Name LaclsBrRemittance
Description LACLS Informações Bancárias do Brasil
Enabled Yes
132
Transaction Types”
7. Creating the segments to store additional information as DFF in Receivables Transaction Types:
SEQUENCE 10 - “Invoice Type”
Name ISV_INVOICE_TYPE
IMPORTANT:

information.
Code ISV_INVOICE_TYPE
API Name LaclsBrRemittance
Context Code LACLS_BR_REMITTANCE
Description Tipo de Nota
Enabled Y
Data Type Character

example: ATTRIBUTE1
Value Set ISVCLS_BRA_INVOICE_TYPES_AR
Range Type
133
Required N
Default Type
Prompt Tipo de nota
Display Type List of Values
Display Size 20
Display Height
Ready-only
Instruction Help Text
BI Enabled Y
BI Label
134
Entering the Receivables setup for the Transaction Types:
1. Go to Home
3. Choose Manage Transaction Types Task
4. In the main Transaction Types page, find or create the transaction type that needs to store
theses information created above in Descriptive Flexfields
Click on the Additional Information tab option and choose “LACLS Informações Bancárias do
Brasil” in Context Value.
6. Put information in fields of “LACLS Informações Bancárias do Brasil”
135
DFF - PAYABLES INVOICES - HEADER
It is necessary create an additional information to identify in payables invoices header (manual entry),
the scenarios below:
• Fiscal Document: Model, Serie, SubSerie and Fiscal Document Key
Fiscal Document Access Key (when fiscal document is entry in AP Open

Interface, the field core “Fiscal Document Access Key” in tab Tax (section
header) is not enable in WS)
Setting up the AP Invoices DFF:
4. On the field Flexfield Code inform AP_INVOICES and press Search button
5. On Search Results area, select the line “Invoices” in column “Name” and Press Edit icon
Flexfield.
Create Context
Description
Enabled Yes
136
Invoices”
7. Creating the segments to store additional information as DFF in AP invoices header:
Name ISV_MODEL
IMPORTANT:

information.
Code ISV_MODEL
API Name IsvModel
Description Model
Enabled Yes
Data Type Character
137
example: ATTRIBUTE1
Range Type
Required N
Default Type
Prompt Modelo
Display Size 2
Display Height
Ready-only
BI Enabled Y
BI Label
138
SEQUENCE 20 - “Serie”
Name ISV_SERIE
IMPORTANT:

information.
Code ISV_SERIE
API Name IsvSerie
Description Serie
Enabled Yes
Data Type Character

example: ATTRIBUTE2
139
Range Type
Required N
Default Type
Prompt Serie
Display Size 10
Display Height
Ready-only
BI Enabled Y
BI Label
140
SEQUENCE 30 - “SubSerie”
Name ISV_SUBSERIE
IMPORTANT:

information.
Code ISV_SUBSERIE
API Name isvSubserie
Description SubSerie
Enabled Yes
Data Type Character

example: ATTRIBUTE3
141
Range Type
Required N
Default Type
Prompt SubSerie
Display Size 40
Display Height
Ready-only
BI Enabled Y
BI Label
142
SEQUENCE 40 - “Invoice Type” - OBSOLETED
This attribute was moved for lines additional information.
SEQUENCE 50 - “Fiscal Document Access Key”
Name ISV_ACCESS_KEY
IMPORTANT:

information.
Code ISV_ACCESS_KEY
API Name isvAccessKey
Description Chave de Acesso do Documento Fiscal
Enabled Yes
143
Data Type Character

example: ATTRIBUTE5
Range Type
Required N
Default Type
Prompt Chave de Acesso
Display Size 44
Display Height
Ready-only
BI Enabled Y
BI Label
144
145
Entering the AP Invoice Document for the Transactions:
1. Go to Home
2. Access Payables module
3. Choose Invoices functionality
4. In the main Invoice page, find or create the Transaction that needs to store theses information
created above in Descriptive Flexfields
5. Choose Show More option
Context Value.
146
DFF - PAYABLES INVOICES - LINES
It is necessary create an additional information to identify in payables invoices lines (manual entry), the
scenarios below:
• No Fiscal Document – Base Table Credit (used for identifying invoice line eligible for “Bloco F100
SPED”)
Setting up the AP Invoices DFF:
4. On the field Flexfield Code inform AP_INVOICE_LINES and press Search button
5. On Search Results area, select the line “Invoices Lines” in column “Name” and Press Edit icon
Flexfield.
Create Context
Description
Enabled Yes
147
Invoices”
7. Creating the segments to store additional information as DFF in AP invoices Lines:
SEQUENCE 10 - “ISV_INVOICE_TYPE” - OBSOLETED
SEQUENCE 20 - “ISV_INVOICE_TYPE_L”
Name ISV_INVOICE_TYPE_L
IMPORTANT:

information.
Code ISV_INVOICE_TYPE_L
API Name isvInvoiceTypeL
148
Description Código de Base de Cálculo do Crédito
Enabled Yes
Data Type Character

example: ATTRIBUTE2
Value Set ISVCLS_BRA_INVOICE_TYPES
Range Type
Required N
Default Type
Prompt Codigos de Base de Calculo de Credito
Display Size 20
Display Height
Ready-only
BI Enabled Y
BI Label
149
SEQUENCE 30 - “LACLS_BR_ESCRITURA_FLAG”
Name LACLS_BR_ESCRITURA_FLAG
IMPORTANT:

information.
Code LACLS_BR_ESCRITURA_FLAG
API Name laclsBrEscrituraFlag
Description Envia para escrituração?
Enabled Yes
Data Type Character

example: ATTRIBUTE3
150
Value Set LACLS_BR_YES_NO
Range Type
Required N
Default Type
Prompt Envia para escrituração?
Display Size 3
Display Height
Ready-only
BI Enabled Y
BI Label
151
Entering the AP Invoice Document for the Lines Transaction:
152
1. Go to Home
2. Access Payables module
3. Choose Invoices functionality
4. In the main Invoice page, find or create the Transaction
5. Go to the last column called “Details” in line that needs information in Descriptive Flexfields
6. Click on icon for fill additional information in line DFF
Context Value.
8. Put information in field of “ISV Additional Information”
153
DFF - PAYABLES INVOICES INTERFACE - HEADER
It is necessary create an additional information in interface table with the same information of AP
header table.
This is required when using WS to insert information in open interface.
Setting up the AP Invoices Interface DFF:
4. On the field Flexfield Code inform AP_INVOICES and press Search button
5. On Search Results area, select the line “Invoices Gateway Header” in column “Name” and Press
Edit icon
Flexfield.
Create Context
Description
Enabled Yes
154
d. Click on button Save and Close again, for return to page: “Edit Descriptive
Flexfield: Invoices Gateway Header”
7. Creating the segments to store additional information as DFF in AP invoices interface header:
IMPORTANT: All attributes informed in “Table Column” field MUST be equal attributes in AP
invoice header flexfield create above.
Name ISV_MODEL
IMPORTANT:

information.
Code ISV_MODEL
API Name IsvModel
Description
Enabled Yes
155
Data Type Character

example: ATTRIBUTE1
Range Type
Required N
Default Type
Prompt Modelo
Display Size 2
Display Height
Ready-only
156
SEQUENCE 20 - “Serie”
Name ISV_SERIE
IMPORTANT:

information.
Code ISV_SERIE
API Name IsvSerie
Description Serie
Enabled Yes
Data Type Character

example: ATTRIBUTE2
Range Type
Required N
Default Type
Prompt Serie
Display Size 10
Display Height
157
Ready-only
SEQUENCE 30 - “SubSerie”
Name ISV_SUBSERIE
IMPORTANT:

information.
Code ISV_SUBSERIE
API Name isvSubserie
Description SubSerie
Enabled Yes
Data Type Character
158
example: ATTRIBUTE3
Range Type
Required N
Default Type
Prompt SubSerie
Display Size 40
Display Height
Ready-only
159
SEQUENCE 40 - “Invoice Type” - OBSOLETED
This attribute was moved for lines additional information.
SEQUENCE 50 - “Fiscal Document Access Key”
Name ISV_ACCESS_KEY
IMPORTANT:

information.
Code ISV_ACCESS_KEY
API Name isvAccessKey
Description Chave de Acesso do Documento Fiscal
Enabled Yes
Data Type Character

example: ATTRIBUTE5
Range Type
Required N
Default Type
Prompt Chave de Acesso
160
Display Size 44
Display Height
Ready-only
161
162
DFF - PAYABLES INVOICE INTERFACE - LINES
It is necessary create an additional information in interface lines table with the same information of AP
line table.
This is required when using WS to insert information in open interface.
Setting up the AP Invoice Lines Interface DFF:
4. On the field Flexfield Code inform AP_INVOICE_LINES and press Search button
5. On Search Results area, select the line “Invoice Gateway Lines” in column “Name” and Press Edit
icon
Flexfield.
Create Context
Description
Enabled Yes
163
Invoice Gateway Lines”
7. Creating the segments to store additional information as DFF in AP invoice Interface Lines:
IMPORTANT: All attributes informed in “Table Column” field MUST be equal attributes in AP
invoice lines flexfield create above.
SEQUENCE 10 - “ISV_INVOICE_TYPE” - OBSOLETED
SEQUENCE 20 - “ISV_INVOICE_TYPE_L”
Name ISV_INVOICE_TYPE_L
IMPORTANT:

information.
Code ISV_INVOICE_TYPE_L
API Name isvInvoiceTypeL
164
Description Código de Base de Cálculo do Crédito
Enabled Yes
Data Type Character

example: ATTRIBUTE2
Value Set ISVCLS_BRA_INVOICE_TYPES
Range Type
Required N
Default Type
Prompt Codigos de Base de Calculo de Credito
Display Size 20
Display Height
Ready-only
BI Enabled Y
BI Label
165
SEQUENCE 30 - “LACLS_BR_ESCRITURA_FLAG”
Name LACLS_BR_ESCRITURA_FLAG
IMPORTANT:

information.
Code LACLS_BR_ESCRITURA_FLAG
API Name laclsBrEscrituraFlag
Description Envia para escrituração?
Enabled Yes
Data Type Character

example: ATTRIBUTE3
166
Value Set LACLS_BR_YES_NO
Range Type
Required N
Default Type
Prompt Envia para escrituração?
Display Size 3
Display Height
Ready-only
167
168
DFF - ASSET CATEGORY
It is necessary create an additional information in Asset Category for identifying tax credit type.
NOTE:
These bellow steps is necessary if you want to define tax recovery for your assets in asset level, so if
you define here value for “Tomada de Crédito” you have to set all of them with specific option or you
can set this value in book level (“DFF – BOOK CONTROLS” topic) and set only the assets that have
some exception, that mean that they are different of default value configured in their book level.
Setting up the Asset Additions DFF:
2. Search for Manage Fixed Assets Descriptive Flexfields
3. Click on Manage Fixed Assets Descriptive Flexfields link
4. On the field Flexfield Code inform FA_ADDITIONS and press Search button
5. On Search Results area, select the line “Asset Category” in column “Name” and Press Edit icon
Flexfield.
Create Context
Context Code LACLS_BR_ISV_CONTEXT
Description
Enabled Yes
169
Asset Category”
7. Creating the segments to store additional information as DFF in Asset Category:
SEQUENCE 10 - “LACLS_BR_ISV_TAX_CREDIT”
Name LACLS_BR_ISV_TAX_CREDIT
IMPORTANT:

information.
Code LACLS_BR_ISV_TAX_CREDIT
API Name laclsBrIsvTaxCredit
Description Tomada de Crédito
170
Enabled Yes
Data Type Character

example: ATTRIBUTE1
Value Set LACLS_BR_ISV_TAX_CREDIT_TYPES
Range Type
Required N
Default Type
Prompt Tomada de Crédito
Display Size 20
Display Height
Ready-only
171
Entering the FA Asset:
172
1. Go to Home
2. Access Fixed Asset module
3. Choose Assets functionality
4. In Tasks menu choose: Update Descriptive Details
5. Find Asset and click on “Change Descriptive Details” button
6. In Descriptive Details section, choose “ISV Additional Information” in Context Value field
7. Fill “Tomada de Credito” field with option in list of values:
173
DFF – BOOK CONTROLS
It is necessary create an additional information in Book Controls for identifying tax credit type.
NOTE:
These bellow steps is necessary if you want to define tax recovery for your assets in book level, so if
you define here value for “Tomada de Crédito” so all of assets under this book will automatic assume
this value as default.
4. On the field Flexfield Code inform FA_BOOK_CONTROLS and press Search button
5. On Search Results area, select the line “Book Controls” in column “Name” and Press Edit icon
Flexfield.
e. On Search Results area press Create icon
f. Create a Context entering each information as follow:
Create Context
Description
Enabled Yes
174
g. Click on button Save and Close, for save the context created
h. Click on button Save and Close again, for return to page: “Edit Descriptive Flexfield:
Asset Category”
7. Creating the segments to store additional information as DFF in Book Controls:
SEQUENCE 10 - “LACLS_BR_ISV_TAX_CREDIT”
Name LACLS_BR_ISV_TAX_CREDIT
IMPORTANT:

information.
Code LACLS_BR_ISV_TAX_CREDIT
API Name laclsBrIsvTaxCredit
Description Tomada de Crédito
175
Enabled Yes
Data Type Character

example: ATTRIBUTE1
Value Set LACLS_BR_ISV_TAX_CREDIT_TYPES
Range Type
Required N
Default Type
Prompt Tomada de Crédito
Display Size 20
Display Height
Ready-only
176
177
Configuring Asset Books:
1. Go to Home
2. Access Offering Fixed Assets
3. Choose Task: Manage Asset Books
4. Search your Asset Book and click in pencil icon to edit it:
5. Select Context Value: ISV Additional Information and them fill “Tomada de Credito” field with
option in list of values:
178
DFF – FA LOCATIONS
It is necessary create an additional information in FA Locations for associate LRU information.
4. On the field Flexfield Code inform FA_LOCATIONS and press Search button
5. On Search Results area, select the line “Locations” in column “Name” and Press Edit icon
6. This table no allow setup using context specific. Please, check docID: Asset Location Descriptive
Flexfield Does Not Display the Context Values in the Manage Asset Location Form (Doc ID
2281604.1) for more details.
7. In “Global Segments” section, click on “+” for include a new DFF code.
SEQUENCE 10 - “LACLS_BR_FA_LOC_LRU”
Name LACLS_BR_FA_LOC_LRU
IMPORTANT:

information.
Code LACLS_BR_FA_LOC_LRU
API Name laclsBrFaLocLru
Flexfield Code FA_LOCATIONS
Description
Enabled Yes
Data Type Character
179
example: ATTRIBUTE1
Value Set ORA_FA_LEGAL_REPORTING_UNITS
Range Type
Required N
Default Type
Prompt LRU
Display Size
Display Height
Ready-only
BI Enabled Y
BI Label
180
Configuring FA Locations:
1. Go to Home
2. Go to Setup and Maintenance → Financials → Fixed Assets
181
3. Access Offering Fixed Assets
4. Choose Task: Manage Assets Locations
5. Search your Asset Asset Locations and fill the “LRU” field in Additional Information section, as
below:
182
DFF – FDG – UPDATE FISCAL ATTRIBUTES
This setup is not required and needs customization in FDG extractor for show the DFF information.
All customizations in FDG extractor is responsibility/maintenance of the project/customer.
DFF attribute: LACLS_BR_NAT_OP must be created when Fiscal third party does not have solution about
scenario explained in topic 2 of this document.
Setting up the FDG Update Fiscal Attributes DFF:
4. On the field Flexfield Code inform JGFsclHdrsAtrbExtDFF and press Search button
5. On Search Results area, select the line “Asset Category” in column “Name” and Press Edit icon
Flexfield.
i. On Search Results area press Create icon
j. Create a Context entering each information as follow:
Create Context
Description
Enabled Yes
183
k. Click on button Save and Close, for save the context created
l. Click on button Save and Close again, for return to page: “Edit Descriptive Flexfield: JG
Fiscal Header Attributes Extensions DFF”
7. Creating the segments to store additional information as DFF in FDG:
SEQUENCE 10 - “LACLS_BR_NAT_OP”
Name LACLS_BR_NAT_OP
IMPORTANT:

information.
Code LACLS_BR_NAT_OP
API Name laclsBrNatOp
Description Natureza da Operação
Enabled Yes
184
Data Type Character

example: ATTRIBUTE1
Range Type
Required N
Default Type
Prompt Natureza da Operação
Display Size 60
Display Height
Ready-only
185
Entering the FDG Fiscal Attributes:
1. Go to Home
2. FGD module, through AR or Shipment functionality
3. In Tasks menu choose: Manage Fiscal Document Generation
4. Find fiscal document with status: Transaction entered
5. Click on “Update Fiscal Attributes” button
6. In header section, choose “ISV Additional Information” in Context Segment field
7. Fill “Natureza da Operação” field with text free – maximum 60 characters, according SEFAZ
layout:
186
187
MANAGE LOOKUPS
ISVCLS_BRA_INVOICE_TYPES
The lookup ISVCLS_BRA_INVOICE_TYPES will store the information for identify invoice eligible for “Bloco
F-100 SPED” in inbound transactions.
ISVCLS_BRA_INVOICE_TYPES must be filled with values to identify lines of “no fiscal documents” in
Oracle Payables that will be sent to Government in the EFD obligation: Bloco F100. List of valid values is
based on Sped Table 4.3.7 (Tabela Base de Cálculo do Crédito).
It’s requires the following setup for common setups:
Creating Lookup:
2. Search for Define Lookups
3. Click on Define Lookups link
4. Click on Manage Common Lookups link. It provides the functionality to create the Lookups.
5. Go to Search Results region area and click on New icon to define the lookup
Lookup
Lookup Type ISVCLS_BRA_INVOICE_TYPES

Meaning Invoice Line Types for F100 - Inbound
Transactions
Description Invoice LineTypes for F100 - Inbound
Transactions
Module Payables
Lookup Configuration Level User
REST Access Secured Secure
7. Click on Save button
Lookup Codes
188
Below you can put the information for classify the invoice line eligible for F100 in each field of the
Lookup Enabled Start Date End Date Meaning / Description

Code
01 Y 01/01/19 Aquisição de bens para revenda
02 Y 01/01/19 Aquisição de bens utilizados como insumo
03 Y 01/01/19 Aquisição de serviços utilizados como insumo
04 Y 01/01/19 Energia elétrica e térmica, inclusive sob a forma de
vapor
05 Y 01/01/19 Aluguéis de prédios
06 Y 01/01/19 Aluguéis de máquinas e equipamentos
07 Y 01/01/19 Armazenagem de mercadoria e frete na operação
de venda
08 Y 01/01/19 Contraprestações de arrendamento mercantil
09 Y 01/01/19 Máquinas, equipamentos e outros bens
incorporados ao ativo imobilizado (crédito sobre
encargos de depreciação).
10 Y 01/01/19 Máquinas, equipamentos e outros bens
incorporados ao ativo imobilizado (crédito com
base no valor de aquisição).
11 Y 01/01/19 Amortização e Depreciação de edificações e
benfeitorias em imóveis
12 Y 01/01/19 Devolução de Vendas Sujeitas à Incidência Não-
Cumulativa
13 Y 01/01/19 Outras Operações com Direito a Crédito (inclusive
os créditos presumidos sobre receitas)
14 Y 01/01/19 Atividade de Transporte de Cargas –
Subcontratação
15 Y 01/01/19 Atividade Imobiliária – Custo Incorrido de Unidade
Imobiliária
16 Y 01/01/19 Atividade Imobiliária – Custo Orçado de unidade
não concluída
17 Y 01/01/19 Atividade de Prestação de Serviços de Limpeza,
Conservação e Manutenção – vale-transporte,
vale-refeição ou vale-alimentação, fardamento ou
uniforme.
18 Y 01/01/19 Estoque de abertura de bens
.
The configuration will result in something like this:
189
190
ISVCLS_BRA_INVOICE_TYPES_AR
The lookup ISVCLS_BRA_INVOICE_TYPES_AR will store the information for identify invoice eligible for
“Bloco F-100 SPED” for outbound transactions.
ISVCLS_BRA_INVOICE_TYPES_AR must be filled with values to identify “no fiscal documents” in Oracle
Receivables, that will be sent to Government in the EFD obligation: Bloco F100. No have a list of valid
values of Government.
Creating Lookup:
4. Click on Manage Common Lookups link. It provides the functionality to create the Lookups.
Lookup
Lookup Type ISVCLS_BRA_INVOICE_TYPES_AR

Meaning Invoice Types for F100 - Outbound Transactions
Description Invoice Types for F100 - Outbound Transactions
Module Receivables
Lookup Codes
Below you can put the information for classify the invoice eligible for F100 in each field of the
Lookup Enabled Start End Meaning / Description

Code Date Date
01 Y 01/01/19 Locação de Espaço
191
02 Y 01/01/19 Patrocínio
.
192
LACLS_BR_ISV_ITEM_DEFAULT
The lookup LACLS_BR_ISV_ITEM_DEFAULT will store the information for identify item default in inbound
transaction in AP (Oracle Payables), when this transaction doesn’t have PO or inventory item informed.
For some ISV Third Party, is required item information for integration. Then, you must create the
inventory item for goods and another item for services. These inventory items created, must be
informed in “Tag” field of this lookup, considering the “Code” field equal GOODS or SERVICE.
IMPORTANT: This lookup must be only one code activated for GOODS and SERVICE.
When transaction doesn’t have PO or inventory item informed, the AP Extractor will be to consider the
“Product Type” informed in line of AP transaction and, according this value, will be find the item default
in “Tag” field, considering “Code” field: GOODS or SERVICE.
Creating Lookup:
4. Click on Manage Standard Lookups link. It provides the functionality to create the Lookups.
Lookup
Lookup Type LACLS_BR_ISV_ITEM_DEFAULT

Meaning LACLS_BR_ISV_ITEM_DEFAULT
Description ISV Item Default
193
Lookup Codes
Below you can put the information for classify the item default for GOODS or SERVICES, based in
“Product Type” of line AP transactions, for example:
Lookup Enabled Start End Meaning Description Tag

Code Date Date
GOODS Y 01/01/19 GOODS Default Item for You must fill with Item default
goods code, created in Oracle
Inventory, for example:
ISV_DEFAULT_GOODS
SERVICES Y 01/01/19 SERVICES Default Item for You must fill with Item default
services code, created in Oracle
Inventory, for example:
ISV_DEFAULT_SERV
.
Below you can see the example about the item default created in Oracle Inventory:
Product Management → Product Information Management
194
LACLS_BR_ISV_TAX_CREDIT_TYPES
The lookup LACLS_BR_ISV_TAX_CREDIT_TYPE is used for identifying tax credit type of Asset Category.
This information is considering for select assets to send to Government in Bloco F120 and F130 SPED
obligations.
Creating Lookup:
Lookup
Lookup Type LACLS_BR_ISV_TAX_CREDIT_TYPES

Meaning LACLS_BR_ISV_TAX_CREDIT_TYPES
Description ISV Tax Credit Types
Lookup Codes
You must put the information for identifying tax credit type for Asset Category, as below:

Code Date Date
AQUISITI Y 01/01/19 Acquisition Acquisition
ON
DEPRECI Y 01/01/19 Depreciation Depreciation

ATION
.
195
196
LACLS_BR_YES_NO
The lookup LACLS_BR_YES_NO has Y/N option for use in Descriptive Flexfields that needs this
information.
Creating Lookup:
Lookup
Lookup Type LACLS_BR_YES_NO

Meaning LACLS_BR_YES_NO
Description LACLS Yes/No
Lookup Codes
You must put the information for identifying tax credit type for Asset Category, as below:

Code Date Date
Y Y 01/01/19 Yes Yes
N Y 01/01/19 No No
.
197
198
RELEASE THE REPORTS IN THE CLOUD ENVIRONMENT
LACLS for Brazil provides a set of files that allows Customers to send data to Fiscal Partners called by ISV
(Independent Solution Vendor) for them can generate some tax authority reports. The Solution contains
Reports and the Data Models file types that are released for the solution.
Customers that are installing the LACLS for Brazil must do download of latest patch for Brazil. Please
verify MOS Note: Latin America Cloud Local Solutions (LACLS) - How to Get Latest Pack (Doc ID
2588752.1). For the documentation about required setups, please verify MOS Note: Latin America
Cloud Local Solution for Brazil (Doc ID 2291252.1).
OBSOLETED REPORTS
Reports Display Name File Name
CLL_BrazilianChartOfAccounts CLL_BrazilianChartOfAccounts.xdoz
CLL_BrazilianExtracApSpedContributionsData CLL_BrazilianExtracApSpedContributionsData.xdoz
CLL_BrazilianExtracArSpedContributionsData CLL_BrazilianExtracArSpedContributionsData.xdoz
LACLS_AP_XMLReport LACLS_AP_XMLReport.xdoz
RELEASE THE REPORTS
Reports with XML output (extractors) must be use by Fiscal Partner ISV for generate Government Fiscal
obligation.
These extractors must be deployed under the folders:
Template: Shared Folders→Custom→Local Solution→BR→Fiscal Integrations→Process
Data Model: Shared Folders→Custom→Local Solution→BR→Fiscal Integrations→Process→Data Models
Some reports can be use by user. These have information in UI (as graph and table), no generating XML
as output.
These reports must be deployed under the folders:
Template: Shared Folders → Custom → Local Solution → BR → Fiscal Integrations
Data Model: Shared Folders → Custom → Local Solution → BR → Fiscal Integrations → Data Models
199
Table below shown Report details:
XML Reports Display Name File Name (Template) File Name (Data Model)
Output
YES LACLS_ChartOfAccounts LACLS_ChartOfAccounts.xdoz LACLS_ChartOfAccountsDm.xdmz
YES LACLS_ExtractApSpedData_Incremental LACLS_ExtractApSpedData_Incremental.xdoz LACLS_ExtractApSpedDataDm_Incremental.xdmz
YES LACLS_ExtractArSpedData_Incremental LACLS_ExtractArSpedData_Incremental.xdoz LACLS_ExtractArSpedDataDm_Incremental.xdmz
NO LACLS_Receivables3PartyProcessingStatus LACLS_Receivables3PartyProcessingStatus.xdoz LACLS_Receivables3PartyProcessingStatusDm.xdmz
YES LACLS_SpedInvBlocoH LACLS_SpedInvBlocoH.xdoz LACLS_ExtractSpedInvBlocoHDm.xdmz
YES LACLS_ExtractSpedAssetDeprn LACLS_ExtractSpedAssetDeprn.xdoz LACLS_ExtractSpedAssetDeprnDm.xdmz
YES LACLS_ExtractTaxes LACLS_ExtractTaxes.xdoz LACLS_ExtractTaxesDm.xdoz
YES LACLS_ExtractFinancialAppointment LACLS_ExtractFinancialAppointment.xdoz LACLS_ExtractFinancialAppointmentDm.xdmz
YES LACLS_PoSearch LACLS_PoSearch.xdoz LACLS_PoSearch.xdmz
YES LACLS_ExtractSpedInvBlocoK LACLS_ExtractSpedInvBlocoK.xdoz LACLS_ExtractSpedInvBlocoKDm.xdmz
YES LACLS_BR_TaxAuthoritySupplierDetailsData LACLS_BR_TaxAuthoritySupplierDetailsData.xdoz LACLS_BR_TaxAuthoritySupplierDetailsDm.xdmz
YES LACLS_ExtractTaxWithholdingData LACLS_ExtractTaxWithholdingData.xdoz LACLS_ExtractTaxWithholdingDataDm.xdmz
YES LACLS_ExtractArMod21 LACLS_ExtractArMod21.xdoz LACLS_ExtractArMod21Dm.xdmz
NO LACLS_ManageInvoiceMod21 LACLS_ManageInvoiceMod21.xdoz LACLS_ManageInvoiceMod21Dm.xdmz
NO LACLS_NFSeSubstituteReport LACLS_NFSeSubstituteReport.xdoz LACLS_NFSeSubstituteReportDm.xdmz
YES LACLS_ExtractDFFSetupDetails LACLS_ExtractDFFSetupDetails.xdoz LACLS_ExtractDFFSetupDetailsDm.xdmz
YES LACLS_RunningProcesses LACLS_RunningProcesses.xdoz LACLS_RunningProcessesDm.xdmz
200
BI PUBLISHER REPOSITORY - REPORTS
Considering that Customer is already a User of the BIP tool, below will be described the steps required
to deploy the reports in the BIP folders.
1. Access BI Publisher Enterprise Tool (including /xmlpserver after url used to access the Cloud
environment).
A similar page will be displayed:
2. Click on Catalog option in Menu
3. Click on Expand Shared Folders option
201
4. Click on Expand Custom option
5. If is your first setup, you must create a new folder called “Local Solution”. If the folder already
exists, click on Expand Local Solution option (next step).
For create a new folder “Local Solution”, you must click on “+” and “Folder” option
Put the text “Local Solution” in Folder Name field and click on “Create” button
202
6. Click on Expand Local Solution option
7. If is your first setup, you must create a new folder called “BR”. If the folder already exists, click
on Expand BR option (next step).
For create a new folder “BR”, you must click on “+” and “Folder” option
Put the text “BR” in Folder Name field and click on “Create” button
203
8. Click on Expand BR option
9. If is your first setup, you must create a new folder called “Fiscal Integrations”. If the folder
already exists, click on Expand Fiscal Integrations option (next step).
For create a new folder “Fiscal Integrations”, you must click on “+” and “Folder” option
204
Put the text “Fiscal Integrations” in Folder Name field and click on “Create” button
10. Click on Expand Fiscal Integrations option
IMPORTANT:
1) For reports used by Fiscal Partner ISV, you must create a “Process” folder under
“Fiscal Integrations” folder.
2) In this folder “Fiscal Integrations” or “Fiscal Integrations → Process” must be

imported all files with extension equal “.xdoz” released in patch. More details in step
18 in this topic.
3) Under “Fiscal Integrations → Process” folders you must deploy reports with XML
output. Please, see table with reports details in begin of this topic.
11. If is your first setup, you must create a new folder called “Data Models”. If the folder already
exists, click on Expand Data Models option (next step).
205
For create a new folder “Data Models”, you must click on “+” and “Folder” option
Put the text “Data Models” in Folder Name field and click on “Create” button
12. Click on Expand Data Models option
206
IMPORTANT:
1) For data models used by Fiscal Partner ISV, you must create a “Process” folder under
“Fiscal Integrations” folder.
2) In this folder “Fiscal Integrations → Data Models” or “Fiscal Integrations → Process →

Data Models” must be imported all files with extension equal “.xdmz” released in
patch. More details in step 14 in this topic.
3) Under “Fiscal Integrations → Process → Data Models” folders you must deploy reports
with XML output. Please, see table with reports details in begin of this topic.
13. After download and unzip the patch, you must do upload the artefacts in Oracle Cloud, using
folders created above, considering information:
XML
Folder in patch Folder in Oracle Cloud
Output
YES “patch_number”/BR/FISCAL_INTEG/CA/BI/Process/dat /Shared Folders/Custom/Local Solution/BR/Fiscal

amodel Integrations/Process/Data Models
YES “patch_number”/BR/FISCAL_INTEG/CA/BI/Process/te /Shared Folders/Custom/Local Solution/BR/Fiscal

mplate Integrations/Process
NO “patch_number”/BR/FISCAL_INTEG/CA/BI/datamodel /Shared Folders/Custom/Local Solution/BR/Fiscal

Integrations/Data Models
NO “patch_number”/BR/FISCAL_INTEG/CA/BI/template /Shared Folders/Custom/Local Solution/BR/Fiscal

Integrations
14. For upload of Data Models artefacts, you must navigate to the structure /Shared
Folders/Custom/Local Solution/BR/Fiscal Integrations/Process/Data Models or /Shared
Folders/Custom/Local Solution/BR/Fiscal Integrations/Data Models, click on Upload Resource
icon. There are two upload resource icon available: one in the upper left panel option. Other in
the borrow left panel option
IMPORTANT: All files “.xdmz” must be imported to this folder
207
The following page will be displayed:
15. Press Choose File button and select each file in path:
“patch_number”/BR/FISCAL_INTEG/CA/BI/Process/datamodel or
“patch_number”/BR/FISCAL_INTEG/CA/BI/datamodel for upload.
208
16. Click on Upload button
17. You will receive a message Upload Completed. After to finish uploads for all artefacts of the
patch, a similar page will be displayed showing all the artefact uploaded:
18. For upload of Template artefacts, you must navigate to the structure /Shared
Folders/Custom/Local Solution/BR/Fiscal Integrations/Process or /Shared
Folders/Custom/Local Solution/BR/Fiscal Integrations, click on Upload Resource icon. There
are two upload resource icon available: one in the upper left panel option. Other in the borrow
left panel option
IMPORTANT: All files “.xdoz” must be imported to this folder
209
The following page will be displayed:
19. Press Choose File button and select each file in path:
“patch_number”/BR/FISCAL_INTEG/CA/BI/Process/template or
“patch_number”/BR/FISCAL_INTEG/CA/BI/template for upload.
210
20. Click on Upload button
21. You will receive a message Upload Completed. After to finish uploads for all artefacts of the
patch, a similar page will be displayed showing all the artefact uploaded:
22. After uploaded the artefact, is necessary associated the Template with Data Models
corresponding. For this, you must select de Template and click on “Edit” link:
211
23. In this page, you must click in Find icon, in Data Model section, for select the Data Model
corresponding for the template.
24. Under folder “Process → Data Models” or “Data Models”, you must select the artefact
corresponding for the for template. This information is in topic “Release the Reports” in this
document.
212
25. Click on Open button
26. Click on Save icon.
IMPORTANT: You must repeat the steps from 22 to 26 for all files “.xdoz” and “.xdmz”
included in the patch
213
GENERATING THE REPORTS
Use Reports and Analytics work area to run reports referenced by this document that must be executed
only by user (no have XML output). It’s not applied to Fiscal Partner ISV.
To get to the Reports and Analytics go to Navigator -> Tools -> Reports and Analytics
Fiscal Partner ISV must use WebServices (WS) to get XML data integration for generate Government
Fiscal Obligations. Exists 2 WS can be used, as below:
• Batch Processing: Must be used to integrate high data volume.
Please, verify topic: “Mass Processing” for more details about this solution.
For this integration Fiscal Partner ISV must use ScheduleService WebService
(https://<servername>/xmlpserver/services/v2/ScheduleService?wsdl).
Please, see notes below in My Oracle Support for more details:
- How To Schedule BI Publisher Report And Download Output Via Web Service? (Doc ID
2543601.1)
- Oracle BI Publisher Web Services APIs - Common Use Case Examples (Doc ID 1344535.1)
• Online Processing: Must be used to integrate low data volume
For this integration Fiscal Partner ISV must use PublicReportService WebService – operation:
runReport (https://<servername>/xmlpserver/services/PublicReportService?wsdl).
Please, see notes below in My Oracle Support for more details:
- Oracle BI Publisher Web Services APIs - Common Use Case Examples (Doc ID 1344535.1)
In the next topic will be showed the reports available for Brazilian ISVs.
214
LACLS_CHARTOFACCOUNTS (CHART OF ACCOUNTS)
The LACLS_ChartOfAccounts Extractor shows in xml format the chart of accounts plans by Legal entity,
Ledger, Establishment and Segment Name (that use to be Account or Cost of Center).
REPORT PARAMETERS
The following table describes the report parameters:
Name Description
Legal Entity LOV of Legal Entity
Ledger LOV of Ledger, considering Legal Entity informed in parameter
Establishment LOV of Establishment, considering Legal Entity informed in parameter
Segment Name LOV of Segment Name of Flexfield Structure
Complete Segment? LOV with values Y/N. Default value: Y. This parameter is not used for
filter the records.
This is used for show in tag <CONCATENATED_SEGMENTS> the

complete segment value or only the account segment value. It’s not
used as parameter for filter the data.
Last Update Date - From Last Update Date for start the find of records
(format YYYY-MM-DDT00:00:00.000-00:00)
Rownum From Row number for start the find of records
Rownum To Row number for end the find of records
FREQUENTLY ASKED QUESTIONS

The following table lists frequently asked questions about the LACLS_ChartOfAccounts Extractor
FAQ Answer
How do I find this report?
1. Go to Navigator
2. In Tools, Click on Reports and Analytics
3. Click on Browse Catalog button
4. Click on Shared Folders → Custom → Local Solution → BR →

Fiscal Integrations
215
5. Click on Open Link from “LACLS_ChartOfAccounts”
6. Enter the input Parameters and press Apply button
When do I use this Monthly

report?
What can I do with this Generate the Chart of Accounts Plan or Cost of Center Plan by Legal Entity
report? and Ledger for ISVs.
216
LACLS_EXTRACTAPSPEDDATA_INCREMENTAL (FDC/AP INVOICES EXTRACT DATA)
The LACLS_ExtractApSpedData_Incremental Extractor shows in xml format all inbound invoices by a

period of date.
REPORT PARAMETERS
Name Description
Legal Entity LOV of Legal Entity, considering only LE for Brazil country
Business Unit LOV of Business Unit, considering Legal Entity informed in parameter
Legal Reporting Unit LOV of Legal Reporting Unit, considering Business Unit and Legal
Entity informed in parameters
Invoice Number Invoice Number
Invoice Date From Invoice Issuing Date From (format DD-MM-YYYY)
Invoice Date To Invoice Issuing Date To (format DD-MM-YYYY)
GL Date From Invoice Accounting Date From (format DD-MM-YYYY)
GL Date To Invoice Accounting Date To (format DD-MM-YYYY)
Last Update Date From Last Update Date for start the find of records
Last Update Date To Last Update Date for end the find of records
Model Invoice Model (FDC transactions – model core field / AP transactions
– Model DFF field). Only fiscal documents with Model filled is showed
in extractor

The following table lists frequently asked questions about the LACLS_ExtractApSpedData_Incremental
Extractor
FAQ Answer
1. Go to Navigator
217

Fiscal Integrations
5. Click on Open Link from “LACLS_ExtractApSpedData_Incremental”
When do I use this On Demand

report?
What can I do with this Generate AP Invoices Information by period.
report?
218
LACLS_EXTRACTARSPEDDATA_INCREMENTAL (AR INVOICES / SHIPMENT EXTRACT DATA)
The LACLS_ExtracArSpedData_Incremental Extractor shows in xml format, Shipment and Receivables

transactions, by a period of date.
REPORT PARAMETERS
Name Description
Last Update Date - From Last Update Date from - for start the find of records (format YYYY-
MM-DDT00:00:00.000-00:00). It’s required.
Last Update Date - To Last Update Date to - for end the find of records (format YYYY-MM-
DDT00:00:00.000-00:00)
Document number Transaction Number
LRU LOV of Legal Reporting Unit
Invoice Status LOV of Fiscal Document status – only FDG transactions. Default
values: APPROVED, CANCEL and VOID
For AR transactions select “All” option
Complete Flag AR Transactions status. Contains LOV with values Y/N. Default value:
Y
CFOP Find transactions with CFOP informed in parameter. If transaction has
different CFOPs in lines and one lines has the CFOP informed, all lines
are be showed.

The following table lists frequently asked questions about the LACLS_ExtracArSpedData_Incremental
Extractor
FAQ Answer
1. Go to Navigator
219
Fiscal Integrations
5. Click on Open Link from “LACLS_ExtractArSpedData_Incremental”

report?
What can I do with this Generate AR Invoices Information by period.
report?
220
LACLS_RECEIVABLES3PARTYPROCESSINGSTATUS (AR INVOICES ANALYTIC REPORT)
The LACLS_Receivables3PartyProcessingStatus Report shows an analytic report the status of processing

AR Invoices by ISV. It’s showed the chart and table with data selected, considering parameters
REPORT PARAMETERS
Name Description
Date From Date From (format MM-DD-YYYY)
Date To Date To (format MM-DD-YYYY)

The following table lists frequently asked questions about the LACLS_Receivables3PartyProcessingStatus
Report
FAQ Answer
1. Go to Navigator

Fiscal Integrations
221
5. Click on Open Link from
“LACLS_Receivables3PartyProcessingStatus”

report?
What can I do with this Generate Status of AR Invoices processed.
report?
222
LACLS_SPEDINVBLOCOH (INV TRANSACTIONS – SPED BLOCO H)
The LACLS_SpedInvBlocoH Extractor shows in xml format all inventory transactions comply with SPED
Bloco H.
REPORT PARAMETERS
Name Description
As Of Date Reference Date of item (format MM-DD-YYYY)
Cost Organization LOV of Cost Organization
Cost Book LOV of Cost Book
Item LOV of Item

The following table lists frequently asked questions about the LACLS_SpedInvBlocoH Extractor
FAQ Answer
1. Go to Navigator

Fiscal Integrations
223
5. Click on Open Link from “LACLS_SpedInvBlocoH”

report?
What can I do with this Generate inventory transactions comply with SPED Bloco H by Third Party
report? System.
224
LACLS_EXTRACTSPEDASSETDEPRN (SPED BLOCO S F120/F130 AND CIAP BLOCO G)
The LACLS_ExtractSpedAssetDeprn Extractor shows in xml format all asset for comply with SPED Bloco
F120 and F130 (PIS/COFINS) and Bloco G (ICMS-CIAP).
NOTE:
This report has CreatingFiscalDocumentsforFixedAssetTransfers.pdf (Order to Cash for Brazil Doc ID
2335507.1) document as prerequisite that consist in prepare Asset module to internal transfer assets
using fiscal documents. So, the main point here is creating asset location and associate them to Legal
Reporting Units, so for this the minimum steps of documents are: 2B, 2C and 2D other ones is
required if you use FDG to transfer assets.
As the same extractor is used to generate different obligations, all parameters are able for use, but is
important pay attention in filled some parameters, as example below:
• Bloco G:
o Acquisition Date From => first day of the month to consider fixed asset buy
o Acquisition Date To => last day of the month to consider fixed asset buy
o Generate Depreciation => N
Note:
1) It’s recommended to use parameters “Rownum From” and “Rownum To”
2) To get ICMS amount recovery tax, it’s necessary found invoice in AP
extractor: LACLS_ExtractApSpedData_Incremental. As AP integration occurs
before Fixed Asset integration, it’s recommended that fiscal partner use data
already integrated. If this is not possible and it’s necessary to call AP extractor
again, fiscal partner must use parameter “Invoice Date From” and “Invoice
Date To” and put the result in a temporary table (to avoid multiple calls in AP
extractor)
3) Quantity of tax recovery installments is controlled by the Fiscal Partner
• Bloco F120 (Depreciation):

o Generate Depreciation => Y
o Depreciation Date From => first day of the month to consider fixed asset depreciation
o Depreciation Date To => last day of the month to consider fixed asset depreciation
o PIS/COFINS Credit Taking => DEPRECIATION (If this parameter is null, must be
considered <G_ASSET_ID>.<G_ASSET_SUMMARY>.<CRED_TYPE> tag equals
DEPRECIATION) in XML file
225
2) To get PIS and COFINS amount recovery tax, when Credit Taken is on
Depreciation, not is necessary use AP extractor, because depreciation amount
is calculated by Fixed Asset module. Fiscal Partner must apply PIS/COFINS
percentual (1,65% and 7,60%) over depreciation amount (tag:
<G_ASSET_ID>.<G_ASSET_DEPRN>.<DEPRN_AMOUNT>)
3) Quantity of tax recovery installments is controlled by Fixed Asset module
(G_ASSET_ID>.<G_ASSET_SUMMARY>.<LIFE_IN_MONTHS>)
• Bloco F130 (Acquisition):

o Acquisition Date From => first day of the month to consider fixed asset acquisition
o Acquisition Date To => last day of the month to consider fixed asset acquisition
o Generate Depreciation => N
o PIS/COFINS Credit Taking => AQUISITION (If this parameter is null, must be considered
<G_ASSET_ID>.<G_ASSET_SUMMARY>.<CRED_TYPE> tag equals AQUISITION) in XML file
Note:
2) To get PIS and COFINS amount recovery tax, it’s necessary found invoice in AP
extractor: LACLS_ExtractApSpedData_Incremental. As AP integration occurs
before Fixed Asset integration, it’s recommended that fiscal partner use data
already integrated. If this is not possible and it’s necessary to call AP extractor
again, fiscal partner must use parameter “Invoice Date From” and “Invoice
Date To” and put the result in a temporary table (to avoid multiple calls in AP
extractor)
3) Quantity of tax recovery installments is controlled by the Fiscal Partner
REPORT PARAMETERS
Name Description
LRU LOV of Legal Reporting Unit (LRU), considering Legal Entity informed
in parameter
Ledger Name LOV of Ledgers, considering Legal Entity and LRU informed in
parameters
Asset Num Asset Number
CNPJ Num CNPJ Number of Legal Reporting Unit (LRU) OBSOLETE – MUST BE
USE LRU PARAMETER
Acquisition Date From Acquisition Date (format DD-MM-YYYY)
Acquisition Date To Acquisition Date (format DD-MM-YYYY)
226
Generate Depreciation LOV with options: Y or N. Responsible to shown <G_ASSET_DEPRN>
group in XML file
Depreciation Date From Date From of asset depreciation (format DD-MM-YYYY)
Depreciation Date To Date To of asset depreciation (format DD-MM-YYYY)
PIS/COFINS Credit Taking LOV with options: AQUISITION or DEPRECIATION

The following table lists frequently asked questions about the LACLS_ExtractSpedAssetDeprn Extractor
FAQ Answer
1. Go to Navigator

Fiscal Integrations
5. Click on Open Link from “LACLS_ExtractSpedAssetDeprn”
227

report?
What can I do with this Generate asset depreciation comply with SPED Bloco F120 and F130 by
report? Third Party System.
228
LACLS_EXTRACTTAXES
The LACLS_ExtractTaxes Extractor shows in xml format all taxes setup in ERP Cloud. This is an auxiliary
extractor of tax setup information for third party query.
REPORT PARAMETERS
Name Description
Tax Tax Name. Can be informed only part of tax name and internally, the
extractor will consider the special character % for find the tax.
Tax Rate Tax Rate (only numbers – without signal “%”)
Regime Type LOV Regime type with options: Transaction (I) and Withholding (W)
Tax Type Tax Type Name. Can be informed only part of tax type name and
internally, the extractor will consider the special character % for find the
tax.
IBGE Code IBGE Code for identify City for tax municipal (ISS)

The following table lists frequently asked questions about the LACLS_ExtractTaxes Report
FAQ Answer
1. Go to Navigator

Fiscal Integrations
229
5. Click on Open Link from “LACLS_ExtractTaxes”

report?
What can I do with this Generate tax setup information.
report?
230
LACLS_EXTRACTFINANCIALAPPOINTMENT (APONTAMENTO FINANCEIRO)
The LACLS_ExtractFinancialAppointment Extractor was created for attend “NDD-Frete” Third Party. It’s
shows in xml format payments of invoice (fatura) related to CTe and NFSe documents.
REPORT PARAMETERS
Name Description
CNPJ Tomador CNPJ number of Company that will be pay the invoice (fatura)
CNPJ Supplier CNPJ number of Supplier that was paid in invoice (fatura)
Invoice Num Invoice number (fatura) that was paid
Date From Date From of invoice (fatura) payment
Date To Date To of invoice (fatura) payment

The following table lists frequently asked questions about the LACLS_ExtractFinancialAppointment
Extractor
FAQ Answer
1. Go to Navigator

Fiscal Integrations
231
5. Click on Open Link from “LACLS_ExtractFinancialAppointment”

report?
What can I do with this Generate payment of invoice (fatura) information.
report?
232
LACLS_POSEARCH
The LACLS_PoSearch Extractor shows in xml format all Purchase Orders, considering the parameters
options.
This extractor show all open POs generated by the Company, referring to service purchases.
Parameter “Company CNPJ Number” must be informed the Company CNPJ that is taking the service and
in parameter “Supplier CNPJ Number” must be informed the Supplier CNPJ providing the service. If the
supplier informed the Purchase Order number in the fiscal document (it must be mapped in the project,
since the ABRASF layout does not have a specific field), the “PO Number” parameter must be used.
This extractor must be used in the integration with the Service Invoice, in order to identify the necessary
fields to insert in the Open Interface of the AP, as detailed in the topic “Integration NFSe x AP” of this
document.
Fiscal Third-Party, after capturing the Purchase Order data in the ERP Cloud, must do the validations
below, considering the information from the Supplier Service Fiscal Document, in order to find the PO. If
it is not possible to derive the PO, the extractor always returns a line, only with the information of the
Company and the Supplier. Thus, it is possible to search for the necessary data to be inserted in the AP
Open Interface, without using the PO reference.
Following are the validations to derive the PO:
1) Consider tag <PRODUCT_FISC_CLASSIFICATION> of extractor that has “Lei Complementar 116”

information (<ItemListaServico> - campo: B-31 no layout ABRASF) or City Code information
(<CodigoTributacaoMunicípio> - campo: B-33 no layout da ABRASF). It is necessary to confirm with
customer if both information are be used or LC116 only. This registration in the ERP Cloud must
be doing in item catalog setup: LACLS_SERVICE_CODE or LACLS_NCM_SERVICE_CODE (details are
in the document: Setup Brazil to work with ISVs - My Oracle Support: LACLS - Integrations with
ISVs (Doc ID 2240956.1).
2) Consider tags: <NEED_BY_DATE> or <PROMISED_DATE> of extractor that be nearest of NFSe

issuing date (campo A-4 <DataEmissao> no layout ABRASF). If the 2 dates are informed in the PO,
consider the lowest date.
3) Consider value available in Shipment PO that will be billed with service value in the NFSe
(<ValorServicos> - campo: B-16 no layout da ABRASF). To find this balance, it is necessary:
a. Find available quantity: perform tags subtraction <SHIPMENT_QUANTITY> and

<SHIPMENT_QUANTITY_BILLED> of extractor.
b. Multiply the previously found available quantity by the unit value - tag
<LINE_UNIT_PRICE> of extractor.
233
4) If you do not find POs with a balance available to bill the NFSe, you must add the balances of the
POs found and:
a. If the sum of the POs is enough to pay the NFSe, several lines must be inserted in the
document for the AP interface, one line for each PO found. In this case, the WS call must
be made, considering the <InvoiceInterfaceLine> group for each line referring to the
previously located POs.
b. If the sum of the POs is not enough to make the payment of the NFSe, the balance found
in the PO must be considered and the remainder must be entered without a PO in the
Open Interface of the AP, without the association with the PO.
If the extractor does not find any PO for the Company and Supplier informed, the group
<G_PO_DETAILS> will not be displayed and the fiscal document must be inserted in the AP Open
Interface, without association with PO.
REPORT PARAMETERS
Name Description
Company CNPJ Number It’s required. Must be informed the Company CNPJ Number in Supplier
Fiscal Document
Supplier CNPJ Number It’s required. Must be informed the Supplier CNPJ Number in Supplier
Fiscal Document
PO Number It’s optional. If informed, must be Purchase Order Number in Supplier
Fiscal Document

The following table lists frequently asked questions about the LACLS_PoSearch Extractor
FAQ Answer
1. Go to Navigator
234
Fiscal Integrations
5. Click on Open Link from “LACLS_PoSearch”

report?
What can I do with this Generate Purchase Order Information.
report?
235
LACLS_EXTRACTSPEDINVBLOCOK (INV TRANSACTIONS – SPED BLOCO K)
The LACLS_ExtractSpedInvBlocoK Extractor shows in xml format all inventory transactions comply with
SPED Bloco K.
REPORT PARAMETERS
Name Description
Inv Org LOV of Inventory Organization
Accounting Period LOV of period – format: MON-YY
CNPJ LOV of Legal Reporting Unit (LRU)

The following table lists frequently asked questions about the LACLS_ExtractSpedInvBlocoK Extractor
FAQ Answer
1. Go to Navigator

Fiscal Integrations
236
5. Click on Open Link from “LACLS_ExtractSpedInvBlocoK”

report?
What can I do with this Generate inventory transactions comply with SPED Bloco K by Third Party
report? System.
237
LACLS_BR_TAXAUTHORITYSUPPLIERDETAILSDATA
The LACLS_BR_TaxAuthoritySupplierDetailsData Extractor shows in xml format the setup about Tax
Authority Suppliers.
REPORT PARAMETERS
Name Description
Business Unit LOV of Business Unit
Supplier LOV of Supplier configured as TAX AUTHORITY type
Supplier Site LOV of Supplier Site Code

The following table lists frequently asked questions about the
LACLS_BR_TaxAuthoritySupplierDetailsData Extractor
FAQ Answer
1. Go to Navigator

Fiscal Integrations
238
5. Click on Open Link from
“LACLS_BR_TaxAuthoritySupplierDetailsData”

report?
What can I do with this Generate Tax Authority Supplier Details by Third Party System.
report?
239
LACLS_EXTRACTTAXWITHHOLDINGDATA
The LACLS_ExtractTaxWithholdingData Extractor shows in xml format the Wihholding Tax information
in inbound transactions.
It’s like G_TAXES_WITHHELD_V in LACLS_ExtractApSpedData_Incremental extractor, with parameters
that allow found records using payment information, for example: check date.
REPORT PARAMETERS
Name Description
Legal Entity LOV of Legal Entity, considering only LE for Brazil country
Business Unit LOV of Business Unit, considering Legal Entity informed in
parameter
Invoice Number Invoice Number (main invoice – no withhold invoice)
Tax Withhold - Date From Tax Withhold Date From (format MM-DD-YYYY) – used as filter in
<TAX_POINT_DATE> tag
Tax Withhold - Date To Tax Withhold Date To (format MM-DD-YYYY) – used as filter in
<TAX_POINT_DATE> tag
Withhold Calculation Point Possible values:
Invoice -> when calculation point is entry of transaction
Payment -> when calculation point is payment of transaction
Invoice Date Invoice Date (main invoice – no withhold invoice)
CNPJ Number LRU’s CNPJ

The following table lists frequently asked questions about the LACLS_ExtractTaxWithholdingData
Extractor
FAQ Answer
1. Go to Navigator
240
Fiscal Integrations
5. Click on Open Link from “LACLS_ExtractTaxWithholdingData”

report?
What can I do with this Generate Tax Withholding information by Third Party System.
report?
241
LACLS_EXTRACTARMOD21
The LACLS_ExtractArMod21 Extractor shows in xml format data information about Fiscal Document
Model 21 that will be used by ISV to format according company business requirements
REPORT PARAMETERS
Name Description
Trx Number Transaction Number from AR Transactions
LRU LOV of Legal Reporting Unit used to create a Model 21
Complete Flag AR Transactions status. Contains LOV with values Y/N. Default
value: Y
Last Update Date - To Last Update Date to - for end the find of records (format YYYY-
MM-DDT00:00:00.000-00:00)

The following table lists frequently asked questions about the LACLS_ExtractArMod21 Extractor
FAQ Answer
1. Go to Navigator

Fiscal Integrations
242
5. Click on Open Link from “LACLS_ExtractArMod21”

report?
What can I do with this Generate Invoice Model 21 information by Third Party System.
report?
243
LACLS_NFSESUBSTITUTEREPORT
The LACLS_NFSeSubstituteReport Report shows an analytic information about NFSe Substitute that was
not cancel AR Transactions. It’s showed the table with data selected, considering parameters
REPORT PARAMETERS
Name Description
Business Unit LOV of Business Unit, considering Legal Entity informed in
parameter
LRU LOV of Legal Reporting Unit

The following table lists frequently asked questions about the LACLS_NFSeSubstituteReport Report
FAQ Answer
1. Go to Navigator

Fiscal Integrations
244
5. Click on Open Link from “LACLS_NFSeSubstituteReport”

report?
What can I do with this Generate NFSe Substitute Report.
report?
245
LACLS_EXTRACTDFFSETUPDETAILS
The LACLS_ExtractDFFSetupDetails Extractor shows in xml format, details about Descriptive Flexfield
setup in customer environment. With this information, Fiscal Third-Party can derive the attribute in FDG
extractor with the data origin in ERP Cloud.
REPORT PARAMETERS
Name Description
Context Code Inform the DFF Context Code, for example: LACLS_BR_TAX_PAY.
It’s possible to inform only part of the text to find, for example: TAX
Table Name Inform the Table Name that has DFF information setup, for
example: AP_INVOICES_ALL. It’s possible to inform only part of
the text to find, for example: INV
Column Name Inform the Column Name that has DFF information setup, for
example: ATTRIBUTE1. It’s possible to inform only part of the text
to find, for example: 1
Segment Code Inform the Segment Code that has DFF information setup, for
example: ISV_MODEL. It’s possible to inform only part of the text
to find, for example: MODEL
Segment Enable Flag LOV possible values: Y/N.

The following table lists frequently asked questions about the LACLS_ExtractDFFSetupDetails Extractor
FAQ Answer
1. Go to Navigator

Fiscal Integrations
246
5. Click on Open Link from “LACLS_ExtractDFFSetupDetails”

report?
What can I do with this Generate Descriptive Flexfield setup details.
report?
247
LACLS_RUNNINGPROCESSES
The LACLS_RunningProcesses Extractor must be used for getting job quantity in “Running” status. This is
necessary for put new jobs in schedule processes. Other statuses are able and “Running” is default.
REPORT PARAMETERS
Name Description
Status LOV of Status. RUNNING is default value. Possible values:
BLOCKED
CANCELLED
CANCELLING
COMPLETED
ERROR
ERROR_AUTO_RETRY
ERROR_MANUAL_RECOVERY
EXPIRED
FINISHED
HOLD
PAUSED
PENDING_VALIDATION
READY
RUNNING
SCHEDULE_ENDED
SUCCEEDED
VALIDATION_FAILED
WAIT
WARNING

The following table lists frequently asked questions about the LACLS_RunningProcesses Extractor
FAQ Answer
1. Go to Navigator
248

Fiscal Integrations
5. Click on Open Link from “LACLS_RunningProcesses”

report?
What can I do with this Get job quantity in processing.
report?
249
LACLS_MANAGEINVOICEMOD21
The LACLS_ManageInvoiceMod21 is a report that shows an analytic information about Model 21

documents. It’s showed the table with data selected, considering parameters
REPORT PARAMETERS
Name Description
Trx Number Transaction Number from AR Transactions
LRU LOV of Legal Reporting Unit used to create a Model 21
Complete Flag AR Transactions status. Contains LOV with values Y/N. Default
value: Y
Last Update Date - To Last Update Date to - for end the find of records (format YYYY-
MM-DDT00:00:00.000-00:00)

The following table lists frequently asked questions about the LACLS_ManageInvoiceMod21 Report
FAQ Answer
1. Go to Navigator

Fiscal Integrations
250
5. Click on Open Link from “LACLS_ManageInvoiceMod21”

report?
What can I do with this Generate Model 21 Report.
report?
251
FILES IN UCM
GenericSoapPort Web Service (https://<hostname:port>/idcws/GenericSoapPort) is used for getting

information about files in UCM. This is identifier by values informed in idcService Parameter. For
example: idcService=GET_SEARCH_RESULTS or idcService=GET_FILE.
However, for operations as file delete or update file title in UCM, it’s necessary a custom specific role.
This topic contains a step-by-step for create role customization and some payload examples about this
Web Services.
ROLE CONTENT_ADMINISTRATON_CUSTOM
LACLS_CONTENT_ADMINISTRATION_CUSTOM role must be created based in role core:

CONTENT_ADMINISTRATION.
For create the custom role setup, you must:
1) Navigate to Tools -> Security Console
2) In option “Roles”, click on “Create Role” button
3) Enter with the information as the follow:
Create Role
Role Name Content Administration Custom
Role Code LACLS_CONTENT_ADMINISTRATION_CUSTOM
Role Category Common - Job Roles
Predefined Role Not selected
Description
252
4) Click on “Next” button for steps: 2 and 3.
5) In the step 4, must add the core role: Content Administration. Click in “+ Add Role” option and
pop-up to search role is show
6) Search for text: “Content Administration”
7) Select role “Content Administration” and click on “Add Role Membership” button
8) After click on “Add Role Membership” button, the pop-up is closed and the screen in step: 4 is
like this:
253
9) Click on “Next” button in steps: 4, 5 and 6.
10) In step: 7, click on “Save and Close” button, as below:
11) Associate custom role: “Content Administration Custom” in integration user that will be access
in UCM (Content Server)
12) Execute LDAP Jobs. Navigate to “Tools -> Schedule Processes” and execute the processes below,
using “New Schedule Processes” button:
a. Send Personal Data for Multiple Users to LDAP
b. Send Pending LDAP Requests
c. Retrieve Latest LDAP Changes
254
PAYLOAD EXAMPLES
This topic contains payload examples for different values used in “idcService” parameter
• IdcService="GET_SEARCH_RESULTS"
<soapenv:Body>
<ucm:GenericRequest webKey="cs">
<ucm:Service IdcService="GET_SEARCH_RESULTS">
<ucm:Document>
<ucm:Field name="QueryText">dDocAccount <Substring> `fin$/receivables$/import`</ucm:Field>
<ucm:Field name="QueryText">dDocTitle <Substring> `XML_Nfe`</ucm:Field>
</ucm:Document>
</ucm:Service>
</ucm:GenericRequest>
</soapenv:Body>
• IdcService="GET_FILE"
<soapenv:Body>
<ucm:Service IdcService="GET_FILE">
<ucm:Document>
<ucm:Field name="dDocTitle">XML_Nfe_2068139_2022-01-26_13_01_592</ucm:Field>
<ucm:Field name="dID">2938243</ucm:Field>
</ucm:Document>
</ucm:Service>
</soapenv:Body>
• IdcService="DELETE_DOC"
<soapenv:Body>
<ucm:Service IdcService="DELETE_DOC">
<ucm:Document>
<ucm:Field name="dDocAccount">fin$/receivables$/import</ucm:Field>
</ucm:Document>
</ucm:Service>
</soapenv:Body>
</soapenv:Envelope>
255
• IdcService="UPDATE_DOCINFO"
<soapenv:Body>
<ucm:Service IdcService="UPDATE_DOCINFO">
<ucm:Document>
<ucm:Field name="dTitle">Processed_XML_Nfe_xxxxx.xml</ucm:Field>
<ucm:Field name="dDocAccount">fin$/receivables$/import</ucm:Field>
</ucm:Document>
</ucm:Service>
</soapenv:Body>
</soapenv:Envelope>
256
INTEGRATION NFSE X AP
Web Service used in this integration is responsible for inserting the Service Invoice data into Open
Interface AP tables. Details can be found at the links:
• Header = https://docs.oracle.com/en/cloud/saas/financials/22a/oeswf/invoiceheader-d16547e39192.html#invoiceheader
• Lines = https://docs.oracle.com/en/cloud/saas/financials/22a/oeswf/invoiceline-d16547e33928.html#invoiceline
After execution this Web Service by the Fiscal Third-Party, the Service Invoice will be available for
processing, using the Job Process: “Import Payables Invoice”. The user must manually submit this Job,
using the Source parameter equal to "LACLS_BR_NFSE", as defined in the mapping table (See details in
next topic). When finished, the Job displays a detailed report with possible processing errors, allowing
corrections in Open Interface AP, if necessary.
For finished with successfully the Open Interface AP process, it’s necessary basic setup, for example:
Company, Supplier, Items, etc. and some specifics setup for this integration. These setups can be identified
with blue color in the “Note” column in the mapping table below. Details on the specific setups, please,
verify document: Recommended Approach to Setup Oracle ERP Cloud focusing on Brazilian Taxes in My
Oracle Support – DocId: Latin America Cloud Local Solution for Brazil (Doc ID 2291252.1)
Company taking service is the responsible of transaction taxes calculation or withholding taxes calculation.
Therefore, these taxes must be calculated in the AP, as expected in the customer scenario.
257
WS FIELDS MAPPING
Fields mapped below are required for the integration of service invoices into the Open Interface AP.
This mapping was performed using the topic “10 ESTRUTURAS DE DADOS” of ABRASF layout, version 2.04. For more details, see the link:
http://www.abrasf.org.br/arquivos/publico/NFS-e/Versao_2.04/NFS-e_Manual_de_Orientacao_do_Contribuinte_2.04.pdf
# Campo Pai Tipo Ocor Tam Dec Desc NFSE LAYOUT ABRASF Note
1 Header - 1-1 - -
2 invoiceInterfaceHeader createInvoiceInterface - 1-1 - -
Configurar o valor
3 Source invoiceInterfaceHeader C 1-1 - Fixo "LACLS_BR_NFSE" não se aplica "LACLS_BR_NFSE " na lookup de
origem de documento no AP.
<CPFCNPJTomador> - campo: B-48
Com base no CNPJ do tomador da
buscar o ID da organização no extrator LACLS_PoSearch.
4 OrgId invoiceInterfaceHeader N 0-1 - NFSe, pesquisa no extrator
Tag <G_IDENTIFIERS>.<BUSINESS_UNIT_ID>
LACLS_PoSearch no parâmetro:
Company CNPJ Number
<CPFCNPJTomador> - campo: B-48
Com base no CNPJ do tomador da NFSe
buscar o ID do entidade legal no extrator
5 LegalEntityId invoiceInterfaceHeader N 0-1 - (campo 10.17.1.1 da ABRASF), pesquisa
LACLS_PoSearch. Tag <G_IDENTIFIERS>.<LE_ID>
no extrator LACLS_PoSearch no
parâmetro: Company CNPJ Number
buscar o ID do entidade legal no extrator

6 FirstPartyRegistrationId invoiceInterfaceHeader N 0-1 - LACLS_PoSearch. Tag não se aplica
<G_IDENTIFIERS>.<REGISTRATION_ID>
<CPFCNPJPrestador> - campo: B-43

Com base no CNPJ do prestador da
buscar o ID do fornecedor no extrator LACLS_poSearch.
7 VendorId invoiceInterfaceHeader N 0-1 - NFSe, pesquisa no extrator
Tag <G_IDENTIFIERS>.<SUPPLIER_ID>
LACLS_PoSearch no parâmetro:
Supplier CNPJ Number
258

buscar o ID do site do fornecedor no extrator Com base no CNPJ do prestador da
8 VendorSiteId invoiceInterfaceHeader N 0-1 - LACLS_poSearch. Tag NFSe, pesquisa no extrator
<G_IDENTIFIERS>.<SUPPLIER_SITE_ID> LACLS_PoSearch no parâmetro:
Supplier CNPJ Number
9 CalculateTaxDuringImportFlag invoiceInterfaceHeader C 1-1 - Fixo false não se aplica

10 AddTaxToInvoiceAmountFlag invoiceInterfaceHeader C 1-1 - Fixo false não se aplica
Exibir o numero da RPS, concatenada com a <Numero> - campo: B-4 ||-||
11 Description invoiceInterfaceHeader N 0-1 -
discriminação da NFSe <Discriminacao> - campo: B-35
12 GlDate invoiceInterfaceHeader D 1-1 - Data atual (SYSDATE) - formato YYYY-MM-DD não se aplica
Valor liquido da NFSe - 9999999999999.99 - formato 15
13 InvoiceAmount invoiceInterfaceHeader N 1-1 13 2 <ValorLiquidoNfse> - campo: A-11 Valor liquido da NFSe
posicoes - 13 inteiras e 2 decimais
14 InvoiceCurrencyCode invoiceInterfaceHeader C 1-1 - Fixo "BRL" não se aplica
15 PaymentCurrencyCode invoiceInterfaceHeader C 1-1 - Fixo "BRL" não se aplica
16 InvoiceDate invoiceInterfaceHeader D 1-1 - Data de emissão da NFSe - formato YYYY-MM-DD <DataEmissao> - campo: A-4
Número de identificação da NFSe concatenado data de
<Numero> - campo: A-2||-||
emissao (formator YYYYMMDD) e Numero do CNPJ do
17 InvoiceNumber invoiceInterfaceHeader C 1-1 - <DataEmissao> - campo: A-4 ||-||
prestador do serviço - utilizar o "-" para concatenar as
informações
18 InvoiceTypeLookupCode invoiceInterfaceHeader C 1-1 - Fixo "STANDARD" não se aplica
WS recupera do cadastrro do
fornecedor. Caso o cadastro nao
19 PaymentMethodCode invoiceInterfaceHeader C 0-0 pode ser nulo não se aplica tenha a definicao, o registro fica
parado na interface.
Se houver na PO manter o
TERM_ID dela. Caso tenha
associação de mais de uma PO
com diferentes TERMS_ID, deve
20 TermsId invoiceInterfaceHeader C 0-0 - pode ser nulo não se aplica ser deixado nulo e o WS recupera
do cadastro do fornecedor. Caso o
cadastro do fornecedor nao tenha
a configuracao, o registro fica
parado na interface.
Este campo pode ser usado para
calculo do imposto, definir se o
21 Document Fiscal Classification invoiceInterfaceHeader C 0-0 - pode ser nulo não se aplica projeto vai usar e qual valor deve
ser informado. Se não houver
definição informar nulo.
259
22 AttributeCategory invoiceInterfaceHeader C 1-1 Fixo "ISVCLS_BRA" não se aplica
Modelo do documento fiscal

Informar o modelo de acordo com o parceiro fiscal
Attribute? - deverá ser derivado para encontrar a
atributos fiscais para escrituração.
coluna do DFF que armazena o modelo, que pode variar
Consultar configuração no
por Empresa.
documento: Setup Brazil to work
Para encontrar a coluna do DFF que possui o modelo
with ISVs - My Oracle Support:
configurado no DFF: "ISV Additional Information",
23 Attribute? invoiceInterfaceHeader C 1-1 não se aplica LACLS - Integrations with ISVs (Doc
deve-se fazer um DE-PARA, considerando o code igual a
ID 2240956.1)
“ISV_MODEL”. Utilizar o extrator:
LACLS_ExtractDFFSetupDetails – Parâmetros: Context
Code = ISVCLS_BRA / Table Name = AP_INVOICES_ALL /
Segment Code = ISV_MODEL / Segment Enable Flag =
Yes
Tag: <G_DFF_LIST>.<COLUMN_NAME>
24 InvoiceInterfaceLine invoiceInterfaceHeader - 1-N - - Linha de Serviço
25 AccountingDate InvoiceInterfaceLine D 1-1 - Data atual (SYSDATE) - formato YYYY-MM-DD não se aplica
Valor total da NFSe - 9999999999999.99 - formato 15

26 Amount InvoiceInterfaceLine N 1-1 13 2 <ValorServicos> - campo: B-16 Valor total da NFSe
A definir junto com cliente, quando não tiver PO.
27 Description InvoiceInterfaceLine C 1-1 - Quando houver PO o sistema tras a descrição da linha da
PO.
Fixo "1" e deve ser sequencial quando o documento
28 LineNumber InvoiceInterfaceLine C 1-1 - não se aplica
possuir mais de uma linha
29 DistCodeConcatenated InvoiceInterfaceLine C 0-0 - não preencher em caso de PO não se aplica
30 DistributionSetName InvoiceInterfaceLine C 1-1 - Utilizar quando não tiver PO. Definir junto com cliente não se aplica Definir setup no Saas
31 LineTypeLookupCode InvoiceInterfaceLine C 1-1 - Fixo "ITEM" não se aplica
Quando tem PO não precisa informar.
32 ShipToLocationId InvoiceInterfaceLine N 0-0 Sem PO utilizar a tag não se aplica
<G_IDENTIFIERS>.<SHIP_TO_LOCATION_ID>
Definição de negócio (projeto) .
Pode ocorrer em alguns clientes,
de informar um terceiro local para
33 FinalDischargeLocationId InvoiceInterfaceLine N 0-0 - pode ser nulo não se aplica
cálculo do ISS. Necessário verificar
com o projeto.
pode ser nulo, O WS recupera como default quando

34 TrxBusinessCategory InvoiceInterfaceLine C 0-0 - não se aplica
definido na PO.
35 PrimaryIntendedUse InvoiceInterfaceLine C 0-0 - não se aplica Definir setup no Saas
definido na PO.
260
36 UserDefinedFiscClass InvoiceInterfaceLine C 1-1 - não se aplica Definir setup no Saas
definido na PO.
definido na PO.
OBS: No manual de ISV, sugerimos a criação do catalogo,
utilizando o padrão: Concatenar o codigo da lista federal
do item e o codigo do municipio, iniciando com pipe "|". <ItemListaServico> - campo: B-31
37 ProductFiscClassification InvoiceInterfaceLine C 0-0 - Ex: |1401|140101. <CodigoTributacaoMunicípio> - Definir setup no Saas
No layout ABRASF, temos as tags <ItemListaServico> e campo: B-33
<CodigoTributacaoMunicípio>
Definir com cliente qual o padrão utilizado. Se as 2
informações concatenadas ou somente a Lei
Complementar 116

38 ProductCategory InvoiceInterfaceLine C 0-0 - Definir setup no Saas
definido na PO.

39 ProductType InvoiceInterfaceLine C 1-1 - definido na PO. não se aplica
Caso contrario, fixo "SERVICES"
Base de calculo do Imposto
40 AssessableValue InvoiceInterfaceLine N 1-1 - Valor total da NFSe - 9999999999999.99 - formato 15 <ValorServicos> - campo: B-16 Valor total da NFSe
41 Reference1 InvoiceInterfaceLine C 0-0 - pode ser nulo não se aplica
42 Reference2 InvoiceInterfaceLine C 0-0 - pode ser nulo não se aplica
Se tiver na PO, utilizar a tag
43 PONumber InvoiceInterfaceLine C 0-0 -
<G_PO_DETAILS>.<PO_NUMBER>. Caso contrario, nulo
44 POLineNumber InvoiceInterfaceLine C 0-0 - <G_PO_DETAILS>.<PO_LINE_NUMBER>. Caso contrario,
nulo
45 POShipmentNumber InvoiceInterfaceLine C 0-0 - <G_PO_DETAILS>.<SHIPMENT_NUM>. Caso contrario,
nulo
261
REQUEST PAYLOAD EXAMPLE
<soapenv:Envelope xmlns:inv="http://xmlns.oracle.com/apps/financials/payables/invoices/quickInvoices/invoiceInterfaceService/"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:typ="http://xmlns.oracle.com/apps/financials/payables/invoices/quickInvoices/invoiceInterfaceService/types/">
<soapenv:Header><wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"><wsu:Timestamp wsu:Id="TS-
88C73FAA831B31D765164279164996714"><wsu:Created>2022-01-21T19:00:49.966Z</wsu:Created><wsu:Expires>2053-09-
29T20:47:29.966Z</wsu:Expires></wsu:Timestamp><wsse:UsernameToken wsu:Id="UsernameToken-
88C73FAA831B31D765164279164996613"><wsse:Username>USER_NAME</wsse:Username><wsse:Password Type="http://docs.oasis-
open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">
PASSWORD</wsse:Password></wsse:UsernameToken></wsse:Security>
</soapenv:Header>
<soapenv:Body>
<typ:createInvoiceInterface>
<typ:invoiceInterfaceHeader>
<inv:Source>LACLS_BR_NFSE</inv:Source>
<inv:OrgId>300000001567037</inv:OrgId>
<inv:LegalEntityId>300000001566001</inv:LegalEntityId>
<inv:FirstPartyRegistrationId>300000013187152</inv:FirstPartyRegistrationId>
<inv:VendorId>300000002766857</inv:VendorId>
<inv:VendorSiteId>300000002766887</inv:VendorSiteId>
<inv:CalculateTaxDuringImportFlag>false</inv:CalculateTaxDuringImportFlag>
<inv:AddTaxToInvoiceAmountFlag>false</inv:AddTaxToInvoiceAmountFlag>
<inv:Description>99999-Teste WS NFSE x Open AP</inv:Description>
<inv:GlDate>2022-01-21</inv:GlDate>
<inv:InvoiceAmount currencyCode="BRL">10000.00</inv:InvoiceAmount>
<inv:InvoiceCurrencyCode>BRL</inv:InvoiceCurrencyCode>
<inv:PaymentCurrencyCode>BRL</inv:PaymentCurrencyCode>
<inv:InvoiceDate>2022-01-17</inv:InvoiceDate>
<inv:InvoiceNumber>88881-20220117-51083468000128</inv:InvoiceNumber>
<inv:InvoiceTypeLookupCode>STANDARD</inv:InvoiceTypeLookupCode>
<inv:AttributeCategory>ISVCLS_BRA</inv:AttributeCategory>
<inv:Attribute1>99</inv:Attribute1>


<inv:InvoiceInterfaceLine>
<inv:AccountingDate>2022-01-21</inv:AccountingDate>
<inv:Amount currencyCode="BRL">3431.50</inv:Amount>
<inv:LineNumber>1</inv:LineNumber>
<inv:LineTypeLookupCode>ITEM</inv:LineTypeLookupCode>
<inv:TrxBusinessCategory/>
<inv:PrimaryIntendedUse/>
<inv:UserDefinedFiscClass/>
<inv:ProductFiscClassification/>
<inv:ProductCategory/>
<inv:ProductType/>
<inv:FinalDischargeLocationId/>
<inv:AssessableValue>3431.50</inv:AssessableValue>
<inv:TaxClassificationCode/>
<inv:ShipToLocationId/>
<inv:PONumber>495</inv:PONumber>
<inv:POLineNumber>1</inv:POLineNumber>
<inv:POShipmentNumber>1</inv:POShipmentNumber>
</inv:InvoiceInterfaceLine>


<inv:InvoiceInterfaceLine>
<inv:AccountingDate>2022-01-21</inv:AccountingDate>
<inv:Amount currencyCode="BRL">6568.50</inv:Amount>
<inv:Description>NFSE SEM PO</inv:Description>
262
<inv:LineNumber>2</inv:LineNumber>
<inv:DistributionSetName>SP HQ</inv:DistributionSetName>
<inv:LineTypeLookupCode>ITEM</inv:LineTypeLookupCode>
<inv:TrxBusinessCategory/>
<inv:PrimaryIntendedUse/>
<inv:UserDefinedFiscClass/>
<inv:ProductFiscClassification>|0710|</inv:ProductFiscClassification>
<inv:ProductCategory/>
<inv:ProductType>SERVICES</inv:ProductType>
<inv:FinalDischargeLocationId/>
<inv:AssessableValue>6568.50</inv:AssessableValue>
<inv:TaxClassificationCode/>
<inv:ShipToLocationId>300000008104966</inv:ShipToLocationId>
</inv:InvoiceInterfaceLine>
</typ:invoiceInterfaceHeader>
</typ:createInvoiceInterface>
</soapenv:Body>
</soapenv:Envelope>
263
CUSTOM: RTV SCENARIO
This topic has details about the customization of RTV (Return To Vendor) scenario, where the CST that
must be considered when issuing the fiscal document (FDG Extractor) must be the derivation of CST
informed in the Supplier XML to RTV CST, and not the derivate/calculated by the ERP Cloud, when XML
is captured by FDC module.
The proposed solution is:

• customize the CMK to capture and store in the “tax situation code” field, the CST referring to
the taxes of the Supplier fiscal document, at the moment of entry into the FDC;
• configure FROM/TO list between inbound CST values (Supplier XML) with outbound CST (RTV
fiscal document issuing) using Mapping Set task;
• Since 22C ERP Cloud version, FDG released a new XML layout that use this setup for generate
tags <CST_CODE_RTV> and <ORIGINAL_CST_CODE> in group <TAX_LINES>. Details can be found
in:
https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/fin/releases/
22C/22C-financials-wn.htm#F23997
Note: Fiscal partner must use the new tag (<TAX_LINES>.<CST_CODE_RTV>) to generate CST
information in RTV Fiscal Document before generate and send to SEFAZ.
NOTE:
Customizations in the CMK process are the responsibility/maintenance of the project/customer.
CMK CUSTOM
CMK is the responsible to read the Supplier XML, to do the parse and to load tags values into FDC tables.
NOTE:
To do this customization is very import to know “Collaboration Message” module. Incorrect customs
in CMK files impact in failed of import Supplier XML into FDC module.
264
XML transformation file, used in CMK, must be modified to store the CST of taxes in Supplier XML, in the
TAX_SITUATION_CODE field of FDC table: JG_FSCL_TAX_LINES_ALL.
Details about this custom, please see topic: Oracle Cloud CMK Setup to optimize Fiscal Document
information in DocID: Latin America Cloud Local Solution for Brazil (Doc ID 2291252.1)
REQUIRED SETUPS
It’s necessary configure LRU with two Tax Reporting Code to identify if Company is contributor of ICMS
and IPI or not. You must do the mapping of derivate inbound CST to outbound CST too.
Details about this setup, please see attachment: Recommended Approach to Setup Oracle ERP Cloud
focusing on Brazilian Taxes in DocID: Latin America Cloud Local Solution for Brazil (Doc ID 2291252.1)
FDG – RTV FISCAL DOCUMENT ISSUING
Before 22C ERP Cloud version, for attend RTV scenario, FDG custom was necessary. This custom
included the tags: ORIGINAL_CST_CODE (CST Code from Supplier XML) and CST_CODE_RTV (Output CST
derived in mapping by user) in TAX_REFERENCE group in FDG XML layout.
Since 22C ERP Cloud version, FDG released a new XML layout that generate tags <CST_CODE_RTV> and
<ORIGINAL_CST_CODE> in group <TAX_LINES>. Details can be found in:
https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/fin/releases/22C/22C
-financials-wn.htm#F23997
So, for issuing RTV fiscal document, the Fiscal Third-Party must consider the tag: CST_CODE_RTV in
group <TAX_LINES> to generate XML and send to SEFAZ, because TAX_REFERENCE group does not exist
from 22C ERP version.
265
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject
to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose.
We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not
be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.
266

LACLS Fiscal ISV Integrations For Brazil

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LACLS Fiscal ISV Integrations For Brazil

Uploaded by

Copyright:

Available Formats

Oracle Financials Cloud

Latin America Cloud Local Solution

Date Version Notes

IMPORTATION / EXPORTATION PROCESS

ADDRESS OF CUSTOMER OR SUPPLY:

For importation or exportation processes, the address structure of Customers or

• Exportation → When country in tag <SHIP_TO_PARTY_SITE_COUNTRY> is

• Importation → When country in tag <SHIP_TO_PARTY_SITE_COUNTRY> is

<NATOP> TAG - SEFAZ

<INFCPL> TAG - SEFAZ

The AP fiscal extractor is showing the comments information in fiscal document.

The configuration will result something like this:

<TERM_ID> - FDG EXTRACTOR

The configuration will result something like this:

The configuration will result something like this:

LAYOUT SEFAZ SCENARIO 1 SCENARIO 2 SCENARIO 3

For generate <vDup> tag, it’s necessary:

1) Subtract discount amount (<TRADING_DISCOUNT> tag).

<DHEMI> AND <DHSAIENT> TAGS - SEFAZ

<REFNFP> GROUP - SEFAZ

• Less than 45, you can submit new jobs.

1) Navigate to Setup and Maintenance

Create Fiscal Attribute Defaults

Attribute Template LACLS_BR_EXPORTATION

Start Date *filled automatically with actual date

Legal Message Code Legal Message Text

6) Click on “Save and Close” button

The configuration will result something like this:

SEFAZ layout tag Legal Message Code Legal Message Text

UFSaidaPais LACLS_BR_UF_SAIDA_PAIS *fill with information by company,

xLocExporta LACLS_BR_LOC_EXPORTA * fill with information by company,

xLocDespacho LACLS_BR_LOC_DESPACHO * fill with information by company,

In the FDG XML, this information is shown in <FISCAL_DOC_HEADER_DETAILS> group, when

These three Legal Messages Codes (LACLS_BR_UF_SAIDA_PAIS, LACLS_BR_LOC_EXPORTA and

123 1 ISS R$ 50,00

123 1 INSS R$ 70,00

123 2 ISS R$ 80,00

123 2 INSS R$ 150,00

In <infAdic> section of DANFE must appear: “Vl Retenção IR/ISS/INSS: 300,00/130,00/220,00”

• INSS → 9th paragraph of article 47 of Normative Instruction 971-2009

It’s recommended create a FDG template as below:

1) Navigate to Setup and Maintenance

Attribute Template LACLS_BR_WHT_TAX

Start Date *filled automatically with actual date

Legal Message Code Legal Message Text

6) Click on “Save and Close” button

The configuration will result something like this:

In the FDG XML, this information is shown in <FISCAL_DOC_HEADER_DETAILS> group, when

In “Additional Taxpayer Information” tab, put the information as example:

ITEM CATALOG: LACLS_CAT_CHARGES

item qtd unit amount shipment set Catalog Category

2) The BIP has a limitation about file size.

Example in Sales Order:

SETUP - ITEM CATALOG: LACLS_CAT_CHARGES

For to do this setup you must:

1) Navigate to Product Management

2) Navigate to Product Information Management

* Catalog Name LACLS_CAT_CHARGES

* Catalog Code LACLS_CAT_CHARGES

* Description LACLS Catalog Charges for Freight

* Controlled At Master Level

* Start Date 8/31/20

Assign items to leaf level Selected